Dear colleagues, thanks again for the engagement with the draft so far. I just posted a new ID incorporating the feedback so far received. Special thank you to Jeff, who also provided a large diff.
For the diff: https://author-tools.ietf.org/iddiff?url1=draft-ietf-grow-bgpopsecupd-14&url2=draft-ietf-grow-bgpopsecupd-15&difftype=--html The WGLC deadline is in three days; Feedback so far was somewhat limited. The document is a very short read, and it would be really appreciated to get some more feedback, or--ideally--agreement. ;-) So, if you have some time to give the draft a read, please do so before the 10th! With best regards, Tobias On Thu, 2026-03-19 at 19:10 +0800, Paolo Lucente wrote: > > 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. > > > > [1] https://datatracker.ietf.org/doc/bcp78/ > > [2] https://datatracker.ietf.org/doc/bcp79/ > > [3] https://datatracker.ietf.org/doc/rfc6701/ > > > > The IETF datatracker status page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-ietf-grow-bgpopsecupd/ > > > > There is also an HTML version available at: > > https://www.ietf.org/archive/id/draft-ietf-grow-bgpopsecupd-12.html > > > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bgpopsecupd-12 > > > > _______________________________________________ > > GROW mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M [email protected] Pronouns: he/him/his _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
