RE: [PWE3] PW Update and PW Redundancy

"Nitin Bahadur" <nitinb@juniper.net> Tue, 04 December 2007 01:03 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 1IzMCA-0008M4-Jd; Mon, 03 Dec 2007 20:03:30 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1IzMC9-0008Lv-OX for pwe3-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 20:03:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzMC9-0008Lj-Ew for pwe3@ietf.org; Mon, 03 Dec 2007 20:03:29 -0500
Received: from exprod7og111.obsmtp.com ([64.18.2.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzMC7-0008TV-Uz for pwe3@ietf.org; Mon, 03 Dec 2007 20:03:29 -0500
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP; Mon, 03 Dec 2007 17:03:23 PST
Received: from emailcorp1.jnpr.net ([66.129.254.11]) by gamma.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Dec 2007 17:02:29 -0800
Received: from emailcorp3.jnpr.net ([66.129.254.13]) by emailcorp1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Dec 2007 17:02:05 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] PW Update and PW Redundancy
Date: Mon, 03 Dec 2007 16:59:56 -0800
Message-ID: <7FA0C743C38E5340BFC2873488FA1E8ED61D7C@emailcorp3.jnpr.net>
In-Reply-To: <4754A34E.5020603@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] PW Update and PW Redundancy
Thread-Index: Acg2DxvtjJFk345JTNelt6XmVbzHbwAAU9iQ
From: Nitin Bahadur <nitinb@juniper.net>
To: Mark Townsley <townsley@cisco.com>, pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 04 Dec 2007 01:02:05.0361 (UTC) FILETIME=[4962BA10:01C83611]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc:
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

Not sure if you even need that (since both PWs start from the same PE).
The 2nd PW can be setup in the control plane and the control-plane can
do a make-before-break in the forwarding plane.

Nitin

> -----Original Message-----
> From: Mark Townsley [mailto:townsley@cisco.com]
> Sent: Monday, December 03, 2007 4:46 PM
> 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
> https://www1.ietf.org/mailman/listinfo/pwe3


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