[rfc-dist] RFC 3814 on Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)

[rfc-editor at rfc-editor.org]

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


        RFC 3814

        Title:      Multiprotocol Label Switching (MPLS) Forwarding
                    Equivalence Class To Next Hop Label Forwarding
                    Entry (FEC-To-NHLFE) Management Information Base
                    (MIB)
        Author(s):  T. Nadeau, C. Srinivasan, A. Viswanathan
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    tnadeau at cisco.com, cheenu at bloomberg.net,
                    arunv at force10networks.com
        Pages:      42
        Characters: 87518
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-ftn-mib-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3814.txt


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 managed objects for defining, configuring,
and monitoring Forwarding Equivalence Class (FEC) to Next Hop Label
Forwarding Entry (NHLFE) mappings and corresponding actions for use
with Multiprotocol Label Switching (MPLS).

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

        help: ways_to_get_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
unlimited distribution.echo 
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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative