[CCAMP] RFC 6825 on Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS

rfc-editor@rfc-editor.org Tue, 15 January 2013 01:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE2311E80B8; Mon, 14 Jan 2013 17:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.162
X-Spam-Level:
X-Spam-Status: No, score=-102.162 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFfOzdtT5m5a; Mon, 14 Jan 2013 17:33:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E839A11E80A2; Mon, 14 Jan 2013 17:33:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6D474B1E004; Mon, 14 Jan 2013 17:22:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130115012259.6D474B1E004@rfc-editor.org>
Date: Mon, 14 Jan 2013 17:22:59 -0800
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] RFC 6825 on Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 01:33:42 -0000

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

        
        RFC 6825

        Title:      Traffic Engineering Database Management Information 
                    Base in Support of MPLS-TE/GMPLS 
        Author:     M. Miyazawa, T. Otani,
                    K. Kumaki, T. Nadeau
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2013
        Mailbox:    ma-miyazawa@kddilabs.jp, 
                    Tm-otani@kddi.com, 
                    ke-kumaki@kddi.com,
                    tnadeau@juniper.net
        Pages:      40
        Characters: 72765
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-ted-mib-15.txt

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

This memo defines the Management Information Base (MIB) objects for
managing the Traffic Engineering Database (TED) information with
extensions in support of the Multiprotocol Label Switching (MPLS)
with Traffic Engineering (TE) as well as Generalized MPLS (GMPLS) for
use with network management protocols.  [STANDARDS-TRACK]

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  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