https://github.com/anima-wg/constrained-join-proxy/commit/ae753b1d9bdfda9bd92633c6270e73af1ae33590
Amanda Baber via RT <[email protected]> wrote: > https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-join-proxy-20 > Section 8.3: draft-ietf-core-href (currently in the RFC Ed Queue) added > a field called "CRI Scheme Number" to the URI Schemes registry. Please > add one of the following lines to the URI scheme registration template: > CRI Scheme Number: TBA from the Expert Review range > CRI Scheme Number: TBA from the First Come First Served range okay... But, href-30 says: | Identifier (URI) Schemes Registry may indicate that there are | special requirements on the CRI scheme number to be assigned for | the new URI Scheme. | If that is not the case, IANA will assign a value autonomously. As we *DO NOT* have special requirements, it would be fine: If no requirement is specified in the registration, IANA will autonomously assign a number in the range 1000 to 20000, inclusive, that has not yet been used. (As far as I know, we can not use the CRI in the core?rt= reply) > Section 8.4: According to RFC 6335, Section 8.1.1, the contact for the > port registrations should be the IETF Chair <[email protected]> rather > than the IESG. Okay. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
