[Idr] draft-ietf-idr-sr-policy-seglist-id-00 - Early allocation request

[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 (19) Segment List ID 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-seglist-id-01 with the changes below.

Cheerily,  Susan Hares


Changes to document:

#1 - Introduction, paragraph 1
Problem: out of date reference
Current/

  In order to distribute SR policies to the headend, [I-D.ietf-idr-

   segment-routing-te-policy] specifies a mechanism by using BGP./



update from [I-D.ietf-idr-segment-routing-te-policy]
to [draft-ietf-idr-sr-policy-safi]


#2 - Introduction, paragraph 2


Current text:/

   For example, a network controller distributes SR policies to the

   headend nodes, and the headend nodes collect traffic forwarding

   statistics per segment list./



revised text:/

   Consider the case of a network controller distributing

   SR policies to the headend nodes where the headend nodes need to

   collect traffic forwarding statistics per segment list. /



#3 - Introduction, paragraph 3
Current text:
   For another example, a network controller distributes SR policies
   using BGP, and then it uses NETCONF to set some configurations of
   the segment lists, which are not suitable to be carried in BGP. So,
   the controller needs to specify which segment list these
   configurations belong to when it issues them. In this case, a simple
   identifier of segment list can also be helpful./

New text:
   Consider a second example where a network controller distributes SR policies
   using BGP, and then it uses NETCONF to set some configurations of
   the segment lists which are not suitable to be carried in BGP.
   The controller needs to specify which segment list these
   configurations belong to when it issues them. In this case, a simple
   identifier of segment list can also be helpful.

#4 - Section 3 - Security consideration

   The security requirements and mechanisms described in [I-D.ietf-idr-
   segment-routing-te-policy] also apply to this document.

update from [I-D.ietf-idr-segment-routing-te-policy]
to [draft-ietf-idr-sr-policy-safi]



#4 - Normative References


   [I-D.ietf-idr-segment-routing-te-policy] Previdi, S., Filsfils, C.,
             Talaulikar, K., Mattes, P., and D. Jain, "Advertising
             Segment Routing Policies in BGP", Work in Progress,
             Internet- Draft, draft-ietf-idr-segment-routing-te-policy-
             25, 26 September 2023, <http://www.ietf.org/internet-
             drafts/draft- ietf-idr-segment-routing-te-policy-25.txt>.


update from [I-D.ietf-idr-segment-routing-te-policy]
to [draft-ietf-idr-sr-policy-safi]

-