draft-ietf-mmusic-dtls-sdp-20.txt   draft-ietf-mmusic-dtls-sdp-21.txt 
Network Working Group C. Holmberg Network Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 5763,7345 (if approved) R. Shpount Updates: 5763,7345 (if approved) R. Shpount
Intended status: Standards Track TurboBridge Intended status: Standards Track TurboBridge
Expires: August 17, 2017 February 13, 2017 Expires: September 13, 2017 March 12, 2017
Using the SDP Offer/Answer Mechanism for DTLS Using the SDP Offer/Answer Mechanism for DTLS
draft-ietf-mmusic-dtls-sdp-20.txt draft-ietf-mmusic-dtls-sdp-21.txt
Abstract Abstract
This document defines the SDP offer/answer procedures for negotiating This document defines the SDP offer/answer procedures for negotiating
and establishing a DTLS association. The document also defines the and establishing a DTLS association. The document also defines the
criteria for when a new DTLS association must be established. The criteria for when a new DTLS association must be established. The
document updates RFC 5763 and RFC 7345, by replacing common SDP document updates RFC 5763 and RFC 7345, by replacing common SDP
offer/answer procedures with a reference to this specification. offer/answer procedures with a reference to this specification.
This document defines a new SDP media-level attribute, 'dtls-id'. This document defines a new SDP media-level attribute, 'dtls-id'.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 August 17, 2017. This Internet-Draft will expire on September 13, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 5, line 17 skipping to change at page 5, line 17
Value: dtls-id-value Value: dtls-id-value
Usage Level: media Usage Level: media
Charset Dependent: no Charset Dependent: no
Default Value: N/A Default Value: N/A
Syntax: Syntax:
dtls-id-value = 6*256(dtls-id-char) dtls-id-value = 20*255(dtls-id-char)
dtls-id-char = ALPHA / DIGIT / "+" / "/" / "-" / "_" dtls-id-char = ALPHA / DIGIT / "+" / "/" / "-" / "_"
<ALPHA and DIGIT defined in [RFC4566]> <ALPHA and DIGIT defined in [RFC4566]>
Example: Example:
a=dtls-id:abc3de65cddef001 a=dtls-id:abc3de65cddef001be82
Every time an endpoint requests to establish a new DTLS association, Every time an endpoint requests to establish a new DTLS association,
the endpoint MUST generate a new local 'dtls-id' attribute value. A the endpoint MUST generate a new local 'dtls-id' attribute value. A
non-changed local 'dtls-id' attribute value, in combination with non- non-changed local 'dtls-id' attribute value, in combination with non-
changed fingerprints, indicates that the endpoint intends to reuse changed fingerprints, indicates that the endpoint intends to reuse
the existing DTLS association. the existing DTLS association.
The 'dtls-id' attribute value MUST be generated using a cryptographic The 'dtls-id' attribute value MUST be generated using a cryptographic
random function and include at least 32 bits of randomness. random function and include at least 120 bits of randomness.
No default value is defined for the SDP 'dtls-id' attribute. No default value is defined for the SDP 'dtls-id' attribute.
Implementations that wish to use the attribute MUST explicitly Implementations that wish to use the attribute MUST explicitly
include it in SDP offers and answers. If an offer or answer does not include it in SDP offers and answers. If an offer or answer does not
contain a 'dtls-id' attribute (this could happen if the offerer or contain a 'dtls-id' attribute (this could happen if the offerer or
answerer represents an existing implementation that has not been answerer represents an existing implementation that has not been
updated to support the 'dtls-id' attribute), the offer or answer MUST updated to support the 'dtls-id' attribute), the offer or answer MUST
be treated as if no 'dtls-id' attribute is included. Unless there is be treated as if no 'dtls-id' attribute is included. Unless there is
another mechanism to explicitly indicate that a new DTLS association another mechanism to explicitly indicate that a new DTLS association
is to be established, a modification of one or more of the following is to be established, a modification of one or more of the following
skipping to change at page 20, line 32 skipping to change at page 20, line 32
Subject to charset: no Subject to charset: no
Purpose: Indicates whether a new DTLS association is to be Purpose: Indicates whether a new DTLS association is to be
established/re-established. established/re-established.
Appropriate Values: see Section 4 Appropriate Values: see Section 4
Contact name: Christer Holmberg Contact name: Christer Holmberg
Mux Category: IDENTICAL Mux Category: IDENTICAL
12. Acknowledgements 12. Acknowledgements
Thanks to Justin Uberti, Martin Thomson, Paul Kyzivat, Jens Guballa, Thanks to Justin Uberti, Martin Thomson, Paul Kyzivat, Jens Guballa,
Charles Eckel and Gonzalo Salgueiro for providing comments and Charles Eckel, Gonzalo Salgueiro and Paul Jones for providing
suggestions on the document. comments and suggestions on the document.
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-20
o Change to length and randomness of dtls-id attribute value.
Changes from draft-ietf-mmusic-sdp-dtls-19 Changes from draft-ietf-mmusic-sdp-dtls-19
o Change based on comment from Roman. o Change based on comment from Roman.
Changes from draft-ietf-mmusic-sdp-dtls-18 Changes from draft-ietf-mmusic-sdp-dtls-18
o Changes based on comments from Flemming. o Changes based on comments from Flemming.
o - Change in dtls-id value definition. o - Change in dtls-id value definition.
 End of changes. 8 change blocks. 
8 lines changed or deleted 12 lines changed or added

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