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

"Shahram Davari" <davari@broadcom.com> Fri, 18 February 2011 17:15 UTC

Return-Path: <davari@broadcom.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 A8AF83A6D56; Fri, 18 Feb 2011 09:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5]
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 yWTUe9upzuNI; Fri, 18 Feb 2011 09:15:39 -0800 (PST)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 56EE03A6CC7; Fri, 18 Feb 2011 09:15:39 -0800 (PST)
Received: from [10.16.192.232] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 18 Feb 2011 09:17:34 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Fri, 18 Feb 2011 09:15:37 -0800
From: Shahram Davari <davari@broadcom.com>
To: "'Alexander.Vainshtein@ecitele.com'" <Alexander.Vainshtein@ecitele.com>, "'gregimirsky@gmail.com'" <gregimirsky@gmail.com>
Date: Fri, 18 Feb 2011 09:15:36 -0800
Thread-Topic: [PWE3] [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvPN6zTJGq/0XxDTGy6v16DWGU3fgAAocFMABVQVLE=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD69419A002F9@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 614076275OK8247826-01-01
Content-Type: multipart/alternative; boundary="_000_2C2F1EBA8050E74EA81502D5740B4BD69419A002F9SJEXCHCCR02co_"
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, "'HUANG@core3.amsl.com'" <HUANG@core3.amsl.com>, "'Rotem@core3.amsl.com'" <Rotem@core3.amsl.com>, "'mpls-tp@ietf.org'" <mpls-tp@ietf.org>, "'Mishael.Wexler@ecitele.com'" <Mishael.Wexler@ecitele.com>, "'lihan@chinamobile.com'" <lihan@chinamobile.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>, "'Feng.f.Huang@alcatel-sbell.com.cn'" <Feng.f.Huang@alcatel-sbell.com.cn>, "'Robert.Rennison@ecitele.com'" <Robert.Rennison@ecitele.com>, "'Rotem.Cohen@ecitele.com'" <Rotem.Cohen@ecitele.com>
Subject: Re: [mpls-tp] [PWE3] 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 17:15:40 -0000

I also agree with Sasha. Creating a VCCV type 4 is problematic, almost no hardware exist for it and causes interworking issues. Signaling VCCV needs to change as well.

Thx
Shahram

________________________________
From: pwe3-bounces@ietf.org <pwe3-bounces@ietf.org>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Robert Rennison <Robert.Rennison@ecitele.com>; mpls@ietf.org <mpls@ietf.org>; Luca Martini <lmartini@cisco.com>; mpls-tp@ietf.org <mpls-tp@ietf.org>; Mishael Wexler <Mishael.Wexler@ecitele.com>; lihan@chinamobile.com <lihan@chinamobile.com>; pwe3 <pwe3@ietf.org>; Rotem@core3.amsl.com <Rotem@core3.amsl.com>; HUANG@core3.amsl.com <HUANG@core3.amsl.com>; Feng F <Feng.f.Huang@alcatel-sbell.com.cn>; Cohen <Rotem.Cohen@ecitele.com>
Sent: Thu Feb 17 23:05:19 2011
Subject: Re: [PWE3] [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Greg, and all,
I concur with Greg.
Using GAL with PWs is highly problematic, and all the related issues (raised during the poll on accepting this draft as a WG item) have not, AFAIK, been resolved.

Regards,
     Sasha

________________________________
From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg Mirsky [gregimirsky@gmail.com]
Sent: Friday, February 18, 2011 8:47 AM
To: Luca Martini
Cc: mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HUANG Feng F
Subject: [mpls-tp] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

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