IETF Logo Mail Archive

RE: [PWE3] PW Update and PW Redundancy

"JOUNAY Frederic RD-RESA-LAN" <frederic.jounay@orange-ftgroup.com> Tue, 04 December 2007 02:53 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 1IzNuc-0002ve-H8; Mon, 03 Dec 2007 21:53:30 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1IzNub-0002sb-8G for pwe3-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 21:53:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzNua-0002sE-UV for pwe3@ietf.org; Mon, 03 Dec 2007 21:53:28 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzNuZ-000297-8p for pwe3@ietf.org; Mon, 03 Dec 2007 21:53:28 -0500
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Dec 2007 03:52:37 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] PW Update and PW Redundancy
Date: Tue, 04 Dec 2007 03:52:33 +0100
Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A0FD07010@ftrdmel2>
In-Reply-To: <7FA0C743C38E5340BFC2873488FA1E8ED61D7C@emailcorp3.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] PW Update and PW Redundancy
Thread-Index: Acg2DxvtjJFk345JTNelt6XmVbzHbwAAU9iQAAQEeTA=
References: <4754A34E.5020603@cisco.com> <7FA0C743C38E5340BFC2873488FA1E8ED61D7C@emailcorp3.jnpr.net>
From: JOUNAY Frederic RD-RESA-LAN <frederic.jounay@orange-ftgroup.com>
To: Nitin Bahadur <nitinb@juniper.net>, Mark Townsley <townsley@cisco.com>, pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 04 Dec 2007 02:52:37.0397 (UTC) FILETIME=[BA631C50:01C83620]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

Using another PW would imply to configure a new AII or a new Pwid, and this is actually what we want to avoid for manageability considerations.

Fred 

-----Message d'origine-----
De : Nitin Bahadur [mailto:nitinb@juniper.net] 
Envoyé : mardi 4 décembre 2007 02:00
À : Mark Townsley; pwe3
Objet : RE: [PWE3] PW Update and PW Redundancy


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


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

v2.23.0 | Report a Bug | By Email