Skip to main content

Integration of Resource Management and Session Initiation Protocol (SIP)

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3312.
Authors Bill Marshall , Gonzalo Camarillo , Jonathan Rosenberg
Last updated 2015-10-14 (Latest revision 2002-04-08)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3312 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3312
        Title:      Integration of Resource Management
                    and Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, Ed., W. Marshall, Ed., J. Rosenberg
        Status:     Standards Track
        Date:       October 2002
        Pages:      30
        Characters: 65757
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-manyfolks-resource-07.txt


This document defines a generic framework for preconditions, which are
extensible through IANA registration.  This document also discusses
how network quality of service can be made a precondition for
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.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.