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

Adrian Farrel <adrian@olddog.co.uk> Sun, 23 August 2020 20:47 UTC

Return-Path: <adrian@olddog.co.uk>
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 CCC183A0E53; Sun, 23 Aug 2020 13:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.006
X-Spam-Level:
X-Spam-Status: No, score=0.006 tagged_above=-999 required=5 tests=[MAY_BE_FORGED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XGaUGz-7bI9k; Sun, 23 Aug 2020 13:47:09 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 606FD3A0E52; Sun, 23 Aug 2020 13:47:07 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 07NKl24M004740; Sun, 23 Aug 2020 21:47:02 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E14D922042; Sun, 23 Aug 2020 21:47:01 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id CBAF822048; Sun, 23 Aug 2020 21:47:01 +0100 (BST)
Received: from LAPTOPK7AS653V (1.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.1] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 07NKl0Ae007611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 23 Aug 2020 21:47:01 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'tom petch' <daedulus@btconnect.com>, last-call@ietf.org
Cc: mpls@ietf.org, draft-ietf-mpls-spl-terminology@ietf.org, db3546@att.com, mpls-chairs@ietf.org
References: <159725809676.26545.11479682416116858436@ietfa.amsl.com> <5F3D523E.2050805@btconnect.com>
In-Reply-To: <5F3D523E.2050805@btconnect.com>
Date: Sun, 23 Aug 2020 21:47:00 +0100
Organization: Old Dog Consulting
Message-ID: <08eb01d6798e$8cde63b0$a69b2b10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQF6F6a5eRNF7USBcsjJJyR2gvQXGAF0oomyqfNGkdA=
Content-Language: en-gb
X-Originating-IP: 81.174.197.1
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25622.002
X-TM-AS-Result: No--31.765-10.0-31-10
X-imss-scan-details: No--31.765-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25622.002
X-TMASE-Result: 10--31.765100-10.000000
X-TMASE-MatchedRID: rYpa/RC+czFfsB4HYR80ZggKAWhuC2ojJqv0GX3SOh0/vgFpaLdKGzqJ l56wIdACd5NIkvGj2OvXHU2OPIyBgsRBLZ5x+SkXnaqtHOuEdarj5BwyjnidOI5JUK9UdYkn2P2 km/foisknQd4tVJjVqyfyuWB93oCTAKSENV9htEvM1jffIgQXhq1ZGUKR0Ygs+S5C/08hWc3hmo EMFHeqoQaytMVAgE1V1NTj7+mkLH6e74p71G9s5ZixDyZ4rnsH6KPiBX2tI0grhioeAJKilUGjS uHHltwcM1G9zj7dPEfbWy9Ndwr0MJ6kz0avHexj8eSmTJSmEv2ghxnyQNIbHeZMicrOlIVJcfIu blHY1q33gCZqe7dVr9ZxIWPsCQYqthfZltvQe7KOjIrMSa2sRwikKAH1xS/ea0TOsL14A2nccF+ vY4fYYc/4ZsnuGCiXwpvu0an2gbWQ1IMbaq27M51U1lojafr/qb3/o5s+OcO9eNsTtvBD3ozLyE gWJmpBeEOc+6uohk/Lk+qclEUD4eVHGbcDbAq6OX/V8P8ail3InWAWA4yE6ZuTdmBzA9G/DMq3z /Y/gtW8QIu4z6HhEH7cGd19dSFd
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/q4H01fxonNmbKM6SzqdYAqygSNI>
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: Sun, 23 Aug 2020 20:47:11 -0000

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

Best,
Adrian

-----Original Message-----
From: tom petch <daedulus@btconnect.com> 
Sent: 19 August 2020 17:25
To: last-call@ietf.org
Cc: mpls@ietf.org; draft-ietf-mpls-spl-terminology@ietf.org; db3546@att.com;
mpls-chairs@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-spl-terminology-03.txt> (Special
Purpose Label terminology) to Informational RFC

I find this confusing.

It specifies two ranges 0-15 and 0-1048575 the latter being subdivided 
into ranges 0-15 16-239 etc and then talks of the lower range and the 
higher range; is the higher range 0-1048575 or 16-239 or 16-1048575 or ...?
Lesser and greater or first and second or smaller and larger .. I might 
find unambiguous but reading this with an innocent eye, I find higher 
ambiguous.

And in Security, 'It does not effect the forwarding ...' Well, no, it 
would likely not affect it either:-)

Tom Petch



On 12/08/2020 19:48, The IESG wrote:
>
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document: - 'Special Purpose Label
> terminology'
>    <draft-ietf-mpls-spl-terminology-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2020-08-26. Exceptionally, comments
may
> be sent to iesg@ietf.org instead. In either case, please retain the
beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document discusses and recommends a terminology that may be used
>     when MPLS Special Purpose Labels (SPL) are specified and documented.
>
>     This document updates RFC 7274 and RFC 3032.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-mpls-spl-terminology/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> .
>