Re: [Sipbrandy] New Version Notification for draft-ietf-sipbrandy-osrtp-03.txt

Alan Johnston <alan.b.johnston@gmail.com> Wed, 20 September 2017 01:22 UTC

Return-Path: <alan.b.johnston@gmail.com>
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 <alan.b.johnston@gmail.com>
Date: Tue, 19 Sep 2017 21:22:35 -0400
Message-ID: <CAKhHsXEKtWc1YRbAZOH_xaR1WnSFPZcjSRNULu4-E-HGSbbGxg@mail.gmail.com>
To: sipbrandy@ietf.org
Cc: draft-ietf-sipbrandy-osrtp@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1c06468e34f8055994cfe3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/fd9cipaUeCEEacpW5M1R52CODTE>
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 <sipbrandy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipbrandy/>
List-Post: <mailto:sipbrandy@ietf.org>
List-Help: <mailto:sipbrandy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 01:22:40 -0000

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, <internet-drafts@ietf.org> 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
>
>