I'd be happy to delete all the explanatory and background text, and just
point to the NENA document. The text was added by request.
--Randall
On 8 Mar 2020, at 13:28, Pete Resnick wrote:
Hi Randy,
We probably at some core level disagree about whether "informational
text that explains how i
Hi Randy,
We probably at some core level disagree about whether "informational
text that explains how it is expected to be used" is in-and-of-itself
"normative"; I think in IETF documents, that's really all that it means.
But that might be moot: If the NENA document is going to be updated to
Hi Pete,
The document adds a tag. It also contains informational text that
explains how it is expected to be used. There isn't any normative text.
Once the tag is defined, then NENA i3 will be updated to refer to it,
and to mandate how NENA-compliant clients and servers use it. But a
non-
Hi Randy,
Section 3 of the document defines the operations that one must perform
in order to use the tag. It explains how to go beyond what 5222 provides
by defining which order to look up the servers and what to do depending
on the results received. It changes the discovery procedure defined
Hi Pete,
I don't see this as a new protocol. It is a new service tag that is
optional to use. Not using it won't break anything that wouldn't be
broken without the tag being defined. Using it is an optimization. I
see the draft as only adding a new tag, not defining a new protocol.
--Ran
Thanks, Pete, for a very helpful review.
Barry
On Sat, Mar 7, 2020 at 11:52 AM Pete Resnick via Datatracker <
nore...@ietf.org> wrote:
> Reviewer: Pete Resnick
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all I
