RFC 6794: A Framework for Session Initiation Protocol (SIP) Session Policies
In plain English — editorial summary, not part of the RFC
Proxy servers play a central role as an intermediary in the Session Initiation Protocol (SIP) as they define and impact policies on call routing, rendezvous, and other call features. This document specifies a framework for SIP session policies that provides a standard mechanism by which a proxy can define or influence policies on sessions, such as the codecs or media types to be used. It defines a model, an overall architecture and new protocol mechanisms for session policies. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6794
- Published
- December 2012
- Authors
- V. Hilt; G. Camarillo; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 36
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6795A Session Initiation Protocol (SIP) Event Package for Session-Specific PoliciesCurrent
December 2012
- RFC 6787Media Resource Control Protocol Version 2 (MRCPv2)Current
November 2012
- RFC 6772Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location InformationCurrent
January 2013
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 6872The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information ModelCurrent
February 2013
- RFC 6873Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)Updated
February 2013
- RFC 6714Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)Current
August 2012
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?