Re: [mpls-tp] [PWE3] Pseudo-wires: uni-directional o bi-directional?
Greg Mirsky <gregimirsky@gmail.com> Mon, 28 June 2010 14:01 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 E44533A67B5; Mon, 28 Jun 2010 07:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.278
X-Spam-Level:
X-Spam-Status: No, score=-2.278 tagged_above=-999 required=5 tests=[AWL=0.320,
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 YcDBvTTCXiK7;
Mon, 28 Jun 2010 07:01:10 -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 976313A688F;
Mon, 28 Jun 2010 07:01:09 -0700 (PDT)
Received: by vws7 with SMTP id 7so1543480vws.31 for <multiple recipients>;
Mon, 28 Jun 2010 07:01:16 -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=uBH7kvkC4xi7FetEz0C0LAfw3/WQ6CD7/hrmDCtfQEo=;
b=rdGyU7QBvS65m9vOilJ6f/3mfHMwP93TreNniTyEHeL9SqS2ULtAWC//7WqSwwTxUj
hC3bgF5PeLfDLS89Z5th4bEICg/UQBg8pPKfAn8KZiF5rREFYWt2IEenLWbkgxftO1oa
2zUeM1S9d/13xnHDGhNynMsI/PIo6oTIzVzrk=
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=PQcdV6CmiTj+V816vOZ27f/oyIfWUxzbOz+sefjW1bc2RoXexZjQp9YinMBNPW8NQL
n2jbhj1XH8FZDs5NMVKB1VeaMTQd45AznxsVfvOjAQG+D2bRoRzHemN9IDEgQBO7j9Fm
W5YqRpxgfsUIr6t4zM4uQUKTwLy35QayiotJk=
MIME-Version: 1.0
Received: by 10.220.169.14 with SMTP id w14mr2342079vcy.17.1277733676170;
Mon, 28 Jun 2010 07:01:16 -0700 (PDT)
Received: by 10.220.171.147 with HTTP; Mon, 28 Jun 2010 07:01:15 -0700 (PDT)
In-Reply-To: <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>
<A3C5DF08D38B6049839A6F553B331C76D37F4FB631@ILPTMAIL02.ecitele.com>
Date: Mon, 28 Jun 2010 10:01:15 -0400
Message-ID: <AANLkTikkr-RtYhacCn_40qAut5ylYJETA2O1la_ygMlK@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=0016e646a456e2bf8f048a178d9d
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@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 14:01:11 -0000
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 > >
- 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