| Network Working Group | C. Holmberg |
| Internet-Draft | Ericsson |
| Intended status: Standards Track | R. Shpount |
| Expires: March 10, 2016 | TurboBridge |
| September 7, 2015 |
Using the SDP Offer/Answer Mechanism for DTLS
draft-ietf-mmusic-dtls-sdp-00.txt
This draft defines the SDP offer/answer procedures for negotiating and establishing a DTLS association. The draft also defines the criteria for when a new DTLS association must be established.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 10, 2016.
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
[RFC5763] defines SDP Offer/Answer procedures for SRTP-DTLS. This draft defines the SDP Offer/Answer [RFC3264] procedures for negotiation DTLS in general, based on the procedures in [RFC5763].
This draft also defines the usage of the SDP 'connection' attribute with DTLS. The attribute is used in SDP offers and answers to explicitly indicate whether a new DTLS association is to be established.
As defined in [RFC5245], when Interactive Connectivity Establishment (ICE) [RFC5245] is used, the ufrag value is changed both when ICE is negotiated, and when ICE restart [RFC5245] occurs. These events do not always require a new DTLS association to be established, but currently there is no way to explicitly indicate in an SDP offer or answer whether a new DTLS association is required. To solve that problem, this draft defines the usage of the SDP 'connection' attribute with DTLS. The attribute is used in SDP offers and answers to explicitly indicate whether a new DTLS association is to be established/re-established. The attribute can be used both with and without ICE.
As defined in [RFC5763], an endpoint MUST indicate (in an offer or answer) that a new DTLS association to established in the following cases:
When a new DTLS association is established, an endpoint MUST use a new set of transport parameters (IP address and port combination).
An ICE restart [RFC5245] does not by default require a new DTLS association to be established. A new DTLS association needs to be established only if or more of the criteria listed in Section 2.1 is fulfilled (e.g. if the local transport paramters change).
As defined in [RFC5763], each ICE candidate associated with a component is treated as being part of the same DTLS association. Therefore, from a DTLS perspective it is not considered a change of local transport parameters when an endpoint switches between those ICE candidates.
When the Session Initiation Protocol (SIP) [RFC3261] is used as the signal protocol for establishing a multimedia session, dialogs [RFC3261] might be established between the caller and multiple callees. This is referred to as forking. If forking occurs, separate DTLS associations MUST be established between the caller and each callee.
TBD
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
The SDP 'connection' attribute [RFC4145] was originally defined for connection-oriented protocols, e.g. TCP and TLS. This section defines how the attribute is used with DTLS.
A 'connection' attribute value of 'new' indicates that a new DTLS association MUST be established. A 'connection' attribute value of 'existing' indicates that a new DTLS association MUST NOT be established.
When used with DTLS, there is no default value defined for the attribute. Implementations that wish to use the attribute MUST explicitly include it in SDP offers and answers. If an offer or answer does not contain an attribute, other means needs to be used in order for endpoints to determine whether an offer or answer is associated with an event that requires the DTLS association to be re-established.
This section defines the SDP offer/answer procedures for using the SDP 'connection' attribute for DTLS. The section also describes how the usage of the SDP 'setup' attribute and the SDP 'fingerprint' attribute [RFC4572] is affected.
The procedures in this section are based on the procedures for SRTP-DTLS [RFC5763], with the addition of usage of the SDP 'connection' attribute.
When the offerer sends the initial offer, and the offerer wants to establish a DTLS association, it MUST insert an SDP 'connection' attribute with a 'new' value in the offer. In addition, the offerer MUST insert an SDP 'setup' attribute according to the procedures in [RFC4572], and an SDP 'fingerprint' attribute according to the procedures in [RFC4572], in the offer.
If ICE is used, the offerer MUST insert the SDP 'ice-ufrag' and 'ice-pwd' attributes according to the procedures in [RFC5245] in the offer.
If an answerer receives an offer that contains an SDP 'connection' attribute with a 'new' value, the answerer MUST insert a 'new' value in the associated answer. The same applies if the answerer receives an offer that contains an SDP 'connection' attribute with a 'new' value, but the answerer determines (based on the criteria for establishing a new DTLS association) that a new DTLS association is to be established. In addition, the answerer MUST insert an SDP 'setup' attribute according to the procedures in [RFC4572], and an SDP 'fingerprint' attribute according to the procedures in [RFC4572], in the answer.
If the answerer does not accept the establishment of the DTLS association, it MUST reject the "m=" lines associated with the suggested DTLS association [RFC3264].
If an answerer receives an offer that contains a 'connection' attribute with an 'existing' value, and if the answerer determines that a new DTLS association does not need to be established, it MUST insert a connection attribute with an 'existing' value in the associated answer. In addition, the answerer MUST insert an SDP 'setup' attribute with a value that does not change the previously negotiated DTLS roles, and an SDP 'fingerprint' attribute with a value that does not change the fingerprint, in the answer.
If the answerer receives an offer that does not contain an SDP 'connection' attribute, the answerer MUST NOT insert a 'connection' attribute in the answer.
If ICE is used, the answerer MUST insert the SDP 'ice-ufrag' and 'ice-pwd' attributes according to the procedures in [RFC5245] in the answer.
If a new DTLS association is to be established, and if the answerer becomes DTLS client, the answerer MUST initiate the procedures for establishing the DTLS association. If the answerer becomes DTLS server, it MUST wait for the offerer to establish the DTLS association.
When an offerer receives an answer that contains an SDP 'connection' attribute with a 'new' value, and if the offerer becomes DTLS client, the offerer MUST establish a DTLS association. If the offerer becomes DTLS server, it MUST wait for the answerer to establish the DTLS association.
If the answer contains an SDP 'connection' attribute with an 'existing' value, the offerer will continue using the previously established DTLS association. It is considered an error case if the answer contains a 'connection' attribute with an 'existing' value, and a DTLS association does not exist.
When the offerer sends a subsequent offer, and the offerer wants to establish a new DTLS association, the offerer MUST insert an SDP 'connection' attribute with a 'new' value in the offer. In addition, the offerer MUST insert an SDP 'setup' attribute according to the procedures in [RFC4572], and an SDP 'fingerprint' attribute according to the procedures in [RFC4572], in the offer.
when the offerer sends a subsequent offer, and the offerer does not want to establish a new DTLS association, if a previously established DTLS association exists, the offerer MUST insert an SDP 'connection' attribute with an 'existing' value in the offer. In addition, the offerer MUST insert an SDP 'setup' attribute with a value that does not change the previously negotiated DTLS roles, and an SDP 'fingerprint' attribute with a value that does not change the fingerprint, in the offer.
If ICE is used, the offerer MUST insert the SDP 'ice-ufrag' and 'ice-pwd' attributes according to the procedures in [RFC5245] in the subsequent offer.
Here we will add the RFC updates that are needed.
This draft does not modify the security considerations associated with DTLS, or the SDP offer/answer mechanism. The draft simply clarifies the procedures for negotiating and establishing a DTLS association.
TBD
Thanks to Justin Uberti, Martin Thomson, Paul Kyzivat and Jens Guballa for providing comments and suggestions on the draft.
[RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-holmberg-mmusic-sdp-dtls-01
Changes from draft-holmberg-mmusic-sdp-dtls-00