[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

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA43120052 for <idr@ietfa.amsl.com>; Sun, 2 Jun 2019 11:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvLjbLdDATWh for <idr@ietfa.amsl.com>; Sun, 2 Jun 2019 11:26:14 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02E1612003F for <idr@ietf.org>; Sun, 2 Jun 2019 11:26:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.224.176;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Sun, 2 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"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AdUZbaa/Ht79nR5+Q/GsYOvtGoHpSw==
X-Antivirus: AVG (VPS 190602-2, 06/02/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
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
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 18:26:16 -0000

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