[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PWE3] PW Update and PW Redundancy
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 at 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 at 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 at ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3 at ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3 at ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3