BCP 96, RFC 3936 on Procedures for Modifying the Resource reSerVation Protocol (RSVP)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


        BCP 96
        RFC 3936

        Title:      Procedures for Modifying the Resource reSerVation
                    Protocol (RSVP)
        Author(s):  K. Kompella, J. Lang
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    kireeti@juniper.net, jplang@ieee.org
        Pages:      7
        Characters: 15314
        Updates:    3209, 2205
        SeeAlso:    BCP 96

        I-D Tag:    draft-kompella-rsvp-change-02.txt

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


This memo specifies procedures for modifying the Resource reSerVation
Protocol (RSVP).  This memo also lays out new assignment guidelines
for number spaces for RSVP messages, object classes, class-types, and
sub-objects.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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.

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.


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.
<ftp://ftp.isi.edu/in-notes/rfc3936.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux