Dear all, We received only positive feedback from various distinct stakeholders regarding advancing draft-ietf-grow-bmp-adj-rib-out towards RFC. I'd like state that it appears there is consensus to advance. Thank you all for your input.
Also, IANA has made early allocations for the code points specified in draft-ietf-grow-bmp-adj-rib-out-02. Please review https://www.iana.org/assignments/bmp-parameters for this information. If you have implemented (parts of) draft-ietf-grow-bmp-adj-rib-out, please using these freshly assigned codepoints! We'll now work to advance the document to the next stage. Kind regards, Job On Sat, Dec 01, 2018 at 06:02:57PM +0100, Job Snijders wrote: > Hi all, > > We have only three (positive) responses so far, I’ll let the WGLC run > December 7th to allow opportunity for more responses. > > Kind regards, > > Job > > On Fri, Nov 9, 2018 at 15:08 Job Snijders <[email protected]> wrote: > > > Dear GROW, > > > > As suggested in the working group meeting in Bangkok, > > draft-ietf-grow-bmp-adj-rib-out may ready for last call. The last call > > will be 2 weeks ending November 26th, 2018. > > > > Abstract: > > > > The BGP Monitoring Protocol (BMP) defines access to only the > > Adj-RIB- In Routing Information Bases (RIBs). This document updates > > the BGP Monitoring Protocol (BMP) RFC 7854 by adding access to the > > Adj-RIB- Out RIBs. It adds a new flag to the peer header to > > distinguish Adj- RIB-In and Adj-RIB-Out. > > > > The document is at > > https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-adj-rib-out > > > > Please review the document and provide feedback. > > > > Kind regards, > > > > Job & Chris _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
