RFC 3520: Session Authorization Policy Element
In plain English — editorial summary, not part of the RFC
This document describes the representation of a session authorization policy element for supporting policy-based per-session authorization and admission control. The goal of session authorization is to allow the exchange of information between network elements in order to authorize the use of resources for a service and to co-ordinate actions between the signaling and transport planes. This document describes how a process on a system authorizes the reservation of resources by a host and then provides that host with a session authorization policy element which can be inserted into a resource reservation protocol (e.g., the Resource ReSerVation Protocol (RSVP) PATH message) to facilitate proper and secure reservation of those resources within the network. We describe the encoding of session authorization information as a policy element conforming to the format of a Policy Data object (RFC 2750) and provide details relating to operations, processing rules and error scenarios. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3520
- Published
- April 2003
- Authors
- L-N. Hamer; B. Gage; B. Kosinski; H. Shieh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3521Framework for Session Set-up with Media AuthorizationCurrent
April 2003
- RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent
June 2009
- RFC 5696Baseline Encoding and Transport of Pre-Congestion InformationObsoleted
November 2009
- RFC 3512Configuring Networks and Devices with Simple Network Management Protocol (SNMP)Current
April 2003
- RFC 3511Benchmarking Methodology for Firewall PerformanceObsoleted
April 2003
- RFC 3539Authentication, Authorization and Accounting (AAA) Transport ProfileCurrent
June 2003
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 3483Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR)Current
March 2003
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?