Re: [mpls] Last Call: <draft-ietf-mpls-spl-terminology-03.txt> (Special Purpose Label terminology) to Informational RFC

Stewart Bryant <stewart.bryant@gmail.com> Mon, 24 August 2020 17:44 UTC

Return-Path: <stewart.bryant@gmail.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 615723A0849; Mon, 24 Aug 2020 10:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 2yGtwLSZ3lGW; Mon, 24 Aug 2020 10:44:23 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABA423A0845; Mon, 24 Aug 2020 10:44:22 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id l2so9674063wrc.7; Mon, 24 Aug 2020 10:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=g7Vvwp8XVhecqzqYOTuFzoDs9Ogkrdi9937ypc8JocI=; b=kDyp6qX3+DTS8Q8WVxJvprg/WiP+0fRVSX3RbhXwY1MBmsM3BwIHV/R3/C+nILkQR2 7LGz9UhqVKBH8lV+kQxW5EpZ3DZ9HVNqsyR6qt2sqXCRmq9UfHkXnzcYwWwUNA5Su0jm Xpwglk7iotNrkIYl8xyAUdcColZjqen0qwOAwit0dp6WlnHJX2um5j42pn7sqvSzyTph 183X+2UrOZU0UPdfzeHn6ZGDl7Tn3nP/95VNVaMH5W7LlxqTHxj1zRMpPxG2mgktjqyG e06TFiGLjItzWryA8vlLbJkCWIT3nVMiIAH/g7CPVWYHmBLdVsYcKKKXNxzFDTCTfPCq QvCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=g7Vvwp8XVhecqzqYOTuFzoDs9Ogkrdi9937ypc8JocI=; b=RrJQkru4IskdixKbZoVMPD3PUdsE4beS3c8Zmv6RUkNcTlErMisTs9xRqw4BdLRmE0 hp+Cq9I5LK6DJA0kTOp1E+ASl8Od76CY4vVL7AgwnE9xepWV+LINuMRcFH+Yq8eLSX1C ILV9g9ceSJYfjut+o9uYTFTas50/qxWaP3wW7xtF+qxcMwX/YWHbUg/fuVKAgOVa+PyX NIzZJdMFUX/Dw3gy4AU7CJucyCS3rFUMkXC9QmJvHZbcZyXk3BG3TQFsgJ2gBflbr8rT 8v2LBnAwcaet3GaahW1kOhFJKURhraMIaEHolJPMmmppZBLz2DIMwIjTxpwz7tqeOWv9 9dXg==
X-Gm-Message-State: AOAM531B22zwoABzEZvRJoGPu/0ZSTwnEzOt3H8fnioq370D03ovHfbv EREceuwfw19NCYugvC5lq2E=
X-Google-Smtp-Source: ABdhPJwdYTS9/W/HWFr7P+qf2iacb/R+4wSowqMm7vBQ2CjgUnBFu0lHPjf917n7QVwTizpjsFi1NQ==
X-Received: by 2002:a5d:4bcf:: with SMTP id l15mr6779737wrt.384.1598291060806; Mon, 24 Aug 2020 10:44:20 -0700 (PDT)
Received: from [192.168.178.46] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id 31sm26022645wrp.87.2020.08.24.10.44.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Aug 2020 10:44:20 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <884D193E-0668-4275-8E8E-2011F7C09A3D@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_603A504A-69B5-42A2-AF48-689CC25C6968"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Mon, 24 Aug 2020 18:43:49 +0100
In-Reply-To: <5F439021.7050804@btconnect.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, adrian@olddog.co.uk, last-call@ietf.org, mpls@ietf.org, draft-ietf-mpls-spl-terminology@ietf.org, mpls-chairs@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <159725809676.26545.11479682416116858436@ietfa.amsl.com> <5F3D523E.2050805@btconnect.com> <08eb01d6798e$8cde63b0$a69b2b10$@olddog.co.uk> <5F439021.7050804@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/vR7PRT-wovCfU--K7VzIRtwyNf4>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-spl-terminology-03.txt> (Special Purpose Label terminology) to Informational RFC
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: Mon, 24 Aug 2020 17:44:25 -0000


> On 24 Aug 2020, at 11:02, tom petch <daedulus@btconnect.com> wrote:
> 
> On 23/08/2020 21:47, Adrian Farrel wrote:
>> Hi Tom,
>> 
>> You're right (a condition that must be scarily familiar for you).
>> 
>> Probably...
>> 
>> OLD
>>    o  Collectively, the two ranges are known as Special Purpose Labels
>>       (SPL).
>> 
>>    o  The special purpose labels from the lower range will be called
>>       Base Special Purpose Labels (bSPL).
>> 
>>    o  The special purpose labels from the higher range will be called
>>       Extended Special Purpose Labels (eSPL).
>> NEW
>>    o  Collectively, the two ranges (0-15, and 16-1048575) are known
>>        as Special Purpose Labels (SPL).
>> 
>>    o  The special purpose labels from the lower range (0-15) will be
>>        called Base Special Purpose Labels (bSPL).
>> 
>>    o  The special purpose labels from the higher range (16-1048575)
>>         will be called Extended Special Purpose Labels (eSPL).  The
>>         reserved values 0-15 from the 'Extended Special-Purpose MPLS
>>         Label Values' registry do not need a name as they can never be
>>         used.
>> END
> 
> Yes, clearer.
> 
> Perhaps
> "       The
>    reserved values 0-15 from the 'Extended Special-Purpose MPLS
>    Label Values' registry do not need a name as they are not available for allocation. "
> to tie in with the wording of IANA.  They SHOULD NOT or MUST NOT be used but I can see some independent-minded organisation deciding that because noone else will ever use them then they can and they will so I think 'can never be used' is not quite right.  They can never be allocated so we do not need an identifier for them, which is what I am wanting to express.
> 
> I note that this is Informational and so RFC2119 language is best avoided.
> 
> Tom Petch


There is no history in the Internet of anyone ever treating a "never to be used" value as an opportunity :) 

How about:

> "       The
>    reserved values 0-15 from the 'Extended Special-Purpose MPLS
>    Label Values' registry do not need a name as they MUST NOT be used “

Alternatively:

> "       The
>    reserved values 0-15 from the 'Extended Special-Purpose MPLS
>    Label Values’ registry are called the MUST NOT USE range range as they MUST NOT be used. "


- Stewart