Moin, i just pushed a new version of the two informational documents on BGP security. Both got some changes since the previous version;
draft-ietf-grow-routing-ops-sec-inform probably got the most changes, with Jeff putting in significant work during 126, who now also is a co- author given the extent of input he gave so far. As always, feedback would be really appreciated! With best regards, Tobias On Fri, 2026-10-02 at 01:17 -0700, [email protected] wrote: > A new version of Internet-Draft draft-ietf-grow-routing-ops-sec- > inform-03.txt > has been successfully submitted by Tobias Fiebig and posted to the > IETF repository. > > Name: draft-ietf-grow-routing-ops-sec-inform > Revision: 03 > Title: Current Options for Securing Global Routing > Date: 2026-10-02 > Group: grow > Pages: 56 > URL: > https://www.ietf.org/archive/id/draft-ietf-grow-routing-ops-sec-inform-03.txt > Status: > https://datatracker.ietf.org/doc/draft-ietf-grow-routing-ops-sec-inform/ > HTML: > https://www.ietf.org/archive/id/draft-ietf-grow-routing-ops-sec-inform-03.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-ietf-grow-routing-ops-sec-inform > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-routing-ops-sec-inform-03 > > Abstract: > > The Border Gateway Protocol (BGP) is used for exchanging routing > information between Autonomous Systems in the Internet. Due to > its > importance, it is necessary to ensure the basic security > properties > for BGP and BGP speaking routers. While the general principles > for > securing BGP operations are outlined in RFC 7454, that document > does > not detail the technical and implementation options for securing > BGP. > > This document serves as a contemporary, non-exhaustive repository > of > options and methods for securing BGP. This document explicitly > does > not make value statements on the efficacy of individual > techniques, > nor does it mandate or prescribe the use of specific techniques or > implementation details. > > Operators are advised to carefully consider whether the listed > methods are applicable for their use-cases. Furthermore, the > options > listed in this document may change over time, and should not be > used > as a timeless ground-truth of applicable or sufficient methods. > > > > The IETF Secretariat > -- Univ.Prof. Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M [email protected] _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
