RFC 3312: Integration of Resource Management and Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a generic framework for preconditions which is extensible through IANA registration. This document also discusses how network quality of service can be made a precondition to establishment of sessions initiated by the Session Initiation Protocol (SIP). These preconditions require that the participant reserve network resources before continuing with the session. We do not define new quality of service reservation mechanisms; these preconditions simply require a participant to use existing resource reservation mechanisms before beginning the session
Document record
- Document ID
- RFC3312
- Published
- October 2002
- Authors
- G. Camarillo; W. Marshall; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 30
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3313Private Session Initiation Protocol (SIP) Extensions for Media AuthorizationCurrent
January 2003
- RFC 3311The Session Initiation Protocol (SIP) UPDATE MethodCurrent
October 2002
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
- RFC 3323A Privacy Mechanism for the Session Initiation Protocol (SIP)Current
December 2002
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- RFC 3326The Reason Header Field for the Session Initiation Protocol (SIP)Updated
December 2002
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 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?