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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Sat, 04 April 2020 02:53 UTC

Return-Path: <cpignata@cisco.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 A8EE93A0810; Fri, 3 Apr 2020 19:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=BniDkcpk; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=GN2lMVJT
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 nHgInhJDAZym; Fri, 3 Apr 2020 19:53:18 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E58D3A080C; Fri, 3 Apr 2020 19:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25381; q=dns/txt; s=iport; t=1585968798; x=1587178398; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qdVLhW0CbHngOrFVLmVkozGdFm3sIAJT36f8G8B0URU=; b=BniDkcpk9mXGOexVJcKQuqudi/CUJGVnrACAVyaASbY8HnkKxKvPbTNo 9dzNVWrHrBlCX1BDKbqbp59X7uwzaNrA9gMs+3e2E2VUOwyz6mSgzJCVz 4Y9cug4um1FODxZuGzPXQzpnFCVUODNWdqag/2ftAWpuOIErYg6Ue9rwt A=;
X-IPAS-Result: A0CyAAAn9ode/5RdJa1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gVRQBWxYIAQLKgqEEYNFA4pmgl+TPYRhgUKBEANUCgEBAQwBARgBCgoCBAEBhEQCF4IvJDgTAgMBAQEDAgMBAQEBBQEBAQIBBQRthVYMhXABAQEBAwEBEBEdAQEpAwsBCwICAgEGAg4DBAEBKAMCAgIZDAsUCQgCBA4FGweDBAGBfk0DLgEOknqQZwKBOYhidYEygn8BAQWFThiCDAMGBYEzjDEagUE/gREnHIJNPoJnAQECAYEtARECAR8HERaCZTKCLIdniGE7hgOKMo9eCoI9h2+PNh2CTJk0kQSHUY9DgzcCBAIEBQIOAQEFgWkiZ3BwFTsqAYI+PhIYDVaNRziDO4UUhUF0gSmLZiyBBwGBDwEB
IronPort-PHdr: 9a23:E43gwRUeQUPpASvv5hr9H2fQGsrV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtankxBMVNUlZ59lmwMFNeH4D1YFiB6iTovyQfERj+Kwd5Y//tFN6O3eKw0e36u4XJZBlFjya8ZrU0KwiqqQLWtY8dho4wYq0w0RDO5HBPfqxawm5zbVSUg17w69yx85hq7yk12bo5+tRFULnmcqhwVrFeADk8e2Ay/9Hw9BQ=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.72,342,1580774400"; d="scan'208,217";a="446821390"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2020 02:53:04 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 0342r187017659 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 4 Apr 2020 02:53:02 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 3 Apr 2020 21:53:01 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 3 Apr 2020 21:53:01 -0500
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 3 Apr 2020 21:53:01 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hylB8THDrZYJ0gyx8PpLBbrG4zE2xqkiLOgHO0msq2RXubVpa7/ZAi5fOP/w96pBIMDjmDjkh7ykVAjlp+UlPl4pnF4m+arpWG49UM5Tcscj4bxonQUi6/xZoch5QwnKMNRk8uXevMgGMEZHZsIRmnXe1Ci+Il76w4bpRa8g0kc1EKC5E049XkO4H3z8QalRNc7icvYJijCsYW/AzPykKp+sjUUweshu3W8Lnl6n5hgc1ZYGecVg2C7GOrgbMb3agF/LtXadmiw60lX4T+7cmeUeY45HxC2msmmDKMcTj4alPCcy2pWjAyUCQ3hUybsZd83SUhJ3Su21ky6pnvkyig==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qdVLhW0CbHngOrFVLmVkozGdFm3sIAJT36f8G8B0URU=; b=iBVAo43ikgBqhzHD2yMX0lEWZTp9rFrP6IqLK4NiKkJ3JTxa8NUHd83qXgoDqBIDpSTgUwCtZ6OeZFEKjXVebDEybaoKMUoEDCtjCF2qDr8ucuEt0lt0b7ONDrNPjoCGAlxIXuoMmvd6+DGz76aaznSEIUM5Weg4dj3i718UgOwAjc1EDO2GwJ9uFoHyxfV1DoAzs07bHK9bpved4tzJGIGEN/xK+fOHZd9ZiWFO8phsNujRWZCVNo1cSNJhCKo0N1DYLoPsjMWfhs8LoUp2//1QsMqgI4Qj9sHL6y9S2h7L1a5Hw9saY/GRhOkkfmI6yXVpUuBFGERDpshyOw9OIg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qdVLhW0CbHngOrFVLmVkozGdFm3sIAJT36f8G8B0URU=; b=GN2lMVJTpQ/0ZGCA19dWGg1tbK0pxpU+iHoMxH3+awkpdBBw0302h1hAE+RM+1ctCbwTmJklZj18O1u8AvyEbVWQa/xk8GDjQqep9cSJEtlVnR0yyG6BlDslIQcoSoQw6Y0fqWE+2xrFNW2rq1lGYuzfll749E2AtfN/7hL4iZQ=
Received: from BN8PR11MB3635.namprd11.prod.outlook.com (2603:10b6:408:86::20) by BN8PR11MB3652.namprd11.prod.outlook.com (2603:10b6:408:87::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.20; Sat, 4 Apr 2020 02:52:59 +0000
Received: from BN8PR11MB3635.namprd11.prod.outlook.com ([fe80::2c08:cdcf:fc41:fe74]) by BN8PR11MB3635.namprd11.prod.outlook.com ([fe80::2c08:cdcf:fc41:fe74%7]) with mapi id 15.20.2856.019; Sat, 4 Apr 2020 02:52:59 +0000
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Deborah Brungard <db3546@att.com>
CC: Loa Andersson <loa@pi.nu>, mpls <mpls@ietf.org>, IANA <iana@iana.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls-ads@ietf.org" <mpls-ads@ietf.org>
Thread-Topic: [mpls] early allocations of code points for draft-ietf-mpls-lsp-ping-ospfv3-codepoint-00.txt
Thread-Index: AQHWAtpPbZuTDLBCgUeDTyCkU4t3NKhnwpgAgACP/gA=
Date: Sat, 04 Apr 2020 02:52:59 +0000
Message-ID: <5483F6E3-F88B-48E0-988A-CEE7E7939068@cisco.com>
References: <952d898e-90b1-572a-1c78-f38757597a92@pi.nu> <F64C10EAA68C8044B33656FA214632C8AF90E965@MISOUT7MSGUSRDE.ITServices.sbc.com> <F64C10EAA68C8044B33656FA214632C8AF917E23@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8AF917E23@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.80.23.2.2)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cpignata@cisco.com;
x-originating-ip: [108.203.7.63]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a9d31882-6e0c-4b2e-6699-08d7d843490c
x-ms-traffictypediagnostic: BN8PR11MB3652:
x-microsoft-antispam-prvs: <BN8PR11MB36523A64F3B480C1471BB088C7C40@BN8PR11MB3652.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6108;
x-forefront-prvs: 03630A6A4A
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN8PR11MB3635.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(376002)(346002)(39860400002)(366004)(136003)(396003)(6916009)(81166006)(81156014)(8676002)(966005)(8936002)(6512007)(86362001)(478600001)(71200400001)(36756003)(64756008)(66556008)(66476007)(76116006)(6486002)(66946007)(5660300002)(2906002)(186003)(33656002)(66446008)(4326008)(54906003)(6506007)(2616005)(53546011)(26005)(316002); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: RAujPrG4q46pP8bUvMt8WpSwRhAg6pSqEESnTsofVeLda8TNzHCpRg6qKKziwx5AOl5X9H7dFNN6+jDYRGvbuLKLaoctJNwyGsX1AQlQLnim70B+g11RAJ6L7hXa6W3yxl95vBVEq34FRosmF/7EXdGXGQRy0yteOIN+kK8oqoaE87+OfUU4Pgag1Oat9FSjhhDyjBqf+ZZeCTvHITpztIWFT9s57I++7fn9gbDtHEsL29tZgLyOQ7jdXP1Og//F1cpp+fK2HOiSLxNk6R9dfMXWiVZaktXy+bIxdkiEEox1/rL4AdQjPi27gD9Vlb6QDFVrQ+d+nF85bPOL4psHopsmOF1OY4EjaTzQM4xispMMKLwmkmUECENnUBbbagRi37C9pG5lIJ+5xUvCTuGEwwQQLPupIHuTh1U3NL+OtKWJD4MarxML5w2QufBGn9Jxr9mrGkUUrOtecBP9/7g2PiFwYY+UxK6Slla0az3dAWtJKLFscLNUXf29eGoVP7tN/BIBNIQpcZUqglOVX5v/Vg==
x-ms-exchange-antispam-messagedata: rIM/CfaJEB2rY7icaiZq/Jc59JKoI4TKkypBeIvCNd3/Nue0KwTJNUN76WGmj33tksdiosS5dl4AxL91EF9+V8eySyjw9AD1jlBsA5uhjc3KbrnlKHLbzsR13hIVwfjM/TUHwDlUIKRspQ1Gz1+biQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5483F6E3F88B48E0988ACEE7E7939068ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a9d31882-6e0c-4b2e-6699-08d7d843490c
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2020 02:52:59.4443 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pKp37IyA2kg3U88QftFIEq1J5XTaI3QNQacS/uE47OUbwsB5/HUnzI7iF4M051OoJNSc3cE1GTCBDkZVtjuwLg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3652
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/MpBYkRxSvKh8O6Z3ATtVZA9Uh8Y>
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: Sat, 04 Apr 2020 02:53:22 -0000

