Re: [PWE3] Charter Modification

[Luca Martini <lmartini at cisco.com>]

Danny,

There are quite a few very open statements in the charter additions.
I believe that things should be a bit more specific , or you will end up 
in endless arguments on which WG should be doing the work...

I have a few specific comments :

....cut
> Define requirements for and mechanisms to provide
> protection and restoration of PWs.
>
>   
This seems a bit too general. Today the PW architecture relies on the
PSN to provide all these functions.
Here is a suggestion for a better wording:

Define requirements for and mechanisms to provide protection and
restoration of Pseudowire PE end points.


Note that this includes SS-PW and MS-PWs. All we are dealing with in the
PWE3 WG is the PW end points, not the middle transit PSN.

> Publish document outlining PW-specific congestion avoidance
> and response guidelines.
>
> Publish document outlining PW-specific security considerations.
>
>   
The WG has put a significant effort into including a security
consideration in each of the published RFCs.
I do not believe that the line above is needed at all. Security
considerations should still be kept in the corresponding documents...
Is this meant to initiate some new work ?  If this is the case it is not 
clear.


> Publish specification for enabling P2MP PWs.
>   

No requirements for P2MP ?
The only thing that PWE3 can add to this topic is sharing multiple p2MP 
trees  for multiple PWs...
Everything else should be in MPLS....
This should be made clear.


> Publish requirements and specification for PW load-balancing
> mechanisms.
>
I believe that given the current controversy on how uselful some might 
or might not be, I would like the above line to say :

Publish requirements aplicability statements, and specification for PW 
load-balancing mechanisms.


> Publish requirements and specification for enhanced OAM.

I believe that this should be incorporated in the MPLS-TP change , and 
not here.

>
> Publish requirements and specifications to provide the
> necessary extensions to PWs to support the applications
> of MPLS to transport networks.
>
> In cooperation with the MPLS and CCAMP working groups,
> define extensions necessary to fulfill an MPLS transport
> profile.
>
>

> _______________________________________________
> pwe3 mailing list
> pwe3 at ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>   


_______________________________________________
pwe3 mailing list
pwe3 at ietf.org
https://www.ietf.org/mailman/listinfo/pwe3