Hi Matthias, Indeed, adding an ADD-PATH capability TLV to the Route Monitoring message will be a good use case. In this way, when the BMP server parses the BGP Update message containing the ADD-PATH ID, it does not need to check the related Peer Up notification message again.
BR, Shunwan -----Original Message----- From: GROW [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, December 6, 2021 2:54 PM To: [email protected]; [email protected] Cc: [email protected] Subject: Re: [GROW] On LC for draft-ietf-grow-bmp-tlv (ends December 1st 2021) Hallo GROW WG I've read the draft. TLV on BMP monitoring- and peerdown-messages complete BMP and make it uniform. I am looking very forward to collect ADD-PATH on our collectors as a standard to bring more visability (a.e. backup-path) to our BGP monitoring. I think the draft is ready to forward to IESG. Have a good week Matthias -----Original Message----- From: GROW <[email protected]> On Behalf Of Job Snijders Sent: Dienstag, 16. November 2021 17:16 To: Paolo Lucente <[email protected]> Cc: [email protected] [email protected] <[email protected]> Subject: Re: [GROW] On LC for draft-ietf-grow-bmp-tlv (ends December 1st 2021) Dear all, This starts the formal WGLC period which will run from November 16th until December 1st 2021. Please review https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-grow-bmp-tlv-06&data=04%7C01%7CMatthias.Arnold%40swisscom.com%7C67562bce3536413b2e1008d9a91ca0db%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637726762696880424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1FAQOy3X%2FtjxztaFoNEwcOT4bZGliXRcnTHZbFPc%2FRQ%3D&reserved=0 and provide comments or feedback on the [email protected] mailing list! Kind regards, Job On Tue, Nov 16, 2021 at 05:11:56PM +0100, Paolo Lucente wrote: > Dear Colleagues, Dear Chairs, > > A brief email to follow-up the presentation of draft-ietf-grow-bmp-tlv > last week at the WG meeting. We authors believe there are no more > items to work on for this draft, received inputs were processed and > any questions / concerns were addressed. I'd hence like to ask to LC this > work. > > You may read motivation for this work in the draft itself, let me > supplement it saying that this is a key piece of work that would make > extensible every BMP message defined so far; this, in turn, would > bring BMP on par with other modern monitoring (/ telemetry) protocols (/ > stacks / solutions). > > Paolo > > _______________________________________________ > GROW mailing list > [email protected] > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ietf.org%2Fmailman%2Flistinfo%2Fgrow&data=04%7C01%7CMatthias.Arnol > d%40swisscom.com%7C67562bce3536413b2e1008d9a91ca0db%7C364e5b87c1c7420d > 9beec35d19b557a1%7C0%7C0%7C637726762696880424%7CUnknown%7CTWFpbGZsb3d8 > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3 > 000&sdata=kVCMQOI9D41eBKF4%2FdYiZHyuEG%2Bdm3eM7ls5yLzCSzU%3D&r > eserved=0 _______________________________________________ GROW mailing list [email protected] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fgrow&data=04%7C01%7CMatthias.Arnold%40swisscom.com%7C67562bce3536413b2e1008d9a91ca0db%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637726762696880424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kVCMQOI9D41eBKF4%2FdYiZHyuEG%2Bdm3eM7ls5yLzCSzU%3D&reserved=0 _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
