Moin, I just pushed a new version of this document (the extended version describing things that can be done to secure BGP as an informational that should never out-GROW the draft state) including one fix by Q Misell and changes re: two suggestions on the description of handling non-transitive (extended) communities and changing the prefix-limit suggestions to recommendations on monitoring.
As always, feedback would be highly appreciated. With best regards, Tobias On Wed, 2024-10-02 at 04:03 -0700, internet-dra...@ietf.org wrote: > A new version of Internet-Draft > draft-fiebig-grow-routing-ops-sec-inform-01.txt has been successfully > submitted by Tobias Fiebig and posted to the > IETF repository. > > Name: draft-fiebig-grow-routing-ops-sec-inform > Revision: 01 > Title: Current Options for Securing Global Routing > Date: 2024-10-02 > Group: Individual Submission > Pages: 53 > URL: > https://www.ietf.org/archive/id/draft-fiebig-grow-routing-ops-sec-inform-01.txt > Status: > https://datatracker.ietf.org/doc/draft-fiebig-grow-routing-ops-sec-inform/ > HTML: > https://www.ietf.org/archive/id/draft-fiebig-grow-routing-ops-sec-inform-01.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-fiebig-grow-routing-ops-sec-inform > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-fiebig-grow-routing-ops-sec-inform-01 > > Abstract: > > The Border Gateway Protocol (BGP) is the protocol is a critical > component in the Internet to exchange routing information between > network domains. Due to this central nature, it is an accepted > best > practice to ensure basic security properties for BGP and BGP > speaking > routers. While these general principles are outlined in BCP194, > it > does not provide a list of technical and implementation options > for > securing BGP. > > This document lists available options for securing BGP, serving as > a > contemporary, non-exhaustive, repository of options and methods. > The > document explicitly does not make value statements on the efficacy > of > individual techniques, not does it mandate or prescribe the use of > specific technique or implementations. > > Operators are advised to carefully consider whether the listed > methods are applicable for their use-case to ensure best current > practices are followed in terms of which security properties need > to > be ensured when operating BGP speakers. Furthermore, the listed > options 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 > > -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M tob...@fiebig.nl _______________________________________________ GROW mailing list -- grow@ietf.org To unsubscribe send an email to grow-le...@ietf.org
