Re: [Lsr] IANA Early Allocation Request for "Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS" - draft-ietf-isis-mpls-elc-07

"Acee Lindem (acee)" <acee@cisco.com> Fri, 23 August 2019 19:01 UTC

Return-Path: <acee@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79224120122; Fri, 23 Aug 2019 12:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=mM396jmH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=tJXsawm5
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 zNw3wnQboc0W; Fri, 23 Aug 2019 12:01:50 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C305D1200F5; Fri, 23 Aug 2019 12:01:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13265; q=dns/txt; s=iport; t=1566586909; x=1567796509; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6MAIWLMaFGO+Um2dsdI9w4Z/xRWIo1TVt49YwB0F04M=; b=mM396jmHRvoocBJUupvna2QW8wx0HvOa88KR3Maxt6KEnHFxxIYqr3su t/DdCRHLo93RJgrj/J32ZUssHMaM0mGZEpn3xhkBPIccRh0LQRL4DKEbS yNqaCt5s+zifFpjw+7PuLjTbJvPJM+DSDcgzrkSgdh4B+NUUIEAALpozQ Q=;
IronPort-PHdr: 9a23:3rsVYBGmcOp2QxVpmlca3Z1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4w0Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0ETBoZkYMTlg0kDtSCDBjyJ/PnRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ARAADmN2Bd/4YNJK1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBVQIBAQEBAQsBgRUvUANtViAECyqEIINHA4ptgjcliV+JLYRbgS6BJANUCQEBAQwBAS0CAQGEPwIXglAjNgcOAgoBAQQBAQECAQYEbYUtDIVKAQEBAQMSER0BASkOAQ8CAQgOAwMBAiQEAwICAh8RFAkIAgQBDQUigwABgR1NAx0BAqFJAoE4iGFzgTKCewEBBYUdDQuCFgmBNAGLbxiBf4EQAScME4IeLj5rGQGBFYJKBhCCVTKCJo8chRGJCI1JLUAJAoIdkEmDehuYTkSNI4lojjoCBAIEBQIOAQEFgVcGK4FYcBVlAYJBgkIYIIM6ilNygSmLMiqCKAEB
X-IronPort-AV: E=Sophos;i="5.64,422,1559520000"; d="scan'208,217";a="617828570"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Aug 2019 19:01:26 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x7NJ1QaV003916 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 23 Aug 2019 19:01:27 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 23 Aug 2019 14:01:26 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 23 Aug 2019 14:01:25 -0500
Received: from NAM02-BL2-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.1473.3 via Frontend Transport; Fri, 23 Aug 2019 14:01:25 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PJbQC7QB3dzCl6Y2R1s3WiEJJAnUUggFzmTOO/ehXkZr7ZN9xJHKkSWn7vBUGXPkrBGOEQ5m0v4x2PrHwQJ8ubgnCZb8DpGCYmjGUm5hky7rCon5B0tc0/+cYi0G2vOtJhxheuDks72xAt5bj1Zro6LM9ZcDaCKHZ3DlzZNWwSGNrMW+rjjzV8vgKqpYMANzIkPv4nVqk7easgTd7MOaXXx+13eU7wlkXgBvauE+qyEDCvikZhqRZOKzlt/pkPwxbIzi5JpolfOPCzOH4A7hYtzpNd+EvHuPJ/SwsxZpq5jtJXPaxDFMlzWOCdP5nAkDHQT1wMC3DnFMEaNKe/mPGw==
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=6MAIWLMaFGO+Um2dsdI9w4Z/xRWIo1TVt49YwB0F04M=; b=Vtsj7zTuphKYr3d46Z00MWCsNUkZQPa4m3P71Ar/iROWEmZWvN0+S/LPJm+wWkaqWjmX9xqNG1TqeyzTXSzLLPKnFdiTs1bHbhe7OQvkOH40exVkmjLTZeJcseVAvQqSfyamXBvX+y1KvmFHaBVktsQF1nAqEcV9Rk6jBfXXXbjf0WrtSPkCHWuj5a1pFOYpvBibEhb4AysS9Zua8kBZ+fEO5H4ExUwC7Dfrt8hGz04p7qw1b6kqYn0WjS92LbAqJ6/knjq4N75Y1rYy1+GawCNCTtRAj2PB50X4eLO2fWXb3UZyD+hme1Ep73VGjAeiUCOsKe/QJskAlVCXe1p1Zg==
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=6MAIWLMaFGO+Um2dsdI9w4Z/xRWIo1TVt49YwB0F04M=; b=tJXsawm53+4QLr9Bc6dobcnq4HrtobQgE5nuF8GhvPi7bWsUc+rwruOCO74o0O4kWCDThRv5slXwdtnRpH/RRUp2UEf+ywivfpQC3P8sIlqh8XlBPCZ2IuiMmz6QsF9F3xmRGGW57vnZa55bHcrAyKfiutUayNlBSY4ejDuXT6Q=
Received: from MN2PR11MB4221.namprd11.prod.outlook.com (52.135.38.14) by MN2PR11MB3614.namprd11.prod.outlook.com (20.178.250.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.16; Fri, 23 Aug 2019 19:01:24 +0000
Received: from MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::859c:f271:3be2:74e0]) by MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::859c:f271:3be2:74e0%3]) with mapi id 15.20.2178.020; Fri, 23 Aug 2019 19:01:24 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, IANA <iana@iana.org>
CC: "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-isis-mpls-elc@ietf.org" <draft-ietf-isis-mpls-elc@ietf.org>
Thread-Topic: [Lsr] IANA Early Allocation Request for "Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS" - draft-ietf-isis-mpls-elc-07
Thread-Index: AQHVWdFhQcpxJ3esAkWU0H1YBuYJyqcJCrYAgAAKqgD//749AA==
Date: Fri, 23 Aug 2019 19:01:24 +0000
Message-ID: <41AB70F9-AF71-4615-8CE7-287531177A8E@cisco.com>
References: <216ECAE7-83B4-45EE-92B0-FADA3B467489@cisco.com> <CAMMESsxc9ZAJhotQjtJwWtgdDzB6vwLQibVq1hxw-8zr_9uvzg@mail.gmail.com> <BYAPR11MB3638C40F74A4ED13015F2B6AC1A40@BYAPR11MB3638.namprd11.prod.outlook.com> <CAMMESsxCr7+UvfhhZrp002=b+00k66q=3-8OVD9zsapMdTzKrA@mail.gmail.com>
In-Reply-To: <CAMMESsxCr7+UvfhhZrp002=b+00k66q=3-8OVD9zsapMdTzKrA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1008::143]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b66c9b32-7872-47e1-d910-08d727fc4b3c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3614;
x-ms-traffictypediagnostic: MN2PR11MB3614:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR11MB36147229C332F28E9FF9EEEFC2A40@MN2PR11MB3614.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0138CD935C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(346002)(39860400002)(376002)(136003)(199004)(189003)(86362001)(81156014)(64756008)(4326008)(66446008)(66556008)(66946007)(53546011)(6436002)(256004)(110136005)(229853002)(5660300002)(6116002)(76176011)(25786009)(8936002)(6512007)(81166006)(6306002)(236005)(54896002)(54906003)(316002)(53936002)(66476007)(6486002)(476003)(2616005)(14454004)(7736002)(8676002)(76116006)(36756003)(186003)(2906002)(102836004)(11346002)(446003)(99286004)(33656002)(6506007)(478600001)(71200400001)(71190400001)(46003)(14444005)(486006)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3614; H:MN2PR11MB4221.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: WVJFFnL3c/9mI9D7RQyqU+VEXBsjDdz9I6lQWh317YxPC002WXE0og70XhjxwpofLMxttvDwjz3X/Tq8UlgMQG91KUcpNXJk5/hWwv5zQaiTjRIbzqVLh3tn8EQFXd8Fa0SI5Kd9A1Mbf+p6bYmwsEx/1ez6/uMlx12hwYo2u6gVf6/WjmYbTzN+E8ohxPV9CykLjtQ3k+ZSfwv90/SJMmfdaFFjV5sa7besxDQZ5ntZy7nhDNfj+DUDlqPuZMfu8LGOO3Rz+LqT6ZEVHc2KXLtZH2hoFQqMJjOA8RB24G+hIh1OIg22TO+wicAN3+zjJuie74rpmV1JF89VY2KGuhWTbiZjn6kARz687SF4p9mwJkO1hx2e9NhwcYmoih7O+RXME9JTg5XFDmIq1hcI42tec90f1tD8s1GYoVWWuWw=
Content-Type: multipart/alternative; boundary="_000_41AB70F9AF7146158CE7287531177A8Eciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b66c9b32-7872-47e1-d910-08d727fc4b3c
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2019 19:01:24.1596 (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: W6DO0S5ti1M5aW/btuabwKAx90giQ/VEpcjMkJPZUQxlE9wpCfVrCoKnuEq74srY
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3614
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/YQiYIjdmUv_usLauwWoiuiprLbU>
Subject: Re: [Lsr] IANA Early Allocation Request for "Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS" - draft-ietf-isis-mpls-elc-07
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2019 19:01:52 -0000

To summarize, “early” allocation has been done by the IS-IS Designated Experts. However, these allocations have been permanent as opposed to temporary. If there were ever a problem with an early allocation,  the allocation would need to be deprecated rather than simply expire.
Thanks,
Acee

From: Alvaro Retana <aretana.ietf@gmail.com>
Date: Friday, August 23, 2019 at 2:56 PM
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Acee Lindem <acee@cisco.com>, IANA <iana@iana.org>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-isis-mpls-elc@ietf.org" <draft-ietf-isis-mpls-elc@ietf.org>
Subject: RE: [Lsr] IANA Early Allocation Request for "Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS" - draft-ietf-isis-mpls-elc-07

On August 23, 2019 at 2:18:37 PM, Les Ginsberg (ginsberg) (ginsberg@cisco.com<mailto:ginsberg@cisco.com>) wrote:
Most IS-IS TLV registries are “Expert Review” and we have been doing early allocation for many years now.
Are you now saying this has been invalid process for all of these years??

No, not exactly.

What I’m saying is that the rfc7120 process doesn’t apply to registries which are Expert Review only; specifically, look at §3.

For Expert Review only registries, IANA still has to be in the loop when doing the allocation, because they are the interface with the DEs.  However, unlike early allocations done through rfc7120, the DE-assigned ones don’t expire…and the requirements for Expert Review may be simpler.  So, the allocation may be done “early”, as in before the process is complete…which is perfectly fine, as long as there are no explicit instructions in the registry-creating RFC, and the DE approves.

For example, a registry with an RFC Required policy needs an RFC — obviously!  So the rfc7120 process allows for the early (= before an RFC is published) assignment.  As part of the process, the assignments expire every year and have to be explicitly renewed….in case the work is abandoned and never completed, for example.

OTOH, unless explicitly indicated in the RFC that defined the registry, a DE may assign a code point at pretty much any time (see §5/rfc8126).

Again, IANA can correct me.

Alvaro.