draft: draft-ietf-idr-sr-policy-metric
Type: Proposed Standard
status: WG Draft
adopted: 9/1/2024 (8/1 to 8/30 call)
current version: -04, Needs -05
Early Allocation: 20 wiki Early Allocation, needs early allocation. Call awaits -04 version with Issues fixed (Technical and Editorial)
implementations: TBD
bgp-ls draft: none
Next step: release -05 with issues fixed, and then do an Early Allocation call (2 weeks)
draft (-04): draft-ietf-idr-sr-policy-metric-03 - No changes were made to draft. Issues raise in -03 need to be addressed.
draft (-03): draft-ietf-idr-sr-policy-metric-03
Shepherd report on IDR Email list: TBD
Ketan is concerned that you have the right registry at:
https://www.iana.org/assignments/bgp-tunnel-encapsulation/bgp-tunnel-encapsulation.xhtml#sr-policy-segment-list-sub-tlvs
Please discuss with Ketan about the correct registry. The registry you have specified is at the same level as all segment types. Should it be "SR Policy Segment List Sub-TLVs"
Also, when you update this portion of the text update the IANA comment to the format registry in registry group.
I-D.ietf-idr-sr-policy-safi is now RFC9830. Please update your draft.
The metric for a pathway using SR technology is information critical to a network. Therefore, you must include a warning in the security considerations in section 8 to have the operator carefully restrict access to the metric information.
Please fix the table format for code point 5.
Please indicate what Spring WG document or individual draft mentions "metric" for the Segment list. Add this to a new section denoted as "Cross WG information". We will take this out at publication time, but it will speed up the process of getting your document published.
If there is a SRv6OPS call for a metric on the segment list to aid implementation, please put this information in the "Cross WG information" section.
If there is a PCE feature that specifies metric for the segment list,
please list the feature and the PCE WG document it is in.
If the SR Candidate path information gathered by BGP-LS, gather this metric from the segment list on the candidate path, please include that information in the Cross-WG section
draft (-02): refresh only - Update only refresh the draft. No changes. Needs revision
Email link: https://mailarchive.ietf.org/arch/msg/idr/HiSCW-HKUBQhMSpxB4qqzENrVHA/
draft (-01): -01 handles Issue 1 and Editorial Nit-1.
Technical issues remaining: Issue 2 has needs a bit more in security section.
Based on security AD/SEC-DIR is important to reference:
draft (-00): draft-ietf-idr-sr-policy-metric
Old text:
/ [I-D.ietf-idr-sr-policy-safi]defines SR Policy and Tunnel
Encapsulation Attributes./
**
New text:**
/[I-D.ietf-idr-sr-policy-safi]defines SR Policy and Tunnel
Encapsulation Attributes for the SR Policy tunnel type.
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 metric for a segment is critical piece of
information about critical infrastructure. Care must be take
with distribution of information.
Why are you references draft-ietf-idr-bgp-ls-sr-policy?
Is there something I missed?