[PWE3] PW Update and PW Redundancy

Mark Townsley <townsley@cisco.com> Tue, 04 December 2007 00:46 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 1IzLvc-0007Z3-Ul; Mon, 03 Dec 2007 19:46:24 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1IzLva-0007US-QP for pwe3-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 19:46:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzLva-0007Ro-Ec for pwe3@ietf.org; Mon, 03 Dec 2007 19:46:22 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzLva-0006hK-5m for pwe3@ietf.org; Mon, 03 Dec 2007 19:46:22 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 03 Dec 2007 16:46:21 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lB40kLvY005257 for <pwe3@ietf.org>; Mon, 3 Dec 2007 16:46:21 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lB40kLqj015906 for <pwe3@ietf.org>; Tue, 4 Dec 2007 00:46:21 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Dec 2007 16:46:07 -0800
Received: from dhcp-11d2.ietf70.org ([10.21.115.13]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Dec 2007 16:46:07 -0800
Message-ID: <4754A34E.5020603@cisco.com>
Date: Mon, 03 Dec 2007 16:46:06 -0800
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2007 00:46:07.0486 (UTC) FILETIME=[0E7299E0:01C8360F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=187; t=1196729181; x=1197593181; c=relaxed/simple; s=sjdkim2002; 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:=20PW=20Update=20and=20PW=20Redundancy |Sender:=20; bh=aXdvVsNxg4LB/ftDx+USJt1LzPQuDYSP58XLUw+w+Xc=; b=hTVI9UTGN2oKVkCA4Y40Id2s+8kLJYEbWf9i/XSw1fFeat8i4QaUdj4Zllf4UcWbIeURsWsT LMMVDxWytBUlmP0Y3d/WiPL6tKTDzcmRHL5E686JNPNswIWQhDyZRCet;
Authentication-Results: sj-dkim-2; header.From=townsley@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [PWE3] PW Update and PW Redundancy
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

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
https://www1.ietf.org/mailman/listinfo/pwe3