Re: [Pce] WG Last Call for draft-ietf-pce-binding-label-sid-07 (and Code Point Allocation) Tue, 30 March 2021 10:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5AAF3A083B; Tue, 30 Mar 2021 03:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.191
X-Spam-Status: No, score=0.191 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, FORGED_MUA_MOZILLA=2.309, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MDdVxYNJzeFY; Tue, 30 Mar 2021 03:47:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF3653A0825; Tue, 30 Mar 2021 03:47:08 -0700 (PDT)
Received: from (unknown [xx.xx.xx.68]) by (ESMTP service) with ESMTP id 4F8mNV6nCFz10MB; Tue, 30 Mar 2021 12:47:06 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1617101226; bh=MFuSfpn9wWkRRQWJAnXIpdTqnUtT1XwuuEuw91tYmOM=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; b=hs/1ivbXuwN2YsItue7AMuIDOmXz2ZHWYU3QtFcIuS20BzV5GIqBeNNiP5lHIzvaB w4uwwAVykUZqp+9IhrzTijQoTY5QqBWqq8MOtqKvd4zhqe5HOSKUPk9t65ds22NJdE 8Hu8oBMqGL3oiza/1TMl0KNTOW4mMIgyKAaBu6Hi5EGArD6dgmNz7wlniSlY8k+PtF fNlSyluY96p7YOU55oJj/GJaUeoqSwfS0fY2zN+WrfAYBTPpazlES4skHtIzhwsxtc 5UnS9yx8HuwJXruhO8llUsT0oUx+iRvZGmtyayYhEMkeB/YE71ohTOJB6cFJpv8waI IUgiUhHI7OT2g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) by (ESMTP service) with ESMTP id 4F8mNV63h1z1xpd; Tue, 30 Mar 2021 12:47:06 +0200 (CEST)
Received: from [] ( by exchange-eme6.itn.ftgroup ( with Microsoft SMTP Server (TLS) id 14.3.498.0; Tue, 30 Mar 2021 12:47:06 +0200
To: tom petch <>
CC: "" <>, "" <>, "" <>
References: <> <0b8501d71fcd$c68ee810$53acb830$> <>
From: <>
Organization: Orange
Message-ID: <>
Date: Tue, 30 Mar 2021 12:47:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: []
Archived-At: <>
Subject: Re: [Pce] WG Last Call for draft-ietf-pce-binding-label-sid-07 (and Code Point Allocation)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 30 Mar 2021 10:47:14 -0000

Hi Tom,

What really matters for the IANA early allocation is that the behaviors
associated to the code points are clear and stable. Assuming the WG
agrees on moving to the "binding value" terminology all along the
document, then the technical specification wouldn't change (i.e. it
would clearly be backward compatible [1]) and we could update the phrase
in IANA entry accordingly at final allocation time.




On 27/03/2021 13:02, tom petch wrote:
> <tp>
> Adrian
> I share your comments about the terminology in this I-D which is not precise, failing to specify 'MPLS label' and failing to use 'MPLS label stack entry' but I think that the worst part is this 'binding/Label SID' which to me is a classic example of how not to choose an identifier.  The I-D does use 'binding value' in one place as what appears to be one of the many different terms for this concept and I think that term much better.
> Since this term, whatever it is, gets embedded in IANA, I said that the IANA early allocation should not proceed until this is resolved, but you may not take it that far.
> Tom Petch


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.