RE: [PWE3] BFD for MPLS PWs

+Yaakov and all,
I'd say that an *implicit* OAM requirement for "static" (or manually provisioned) PWs is to provide
some equivalent of the functionality that can be achieved for PWs provisioned using the PWE3  setup 
and maintenance propocol (RFC 4448) by some alternative means. For obvious reasons this cannot be
a full equivalent.

IMHO the best way to arrive to explicit specifications woyld be via the PWE3 OAM Message Mapping draft 
(http://www.ietf.org/internet-drafts/draft-ietf-pwe3-oam-msg-map-04.txt) It could be easily augmented
by explicitly specifying which defects, propagation functions and methods are applicable to manually
provisioned PWs.

And, of course, TDM PWs use their own techniques.

Regards,
                     Sasha

> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Monday, August 07, 2006 10:56 AM
> To: Rahul Aggarwal; Thomas D. Nadeau
> Cc: pwe3 WG ((((E-mail)))); Mustapha Aissaoui; Sasha Vainshtein
> Subject: RE: [PWE3] BFD for MPLS PWs
> 
> 
>  
> 
> Can you please point me to:
>  a) Definition of a static PW ?
> 
> [YJS]  Section 7.1 of RFC 3985 states:
> 
>    Setup or teardown of a PW can be triggered by an operator command,
>    from the management plane of a PE, by signaling set-up or 
> teardown of
>    an AC (e.g., an ATM SVC), or by an auto-discovery mechanism.
>    ...
>    Manual configuration of PWs can be considered a special kind of
>    signaling and is allowed.
> 
> b) Requirements for a static PW ?
> 
> [YJS] Same as requirements for any other PW.
> 
> c) Specifically OAM requirements of a static PW ?
> 
> [YJS] Same as requirements for any other PW.
> 
> d) Definition of a "manually" established PSN ?
> 
> [YJS] see above excerpt from RFC 3985
> 
> e) Requirements for a manually established PSN...
> 
> [YJS] I didn't hear anyone talking about manually establishing a PSN.
> 
> 
> 

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