From nobody Tue Sep 19 18:17:06 2017 Return-Path: X-Original-To: sipbrandy@ietf.org Delivered-To: sipbrandy@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD4A124B18; Tue, 19 Sep 2017 18:17:05 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipbrandy@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.62.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150587022533.29229.8175335632368289442@ietfa.amsl.com> Date: Tue, 19 Sep 2017 18:17:05 -0700 Archived-At: Subject: [Sipbrandy] I-D Action: draft-ietf-sipbrandy-osrtp-03.txt X-BeenThere: sipbrandy@ietf.org X-Mailman-Version: 2.1.22 List-Id: SIPBRANDY working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 01:17:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the SIP Best-practice Recommendations Against Network Dangers to privacY WG of the IETF. Title : An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP) Authors : Alan Johnston Bernard Aboba Andrew Hutton Roland Jesske Thomas Stach Filename : draft-ietf-sipbrandy-osrtp-03.txt Pages : 8 Date : 2017-09-19 Abstract: Opportunistic Secure Real-time Transport Protocol (OSRTP) is an implementation of the Opportunistic Security mechanism, as defined in RFC 7435, applied to Real-time Transport Protocol (RTP). OSRTP allows encrypted media to be used in environments where support for encryption is not known in advance, and not required. OSRTP does not require SDP extensions or features and is fully backwards compatible with existing implementations using encrypted and authenticated media and implementations that do not encrypt or authenticate media packets. OSRTP is not specific to any key management technique for SRTP. OSRTP is a transitional approach useful for migrating existing deployments of real-time communications to a fully encrypted and authenticated state. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipbrandy-osrtp/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipbrandy-osrtp-03 https://datatracker.ietf.org/doc/html/draft-ietf-sipbrandy-osrtp-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipbrandy-osrtp-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Sep 19 18:22:41 2017 Return-Path: X-Original-To: sipbrandy@ietfa.amsl.com Delivered-To: sipbrandy@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0226C132199; Tue, 19 Sep 2017 18:22:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4REVFGvyNudX; Tue, 19 Sep 2017 18:22:38 -0700 (PDT) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B15611321AC; Tue, 19 Sep 2017 18:22:37 -0700 (PDT) Received: by mail-lf0-x230.google.com with SMTP id r17so1241820lff.6; Tue, 19 Sep 2017 18:22:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7IQwGRiWKPSAHV56zLQwBjtAru9jZsGLQsOhHD6XwT4=; b=sP1tcRgs6GdfvphWch4UnWPkE4jES/5KPSeKYjsQTS8IivYNFi0O5C9tq9+5g6FgQ3 fGxXnvb0WCnEEvy4Vqi6J9G3VMdlic93sGWdHJu7rE65fqwR0TU/vPLdqKyZxkEMNVE7 tdEOsOP4FIqFs6xStjmO9TWjy1TSKQ99Opl5ELvhnifu3nTsRnaedjWutmwHICAU8HN4 xqBHsvxCeWAVLgFzallFVMOhcLGJ+Srz/0MIfiDfI5SOIOcP33KLbWhsvnnu7PvSHGD4 +ONBVbJq8dDhq3GixpmJFEQqdf2iZZkOl9UT0MZKPdwxOXFFKSClBrmFp9huzYjRZ1zP Ob7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7IQwGRiWKPSAHV56zLQwBjtAru9jZsGLQsOhHD6XwT4=; b=uJZvU56q0pD1H5414//JNeOTn6k7dCf517TcS+H5CwgZ6fDgQZpBpkmyz5I1k5s5Vm 3jJiqyX+WXWFvj3sKK1BiyBU+OgHEMcb8Iq5E+jg3NKJe7Wwp+rYq5dCgXGE7WhjQhb0 5f5t3kSo+1yPT5GSD/qMfIj6ouYAuRrFYGFKmyjnB9iwME6SG4KCVtFlQS46cAlSQfiW rt7p3vT/JFkQB6F+7r6aE0NpCQiL+W6h/ZprvMmAgLl5//E5PAsbBuOr4Fdi3jYxHh04 0Vo+Zvw/99HeNKTkqodY3EVCcMUST0hyJbi4X9jcjbyo8s6DE4/AkP8pTIRmBkCkwPFL Qc7Q== X-Gm-Message-State: AHPjjUhmTvU9mnsK/k2e+cCl3QEggzd9zF/1a7CWRDDTPHeuGk/ix0Ja UvFnzkhRc6PaL3klR8DJQfXZziv78CCzc0wZpcLtcOTs X-Google-Smtp-Source: AOwi7QDeoXS0l7kZJxypp9pZbKG0LDvRBDhLtelt9G7c2tT3z95oT/8z7GX9DmA7jGaofyBYNmCyWMuDhHUtdDziByg= X-Received: by 10.25.78.153 with SMTP id u25mr173777lfk.111.1505870555784; Tue, 19 Sep 2017 18:22:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.29.193 with HTTP; Tue, 19 Sep 2017 18:22:35 -0700 (PDT) In-Reply-To: <150587022555.29229.14896751682296381537.idtracker@ietfa.amsl.com> References: <150587022555.29229.14896751682296381537.idtracker@ietfa.amsl.com> From: Alan Johnston Date: Tue, 19 Sep 2017 21:22:35 -0400 Message-ID: To: sipbrandy@ietf.org Cc: draft-ietf-sipbrandy-osrtp@ietf.org Content-Type: multipart/alternative; boundary="94eb2c1c06468e34f8055994cfe3" Archived-At: Subject: Re: [Sipbrandy] New Version Notification for draft-ietf-sipbrandy-osrtp-03.txt X-BeenThere: sipbrandy@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIPBRANDY working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 01:22:40 -0000 --94eb2c1c06468e34f8055994cfe3 Content-Type: text/plain; charset="UTF-8" All, This -03 version references draft-ietf-mmusic-opportunistic-negotiation and also addresses some comments Christer sent to the mmusic list a while back. Other comments and feedback are most welcome! - Alan - On Tue, Sep 19, 2017 at 9:17 PM, wrote: > > A new version of I-D, draft-ietf-sipbrandy-osrtp-03.txt > has been successfully submitted by Alan Johnston and posted to the > IETF repository. > > Name: draft-ietf-sipbrandy-osrtp > Revision: 03 > Title: An Opportunistic Approach for Secure Real-time Transport > Protocol (OSRTP) > Document date: 2017-09-18 > Group: sipbrandy > Pages: 8 > URL: https://www.ietf.org/internet-drafts/draft-ietf-sipbrandy- > osrtp-03.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-sipbrandy- > osrtp/ > Htmlized: https://tools.ietf.org/html/draft-ietf-sipbrandy-osrtp-03 > Htmlized: https://datatracker.ietf.org/ > doc/html/draft-ietf-sipbrandy-osrtp-03 > Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipbrandy- > osrtp-03 > > Abstract: > Opportunistic Secure Real-time Transport Protocol (OSRTP) is an > implementation of the Opportunistic Security mechanism, as defined in > RFC 7435, applied to Real-time Transport Protocol (RTP). OSRTP > allows encrypted media to be used in environments where support for > encryption is not known in advance, and not required. OSRTP does not > require SDP extensions or features and is fully backwards compatible > with existing implementations using encrypted and authenticated media > and implementations that do not encrypt or authenticate media > packets. OSRTP is not specific to any key management technique for > SRTP. OSRTP is a transitional approach useful for migrating existing > deployments of real-time communications to a fully encrypted and > authenticated state. > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > --94eb2c1c06468e34f8055994cfe3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All,

This -03 version references draft-= ietf-mmusic-opportuni= stic-negotiation and also addresses some comments Christer sent to the mmus= ic list a while back.

Other comments and feedback are most welcome!

- Alan -

On Tue, S= ep 19, 2017 at 9:17 PM, <internet-drafts@ietf.org> w= rote:

A new version of I-D, draft-ietf-sipbrandy-osrtp-03.txt
has been successfully submitted by Alan Johnston and posted to the
IETF repository.

Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-sipbrandy-osrtp Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A003
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An Opportunistic Approach for Secu= re Real-time Transport Protocol (OSRTP)
Document date:=C2=A0 2017-09-18
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 sipbrandy
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-ietf-sipbra= ndy-osrtp-03.txt
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-ietf-sipbrandy-osrtp/=
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https:/= /tools.ietf.org/html/draft-ietf-sipbrandy-osrtp-03
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/html/draft-ietf-sipbrandy-osr= tp-03
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipbrandy-<= wbr>osrtp-03

Abstract:
=C2=A0 =C2=A0Opportunistic Secure Real-time Transport Protocol (OSRTP) is a= n
=C2=A0 =C2=A0implementation of the Opportunistic Security mechanism, as def= ined in
=C2=A0 =C2=A0RFC 7435, applied to Real-time Transport Protocol (RTP).=C2=A0= OSRTP
=C2=A0 =C2=A0allows encrypted media to be used in environments where suppor= t for
=C2=A0 =C2=A0encryption is not known in advance, and not required.=C2=A0 OS= RTP does not
=C2=A0 =C2=A0require SDP extensions or features and is fully backwards comp= atible
=C2=A0 =C2=A0with existing implementations using encrypted and authenticate= d media
=C2=A0 =C2=A0and implementations that do not encrypt or authenticate media<= br> =C2=A0 =C2=A0packets.=C2=A0 OSRTP is not specific to any key management tec= hnique for
=C2=A0 =C2=A0SRTP.=C2=A0 OSRTP is a transitional approach useful for migrat= ing existing
=C2=A0 =C2=A0deployments of real-time communications to a fully encrypted a= nd
=C2=A0 =C2=A0authenticated state.




Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--94eb2c1c06468e34f8055994cfe3-- From nobody Wed Sep 27 12:48:04 2017 Return-Path: X-Original-To: sipbrandy@ietfa.amsl.com Delivered-To: sipbrandy@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527DA13214D for ; Wed, 27 Sep 2017 06:46:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n0pNUKpvuNxM for ; Wed, 27 Sep 2017 06:46:35 -0700 (PDT) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC875134BB7 for ; Wed, 27 Sep 2017 06:46:17 -0700 (PDT) X-AuditID: c1b4fb30-0adfd9c000001911-91-59cbaba7a9bc Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C8.40.06417.7ABABC95; Wed, 27 Sep 2017 15:46:15 +0200 (CEST) Received: from ESESSMB109.ericsson.se ([169.254.9.6]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0352.000; Wed, 27 Sep 2017 15:46:14 +0200 From: Christer Holmberg To: "sipbrandy@ietf.org" Thread-Topic: Comments on draft-ietf-sipbrandy-osrtp-03 Thread-Index: AQHTN5b8rC0e7mevfkisocmsgp0HOA== Date: Wed, 27 Sep 2017 13:46:14 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.20] Content-Type: multipart/alternative; boundary="_000_D5F187AE22C5Echristerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7ge7y1acjDV5eNbJYse4UkwOjx5Il P5kCGKO4bFJSczLLUov07RK4MpYfOc5S0BRTceHIUeYGxr1+XYycHBICJhJ9e14wdTFycQgJ HGGUOPr7GxuEs4hR4taB6exdjBwcbAIWEt3/tEEaRAR0JSavuMgIYgsLGEm8fb2VESJuLrG0 8xQTSLmIgJ7Enp54kDCLgKpEy/SzzCA2r4C1xJGew0wgNqOAmMT3U2vAbGYBcYlbT+YzQdwj ILFkz3lmCFtU4uXjf6wgtijQyA0nbrNDxBUlrk5fDtWbIPH29gd2iPmCEidnPmGZwCg0C8nY WUjKZiEpg4gbSLw/N58ZwtaWWLbwNZStL7Hxy1lGCNta4t7T9WzIahYwcqxiFC1OLU7KTTcy 0kstykwuLs7P08tLLdnECIyUg1t+G+xgfPnc8RCjAAejEg/vyqmnI4VYE8uKK3MPMUpwMCuJ 8JauAgrxpiRWVqUW5ccXleakFh9ilOZgURLnddx3IUJIID2xJDU7NbUgtQgmy8TBKdXAqLxX z/jLuouHbY8sLfXIuHzRemZP/rRN0yfbNPPrzkx67vLE7dM13X/Xzp9QkuqKPfjxUcu2+0sf O4Uzlm79cy944qpz7ScVs9vtpCMfxJ3nq/0g0ljWMsuiRr+//rEdJ+tmhxSrvnVxAsv+rvh7 5xjn++AdHo3a7yceXvPc4/bOSuajfN3X/JRYijMSDbWYi4oTAQMpoMCQAgAA Archived-At: X-Mailman-Approved-At: Wed, 27 Sep 2017 12:48:03 -0700 Subject: [Sipbrandy] Comments on draft-ietf-sipbrandy-osrtp-03 X-BeenThere: sipbrandy@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIPBRANDY working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2017 13:46:41 -0000 --_000_D5F187AE22C5Echristerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, As Alan mentioned, I provide my previous comments on the MMUSIC list (27th = January). That was a mistake my side. I have copy/pasted those comments at = the end of this e-mail for your reference. Here are my comments on the latest version (-03) of the draft. Q1 and Q2 ar= e editorial, Q3 may require some discussions with MMUSIC. In general, my previous comments have been addressed. Thank You! :) Q1: Please expand OSRTP on first occurrence in the Abstract and the Introdu= ction. Q2: In the Introduction, do we really want to reference the kaplan draft? I= realise it is only an Informative reference, but do we expect it to ever b= e published as RFC? If it contains useful information, perhaps it can be ad= ded to this draft as an Appendix. Q3: In MMUSIC, I have questioned the need for draft-ietf-mmusic-opportunist= ic-negotiation, because I think Section 3 of this draft already contains mo= st of the SDP Offer/Answer procedures. My suggestion is that we would renam= e Section 3 to =93SDP Offer/Answer Procedures=94, include the normal sub-se= ctions (=93Sending of initial offer=94, etc), and we would have everything = in one place. As an alternative, this draft should not talk about offer/ans= wer, but I think that would be quite difficult. Regards, Christer =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D My previous comments on the MMUSIC list = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Hi, I will read the rest of the document later, but a few initial comments on t= he Abstract: The text says: =93OSRTP is an implementation of Opportunistic Security, as defined in R= FC 7435.=94 Q1: I suggest to say =93=85of the Opportunistic Security mechanism, defined= in RFC 7435, for RTP.=94 Q2: I suggest to place this sentence first in the abstract. Currently the f= irst sentence talks about what OSRTP does, before it has been explained wha= t OSRTP is. The text says: =93OSRTP does not require advanced SDP extensions or features and is fully backwards compatible with existing secure and insecure implementations.=94 Q3: I suggest to remove =93advanced=94, because I don=92t know what an adva= nced SDP extension is :) Q4: What do you mean by =93secure and insecure implementations=94? I think = some re-wording or clarification is needed. Regards, Christer --_000_D5F187AE22C5Echristerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi,

As Alan mentioned, I provide my previous comments on the MMUSIC list (= 27th January). That was a mistake my side. I have copy/pasted those comment= s at the end of this e-mail for your reference.

Here are my comments on the latest version (-03) of the draft. Q1 and = Q2 are editorial, Q3 may require some discussions with MMUSIC.

In general, my previous comments have been addressed. Thank You! :)

Q1: Please expand OSRTP on first occurrence in the Abstract and t= he Introduction.

Q2: In the Introduction, do we really want to reference the kapla= n draft? I realise it is only an Informative reference, but do we expect it= to ever be published as RFC? If it contains useful information, perhaps it= can be added to this draft as an Appendix.

Q3: In MMUSIC, I have questioned the need for draft-ietf-mmusic-o= pportunistic-negotiation, because I think Section 3 of this draft already c= ontains most of the SDP Offer/Answer procedures. My suggestion is that we w= ould rename Section 3 to =93SDP Offer/Answer Procedures=94, include the normal sub-sections (=93Sending of initial offe= r=94, etc), and we would have everything in one place. As an alternative, t= his draft should not talk about offer/answer, but I think that would be qui= te difficult.

Regards,

Christer




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D My previous comments on the MMUSIC l= ist =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Hi,

 

I will read the rest of the document later, but a few init= ial comments on the Abstract:

 

The text says:

 

   =93OSRTP is an implementation of Opportunisti= c Security, as defined in RFC 7435.=94

 

Q1: I suggest to say =93=85of the Opportunistic Security m= echanism, defined in RFC 7435, for RTP.=94

 

Q2: I suggest to place this sentence first in the abstract= . Currently the first sentence talks about what OSRTP does, before it has b= een explained what OSRTP is.

 

The text says:

 

   =93OSRTP does not require advanced SDP extens= ions or features and is

   fully backwards compatible with existing secu= re and insecure

   implementations.=94

 

Q3: I suggest to remove =93advanced=94, because I don=92t = know what an advanced SDP extension is :)

 

Q4: What do you mean by =93secure and insecure implementat= ions=94? I think some re-wording or clarification is needed.

 

Regards,

 

Christer

--_000_D5F187AE22C5Echristerholmbergericssoncom_--