RFC 3521: Framework for Session Set-up with Media Authorization
In plain English — editorial summary, not part of the RFC
Establishing multimedia streams must take into account requirements for end-to-end QoS, authorization of network resource usage and accurate accounting for resources used. During session set up, policies may be enforced to ensure that the media streams being requested lie within the bounds of the service profile established for the requesting host. Similarly, when a host requests resources to provide a certain QoS for a packet flow, policies may be enforced to ensure that the required resources lie within the bounds of the resource profile established for the requesting host. To prevent fraud and to ensure accurate billing, this document describes various scenarios and mechanisms that provide the linkage required to verify that the resources being used to provide a requested QoS are in- line with the media streams requested (and authorized) for the session. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3521
- Published
- April 2003
- Authors
- L-N. Hamer; B. Gage; H. Shieh
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3644Policy Quality of Service (QoS) Information ModelCurrent
November 2003
- RFC 3670Information Model for Describing Network Device QoS Datapath MechanismsCurrent
January 2004
- RFC 2755Security Negotiation for WebNFSCurrent
January 2000
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 4710Real-time Application Quality-of-Service Monitoring (RAQMON) FrameworkCurrent
October 2006
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 3313Private Session Initiation Protocol (SIP) Extensions for Media AuthorizationCurrent
January 2003
- RFC 3312Integration of Resource Management and Session Initiation Protocol (SIP)Updated
October 2002
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?