metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 3182: Identity Representation for RSVP

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3182
Published
October 2001
Authors
S. Yadav; R. Yavatkar; R. Pabbati; P. Ford; T. Moore; S. Herzog; R. Hess
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
18
Also known as
—
Obsoletes:
RFC 2752

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3182-identity-representation-for-rsvp