draft: draft-ietf-idr-sr-policy-seglist-id
Type: Proposed Standard
Spring: Segment list RFC9256
current revision: -08
status: WG LC pending, in Spring check at IETF-125.
adopted: 11/6/2024
current version: 08 (published 2/10/2026),
Early Allocation: yes, ready for query with -06 revision (11/2 to 11/17/2025)
implementations: H3C and ZTE (2 implementations)
bgp-ls draft: none
status: WG LC IPR Call done (1/5 to 1/12), Needs Spring check.
status: -04 is ready for early allocation. AD ask for specific request instead of bundled requests.
draft: https://www.ietf.org/archive/id/draft-ietf-idr-sr-policy-seglist-id-06.txt
email: https://mailarchive.ietf.org/arch/msg/idr/PzWso9VdqSJE_sE3F71rrPp85Qk/
status: -04 is ready for early allocation
email: https://mailarchive.ietf.org/arch/msg/idr/Me5erFR0TjMypo9uEnxjYQz_eEY/
status: Needs -04 revision to resolve technical issues from -02
email: https://mailarchive.ietf.org/arch/msg/idr/ZoOmSG_E48FiW-e5GsW4_bWd4hs/
Technical issues resolved: #1 resolved, #2 partially resolved
old text:/ The security requirements and mechanisms
described in[ draft-ietf-idr-sr-policy-safi] also apply to this document./
Problem: You have added critical information to
[draft-ietf-idr-sr-policy-safi] regarding
seglist-id to the SR Policy information. You need
to discuss how to protect the critical information in
seglist-id.
Please see that you are filling out all the Sub-TLV
template from https://wiki.ietf.org/group/idr/TEA-templates/SubTLV
Here's what I think you need to add:
draft: draft-ietf-idr-sr-policy-seglist-id-02
Status: WG draft
implementations: unknown
allocation status: preliminary (upcoming issue)
WG LC status: unknown
Comment: Thank you for a carefully written document.
old text:/
When signaling SR Policy by PCEP [I-D.ietf-pce-multipath], a segment
list is identified by "Path ID", which is a 4-octet identifier. In
this document, the segment list identifier is also represented using
a 4-octet ID./
new test:/
When signaling SR Policy by PCEP [I-D.ietf-pce-multipath] (see section 5.2),
a segment list is identified by "Path ID", which is a 4-octet identifier. In
this document, the segment list identifier is also represented using
a 4-octet ID./
Security section should refer to security section in
[draft-ietf-idr-sr-policy-safi]. It is important to reference:
a) operates in trusted environment (as draft-ietf-idr-sr-policy-safi)
b) Operators must a Segment ID for a segment is critical piece of
information about critical infrastructure. Care must be take
with distribution of information.