[Idr] FW: draft-ietf-idr-segment-routing-te-policy-06.txt - Early Allocation Requests Approved by Alvaro

"Susan Hares" <shares@ndzh.com> Sun, 02 June 2019 18:26 UTC

From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Sun, 02 Jun 2019 14:25:59 -0400
Message-ID: <018c01d51970$a0891e70$e19b5b50$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_018D_01D5194F.197C3960"
Content-Language: en-us
Thread-Index: AdUZbaa/Ht79nR5+Q/GsYOvtGoHpSw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sIcQPy8xekl60EYozdfi_h8uWKQ>
Subject: [Idr] FW: draft-ietf-idr-segment-routing-te-policy-06.txt - Early Allocation Requests Approved by Alvaro
Precedence: list

Early allocation for the draft-ietf-idr-segment-routing-te-policy-06.txt has been approved by Alvaro on Friday.  This allocation is usually processed by IANA  quickly (1-2 weeks).   I will track the IANA processing, but If anyone see the allocation before I announce it please send a message to the list.  

 

Sue 

 

From: Alvaro Retana [mailto:aretana.ietf@gmail.com] 
Sent: Friday, May 31, 2019 4:58 PM
To: Susan Hares
Cc: John Scudder; Dongjie (Jimmy)
Subject: Re: draft-ietf-idr-segment-routing-te-policy-06.txt - Early Allocation Requests

 

Approved.

 

On May 30, 2019 at 12:37:57 AM, Susan Hares (shares@ndzh.com) wrote:

Alvaro: 

The IDR WG requests an early allocation for  values draft-ietf-idr-segment-routing-te-policy-06.txt 

The details are below.  Please let me know if you have any 

Susan Hares 

------------

Stability: The draft is stable and is ready for implementation.   

Planned implementations:  Cisco, Huawei, Arista (?) 

WG consideration:  Call done from  4/30 to 5/14/2019 

·         No objections or concerns were noted that were not resolved in the discussion,  

·         Support was shown from multiple vendors (Arista, Cisco, Huawei, google

Allocations Required: 

Section:    <https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-06#section-8.3> 8.3.  Existing Registry: BGP Tunnel Encapsulation Attribute sub-TLVs

 
What needs to be allocated: 
 
   This document defines new sub-TLVs in the registry "BGP Tunnel
   Encapsulation Attribute sub-TLVs" to be assigned by IANA:

 

The first 3 code points have already been assigned with the following status: 
TEMPORARY: registered 2017-10-12, extension registered 2018-08-27, expires 2019-10-12. 
 
We ask that these be considered for a second extension until 2020-10-12 due to the 
fact the implementations need to include the second set of parameters. 
          Codepoint       Description              Reference
          ------------------------------------------------------
          12              Preference sub-TLV       This document - 
          13              Binding SID sub-TLV      This document
          128             Segment List sub-TLV     This document
 
We ask that IANA assign these parameters in the registry:
 
          TBD1            ENLP sub-TLV             This document
          TBD2            Priority sub-TLV         This document
          TBD3            Policy Name sub-TLV      This document

 

The WG notes, if it is appropriate for IANA to do so the following values would be 

helpful for implementers: 

 

                              14                                   ENLP sub-TLV                    This document

                              15                                   Priority sub-TLV                 This document

                              129                                 Policy Name sub-TLV      This document

[Idr] FW: draft-ietf-idr-segment-routing-te-polic… Susan Hares