On 1/15/26 2:46 PM, Hollenbeck, Scott wrote: > [SAH] Before I comment on anything below, we need to discuss the > applicability of RFC 7120. It's focused on "Early IANA Allocation of > Standards Track Code Points". I want to emphasize the "Code Points" part of > the title. I didn't find a concise definition in 7120 that describes what a > code point is, but the acceptability of your replacement text hinges on > whether or not an Internet-Draft can be described as a code point. It seems > like a stretch to me since an I-D isn't a value that needs to be implemented > in code where interoperability depends on value agreement. It's not exactly a > TCP port number, for example. > > That's just my take. What do others think?
Do we really want to rathole on what is and what is not a "code point"? Is it only a value of no more than one octet? Can a 1 million bit number be a code point? Are OIDs code points, because they too are sequences of octets, just like a URI. And OIDs are definitely used in IETF early registrations. The point is that 7120 describes the process for early registrations. It is well used in the IETF and we would not be doing anything unusual. You stated during the interim that it would be difficult to write the instructions for doing early registrations, and the text on offer shows that you do not need to do so... it already exists in an RFC. -andy, as an individual _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
