draft-ietf-mmusic-udptl-dtls-06.txt   draft-ietf-mmusic-udptl-dtls-07.txt 
MMUSIC Working Group C. Holmberg MMUSIC Working Group C. Holmberg
Internet-Draft I. Sedlacek Internet-Draft I. Sedlacek
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: September 26, 2014 G. Salgueiro Expires: October 18, 2014 G. Salgueiro
Cisco Cisco
March 25, 2014 April 16, 2014
UDP Transport Layer (UDPTL) over Datagram Transport Layer Security UDP Transport Layer (UDPTL) over Datagram Transport Layer Security
(DTLS) (DTLS)
draft-ietf-mmusic-udptl-dtls-06 draft-ietf-mmusic-udptl-dtls-07
Abstract Abstract
This document specifies how the UDP Transport Layer (UDPTL) protocol, This document specifies how the UDP Transport Layer (UDPTL) protocol,
the predominant transport protocol for T.38 fax, can be transported the predominant transport protocol for T.38 fax, can be transported
over the Datagram Transport Layer Security (DTLS) protocol, how the over the Datagram Transport Layer Security (DTLS) protocol, how the
usage of UDPTL over DTLS is indicated in the Session Description usage of UDPTL over DTLS is indicated in the Session Description
Protocol (SDP), and how UDPTL over DTLS is negotiated in a session Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
established using the Session Initiation Protocol (SIP). established using the Session Initiation Protocol (SIP).
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 September 26, 2014. This Internet-Draft will expire on October 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 36 skipping to change at page 2, line 36
5.4. Compatibility With UDPTL over UDP . . . . . . . . . . . . 8 5.4. Compatibility With UDPTL over UDP . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 13 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 13
A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 13 A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 13
A.2. Basic Message Flow . . . . . . . . . . . . . . . . . . . 13 A.2. Basic Message Flow . . . . . . . . . . . . . . . . . . . 14
A.3. Message Flow Of T.38 Fax Replacing Audio Media Stream in A.3. Message Flow Of T.38 Fax Replacing Audio Media Stream in
An Existing Audio-Only Session . . . . . . . . . . . . . 19 An Existing Audio-Only Session . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
While it is possible to transmit highly sensitive documents using While it is possible to transmit highly sensitive documents using
traditional telephony encryption devices, secure fax on the Public traditional telephony encryption devices, secure fax on the Public
Switched Telephone Network (PSTN) was never widely considered or Switched Telephone Network (PSTN) was never widely considered or
prioritized. This was mainly because of the challenges involved with prioritized. This was mainly because of the challenges involved with
skipping to change at page 7, line 10 skipping to change at page 7, line 10
When the offerer receives an SDP answer and, if the offerer ends up When the offerer receives an SDP answer and, if the offerer ends up
being active it MUST initiate a DTLS handshake by sending a DTLS being active it MUST initiate a DTLS handshake by sending a DTLS
ClientHello message on the negotiated media stream, towards the IP ClientHello message on the negotiated media stream, towards the IP
address and port of the answerer. address and port of the answerer.
4.5. Modifying the Session 4.5. Modifying the Session
Once an offer/answer exchange has been completed, either endpoint MAY Once an offer/answer exchange has been completed, either endpoint MAY
send a new offer in order to modify the session. The endpoints can send a new offer in order to modify the session. The endpoints can
reuse the existing DTLS association if the key fingerprint values and reuse the existing DTLS association if the key fingerprint values and
transport parameters indicated by each endpoint are unchanged are transport parameters indicated by each endpoint are unchanged.
unchanged. Otherwise, following the rules as for the initial offer/ Otherwise, following the rules as for the initial offer/answer
answer exchange, the endpoints can negotiate and create a new DTLS exchange, the endpoints can negotiate and create a new DTLS
association and, once created, delete the previous DTLS association, association and, once created, delete the previous DTLS association,
following the same rules of for the initial offer/answer exchange. following the same rules of for the initial offer/answer exchange.
Each endpoint needs to be prepared to receive data on both the new
and old DTLS associations, as long as both are alive.
5. Miscellaneous Considerations 5. Miscellaneous Considerations
5.1. Anonymous Calls 5.1. Anonymous Calls
When making anonymous calls, a new self-signed certificate SHOULD be When making anonymous calls, a new self-signed certificate SHOULD be
used for each call and attributes inside the certificate SHALL NOT used for each call and attributes inside the certificate SHALL NOT
contain information that either allows correlation or identification contain information that either allows correlation or identification
of the user making anonymous calls. This is particularly important of the user making anonymous calls. This is particularly important
for the subjectAltName and commonName attributes. for the subjectAltName and commonName attributes.
skipping to change at page 10, line 9 skipping to change at page 10, line 9
Special thanks to Peter Dawes, who provided comments on the initial Special thanks to Peter Dawes, who provided comments on the initial
version of the draft, and to Paul E. Jones, James Rafferty, Albrecht version of the draft, and to Paul E. Jones, James Rafferty, Albrecht
Schwarz, Oscar Ohlsson, David Hanes, Adam Gensler, Ari Keranen and Schwarz, Oscar Ohlsson, David Hanes, Adam Gensler, Ari Keranen and
Flemming Andreasen who provided valuable feedback and input on the Flemming Andreasen who provided valuable feedback and input on the
MMUSIC mailing list. MMUSIC mailing list.
9. Change Log 9. 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-udptl-dtls-06
o Changes based on WGLC comments by Paul Kyzivat
o - Indicating that, when a new and an old DTLS association exist,
each endpoint needs to be prepared to receive data on both.
o - Editorial nit.
Changes from draft-ietf-mmusic-udptl-dtls-05 Changes from draft-ietf-mmusic-udptl-dtls-05
o Changes based on comments by Flemming Andreasen o Changes based on comments by Flemming Andreasen
o - SDP Offer/Answer sections structured according to RFC 3264. o - SDP Offer/Answer sections structured according to RFC 3264.
o - Clarified that ICE considerations also apply to ICE restart. o - Clarified that ICE considerations also apply to ICE restart.
o - Editorial changes. o - Editorial changes.
Changes from draft-ietf-mmusic-udptl-dtls-04 Changes from draft-ietf-mmusic-udptl-dtls-04
o Changes based on comments by Flemming Andreasen o Changes based on comments by Flemming Andreasen
 End of changes. 8 change blocks. 
8 lines changed or deleted 17 lines changed or added

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