[mpls] RFC 6639 on Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview

rfc-editor@rfc-editor.org Mon, 18 June 2012 06:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB21821F8466; Sun, 17 Jun 2012 23:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.121
X-Spam-Level:
X-Spam-Status: No, score=-102.121 tagged_above=-999 required=5 tests=[AWL=0.479, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ae+UxAaogg5L; Sun, 17 Jun 2012 23:26:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id DA6BE11E80BA; Sun, 17 Jun 2012 23:26:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9687472E042; Sun, 17 Jun 2012 23:26:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120618062604.9687472E042@rfc-editor.org>
Date: Sun, 17 Jun 2012 23:26:04 -0700
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6639 on Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 06:26:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6639

        Title:      Multiprotocol Label Switching Transport Profile 
                    (MPLS-TP) MIB-Based Management Overview 
        Author:     D. King, Ed.,
                    M. Venkatesan, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       June 2012
        Mailbox:    daniel@olddog.co.uk, 
                    venkat.mahalingams@gmail.com
        Pages:      29
        Characters: 58669
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-mib-management-overview-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6639.txt

A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks.  These MIB modules are
defined in separate documents that focus on the specific areas of
responsibility of the modules that they describe.

The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
functionality specific to the construction of packet-switched
transport networks.

This document describes the MIB-based architecture for MPLS-TP,
indicates the interrelationships between different existing MIB
modules that can be leveraged for MPLS-TP network management, and
identifies areas where additional MIB modules are required.
This document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC