> -----Original Message----- > From: Andy Newton <[email protected]> > Sent: Thursday, January 15, 2026 2:30 PM > To: [email protected]; [email protected]; [email protected] > Subject: [EXTERNAL] [regext] Re: I-D Action: > draft-ietf-regext-ext-registry-epp- > 01.txt > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > > Scott, > > I offer the following friendly amendments. > > -andy, as an individual
[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? Scott _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
