draft-ietf-sip-manyfolks-resource-00.txt   draft-ietf-sip-manyfolks-resource-01.txt 
SIP Working Group W. Marshall SIP Working Group W. Marshall
Internet Draft AT&T Internet Draft AT&T
Document: <draft-ietf-sip-manyfolks-resource-00> Document: <draft-ietf-sip-manyfolks-resource-01>
K. Ramakrishnan K. Ramakrishnan
TeraOptic Networks TeraOptic Networks
E. Miller E. Miller
Terayon
G. Russell G. Russell
CableLabs CableLabs
B. Beser B. Beser
Pacific Broadband Pacific Broadband
M. Mannette M. Mannette
K. Steinbrenner K. Steinbrenner
3Com 3Com
skipping to change at line 31 skipping to change at line 33
M. Ramalho M. Ramalho
Cisco Cisco
J. Pickens J. Pickens
Com21 Com21
P. Lalwaney P. Lalwaney
Nokia Nokia
J. Fellows J. Fellows
Motorola Copper Mountain Networks
D. Evans D. Evans
D. R. Evans Consulting D. R. Evans Consulting
K. Kelly K. Kelly
NetSpeak NetSpeak
A. Roach A. Roach
Ericsson Ericsson
J. Rosenberg J. Rosenberg
D. Willis D. Willis
S. Donovan S. Donovan
dynamicsoft dynamicsoft
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
November, 2000 February, 2001
Integration of Resource Management and SIP Integration of Resource Management and SIP
SIP Working Group Expiration 5/31/01 1
SIP Extensions for Resource Management November 2000
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026[1]. all provisions of Section 10 of RFC2026[1].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by other six months and may be updated, replaced, or obsoleted by other
skipping to change at line 78 skipping to change at line 77
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
The distribution of this memo is unlimited. It is filed as <draft- The distribution of this memo is unlimited. It is filed as <draft-
ietf-sip-manyfolks-resource-00.txt>, and expires May 31, 2001. ietf-sip-manyfolks-resource-01.txt>, and expires August 31, 2001.
Please send comments to the authors. Please send comments to the authors.
1. Abstract 1. Abstract
This document discusses how network QoS and security establishment This document discusses how network QoS and security establishment
can be made a precondition to sessions initiated by the Session can be made a precondition to sessions initiated by the Session
Initiation Protocol (SIP), and described by SDP. These preconditions Initiation Protocol (SIP), and described by SDP. These preconditions
require that the participant reserve network resources (or establish require that the participant reserve network resources (or establish
a secure media channel) before continuing with the session. We do a secure media channel) before continuing with the session. We do
not define new QoS reservation or security mechanisms; these pre- not define new QoS reservation or security mechanisms; these pre-
skipping to change at line 104 skipping to change at line 103
signaling. The objective of such a mechanism is to enable deployment signaling. The objective of such a mechanism is to enable deployment
of robust IP Telephony services, by ensuring that resources are made of robust IP Telephony services, by ensuring that resources are made
available before the phone rings and the participants of the call available before the phone rings and the participants of the call
are "invited" to participate. are "invited" to participate.
This document also proposes an extension to the Session Initiation This document also proposes an extension to the Session Initiation
Protocol (SIP) to add a new COMET method, which is used to confirm Protocol (SIP) to add a new COMET method, which is used to confirm
the completion of all pre-conditions by the session originator. the completion of all pre-conditions by the session originator.
2. Conventions used in this document 2. Conventions used in this document
SIP Working Group Expiration 5/31/01 2
SIP Extensions for Resource Management November 2000
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119[4]. this document are to be interpreted as described in RFC-2119[4].
3. Introduction 3. Introduction
For an Internet Telephony service to be successfully used by a large For an Internet Telephony service to be successfully used by a large
number of subscribers, it must offer few surprises to those number of subscribers, it must offer few surprises to those
accustomed to the behavior of existing telephony services. One accustomed to the behavior of existing telephony services. One
expectation is that of connection quality, implying resources must expectation is that of connection quality, implying resources must
be set aside for each call. be set aside for each call.
A key contribution of the DCS architecture, as described in [5], is A key contribution is a recognition of the need for coordination
a recognition of the need for coordination between call signaling, between call signaling, which controls access to telephony specific
which controls access to telephony specific services, and resource services, and resource management, which controls access to network-
management, which controls access to network-layer resources. This layer resources. This coordination is designed to meet the user
coordination is designed to meet the user expectations and human expectations and human factors associated with telephony.
factors associated with telephony.
While customers may expect, during times of heavy load, to receive a While customers may expect, during times of heavy load, to receive a
"fast busy" or an announcement saying "all circuits are busy now," "fast busy" or an announcement saying "all circuits are busy now,"
the general expectation is that once the destination phone rings the general expectation is that once the destination phone rings
that the connection can be made. Blocking a call after ringing the that the connection can be made. Blocking a call after ringing the
destination is considered a "call defect" and is a very undesirable destination is considered a "call defect" and is a very undesirable
exception condition. exception condition.
This draft addresses both "QoS-Assured" and "QoS-Enabled" sessions. This draft addresses both "QoS-Assured" and "QoS-Enabled" sessions.
A "QoS-Assured" session will complete only if all the required A "QoS-Assured" session will complete only if all the required
skipping to change at line 161 skipping to change at line 155
Coordination between call signaling and resource management is also Coordination between call signaling and resource management is also
needed to prevent fraud and theft of service. The coordination needed to prevent fraud and theft of service. The coordination
between call-signaling and QoS setup protocols ensures that users between call-signaling and QoS setup protocols ensures that users
are authenticated and authorized before receiving access to the are authenticated and authorized before receiving access to the
enhanced QoS associated with the telephony service. enhanced QoS associated with the telephony service.
This coordination, referred to in this draft as "preconditions," This coordination, referred to in this draft as "preconditions,"
require that the participant reserve network resources (or establish require that the participant reserve network resources (or establish
a secure media channel) before continuing with the session. We do a secure media channel) before continuing with the session. We do
not define new QoS reservation or security mechanisms; these pre- not define new QoS reservation or security mechanisms; these pre-
SIP Working Group Expiration 5/31/01 3
SIP Extensions for Resource Management November 2000
conditions simply require a participant to use existing resource conditions simply require a participant to use existing resource
reservation and security mechanisms before beginning the session. reservation and security mechanisms before beginning the session.
In the case of SIP [2], this effectively means that the "phone won't In the case of SIP [2], this effectively means that the "phone won't
ring" until the preconditions are met. These preconditions are ring" until the preconditions are met. These preconditions are
described by new SDP parameters, defined in this document. The described by new SDP parameters, defined in this document. The
parameters can mandate end-to-end QoS reservations based on RSVP [6] parameters can mandate end-to-end QoS reservations based on RSVP [5]
or any other end-to-end reservation mechanism (such as YESSIR [7], or any other end-to-end reservation mechanism (such as YESSIR [6],
or PacketCable's Dynamic Quality of Service (D-QoS) [8]), and or PacketCable's Dynamic Quality of Service (D-QoS) [7]), and
security based on IPSEC [9]. The preconditions can be defined security based on IPSEC [8]. The preconditions can be defined
independently for each media stream. independently for each media stream.
The QoS architecture of the Internet separates QoS signaling from The QoS architecture of the Internet separates QoS signaling from
application level signaling. Application layer devices (such as web application level signaling. Application layer devices (such as web
proxies and SIP servers) are not well suited for participation in proxies and SIP servers) are not well suited for participation in
network admission control or QoS management, as this is network admission control or QoS management, as this is
fundamentally a network layer issue, independent of any particular fundamentally a network layer issue, independent of any particular
application. In addition, since application devices like SIP servers application. In addition, since application devices like SIP servers
are almost never on the "bearer path" (i.e., the network path the are almost never on the "bearer path" (i.e., the network path the
RTP [10] takes), and since the RTP path and signaling paths can be RTP [9] takes), and since the RTP path and signaling paths can be
completely different (even traversing different autonomous systems), completely different (even traversing different autonomous systems),
these application servers are generally not capable of managing QoS these application servers are generally not capable of managing QoS
for the media. Keeping QoS out of application signaling also means for the media. Keeping QoS out of application signaling also means
that there can be a single infrastructure for QoS across all that there can be a single infrastructure for QoS across all
applications. This eliminates duplication of functionality, reducing applications. This eliminates duplication of functionality, reducing
management and equipment costs. It also means that new applications, management and equipment costs. It also means that new applications,
with their own unique QoS requirements, can be easily supported. with their own unique QoS requirements, can be easily supported.
This loose coupling works very well for a wide range of This loose coupling works very well for a wide range of
applications. For example, in an interactive game, one can establish applications. For example, in an interactive game, one can establish
skipping to change at line 219 skipping to change at line 209
A similar model exists for security. Rather than inventing new A similar model exists for security. Rather than inventing new
security mechanisms for each new application, common security tools security mechanisms for each new application, common security tools
(such as IPSEC) can be used across all applications. As with QoS, a (such as IPSEC) can be used across all applications. As with QoS, a
means in application level protocols is needed to indicate that a means in application level protocols is needed to indicate that a
security association is needed for the application to execute. security association is needed for the application to execute.
To solve both of these problems, we propose an extension to SDP To solve both of these problems, we propose an extension to SDP
which allows indication of pre-conditions for sessions. These which allows indication of pre-conditions for sessions. These
preconditions indicate that participation in the session should not preconditions indicate that participation in the session should not
SIP Working Group Expiration 5/31/01 4
SIP Extensions for Resource Management November 2000
proceed until the preconditions are met. The preconditions we define proceed until the preconditions are met. The preconditions we define
are (1) success of end-to-end resource reservation, and (2) success are (1) success of end-to-end resource reservation, and (2) success
of end- to-end security establishment. We chose to implement these of end- to-end security establishment. We chose to implement these
extensions in SDP, rather than SIP [2] or SAP [11], since they are extensions in SDP, rather than SIP [2] or SAP [10], since they are
fundamentally a media session issue. SIP is session agnostic; fundamentally a media session issue. SIP is session agnostic;
information about codecs, ports, and RTP [10] are outside the scope information about codecs, ports, and RTP [9] are outside the scope
of SIP. Since it is the media sessions that the reservations and of SIP. Since it is the media sessions that the reservations and
security refer to, SDP is the appropriate venue for the extensions. security refer to, SDP is the appropriate venue for the extensions.
Furthermore, placement of the extensions in SDP rather than SIP or Furthermore, placement of the extensions in SDP rather than SIP or
SAP allows specification of preconditions for individual media SAP allows specification of preconditions for individual media
streams. For example, a multimedia lecture might require reservation streams. For example, a multimedia lecture might require reservation
for the audio, but not the video (which is less important). for the audio, but not the video (which is less important).
Our extensions are completely backward compatible. If a recipient Our extensions are completely backward compatible. If a recipient
does not understand them, normal SIP or SAP processing will occur, does not understand them, normal SIP or SAP processing will occur,
at no penalty of call setup latency. at no penalty of call setup latency.
skipping to change at line 277 skipping to change at line 263
Call signaling needs to provide enough information to the resource Call signaling needs to provide enough information to the resource
management protocol so as to enable resources to be allocated in the management protocol so as to enable resources to be allocated in the
network. This typically requires most if not all of the components network. This typically requires most if not all of the components
of a packet classifier (source IP, destination IP, source port, of a packet classifier (source IP, destination IP, source port,
destination port, protocol) to be available for resource allocation. destination port, protocol) to be available for resource allocation.
3.2 Overview 3.2 Overview
For acceptable interactive voice communication it is important to For acceptable interactive voice communication it is important to
achieve end-to-end QoS. The end-to-end QoS assurance implies achieve end-to-end QoS. The end-to-end QoS assurance implies
SIP Working Group Expiration 5/31/01 5
SIP Extensions for Resource Management November 2000
achieving low packet delay and packet loss. End-to-end packet delay achieving low packet delay and packet loss. End-to-end packet delay
must be small enough that it does not interfere with normal voice must be small enough that it does not interfere with normal voice
conversations. The ITU recommends no greater than 300 ms roundtrip conversations. The ITU recommends no greater than 300 ms roundtrip
delay for telephony service. Packet loss must be small enough to delay for telephony service. Packet loss must be small enough to
not perceptibly impede voice quality or the performance of fax and not perceptibly impede voice quality or the performance of fax and
voice band modems. voice band modems.
If it is found that the network cannot guarantee end-to-end QoS If it is found that the network cannot guarantee end-to-end QoS
resources, there are two alternatives: either (1) allow call resources, there are two alternatives: either (1) allow call
signaling to proceed with high probability of excessive delay and signaling to proceed with high probability of excessive delay and
skipping to change at line 336 skipping to change at line 318
If the ISP's of the various participants are using differing If the ISP's of the various participants are using differing
resource reservation protocols, translation is necessary, but this resource reservation protocols, translation is necessary, but this
is done within the network, without knowledge of the participants. is done within the network, without knowledge of the participants.
The direction attribute indicates in which direction reservations The direction attribute indicates in which direction reservations
should be reserved. If "send", it means reservations should be made should be reserved. If "send", it means reservations should be made
in the direction of media flow from the session originator to in the direction of media flow from the session originator to
participants. If "recv", it means reservations should be made in the participants. If "recv", it means reservations should be made in the
direction of media flow from participants to the session originator. direction of media flow from participants to the session originator.
SIP Working Group Expiration 5/31/01 6
SIP Extensions for Resource Management November 2000
In the case of "sendrecv", it means reservations should be made in In the case of "sendrecv", it means reservations should be made in
both directions. If the direction attribute is "sendrecv" but the both directions. If the direction attribute is "sendrecv" but the
endpoints only support a single-direction resource reservation endpoints only support a single-direction resource reservation
protocol, then both the originator and participants cooperate to protocol, then both the originator and participants cooperate to
ensure the agreed precondition is met. ensure the agreed precondition is met.
In the case of security, the same attributes are defined - In the case of security, the same attributes are defined -
optional/mandatory, and send/recv/sendrecv. Their meaning is optional/mandatory, and send/recv/sendrecv. Their meaning is
identical to the one above, except that a security association identical to the one above, except that a security association
should be established in the given direction. The details of the should be established in the given direction. The details of the
security association are not signaled by SDP; these depend on the security association are not signaled by SDP; these depend on the
Security Policy Database of the participant. Security Policy Database of the participant.
Either party can include a "confirm" attribute in the SDP. When the Either party can include a "confirm" attribute in the SDP. When the
"Confirm" attribute is present, the recipient sends a COMET message "Confirm" attribute is present, the recipient sends a COMET message
to the sender, with SDP attached, telling the status of each to the sender, with SDP attached, telling the status of each
skipping to change at line 394 skipping to change at line 375
The formatting of the qos attribute in the Session Description The formatting of the qos attribute in the Session Description
Protocol (SDP)[3] is described by the following BNF: Protocol (SDP)[3] is described by the following BNF:
qos-attribute = "a=qos:" strength-tag SP direction-tag qos-attribute = "a=qos:" strength-tag SP direction-tag
[SP confirmation-tag] [SP confirmation-tag]
strength-tag = ("mandatory" | "optional" | "success" | strength-tag = ("mandatory" | "optional" | "success" |
"failure") "failure")
direction-tag = ("send" | "recv" | "sendrecv") direction-tag = ("send" | "recv" | "sendrecv")
confirmation-tag = "confirm" confirmation-tag = "confirm"
SIP Working Group Expiration 5/31/01 7
SIP Extensions for Resource Management November 2000
and the security attribute: and the security attribute:
security-attribute = "a=secure:" SP strength-tag SP direction-tag security-attribute = "a=secure:" SP strength-tag SP direction-tag
[SP confirmation-tag] [SP confirmation-tag]
4.1 SDP Example 4.1 SDP Example
The following example shows an SDP description carried in a SIP The following example shows an SDP description carried in a SIP
INVITE message from A to B: INVITE message from A to B:
skipping to change at line 428 skipping to change at line 406
a=secure:mandatory sendrecv a=secure:mandatory sendrecv
m=application 32416 udp wb m=application 32416 udp wb
a=orient:portrait a=orient:portrait
a=qos:optional sendrecv a=qos:optional sendrecv
a=secure:optional sendrecv a=secure:optional sendrecv
This SDP indicates that B should not continue its involvement in the This SDP indicates that B should not continue its involvement in the
session until resources for the audio are reserved from B to A, and session until resources for the audio are reserved from B to A, and
a bi-directional security association is established for the video. a bi-directional security association is established for the video.
B can join the sessions once these preconditions are met, but should B can join the sessions once these preconditions are met, but should
reserve resources and establish a bidirectional security association reserve resources and establish a bi-directional security
for the whiteboard. association for the whiteboard.
4.2 SDP Allowable Combinations 4.2 SDP Allowable Combinations
If the recipient of the SDP (e.g. the UAS) is capable and willing to If the recipient of the SDP (e.g. the UAS) is capable and willing to
honor the precondition(s), it returns a provisional response honor the precondition(s), it returns a provisional response
containing SDP, along with the qos/security attributes, for each containing SDP, along with the qos/security attributes, for each
such stream. This SDP MUST be a subset of the preconditions such stream. This SDP MUST be a subset of the preconditions
indicated in the INVITE. indicated in the INVITE.
Table 1 illustrates the allowed values for the direction tag in the Table 1 illustrates the allowed values for the direction tag in the
response. Each row represents a value of the direction in the SIP response. Each row represents a value of the direction in the SIP
INVITE, and each column the value in the response. An entry of N/A INVITE, and each column the value in the response. An entry of N/A
means that this combination is not allowed. A value of A->B (B->A) means that this combination is not allowed. A value of A->B (B->A)
implies that the precondition is for resources reserved (or security implies that the precondition is for resources reserved (or security
established) from A to B (B to A). A value of A<->B means that the established) from A to B (B to A). A value of A<->B means that the
precondition is for resource reservation or security establishment precondition is for resource reservation or security establishment
in both directions. The value in the response is the one used by in both directions. The value in the response is the one used by
both parties. both parties.
SIP Working Group Expiration 5/31/01 8
SIP Extensions for Resource Management November 2000
B: response B: response
A: request send recv sendrecv none A: request send recv sendrecv none
send N/A A->B N/A -- send N/A A->B N/A --
recv B->A N/A N/A -- recv B->A N/A N/A --
sendrecv A<-B B<-A A<->B -- sendrecv A<-B B<-A A<->B --
none -- -- -- -- none -- -- -- --
Table 1: Allowed values of coupling Table 1: Allowed values of coupling
Table 2 illustrates the allowed values for the strength tag in the Table 2 illustrates the allowed values for the strength tag in the
skipping to change at line 504 skipping to change at line 479
originator. originator.
B: confirmation B: confirmation
B: reponse send recv sendrecv B: reponse send recv sendrecv
A->B N Y N A->B N Y N
A<-B Y N N A<-B Y N N
A<->B Y Y Y A<->B Y Y Y
Table 4: Allowed values of direction in confirmation from B Table 4: Allowed values of direction in confirmation from B
SIP Working Group Expiration 5/31/01 9
SIP Extensions for Resource Management November 2000
5. SIP Extension: The COMET Method 5. SIP Extension: The COMET Method
The COMET method is used for communicating successful completion of The COMET method is used for communicating successful completion of
preconditions from the calling to called user agents. preconditions between the user agents.
The signaling path for the COMET method is the signaling path The signaling path for the COMET method is the signaling path
established as a result of the call setup. This can be either established as a result of the call setup. This can be either
direct signaling between the calling and called user agents or a direct signaling between the calling and called user agents or a
signaling path involving SIP proxy servers that were involved in the signaling path involving SIP proxy servers that were involved in the
call setup and added themselves to the Record-Route header on the call setup and added themselves to the Record-Route header on the
initial INVITE message. initial INVITE message.
The precondition information is communicated in the message body, The precondition information is communicated in the message body,
which MUST contain an SDP. For every agreed precondition, the which MUST contain an SDP. For every agreed precondition, the
skipping to change at line 558 skipping to change at line 530
as would any other non-INVITE request for a call. In particular, as would any other non-INVITE request for a call. In particular,
when sent over UDP, the COMET request is retransmitted with an when sent over UDP, the COMET request is retransmitted with an
exponentially increasing interval, starting at 500 milliseconds and exponentially increasing interval, starting at 500 milliseconds and
increasing to 4 seconds. Note that a UAC SHOULD NOT retransmit the increasing to 4 seconds. Note that a UAC SHOULD NOT retransmit the
COMET request when it receives a retransmission of the provisional COMET request when it receives a retransmission of the provisional
response being acknowledged, although doing so does not create a response being acknowledged, although doing so does not create a
protocol error. As with any other non-INVITE request, the UAC protocol error. As with any other non-INVITE request, the UAC
continues to retransmit the COMET request until it receives a final continues to retransmit the COMET request until it receives a final
response. response.
SIP Working Group Expiration 5/31/01 10
SIP Extensions for Resource Management November 2000
A COMET request MAY be cancelled. However, whilst allowed for A COMET request MAY be cancelled. However, whilst allowed for
purposes of generality, usage of CANCEL with COMET is NOT purposes of generality, usage of CANCEL with COMET is NOT
RECOMMENDED. RECOMMENDED.
5.1 Header Field Support for COMET Method 5.1 Header Field Support for COMET Method
Tables 3 and 4 are extensions of tables 4 and 5 in the SIP Tables 3 and 4 are extensions of tables 4 and 5 in the SIP
specification[2]. Refer to Section 6 of [2] for a description of specification[2]. Refer to Section 6 of [2] for a description of
the content of the tables. the content of the tables.
skipping to change at line 608 skipping to change at line 577
Content-Type e * Content-Type e *
CSeq gc m CSeq gc m
Date g o Date g o
Encryption g o Encryption g o
Expires g o Expires g o
From gc m From gc m
Hide R o Hide R o
Max-Forwards R o Max-Forwards R o
Organization g o Organization g o
Table 3 Summary of header fields, A-0 Table 3 Summary of header fields, A-0
SIP Working Group Expiration 5/31/01 11
SIP Extensions for Resource Management November 2000
Header Where COMET Header Where COMET
------ ----- ---- ------ ----- ----
Priority R o Priority R o
Proxy-Authenticate 407 o Proxy-Authenticate 407 o
Proxy-Authorization R o Proxy-Authorization R o
Proxy-Require R o Proxy-Require R o
Require R o Require R o
Retry-After R - Retry-After R -
Retry-After 404,480,486 o Retry-After 404,480,486 o
Retry-After 503 o Retry-After 503 o
skipping to change at line 653 skipping to change at line 618
The COMET request MUST contain a message body. The COMET request MUST contain a message body.
5.4 Behavior of SIP User Agents 5.4 Behavior of SIP User Agents
Unless stated otherwise, the protocol rules for the COMET request Unless stated otherwise, the protocol rules for the COMET request
governing the usage of tags, Route and Record-Route, retransmission governing the usage of tags, Route and Record-Route, retransmission
and reliability, CSeq incrementing and message formatting follow and reliability, CSeq incrementing and message formatting follow
those in [2] as defined for the BYE request. those in [2] as defined for the BYE request.
A COMET request MAY be cancelled. A UAS receiving a CANCEL for an A COMET request MAY be cancelled. A UAS receiving a CANCEL for a
COMET request SHOULD respond to the COMET with a "487 Request COMET request SHOULD respond to the COMET with a "487 Request
Cancelled" response if a final response has not been sent to the Cancelled" response if a final response has not been sent to the
COMET and then behave as if the request were never received. COMET and then behave as if the request were never received.
5.5 Behavior of SIP Proxy and Redirect Servers 5.5 Behavior of SIP Proxy and Redirect Servers
5.5.1 Proxy Server 5.5.1 Proxy Server
Unless stated otherwise, the protocol rules for the COMET request at Unless stated otherwise, the protocol rules for the COMET request at
a proxy are identical to those for a BYE request as specified in a proxy are identical to those for a BYE request as specified in
[2]. [2].
SIP Working Group Expiration 5/31/01 12
SIP Extensions for Resource Management November 2000
5.5.2 Forking Proxy Server 5.5.2 Forking Proxy Server
Unless stated otherwise, the protocol rules for the COMET request at Unless stated otherwise, the protocol rules for the COMET request at
a proxy are identical to those for a BYE request as specified in a proxy are identical to those for a BYE request as specified in
[2]. [2].
5.5.3 Redirection Server 5.5.3 Redirection Server
Unless stated otherwise, the protocol rules for the COMET request at Unless stated otherwise, the protocol rules for the COMET request at
a proxy are identical to those for a BYE request as specified in a proxy are identical to those for a BYE request as specified in
[2]. [2].
6. SIP Extension: The 580-Precondition-Failure Response 6. SIP Extension: The 183-Session-Progress Response
An additional provisional response is defined by this draft, which
is returned by a UAS to convey information not otherwise classified.
6.1 Status Code and Reason Phrase
The following is to be added to Figure 4 in Section 5.1.1,
Informational and success Status codes.
Informational = "183" ;Session-Progress
6.2 Status Code Definition
The following is to be added to a new section 7.1.5
7.1.5 183 Session Progress
The 183 (Session Progress) response is used to convey information
about the progress of the call which is not otherwise classified.
The Reason-Phrase MAY be used to convey more details about the call
progress.
The Session Progress response MAY contain a message body. If so, it
MUST contain a "Content-Disposition" header indicating the proper
treatment of the message body.
7. SIP Extension: The 580-Precondition-Failure Response
An additional error response is defined by this draft, which is An additional error response is defined by this draft, which is
returned by a UAS if it is unable to perform the mandatory returned by a UAS if it is unable to perform the mandatory
preconditions for the session. preconditions for the session.
6.1 Status Code and Reason Phrase 7.1 Status Code and Reason Phrase
The following is to be added to Figure 8, Server error status codes The following is to be added to Figure 8, Server error status codes
Server-Error = "580" ;Precondition-Failure Server-Error = "580" ;Precondition-Failure
6.2 Status Code Definition 7.2 Status Code Definition
The following is to be added to a new section 7.5.7. The following is to be added to a new section 7.5.7.
7.5.7 580 Precondition Failure 7.5.7 580 Precondition Failure
The server was unable to establish the qos or security association The server was unable to establish the qos or security association
mandated by the SDP precondition. mandated by the SDP precondition.
7. SIP Extension: Content-Disposition type 8. SIP Extension: Content-Disposition header
An additional type value is defined by this draft, which is returned An additional entity header is defined by this draft, which is
by a UAS in a provisional response indicating preconditions for the returned by a UAS in a provisional response indicating preconditions
session. for the session.
The following is to be changed in section 6.15. The following is to be added to Table 3, SIP headers, in Section 3.
Disposition-type = "render" | "session" | "icon" | "alert" | Entity-header = Content-Disposition ; Section 6.14a
"precondition" | disp-extension-token
The following entry is to be added to Table 4, Summary of header
fields, A-O, in Section 6.
where enc e-e ACK BYE CAN INV OPT REG
Content-Disposition e e o o - o o o
The following is to be added to a new section after 6.14.
6.14a Content-Disposition
Content-disposition = "Content-Disposition" ":"
Disposition-type *( ";" disp-param)
Disposition-type = "precondition" | disp-extension-token
Disp-extension-token = token
Disp-param = "handling" "=" "optional" | "required"
| other-handling
Other-handling = token
The Content-Disposition header field describes how the message body
is to be interpreted by the UAC or UAS.
The value "precondition" indicates the body part describes QoS The value "precondition" indicates the body part describes QoS
and/or security preconditions that SHOULD be established prior to and/or security preconditions that SHOULD be established prior to
the start of the session. the start of the session.
8. SIP Usage Rules The handling parameter, disp-param, describes how the UAC or UAS
should react if it receives a message body whose content type or
disposition type it does not understand. If the parameter has the
value "optional" the UAS MUST ignore the message body; if it has the
value "required" the UAS MUST return 415 (Unsupported Media Type).
If the handling parameter is missing, the value "required" is to be
assumed.
8.1 Overview 9. Option tag for Requires and Supported headers
SIP Working Group Expiration 5/31/01 13 This draft defines the option tag "precondition" for use in the
SIP Extensions for Resource Management November 2000 Require and Supported headers [12].
A UAS that supports this extension MUST respond to an OPTION request
with a Supported header that includes the "precondition" tag.
A UAC MAY include a "Require: precondition" in an INVITE request if
it wants the session initiation to fail if the UAS does not support
this feature.
Presence of the precondition entries in the SDP message body of an
INVITE request or response indicates support of this feature. The
UAC or UAS MAY in addition include a "Supported: precondition"
header in the request or response.
10. SIP Usage Rules
10.1 Overview
The session originator (UAC) prepares an SDP message body for the The session originator (UAC) prepares an SDP message body for the
INVITE describing the desired QoS and security preconditions for INVITE describing the desired QoS and security preconditions for
each media flow, and the desired directions. The token value "send" each media flow, and the desired directions. The token value "send"
means the direction of media from originator (whichever entity means the direction of media from originator (whichever entity
created the SDP) to recipient (whichever entity received the SDP in created the SDP) to recipient (whichever entity received the SDP in
a SIP message), and "recv" is from recipient to originator. In an a SIP message), and "recv" is from recipient to originator. In an
INVITE, the UAC is the originator, and the UAS is the recipient. The INVITE, the UAC is the originator, and the UAS is the recipient. The
roles are reversed in the response. roles are reversed in the response.
skipping to change at line 754 skipping to change at line 785
not let the session proceed until the mandatory preconditions are not let the session proceed until the mandatory preconditions are
met. The UAC attempts to reserve the needed resources and establish met. The UAC attempts to reserve the needed resources and establish
the security associations. the security associations.
If either party requests a confirmation, a COMET message is sent to If either party requests a confirmation, a COMET message is sent to
that party. The COMET message contains the success/failure that party. The COMET message contains the success/failure
indication for each precondition. For a precondition with a indication for each precondition. For a precondition with a
direction value of "sendrecv," the COMET indicates whether the direction value of "sendrecv," the COMET indicates whether the
sender is able to confirm both directions or only one direction. sender is able to confirm both directions or only one direction.
Upon receipt of the COMET message, the UAC/UAS continues normal SIP Upon receipt of the COMET message, the UAC/UAS continues normal SIP
call handling, by (for a UAS) alerting the user and sending e.g. a call handling. For a UAS this includes alerting the user and
180-Ringing or 200-OK response. The UAC SIP transaction completes sending a 180-Ringing or 200-OK response. The UAC SIP transaction
normally. completes normally.
Note that this extension requires usage of reliable provisional Note that this extension requires usage of reliable provisional
responses [12]. This is because the 18x contains SDP with responses [11]. This is because the 18x contains SDP with
information required for the session originator to initiate information required for the session originator to initiate
reservations from it towards the participant. reservations towards the participant.
8.2 Behavior of Originator (UAC) 10.2 Behavior of Originator (UAC)
The session originator (UAC) MAY include QoS and security The session originator (UAC) MAY include QoS and security
preconditions (including the desired direction) for each media flow preconditions (including the desired direction) for each media flow
in the SDP sent with the INVITE. The token value "send" means the in the SDP sent with the INVITE. The token value "send" means the
direction of media from originator (whichever entity created the direction of media from originator (whichever entity created the
SDP) to recipient (whichever entity received the SDP in a SIP SDP) to recipient (whichever entity received the SDP in a SIP
message), and "recv" is from recipient to originator. If message). The token value "recv" means the direction of media from
preconditions are included in the INVITE request, the UAC MUST recipient to originator. If preconditions are included in the
indicate support for reliable provisional responses [12]. INVITE request, the UAC MUST indicate support for reliable
provisional responses [11].
If the UAC receives a 18x provisional response without a Content- If the UAC receives a 18x provisional response without a Content-
Disposition of "precondition," or without SDP, or with SDP but Disposition of "precondition," or without SDP, or with SDP but
without any qos/security preconditions in any stream, UAC treats it without any qos/security preconditions in any stream, UAC treats it
as an indication that the UAS is unable or unwilling to perform the as an indication that the UAS is unable or unwilling to perform the
SIP Working Group Expiration 5/31/01 14
SIP Extensions for Resource Management November 2000
preconditions requested. As such, the UAC SHOULD proceed with normal preconditions requested. As such, the UAC SHOULD proceed with normal
call setup procedures. call setup procedures.
If the 18x provisional response contained a Content-Disposition of If the 18x provisional response contained a Content-Disposition of
"precondition" and contained SDP with mandatory qos/security "precondition" and contained SDP with mandatory qos/security
parameters, the UAC SHOULD NOT let the session proceed until the parameters, the UAC SHOULD NOT let the session proceed until the
mandatory preconditions are met. mandatory preconditions are met.
If the 18x provisional response with preconditions requested an If the 18x provisional response with preconditions requested an
acknowledgement (using the methods of [12]), the UAC MUST include an acknowledgement (using the methods of [11]), the UAC MUST include an
updated SDP in the PRACK if the UAC modified the original SDP based updated SDP in the PRACK if the UAC modified the original SDP based
on the response from the UAS. Such a modification MAY be due to on the response from the UAS. Such a modification MAY be due to
negotiation of compatible CODECs, or MAY be due to negotiation of negotiation of compatible CODECs, or MAY be due to negotiation of
mandatory preconditions. If the provisional response received from mandatory preconditions. If the provisional response received from
the UAS is a 180-Ringing, and the direction value of a mandatory the UAS is a 180-Ringing, and the direction value of a mandatory
precondition is "sendrecv," and the UAC uses a one-way QoS mechanism precondition is "sendrecv," and the UAC uses a one-way QoS mechanism
(such as RSVP), the updated SDP in the PRACK SHOULD request a (such as RSVP), the updated SDP in the PRACK SHOULD request a
confirmation from the UAS so that the bi-directional precondition confirmation from the UAS so that the bi-directional precondition
can be satisfied before performing the requested alerting function. can be satisfied before performing the requested alerting function.
skipping to change at line 815 skipping to change at line 843
If the UAC had requested confirmation in the initial SDP, it MAY If the UAC had requested confirmation in the initial SDP, it MAY
wait for the COMET message from the UAS containing the wait for the COMET message from the UAS containing the
success/failure status of each precondition. The UAC MAY set a success/failure status of each precondition. The UAC MAY set a
local timer to limit the time waiting for preconditions to complete. local timer to limit the time waiting for preconditions to complete.
The UAC SHOULD merge the success/failure status in the COMET message The UAC SHOULD merge the success/failure status in the COMET message
with its local status. For example, if the COMET message indicated with its local status. For example, if the COMET message indicated
success in the "send" direction, and the UAC was also able to meet success in the "send" direction, and the UAC was also able to meet
the precondition in the "send" direction, they combine to meet the the precondition in the "send" direction, they combine to meet the
precondition in the "sendrecv" direction. precondition in the "sendrecv" direction.
If any of the mandatory preconditions cannot be met, and a If any of the mandatory preconditions cannot be met, and a
confirmation was not requested by the UAS, the UAC MUST send a confirmation was not requested by the UAS, the UAC MUST send a
CANCEL and terminate the session. If any of the optional CANCEL and terminate the session. If any of the optional
preconditions cannot be met, the UAC MAY consult with the preconditions cannot be met, the UAC MAY consult with the
originating customer for guidance on whether to complete the originating customer for guidance on whether to complete the
session. session.
When all the preconditions have either been met or have failed, and When all the preconditions have either been met or have failed, and
the SDP received from the UAS included a confirmation request, the the SDP received from the UAS included a confirmation request, the
UAC MUST send a COMET message to the UAS with SDP, where each UAC MUST send a COMET message to the UAS with SDP. Each
precondition is updated to indicate success/failure and the precondition is updated to indicate success/failure and the
appropriate direction tag based on local operations performed appropriate direction tag is updated based on local operations
combined with the received COMET message, if any. performed combined with the received COMET message, if any.
The session now completes normally, as per [2]. The session now completes normally, as per [2].
8.3 Behavior of Destination (UAS) 10.3 Behavior of Destination (UAS)
On receipt of an INVITE request containing preconditions, the UAS On receipt of an INVITE request containing preconditions, the UAS
MUST generate a 18x provisional response containing a subset of the MUST generate a 18x provisional response containing a subset of the
preconditions supported by the UAS. In the response, the token preconditions supported by the UAS. In the response, the token
SIP Working Group Expiration 5/31/01 15
SIP Extensions for Resource Management November 2000
value "send" means the direction of the media from the UAS to the value "send" means the direction of the media from the UAS to the
UAC, and "recv" is from the UAC to the UAS. This is reversed from UAC, and "recv" is from the UAC to the UAS. This is reversed from
the SDP in the initial INVITE. The 18x provisional response MUST the SDP in the initial INVITE. The 18x provisional response MUST
include a Content-Disposition header with parameter "precondition." include a Content-Disposition header with parameter "precondition."
If the "confirm" attribute is present in the SDP received from the If the "confirm" attribute is present in the SDP received from the
UAC, or if the direction tag of a mandatory QoS precondition is UAC, or if the direction tag of a mandatory QoS precondition is
"sendrecv" and the UAS only supports a one-way QoS reservation "sendrecv" and the UAS only supports a one-way QoS reservation
scheme (e.g. RSVP), then the UAS SHOULD include a "confirm" scheme (e.g. RSVP), then the UAS SHOULD include a "confirm"
attribute. attribute. If the UAS is able to satisfy the preconditions
immediately, and no confirmation is requested by the UAC, then a
180-Ringing response is appropriate. Otherwise a 183-Session-
Progress response SHOULD be used.
If the INVITE request did not contain any preconditions, but did If the INVITE request did not contain any preconditions, but did
indicate support for reliable provisional responses[12], the UAS MAY indicate support for reliable provisional responses[11], the UAS MAY
include preconditions in a 18x provisional response to the INVITE. include preconditions in a 18x provisional response to the INVITE.
The 18x provisional response MUST include a Content-Disposition The 18x provisional response MUST include a Content-Disposition
header with the parameter "precondition." The 18x provisional header with the parameter "precondition." The 18x provisional
response MUST request an acknowledgement using the mechanism of response MUST request an acknowledgement using the mechanism of
[12]. If the PRACK includes an SDP without any preconditions, the [11]. If the PRACK includes an SDP without any preconditions, the
UAS MAY complete the session without the preconditions, or MAY UAS MAY complete the session without the preconditions, or MAY
reject the INVITE request. reject the INVITE request.
The UAS SHOULD request an acknowledgement to the 18x provisional The UAS SHOULD request an acknowledgement to the 18x provisional
response, using the mechanism of [12]. The UAS SHOULD wait for the response, using the mechanism of [11]. The UAS SHOULD wait for the
PRACK message before initiating resource reservation to allow the PRACK message before initiating resource reservation to allow the
resource reservation to reflect 3-way SDP negotiation, or other resource reservation to reflect 3-way SDP negotiation, or other
information available only through receipt of the PRACK. information available only through receipt of the PRACK.
If the INVITE request or PRACK message contained mandatory If the INVITE request or PRACK message contained mandatory
preconditions, or requested a confirmation of preconditions, the UAS preconditions, or requested a confirmation of preconditions, the UAS
MUST NOT alert the called user. MUST NOT alert the called user.
The UAS now attempts to reserve the qos resources and establish the The UAS now attempts to reserve the qos resources and establish the
security associations. The UAS MAY set a local timer to limit the security associations. The UAS MAY set a local timer to limit the
skipping to change at line 894 skipping to change at line 923
only able to ensure "send" or "recv," the direction tag in the COMET only able to ensure "send" or "recv," the direction tag in the COMET
MUST only indicate what the UAS ensures. The Request-URI, call-leg MUST only indicate what the UAS ensures. The Request-URI, call-leg
identification, and other headers of this COMET message are to be identification, and other headers of this COMET message are to be
constructed identically to a BYE. constructed identically to a BYE.
If the UAS had requested confirmation of a precondition in the If the UAS had requested confirmation of a precondition in the
response SDP, it SHOULD wait for the COMET message from the response SDP, it SHOULD wait for the COMET message from the
originator containing the success/failure indication of each originator containing the success/failure indication of each
precondition from the originator's point of view. The precondition from the originator's point of view. The
success/failure indications in the COMET message from the UAC SHOULD success/failure indications in the COMET message from the UAC SHOULD
SIP Working Group Expiration 5/31/01 16
SIP Extensions for Resource Management November 2000
be combined with the local status to determine the overall be combined with the local status to determine the overall
success/failure of the precondition. For example, if the COMET success/failure of the precondition. For example, if the COMET
message indicated success in the "send" direction, and the UAS was message indicated success in the "send" direction, and the UAS was
also able to meet the precondition in the "send" direction, they also able to meet the precondition in the "send" direction, they
combine to meet the precondition in the "sendrecv" direction. If combine to meet the precondition in the "sendrecv" direction. If
that combination indicates a failure for a mandatory precondition, that combination indicates a failure for a mandatory precondition,
the UAS MUST send a 580-Precondition-Failure response to the UAC. the UAS MUST send a 580-Precondition-Failure response to the UAC.
Once the preconditions are met, the UAS alerts the user, and the SIP Once the preconditions are met, the UAS alerts the user, and the SIP
transaction proceeds normally. transaction proceeds normally.
The UAS MAY send additional 18x provisional responses with Content- The UAS MAY send additional 18x provisional responses with Content-
Disposition of "precondition," and the procedures described above Disposition of "precondition," and the procedures described above
are repeated sequentially for each. are repeated sequentially for each.
9. Examples 11. Examples
9.1 Basic (Single-Media) Call Flow 11.1 Single Media Call Flow
Figure 1 presents a high-level overview of a basic end-point to end- Figure 1 presents a high-level overview of a basic end-point to end-
point (UAC-UAS) call flow. This example is appropriate for a point (UAC-UAS) call flow. This example is appropriate for a
single-media session with a mandatory quality-of-service "sendrecv" single-media session with a mandatory quality-of-service "sendrecv"
precondition, where both the UAC and UAS can only perform a single- precondition, where both the UAC and UAS can only perform a single-
direction ("send") resource reservation. direction ("send") resource reservation.
The session originator (UAC) prepares an SDP message body for the The session originator (UAC) prepares an SDP message body for the
INVITE describing the desired QoS and security preconditions for INVITE describing the desired QoS and security preconditions for
each media flow, and the desired direction "sendrecv." This SDP is each media flow, and the desired direction "sendrecv." This SDP is
skipping to change at line 939 skipping to change at line 963
The recipient of the INVITE (UAS), being willing to perform the The recipient of the INVITE (UAS), being willing to perform the
requested precondition, returns a 183-Session-Progress provisional requested precondition, returns a 183-Session-Progress provisional
response containing SDP, along with the qos/security attribute for response containing SDP, along with the qos/security attribute for
each stream having a precondition. Since the "sendrecv" direction each stream having a precondition. Since the "sendrecv" direction
tag required a cooperative effort of the UAC and UAS, the UAS tag required a cooperative effort of the UAC and UAS, the UAS
requests a confirmation when the preconditions are met, with the SDP requests a confirmation when the preconditions are met, with the SDP
entry "a=qos:mandatory sendrecv confirm." The UAS now attempts to entry "a=qos:mandatory sendrecv confirm." The UAS now attempts to
reserve the qos resources and establish the security associations. reserve the qos resources and establish the security associations.
The 183-Session-Progress provisional response is sent using the The 183-Session-Progress provisional response is sent using the
reliability mechanism of [12]. UAC sends the appropriate PRACK and reliability mechanism of [11]. UAC sends the appropriate PRACK and
UAS responds with a 200-OK to the PRACK. UAS responds with a 200-OK to the PRACK.
The 183-Session-Progress is received by the UAC, and the UAC The 183-Session-Progress is received by the UAC, and the UAC
requests the resources needed in its "send" direction, and requests the resources needed in its "send" direction, and
establishes the security associations. Once the preconditions are establishes the security associations. Once the preconditions are
met, the UAC sends a COMET message as requested by the confirmation met, the UAC sends a COMET message as requested by the confirmation
token. This COMET message contains an entry "a=qos:success send" token. This COMET message contains an entry "a=qos:success send"
SIP Working Group Expiration 5/31/01 17
SIP Extensions for Resource Management November 2000
Originating (UAC) Terminating (UAS) Originating (UAC) Terminating (UAS)
| SIP-Proxy(s) | | SIP-Proxy(s) |
| INVITE | | | INVITE | |
|---------------------->|---------------------->| |---------------------->|---------------------->|
| | | | | |
| 183 w/SDP | 183 w/SDP | | 183 w/SDP | 183 w/SDP |
|<----------------------|<----------------------| |<----------------------|<----------------------|
| | | |
| PRACK | | PRACK |
|---------------------------------------------->| |---------------------------------------------->|
skipping to change at line 998 skipping to change at line 1018
| | | | | |
| | | |
| ACK | | ACK |
|---------------------------------------------->| |---------------------------------------------->|
Figure 1: Basic Call FLow Figure 1: Basic Call FLow
The UAS successfully performs its resource reservation, in its The UAS successfully performs its resource reservation, in its
"send" direction, and waits for the COMET message from the UAC. "send" direction, and waits for the COMET message from the UAC.
On receipt of the COMET message, the UAS combines the "send" On receipt of the COMET message, the UAS processes the "send"
confirmation in the SDP with its "send" success, and knows all confirmation contained in the COMET SDP. The "send" confirmation
preconditions have been met. The UAS then continues with session from the UAC coupled with its own "send" success, allows the UAS to
establishment. At this point it alerts the user, and sends a 180- determine that all preconditions have been met. The UAS then
Ringing provisional response. This provisional response is also continues with session establishment. At this point it alerts the
user, and sends a 180-Ringing provisional response. This
SIP Working Group Expiration 5/31/01 18 provisional response is also sent using the reliability mechanism of
SIP Extensions for Resource Management November 2000 [11], resulting in a PRACK message and 200-OK of the PRACK.
sent using the reliability mechanism of [12], resulting in a PRACK
message and 200-OK of the PRACK.
When the destination party answers, the normal SIP 200-OK final When the destination party answers, the normal SIP 200-OK final
response is sent through the proxies to the originator, and the response is sent through the proxies to the originator, and the
originator responds with an ACK message. originator responds with an ACK message.
Either party can terminate the call. An endpoint that detects an Either party can terminate the call. An endpoint that detects an
"on-hook" (request to terminate the call) releases the QoS resources "on-hook" (request to terminate the call) releases the QoS resources
held for the connection, and sends a SIP BYE message to the remote held for the connection, and sends a SIP BYE message to the remote
endpoint, which is acknowledged with a 200-OK. endpoint, which is acknowledged with a 200-OK.
9.2 Advanced (Multiple-Media) Call Flow 11.2 Multiple Media Call Flow
Figure 2 presents a high-level overview of an advanced end-point to Figure 2 presents a high-level overview of an advanced end-point to
end-point (UAC-UAS) call flow. This example is appropriate for a end-point (UAC-UAS) call flow. This example is appropriate for a
multiple-media session with some combination of mandatory and multiple-media session with some combination of mandatory and
optional quality-of-service precondition. For example, the optional quality-of-service precondition. For example, the
originator may suggest five media streams, and be willing to originator may suggest five media streams, and be willing to
establish the session if any three of them are satisfied. establish the session if any three of them are satisfied.
The use of reliable provisional responses is assumed, but not shown The use of reliable provisional responses is assumed, but not shown
in this figure. in this figure.
skipping to change at line 1059 skipping to change at line 1076
success/failure results of each precondition attempted by UAC. If success/failure results of each precondition attempted by UAC. If
UAC is not satisfied with the combination of successful UAC is not satisfied with the combination of successful
preconditions, it could instead have sent a CANCEL message. preconditions, it could instead have sent a CANCEL message.
On receipt of the COMET message, UAS examines the combination of On receipt of the COMET message, UAS examines the combination of
satisfied preconditions reported by UAC, and makes a final decision satisfied preconditions reported by UAC, and makes a final decision
whether to proceed with the session. If sufficient preconditions whether to proceed with the session. If sufficient preconditions
are not satisfied, the UAS responds with 580-Precondition-Failure. are not satisfied, the UAS responds with 580-Precondition-Failure.
Otherwise, the session proceeds as in the previous example. Otherwise, the session proceeds as in the previous example.
SIP Working Group Expiration 5/31/01 19
SIP Extensions for Resource Management November 2000
Originating (UAC) Terminating (UAS) Originating (UAC) Terminating (UAS)
| SIP-Proxy(s) | | SIP-Proxy(s) |
| INVITE | | | INVITE | |
|---------------------->|---------------------->| |---------------------->|---------------------->|
| | | | | |
| 183 w/SDP | 183 w/SDP | | 183 w/SDP | 183 w/SDP |
|<----------------------|<----------------------| |<----------------------|<----------------------|
| | | |
| Reservation Reservation | | Reservation Reservation |
===========> <=========== ===========> <===========
skipping to change at line 1102 skipping to change at line 1116
| | | | | |
| 200 OK | 200 OK | | 200 OK | 200 OK |
|<----------------------|<----------------------| |<----------------------|<----------------------|
| | | | | |
| | | |
| ACK | | ACK |
|---------------------------------------------->| |---------------------------------------------->|
Figure 2: Call Flow with negotiation of optional preconditions Figure 2: Call Flow with negotiation of optional preconditions
10. Special considerations with Forking Proxies 12. Special considerations with Forking Proxies
If a proxy along the signaling path between the UAC and UAS forks If a proxy along the signaling path between the UAC and UAS forks
the INVITE request, it results in two or more UASs simultaneously the INVITE request, it results in two or more UASs simultaneously
sending provisional responses with preconditions. The procedures sending provisional responses with preconditions. The procedures
above result in the UAC handling each independently, reserving above result in the UAC handling each independently, reserving
resources and responding with COMET messages as required. resources and responding with COMET messages as required.
This results in multiple resource reservations from the UAC, only This results in multiple resource reservations from the UAC, only
one of which will be utilized for the final session. While one of which will be utilized for the final session. While
functionally correct, this has the unfortunate side-effect of functionally correct, this has the unfortunate side-effect of
increasing the call blocking probability. increasing the call blocking probability.
SIP Working Group Expiration 5/31/01 20
SIP Extensions for Resource Management November 2000
Customized resource allocation protocols may be used by the UAC to Customized resource allocation protocols may be used by the UAC to
reduce this duplicate allocation and prevent excess blocking of reduce this duplicate allocation and prevent excess blocking of
calls. For one such example, see [8]. calls. For one such example, see [8].
11. Advantages of the Proposed Approach 13. Advantages of the Proposed Approach
The use of two-phase call signaling makes it possible for SIP to The use of two-phase call signaling makes it possible for SIP to
meet user expectations that come from the telephony services. meet user expectations that come from the telephony services.
The reservation of resources before the user is alerted makes sure The reservation of resources before the user is alerted makes sure
that the network resources are assured before the destination end- that the network resources are assured before the destination end-
point is informed about the call. point is informed about the call.
The number of messages and the total delay introduced by these The number of messages and the total delay introduced by these
messages is kept to a minimum without sacrificing compatibility with messages is kept to a minimum without sacrificing compatibility with
SIP servers that do not implement preconditions. SIP servers that do not implement preconditions.
12. Security Considerations 14. Security Considerations
If the contents of the SDP contained in the 183-Session-Progress are If the contents of the SDP contained in the 183-Session-Progress are
private then end-to-end encryption of the message body can be used private then end-to-end encryption of the message body can be used
to prevent unauthorized access to the content. to prevent unauthorized access to the content.
The security considerations given in the SIP specification apply to The security considerations given in the SIP specification apply to
the COMET method. No additional security considerations specific to the COMET method. No additional security considerations specific to
the COMET method are necessary. the COMET method are necessary.
13. Notice Regarding Intellectual Property Rights 15. Notice Regarding Intellectual Property Rights
AT&T may seek patent or other intellectual property protection for AT&T may seek patent or other intellectual property protection for
some or all of the technologies disclosed in the document. If any some or all of the technologies disclosed in the document. If any
standards arising from this disclosure are or become protected by standards arising from this disclosure are or become protected by
one or more patents assigned to AT&T, AT&T intends to disclose those one or more patents assigned to AT&T, AT&T intends to disclose those
patents and license them on reasonable and non-discriminatory terms. patents and license them on reasonable and non-discriminatory terms.
Future revisions of this draft may contain additional information Future revisions of this draft may contain additional information
regarding specific intellectual property protection sought or regarding specific intellectual property protection sought or
received. received.
3COM may seek patent or other intellectual property protection for 3COM may seek patent or other intellectual property protection for
some or all of the technologies disclosed in the document. If any some or all of the technologies disclosed in the document. If any
standards arising from this disclosure are or become protected by standards arising from this disclosure are or become protected by
one or more patents assigned to 3COM, 3COM intends to disclose those one or more patents assigned to 3COM, 3COM intends to disclose those
patents and license them on reasonable and non-discriminatory terms. patents and license them on reasonable and non-discriminatory terms.
Future revisions of this draft may contain additional information Future revisions of this draft may contain additional information
regarding specific intellectual property protection sought or regarding specific intellectual property protection sought or
received. received.
14. References 16. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
SIP Working Group Expiration 5/31/01 21
SIP Extensions for Resource Management November 2000
2. M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP: 2. M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP:
Session Initiation Protocol," RFC 2543, March 1999. Session Initiation Protocol," RFC 2543, March 1999.
3. M. Handley and V. Jacobson, "SDP: Session Description Protocol," 3. M. Handley and V. Jacobson, "SDP: Session Description Protocol,"
RFC 2327, April 1998. RFC 2327, April 1998.
4. Bradner, S., "Key words for use in RFCs to Indicate Requirement 4. Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997 Levels", BCP 14, RFC 2119, March 1997
5. DCS Group, "Architectural Considerations for Providing Carrier 5. R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, and S. Jamin,
Class Telephony Services Utilizing SIP-based Distributed Call
Control Mechanisms", <draft-dcsgroup-sip-arch-03.txt>, November
2000, Work in Progress.
6. R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, and S. Jamin,
"Resource ReSerVation protocol (RSVP) -- version 1 functional "Resource ReSerVation protocol (RSVP) -- version 1 functional
specification," RFC 2205, September, 1997. specification," RFC 2205, September, 1997.
7. P. P. Pan and H. Schulzrinne, "YESSIR: A simple reservation 6. P. P. Pan and H. Schulzrinne, "YESSIR: A simple reservation
mechanism for the Internet," in Proc. International Workshop on mechanism for the Internet," in Proc. International Workshop on
Network and Operating System Support for Digital Audio and Video Network and Operating System Support for Digital Audio and Video
(NOSSDAV), (Cambridge, England), July 1998. Also IBM Research (NOSSDAV), (Cambridge, England), July 1998. Also IBM Research
Technical Report TC20967. Available at Technical Report TC20967. Available at
http://www.cs.columbia.edu/~hgs/papers/Pan98_YESSIR.ps.gz. http://www.cs.columbia.edu/~hgs/papers/Pan98_YESSIR.ps.gz.
8. PacketCable, Dynamic Quality of Service Specification, pkt-sp- 7. PacketCable, Dynamic Quality of Service Specification, pkt-sp-
dqos-i01-991201, December 1, 1999. Available at dqos-i01-991201, December 1, 1999. Available at
http://www.packetcable.com/specs/pkt-sp-dqos-i01-991202.pdf. http://www.packetcable.com/specs/pkt-sp-dqos-i01-991202.pdf.
9. S. Kent and R. Atkinson, "Security architecture for the internet 8. S. Kent and R. Atkinson, "Security architecture for the internet
protocol," RFC 2401, November 1998. protocol," RFC 2401, November 1998.
10. H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: 9. H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: a
a Transport Protocol for Real-Time Applications," RFC 1889, Transport Protocol for Real-Time Applications," RFC 1889, January
January 1996. 1996.
11. M. Handley, C. Perkins, and E. Whelan, "Session Announcement 10. M. Handley, C. Perkins, and E. Whelan, "Session Announcement
Protocol," Internet Draft, <draft-ietf-mmusic-sap-v2-06.txt>, Protocol," RFC2974, October, 2000.
March 2000, Work in Progress.
12. "Reliability of Provisional Responses in SIP," Internet Draft 11. "Reliability of Provisional Responses in SIP," RFC pending.
<draft-ietf-sip-100rel-00.txt>, January 2000, Work in Progress.
15. Acknowledgments 12. "The SIP Supported Header," RFC pending.
17. Acknowledgments
The Distributed Call Signaling work in the PacketCable project is The Distributed Call Signaling work in the PacketCable project is
the work of a large number of people, representing many different the work of a large number of people, representing many different
companies. The authors would like to recognize and thank the companies. The authors would like to recognize and thank the
following for their assistance: John Wheeler, Motorola; David following for their assistance: John Wheeler, Motorola; David
Boardman, Daniel Paul, Arris Interactive; Bill Blum, Jay Strater, Boardman, Daniel Paul, Arris Interactive; Bill Blum, Jay Strater,
Jeff Ollis, Clive Holborow, General Instruments; Doug Newlin, Guido Jeff Ollis, Clive Holborow, General Instruments; Doug Newlin, Guido
SIP Working Group Expiration 5/31/01 22
SIP Extensions for Resource Management November 2000
Schuster, Ikhlaq Sidhu, 3Com; Jiri Matousek, Bay Networks; Farzi Schuster, Ikhlaq Sidhu, 3Com; Jiri Matousek, Bay Networks; Farzi
Khazai, Nortel; John Chapman, Bill Guckel, Cisco; Chuck Kalmanek, Khazai, Nortel; John Chapman, Bill Guckel, Cisco; Chuck Kalmanek,
Doug Nortz, John Lawser, James Cheng, Tung-Hai Hsiao, Partho Mishra, Doug Nortz, John Lawser, James Cheng, Tung-Hai Hsiao, Partho Mishra,
AT&T; Telcordia Technologies; and Lucent Cable Communications. AT&T; Telcordia Technologies; and Lucent Cable Communications.
16. Author's Addresses 18. Author's Addresses
Bill Marshall Bill Marshall
AT&T AT&T
Florham Park, NJ 07932 Florham Park, NJ 07932
Email: wtm@research.att.com Email: wtm@research.att.com
K. K. Ramakrishnan K. K. Ramakrishnan
TeraOptic Networks TeraOptic Networks
Sunnyvale, CA Sunnyvale, CA
Email: kk@teraoptic.com Email: kk@teraoptic.com
Ed Miller Ed Miller
CableLabs Terayon
Louisville, CO 80027 Louisville, CO 80027
Email: E.Miller@Cablelabs.com Email: E.Miller@terayon.com
Glenn Russell Glenn Russell
CableLabs CableLabs
Louisville, CO 80027 Louisville, CO 80027
Email: G.Russell@Cablelabs.com Email: G.Russell@Cablelabs.com
Burcak Beser Burcak Beser
Pacific Broadband Communications Pacific Broadband Communications
San Jose, CA San Jose, CA
Email: Burcak@pacband.com Email: Burcak@pacband.com
skipping to change at line 1281 skipping to change at line 1280
Cisco Cisco
Acton, MA 01720 Acton, MA 01720
Email: oran@cisco.com Email: oran@cisco.com
Flemming Andreasen Flemming Andreasen
Cisco Cisco
Edison, NJ Edison, NJ
Email: fandreas@cisco.com Email: fandreas@cisco.com
Michael Ramalho Michael Ramalho
SIP Working Group Expiration 5/31/01 23
SIP Extensions for Resource Management November 2000
Cisco Cisco
Wall Township, NJ Wall Township, NJ
Email: mramalho@cisco.com Email: mramalho@cisco.com
John Pickens John Pickens
Com21 Com21
San Jose, CA San Jose, CA
Email: jpickens@com21.com Email: jpickens@com21.com
Poornima Lalwaney Poornima Lalwaney
Nokia Nokia
San Diego, CA 92121 San Diego, CA 92121
Email: poornima.lalwaney@nokia.com Email: poornima.lalwaney@nokia.com
Jon Fellows Jon Fellows
Motorola Copper Mountain Networks
San Diego, CA 92121 San Diego, CA 92121
Email: jfellows@gi.com Email: jfellows@coppermountain.com
Doc Evans Doc Evans
D. R. Evans Consulting D. R. Evans Consulting
Boulder, CO 80303 Boulder, CO 80303
Email: n7dr@arrl.net Email: n7dr@arrl.net
Keith Kelly Keith Kelly
NetSpeak NetSpeak
Boca Raton, FL 33587 Boca Raton, FL 33587
Email: keith@netspeak.com Email: keith@netspeak.com
skipping to change at line 1339 skipping to change at line 1334
Steve Donovan Steve Donovan
dynamicsoft dynamicsoft
West Orange, NJ 07052 West Orange, NJ 07052
Email: sdonovan@dynamicsoft.com Email: sdonovan@dynamicsoft.com
Henning Schulzrinne Henning Schulzrinne
Columbia University Columbia University
New York, NY New York, NY
Email: schulzrinne@cs.columbia.edu Email: schulzrinne@cs.columbia.edu
SIP Working Group Expiration 5/31/01 24
SIP Extensions for Resource Management November 2000
Full Copyright Statement Full Copyright Statement
"Copyright (C) The Internet Society (2000). All Rights Reserved. "Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published or assist in its implmentation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at line 1367 skipping to change at line 1359
English. The limited permissions granted above are perpetual and English. The limited permissions granted above are perpetual and
will not be revoked by the Internet Society or its successors or will not be revoked by the Internet Society or its successors or
assigns. This document and the information contained herein is assigns. This document and the information contained herein is
provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
Expiration Date This memo is filed as <draft-ietf-sip-manyfolks- Expiration Date This memo is filed as <draft-ietf-sip-manyfolks-
resource-00.txt>, and expires May 31, 2001. resource-01.txt>, and expires August 31, 2001.
SIP Working Group Expiration 5/31/01 25
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/