Hi Camilo, > > Do you mean the index field from the general TLV header described in > https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv? > Yes. Thank you for your pointer! Now I understand that the Common TLV Header is as follows: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (2 octets) | Length (2 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |G| Index (15 bits) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I have no further questions now.
Thanks, Shunwan > -----Original Message----- > From: Camilo Cardona [mailto:[email protected]] > Sent: Thursday, April 24, 2025 10:06 PM > To: Zhuangshunwan <[email protected]> > Cc: [email protected] > Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-path-marking-tlv-03.txt > > Hello Shunwan, > > Do you mean the index field from the general TLV header described in > https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv? > > Thanks, > Camilo C > > > On 23 Apr 2025, at 21:58, Zhuangshunwan <[email protected]> > wrote: > > > > Dear Authors, > > > > Thanks for the update! > > One comment: According to the latest documentation, how do implementers > know that the Path Status TLV needs to carry an index? > > > > Best Regards, > > Shunwan > > > >> -----Original Message----- > >> From: Camilo Cardona [mailto:[email protected]] > >> Sent: Thursday, April 24, 2025 6:15 AM > >> To: [email protected] > >> Subject: [GROW] Re: I-D Action: > >> draft-ietf-grow-bmp-path-marking-tlv-03.txt > >> > >> Hello grow, > >> > >> Here is a summary of the changes for this version of the bmp path > >> marking draft. > >> > >> - Incorporated editorial improvements, with thanks to Med for many > >> suggestions. > >> - Removed content redundant with the TLV and ebit drafts. > >> - Added a section discussing churn, in response to Jeff’s comments. > >> Since use cases vary, the draft doesnt provide a solution, but > >> explains the potential impact and possible mitigations. Also, updated > >> the handling of unmarked paths to recommend explicitly marking them > >> since it was discussed how an implementation might not include the > >> TLV until it considered appropriate to reduce churn. > >> - Added a section on path status consistency, discussing how actul > >> implementations might diverge from the standard definitions; this > >> will require further discussion in how detailed we should be. > >> - Added security considerations. > >> > >> Please reach out for any suggestions. > >> > >> Thanks, > >> Authors > >> > >>> On 23 Apr 2025, at 17:08, [email protected] wrote: > >>> > >>> Internet-Draft draft-ietf-grow-bmp-path-marking-tlv-03.txt is now > available. > >>> It is a work item of the Global Routing Operations (GROW) WG of the IETF. > >>> > >>> Title: BMP Extension for Path Status TLV > >>> Authors: Camilo Cardona > >>> Paolo Lucente > >>> Pierre Francois > >>> Yunan Gu > >>> Thomas Graf > >>> Name: draft-ietf-grow-bmp-path-marking-tlv-03.txt > >>> Pages: 12 > >>> Dates: 2025-04-23 > >>> > >>> Abstract: > >>> > >>> The BGP Monitoring Protocol (BMP) provides an interface for > >>> obtaining BGP path information, which is is conveyed through BMP > >>> Route Monitoring (RM) messages. This document specifies a BMP > >>> extension to convey the status of a path after being processed by the > BGP process. > >>> > >>> The IETF datatracker status page for this Internet-Draft is: > >>> https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-path-marking-tl > >>> v/ > >>> > >>> There is also an HTMLized version available at: > >>> > >> https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-path-markin > >> g-tlv-03 > >>> > >>> A diff from the previous version is available at: > >>> > >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-path-ma > >> rking-tlv > >> -03 > >>> > >>> Internet-Drafts are also available by rsync at: > >>> rsync.ietf.org::internet-drafts > >>> > >>> > >>> _______________________________________________ > >>> GROW mailing list -- [email protected] > >>> To unsubscribe send an email to [email protected] > >> > >> _______________________________________________ > >> GROW mailing list -- [email protected] > >> To unsubscribe send an email to [email protected] _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
