RSVP Cryptographic Authentication, Version 2
draft-atkinson-teas-rsvp-auth-v2-02
| Document | Type |
Replaced Internet-Draft
(teas WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Atkinson , Tony Li | ||
| Last updated | 2025-09-05 (Latest revision 2025-06-28) | ||
| Replaced by | draft-ietf-teas-rsvp-auth-v2 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-teas-rsvp-auth-v2 | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides an algorithm-independent description of the format and use of RSVP's INTEGRITY object. The RSVP INTEGRITY object is widely used to provide hop-by-hop integrity and authentication of RSVP messages, particularly in MPLS deployments using RSVP-TE. This document obsoletes both RFC2747 and RFC3097.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)