Hi all, Just to inform you we've just uploaded the -01 version of this document. It's basically a rewrite as we propose an approach quite different from the -00, so we are looking forward to your comments either here on the list or in Bangkok in a few weeks.
Thanks, luuk ----- Forwarded message from internet-dra...@ietf.org ----- > Date: Sat, 01 Mar 2025 05:43:27 -0800 > From: internet-dra...@ietf.org > To: Camilo Cardona <cam...@ntt.net>, Colin Petrie <co...@ntt.net>, Luuk > Hendriks <l...@nlnetlabs.nl>, Paolo Lucente <pa...@ntt.net> > Subject: New Version Notification for draft-lucente-grow-bmp-offline-01.txt > > A new version of Internet-Draft draft-lucente-grow-bmp-offline-01.txt has been > successfully submitted by Luuk Hendriks and posted to the > IETF repository. > > Name: draft-lucente-grow-bmp-offline > Revision: 01 > Title: BMP State Summaries > Date: 2025-03-01 > Group: Individual Submission > Pages: 9 > URL: > https://www.ietf.org/archive/id/draft-lucente-grow-bmp-offline-01.txt > Status: https://datatracker.ietf.org/doc/draft-lucente-grow-bmp-offline/ > HTMLized: https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-offline > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-lucente-grow-bmp-offline-01 > > Abstract: > > BMP (BGP Monitoring Protocol) is perfectly suited for real-time > consumption but less ideal in stream processing and off-wire > historical scenarios. The main issue is that the ability to > correctly parse BGP Update PDUs, carried in BMP Route Monitoring > messages, depends on the BGP Capabilities exchanged during the > establishment of the BGP session between the peers via BGP Open PDUs. > The BGP Open PDUs, carried in BMP Peer Up Notification messages, are > exported at the establishment of the BMP session. Similar to BGP, > BMP sessions are typically long-lived, so the crucial information to > correctly parse subsequent messages of such sessions was possibly > sent a relatively long time ago (days, weeks, months). > > This document introduces the concept of Summaries. It defines a new > optional BMP message type, called State Summary, and a new TLV, > called Summary Id. A Summary is similar to the initial > synchronisation performed upon establishment of the BMP session: all > BGP session information is exported in Peer Up Notification messages, > and all RIB contents are exported in Route Monitoring messages. All > the messages carry the new Summary Id TLV, containing an ID uniquely > identifying the summary these messages belong to. The messages are > preceded by a State Summary message carrying the same Summary Id TLV, > as well as meta-data describing the Summary. > > > > The IETF Secretariat > > ----- End forwarded message ----- _______________________________________________ GROW mailing list -- grow@ietf.org To unsubscribe send an email to grow-le...@ietf.org
