Re: [mpls] Last Call: <draft-ietf-mpls-tp-p2mp-framework-05.txt> (A Framework for Point-to-Multipoint MPLS in Transport Networks) to Informational RFC

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 04 January 2014 12:16 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D593F1ADF4F; Sat, 4 Jan 2014 04:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level:
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 AortstPeZRsf; Sat, 4 Jan 2014 04:16:46 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 420861ADF39; Sat, 4 Jan 2014 04:16:46 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04CGb9F021218; Sat, 4 Jan 2014 12:16:38 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04CGZit021190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 4 Jan 2014 12:16:36 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Date: Sat, 4 Jan 2014 12:16:29 -0000
Message-ID: <007201cf0946$d2517c30$76f47490$@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: Ac8JRrPrn/n8O7gdQU+Zn0x2e4iDrA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-p2mp-framework-05.txt> (A Framework for Point-to-Multipoint MPLS in Transport Networks) to Informational RFC
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 04 Jan 2014 12:16:48 -0000

So this doesn't get lost, here comments I sent to the authors before starting
IETF last call...

> Dan will probably want to update his coordinates.
>
> ---
>
> You don't need to be so enthusiastic with your acronyms in Section 1.2
> The following are "well known" according to
> http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>
>   GMPLS   Generalized MPLS
>   LDP     Label Distribution Protocol
>   MPLS    Multiprotocol Label Switching
>
> There is a serial comma missing from
>    OAM     Operations, Administration and Maintenance
> The comma is also missing in your text.
>
> ---
>
> In Section 1.3 you say
>
>   There is no definition for MPLS TE-LSP support of multipoint-to-
>   multipoint connectivity and none is anticipated.
>
> Without opening up a discussion of whether what you cay is true, can you
> say why it is relevant? Perhaps "This document is limited to a 
> discussion of point-to-multipoint function and does not discuss 
> multipoint-to-multipoint support." You might also move this to Section
> 1.1.

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: 02 January 2014 15:17
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-p2mp-framework-05.txt> (A
> Framework for Point-to-Multipoint MPLS in Transport Networks) to Informational
> RFC
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'A Framework for Point-to-Multipoint MPLS in Transport Networks'
>   <draft-ietf-mpls-tp-p2mp-framework-05.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
> ietf@ietf.org mailing lists by 2014-01-16. 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
> 
>    The Multiprotocol Label Switching Transport Profile is the common set
>    of MPLS protocol functions defined to enable the construction and
>    operation of packet transport networks.  The MPLS-TP supports both
>    point-to-point and point-to-multipoint transport paths.  This
>    document defines the elements and functions of the MPLS-TP
>    architecture applicable specifically to supporting point-to-
>    multipoint transport paths.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-p2mp-framework/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-p2mp-framework/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls