idnits 2.17.1 draft-ietf-rsvp-fix-iana-00.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3097 5 Title: RSVP Cryptographic Authentication -- Updated 6 Message Type Value 7 Author(s): R. Braden, L. Zhang 8 Status: Standards Track 9 Date: April 2001 10 Mailbox: Braden@ISI.EDU, lixia@cs.ucla.edu 11 Pages: 4 12 Characters: 6320 13 Updates: 2747 15 I-D Tag: draft-ietf-rsvp-fix-iana-00.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3097.txt 19 This memo resolves a duplication in the assignment of RSVP Message 20 Types, by changing the Message Types assigned by RFC 2747 to 21 Challenge and Integrity Response messages. 23 This document is a product of the Resource Reservation Setup Protocol 24 Working Group of the IETF. 26 This is now a Proposed Standard Protocol. 28 This document specifies an Internet standards track protocol for 29 the Internet community, and requests discussion and suggestions 30 for improvements. Please refer to the current edition of the 31 "Internet Official Protocol Standards" (STD 1) for the 32 standardization state and status of this protocol. Distribution 33 of this memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.