Internet DRAFT - draft-ietf-mpls-rsvp-unnum


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

        RFC 3477

        Title:      Signalling Unnumbered Links in Resource
                    ReSerVation Protocol -
                    Traffic Engineering (RSVP-TE)
        Author(s):  K. Kompella, Y. Rekhter
        Status:     Standards Track
        Date:       January 2003
        Pages:      9
        Characters: 19899
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-rsvp-unnum-08.txt


Current signalling used by Multi-Protocol Label Switching Traffic
Engineering (MPLS TE) does not provide support for unnumbered
links.  This document defines procedures and extensions to
Resource ReSerVation Protocol (RSVP) for Label Switched Path (LSP)
Tunnels (RSVP-TE), one of the MPLS TE signalling protocols, that are
needed in order to support unnumbered links.

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

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.