Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
draft-bala-uni-ldp-rsvp-extensions-04

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (individual in tsv area)
Author Bala Rajagopalan 
Last updated 2015-10-14 (latest revision 2003-01-20)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3476 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Scott Bradner
IESG note On IESG agenda for 23 Jan
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3476

        Title:      Documentation of IANA Assignments for Label
                    Distribution Protocol (LDP), Resource ReSerVation
                    Protocol (RSVP), and Resource ReSerVation
                    Protocol-Traffic Engineering (RSVP-TE) Extensions
                    for Optical UNI Signaling
        Author(s):  B. Rajagopalan
        Status:     Informational
        Date:       March 2003
        Mailbox:    braja@tellium.com
        Pages:      11
        Characters: 22009
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-bala-uni-ldp-rsvp-extensions-04.txt

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

The Optical Interworking Forum (OIF) has defined extensions to the
Label Distribution Protocol (LDP) and the Resource ReSerVation
Protocol (RSVP) for optical User Network Interface (UNI)
signaling.  These extensions consist of a set of new data objects and
error codes.  This document describes these extensions.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.