draft-ietf-mmusic-dtls-sdp-05.txt   draft-ietf-mmusic-dtls-sdp-06.txt 
Network Working Group C. Holmberg Network Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 5763,7315 (if approved) R. Shpount Updates: 5763,7315 (if approved) R. Shpount
Intended status: Standards Track TurboBridge Intended status: Standards Track TurboBridge
Expires: July 21, 2016 January 18, 2016 Expires: August 8, 2016 February 5, 2016
Using the SDP Offer/Answer Mechanism for DTLS Using the SDP Offer/Answer Mechanism for DTLS
draft-ietf-mmusic-dtls-sdp-05.txt draft-ietf-mmusic-dtls-sdp-06.txt
Abstract Abstract
This draft defines the SDP offer/answer procedures for negotiating This draft defines the SDP offer/answer procedures for negotiating
and establishing a DTLS association. The draft also defines the and establishing a DTLS association. The draft also defines the
criteria for when a new DTLS association must be established. criteria for when a new DTLS association must be established.
This draft defines a new SDP media-level attribute, 'dtls- This draft defines a new SDP media-level attribute, 'dtls-
connection'. connection'.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on July 21, 2016. This Internet-Draft will expire on August 8, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Change of Local Transport Parameters . . . . . . . . . . 3 3.2. Change of Local Transport Parameters . . . . . . . . . . 3
3.3. Change of ICE ufrag value . . . . . . . . . . . . . . . . 4 3.3. Change of ICE ufrag value . . . . . . . . . . . . . . . . 4
3.4. Multiple SDP fingerprint attributes . . . . . . . . . . . 4 3.4. Multiple SDP fingerprint attributes . . . . . . . . . . . 4
4. SDP dtls-connection Attribute . . . . . . . . . . . . . . . . 4 4. SDP dtls-connection Attribute . . . . . . . . . . . . . . . . 4
5. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 5 5. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 5
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Generating the Initial SDP Offer . . . . . . . . . . . . 6 5.2. Generating the Initial SDP Offer . . . . . . . . . . . . 6
5.3. Generating the Answer . . . . . . . . . . . . . . . . . . 6 5.3. Generating the Answer . . . . . . . . . . . . . . . . . . 6
5.4. Offerer Processing of the SDP Answer . . . . . . . . . . 7 5.4. Offerer Processing of the SDP Answer . . . . . . . . . . 7
5.5. Modifying the Session . . . . . . . . . . . . . . . . . . 7 5.5. Modifying the Session . . . . . . . . . . . . . . . . . . 8
6. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Transport Protocol Considerations . . . . . . . . . . . . . . 8 7. Transport Protocol Considerations . . . . . . . . . . . . . . 8
7.1. Transport Re-Usage . . . . . . . . . . . . . . . . . . . 8 7.1. Transport Re-Usage . . . . . . . . . . . . . . . . . . . 9
8. SIP Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. SIP Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.2. Update to RFC 5763 . . . . . . . . . . . . . . . . . . . 9 9.2. Update to RFC 5763 . . . . . . . . . . . . . . . . . . . 9
9.3. Update to RFC 7345 . . . . . . . . . . . . . . . . . . . 14 9.3. Update to RFC 7345 . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
13. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 18 13. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 18
14. Normative References . . . . . . . . . . . . . . . . . . . . 19 14. Normative References . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
[RFC5763] defines SDP Offer/Answer procedures for SRTP-DTLS. This [RFC5763] defines SDP Offer/Answer procedures for SRTP-DTLS. This
draft defines the SDP Offer/Answer [RFC3264] procedures for draft defines the SDP Offer/Answer [RFC3264] procedures for
negotiation DTLS in general, based on the procedures in [RFC5763]. negotiation DTLS in general, based on the procedures in [RFC5763].
This draft also defines a new SDP attribute, 'dtls-connection'. The This draft also defines a new SDP attribute, 'dtls-connection'. The
attribute is used in SDP offers and answers to explicitly indicate attribute is used in SDP offers and answers to explicitly indicate
whether a new DTLS association is to be established. whether a new DTLS association is to be established.
skipping to change at page 7, line 47 skipping to change at page 7, line 47
[RFC4145]), the offerer MUST establish a DTLS association. If the [RFC4145]), the offerer MUST establish a DTLS association. If the
offerer becomes DTLS server, it MUST wait for the answerer to offerer becomes DTLS server, it MUST wait for the answerer to
establish the DTLS association. establish the DTLS association.
If the answer contains an SDP 'dtls-connection' attribute with an If the answer contains an SDP 'dtls-connection' attribute with an
'existing' value, the offerer will continue using the previously 'existing' value, the offerer will continue using the previously
established DTLS association. It is considered an error case if the established DTLS association. It is considered an error case if the
answer contains a 'dtls-connection' attribute with an 'existing' answer contains a 'dtls-connection' attribute with an 'existing'
value, and a DTLS association does not exist. value, and a DTLS association does not exist.
An offerer needs to be able to handle error conditions that can occur
during an offer/answer transaction, e.g. if an answer contains an SDP
'dtls-connection' attribute with an 'existing' value even if no DTLS
connection exists, or if the answer contains a new fingerprint value
for an existing DTLS connection. If such error case occurs, the
offerer SHOULD terminate the associated DTLS connection (if it
exists) and send a new offer in order to terminate each media stream
using the DTLS association, by setting the associated port value to
zero [RFC4145].
5.5. Modifying the Session 5.5. Modifying the Session
When the offerer sends a subsequent offer, and if the offerer wants When the offerer sends a subsequent offer, and if the offerer wants
to establish a new DTLS association, the offerer MUST insert an SDP to establish a new DTLS association, the offerer MUST insert an SDP
'dtls-connection' attribute with a 'new' value in the offer. In 'dtls-connection' attribute with a 'new' value in the offer. In
addition, the offerer MUST insert an SDP 'setup' attribute according addition, the offerer MUST insert an SDP 'setup' attribute according
to the procedures in [RFC4145], and an SDP 'fingerprint' attribute to the procedures in [RFC4145], and an SDP 'fingerprint' attribute
according to the procedures in [RFC4572], in the offer. according to the procedures in [RFC4572], in the offer.
when the offerer sends a subsequent offer, and the offerer does not when the offerer sends a subsequent offer, and the offerer does not
skipping to change at page 18, line 21 skipping to change at page 18, line 36
12. Acknowledgements 12. Acknowledgements
Thanks to Justin Uberti, Martin Thomson, Paul Kyzivat and Jens Thanks to Justin Uberti, Martin Thomson, Paul Kyzivat and Jens
Guballa for providing comments and suggestions on the draft. Guballa for providing comments and suggestions on the draft.
13. Change Log 13. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-mmusic-sdp-dtls-05
o Text on handling offer/answer error conditions added.
Changes from draft-ietf-mmusic-sdp-dtls-04 Changes from draft-ietf-mmusic-sdp-dtls-04
o Editorial nits fixed based on comments from Paul Kyzivat: o Editorial nits fixed based on comments from Paul Kyzivat:
Changes from draft-ietf-mmusic-sdp-dtls-03 Changes from draft-ietf-mmusic-sdp-dtls-03
o Changes based on comments from Paul Kyzivat: o Changes based on comments from Paul Kyzivat:
o - Modification of dtls-connection attribute section. o - Modification of dtls-connection attribute section.
 End of changes. 9 change blocks. 
10 lines changed or deleted 24 lines changed or added

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