Hi, I believe that early allocation of code points is a good idea for drafts that have enough traction. In my understanding there is no issue with regards to scarcity, and having distinct code points will help to avoid issues like squatting, or using temporary code points that then need to be updated again - complicating interop development.
In short, I support. Tim > On 3 Jun 2026, at 17:55, Job Snijders <[email protected]> wrote: > > Dear GROW participants, > > We (GROW chairs) received a request to facilitate assignment of provisional > codepoints for the (RPKI-based) discovery mechanism described in Working Group > document draft-ietf-grow-yang-bgp-communities-08 section 8. Please see > https://www.ietf.org/archive/id/draft-ietf-grow-yang-bgp-communities-08.html > > In order to progress the specification by gaining pre-RFC-publication > implementation experience (and testing interoperability), some assignments > need to be made in the SMI Security for S/MIME CMS Content Type, SMI Security > for PKIX Access Descriptor, and RPKI Signed Object registries. > > We are following the "Early IANA Allocation of Standards Track Code Points" > procedure. See https://datatracker.ietf.org/doc/html/rfc7120 for more info. > > Our Area Director requested us to poll the Working Group on this topic > in order to qualify whether condition "d" in RFC 7120, Section 2 is met. > > Copied for context here: > > """ > d. The Working Group chairs and Area Directors (ADs) judge that there is > sufficient interest in the community for early (pre-RFC) implementation > and deployment, or that failure to make an early allocation might lead > to contention for the code point in the field. > """ > > This email starts a one week period during which anybody can let the WG > know if they support or object to Early IANA Allocation (if you object, > please state arguments). > > If there are no objections, we will proceed with the Early IANA > Allocation process. > > Kind regards, > > Job & Paolo > GROW co-chairs > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
