Re: [mpls] Review of draft-ietf-mpls-lsp-ping-registries-update-01

Loa Andersson <> Mon, 06 April 2020 05:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 035FE3A08CB; Sun, 5 Apr 2020 22:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id npmApiQdTaCp; Sun, 5 Apr 2020 22:20:57 -0700 (PDT)
Received: from ( []) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1CF163A0901; Sun, 5 Apr 2020 22:14:48 -0700 (PDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id E52F5320F79; Mon, 6 Apr 2020 07:14:43 +0200 (CEST)
To: tom petch <>, "Carlos Pignataro (cpignata)" <>, Adrian Farrel <>
Cc: mpls <>, "" <>
References: <0f5701d60847$ed2a2230$c77e6690$> <> <10a901d608df$c4cee170$4e6ca450$> <> <> <>
From: Loa Andersson <>
Message-ID: <>
Date: Mon, 6 Apr 2020 13:14:40 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [mpls] Review of draft-ietf-mpls-lsp-ping-registries-update-01
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Apr 2020 05:27:09 -0000


Interesting, looks like we need to continue the discussion on this for a

Working group,

Please respond to this question:

For the LSP Ping registries do we need both the "Experimental Use" and
"Private Use" allocation policies? If we do not need both, which can be



I have had a DOS attack against my mail server, it took us three days to
fix everything.

On 04/04/2020 00:00, tom petch wrote:
> From: mpls <> on behalf of Loa Andersson <>
> Sent: 03 April 2020 07:23
> Carlos and Adrian,
> So for the current draft I'll use "Experimental Use" and remove "Private
> Use", my rationale for that is that I get questions about "Experimental
> Use", but so far has had no question of "Private Use".
> Working Group,
> Please comment on this, either support or objections.
> <tp>
> I think that you should keep both since they have different uses.  Experimental is for us, the IETF, if we cannot quite make up our minds how to proceed yet.
> Private use is for an organisation or group thereof to go their own way and fork from the work of the IETF.  This is not desirable but history shows that it happens and I think that MPLS OAM is an area where the chances of this are higher than with some IETF protocols.
> If there is no private use, then such an organisation will camp on the Experimental which generates a problem for deployed code.
> TP
> /Loa
> for the co-authors
> On 03/04/2020 02:38, Carlos Pignataro (cpignata) wrote:
>>> 2020/04/02 午前7:13、Adrian Farrel <>のメールt;のメール:
>>> Thanks Loa,
>>> I agree with your interpretation of 8126.
>>> I think that the challenge with "experiments on the open Internet" is that the experiments have to have built into them some way to protect against two experiments using the same codepoint. That's not usually done in my experience, meaning that the two allocation classes are often pretty similar. Maybe there is some difference in duration of the use of a code point.
>>> I'd certainly be happy with collapsing these registries to use just one range. I would say that keeping the resulting range small (just a few code points) is desirable.
>> +1
>> Thanks,
>> Carlos.
>>> Best,
>>> Adrian
>>> -----Original Message-----
>>> From: Loa Andersson <>
>>> Sent: 02 April 2020 11:31
>>> To:;
>>> Cc:
>>> Subject: Re: Review of draft-ietf-mpls-lsp-ping-registries-update-01
>>> Adrian,
>>> This is to address your comment on "Private Use" and "Experimental Use",
>>> we will review the rest of the comments and update as needed.
>>> On 02/04/2020 01:06, Adrian Farrel wrote:
>>>> Hi all,
>>> <snip>
>>>> I have a number of small editorials and some larger questions and issues
>>>> set out below. I also have one question that has broader scope:
>>>> For [IANA-MT] and [IANA-Sub-6] you now have both 'Private Use' and
>>>> 'Experimental Use'. I struggle to see how this makes sense. The uses
>>>> decribed in RFC 8126 are sufficiently similar that it is unusual to
>>>> have both categories defined for a single registry. I don't see anything
>>>> in the descriptive text in this document that makes clear why you need
>>>> both categories and how an implementation would decide which range to
>>>> select a code point from.
>>> <snip>
>>> You are right I've been struggling with these two type of code points
>>> also, but came to a slightly different conclusion than you did.
>>> RFC 8126 says:
>>> 4.1.  Private Use
>>>      Private Use is for private or local use only, with the type and
>>>      purpose defined by the local site.  No attempt is made to prevent
>>>      multiple sites from using the same value in different (and
>>>      incompatible) ways.  IANA does not record assignments from registries
>>>      or ranges with this policy (and therefore there is no need for IANA
>>>      to review them) and assignments are not generally useful for broad
>>>      interoperability.  It is the responsibility of the sites making use
>>>      of the Private Use range to ensure that no conflicts occur (within
>>>      the intended scope of use).
>>>      Examples:
>>>         Site-specific options in DHCP [RFC2939]
>>>         Fibre Channel Port Type Registry [RFC4044]
>>>         TLS ClientCertificateType Identifiers 224-255 [RFC5246]
>>> 4.2.  Experimental Use
>>>      Experimental Use is similar to Private Use, but with the purpose
>>>      being to facilitate experimentation.  See [RFC3692] for details.
>>>      IANA does not record assignments from registries or ranges with this
>>>      policy (and therefore there is no need for IANA to review them) and
>>>      assignments are not generally useful for broad interoperability.
>>>      Unless the registry explicitly allows it, it is not appropriate for
>>>      documents to select explicit values from registries or ranges with
>>>      this policy.  Specific experiments will select a value to use during
>>>      the experiment.
>>>      When code points are set aside for Experimental Use, it's important
>>>      to make clear any expected restrictions on experimental scope.  For
>>>      example, say whether it's acceptable to run experiments using those
>>>      code points over the open Internet or whether such experiments should
>>>      be confined to more closed environments.  See [RFC6994] for an
>>>      example of such considerations.
>>>      Example:
>>>         Experimental Values in IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP
>>>         Headers [RFC4727]
>>> It seems to me that "Private Use" are intended for private networks,
>>> where care is taken that the code points are not leaked into the
>>> Internet, but there the network itself is a production network, that
>>> will be run for an unforeseeable amount of time. And that "Experimental
>>> Use" code points are for short lived experiments.
>>> This is different.
>>> I'm very uncertain whether it is sufficiently different to motivate two
>>> different types. If the working group thinks there should be only one
>>> code point, I would argue to keep the code points for "Experimental
>>> Use". If we converge on "one type of code point only, I think this has
>>> a wider impact than this document, and we should probably update RFC
>>> 8126 (again).
>>> I'd like to invite comments on this on the mpls wg list.
>>> /Loa
>>> --
>>> Loa Andersson                        email:
>>> Senior MPLS Expert
>>> Bronze Dragon Consulting             phone: +46 739 81 21 64
> --
> Loa Andersson                        email:
> Senior MPLS Expert
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list


Loa Andersson                        email:
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64