Hi all, draft-ietf-dnsop-ds-automation currently under IESG review is heading to be published as BCP. RFC2026 says:
A specification, or group of specifications, that has, or have been approved as a BCP is assigned a number in the BCP series while retaining its RFC number(s). I'd like to hear the WG preference about whether to cluster draft-ietf-dnsop-ds-automation with an existing BCP (and provide one single entry for IETF DNSSEC recos) or assign a new BCP number for it. Clustering is a way to structure RFCs/Guidance we are producing. We do have so far these two BCP numbers: * BCP 207 consists currently of RFC 8027 on DNSSEC Roadblock Avoidance * BCP 237 consists currently of RFC 9364 on DNS Security Extensions (DNSSEC) My current take is to add draft-ietf-dnsop-ds-automation under BCP 237 (*), but I'm open to WG feedback. Thank you. Cheers, Med (*) Guidance for referencing a specific RFC under a BCP/STD can be seen at https://authors.ietf.org/en/reference-style-guidance: Internet Standards (STDs) and Best Current Practices (BCPs) may consist of a single RFC or multiple RFCs. When an STD or BCP as a whole is referenced, the reference entry should include ALL of the RFCs comprising that subseries at the time of writing. The authors should refer to specific RFC numbers as part of the text (not as citations) and cite the subseries number. The URI to the STD or BCP info page is to be included. The text should appear as follows: See RFC 3552<https://datatracker.ietf.org/doc/rfc3552/> [BCP72]. ____________________________________________________________________________________________________________ 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.
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
