Next step prior to WG-LC: Revise for -01, After -01 then fill out implementation reports.
Upon -01, IDR shepherd will review and send to Directorates (RTG, OPS) and SROPS
draft: draft-ietf-idr-sr-epe-over-l2bundle
Note: renamed draft: draft-ietf-idr-bgpls-sr-epe-over-l2bundle
Type: Proposed Standard
status: Need -01 revision for early allocatnoi
adopted: 9/1/2024 (8/1 to 8/30 call)
current version: -00
implementations: 2 (New H3C Technologies and ZTE Corp)
IANA Allocations: none needed
SR draft: none
Next step prior to WG-LC:
None of the technical issues cited in the shepherd's review for -00 have been addressed. Please release a version -02 with these issue
**draft (-00): draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle
It is unclear what is optional in this portion of the bullet.
Please revise this text to provide a clear indication of what is optional.
- include the PeerAdj SID TLV [RFC9086] for Peer Link(Optional)
(Given 2 implementations, it should be easy to write the correct text.
It is also unclear what is optional in the similar portion of the text in section 3.2:
Link Attribute TLV:
- include the SRv6 End.X SID TLV [RFC9514] for Peer
Link (optional)
Security section needs to be updated to indicate the fact that
you are exposing L2 bundles - which are critical information about the
Peer Adjency infrastructure. Care must be taken to protect any
critial information from the node as it gets passed via BGP-LS.
If you need help with the exact wording, please let me know.
Current text:
This information mustnot be
included in the BGP-LS Link NLRI that corresponds to the PeerNode
SID, as defined in Section 5.1 of [RFC9086].
replace with:
This information must not be
included in the BGP-LS Link NLRI that corresponds to the PeerNode
SID, as defined in Section 5.1 of [RFC9086].
Note that for directly connected EBGP neighbors, if a BGP neighbor is
established over an L2 Bundle, an additional BGP-LS Link NLRI(as
described in Section 5.2 of [RFC9086]) must be generated to advertise
Peer Link information when generating the BGP-LS Link NLRI (as
described in Section 5.1 of [RFC9086]) corresponding to the PeerNode
SID.
replaced with:
Note that for directly connected EBGP neighbors, if a BGP neighbor is
established over an L2 Bundle, an additional BGP-LS Link NLRI (as
described in Section 5.2 of [RFC9086]) must be generated to advertise
Peer Link information when generating the BGP-LS Link NLRI (as
described in Section 5.1 of [RFC9086]) corresponding to the PeerNode
SID.
Current text:
Replace with:
draft (-00): draft-ietf-idr-sr-epe-over-l2bundle
status: Current
draft (-00): draft-ietf-idr-sr-epe-over-l2bundle
status: Current draft is simply the adopted draft.