Hi Kyzer, Thank for your clarification here. It looks like you have taken the text in section 4.3 of RFC4122 "Convert the name to a canonical sequence of octets (as defined by the standards or conventions of its name space); put the name space ID in network byte order.” and rephrased it in this draft. My question remains - what is a “canonical” sequence of octets? Or even its opposite - what is a sequence of octets that is NOT “canonical”? In a standards document it seems reasonable to ask for extremely clear specifications, and I just don’t understand what you are getting at with the use of the term “canonical” here. regards, Geoff > On 28 Aug 2023, at 6:39 am, Kyzer Davis (kydavis) <kydavis@xxxxxxxxx> wrote: > > Geoff and Michael, > > The entire sub-section in 6.5 titled "a note on names" was added in draft-08 to explicitly provide context around name usage, selection and provide a few examples from each of the called out dependencies. > > I can add a reference so the earlier sections that state "canonical sequence of octets in network byte order" have a link to 6.5's sub-section letting folks know where to go to understand what that means? > > Also, to note, I did not pick "canonical sequence of octets in network byte order" this is from the original specs; I am open to a different verbiage to describe this. > > Thanks, > > -----Original Message----- > From: Michael Richardson <mcr+ietf@xxxxxxxxxxxx> > Sent: Saturday, August 26, 2023 2:59 PM > To: Geoff Huston <gih@xxxxxxxxx>; dnsdir@xxxxxxxx; draft-ietf-uuidrev-rfc4122bis.all@xxxxxxxx; last-call@xxxxxxxx; uuidrev@xxxxxxxx > Subject: Re: [Last-Call] Dnsdir telechat review of draft-ietf-uuidrev-rfc4122bis-10 > > > Geoff Huston via Datatracker <noreply@xxxxxxxx> wrote: >> "Section 5.3, 5.5 and 6.5 refer to "a canonical sequence of octets in >> network byte order". It is not specified what that canonical sequence >> is nor is there a reference to a document that specifies the canonical >> sequence for any of the name spaces." > > I think that we generally expect people to use a string, literally, "example.com" > and I think that the words "network byte order" might be what confuses. > > Maybe some people would use RFC1035 sequence of labels format though. > > In the end, it doesn't matter as along as the entity creating the name-based UUID says what they did. Still, I agree that it would be good if we gave more advice here. > > Are there some references you would suggest here, assuming that we just want a string. > > > -- > Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
