draft-ietf-mmusic-dtls-sdp-19.txt   draft-ietf-mmusic-dtls-sdp-20.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: August 17, 2017 February 13, 2017
Using the SDP Offer/Answer Mechanism for DTLS Using the SDP Offer/Answer Mechanism for DTLS
draft-ietf-mmusic-dtls-sdp-19.txt draft-ietf-mmusic-dtls-sdp-20.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 5, line 32 skipping to change at page 5, line 32
Example: Example:
a=dtls-id:abc3de65cddef001 a=dtls-id:abc3de65cddef001
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 contain at least 32 bits of The 'dtls-id' attribute value MUST be generated using a cryptographic
randomness. random function and include at least 32 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 39 skipping to change at page 20, line 39
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 and Gonzalo Salgueiro for providing comments and
suggestions on the document. 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-19
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.
o - Editorial fixes. o - Editorial fixes.
Changes from draft-ietf-mmusic-sdp-dtls-17 Changes from draft-ietf-mmusic-sdp-dtls-17
 End of changes. 3 change blocks. 
3 lines changed or deleted 7 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/