Skip to main content

Applicability Statement for Extensions to RSVP for LSP-Tunnels
draft-ietf-mpls-rsvp-tunnel-applicability-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3210.
Authors XiPeng Xiao , Alan Hannan , Daniel O. Awduche
Last updated 2013-03-02 (Latest revision 2001-04-09)
Replaces draft-awduche-mpls-rsvp-tunnel-applicability
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 3210 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-mpls-rsvp-tunnel-applicability-02
A new Request for Comments is now available in online RFC libraries.

        RFC 3210

        Title:      Applicability Statement for Extensions to RSVP for
                    LSP-Tunnels 
        Author(s):  D. Awduche, A.  Hannan, X. Xiao
        Status:     Informational
        Date:       December 2001
        Mailbox:    awduche@movaz.com, alan@routingloop.com,
                    xxiao@photuris.com 
        Pages:      8
        Characters: 17691
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mpls-rsvp-tunnel-applicability-02.txt

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

This memo discusses the applicability of "Extensions to RSVP (Resource
ReSerVation Protocol) for LSP Tunnels".  It highlights the protocol's
principles of operation and describes the network context for which it
was designed.  Guidelines for deployment are offered and known
protocol limitations are indicated.  This document is intended to
accompany the submission of "Extensions to RSVP for LSP Tunnels" onto
the Internet standards track.

This document is a product of the Multiprotocol Label Switching
Working Group of the IFTF.

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.