Re: [Sipbrandy] OSRTP Question

Andy Hutton <andyhutton.ietf@gmail.com> Tue, 11 October 2016 18:36 UTC

Return-Path: <andyhutton.ietf@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 A0E5A129583 for <sipbrandy@ietfa.amsl.com>; Tue, 11 Oct 2016 11:36:49 -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 ESxaadCKZUpr for <sipbrandy@ietfa.amsl.com>; Tue, 11 Oct 2016 11:36:47 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 16ADE129569 for <sipbrandy@ietf.org>; Tue, 11 Oct 2016 11:36:47 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id i202so34327541ioi.2 for <sipbrandy@ietf.org>; Tue, 11 Oct 2016 11:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7vVYUrYzn5waNaE9M3DuPrKls6LIdFLIJJzcBlvjwz4=; b=zmuFruK3PNg7gJmimQqCSIkoYQ+Jdnd5YEgz2jeILJ0UVqOOHa0yxa8hQbPzoXwLSQ Ckhz1wzLC+cedLFgUnl8+e2ujzNxUBIJH5UA0EcXVOH7dMQ7ESY2izFFNFBgMRSeInEy DlzrzCAWndJXJFyf9gmo6fQ43UQaxhx0eH1plyv1KauhKPT5oWp3f2Z6CKHne8vM9Oiu aq8oHNMkMu6XpKjMsuvSDJOi9W+DWTAiOTQfIq5AHkVWoPzfGqqcuGnWlAs8F3ohOB4N TnaArhfEr+pmhY6e5LHuTiSByApYQK6EhlBvuF4s4MZ+tqYJxTJSl1ac/wLlgXY6H7Al GU7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7vVYUrYzn5waNaE9M3DuPrKls6LIdFLIJJzcBlvjwz4=; b=RMZb2nI4WSmZ5h/MwBl97hhiqdzLMgU0A+IqUIOrz37leg1HPxEkYrdhavrTNKaHDv JlAvvziNwN85UJWZTGXnEpDUE9OWuVe5hlfS+0c273cCa7XuUcb1xnk1i0paaU0JqKR1 Ypabtdj11QVtOG7d2XTCinzK8R6Jj3PlI3cM1cZZqX9WLp+A+BVv/G7cFOoznSihFBN2 6H+nevR3vYfQ1XOkyBEmwlISSW3mDtUPGyxG7MgoZV5GwOkpo37tQqSeKzoomX4TBPMg yLGRhw2wKr+6N3wBkwnxV8AsKnXh5PKOyQo+jNOCwUON7X567PfmZlkkb7Ac6QyxD64o +p2Q==
X-Gm-Message-State: AA6/9RkcQNAlMvFayTynfjgxb4iR0r9hLEtJp/xcpvAgDA5bC+HKmXv1OJA3x72nqLuOqKoLItppNT55+rPOug==
X-Received: by 10.107.131.213 with SMTP id n82mr7172972ioi.125.1476211006481; Tue, 11 Oct 2016 11:36:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.142.203 with HTTP; Tue, 11 Oct 2016 11:36:45 -0700 (PDT)
In-Reply-To: <faa15961-b5a3-d6dd-7845-ca6e28f2556c@ericsson.com>
References: <35CFE35E-E48B-419F-9557-B38A967CE797@nostrum.com> <7656b4d0-b529-46ce-787d-74debb0f1c9c@ericsson.com> <ce0d5592-ef96-ab56-2a56-cb4713e5f99d@ericsson.com> <CAB7PXwRLbzdrd00kmz0QUDQGr5OuRPec6-qSj0P=Th5c7cP3fw@mail.gmail.com> <faa15961-b5a3-d6dd-7845-ca6e28f2556c@ericsson.com>
From: Andy Hutton <andyhutton.ietf@gmail.com>
Date: Tue, 11 Oct 2016 19:36:45 +0100
Message-ID: <CAB7PXwQ-cLZoDm2J2iPQoc4NfCoH8ePXo5QurbPhnNRYmywdQw@mail.gmail.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: multipart/alternative; boundary="001a113ec50ca7b180053e9b287c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/JddA4YjX-nmJJJEtPteRkV_Yojw>
Cc: Ben Campbell <ben@nostrum.com>, sipbrandy@ietf.org
Subject: Re: [Sipbrandy] OSRTP Question
X-BeenThere: sipbrandy@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 11 Oct 2016 18:36:49 -0000

I am not aware that the OSRTP draft violates any normative statements about
using encryption with AVP although there was a discussion at IETF96 about
whether the SDP Answer should contain SAVP if the answerer recognised and
makes use of the a=crypto.

This is why an update to the OSRTP draft has been suggested such that the
answer may contain AVP or SAVP which I think we should accept and if we had
to choose between AVP or SAVP in the answer I think I would fall on the
SAVP side.

Regards
Andy


On Tue, Oct 11, 2016 at 2:17 PM, Gonzalo Camarillo <
Gonzalo.Camarillo@ericsson.com> wrote:

> Hi Andy,
>
> if you do not see any issue here, then you sure won't have any trouble
> responding to Ben's original question below, which is what the ADs are
> actually after, right? ;-) Thanks!
>
> Cheers,
>
> Gonzalo
>
> On 11/10/2016 3:56 PM, Andy Hutton wrote:
> > I am not sure what this issue is here I thought we were heading towards
> > consensus during IETF96 to make the OSRTP draft PS and get the AD's to
> > fix the charter.
> >
> > We discussed the possibility of splitting the draft and taking a small
> > draft to MMUSIC with the normative parts but I think we had consensus
> > that this did not make sense and we should just fix the charter,
> >
> > Regards
> > Andy
> >
> > On Fri, Oct 7, 2016 at 1:44 PM, Gonzalo Camarillo
> > <Gonzalo.Camarillo@ericsson.com <mailto:Gonzalo.Camarillo@ericsson.com>>
> > wrote:
> >
> >     All,
> >
> >     please, note that as you all know the SIPBRANDY WG is chartered not
> to
> >     produce PS specs. So, if we do not provide Ben with some arguments
> for
> >     making this draft PS, it will *not* be a PS. Comments?
> >
> >     https://datatracker.ietf.org/wg/sipbrandy/charter/
> >     <https://datatracker.ietf.org/wg/sipbrandy/charter/>
> >
> >     > The working group is not expected to define new protocols or modify
> >     > existing ones; rather it will define practices for using existing
> >     > protocols.
> >
> >     Thanks,
> >
> >     Gonzalo
> >
> >     On 23/09/2016 8:58 AM, Gonzalo Camarillo wrote:
> >     > Hi,
> >     >
> >     > for context, Ben's question relates to the following paragraph in
> the
> >     > minutes of the last SIPBRANDY session:
> >     >
> >     > https://www.ietf.org/proceedings/96/minutes/minutes-96-sipbrandy
> >     <https://www.ietf.org/proceedings/96/minutes/minutes-96-sipbrandy>
> >     >
> >     >> The group agreed on advancing the osrtp draft as Proposed
> >     >> Standard. However, the SIPBRANDY WG is not chartered to develop
> new
> >     >> protocol mechanisms. Ben, the resposible area director for the
> >     >> SIPBRANDY WG, will look into this and get back to the group with a
> >     >> final plan. In the meantime, the working assumption is that the
> >     >> intended status of the osrtp draft will be Proposed Standard.
> >     >
> >     > Cheers,
> >     >
> >     > Gonzalo
> >     >
> >     > On 23/09/2016 3:28 AM, Ben Campbell wrote:
> >     >> Hi,
> >     >>
> >     >> In the discussions about what status OSRTP should be, I was under
> the
> >     >> impression that people thought that the draft modified (or
> violated)
> >     >> some normative statement about using encryption with AVP rather
> than
> >     >> SAVP. Can anyone point me to the specifics?
> >     >>
> >     >> Thanks!
> >     >>
> >     >> Ben.
> >     >>
> >     >> _______________________________________________
> >     >> Sipbrandy mailing list
> >     >> Sipbrandy@ietf.org <mailto:Sipbrandy@ietf.org>
> >     >> https://www.ietf.org/mailman/listinfo/sipbrandy
> >     <https://www.ietf.org/mailman/listinfo/sipbrandy>
> >     >
> >
> >     _______________________________________________
> >     Sipbrandy mailing list
> >     Sipbrandy@ietf.org <mailto:Sipbrandy@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/sipbrandy
> >     <https://www.ietf.org/mailman/listinfo/sipbrandy>
> >
> >
>