[mpls] RFC 7453 on MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)
rfc-editor@rfc-editor.org Wed, 25 February 2015 22:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF841A893A; Wed, 25 Feb 2015 14:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pLtw8z3oBOt; Wed, 25 Feb 2015 14:18:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC631A8931; Wed, 25 Feb 2015 14:18:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 91921182534; Wed, 25 Feb 2015 14:17:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150225221755.91921182534@rfc-editor.org>
Date: Wed, 25 Feb 2015 14:17:55 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/A-2-ZsWlwU060mbLyW6ql5yOODI>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 7453 on MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 25 Feb 2015 22:18:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7453
Title: MPLS Transport Profile (MPLS-TP) Traffic
Engineering (TE) Management Information Base (MIB)
Author: V. Mahalingam, K. Sampath,
S. Aldrin, T. Nadeau
Status: Standards Track
Stream: IETF
Date: February 2015
Mailbox: venkat.mahalingams@gmail.com,
kannankvs@gmail.com,
aldrin.ietf@gmail.com,
tnadeau@lucidvision.com
Pages: 62
Characters: 117910
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-tp-te-mib-11.txt
URL: https://www.rfc-editor.org/info/rfc7453
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In
particular, it describes additional managed objects and textual
conventions for tunnels, identifiers, and Label Switching Routers to
support Multiprotocol Label Switching (MPLS) MIB modules for transport
networks.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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