Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directional o bi-directional?
Stewart Bryant <stbryant@cisco.com> Mon, 28 June 2010 16:25 UTC
Return-Path: <stbryant@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 799C728B797; Mon, 28 Jun 2010 09:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.914
X-Spam-Level:
X-Spam-Status: No, score=-9.914 tagged_above=-999 required=5 tests=[AWL=0.684,
BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 bdVq4WH9Ix9C;
Mon, 28 Jun 2010 09:25:57 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
by core3.amsl.com (Postfix) with ESMTP id 37AF63A68CE;
Mon, 28 Jun 2010 09:25:57 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com;
dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFALppKExAZnwN/2dsb2JhbACBQ51tcaZXgXkLAZgLhSQE
X-IronPort-AV: E=Sophos; i="4.53,498,1272844800"; d="scan'208,217";
a="126427796"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com
with ESMTP; 28 Jun 2010 16:26:06 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by
rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5SGQ5F7027340;
Mon, 28 Jun 2010 16:26:06 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-9.cisco.com (localhost
[127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o5SGQ4609922;
Mon, 28 Jun 2010 17:26:04 +0100 (BST)
Message-ID: <4C28CD1B.8080907@cisco.com>
Date: Mon, 28 Jun 2010 17:26:03 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.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>
In-Reply-To: <AANLkTikkr-RtYhacCn_40qAut5ylYJETA2O1la_ygMlK@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------070307090706080206000708"
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
Reply-To: stbryant@cisco.com
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:25:59 -0000
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 > <mailto: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> > [mailto: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 <mailto: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 <mailto: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
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… Alexander Vainshtein
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… Greg Mirsky
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… Stewart Bryant
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… Greg Mirsky
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… venkatesan mahalingam
- Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directiona… Greg Mirsky