draft: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-link-mtu/
Draft: 10
Status: WG draft
Type: Proposed Standard
Implementations: Unknown, need 2 for WG LC
draft status: Awaiting Early Allocation + implementations
Early Allocation: Requires -11 RFC9552
email link:shepherd report on -10
Text in section 5 states:
This document requests assigning a new code-point from the BGP-LS Link Descriptor and Attribute TLVs registry as specified in section 4.
This document requests assigning a new code-point from the BGP-LS Link Descriptor and Attribute TLVs registry as specified in section 4. Please update this sub-registry name to RFC9552 naming convention.
Draft: 08
Status: WG draft
Type: Proposed Standard
Implementations: Unknown, need 2 for WG LC
draft status: Awaiting implementations
email link: https://mailarchive.ietf.org/arch/msg/idr/QMV7MShOKt-GaajNdaTRaJzFLHc/
Status: All technical issues from -07 resolved
This document requests assigning a new code-point from the BGP-LS Link Descriptor and Attribute TLVs registry as specified in section 4.
**draft: ** 07
Status: WG draft
Implementations: TBD
email to shepherd: https://mailarchive.ietf.org/arch/msg/idr/enE8GGZ9dueP4PXdoj2bZS0w50w/
Shepherd report for draft-ietf-idr-bgp-ls-link-mtu-07
Status: WG Document
Implementations: Unknown, need 2 for WG LC
draft status: Needs
Summary of Review: Needs -08 prior to WG LC
Status: Needs to resolve 4 technical issues and 1 editorial.
Old text:/
[I-D.ietf-idr-bgp-ls-segment-routing-ext] defines SR extensions to
BGP-LS and specifies the TLVs and sub-TLVs for advertising SR
information. /
New text:/
[RFC9085] defines SR extensions to
BGP-LS and specifies the TLVs and sub-TLVs for advertising SR
information.
Link MTU provides proprietary information regarding a network.
See security section in draft-ietf-idr-bgp-ls-sr-policy-05
for consideration.
Please consider adding many of the points from this section include:
The abstract needs to be 2 paragraphs. Please just remove paragraph 2.