RSVP Cryptographic Authentication -- Updated Message Type Value
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 4
- Abstract
- 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]
- Publication Date
- 2001-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3097- Link
- https://doi.org/10.17487/RFC3097
- Author(s)
- Robert T. BradenLixia Zhang
- Keyword(s)
- RSVP, Security
Latest version of IETF RFC 3097
Document Versions — IETF RFC 3097
-
▶ IETF RFC 3097 (2001-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 2747 [Active*]
- IETF RFC 2961 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3097.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type Value. Available at https://doi.org/10.17487/RFC3097
Snippet:
IETF RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type Value. Available at https://doi.org/10.17487/RFC3097
HTML (ISO 690 compliant)
Preview:
IETF RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type Value. Available at https://doi.org/10.17487/RFC3097
Snippet:
<span class="citation"><cite>IETF RFC 3097</cite>, RSVP Cryptographic Authentication -- Updated Message Type Value. Available at <a href="https://doi.org/10.17487/RFC3097" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3097</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type Value
doi: 10.17487/RFC3097
url: https://doi.org/10.17487/RFC3097
doi: 10.17487/RFC3097
url: https://doi.org/10.17487/RFC3097
Snippet:
<li> <cite id="bib-rfc3097">IETF RFC 3097</cite>, RSVP Cryptographic Authentication -- Updated Message Type Value <span class="doi">10.17487/RFC3097</span> </li>
Referenced By
- IETF RFC 4495 [Active*]
- IETF RFC 5151 [Active*]
- IETF RFC 5946 [Active*]