Moin,
sorry for the double post, but after the submisision lock cleared i
first pushed the -13 i had announced earlier, and then the -14 with
further changes w.r.t. Jeff Haas' comments.

Also, quick reminder to the group: WGLC has technically ended on the
13th, but input so far was rather limited. Further comments on the
document would be really appreciated.

With best regards,
Tobias

On Mon, 2026-03-16 at 03:52 -0700, [email protected] wrote:
> A new version of Internet-Draft draft-ietf-grow-bgpopsecupd-14.txt
> has been
> successfully submitted by Tobias Fiebig and posted to the
> IETF repository.
> 
> Name:     draft-ietf-grow-bgpopsecupd
> Revision: 14
> Title:    BGP Operations and Security
> Date:     2026-03-16
> Group:    grow
> Pages:    9
> URL:     
> https://www.ietf.org/archive/id/draft-ietf-grow-bgpopsecupd-14.txt
> Status:  
> https://datatracker.ietf.org/doc/draft-ietf-grow-bgpopsecupd/
> HTML:    
> https://www.ietf.org/archive/id/draft-ietf-grow-bgpopsecupd-14.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-ietf-grow-bgpopsecupd
> Diff:    
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bgpopsecupd-14
> 
> 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 met
> 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.
> 
> 
> 
> 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]

Reply via email to