Re: [Lsr] Question on the early allocation - Re: [IANA #1171772] Early Allocations request for "Area Proxy for IS-IS" - draft-li-lsr-isis-area-proxy-04

tom petch <ietfc@btconnect.com> Wed, 03 June 2020 08:43 UTC

Return-Path: <ietfc@btconnect.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 9F7CE3A0EAA for <lsr@ietfa.amsl.com>; Wed, 3 Jun 2020 01:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 PZ6ZmHBA6pxH for <lsr@ietfa.amsl.com>; Wed, 3 Jun 2020 01:43:41 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00122.outbound.protection.outlook.com [40.107.0.122]) (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 9CA543A0EA6 for <lsr@ietf.org>; Wed, 3 Jun 2020 01:43:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SYHOHT7Jp42Rf7XQxgdSyWxEyD7nZ3xWi8AIjZ1alVymS1KV560Vaewl6IkMM0Fav1H4XGa4YVxxEsrwwnrMEARNYBCL8w7VsQu8eRemq4MZHpLGJ+BhNQ3yl6fzVNrjc+r3CZPvKOGXB3dammhyrtHeaC/ar0nH7v6rax4LGJWotEvw+x/Bmjk3udlV7e465gUS/JInxEV0OtFAHQrdLwi4KohHBqofRd1qEemkdKiprrN1wDJHe2Y8UGpkhBrQ27alyYAPF0iJVvnCMLxoD3sDafrQn/Ii22RLlNTq0jiATJ2adGjmp7dOGxSxnyNatgenmh299/hkajrvoq0iLw==
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=HgAuVRZtuZJI19DJCrkCnhHyPe0bI8WPeCAVYPFgFVw=; b=RYPlbxHUbPU7d7S/1U40oL/HYFoh53mAJSu9kUajLTrn9hW0LME96zGybAixygnLra8EB7SgYgkxyENoTRuLBU6+HuqmvzEo4ZdOVwrQmfkd3QXh6iraFnKE1hOQ4mpOwpgG8tMPE4IUM4xq3OV05YQ6VpdjS3W1WC8Z4zvAO1Qn0X28im+79PK7PdflueGpbHine+vurxgiGbkQuBo53hJEo8WBXGX/GBFQs00dR6aM9smU4LEuOoKTgSPkl1phs+P7oGpkPJEUq/h3g86WXJ2EXBBXStDevb4R7QeKlMV41t4i9+10/NE3eYDikzKUgyq0R8um6eAbUoYFPGpUdw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HgAuVRZtuZJI19DJCrkCnhHyPe0bI8WPeCAVYPFgFVw=; b=i1ONqa0wDTh8gywWU4slPC7lAZJXV61Px0UhUab582vPFC2BPJh7KnCOLPXjHboffnIrkq6yWm3sMx2SPHUgqMehx2Y2pbepWFj7iz0gUU3OmCsI5PP/OSkgEkoEI+3eOUHFghZJuirQH0kX1JRgDBIYisBdQkhyjEHDZOGLfHI=
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com (2603:10a6:10:198::14) by DBAPR07MB6872.eurprd07.prod.outlook.com (2603:10a6:10:17c::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.7; Wed, 3 Jun 2020 08:43:39 +0000
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::592c:285:6786:bc65]) by DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::592c:285:6786:bc65%7]) with mapi id 15.20.3066.016; Wed, 3 Jun 2020 08:43:39 +0000
From: tom petch <ietfc@btconnect.com>
To: Loa Andersson <loa@pi.nu>, "tony.li@tony.li" <tony.li@tony.li>
CC: "lsr@ietf.org" <lsr@ietf.org>, "iana-prot-param@iana.org" <iana-prot-param@iana.org>, Martin Vigoureux <martin.vigoureux@nokia.com>, "acee@cisco.com" <acee@cisco.com>
Thread-Topic: [Lsr] Question on the early allocation - Re: [IANA #1171772] Early Allocations request for "Area Proxy for IS-IS" - draft-li-lsr-isis-area-proxy-04
Thread-Index: AQHWOLPtWJkDX5vsukir6bbudJiPPajFcliAgAELOACAABUe4A==
Date: Wed, 03 Jun 2020 08:43:38 +0000
Message-ID: <DBAPR07MB7016A90CE8BD1EDC05CDB230A0880@DBAPR07MB7016.eurprd07.prod.outlook.com>
References: <RT-Ticket-1171772@icann.org> <C952BE83-EF9E-437F-836C-D3221FF533DF@cisco.com> <rt-4.4.3-29956-1591060382-1741.1171772-37-0@icann.org> <39E5E5AC-8E29-43F0-86C3-194754A5B7A7@gmail.com> <918d12eb-d2c2-7867-5cb7-8913a8e35c7b@pi.nu> <92F24980-10F5-4EB9-839A-DCF5A2AE7552@tony.li>, <b2da6f1d-83c7-2547-936d-1608ce97ca54@pi.nu>
In-Reply-To: <b2da6f1d-83c7-2547-936d-1608ce97ca54@pi.nu>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: pi.nu; dkim=none (message not signed) header.d=none;pi.nu; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [81.131.229.108]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 36fde821-c3e4-4803-c499-08d8079a365c
x-ms-traffictypediagnostic: DBAPR07MB6872:
x-microsoft-antispam-prvs: <DBAPR07MB68729C82731B4052934C2522A0880@DBAPR07MB6872.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 04238CD941
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: U/kjwgFue3gQfHtEHKyu2GaQ1icpPCnFcorQ/T6J1VZMP+/AAgdBH+sefSbn/z963i5N95jfN0PbtJ9A3j+w1etxR8/wjw4i4fv4GGaIQk6oCDa4U4RKQFBTVF5wc9c5Bg05OM3eHwnpGzB0NdzKaK35J2XWxVpRxyrJjyI3vvuhya3tcvQij0M7wuwU8FbNmW4DYeUirvPeHRReViSHOnAgB4aDXFZbNN654HD8ezRKEVefM51tvcKVNw9HKz+ZMx+HW4XDoT+0LMK1rMoPgtKWIqH+CcVL/yti7EIJnAMAQQQpNSMtSTMS9rpjM2nClbHgA3MxcfizjfoAycyyfbZ+99Gzgyzj/8gvk3Db3Kv8Kj11TFF+35waS3LRU2lupEn6amnY0fiYYNQAxHJZpA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DBAPR07MB7016.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(136003)(346002)(376002)(39860400002)(366004)(396003)(83380400001)(9686003)(86362001)(66476007)(66446008)(76116006)(66946007)(55016002)(64756008)(91956017)(66556008)(71200400001)(8936002)(26005)(52536014)(6506007)(2906002)(186003)(478600001)(5660300002)(316002)(54906003)(110136005)(8676002)(966005)(33656002)(7696005)(53546011)(4326008); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: doSEM/Jo6KWjrukmVmC27GD/lbyLKl0zRt/Lp0CrJrIV75tasa9GB2X1Ud62YLqBB95sxBz6tMYPzh3uDoFbnHvsGyXVeNPeKynVRFGVdrHQzrNGWXzWdZFJ+s6tGsWWtn8dVPirfD5L64h9QbzXKBxnTgkIyCg7s9UEBRwF/dZhlXi7+TbsUI4NvaXA6Vtg5m9XwIP4E2/l/7kkfZBRK3u2t97LxEcdd1JSUcZHEcnkyA+FlbcU48YGVZkSH+T3cxM4FSKmYiz3FcXx5adoVqzwlF1O7aEKp1vcvgtmxw2mfPufLrBeVW9cZW0Lfg7XWtZdYzpr0yy7p/Ec0Esku+AC+3z2+fefmPslZ/89gN0DzdgKh6nhp8ZWyDHM4c50F8wiHKOpHvgcnEQENqJvT+Lq1hP2sUZBeLYPDNSelNgAywnnuj5SnTB1a3CmU0ZW7dJwcGPtIrB/75ra+rVfx72Na2K7+oAvLR+hMh5ORBNXWYZXIwuHzBflIYmvlnYj
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 36fde821-c3e4-4803-c499-08d8079a365c
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2020 08:43:38.9739 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 65tNdo8+7+wOhxdTE0DVxzm5PgQJ+SFEN/kDZo0LcigX2o3kASufiqGFHDG2Lmumkj3sd9Dps6LvtzpeiFxeyg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBAPR07MB6872
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4E8FlZTHFFRPIZJ7jB486fmRAW8>
Subject: Re: [Lsr] Question on the early allocation - Re: [IANA #1171772] Early Allocations request for "Area Proxy for IS-IS" - draft-li-lsr-isis-area-proxy-04
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: Wed, 03 Jun 2020 08:43:44 -0000

From: Lsr <lsr-bounces@ietf.org> on behalf of Loa Andersson <loa@pi.nu>
Sent: 03 June 2020 08:20

Tony,

I guess that this shows that we should take care naming our registries.

In line please-

On 02/06/2020 23:24, tony.li@tony.li wrote:
>
> Hi Loa,
>
>> The code points are requested from "the IS-IS TLV Codepoints registry",
>> howver the "IS-IS TLV Codepoints" is a name space with 14 different
>> registries. I think the the registry you want to allocated code point
>> from the "TLV Codepoints registry”
>
>
> I apologize for the confusion, you are certainly correct.
>
> The confusion arises because the page is named “IS-IS TLV Codepoints”
> and the registry is the “TLV Codepoints Registry” so to be precise, we
> should request an allocation from the “IS-IS TLV Codepoints TLV
> Codepoints Registry”.  That does seem somewhat awkward and redundant
> redundant.
>
> To reduce confusion in the future, perhaps the entire page should be
> renamed to “IS-IS Codepoints”?

In the party of the world there I'm active there is a tendency to call
"the page" the "name space", that stops us from repeating "registry" to
often, so we have name space, registry and sub-registry. This is as I
understand it a terminology IANA understands, even if there is no formal
acceptance of it.

<tp>
Loa,

I try to persuade authors to follow RFC8126 (which I think IANA understands).  It recognises the historical confusion with naming and recommends that, going forward, a two tier naming of Group and Registry be used.  I see the TLV Codepoints Registry as part of the I S - I S (spaces added to fool the spam detectors) Group.  That seems to me to be clear and unambiguous and not prolix.  I think that its inclusion in the RFC makes it formally accepted by the IETF:-)

Tom Petch
Renaming the name space would require us to update a number of IS-IS
documents. I would advice against that, but if the wg decides to do it
try to help to get correct.

For the time being I'd say that we want to allocate the code points
from the "TLV Codepoints" reistry in the IS-IS TLV Codepoints"
namespace.

Doing that way it is also easier to find the correct registry.

 >/Loa
>
> Regards,
> Tony
>

--

My mail server from time to time has come under DOS attacks,
we are working to fix it but it may take some time. If you
get denial of service sending to me plz try to use
loa.pi.nu@gmail


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

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr