Re: [mpls] please review and comment on draft-ietf-mpls-spl-terminology-00

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 05 August 2019 14:48 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 75622120230; Mon, 5 Aug 2019 07:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 QvuDKlcmJn9N; Mon, 5 Aug 2019 07:48:17 -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 A086F12022C; Mon, 5 Aug 2019 07:48:16 -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 x75EmCTi004753; Mon, 5 Aug 2019 15:48:14 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6E99322073; Mon, 5 Aug 2019 15:48:13 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS id 2B8E6220FA; Mon, 5 Aug 2019 15:47:01 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.55.143]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x75El0ax014828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Aug 2019 15:47:00 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Loa Andersson'" <loa@pi.nu>, <mpls@ietf.org>
Cc: <draft-ietf-mpls-spl-terminology@ietf.org>, <mpls-chairs@ietf.org>
References: <32b8812e-612f-ad46-5d7f-8a388e380680@pi.nu>
In-Reply-To: <32b8812e-612f-ad46-5d7f-8a388e380680@pi.nu>
Date: Mon, 5 Aug 2019 15:46:59 +0100
Organization: Old Dog Consulting
Message-ID: <044801d54b9c$a309fda0$e91df8e0$@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: AQILzu4c0kox5ZLU+XvtdUsedrO9IaZ/iYwQ
Content-Language: en-gb
X-Originating-IP: 87.112.55.143
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-24824.000
X-TM-AS-Result: No--25.437-10.0-31-10
X-imss-scan-details: No--25.437-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24824.000
X-TMASE-Result: 10--25.436800-10.000000
X-TMASE-MatchedRID: H0/uSqZo4D6WfDtBOz4q23FPUrVDm6jtS/ceBQrgS1GnRvssirgAK1bT tJpG9MBBacAE0BXYlcvos7IkKKuHv2MFwILfD7Ygkr0W/BDHWEXg02I3oyGU8Dt7ZjJPAVIiQbN TsIpfWx100u7RRzZGJSHLV9tiezQQkIURhdJWezuqNnzrkU+2mky2QelP2Gj6dNfwwV0Dnr74eY E/JF5KDK/vNCEa2eMJ22Kl3jXtGB9H4UfwjA8Kge5b8GtgkaX9B4Id7CiQcz9s98Z8fG/6kXGaI 3obawWA7Bcpk9b8c2UDTO7t0MJ81Xw/Myj5kX8jqSG7nd+vxDcO9z+P2gwiBS/viQPfOXgnVkEH zL0JqHPKwCMHWrmfRNHsFnkoty1Jpr9mIV4enT71WO1NzV/CYFHewY36PuY0hgn72LMkncpNLIM 9jwUeZ684CEZJnIyVU6WsjEEjHBHGuitb2uBRc/7kh4czHCCaqV3VmuIFNEvWXfwzppZ8SI+04h OwZfJRufn6f1qEnWl0xfeV4aF6gN5bQ01TbK1/qa6SJk58+LZd811WB7wXJ3QRKyUJW+vLtNfew smJeFYZw5ucm3NLWsuT6pyURQPh5UcZtwNsCro5f9Xw/xqKXcidYBYDjITpi2QFaYS1v20qtq5d 3cxkNQwWxr7XDKH8lExlQIQeRG0=
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/ZSsv7eCCr0EX9UffuWuuu5FCARY>
Subject: Re: [mpls] please review and comment on draft-ietf-mpls-spl-terminology-00
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, 05 Aug 2019 14:48:20 -0000

Hi Loa,

I guess all authors should review their own work!

Idnits says...

> -- The draft header indicates that this document updates RFC3032, but the
>     abstract doesn't seem to mention this, which it should.
>
> -- The draft header indicates that this document updates RFC7274, but the
>     abstract doesn't seem to mention this, which it should.

The Abstract also has notes that we should now remove. So...

OLD
   This document discusses and recommends a terminology that may be used
   when MPLS Special Purpose Labels (SPL) are specified and documented.

   Note: The rest of the text in this section is not really part of the
   abstract even though the text is placed here.  It is working notes.

   Note: At least at the moment it is not the intention to take this
   document to an RFC, but it might be polled to become a wg document to
   see if the MPLS working group agree on the proposed terminology.

   Note: The changes we propose are minor, but we might have to progress
   the document to RFC since there is a proposed change to the "Special-
   Purpose Multiprotocol Label Switching (MPLS) Label Values" registry.
NEW
   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 3032 and RFC 7274 by clarifying and refining
   The terminology that those documents define.  It does not make any
   Changes to on-wire formats or the behaviour of implementations.
END

---

Section 1

OLD
   RFC 7274 [RFC7274] made some changes to the terminology used for MPLS
   Special Purpose Labels, but did not define consistent terminology.
NEW
   RFC 7274 [RFC7274] made some changes to the terminology used for MPLS
   Special Purpose Labels, labels 0-15 as originally defined in RFC 3032
[RFC3032],
   but did not define consistent terminology.
END

---

Section 1

OLD
   One thing that RFC 7274 did was to deprecate use use of the term
   "reserved labels"
NEW
   One thing that RFC 7274 did was to deprecate use of the term
   "reserved labels" [RFC3032]
END

---

Section 1

OLD
   At the time of posting this Internet-Draft, the IETF is in the
   process of allocating the very first SPLs from the Extended SPL range
   [I-D.ietf-mpls-sfc].  
NEW
   The first SPL from the Extended SPL range was allocated for
   RFC 8595 [RFC8595].
END

---

Section 1 Add a final paragraph...

   This document updates RFC 3032 and RFC 7274 by clarifying and refining
   The terminology that those documents define.  It does not make any
   Changes to on-wire formats or the behaviour of implementations.

---

Thanks,
Adrian

-----Original Message-----
From: mpls <mpls-bounces@ietf.org> On Behalf Of Loa Andersson
Sent: 15 July 2019 08:05
To: mpls@ietf.org
Cc: draft-ietf-mpls-spl-terminology@ietf.org; mpls-chairs@ietf.org
Subject: [mpls] please review and comment on
draft-ietf-mpls-spl-terminology-00

Folks,

About a week ago we posted the first working group version of
draft-ietf-mpls-spl-terminology.

Please read and comment. Please send comments to the mpls wg mailing
list.

The authors think that the draft is stable and plan to request wglc
after the f2f meeting in Montreal.

/Loa
fior the co-authors
-- 


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

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