From nobody Fri Apr 10 14:49:40 2020 Return-Path: X-Original-To: perc@ietfa.amsl.com Delivered-To: perc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8963A0E0E for ; Fri, 10 Apr 2020 14:49:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.837 X-Spam-Level: X-Spam-Status: No, score=-1.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 vG8kKdKqc6qI for ; Fri, 10 Apr 2020 14:49:36 -0700 (PDT) Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 8B65E3A0E1B for ; Fri, 10 Apr 2020 14:49:36 -0700 (PDT) Received: by mail-lf1-x12b.google.com with SMTP id t11so2291037lfe.4 for ; Fri, 10 Apr 2020 14:49:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=301JHxzRnugolHrQRV238KmRbcbcvAjEtF57EpS01Jo=; b=EWa4VVVRbWQADWBh9x6k9BGapVmVjF3JrmfKpciOt93Q11UZ8r7pFsNj3nmLwCNan6 vShWy5aWRZJmOC7K7RktXrEWAWyCa4bMQtdlKvIaRDMRJPXaW6N2vmjfRJcP4/5Iqt5P G3fyxLilqrorf1++JOYDLQR/872vOVX8oTv6s5GViARgxhL+L6GQ677rIOlPHwkEr4wQ dg5S0MlSlt9fwxsaDn9Lo0d08phuhHrEqATVOtJ/lCJ4wn+Te+HR+bPuRb9yXk89lNdZ kGNgFCBe54XZHK06xdOx8RNJvK1M4JYuemi64GjZsJ1T3pT3/jFu43y+/FL65RGgD5B9 sr8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=301JHxzRnugolHrQRV238KmRbcbcvAjEtF57EpS01Jo=; b=GvUCRkGFHthU2kAwQQl838eu3zw8B1OMy166j93MTD7u6xUP4mrehan0BtPjj17js4 HhyBNF9dTASQeY6vKrBXmyp1BgoLCBycmpMpmh3+5YQ0wZSX6a7BWbzsn11hM39tQVrM fCSbLl8exx6xwFO5vZSvWXWFskyCrlHFzUNoN/LQQRT7G50LZUOWuXlrEXSyfLOS6PTp u5zxTnyHs+KryCqguLAPXZbEDDWqbNkU1+fWIbsD42I2F0+yoM2G99dudUQPwe+krkA7 gKMRLzj4zaCxQFVo51+qcsWiZWXOKWiiLm6nK3xzQ/Ejrsyd2S/Rl6W798BQf9tMTXWC RwYg== X-Gm-Message-State: AGi0PubnY90YN9TNuDB30VNdslb6Xo9W71pNn6O7Orl9zCH2fgN8YfbO CyAtjavH6OtbiJUlnYF0vczj+WBbd4JRS/rENWUDc6ajN0s= X-Google-Smtp-Source: APiQypLZ0r2+ZtrBKEhVVrG+NJu3TUEA1CvvdAbuCmlfBJhtNf9v7HCvLhr9V6Ah1i6GmD4yIsihDAgTo+Ntg6gJnFY= X-Received: by 2002:a05:6512:304e:: with SMTP id b14mr3484244lfb.119.1586555374231; Fri, 10 Apr 2020 14:49:34 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Fri, 10 Apr 2020 14:49:18 -0700 Message-ID: To: perc@ietf.org Content-Type: multipart/alternative; boundary="0000000000007f6bea05a2f6b5a7" Archived-At: Subject: [Perc] Secure Frames (SFrames): e2e media encryption (Fwd) X-BeenThere: perc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Privacy Enhanced RTP Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2020 21:49:38 -0000 --0000000000007f6bea05a2f6b5a7 Content-Type: text/plain; charset="UTF-8" See below for an article on the SFrames e2e media encryption scheme: https://webrtcbydralex.com/index.php/2020/03/30/secure-frames-sframes-end-to-end-media-encryption-with-webrtc-now-in-chrome/#more-1290 --0000000000007f6bea05a2f6b5a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable --0000000000007f6bea05a2f6b5a7-- From nobody Fri Apr 10 14:56:06 2020 Return-Path: X-Original-To: perc@ietfa.amsl.com Delivered-To: perc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 385D23A0CE3 for ; Fri, 10 Apr 2020 14:56:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 oeiiXjx55aG8 for ; Fri, 10 Apr 2020 14:56:02 -0700 (PDT) Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 B1D003A0CE0 for ; Fri, 10 Apr 2020 14:56:02 -0700 (PDT) Received: by mail-vs1-xe31.google.com with SMTP id u11so2125649vsu.10 for ; Fri, 10 Apr 2020 14:56:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lH1jx56EMzDO0pb+yJHNc/peBiyOG3walNEFdoVxfeU=; b=DaDh+gmC3/FaxO/GUhjKcb2LFIQXXRYqS1CQQq7wDmFGSio7iT6jIygzMCbe6VrhmM 3GSDlfM55DTf0ifF+4z+ast6qbdPmq6rpZJPOhkkNrCrqkh/uIeAoz2G7Ema/C8DYXdA 3mmr5X25cgRfIk3tjfPYnaqEkC6mZpXTiN08PcoXAHkAr0iokKQ6W6P6/TrH10A+mI99 kuaIrFcOdRufvE8x0lDXSOm6DZw/QZ7Q37cZeKsA59ERH47jMBDz8w14Q2tdd/ix+L1Y GYs3wqSUlxK7prc4AwwsqEYFz7HGrR0vJX5wXkxafE9cnVWutHhQcIPA4nfUKwvsR0lc IakA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lH1jx56EMzDO0pb+yJHNc/peBiyOG3walNEFdoVxfeU=; b=E0sISbE67gpSFFh6ZO73b4eIkAbazzgSn+SkwtJiQPZ976zFKwMWC6T00Wiu2+BgyV 8WGMAo8RgKnOXv/7lRJh2Riys259PfnLvtEhAD0UTdZsxL9QoBppPYEWbxhR4E/K9bC5 lN2a3bcHQC+DPSuVrRLI6GFM8KnDQuwsFvdtqwNGKkYjXG1I27bSgxoRG3Zo3UflYjS0 o8reuhfaySKZXJIXrdZ7Ze4eYX5DOgDqg0irT0/wYZcXESixBpcKLN4S2pp7zY/s1XSN zIDvOoFoHBjHZKGdAoqdq3+3W3kMxI9NmlZzSOcfbEaI/WbQd4jfZtNYvy3Mi9VUVG6h 3xhA== X-Gm-Message-State: AGi0PubnLYazu+Gk8P0Npu7bup7624FCFgnHP8tTRiBCbjCthU7IBPCd 5dpjsJWYHvVyzNPgU56a9ZFqQ4hAfn0Q+VwD9DUcQA== X-Google-Smtp-Source: APiQypI2YEvOSBdLqgRt2WSduUDMDhoRmTggEey9MXe1KrnC1UGyA4lP1j8b69GPGRE1BPVqYslAbdby+sb9tV5J2gQ= X-Received: by 2002:a67:7d83:: with SMTP id y125mr4760265vsc.96.1586555760884; Fri, 10 Apr 2020 14:56:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Justin Uberti Date: Fri, 10 Apr 2020 14:55:48 -0700 Message-ID: To: Bernard Aboba Cc: perc@ietf.org Content-Type: multipart/alternative; boundary="0000000000008bb23805a2f6cc89" Archived-At: Subject: Re: [Perc] Secure Frames (SFrames): e2e media encryption (Fwd) X-BeenThere: perc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Privacy Enhanced RTP Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2020 21:56:04 -0000 --0000000000008bb23805a2f6cc89 Content-Type: text/plain; charset="UTF-8" That link wasn't working for me, try this one: https://webrtcbydralex.com/index.php/2020/03/30/secure-frames-sframes-end-to-end-media-encryption-with-webrtc-now-in-chrome/ We have been using this in production for some time and have been happy with the results. As noted by Alex, it provides lower overhead than other methods and is also RTP-agnostic. On Fri, Apr 10, 2020 at 2:49 PM Bernard Aboba wrote: > See below for an article on the SFrames e2e media encryption scheme: > > https://webrtcbydralex.com/index.php/2020/03/30/secure-frames-sframes-end-to-end-media-encryption-with-webrtc-now-in-chrome/#more-1290 > > > > > _______________________________________________ > Perc mailing list > Perc@ietf.org > https://www.ietf.org/mailman/listinfo/perc > --0000000000008bb23805a2f6cc89 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

We have bee= n using this in production for some time and have been happy with the resul= ts. As noted by Alex, it provides lower overhead than other methods and is = also RTP-agnostic.

On Fri, Apr 10, 2020 at 2:49 PM Bernard Aboba <bernard.aboba@gmail.com> wrote:<= br>
_______________________________________________
Perc mailing list
Perc@ietf.org
https://www.ietf.org/mailman/listinfo/perc
--0000000000008bb23805a2f6cc89-- From nobody Sat Apr 18 08:12:54 2020 Return-Path: X-Original-To: perc@ietf.org Delivered-To: perc@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EE03A0A9E for ; Sat, 18 Apr 2020 08:12:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.127.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <158722277261.28102.6862840729686025974@ietfa.amsl.com> Date: Sat, 18 Apr 2020 08:12:52 -0700 From: IETF Secretariat Archived-At: Subject: [Perc] Milestones changed for perc WG X-BeenThere: perc@ietf.org X-Mailman-Version: 2.1.29 List-Id: Privacy Enhanced RTP Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 15:12:53 -0000 Changed milestone "Submit encrypted key transport specification to IESG (Standards Track)", resolved as "Done", added draft-ietf-perc-srtp-ekt-diet to milestone. Changed milestone "Submit architecture or framework specification to IESG (Standards Track)", resolved as "Done", added draft-ietf-perc-private-media-framework to milestone. URL: https://datatracker.ietf.org/wg/perc/about/ From nobody Thu Apr 30 12:23:10 2020 Return-Path: X-Original-To: perc@ietfa.amsl.com Delivered-To: perc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8253D3A086E; Thu, 30 Apr 2020 12:22:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 gKKBGQGBjpUz; Thu, 30 Apr 2020 12:22:30 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50DEE3A106D; Thu, 30 Apr 2020 12:22:30 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 5A99BF4073E; Thu, 30 Apr 2020 12:22:13 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, perc@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20200430192213.5A99BF4073E@rfc-editor.org> Date: Thu, 30 Apr 2020 12:22:13 -0700 (PDT) Archived-At: Subject: [Perc] =?utf-8?q?RFC_8723_on_Double_Encryption_Procedures_for_th?= =?utf-8?q?e_Secure_Real-Time_Transport_Protocol_=28SRTP=29?= X-BeenThere: perc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Privacy Enhanced RTP Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2020 19:22:34 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8723 Title: Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP) Author: C. Jennings, P. Jones, R. Barnes, A.B. Roach Status: Standards Track Stream: IETF Date: April 2020 Mailbox: fluffy@iii.ca, paulej@packetizer.com, rlb@ipv.sx, adam@nostrum.com Pages: 18 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-perc-double-12.txt URL: https://www.rfc-editor.org/info/rfc8723 DOI: 10.17487/RFC8723 In some conferencing scenarios, it is desirable for an intermediary to be able to manipulate some parameters in Real-time Transport Protocol (RTP) packets, while still providing strong end-to-end security guarantees. This document defines a cryptographic transform for the Secure Real-time Transport Protocol (SRTP) that uses two separate but related cryptographic operations to provide hop-by-hop and end-to-end security guarantees. Both the end-to-end and hop-by-hop cryptographic algorithms can utilize an authenticated encryption with associated data (AEAD) algorithm or take advantage of future SRTP transforms with different properties. This document is a product of the Privacy Enhanced RTP Conferencing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC