Applicability of Keying Methods for RSVP Security
draft-behringer-tsvwg-rsvp-security-groupkeying-01

Document Type Replaced Internet-Draft (individual)
Last updated 2008-04-02 (latest revision 2007-11-19)
Replaced by draft-ietf-tsvwg-rsvp-security-groupkeying
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tsvwg-rsvp-security-groupkeying
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-behringer-tsvwg-rsvp-security-groupkeying-01.txt

Abstract

The Resource reSerVation Protocol (RSVP) allows hop-by-hop authentication of RSVP neighbors. This requires messages to be cryptographically signed using a shared secret between participating nodes. This document compares group keying for RSVP with per neighbor or per interface keying, and discusses the associated key provisioning methods as well as applicability and limitations of these approaches. Draft-weis-gdoi-for-rsvp specifies how the Group Domain of Interpretation (GDOI) can be used to distribute group keys to RSVP nodes. The present document also discusses applicability of such group keying to RSVP encryption.

Authors

Michael Behringer (mbehring@cisco.com)
Francois Le Faucheur (flefauch@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)