Re: [mpls] MPLS wg charter update

Hi Loa,

Please find two very small questions/comments inline.

Thumb typed by Carlos Pignataro.
Excuze typofraphicak errows

On May 11, 2013, at 4:43 AM, "Loa Andersson" <loa@pi.nu> wrote:

> Working Group,
> 
> The working group chairs have discussed an MPLS wg charter update
> for sometime.
> 
> We have converged on the text below and while we understand that
> it still not "perfect" (for some value of perfect) we believe that
> it is good enough to serve as a basis for a working group discussion
> of our charter.
> 
> Please note that this is not a "re-charter", but a normal charter update
> (maintenance) that should take place when adopting new work items or
> finalizing others. The only "issue" is that we have not maintained the
> charter to the degree we should have during the last years when the
> work load has been quite heavy.
> 
> Please view the text below as a starting point for an update of our
> charter and send your comments to mpls@ietf.org. We would like to see
> your comments before June 7th, 2013.
> 
> -------------------- Proposed new charter text -------------------------
> 
> 
> Description of Working Group
> 
> The MPLS working group is responsible for standardizing technology
> for label switching and for the implementation of label-switched
> paths over packet based link-level technologies.
> 
> The responsibility includes procedures and protocols for the
> distribution of labels between Label Switching Routers (LSRs),
> MPLS packet encapsulation, and for Operation, Administration, and
> Maintenance (OAM) (including the necessary management objects
> expressed as MIB modules or using other techniques).
> 
> The current WG work items are:
> 

The text above looks good. A nit: are these "work items" or "focus areas"?

> •    Maintain existing MPLS requirements, mechanisms, and protocols,
>        in coordination with other working groups, e.g. CCAMP, PWE3
>        and OPSAWG working groups.
> •    Evolve key MPLS protocols, including LDP, tLDP, mLDP, RSVP-TE
>        and LSP Ping to meet new requirements.
> •    Define an overall OAM framework for topology-driven, traffic
>        engineered, and transport profile MPLS applications.
> •    Determine MPLS-specific aspects of traffic engineering for
>        multi-areas/multi-AS in cooperation with the CCAMP WG
> •    Define necessary extensions for MPLS key protocols for
>        dual-stack and IPv6 only networks

In addition to defining extensions, could we add also a "gap analysis" of the IPv6 (dual stack and IPv6 only) state for MPLS key protocols and procedures?

Thanks,

Carlos. 

> •    Coordinate with the CCAMP working group on the extensions of
>        MPLS and GMPLS protocols
> •    Document current implementation practices for MPLS load sharing.
> •    Document mechanisms for securing MPLS networks in coordination
>        with the KARP working group.
> •    Document mechanisms for adding multi-topology support to
>        existing MPLS protocols.
> •    Document use cases for MPLS protocols.
> 
> -------------------------- end proposed text ------------------------
> 
> Loa
> (for the wg chairs)
> 
> -- 
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 