Re: [mpls] Fwd: I-D Action: draft-zulr-mpls-tp-linear-protection-switching-09.txt

Curtis Villamizar <curtis@ipv6.occnc.com> Fri, 31 January 2014 17:34 UTC

Return-Path: <curtis@ipv6.occnc.com>
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 161821A03EC for <mpls@ietfa.amsl.com>; Fri, 31 Jan 2014 09:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 7xp0btiGZ7zG for <mpls@ietfa.amsl.com>; Fri, 31 Jan 2014 09:34:20 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6D46B1A03E7 for <mpls@ietf.org>; Fri, 31 Jan 2014 09:34:20 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0VHY8U5082068; Fri, 31 Jan 2014 12:34:09 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401311734.s0VHY8U5082068@maildrop2.v6ds.occnc.com>
To: Eric Gray <eric.gray@ericsson.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 31 Jan 2014 16:49:19 +0000." <48E1A67CB9CA044EADFEAB87D814BFF632A03E8D@eusaamb107.ericsson.se>
Date: Fri, 31 Jan 2014 12:34:08 -0500
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "huubatwork@gmail.com" <huubatwork@gmail.com>
Subject: Re: [mpls] Fwd: I-D Action: draft-zulr-mpls-tp-linear-protection-switching-09.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: Fri, 31 Jan 2014 17:34:23 -0000

See inline.

In message <48E1A67CB9CA044EADFEAB87D814BFF632A03E8D@eusaamb107.ericsson.se>
Eric Gray writes:
> 
> Loa,
>  
> 	As I understand it, when an Internet Draft is published as an
> Independent Stream RFC, the publication notice will explicitly state
> that the document is not an IETF working group product.
>  
> 	I think it might be a good idea to offer the WG a chance to
> try to improve the quality of the draft prior to its publication, but
> I also think it is important for folks to realize two things:
>  
> 1) Because the proposal is to publish the draft as Independent, the
>      Authors aren't expected to respond to or address any detailed
>      comments on the draft itself; 2) There is no implicit working
>      group endorsement to be imputed by any lack of comments on the
>      draft itself.
>  
> 	Hence I believe - just to be clear - you are asking only for
> comments on the decision to allow publication of the draft as an
> Independent Stream RFC.
>  
> 	Is that correct?
>  
> 	Presumably, if anyone has detailed or editorial comments on
> the draft, it is probably preferable for those comments to be
> addressed to the authors of the draft privately...
>  
> --
> Eric
>  
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Thursday, January 30, 2014 12:05 AM
> To: huubatwork@gmail.com; mpls-chairs@tools.ietf.org
> Cc: mpls@ietf.org
> Subject: Re: [mpls] Fwd: I-D Action: draft-zulr-mpls-tp-linear-protection-switching-09.txt
>  
> Working Group, authors,
>  
> The authors of draft-zulr-mpls-tp-linear-protection-switching
> (http://tools.ietf.org/html/draft-zulr-mpls-tp-linear-protection-
> switching) are looking to publish their document as an Independent
> Stream RFC. The MPLS Working Group was informed about this on the
> MPLS working group mailing (see below).
>  
>  
> The MPLS Working Group decided to progress a Proposed Standard RFC for
> MPLS-TP Linear protection Switching (RFC 6378). This is still the
> Working Group consensus.  Further there is work-in-progress to update
> RFC 6378 to match the functionality of APS.
>  
> However it is a long standing tradition to publish documents that were
> not progressed as working group RFCs, particularly if they have been
> implemented and deployed. This for example is done for the historic
> record and due to the value of documenting deployed solutions.
>  
> This is the case with  draft-zulr-mpls-tp-linear-protection-switching.
> The document clearly states that IETF Standard Track MPLS-TP Linear
> Protection is specified in RFC 6378. It also states that the protocol
> specified in the draft is a non-IETF pre-standard protocol.
>  
> The MPLS working group chairs are therefore not opposed to the
> publication of the document as an RFC on the Independent Stream.
>  
> The Working Group chairs invite the working group to comment on this,
> please send comments to the working group mailing list (mpls@ietf.org)
>  
> The MPLS Working Group Chairs
> Loa, Ross and George
>  
>  
> On 2014-01-25 19:46, Huub van Helvoort wrote:
> > Dear WG chairs,
> >
> > The authors of draft-zulr-mpls-tp-linear-protection-switching
> > have decided to publish the document on the independent stream
> > as an informational RFC.
> >
> > Because it documents the pre-standard implementation of MPLS-TP
> > linear protection that has been deployed by several network
> > operators using equipment from multiple vendors.
> > At the time of publication these pre-standard implementations
> > were still in operation carrying live traffic.
> >
> > Best regards, Huub van Helvoort.
> >
> >
> > -------- Original Message --------
> > Subject: I-D Action: draft-zulr-mpls-tp-linear-protection-switching-09.txt
> > Date: Fri, 24 Jan 2014 23:36:02 -0800
> > From: internet-drafts@ietf.org
> > Reply-To: internet-drafts@ietf.org
> > To: i-d-announce@ietf.org
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> >          Title           : Pre-standard Linear Protection Switching in
> > MPLS-TP
> >          Authors         : Huub van Helvoort
> >                            Jeong-dong Ryoo
> >                            Haiyan Zhang
> >                            Feng Huang
> >                            Han Li
> >                            Alessandro D'Alessandro
> >      Filename        :
> > draft-zulr-mpls-tp-linear-protection-switching-09.txt
> >      Pages           : 27
> >      Date            : 2014-01-24
> >
> > Abstract:
> >     The IETF Standards Track solution for MPLS Transport Profile (MPLS-
> >     TP) Linear Protection is provided in RFC 6378, draft-ietf-mpls-psc-
> >     updates and draft-ietf- mpls-tp-psc-itu.
> >
> >     This document describes the pre-standard implementation of MPLS-TP
> >     Linear Protection that has been deployed by several network operators
> >     using equipment from multiple vendors.  At the time of publication
> >     these pre-standard implementations were still in operation carrying
> >     live traffic."
> >
> >     The specified mechanism supports 1+1 unidirectional/bidirectional
> >     protection switching and 1:1 bidirectional protection switching.  It
> >     is purely supported by MPLS-TP data plane, and can work without any
> >     control plane.
> >
> >     This document is a product of a joint Internet Engineering Task Force
> >     (IETF) / International Telecommunications Union Telecommunications
> >     Standardization Sector (ITU-T) effort to include an MPLS Transport
> >     Profile within the IETF MPLS and PWE3 architectures to support the
> >     capabilities and functionalities of a packet transport network as
> >     defined by the ITU-T.

The above paragraph is not true since this is not a product of an IETF
WG nor is it related to the agreed upon process between ITU-T and
IETF.  Therefore the paragraph should be removed.

> >     [Editor's note] To be included in "Status of Memo": This document is
> >     not an Internet Standards Track specification; it is published for
> >     informational purposes.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-zulr-mpls-tp-linear-protection-switching/
> >
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-zulr-mpls-tp-linear-protection-switching-09
> >
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-zulr-mpls-tp-linear-protection-switching-09
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission
> > until the htmlized version and diff are available at tools.ietf.vorg.