RE: [PWE3] PW Update and PW Redundancy

Hi Mark, Wim,

A "make before break" based on the pwe3-redundancy draft for CESoPSN would imply the following configurations at both endpoints:
- New AII or PWid (must be defined so as to get the highest priority)
- AC/"new PW" binding
- New int. Paramters to the "new PW"
The cumbersome configuration could be prone to mis-configuration and so possible service disruption.
Upon the switchover step as defined in pwe3-redundancy draft, the initial PW must be teared down. This is not required, so not specified in the PW redundancy procedure. 
Hence the initial PW removal must be achieved via CLI/knob (to be supported at the both endpoints).
Extending the PW redundancy for a dynamic update for CESoPSN on the fly without service interruption would lead to define also some specific extensions.
So,let's figure out the pros and cons of both approaches.
The PW Update draft proposes a real PW dynamic update since it allows to maintain the PW FEC and so alleviates the operational concerns.

Best regards,

Frederic

-----Message d'origine-----
De : HENDERICKX Wim [mailto:wim.henderickx@alcatel-lucent.be] 
Envoyé : mardi 4 décembre 2007 01:53
À : Mark Townsley; pwe3
Objet : RE: [PWE3] PW Update and PW Redundancy

Mark, I think this indeed a good alternative according to me. 

-----Original Message-----
From: Mark Townsley [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
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