Re: [dispatch] Plan to Submit a Proposal for Opportunistic SRTP

Alan Johnston <alan.b.johnston@gmail.com> Fri, 25 September 2015 20:31 UTC

Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA361A1B57 for <dispatch@ietfa.amsl.com>; Fri, 25 Sep 2015 13:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 19.023
X-Spam-Level: *******************
X-Spam-Status: Yes, score=19.023 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, MALFORMED_FREEMAIL=0.001, MISSING_HEADERS=1.021, SPF_PASS=-0.001, URIBL_SBL=20] autolearn=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 tdyPYAuoTNiD for <dispatch@ietfa.amsl.com>; Fri, 25 Sep 2015 13:31:54 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 443581A1B20 for <dispatch@ietf.org>; Fri, 25 Sep 2015 13:31:54 -0700 (PDT)
Received: by ioiz6 with SMTP id z6so122584547ioi.2 for <dispatch@ietf.org>; Fri, 25 Sep 2015 13:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=squKHOFRrWTHc8Hau9Yplvdh1QKBqqyOrWpj6NyCWCQ=; b=Z+0zcUAgEWSTFFmwYJgOdfFHCDaQJ14CTHb82CVdSR7tXpfogmVmx5tpW8jGTOF8A7 lfhy9x5QIkayayWsZB7oeMSTNBsEMHOlLZjvJBfgwQLy+FYp7SuTjdvROgeN3dc3gLAe 5cz9Zlb5XGcW5evA3GqVK/1c5O/Wg+YrPMTZLNWPc4/YSE4cFLdJVFJJnc/OTxq5T0LQ PEPjs/Blxmy/v0uKg7IlAXZUyRDU1qx9kErSM7QR7zDaOt/Nc7nJLCThpr0DM3s8enRP 1mnKl8XAOVSQZY64gRd1l3iMwKxb/Q0NSFjK7H8Ew1BALIWZtIOFrbbssbNtoCo5xcdY Ibzg==
MIME-Version: 1.0
X-Received: by 10.107.40.12 with SMTP id o12mr8453627ioo.84.1443213113657; Fri, 25 Sep 2015 13:31:53 -0700 (PDT)
Received: by 10.79.32.86 with HTTP; Fri, 25 Sep 2015 13:31:53 -0700 (PDT)
In-Reply-To: <56017B78.8732.31D9DCBE@fas_vm.surguttel.ru>
References: <56017B78.8732.31D9DCBE@fas_vm.surguttel.ru>
Date: Fri, 25 Sep 2015 15:31:53 -0500
Message-ID: <CAKhHsXF=O=FMD3edpaMJ9TUJFXuqcomwFUwfqh42QU+O41Tscg@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
Cc: DISPATCH <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141d150f993cb0520983c9a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/xGOjFiuTZXcLLxgSWvAsdab458Q>
X-Mailman-Approved-At: Fri, 25 Sep 2015 16:07:18 -0700
Subject: Re: [dispatch] Plan to Submit a Proposal for Opportunistic SRTP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 20:31:56 -0000

Hi Anton,

Glad you support the idea.

The approach described in draft-johnston-dispatch-osrtp is not identical to
that in draft-kaplan-mmusic-best-effort-srtp.  In the next version, we'll
include a section that discusses the differences.

The differences relate to the fact that OSRTP is based on and compliant
with Opportunistic Security defined in RFC 7435, while
draft-kaplan-mmusic-best-effort-srtp used something we used to call "best
effort SRTP" which predates OS by many years.  The other draft also has
lots of historical background and discussions of alternate approaches.  We
could decide to publish that information if we move forward with OSRTP, but
we thought it useful to leave it out in the initial versions of OSRTP to
show that the proposed approach is very simple with just a few normative
statements needed.

- Alan -

On Tue, Sep 22, 2015 at 11:02 AM, Anton Tveretin <fas_vm@surguttel.ru>
wrote:

> I fully support the idea. But this I-D seems to be a little more than a
> reference to
> draft-kaplan-mmusic-best-effort-srtp-01...
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>