Re: [mpls] early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt

Loa Andersson <loa@pi.nu> Thu, 26 March 2020 03:33 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 7C65E3A0810; Wed, 25 Mar 2020 20:33:35 -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 4FfGsnnXTvgk; Wed, 25 Mar 2020 20:33:33 -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 D5D153A080B; Wed, 25 Mar 2020 20:33:32 -0700 (PDT)
Received: from [192.168.1.6] (unknown [119.94.165.58]) (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 C9F42365026; Thu, 26 Mar 2020 04:33:28 +0100 (CET)
To: IANA <iana@iana.org>
Cc: "BRUNGARD, DEBORAH A" <db3546@att.com>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls-ads@ietf.org" <mpls-ads@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
References: <952d898e-90b1-572a-1c78-f38757597a92@pi.nu> <F64C10EAA68C8044B33656FA214632C8AF90E965@MISOUT7MSGUSRDE.ITServices.sbc.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <dceb5318-b6ce-b2d4-8bf0-e7201590675e@pi.nu>
Date: Thu, 26 Mar 2020 11:33:25 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8AF90E965@MISOUT7MSGUSRDE.ITServices.sbc.com>
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/pJs0MFfmVFyG2jIKCGrF7RV_WpU>
Subject: Re: [mpls] early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt
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, 26 Mar 2020 03:33:36 -0000

IANA,

The requested early allocations have been approved by Deborah according 
to step 5 in the process of RFC 7120.

Can you please go head and makes the early allocations.

/Loa
for the mpls co-chairs

On 26/03/2020 03:18, BRUNGARD, DEBORAH A wrote:
> Hi Loa, IANA,
> 
> I approve these early allocations-
> Thanks-
> Deborah
> 
> 
> -----Original Message-----
> From: Loa Andersson <loa@pi.nu>
> Sent: Tuesday, March 24, 2020 6:37 AM
> To: BRUNGARD, DEBORAH A <db3546@att.com>
> Cc: mpls-chairs@ietf.org; mpls-ads@ietf.org; IANA <iana@iana.org>rg>; mpls@ietf.org
> Subject: early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt
> 
> Deborah,
> 
> This is the process for early allocations of IANA codepoints as
> described in RFC 7120. The comments preceded with (-) are mine
> describing how the current draft 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.
> 
>          - This has been done, though the authors actually requested the
>            code points to be made to an individual draft (draft-nainar-
>            mpls-lsp-ping-ospfv3-codepoint)
> 
>          - The wg chair responded that early code point allocations can
>            only be made to working group documents.
> 
>          - The working group document is no at hand and the working group
>            chairs are prepared to go ahead and request the 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-lsp-ping-
>           ospfv3-codepoint 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 the har 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 for in the process
>            for early allocation.
> 
>          - the mail is sent to Deborah Brungard as responsible AD, with a
>            copy to the the other rtg-ads.
> 
>          - we request support for early allocation of the codes as
>            requested in Sectioon 7 (IANA considerations) in draft-ietf-
>            mpls-lsp-ping-ospfv3-codepoint, i.e.:
>            One new code point for OSPFv3 in the "Protocol in the Segment
>            ID sub-TLV"
>            Renaming of the existing OSPF code point in the same registry
>            to "OSPFv3".
> 
>            and
> 
>            One new code point for OSPFv3 in the "Protocol in Label Stack
>            Sub-TLV of Downstream Detailed Mapping TLV"
>            Renaming of the existing OSPF code point in the same registry
>            to "OSPFv3".
> 
>          - 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.
> 
> PS
> This mail is sent to IANA, even though IANA do not need to take any
> action until the formal request.
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64