trimming:
On 10/14/22 2:57 PM, Russ Housley wrote:
Robert:
Thanks for the prompt review.
Happy to be able to get it out quickly. Genart is crunched.
Minor Issue:
The document says operators need to not use colliding names but then explicitly
declaires on how an operator would know if a name is already in use is out of
scope. Surely there was a discussion about a registry, and the IESG is
certainly going to ask. It would save some time if you could add something to
the shepherd writeup explaining why a registry wasn't pursued in this document?
The standard ones are managed by 3GPP, so an IANA registry seems like an overstep.
3GPP makes use of IANA for many other things - maybe nudge from that side?
Nits:
At:
"The 49 NF types that are defined for 3GPP Release 17 listed in Table
6.1.6.3.3-1 of [TS29.510], and each NF type is identified by a short ASCII
string."
the sentence doesn't parse. Do you mean "are listed" or "There are 49 NF types"
or something else?
There are 49 NF Types defined in for 3GPP Release 17 listed in
Table 6.1.6.3.3-1 of [TS29.510].
At:
"The NFTypes MUST contain only an ASCII string, MUST contain at least one ASCII
character, and MUST NOT contain more than 32 ASCII characters."
I suggest "Each NFType MUST"
Yes. I will make that change.
At:
"The mechanism for an operator to determine whether an ASCII string associate
with a NF Type is unique across operators is outside the scope of this document"
I suggest "string associate with" -> "string is associated with"
Yes. I will make that change.
Russ
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
