Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directional o bi-directional?

Greg Mirsky <gregimirsky@gmail.com> Mon, 28 June 2010 16:50 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 0796C3A6843; Mon, 28 Jun 2010 09:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level:
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[AWL=0.291, 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 gnN0nYHiLJvk; Mon, 28 Jun 2010 09:50:50 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 780C33A68F3; Mon, 28 Jun 2010 09:50:49 -0700 (PDT)
Received: by vws7 with SMTP id 7so1721015vws.31 for <multiple recipients>; Mon, 28 Jun 2010 09:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mFXV9lK1AH/DoYhO6j0xrncNpu/q/AGa1ZBpKNWx+Us=; b=VEeiZD6/okTZ9nnQApH6K4a4oidC1Dp+koHKjQxnBkqVLKVXbXPXNw93qz2nQdWT4Q eI5jOPwMnyqPJknR7IP58TiuDbpPAJyqoHDY/8am+l/SLxHs//QUfry0W9pXojpJKtOk f9jwfKYglc6Es3Cw4PV9oBuEZg/6MG7eVAc/U=
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=xooBge7Unjj8OWY842LeU6Iffq7i44awnQQXH3lwUhJ1+RV2L1VXmrqmuO/VfGeeTl 6GGTkod5YmERqzAL3p9/k5rxlisJKt0KqUbHq+o+BZkVYd8tYiCN2z2EtPn4VeO8egLs +vzTWetlg2m9MwTbC+VOgD6Oiy6j3FaYRCyT0=
MIME-Version: 1.0
Received: by 10.220.168.10 with SMTP id s10mr1337088vcy.50.1277743856592; Mon, 28 Jun 2010 09:50:56 -0700 (PDT)
Received: by 10.220.171.147 with HTTP; Mon, 28 Jun 2010 09:50:56 -0700 (PDT)
In-Reply-To: <4C28CD1B.8080907@cisco.com>
References: <4C1B9561.1090001@trajano.us.es> <48E7911F78327A449A9FB956376672868206FF34@exrad4.ad.rad.co.il> <4C279AFB.9090005@trajano.us.es> <A3C5DF08D38B6049839A6F553B331C76D37F026BB4@ILPTMAIL02.ecitele.com> <4C289993.6070507@cisco.com> <A3C5DF08D38B6049839A6F553B331C76D37F4FB631@ILPTMAIL02.ecitele.com> <AANLkTikkr-RtYhacCn_40qAut5ylYJETA2O1la_ygMlK@mail.gmail.com> <4C28CD1B.8080907@cisco.com>
Date: Mon, 28 Jun 2010 12:50:56 -0400
Message-ID: <AANLkTilH0FwZjD7ZotqRf3j85sg0cNX6UhARcJe7IzaF@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=0016364eecceafa99a048a19ec0f
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directional o bi-directional?
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: Mon, 28 Jun 2010 16:50:52 -0000

Dear Stewart,
perhaps I'm applying section/segment terminology to PW without sufficient
explanation of my view. After reading comments by you and Sasha I've looked
at SS-PW as a bi-directional link or section. If such presentation of SS-PW
is valid then it's co-routedness, as you've noted, is obvious. I agree that
SS-PW can be referred as segment as well but then its co-routedness is not
self-evident. Interestingly, from the view of SS-PW as a bi-directional
link/section directly follows bi-directional co-routed essence of MS-PW.

Regards,
Greg

On Mon, Jun 28, 2010 at 12:26 PM, Stewart Bryant <stbryant@cisco.com> wrote:

>  Greg
>
> I do not understand your point.
>
> MS-PW S-PEs serve a purpose in breaking the PW into segments. If you do not
> need that decomposition in a network, there is nothing requiring their use.
> However we should not prohibit their use either, as there are scenarios
> whether this decomposition is of benefit.
>
> If you need an existence proof of this point, remember that we initially
> designed SS-PW and needed to create MS-PW to address requirements of network
> operators that has deployed SS-PW.
>
> Stewart
>
>
>
>
>
>
> On 28/06/2010 15:01, Greg Mirsky wrote:
>
> Dear Sasha,
> I too find Stewart's explanation very useful for overall MPLS-TP. And in
> this perspective perhaps the SS PW might be also referred as PW section.
>
> Regards,
> Greg
>
> On Mon, Jun 28, 2010 at 8:56 AM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com> wrote:
>
>>  Stewart,
>>
>> Lots of thanks for a prompt and unambiguous response..
>>
>> This issues looks like one more fine point of MPLS-TP-ese to me: Does
>> “co-routed” mean “co-routed in the immediate lower layer” or “co-routed in
>> all the underlying layers down to the duct”?
>>
>> FWIW, I tend to agree with your interpretation: “co-routed” means
>> “co-routed in the immediate lower layer”, and hence PWs (both single-segment
>> and multi-segment) are co-routed bi-directional LSPs.
>>
>>
>>
>> Regards,
>>
>>      Sasha
>>
>>
>>
>> *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf
>> Of *Stewart Bryant
>> *Sent:* Monday, June 28, 2010 3:46 PM
>> *To:* pwe3@ietf.org
>>
>> *Subject:* Re: [PWE3] Pseudo-wires: uni-directional o bi-directional?
>>
>>
>>
>>
>>
>>    It seems to me that PWs are associated bi-directional LSPs...
>>
>>
>>
>> PWs are co-routed bi-directional since it is required that they go through
>> the same xPEs in each direction, and the xPEs knows about the association of
>> the two directional components.
>>
>> Whether they run over co-routed bi-directional, or associated
>> bi-directional LSP is a deployment/applicability issue.
>>
>> - Stewart
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>>
>
>
> --
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>