IETF Logo Mail Archive

Re: [PWE3] PW Update and PW Redundancy

Mark Townsley <townsley@cisco.com> Wed, 05 December 2007 22:20 UTC

Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J02bb-0005k7-1B; Wed, 05 Dec 2007 17:20:35 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1J02ba-0005ht-8d for pwe3-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 17:20:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J02bZ-0005hj-VC for pwe3@ietf.org; Wed, 05 Dec 2007 17:20:33 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J02bY-0001rj-IA for pwe3@ietf.org; Wed, 05 Dec 2007 17:20:33 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 05 Dec 2007 14:20:33 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lB5MKVMl026934; Wed, 5 Dec 2007 14:20:31 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lB5MKSqh000325; Wed, 5 Dec 2007 22:20:30 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 14:20:28 -0800
Received: from dhcp-11d2.ietf70.org ([10.21.125.92]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 14:20:28 -0800
Message-ID: <4757242A.1060803@cisco.com>
Date: Wed, 05 Dec 2007 14:20:26 -0800
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Yang Yang <HealthingHearts@ieee.org>
Subject: Re: [PWE3] PW Update and PW Redundancy
References: <4754A34E.5020603@cisco.com> <208680DE650EAB4EB4248FE666AD8E3698D72B@FRVELSMBS22.ad2.ad.alcatel.com> <d119ea40712051102m87a996fiae6724e8d0df900d@mail.gmail.com>
In-Reply-To: <d119ea40712051102m87a996fiae6724e8d0df900d@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Dec 2007 22:20:28.0145 (UTC) FILETIME=[0A387E10:01C8378D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1510; t=1196893232; x=1197757232; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=townsley@cisco.com; z=From:=20Mark=20Townsley=20<townsley@cisco.com> |Subject:=20Re=3A=20[PWE3]=20PW=20Update=20and=20PW=20Redundancy |Sender:=20; bh=Of3qayfEzPqDDzyQNrxclEa8DxL+0JZ9ACpHzvjqmSo=; b=iLy8Rg+7rZ2Jx17NTtNq6Gp12mZLFJUUDhOWR4PRZuAi54ciR08x4FXUaf+yncw/iOBOPKcA HBWYMOMzG0OV/K/Mtej6hHU1Y06GCIHLcYXKNmVy7wcFJcC1nyUGJI2V;
Authentication-Results: sj-dkim-4; header.From=townsley@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: pwe3 <pwe3@ietf.org>, HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Yang Yang wrote:
>  Hello all,
>    The bandwidth of the underlying tunnel may not be bigger enough to 
> set up a redundant PW.  In this case, it may be good to only update 
> the traffic profile of the PW.
This doesn't make much sense - A redundant PW doesn't use any bandwidth 
until the old PW is torn down.

- Mark
>  
>     Best Regards!
>        Yang
>
> On Dec 4, 2007 8:53 AM, HENDERICKX Wim 
> <wim.henderickx@alcatel-lucent.be 
> <mailto:wim.henderickx@alcatel-lucent.be>> wrote:
>
>     Mark, I think this indeed a good alternative according to me.
>
>     -----Original Message-----
>     From: Mark Townsley [mailto:townsley@cisco.com
>     <mailto:townsley@cisco.com>]
>     Sent: dinsdag 4 december 2007 1:46
>     To: pwe3
>     Subject: [PWE3] PW Update and PW Redundancy
>
>
>     If PW Update is a "make before break" model, why not just setup a
>     redundant PW ala                    
>     draft-muley-pwe3-redundancy-00.txt
>     and then kill the old PW after?
>
>     - Mark
>
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www1.ietf.org/mailman/listinfo/pwe3
>     <https://www1.ietf.org/mailman/listinfo/pwe3>
>
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www1.ietf.org/mailman/listinfo/pwe3
>     <https://www1.ietf.org/mailman/listinfo/pwe3>
>
>


_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3

v2.23.0 | Report a Bug | By Email