[Idr] draft-ietf-idr-sr-policy-metric-00.txt - Early Allocation Request - Need a revision of hte draft

[Susan Hares <[e-mail]>]

Greetings:

Your request for early allocation cannot be processed at this time.
[draft-ietf-idr-sr-policy-safi-04]
(https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-safi/)

has not been approved by the IESG, so values for registry for
SR Policy Segment List Sub-TLVs cannot be assigned.

When the registry is created, I will recommend the following values be assigned.
https://wiki.ietf.org/e/en/group/idr/Early-Allocation-Status


Value    Description      Reference
------   ---------------  ------------------
TBA (20) Metric sub-TLV   This document


As part of the Early allocation processing, I reviewed your document.  Please make the associated editorial changes.

I look forward to receiving draft-ietf-idr-sr-policy-metric-01.txt with the changes below.

Cheerily,  Susan Hares
-----------------------------------


Editorial changes:

Existing Abstract:
   SR Policy candidate paths can be represented in BGP UPDATE messages.
   BGP can then be used to propagate the SR Policy candidate paths to
   the headend nodes in the network.  After SR Policy is installed on
   the ingress node, the packets can be steered into SR Policy through
   route selection.  Therefore, route selection may be performed on the
   ingress node of the SR Policy.  If there are multiple routes to the
   same destination, the route selection node can select routes based on
   the local policy.  The local policy may use the IGP metric of the
   selected path, which is the IGP Metric of the SR Policy.  Thus the
   BGP UPDATE message needs to carry the metric of each segment list of
   the SR Policy Candidate Path, which can be used in path selection of
   routing.

Please move most of this abstract into the introduction.

Suggested Abstract: /
   This specifies how BGP Can carry the metric of each segment list of
   the SR Policy Candidate Path in the BGP Tunnel Encapsulation attribute.
   This metric can be used by BGP policy and the SRPM to select a
   Best path for SR-Routing. /

2. Change references in sections 1, 2, and 9 (References)

Please change all references of [draft-ietf-idr-segment-routing-te-policy] to
[draft-ietf-idr-sr-policy-safi]

3. change to section 7.1

Old text:/

   This document defines a new Sub-TLV in requests registries "SR Policy

   List Sub-TLVs [I-D.ietf-idr-segment-routing-te-policy]:/



New text:/

   This document defines a new Sub-TLV in the "SR Policy
   List Sub-TLVs" register under the BGP Tunnel Encapsulation grouping
  (see [I-D.ietf-idr-sr-policy-safi])

PS  - Remember if you are defining a new registry in a draft, you can simply use the values.

Cheerily, Sue