Hi all, Forwarding to IDR to increase awareness about this WGLC.
Cheers, Med > -----Message d'origine----- > De : Paolo Lucente <[email protected]> > Envoyé : jeudi 19 mars 2026 12:11 > À : [email protected]; [email protected]; > [email protected] > Objet : [GROW] Re: WG Last Call: draft-ietf-grow-bgpopsecupd-12 > (Ends 2026-04-10) > > > Dears, > > We have just extended the WCLC for this document by another 3 > weeks, ending on 2026-04-10. This is to allow for further feedback > to the document and because two new versions of the document were > released since starting WGLC. > > Encouraging anybody who has read the document to provide feedback > or support WGLC by replying to this thread. > > Paolo > > > On 25/2/26 18:23, Paolo Lucente via Datatracker wrote: > > This message starts a WG Last Call for: > > draft-ietf-grow-bgpopsecupd-12 > > > > This Working Group Last Call ends on 2026-03-13 > > > > Abstract: > > The Border Gateway Protocol (BGP) is a critical component in > the > > Internet to exchange routing information between network > domains. > > Due to this central nature, it is important to understand > the > > security and reliability requirements that can and should be > ensured > > to prevent accidental or intentional routing disturbances. > > > > Previously, security considerations for BGP have been > described in > > RFC7454 / BCP194. Since the publications of RFC7454, > several > > developments and changes in operational practice took place > that > > warrant an update of these best current practices. This > document > > obsoletes RFC7454, focusing on the overall goals, and > providing a > > less implementation centric set of best practices. > > > > This document describes security requirements and goals when > > operating BGP for exchanging routing information with other > networks, > > and explicitly does not focus on specific technical > implementations > > and requirements. > > > > File can be retrieved from: > > > > Please review and indicate your support or objection to proceed > with > > the publication of this document by replying to this email > keeping > > [email protected] in copy. Objections should be explained and > suggestions > > to resolve them are highly appreciated. > > > > Authors, and WG participants in general, are reminded of the > > Intellectual Property Rights (IPR) disclosure obligations > described in BCP 79 [1]. > > Appropriate IPR disclosures required for full conformance with > the > > provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you > are aware of any. > > Sanctions available for application to violators of IETF IPR > Policy > > can be found at [3]. > > > > Thank you. ____________________________________________________________________________________________________________ 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. _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