Deborah,

Thanks for this follow-up.

Strictly, draft-ietf-mpls-lsp-ping-ospfv3-codepoint does not deprecate and reassign a code point — it merely renames it to match usage.

Similar renaming has been done as e.g, https://tools.ietf.org/html/rfc6829#section-2.

I agree that a more detailed operational considerations is needed on this explaining it.

I really do not think this applies to RFC8690 since that only clarifies the Length and has no mention of the Protocol field. But if you think so, it can be added.

Thanks,

Carlos.


2020/04/03 午後2:17、BRUNGARD, DEBORAH A <db3546@att.com<mailto:db3546@att.com>>のメール:

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<mailto:db3546@att.com>>
Sent: Wednesday, March 25, 2020 3:18 PM
To: Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>>
Cc: mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>; mpls-ads@ietf.org<mailto:mpls-ads@ietf.org>; IANA <iana@iana.org<mailto:iana@iana.org>>; mpls@ietf.org<mailto: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<mailto:loa@pi.nu>>
Sent: Tuesday, March 24, 2020 6:37 AM
To: BRUNGARD, DEBORAH A <db3546@att.com<mailto:db3546@att.com>>
Cc: mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>; mpls-ads@ietf.org<mailto:mpls-ads@ietf.org>; IANA <iana@iana.org<mailto:iana@iana.org>>; mpls@ietf.org<mailto: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<mailto:loa@pi.nu>
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls