draft-ietf-sipbrandy-osrtp-01.txt   draft-ietf-sipbrandy-osrtp-02.txt 
SIPBRANDY Working Group A. Johnston SIPBRANDY Working Group A. Johnston
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track B. Aboba Intended status: Informational B. Aboba
Expires: May 3, 2017 Microsoft Expires: November 9, 2017 Microsoft
A. Hutton A. Hutton
Unify Unify
R. Jesske R. Jesske
Deutsche Telekom Deutsche Telekom
T. Stach T. Stach
Unaffiliated Unaffiliated
October 30, 2016 May 8, 2017
An Opportunistic Approach for Secure Real-time Transport Protocol An Opportunistic Approach for Secure Real-time Transport Protocol
(OSRTP) (OSRTP)
draft-ietf-sipbrandy-osrtp-01 draft-ietf-sipbrandy-osrtp-02
Abstract Abstract
Opportunistic Secure Real-time Transport Protocol (OSRTP) allows Opportunistic Secure Real-time Transport Protocol (OSRTP) allows
encrypted media to be used in environments where support for encrypted media to be used in environments where support for
encryption is not known in advance, and not required. OSRTP is an encryption is not known in advance, and not required. OSRTP is an
implementation of Opportunistic Security, as defined in RFC 7435. implementation of Opportunistic Security, as defined in RFC 7435.
OSRTP does not require advanced SDP extensions or features and is OSRTP does not require advanced SDP extensions or features and is
fully backwards compatible with existing secure and insecure fully backwards compatible with existing secure and insecure
implementations. OSRTP is not specific to any key management implementations. OSRTP is not specific to any key management
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 May 3, 2017. This Internet-Draft will expire on November 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 33 skipping to change at page 5, line 33
According to [RFC6982], "this will allow reviewers and working groups According to [RFC6982], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
There are implementations of [I-D.kaplan-mmusic-best-effort-srtp] in There are implementations of [I-D.kaplan-mmusic-best-effort-srtp] in
deployed products by Microsoft and Unify. The IMTC "Best Practices deployed products by Microsoft and Unify. The IMTC "Best Practices
for SIP Security" document [IMTC-SIP] recommends this approach. The for SIP Security" document [IMTC-SIP] recommends this approach. The
SIP Forum plans to include support in the SIPconnect 2.0 SIP trunking SIP Forum planned to include support in the SIPconnect 2.0 SIP
recommendation [SIPCONNECT] which is under development. There are trunking recommendation [SIPCONNECT]. There are many deployments of
many deployments of ZRTP [RFC6189]. ZRTP [RFC6189].
6. Acknowledgements 6. Acknowledgements
This document is dedicated to our friend and colleague Francois Audet This document is dedicated to our friend and colleague Francois Audet
who is greatly missed in our community. His work on improving who is greatly missed in our community. His work on improving
security in SIP and RTP provided the foundation for this work. security in SIP and RTP provided the foundation for this work.
Thanks to Eric Rescorla, Martin Thomson, and Richard Barnes for their Thanks to Eric Rescorla, Martin Thomson, and Richard Barnes for their
comments. comments.
skipping to change at page 7, line 33 skipping to change at page 7, line 33
Capability Negotiation", RFC 5939, DOI 10.17487/RFC5939, Capability Negotiation", RFC 5939, DOI 10.17487/RFC5939,
September 2010, <http://www.rfc-editor.org/info/rfc5939>. September 2010, <http://www.rfc-editor.org/info/rfc5939>.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982, Code: The Implementation Status Section", RFC 6982,
DOI 10.17487/RFC6982, July 2013, DOI 10.17487/RFC6982, July 2013,
<http://www.rfc-editor.org/info/rfc6982>. <http://www.rfc-editor.org/info/rfc6982>.
[SIPCONNECT] [SIPCONNECT]
"SIP-PBX / Service Provider Interoperability SIPconnect "SIP-PBX / Service Provider Interoperability SIPconnect
2.0 - DRAFT Technical Recommendation", SIP 2.0 - Technical Recommendation", SIP Forum http://www.sipf
Forum http://www.sipforum.org/content/view/179/213/, 2015, orum.org/component/option,com_docman/task,doc_download/
<http://www.sipforum.org>. gid,838/Itemid,261/, 2017, <http://www.sipforum.org>.
Authors' Addresses Authors' Addresses
Alan Johnston Alan Johnston
Unaffiliated Unaffiliated
Bellevue, WA Bellevue, WA
USA USA
Email: alan.b.johnston@gmail.com Email: alan.b.johnston@gmail.com
Bernard Aboba Bernard Aboba
 End of changes. 7 change blocks. 
12 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/