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

"BRUNGARD, DEBORAH A" <db3546@att.com> Fri, 03 April 2020 18:17 UTC

Return-Path: <db3546@att.com>
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 10E733A0A14; Fri, 3 Apr 2020 11:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 0BU1yWg5UJFh; Fri, 3 Apr 2020 11:17:46 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99F4E3A09FC; Fri, 3 Apr 2020 11:17:46 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 033IE6YR002443; Fri, 3 Apr 2020 14:17:44 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049297.ppops.net-00191d01. with ESMTP id 306a81g26g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 03 Apr 2020 14:17:44 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 033IHf9c012390; Fri, 3 Apr 2020 14:17:42 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [135.66.87.38]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 033IHbin012285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Apr 2020 14:17:38 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [127.0.0.1]) by zlp27130.vci.att.com (Service) with ESMTP id D6C69400B57E; Fri, 3 Apr 2020 18:17:37 +0000 (GMT)
Received: from MISOUT7MSGHUBAA.ITServices.sbc.com (unknown [130.9.129.145]) by zlp27130.vci.att.com (Service) with ESMTPS id BA3AE400B574; Fri, 3 Apr 2020 18:17:37 +0000 (GMT)
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.76]) by MISOUT7MSGHUBAA.ITServices.sbc.com ([130.9.129.145]) with mapi id 14.03.0487.000; Fri, 3 Apr 2020 14:17:37 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: Loa Andersson <loa@pi.nu>
CC: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls-ads@ietf.org" <mpls-ads@ietf.org>, IANA <iana@iana.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt
Thread-Index: AQHWAcg1qTV42xSKYUun4GRqqw1U/qhZsFtQgA3WqxA=
Date: Fri, 3 Apr 2020 18:17:36 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C8AF917E23@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <952d898e-90b1-572a-1c78-f38757597a92@pi.nu> <F64C10EAA68C8044B33656FA214632C8AF90E965@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8AF90E965@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.184.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-03_15:2020-04-03, 2020-04-03 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 malwarescore=0 lowpriorityscore=0 clxscore=1015 adultscore=0 mlxlogscore=999 spamscore=0 impostorscore=0 mlxscore=0 phishscore=0 priorityscore=1501 bulkscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004030150
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/JohV_Z201JKVe5euGLjjFuIWLOI>
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: Fri, 03 Apr 2020 18:17:48 -0000

Hi MPLS WG, MPLS Chairs,

Here's an update on these early allocations. IANA has finished the early allocation for OSPFv3 codepoints. They responded they could not rename the OSPF codepoint as OSPFv2 until the draft was approved. The chairs asked if a note could be added to the OSPF codepoint saying it will be renamed. IANA asked for my approval to add such a note.

When asked for my initial approval on this IANA early allocation, I only looked at the draft itself and not at RFC8287 which it "updates". It was my error to assume RFC8287's OSPF codepoint was for OSPFv2 and this draft updated to add a codepoint for OSPFv3. Reviewing RFC8287, the OSPF codepoint is used by IPv4 and IPv6, so it currently represents both OSPFv2 and v3. Codepoints are usually deprecated (obsoleted), but they are not reassigned when in use. Especially if there are no registry limitations.

Before approving adding this note, I requested the authors to add information on interoperability aspects and rationale on renaming as the best solution. As this is a working group draft, I encourage the working group to engage on the solution.

Note, the document not only impacts RFC8287 but also RFC8690.

Thanks,
Deborah


-----Original Message-----
From: BRUNGARD, DEBORAH A <db3546@att.com> 
Sent: Wednesday, March 25, 2020 3:18 PM
To: Loa Andersson <loa@pi.nu>
Cc: mpls-chairs@ietf.org; mpls-ads@ietf.org; IANA <iana@iana.org>rg>; mpls@ietf.org
Subject: RE: early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt

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