WG Review: Multiprotocol Label Switching (mpls)

The IESG <iesg-secretary@ietf.org> Tue, 25 November 2014 21:28 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 6B9AC1A88FA; Tue, 25 Nov 2014 13:28:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id I1IDkwjrEigr; Tue, 25 Nov 2014 13:28:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8D941A878C; Tue, 25 Nov 2014 13:28:21 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Multiprotocol Label Switching (mpls)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141125212821.31487.99815.idtracker@ietfa.amsl.com>
Date: Tue, 25 Nov 2014 13:28:21 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/MMd0a6N26oiEixoLmF_ag9K0nTM
Cc: mpls WG <mpls@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Nov 2014 21:28:23 -0000

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

  Loa Andersson <loa@pi.nu>
  George Swallow <swallow@cisco.com>
  Ross Callon <rcallon@juniper.net>

  Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>

Assigned Area Director:
  Adrian Farrel <adrian@olddog.co.uk>

Mailing list
  Address: mpls@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/mpls
  Archive: http://www.ietf.org/mail-archive/web/mpls/


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 

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
  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.