Re: [PWE3] draft-jin-pwe3-cbit-negotiation-01

Ed <maillist.ed@gmail.com> Thu, 25 November 2010 00:46 UTC

Return-Path: <maillist.ed@gmail.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 70D1028C15C for <pwe3@core3.amsl.com>; Wed, 24 Nov 2010 16:46:34 -0800 (PST)
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 6dW2NLMZPQfW for <pwe3@core3.amsl.com>; Wed, 24 Nov 2010 16:46:32 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 74F423A69C3 for <pwe3@ietf.org>; Wed, 24 Nov 2010 16:46:32 -0800 (PST)
Received: by wwa36 with SMTP id 36so333017wwa.13 for <pwe3@ietf.org>; Wed, 24 Nov 2010 16:47:32 -0800 (PST)
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=xIOvH0Flo0+XZGkVrkuMexIvYXIUT8RlzI3CmoONWMI=; b=FAAZngBRJ3AIFKUSaABIASHvWU7AGRDrXQujw6gJYatIFTqJuG6b3f0mkynY++JhjM gVDtZmivlGovzFzHupXPFblAW7IDdJM3cDUosEgB1ZYVxrkE8iUPmmNyNkOrvZo3Tm4C BsEjtzP789/Zwg3/KxDy7efEm/dO6m1e+HFP4=
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=RAggunDjUmjKJbm6TX7vmtIwQDb+sGMA7naETGMS8KEgsF9KBHezggk60gz8RvpUsP vp1NDrP0RKbCd6T5ObtF1ebOsMRhvWHiYGS4rspI4RMR2LJGueOhf4UQL76vNqvRiqbd KYgEAabx4XeM1IRGxItHiUcN5ITCty/FaW7F4=
MIME-Version: 1.0
Received: by 10.227.141.78 with SMTP id l14mr97702wbu.15.1290646051034; Wed, 24 Nov 2010 16:47:31 -0800 (PST)
Received: by 10.227.137.131 with HTTP; Wed, 24 Nov 2010 16:47:30 -0800 (PST)
In-Reply-To: <654701C60BCC7C4EBD533B89D72BDFEA02F1715E@XMB-RCD-204.cisco.com>
References: <SNT123-W7AA37A5B0DB04562D20CFF43A0@phx.gbl> <XFE-SJC-2213HvoFOAm00000067@xfe-sjc-221.amer.cisco.com> <654701C60BCC7C4EBD533B89D72BDFEA02F1715E@XMB-RCD-204.cisco.com>
Date: Thu, 25 Nov 2010 11:47:30 +1100
Message-ID: <AANLkTim6e==d_P2suW14YRtTDM-9H_Zu_oWjd03oRASe@mail.gmail.com>
From: Ed <maillist.ed@gmail.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
Content-Type: multipart/alternative; boundary="0016e65b584067161d0495d5f3e4"
Cc: vishwas@ipinfusion.com, lizhong.jin@zte.com.cn, pwe3@ietf.org, thomas.nadeau@huawei.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: Thu, 25 Nov 2010 00:46:34 -0000

Hi Raymond,

Option 1 seems to be simply to resignal the FEC - with the corresponding
traffic forwarding impact. Can PE2 send a new label mapping with cbit=1 be
sent without requiring label withdrawal message and label request message,
for example?

Also, does the the changing of the control word from PREFERRED to
non-PREFERRED need to be considered as well?

Thanks

Regards,
Edward


On Wed, Nov 24, 2010 at 11:12 PM, Reshad Rahman (rrahman) <rrahman@cisco.com
> wrote:

>  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 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>