draft-ietf-sipcore-199-00.txt   draft-ietf-sipcore-199-01.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Expires: October 29, 2009 April 27, 2009 Expires: June 5, 2010 December 2, 2009
Response Code for Indication of Terminated Dialog Response Code for Indication of Terminated Dialog
draft-ietf-sipcore-199-00.txt draft-ietf-sipcore-199-01.txt
Abstract
This specification defines a new SIP response code, 199 Early Dialog
Terminated, which a SIP forking proxy and a UAS can use to indicate
upstream towards the UAC that an early dialog has been terminated,
before a final response is sent towards the UAC.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in 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.
This Internet-Draft will expire on October 29, 2009. This Internet-Draft will expire on June 5, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This specification defines a new SIP response code, 199 Early Dialog described in the BSD License.
Terminated, which a SIP forking proxy and a UAS can use to indicate
upstream towards the UAC that an early dialog has been terminated,
before a final response is sent towards the UAC.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. User Agent Client behavior . . . . . . . . . . . . . . . . . . 4 4. User Agent Client behavior . . . . . . . . . . . . . . . . . . 4
4.1. Examples of resource types . . . . . . . . . . . . . . . . 5 4.1. Examples of resource types . . . . . . . . . . . . . . . . 5
4.2. Examples of policy procedures . . . . . . . . . . . . . . 6 4.2. Examples of policy procedures . . . . . . . . . . . . . . 6
5. User Agent Server behavior . . . . . . . . . . . . . . . . . . 7 5. User Agent Server behavior . . . . . . . . . . . . . . . . . . 7
skipping to change at page 13, line 39 skipping to change at page 13, line 39
| |-- ACK (2) --------------------->| | | | |-- ACK (2) --------------------->| | |
| | | | | | | | | | | |
Figure 3: Example call flow Figure 3: Example call flow
12. Security Considerations 12. Security Considerations
General security issues related to SIP responses are described in General security issues related to SIP responses are described in
[RFC3261]. Due to the nature of the 199 response, it may be [RFC3261]. Due to the nature of the 199 response, it may be
attractive to use it for launching attacks in order to terminate attractive to use it for launching attacks in order to terminate
specific early dialogs. SIP security mechanisms (e.g. hop-to-hop specific early dialogs (other early dialogs will not be affected).
TLS) can be used to minimize, or eliminate, the risk for such In addition, if a man-in-the-middle sends a 199 response to the UAC,
attacks. which terminates a specific dialog, it can take a while until the UAS
finds out that the UAC, and possbile stateful intermediates, have
terminated the dialog. SIP security mechanisms (e.g. hop-to-hop TLS)
can be used to minimize, or eliminate, the risk for such attacks.
13. IANA Considerations 13. IANA Considerations
This section registers a new SIP response code and a new option tag, This section registers a new SIP response code and a new option tag,
according to the procedures of RFC 3261. according to the procedures of RFC 3261.
13.1. IANA Registration of the 199 response code 13.1. IANA Registration of the 199 response code
This section registers a new SIP response code, 199. The required This section registers a new SIP response code, 199. The required
information for this registration, as specified in RFC 3261, is: information for this registration, as specified in RFC 3261, is:
skipping to change at page 15, line 33 skipping to change at page 15, line 33
[RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller [RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller
Preferences for the Session Initiation Protocol (SIP)", Preferences for the Session Initiation Protocol (SIP)",
RFC 3841, August 2004. RFC 3841, August 2004.
[RFC5009] Ejza, R., "Private Header (P-Header) Extension to the [RFC5009] Ejza, R., "Private Header (P-Header) Extension to the
Session Initiation Protocol (SIP) for Authorization of Session Initiation Protocol (SIP) for Authorization of
Early Media", RFC 5009, September 2007. Early Media", RFC 5009, September 2007.
[I-D.ietf-mmusic-ice] [I-D.ietf-mmusic-ice]
Rosenberg, J., "Interactive Connectivity Establishment Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", Traversal for Offer/Answer Protocols",
draft-ietf-mmusic-ice-19 (work in progress), October 2007. draft-ietf-mmusic-ice-19 (work in progress), October 2007.
15.2. Informational References 15.2. Informational References
[RFC5057] Sparks, R., "Multiple Dialog Usages in the Session [RFC5057] Sparks, R., "Multiple Dialog Usages in the Session
Initiation Protocol", RFC 5057, November 2007. Initiation Protocol", RFC 5057, November 2007.
Author's Address Author's Address
 End of changes. 6 change blocks. 
18 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/