Hi all,

FYI, we've just uploaded a new version of our bmp-offline draft.
(Formerly known as "BMP State Summaries", now renamed to "BMP Snapshots")


Best,
 luuk


----- Forwarded message from [email protected] -----

> Date: Mon, 20 Oct 2025 00:18:10 -0700
> From: [email protected]
> To: [email protected]
> Subject: I-D Action: draft-lucente-grow-bmp-offline-02.txt
> 
> Internet-Draft draft-lucente-grow-bmp-offline-02.txt is now available.
> 
>    Title:   BMP Snapshots
>    Authors: Luuk Hendriks
>             Paolo Lucente
>             Camilo Cardona
>             Colin Petrie
>    Name:    draft-lucente-grow-bmp-offline-02.txt
>    Pages:   16
>    Dates:   2025-10-20
> 
> Abstract:
> 
>    BMP (BGP Monitoring Protocol) is perfectly suited for real-time
>    consumption but less ideal in stream processing and off-wire
>    historical scenarios.  The issue is that the necessary information to
>    produce a complete view and enabling correct processing of all
>    messages in the stream, is only sent out at the beginning of the BMP
>    session.  This document introduces the concept of BMP Snapshots,
>    enabling BMP stations to synchronize mid-stream, and, providing the
>    basis for self-contained, time-binned archiving of BMP data.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-lucente-grow-bmp-offline/
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-offline-02
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-lucente-grow-bmp-offline-02
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

----- End forwarded message -----

_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to