RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Fri, 02 September 2011 05:10 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3D421F9294; Thu, 1 Sep 2011 22:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[AWL=1.005, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-OVIbb9cgdF; Thu, 1 Sep 2011 22:10:56 -0700 (PDT)
Received: from mail174.messagelabs.com (mail174.messagelabs.com [85.158.138.51]) by ietfa.amsl.com (Postfix) with SMTP id B8A0B21F920A; Thu, 1 Sep 2011 22:10:53 -0700 (PDT)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-2.tower-174.messagelabs.com!1314939937!29964760!4
X-Originating-IP: [147.234.242.234]
X-StarScan-Version: 6.3.6; banners=-,-,-
Received: (qmail 1856 invoked from network); 2 Sep 2011 05:05:48 -0000
Received: from ilptbmg01-out.ecitele.com (HELO ilptbmg01-out.ecitele.com) (147.234.242.234) by server-2.tower-174.messagelabs.com with SMTP; 2 Sep 2011 05:05:48 -0000
X-AuditID: 93eaf2e7-b7c4dae0000018d7-34-4e60642187d2
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id 2F.82.06359.124606E4; Fri, 2 Sep 2011 08:05:38 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Fri, 2 Sep 2011 08:05:47 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Fri, 02 Sep 2011 08:05:47 +0300
Subject: RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxozUQ02r1up0JKR8GfF1MoWEKo7gAXg5t5
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EF7BD46D@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com> <4E5CD1DF.90702@cisco.com>, <07F7D7DED63154409F13298786A2ADC903FABF6A@EXRAD5.ad.rad.co.il> <A3C5DF08D38B6049839A6F553B331C760111EF7BD46C@ILPTMAIL02.ecitele.com>, <4E5FC1E0.4050802@cisco.com>
In-Reply-To: <4E5FC1E0.4050802@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD46DILPTMAIL02e_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLsWRmVeSWpSXmKPExsUy+dWnL7pKKQl+Bp+nc1jM+DOR2eLZxvks Fs/v/GW3uLV0JatF+9qzLBZ9n7awWJx7OofR4kPXD1YHDo8pvzeyeixZ8pPJY9LaNI8vlz+z BbBENTDaJObl5ZcklqQqpKQWJ9sqBRRlliUmVyopZKbYKhkqKRTkJCan5qbmldgqJRYUpOal KNlxKWAAG6CyzDyF1Lzk/JTMvHRbJc9gf10LC1NLXUMlOzVlQ2NrrpCMzGKFVN3cxMwchdzU 4uLE9FQFoEjCFuaMaa0vmAr+eFR8XNXM1sB4366LkZNDQsBEYuKeWywQtpjEhXvr2UBsIYG9 jBIzF+t3MXIB2ZMZJfZ2nWIGSbAJ2EpsWn0XrEhEQFdi9oYbjCBFzAINTBLfb3aydzFycLAI qEic+poDUiMsECBxYP0yFoj6QIn1d3+wQthGEhumgpRzcvACxR9f3MgKsXgrq8Tem2C7OAU0 JX4c6WUCsRmBjvt+ag2YzSwgLnHryXwmiKMFJJbsOc8MYYtKvHz8jxWiXlTiTvt6Roj6fImm T0tYIXYJSpyc+QTqYUmJgytusExgFJuFZOwsJC2zkLRAxPUkbkydwgZha0ssW/iaGcLWlZjx 7xALsvgCRvZVjKKZOQUlSbnpBoZ6qcmZJak5qXrJ+bmbGCFJ7PkOxl/zVQ4xCnAwKvHwRqyL 9xNiTSwrrsw9xCjJwaQkyiudkOAnxJeUn1KZkVicEV9UmpNafIhRgoNZSYR3IgtQjjclsbIq tSgfJuUKDPyJzFLcyfnAxJxXEm9sYICboyTO+zT5ja+QQDowZWanphakFsHMkeHgUJLgNUkG WiFYlJqeWpGWmVOCkGbi4AQ5gwfojPMgNbzFBYm5xZnpEPlTjIpS4rybQBICIImM0jy4XlDm qv////8rRnGgp4V5L4BU8QCzHlz3K6DBTECD/2nHgwwG5hq4lFQDo9qniq1r1ueJyR1iP/rf Urfr/JWguCde6s8MFnisKmo69SlO+NNuw409n80nHxXQUrn2OTEwJ7b7fZNmwMejDy6GvbBw mqOv2SO413dWxE33y5NVV9ZKfJFN5vnUrfH/zcHTImq6B3YFRO6/sH31DLH3b2ZwB+4NCp9r f+Lmy1U7PUOuCOnstVJiKc5INNRiLipOBADbF8WRNwQAAA==
X-Mailman-Approved-At: Fri, 02 Sep 2011 08:35:37 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Luca Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2011 05:10:57 -0000

Stewart,
Lots of thanks for a prompt response.

My original email contained a typo (S-PE instead of T-PE  named as inserting ) which I've acknowledged and corrected in this thread (please see http://www.ietf.org/mail-archive/web/pwe3/current/msg12586.html).

With this correction in mind, the example I've presented (an MS-PW that originates in a T-PE in a MPLS-TP domain and them crosses - at S-PE - into an IP/MPLS domain) matches, IMHO, Yaakov's question. And if the operator wishes to improve traffic distribution in the IP/MPLS domain which employs ECMP, flow labels would be inserted by T-PE.

I believe that the change in draft-ietf-pwe3-gal-in-pw that you've proposed in http://www.ietf.org/mail-archive/web/pwe3/current/msg12613.html resolves the original issue I've raised of both GAL and flow label "competing" for the BoS position.

However, a conceptual question - can any MPLS-TP restrictions be placed on PWs?- remains open as noted in Greg's comment (please see http://www.ietf.org/mail-archive/web/pwe3/current/msg12620.html). IMHO and FWIW we should acknowledge the fact (implicitly recognized  already in RFC 5920) that there is simply no such thing as a MPLS-TP PW.

Hopefully this note clarifies my position on the subject.

Regards, and apologies for the original typo,
     Sasha

________________________________
From: Stewart Bryant [stbryant@cisco.com]
Sent: Thursday, September 01, 2011 8:33 PM
To: Alexander Vainshtein
Cc: Yaakov Stein; mpls@ietf.org; pwe3; iesg@ietf.org; pwe3-chairs@tools.ietf.org; Luca Martini; IETF Discussion
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw


On 01/09/2011 17:07, Alexander Vainshtein wrote:
Yaakov,
You've written
PW that starts in an MPLS-TP domain, can easily leak into a non-TP domain
This is exactly the point that I've raised in my IETF LC comment on the draft (for MS-PW) - please see my email (to several lists) that explains that in some detail, at http://www.ietf.org/mail-archive/web/pwe3/current/msg12581.html.

Regards,
Sasha

The operator intends to improve traffic distribution in the IP/MPLS domain, hence he enables insertion and discard of "flow labels" at the two S-PEs.

Speaking as an author of the FAT-PW draft I do not recall any text that proposes that S-PEs insert FLs in the stack, and it never occurred to me that anyone anyone would try, since would require a change to the design of the S-PEs.

Stewart




This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.