RFC 3097: RSVP Cryptographic Authentication -- Updated Message Type Value
In plain English — editorial summary, not part of the RFC
This memo resolves a duplication in the assignment of RSVP Message Types, by changing the Message Types assigned by RFC 2747 to Challenge and Integrity Response messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3097
- Published
- April 2001
- Authors
- R. Braden; L. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 2747
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 2000
- RFC 2746RSVP Operation Over IP TunnelsCurrent
January 2000
- RFC 2745RSVP Diagnostic MessagesCurrent
January 2000
- RFC 3726Requirements for Signaling ProtocolsCurrent
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?