Hi Med,

I should've replied earlier about possible 7120/8126 issues you pointed out 
w/r/t this text:


"All assignments according to "IETF Review with Expert Review" are made on a 
"IETF Review" basis per Section 4.8 of [RFC8126] with "Expert Review" 
additionally required per Section 4.5 of [RFC8126]. The procedure for early 
IANA allocation of "standards track code points" defined in [RFC7120] also 
applies. When such a procedure is used, IANA will ask the designated expert(s) 
to approve the early allocation before registration."


The last sentence does describe IANA's existing approach to processing early 
allocation requests that require expert review, as in Specification Required 
registries. This isn't described in RFC 7120, but we don't want to make an 
early allocation and then wait to request expert review until IETF Last Call. 
This will be spelled out in 7120bis.


We're not sure there's an issue with making early allocations available for 
registries that use "IETF Review With Expert Review" (which is in wide use, and 
which is being documented in 8126bis and 7120bis). We understand these to be 
IETF Review registries that have an additional review step, and we already have 
a process for obtaining that review for early allocations. In addition, we 
understand that IETF Review is a kind of primary, overriding registration 
procedure. In describing Expert Review registrations requested in IETF Stream 
I-Ds, RFC 8126, Section 5.5 says, "It is also not intended for the expert 
review to override IETF consensus: the IESG should consider the review in its 
own evaluation, as it would do for other Last Call reviews."

thanks,
Amanda

________________________________
From: Mohamed Boucadair via Datatracker <[email protected]>
Sent: Friday, April 24, 2026 5:12 AM
To: The IESG
Cc: [email protected]; [email protected]; 
[email protected]; [email protected]
Subject: [Ext] [iesg] Mohamed Boucadair's No Objection on 
draft-ietf-cose-cbor-encoded-cert-18: (with COMMENT)

Mohamed Boucadair has entered the following ballot position for
draft-ietf-cose-cbor-encoded-cert-18: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!PtGJab4!6olvjPG-KL8KNkfOd9CxCsOyyglgluLS3Dz2MJboKf-g_xctc4sojL7v7vcy6LmyER4IgtRw_na2tFoYbe2X0Wo$
 [ietf[.]org]
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/__;!!PtGJab4!6olvjPG-KL8KNkfOd9CxCsOyyglgluLS3Dz2MJboKf-g_xctc4sojL7v7vcy6LmyER4IgtRw_na2tFoYrzP4iXk$
 [datatracker[.]ietf[.]org]



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi John, Göran, Shahid, Joel, and Martin,

Many thanks for the well-written document. Excellent work.

Thank you for the discussion and changes made in [1] to address comments in my
previous ballot [2].

I appreciate that consistency is followed by the authors vs the resolution to a
similar DISCUSS for RFC9668, but some of that text smells like updating the
rules in RFC7120.

Cheers,
Med

[1]
https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url1=draft-ietf-cose-cbor-encoded-cert-17&url2=draft-ietf-cose-cbor-encoded-cert-18&difftype=--html__;!!PtGJab4!6olvjPG-KL8KNkfOd9CxCsOyyglgluLS3Dz2MJboKf-g_xctc4sojL7v7vcy6LmyER4IgtRw_na2tFoYOFkV3Vs$
 [author-tools[.]ietf[.]org]

[2] 
https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/cose/m6QDwcY8SkSDtsUuLaJLOA-OfLY/__;!!PtGJab4!6olvjPG-KL8KNkfOd9CxCsOyyglgluLS3Dz2MJboKf-g_xctc4sojL7v7vcy6LmyER4IgtRw_na2tFoY3feFAgE$
 [mailarchive[.]ietf[.]org]


_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to