Subject: [ieee-ietf-coord] FW: [new-work] WG Review: Multiprotocol Label Switching (mpls)

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Wed, 26 Nov 2014 10:08:07 +0000

Please forward to the relevant WGs in IEEE 802. 

Thanks and Regards,

Dan

> -----Original Message-----
> From: new-work [mailto:[email-masked]] On Behalf Of The
> IESG
> Sent: Tuesday, November 25, 2014 11:28 PM
> To: [email-masked]
> Subject: [new-work] WG Review: Multiprotocol Label Switching (mpls)
> 
> The Multiprotocol Label Switching (mpls) working group in the Routing Area
> of the IETF is undergoing rechartering. The IESG has not made any
> determination yet. The following draft charter was submitted, and is
> provided for informational purposes only. Please send your comments to the
> IESG mailing list (iesg at ietf.org) by 2014-12-02.
> 
> Multiprotocol Label Switching (mpls)
> ------------------------------------------------
> Current Status: Active WG
> 
> Chairs:
>   Loa Andersson <[email-masked]>
>   George Swallow <[email-masked]>
>   Ross Callon <[email-masked]>
> 
> Secretaries:
>   Martin Vigoureux <[email-masked]>
> 
> Assigned Area Director:
>   Adrian Farrel <[email-masked]>
> 
> Mailing list
>   Address: [email-masked]
>   To Subscribe: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_mpls&d=AAICAg&c=BFpWQw8bsuKpl1
> SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=RUDEU4
> zSwDvwDM1ag1KBwBYizb65SPeUo2RDActX0bE&s=ONKJGYVQBC5ss-W-
> x7UucmLPaYt9czWA-uZd5Pl6lS8&e=
>   Archive: https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__www.ietf.org_mail-
> 2Darchive_web_mpls_&d=AAICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=RUDEU4zSwDvwDM1ag1KB
> wBYizb65SPeUo2RDActX0bE&s=TQLtkS3vaYK4tzySbXLU7Jcq1O0-
> IpaDGFfmjVpiu2c&e=
> 
> Charter:
> 
> 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 working group's responsibilities include 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 YANG models or
> MIB modules.
> 
> The current WG focus areas and work items are:
> 
> - Maintain existing MPLS requirements, mechanisms, and protocols,
>   as currently documented in RFCs, in coordination with other
>   working groups that work in overlapping areas including the
>   BESS, BFD, CCAMP, OPSAWG, PALS, SPRING, and TEAS
>   working groups.
> 
> - Evolve key MPLS protocols, including LDP, tLDP, mLDP, RSVP-TE
>   for packet networks, and LSP Ping to meet new requirements.
> 
> - Document MPLS-specific aspects of traffic engineering including
>   for multi-areas/multi-AS scenarios in cooperation with the TEAS
>   working group.
> 
> - Coordinate the work on RSVP-TE with CCAMP and TEAS. In the cases
>   where there is an overlap, generic parts will be done by the TEAS
>   working group, MPLS data plane specific parts will be done by the
>   MPLS working group, and support for any other specific data planes
>   will be done by the CCAMP working group. The TEAS working group acts
>   as the hub for coordinating this work, and the MPLS working group
>   will track agreements about work to be done in this working group
>   through milestones in this charter.
> 
> - Define data models for MPLS working group related solutions.
>   YANG models and MIB modules may be considered. Coordinate with
>   the LIME and NETMOD working groups for core YANG models.
> 
> - Define an overall OAM framework for topology-driven, traffic
>   engineered, and transport profile MPLS applications.
> 
> - Define the necessary extensions for MPLS key protocols for dual-
>   stack and IPv6-only networks.
> 
> - Document current implementation practices for MPLS load sharing.
> 
> - Document mechanisms for securing MPLS protocols and data plane.
> 
> - Document mechanisms for adding multi-topology support to existing
>   MPLS protocols.
> 
> - Define the necessary protection protocols and scenarios for transport
>   profile MPLS applications
> 
> - Document use cases for MPLS protocols.
> 
> Milestones:
> 
> TBD
> 
> _______________________________________________
> new-work mailing list
> [email-masked]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_new-
> 2Dwork&d=AAICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQz
> vlsiLQfucBXRucPvdrphpBsFA&m=RUDEU4zSwDvwDM1ag1KBwBYizb65SPeUo
> 2RDActX0bE&s=EK5gQbzMc4ePrPWuwvIEcWiKHFA_rWvrfW2GRxdxuT8&e=