Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Luca Martini <lmartini@cisco.com> Fri, 11 March 2011 13:37 UTC
Return-Path: <lmartini@cisco.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 764153A6BE8; Fri, 11 Mar 2011 05:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLUKklh89MY5; Fri, 11 Mar 2011 05:37:03 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id 13A103A69AE; Fri, 11 Mar 2011 05:37:03 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p2BDVbhM014634 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 11 Mar 2011 06:31:38 -0700 (MST)
Message-ID: <4D7A2439.6010508@cisco.com>
Date: Fri, 11 Mar 2011 06:31:37 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
In-Reply-To: <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: lihan@chinamobile.com, mpls@ietf.org, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 13:37:04 -0000
Greg , Some On 02/18/11 11:15, Greg Mirsky wrote: > Dear Luca, > I see at least two issues: > > * use of GAL for PW, in my view, is another VCCV CC type that has > to be negotiated as described in RFC 5085. > These are valid points, but this document in question does not define, not discussed VCCV. We have since posted a draft that proposes a new VCCV mode , and we welcome comments regarding that document. (draft-nadeau-pwe3-vccv-2-01.txt) > * use of GAL creates ambiguous situation when PW CW is used. The > benefit from extending GAL in PW, as I see, is for PWs that are > not required to use PW CW. That might be a good enough reason to > update RFC 5586 as proposed in the document but we must address > use cases of GAL in PWs that require presence PW CW. If we > prohibit or even discourage use of GAL for these PWs that have > PW VCCV as native Associated Channel, then architecture of ACh > for MPLS-TP PW not simplified as result of adopting the proposal. > > Regard Greg, The GAL is basically a notifier that the packet following the end of the MPLS label stack, is explicitly defined as a G-ACH format. Normally the packet would be decoded as an IP packet , unless the last label on the stack indicated otherwise. The GAL can certainly be applied to a PW OAM packet on a PW that uses the CW, and this document does not define that , nor restricts it. The scope of this document is limited to removing an unnecessary restriction in rfc5586, hence this comment not applicable to this document. Thanks. Luca > s, > Greg > > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com > <mailto:lmartini@cisco.com>> wrote: > > Greg, > > Sorry, but I do not remember the point you mention. > Can you explain again here ? > Thanks. > Luca > > > On 02/17/11 23:47, Greg Mirsky wrote: > > Dear Authors and All, > > prior to the meeting in Bejing and acceptance of this proposal as WG > > document Luca and I agreed that use of GAL with PW VCCV presents a > > problem. > > I was not attending the IETF-79, nor I found discussion of this > issue > > in the minutes. I think that this issue should be specified, > > explained. In my view, this document updates not only RFC 5586 > > but RFC 5085 too. > > > > Regards, > > Greg > > > > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt > > > > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini > <lmartini@cisco.com <mailto:lmartini@cisco.com> > > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote: > > > > Greg, > > > > You are correct , the proposed update does not propose any > changes > > to VCCV. > > However the problem with vccv is not as simple as to ask for > a new > > code point from IANA. > > Given the good amount of discussion on this point, we should > > probably have a discussion in Beijing. > > > > Luca > > > > > > > > On 10/29/2010 05:07 PM, Greg Mirsky wrote: > >> Dear Authors, > >> I think that proposed update of the Section 4.2. RFC 5586 > makes it possible > >> to use GAL on MPLS-TP PW that uses Control Word. I consider > it to be > >> conflict between PW VCCV CC types because use of GAL is not > negotiated > >> through PW VCCV negotiation. To avoid such situation I propose: > >> > >> - in Section 5 request IANA to assign new CC Type "MPLS > Generic > >> Associated Channel Label" > >> - assign precedence to new CC Type that affects Section > 7 RFC 5085 > >> > >> Regards, > >> Greg > >> > >> > >> > >> _______________________________________________ > >> mpls mailing list > >> mpls@ietf.org <mailto:mpls@ietf.org> <mailto:mpls@ietf.org > <mailto:mpls@ietf.org>> > >> https://www.ietf.org/mailman/listinfo/mpls > > > > > > > > _______________________________________________ > > mpls mailing list > > mpls@ietf.org <mailto:mpls@ietf.org> > > https://www.ietf.org/mailman/listinfo/mpls > >
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Greg Mirsky
- [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-0… Greg Mirsky
- Re: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-… Alexander Vainshtein
- Re: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-… neil.2.harrison
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Luca Martini
- Re: [mpls-tp] [PWE3] WG LC draft-lm-pwe3-mpls-tp-… Shahram Davari
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Luca Martini
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Greg Mirsky
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Alexander Vainshtein
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… venkatesan mahalingam
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Thomas Nadeau
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Alexander Vainshtein
- Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-… Robert Rennison
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Greg Mirsky
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Alexander Vainshtein
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Greg Mirsky
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Alexander Vainshtein
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Curtis Villamizar
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Alexander Vainshtein
- Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-m… Curtis Villamizar