Re: [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Greg Mirsky <gregimirsky@gmail.com> Fri, 18 February 2011 18:14 UTC

Return-Path: <gregimirsky@gmail.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 247FB3A6D6A; Fri, 18 Feb 2011 10:14:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level:
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 Jk3U5VHbczmr; Fri, 18 Feb 2011 10:14:54 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 9D8E33A6D48; Fri, 18 Feb 2011 10:14:53 -0800 (PST)
Received: by vxi40 with SMTP id 40so2334276vxi.31 for <multiple recipients>; Fri, 18 Feb 2011 10:15:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eFhbxbVkVd9RRDxruN1eHxWuzfkY9LqBZ17udURWnxI=; b=Eyw3njNi9WkoxdXq6rv6DfBqfhylFf3/LoS1KEOtAqtvDV3cdcJgDr78E5VlUpM2P1 Ylbd7TKcDv9u49VmyNRq3zkMppKwXJMvuDcdzEdE5foR04unDz+8uOzPCgWTGZAS0Hqq 1Km/WT6PytuY2a1FiaKrBTZrp2ugj2QmeOniM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C8KfCMqjLbrj7/7LT+ldM0AolurQ3cZ8lRDVT08f8H962E9+r3oXco5QaMOeU+QzDr HMsTbIy+Nw/96Lz8lElBzultAuw9qltnHYe8oyzo+N31KBtGH4+OT6cKJl2lBPgrReMK FMZdb8V/POafL1EFBx6cwms/89yqOSaVHgecI=
MIME-Version: 1.0
Received: by 10.52.164.166 with SMTP id yr6mr1831510vdb.245.1298052926692; Fri, 18 Feb 2011 10:15:26 -0800 (PST)
Received: by 10.52.165.9 with HTTP; Fri, 18 Feb 2011 10:15:26 -0800 (PST)
In-Reply-To: <4D5E9442.3030101@cisco.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com>
Date: Fri, 18 Feb 2011 10:15:26 -0800
Message-ID: <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Luca Martini <lmartini@cisco.com>
Content-Type: multipart/alternative; boundary="bcaec53f9359985e7f049c927f19"
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, 18 Feb 2011 18:14:55 -0000

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.
   - 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.

Regards,
Greg

On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <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>> 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>
> >>     https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
>
>