[mpls] Early allocation of code points for draft-ietf-mpls-sr-epe-oam
Loa Andersson <loa@pi.nu> Thu, 06 May 2021 07:56 UTC
Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5145C3A16B9; Thu, 6 May 2021 00:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 h38s5gutAxSz; Thu, 6 May 2021 00:56:16 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 616E73A16BA; Thu, 6 May 2021 00:56:16 -0700 (PDT)
Received: from [192.168.0.7] (c83-250-136-37.bredband.comhem.se [83.250.136.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 0E2CE2FD2F2; Thu, 6 May 2021 09:56:14 +0200 (CEST)
From: Loa Andersson <loa@pi.nu>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, rtg-ads@ietf.org, Shraddha Hegde <shraddha@juniper.net>
Cc: "draft-ietf-mpls-sr-epe-oam@ietf.org" <draft-ietf-mpls-sr-epe-oam@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Message-ID: <a97006c4-964f-4e6b-aa06-d828a878d2bf@pi.nu>
Date: Thu, 06 May 2021 09:56:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/3KyAZH4zhXekfj6gqJ_7rYst1lk>
Subject: [mpls] Early allocation of code points for draft-ietf-mpls-sr-epe-oam
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 07:56:21 -0000
Martin, This is the process for early allocations of IANA codepoints as described in RFC 7120. The comments preceded with (-) are mine describing how the draft-ietf-mpls-sr-epe-oam meet the requirements for early allocation, 1. The authors (editors) of the document submit a request for early allocation to the Working Group chairs, specifying which code points require early allocation and to which document they should be assigned. - The document is stable and implementations are under way. - working group chairs are prepared to go ahead and request the earlly allocations. 2. The WG chairs determine whether the conditions for early allocations described in Section 2 are met, particularly conditions (c) and (d). - the working group chairs has reviewed the draft in the light of section 2 of RFC 7120. - the wg chairs are convinced that draft-ietf-mpls-sr-epe-oam meet all the criteria listed in section 2 of RFC 7120. 3. The WG chairs gauge whether there is consensus within the WG that early allocation is appropriate for the given document. - the wg chairs are convinced that there are consensus in the wg to go ahead and do the early allocation. 4. If steps 2) and 3) are satisfied, the WG chairs request approval from the Area Director(s). The Area Director(s) may apply judgement to the request, especially if there is a risk of registry depletion. - This mail is the request according to step four in the process for early allocation according to the IANA section of draft-ietf-mpls-sr-epe-oam. - the mail is sent to Martin Vigoureux as responsible AD, with a copy to the the other rtg-ads. - we request support for early allocation of the codes as requested in IANA considerations sectio in draft-ietf-mpls-sr-epe-oam, i.e.: Three new Target FEC stack sub-TLVs from the "Sub-TLVs for TLV types 1,16 and 21" subregistry in the "TLVs" registry of the "Multi-Protocol Label switching (MPLS) Label Switched Paths (LSPs) Ping parameters" namespace. -- PeerAdj SID Sub-TLV : TBD1 -- PeerNode SID Sub-TLV: TBD2 -- PeerSet SID Sub-TLV : TBD3 - we will wait for the response from the responsible AD before going ahead with step 5 in this process. 5. If the Area Directors approve step 4), the WG chairs request IANA to make an early allocation. 6. IANA makes an allocation from the appropriate registry, marking it as "Temporary", valid for a period of one year from the date of allocation. The date of first allocation and the date of expiry are also recorded in the registry and made visible to the public. /Loa for the MPLS wg co-chairs. -- Loa Andersson email: loa@pi.nu Senior MPLS Expert loa.pi.nu@gmail.com Bronze Dragon Consulting phone: +46 739 81 21 64
- [mpls] Early allocation of code points for draft-… Loa Andersson
- Re: [mpls] Early allocation of code points for dr… Martin Vigoureux
- [mpls] Fwd: Early allocation of code points for d… Loa Andersson
- [mpls] [IANA #1196929] Fwd: Early allocation of c… Sabrina Tanamal via RT
- Re: [mpls] [IANA #1196929] Fwd: Early allocation … Shraddha Hegde