[GROW] I-D Action: draft-ietf-grow-bmp-rel-00.txt

2023-12-07 Thread internet-drafts
Internet-Draft draft-ietf-grow-bmp-rel-00.txt is now available. It is a work
item of the Global Routing Operations (GROW) WG of the IETF.

   Title:   Logging of routing events in BGP Monitoring Protocol (BMP)
   Authors: Paolo Lucente
Camilo Cardona
   Name:draft-ietf-grow-bmp-rel-00.txt
   Pages:   8
   Dates:   2023-12-07

Abstract:

   The BGP Monitoring Protocol (BMP) does provision for BGP session
   event logging (Peer Up, Peer Down), state synchronization (Route
   Monitoring), debugging (Route Mirroring) and Statistics messages,
   among the others.  This document defines a new Route Event Logging
   (REL) message type for BMP with the aim of covering use-cases with
   affinity to alerting, reporting and on-change analysis.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-rel/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-rel-00

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] The GROW WG has placed draft-msri-grow-bmp-bgp-rib-stats in state "Call For Adoption By WG Issued"

2023-12-07 Thread Thomas.Graf
Dear GROW,

I support the adoption of the document.

Some comments for the authors:

I suggest to reference RFC 9494 in TBD6 of section 2.1 to clearly describe the 
meaning.

Regarding TBD5, the meaning of "marked as stale by any configuration" is 
unclear to me. Please describe in more detail.

Would you consider to align the proposed counters to what is being defined in 
section 2.1 of BMP path status 
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-path-marking-tlv-00#section-2.1
 ?

>From an operator perspective, this would make a lot of sense since depending 
>on use case a statistical peering or per path view is needed.

Best wishes
Thomas

-Original Message-
From: GROW  On Behalf Of IETF Secretariat
Sent: Wednesday, December 6, 2023 6:18 PM
To: draft-msri-grow-bmp-bgp-rib-st...@ietf.org; grow-cha...@ietf.org; 
grow@ietf.org
Subject: [GROW] The GROW WG has placed draft-msri-grow-bmp-bgp-rib-stats in 
state "Call For Adoption By WG Issued"


Be aware: This is an external email.



The GROW WG has placed draft-msri-grow-bmp-bgp-rib-stats in state Call For 
Adoption By WG Issued (entered by Job Snijders)

The document is available at
https://datatracker.ietf.org/doc/draft-msri-grow-bmp-bgp-rib-stats/


___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

smime.p7s
Description: S/MIME Cryptographic Signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] The GROW WG has placed draft-fiebig-grow-bgpopsecupd in state "Call For Adoption By WG Issued"

2023-12-07 Thread Thomas.Graf
Dear GROW,

I support the adoption of document. It gives a network operator a good overview 
on BGP security considerations.

Best wishes
Thomas

-Original Message-
From: GROW  On Behalf Of IETF Secretariat
Sent: Wednesday, December 6, 2023 6:17 PM
To: draft-fiebig-grow-bgpopsec...@ietf.org; grow-cha...@ietf.org; grow@ietf.org
Subject: [GROW] The GROW WG has placed draft-fiebig-grow-bgpopsecupd in state 
"Call For Adoption By WG Issued"


Be aware: This is an external email.



The GROW WG has placed draft-fiebig-grow-bgpopsecupd in state Call For Adoption 
By WG Issued (entered by Job Snijders)

The document is available at
https://datatracker.ietf.org/doc/draft-fiebig-grow-bgpopsecupd/


___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

smime.p7s
Description: S/MIME Cryptographic Signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] The GROW WG has placed draft-pels-grow-yang-bgp-communities in state "Call For Adoption By WG Issued"

2023-12-07 Thread Thomas.Graf
Dear GROW,

I support the adoption of the document.

Some comments for the authors:

I suggest to reference RFC 9494 in TBD6 of section 2.1 to clearly describe the 
meaning.

Regarding TBD5, the meaning of "marked as stale by any configuration" is 
unclear to me. Please describe in more detail.

Would you consider to align the proposed counters to what is being defined in 
section 2.1 of BMP path status 
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-path-marking-tlv-00#section-2.1
 ?

>From an operator perspective, this would make a lot of sense since depending 
>on use case a statistical peering or per path view is needed.

Best wishes
Thomas

-Original Message-
From: GROW  On Behalf Of IETF Secretariat
Sent: Wednesday, December 6, 2023 6:19 PM
To: draft-pels-grow-yang-bgp-communit...@ietf.org; grow-cha...@ietf.org; 
grow@ietf.org
Subject: [GROW] The GROW WG has placed draft-pels-grow-yang-bgp-communities in 
state "Call For Adoption By WG Issued"


Be aware: This is an external email.



The GROW WG has placed draft-pels-grow-yang-bgp-communities in state Call For 
Adoption By WG Issued (entered by Job Snijders)

The document was previously in state Candidate for WG Adoption

The document is available at
https://datatracker.ietf.org/doc/draft-pels-grow-yang-bgp-communities/


___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

smime.p7s
Description: S/MIME Cryptographic Signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow