Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01
"Reshad Rahman (rrahman)" <rrahman@cisco.com> Wed, 24 November 2010 12:12 UTC
Return-Path: <rrahman@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 313AC28C193 for <pwe3@core3.amsl.com>; Wed, 24 Nov 2010 04:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[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 iJYKwe2-x2TK for <pwe3@core3.amsl.com>; Wed, 24 Nov 2010 04:12:01 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 500523A692A for <pwe3@ietf.org>; Wed, 24 Nov 2010 04:12:01 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnYHAN+P7EytJXG8/2dsb2JhbACCApIthjcBiA1xojybO4VHBIRbiRo
X-IronPort-AV: E=Sophos; i="4.59,247,1288569600"; d="scan'208,217"; a="185708548"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rtp-iport-2.cisco.com with ESMTP; 24 Nov 2010 12:13:00 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id oAOCCxjw015605; Wed, 24 Nov 2010 12:12:59 GMT
Received: from xmb-rcd-204.cisco.com ([72.163.62.211]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 24 Nov 2010 06:13:00 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB8BD0.EF8A0BDE"
Date: Wed, 24 Nov 2010 06:12:59 -0600
Message-ID: <654701C60BCC7C4EBD533B89D72BDFEA02F1715E@XMB-RCD-204.cisco.com>
In-Reply-To: <XFE-SJC-2213HvoFOAm00000067@xfe-sjc-221.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] draft-jin-pwe3-cbit-negotiation-01
Thread-Index: AcuKzM/A6x/A0HudQ2y5RIFssxvwXwBA+y0w
References: <SNT123-W7AA37A5B0DB04562D20CFF43A0@phx.gbl> <XFE-SJC-2213HvoFOAm00000067@xfe-sjc-221.amer.cisco.com>
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "Sami Boutros (sboutros)" <sboutros@cisco.com>, Raymond Key <raymond.key@ieee.org>, pwe3@ietf.org
X-OriginalArrivalTime: 24 Nov 2010 12:13:00.0341 (UTC) FILETIME=[EFD5B650:01CB8BD0]
Cc: thomas.nadeau@huawei.com, lizhong.jin@zte.com.cn, vishwas@ipinfusion.com
Subject: Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 24 Nov 2010 12:12:04 -0000
I agree with Sami. Maybe the other options should be in appendix with an explanation of why they were not chosen? Regards, Reshad. From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Sami Boutros (sboutros) Sent: Tuesday, November 23, 2010 12:11 AM To: Raymond Key; pwe3@ietf.org Cc: thomas.nadeau@huawei.com; lizhong.jin@zte.com.cn; vishwas@ipinfusion.com Subject: Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 I personally like option 1 in this draft, describing how to re-enable control word via dynamic LDP signaling. However, you would need to clarify the steps more.. saying in step 3 that PE2 MUST send a label request and in step 5 that PE1 MUST respond to the label request with the configured CW setting on PE1 which was set, as well in step 6 PE2 MUST wait for PE1 label binding before sending it's label binding with CW set. As well, it may be good extending the flow chart described in appendix A in rfc 4447 with option 1. Not sure, if it is worth mentioning the other options since they have issues. Option 2, how will we be able to re-enable CW? isn't that the issue we are trying to fix? Option 3, This is avoiding to solve the problem. Option 4, I don't think this will fly. Thanks, Sami At 01:53 AM 11/19/2010, Raymond Key wrote: Hi PWE3 working group, In the recent IETF79, we have presented the draft "Pseudowire Control Word Negotiation Mechanism Analysis and Update" http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-01 This draft describes the problem of control word negotiation mechanism specified in RFC4447. Based on the problem analysis, possible solutions and their potential shortcomings are also discussed. The authors would like to have more feedback from the mailing list before working on the next version. Grateful if you could review the document and post comments on the mailing list. Thanks, Raymond Key _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3
- [PWE3] draft-jin-pwe3-cbit-negotiation-01 Raymond Key
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 Sami Boutros
- [PWE3] draft-boutros-pwe3-mpls-tp-ms-pw-00 Sami Boutros
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 Reshad Rahman (rrahman)
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 lizhong.jin
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 Reshad Rahman (rrahman)
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 Ed
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 lizhong.jin
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 venkatesan mahalingam
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 Spike Curtis
- Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01 lizhong.jin
- [PWE3] draft-boutros-pwe3-mpls-tp-mac-wd-01 Sami Boutros
- [PWE3] draft-boutros-pwe3-mpls-tp-mac-wd-01 Sami Boutros