Re: [mpls] Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt>
"Adrian Farrel" <adrian@olddog.co.uk> Thu, 03 October 2013 08:50 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 EFBE021F9633; Thu, 3 Oct 2013 01:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level:
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1yWNJkpT1by; Thu, 3 Oct 2013 01:50:13 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B79E621F9767; Thu, 3 Oct 2013 01:48:39 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r938mccf011403; Thu, 3 Oct 2013 09:48:38 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r938mZkw011333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Oct 2013 09:48:36 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: ietf@ietf.org
Date: Thu, 03 Oct 2013 09:48:32 +0100
Message-ID: <031601cec015$591026c0$0b307440$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7AFRRiZXQ2TaqrQyKn1YTQ2cj7dw==
Content-Language: en-gb
Cc: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt>
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 Oct 2013 08:50:26 -0000
Thanks for this document which was surprisingly readable. I have a number of comments from my AD review, but they are all trivial and can be handled as IETF last call comments. Thanks, Adrian --- Nurit will want to change the minor details or her affiliation. --- Abstract Expand MPLS-TP and PW on first use. Expand MS s/recommendations/Recommendations/ >>> Apply throughout document s/nor/or/ --- Section 1 s/telecommunication/Telecommunication/ --- Section 1.2 s/Administration and Maintenance/Administration, and Maintenance/ --- Section 3.4 s/APPENDIX/Appendix/ --- Section 3.5 Please expand PW --- Section 3.7 One might ask whether a co-routed bidirectional path that traverses a LAG or a link bundle uses the same component links in both directions. --- Section 3.8 could probably usefully mention routing along with signaling. --- Section 3.11 s/physical channels/a physical channel/ --- Section 3.16 Please expand LSR --- One paragraph in 3.17 is a bit wild. Therefore, in the context of MPLS-TP LSP or PW Maintenance Entity (defined below) LERs and T-PEs can be MEPs while LSRs and S-PEs can be MIPs. In the case of Tandem Connection Maintenance Entity (defined below), LSRs and S-PEs can be either MEPs or MIPs. s/context of/context of a/ "PW Maintenance Entity" is not defined below (I think). Please expand LER I don't find the definition of "Tandem Connection Maintenance Entity" Maybe you could say ...the case of a Maintenance Entity for a Tandem Connection (defined below) Please expand S-PE --- Section 3.19 Penultimate paragraph Second instance s/(e.g. count packets)./(e.g. counts packets)./ --- Section 3.23 s/described in three ways:/described in one of three ways:/ s/Sub-Path Maintenance Element, and/Sub-Path Maintenance Element, or/ s/as a Tandem Connections./as a Tandem Connection./ --- Section 3.23.2 Section header s/(SMPE):/(SPME):/ --- Section 3.35 The use of pipe ("|") and curly braces ("{" and "}") could usefully be replaced with English language. > -----Original Message----- > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce- > bounces@ietf.org] On Behalf Of The IESG > Sent: 02 October 2013 22:45 > To: IETF-Announce > Cc: mpls@ietf.org > Subject: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the > Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) > drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational > RFC > > > The IESG has received a request from the Multiprotocol Label Switching WG > (mpls) to consider the following document: > - 'A Thesaurus for the Terminology used in Multiprotocol Label Switching > Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport > Network Recommendations.' > <draft-ietf-mpls-tp-rosetta-stone-12.txt> as Informational RFC
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-rosetta… Adrian Farrel
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-rosetta… Huub helvoort