Hi Göran,

Thank you for the follow-up and for the changes made in -18.

Please see inline.

Cheers,
Med

De : Göran Selander <[email protected]>
Envoyé : vendredi 17 avril 2026 17:07
À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; The IESG 
<[email protected]>
Cc : [email protected]; [email protected]; 
[email protected]; [email protected]
Objet : Re: Mohamed Boucadair's Discuss on 
draft-ietf-cose-cbor-encoded-cert-17: (with DISCUSS and COMMENT)


Hi Med,

Thanks for your review.

Please find responses inline inside brackets: <<GS: ... >>. Apologies for any 
hiccups with the formatting.


From: Mohamed Boucadair via Datatracker 
<[email protected]<mailto:[email protected]>>
Date: Friday, 10 April 2026 at 12:54
To: The IESG <[email protected]<mailto:[email protected]>>
Cc: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
 
<[email protected]<mailto:[email protected]>>;
 [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>
Subject: Mohamed Boucadair's Discuss on draft-ietf-cose-cbor-encoded-cert-17: 
(with DISCUSS and COMMENT)
Mohamed Boucadair has entered the following ballot position for
draft-ietf-cose-cbor-encoded-cert-17: Discuss

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.)


----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

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

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

I have two points to check. I flagged some few nits and minor edits that I will
send to the authors in a PR.

# IETF Review with Expert Review

CURRENT:
  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}}.

and

 the registration procedure is "IETF Review with Expert Review".

I remember that Carsten edited draft-bormann-gendispatch-with-expert-review,
but do we have a stable reference where such policy is defined?

# The WG may be closed: not sure how this guidance will age

CURRENT:
  In addition, working group chairs are encouraged to consult the expert(s)
  early during the process outlined in Section 3.1 of {{RFC7120}}.


<<GS: During the IESG evaluation of RFC 9668, John Scudder raised a DISCUSS [0] 
about the IANA considerations using these hybrid registration policies, which 
were not fully specifying their use in the context of the new registry and what 
it meant to use those with respect to the early allocation process. The result 
was text that we are consistently using in several drafts, see for example [1].

So, the paragraph which this DISCUSS is about is just following previous 
resolutions of IESG discussions.
Regarding how this guidance will age, note that it the reference to working 
group chairs is not referring to potential closed WGs.

[0] https://mailarchive.ietf.org/arch/msg/core/CaK5R4gq1wc3CN5-dTN3uRXoU2U/

[1] https://www.ietf.org/rfc/rfc9668.html#section-8.3-3
>>

[Med] I went through that thread and I agree that we need to be consistent. I 
consider my main point closed. Note that I still prefer if we could avoid 
including text that smells like an update to rfc7120#section-3.1:

CURRENT:
 In addition, working group chairs are encouraged to consult the expert(s) 
early during the process outlined in Section 
3.1<https://rfc-editor.org/rfc/rfc7120#section-3.1> of 
[RFC7120<https://www.ietf.org/rfc/rfc9668.html#RFC7120>].

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

# Is this already deployed there or these are deployment targets?

CURRENT:
  C509 is deployed in, e.g., in-vehicle and vehicle-to-cloud communication,
  Uncrewed Aircraft Systems (UAS), and Global Navigation Satellite System (GNSS)

"is deployed" won't age well in an RFC, btw.


<<GS: Thanks, rephrased in PR#354:
https://github.com/cose-wg/CBOR-certificates/pull/354/changes
>>
[Med] ACK

# Please consider adding a reference

CURRENT :

  the CBOR encoding can in many cases reduce the size of  RFC7925 profiled
  certificates by over 50%.

<<GS: Thanks, reference to table added in PR#354:
https://github.com/cose-wg/CBOR-certificates/pull/354/changes
>>
[Med] ACK



# Any reason why this is repeated here?

CURRENT:
  The procedure for early IANA allocation of "standards track code points"
  defined in {{RFC7120}} also applies.

<<GS: The same argument as in the DISCUSS applies here. >>
[Med] Repeating this is an indication that we are not confident that this falls 
under:

   a.  The code points must be from a space designated as "RFC
       Required", "IETF Review", or "Standards Action".  Additionally,
       requests for early assignment of code points from a
       "Specification Required" registry are allowed if the
       specification will be published as an RFC.

and hence an explicit mention is needed ...which is an update to 7120!

Thanks,
Göran


____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to