Identity Representation for RSVP
RFC 3182, “Identity Representation for RSVP”, is a Proposed Standard document published in October 2001 by S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. Herzog, R. Hess. It obsoletes RFC 2752. The canonical text is published by the RFC Editor.
Abstract
This document describes the representation of identity information in POLICY_DATA object for supporting policy based admission control in the Resource ReSerVation Protocol (RSVP). The goal of identity representation is to allow a process on a system to securely identify the owner and the application of the communicating process (e.g., user id) and convey this information in RSVP messages (PATH or RESV) in a secure manner. We describe the encoding of identities as RSVP policy element. We describe the processing rules to generate identity policy elements for multicast merged flows. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3182 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3181 Signaled Preemption Priority Policy Element
- RFC 3183 Domain Security Services using S/MIME
- RFC 3180 GLOP Addressing in 233/8
- RFC 3184 IETF Guidelines for Conduct
- RFC 3179 Script MIB Extensibility Protocol Version 1.1
- RFC 3185 Reuse of CMS Content Encryption Keys
- RFC 3178 IPv6 Multihoming Support at Site Exit Routers
- RFC 3186 MAPOS/PPP Tunneling mode