[DNSOP] Re: [Ext] Re: Mohamed Boucadair's Discuss on draft-ietf-dnsop-must-not-sha1-06: (with DISCUSS and COMMENT)

[[e-mail]]

Hi Paul, 

Looks like a plan. Thanks for taking the action to start draft-hoffman-rfc9364bis.

Cheers,
Med

> -----Message d'origine-----
> De : Paul Hoffman <[e-mail]>
> Envoyé : mardi 22 avril 2025 00:33
> À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> Cc : The IESG <[e-mail]>; draft-ietf-dnsop-must-not-
> [e-mail]; [e-mail]; [e-mail]; Tim Wicinski
> <[e-mail]>
> Objet : Re: [Ext] [DNSOP] Re: Mohamed Boucadair's Discuss on draft-
> ietf-dnsop-must-not-sha1-06: (with DISCUSS and COMMENT)
> 
> 
> On Apr 21, 2025, at 15:19, Wes Hardaker <[e-mail]>
> wrote:
> 
> . . .
> 
> >> # BCP237 Umbrella
> >>
> >> As a big fun of BCP237, I wonder whether we should make this
> more
> >> visible in our DNSSEC “roadmap” documentation and list this
> document
> >> under the BCP237 umbrella?
> >
> > So BCP237 currently only has one document within it (RFC9364).  I
> > think if we added every future DNSSEC document to the BCP it
> would
> > likely get overwhelming.  I would argue that whether or not and
> how
> > often we should update BCP237 is a good discussion for the WG as
> a
> > whole, but it's outside the scope of this particular document
> (set).  But that's very much IMHO.
> 
> As the (current) author of BCP 237, I fully agree with Wes here. It
> is now a bit over two years old; starting an update later this year
> seems appropriate, even if it just adds a few bullet points for new
> documents. Doing so absolutely should not block this draft.
> 
> --Paul Hoffman

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