Re: [PWE3] CW usage in opposite directions for static PWs
Yaakov Stein <yaakov_s@rad.com> Wed, 11 April 2012 07:51 UTC
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E08621F86D3 for <pwe3@ietfa.amsl.com>; Wed, 11 Apr 2012 00:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level:
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
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 Ee3yFjoglte1 for <pwe3@ietfa.amsl.com>; Wed, 11 Apr 2012 00:51:08 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4A821F86D5 for <pwe3@ietf.org>; Wed, 11 Apr 2012 00:51:05 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 11 Apr 2012 10:39:09 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Wed, 11 Apr 2012 10:51:00 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "Andrew G. Malis" <amalis@gmail.com>
Thread-Topic: [PWE3] CW usage in opposite directions for static PWs
Thread-Index: AQHNFiDmR8k+8boiWEyuusmNJqhMmZaTrS8Q///VpYCAADKjoIAASrsAgAAJogCAAAGBgIABNpqg
Date: Wed, 11 Apr 2012 07:50:59 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90436DBCA@EXRAD5.ad.rad.co.il>
References: <07F7D7DED63154409F13298786A2ADC90436C45A@EXRAD5.ad.rad.co.il> <OF7402C519.F08A3B41-ON482579DC.00544743-482579DC.005587A6@zte.com.cn> <CAK+d4xvRzHFEUGd+K9cSnNJZuGc=jF7pjmryu1GmeDMLJ1XNsg@mail.gmail.com> <4F845C49.1070900@cisco.com>
In-Reply-To: <4F845C49.1070900@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A02020B.4F8537E5.002A,ss=1,fgs=0
Cc: Lizhong Jin <lizhong.jin@zte.com.cn>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] CW usage in opposite directions for static PWs
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 07:51:10 -0000
Stewart Of course the PWE3 control protocol is clear in enforcing the use of non-use in both directions. Even there, I do not recall debate on the subject. It was "yeah, I guess that's OK". In my slide deck a few years back I discussed the state of affairs for other methods of setting up PWs I am OK with a decision to enforce the symmetry, but we need to discuss this and agree on it. And perhaps there are other parameters that need similar discussion. For example, can I set up a TDM PW with an E1 in one direction and a T1 in the other ? What about a raw Ethernet PW in one direction and a tagged one in the opposite direction ? If this is a general principle (as I suspect many people believe, but I don't recall was ever explicitly stated) then this should be written up (and the implications considered). Y(J)S -----Original Message----- From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Stewart Bryant Sent: Tuesday, April 10, 2012 19:14 To: Andrew G. Malis Cc: Lizhong Jin; pwe3@ietf.org; Yaakov Stein Subject: Re: [PWE3] CW usage in opposite directions for static PWs On 10/04/2012 17:08, Andrew G. Malis wrote: > All, > > This has been an extremely useful discussion. > > <wg chair hat off> > > Personally, I don't really see much utility in asymmetric CWs in a PW. > > <wg chair hat on> > > Once the WG comes to consensus on the issue one way or the other (and > I would like to hear some more opinions), we should consider document > revisions as necessary to make sure that the consensus is clearly > reflected in the RFCs. > > Cheers, > Andy For LDP signaled PWs, I don't think there is any ambiguity, the CW handling is symmetric. Does anyone read it any other way? Stewart _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3
- Re: [PWE3] CW usage in opposite directions for st… Lizhong Jin
- [PWE3] CW usage in opposite directions for static… Yaakov Stein
- Re: [PWE3] CW usage in opposite directions for st… David Sinicrope
- Re: [PWE3] CW usage in opposite directions for st… Yaakov Stein
- Re: [PWE3] CW usage in opposite directions for st… Lizhong Jin
- Re: [PWE3] CW usage in opposite directions for st… Yaakov Stein
- Re: [PWE3] CW usage in opposite directions for st… Alexander Vainshtein
- Re: [PWE3] CW usage in opposite directions for st… Yaakov Stein
- Re: [PWE3] CW usage in opposite directions for st… Lizhong Jin
- Re: [PWE3] CW usage in opposite directions for st… Andrew G. Malis
- Re: [PWE3] CW usage in opposite directions for st… Stewart Bryant
- Re: [PWE3] CW usage in opposite directions for st… Alexander Vainshtein
- Re: [PWE3] CW usage in opposite directions for st… Yaakov Stein
- Re: [PWE3] CW usage in opposite directions for st… Stewart Bryant
- Re: [PWE3] CW usage in opposite directions for st… Yaakov Stein