IETF Logo Mail Archive

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

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Mon, 28 June 2010 12:56 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 37AFB3A6A2E; Mon, 28 Jun 2010 05:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 ZH18hXuXAxK6; Mon, 28 Jun 2010 05:56:06 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id A14A33A6A37; Mon, 28 Jun 2010 05:56:05 -0700 (PDT)
X-AuditID: 93eaf2e7-b7cc1ae000004fcf-73-4c28980a87a4
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 8E.B4.20431.A08982C4; Mon, 28 Jun 2010 15:39:38 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Mon, 28 Jun 2010 15:56:14 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Mon, 28 Jun 2010 15:56:25 +0300
Thread-Topic: [PWE3] Pseudo-wires: uni-directional o bi-directional?
Thread-Index: AcsWv+zYE2mJpedXQ/2JEvsCz2FbsgAADm1A
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D37F4FB631@ILPTMAIL02.ecitele.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>
In-Reply-To: <4C289993.6070507@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_A3C5DF08D38B6049839A6F553B331C76D37F4FB631ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
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 12:56:10 -0000

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

v2.8.7 | Report a Bug | By Email