Apologies, I’ve not been tracking, but I’m confused. How is this "document replaces RFC7454 / BCP194?”
One of the biggest risk on the Internet today is operator’s ignoring RFC7454 / BCP194. https://dashboard.shadowserver.org/statistics/combined/tree/?day=2023-06-28&source=population&source=population6&tag=bgp&geo=all&data_set=count&scale=log > On Apr 9, 2025, at 7:49 AM, Tobias Fiebig <[email protected]> > wrote: > > Moin, > > with the two E-Ds being adopted, I now pushed a version of the document > referencing those. > > How shall we proceed now? > > With best regards, > Tobias > > > On Wed, 2025-04-09 at 07:48 -0700, [email protected] wrote: >> Internet-Draft draft-ietf-grow-bgpopsecupd-06.txt is now available. >> It is a >> work item of the Global Routing Operations (GROW) WG of the IETF. >> >> Title: Updated BGP Operations and Security >> Authors: Tobias Fiebig >> Nick Hilliard >> Name: draft-ietf-grow-bgpopsecupd-06.txt >> Pages: 8 >> Dates: 2025-04-09 >> >> 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 / BCP194, >> several developments and changes in operational practice took >> place >> that warrant an update of these best current practices. This >> document replaces RFC7454 / BCP194, focusing on the overall goals, >> and providing a less implementation centric set of best practices. >> >> To this end, the document describes the security requirements and >> goals when operating BGP for exchanging routing information with >> other networks. The document explicitly does not focus on >> specific >> technical implementations and requirements. Operators are advised >> to >> consult documentation and contemporary informational documents >> concerning methods to ensure that these properties are >> sufficiently >> ensured in their network. >> >> 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-06.html >> >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bgpopsecupd-06 >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> 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]
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
