[rfc-dist] RFC 4368 on Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface Definition
rfc-editor at rfc-editor.org
Tue Jan 31 16:59:14 PST 2006
A new Request for Comments is now available in online RFC libraries.
Title: Multiprotocol Label Switching (MPLS) Label-Controlled
Asynchronous Transfer Mode (ATM) and Frame-Relay
Management Interface Definition
Author: T. Nadeau, S. Hegde
Status: Standards Track
Date: January 2006
Mailbox: tnadeau at cisco.com,
subrah at cisco.com
I-D Tag: draft-ietf-mpls-lc-if-mib-08.txt
This memo defines two MIB modules and corresponding MIB Object
Definitions that describe how label-switching-controlled
Frame-Relay and Asynchronous Transfer Mode (ATM) interfaces can be managed given the interface stacking as defined in the MPLS-LSR-STD-MIB and
MPLS-TE-STD-MIB. [STANDARDS TRACK]
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist