RFC 3313: Private Session Initiation Protocol (SIP) Extensions for Media Authorization
In plain English — editorial summary, not part of the RFC
This document describes the need for QoS and media authorization and defines a SIP extension that can be used to integrate QoS admission control with call signaling and help guard against denial of service attacks. The use of this extension is only applicable in administrative domains, or among federations of administrative domains with previously agreed-upon policies, where both the SIP proxy authorizing the QoS, and the policy control of the underlying network providing the QoS belong to that administrative domain or federation of domains.
Document record
- Document ID
- RFC3313
- Published
- January 2003
- Authors
- W. Marshall
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3312Integration of Resource Management and Session Initiation Protocol (SIP)Updated
October 2002
- RFC 4032Update to the Session Initiation Protocol (SIP) Preconditions FrameworkCurrent
March 2005
- RFC 3292General Switch Management Protocol (GSMP) V3Current
June 2002
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 3521Framework for Session Set-up with Media AuthorizationCurrent
April 2003
- RFC 3086Definition of Differentiated Services Per Domain Behaviors and Rules for their SpecificationCurrent
April 2001
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
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?