IETF Logo Mail Archive

Re: [Sipbrandy] Status of our drafts

"Peterson, Jon" <jon.peterson@neustar.biz> Thu, 04 May 2017 20:23 UTC

Return-Path: <prvs=0297f065b3=jon.peterson@neustar.biz>
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 1618F126BF0 for <sipbrandy@ietfa.amsl.com>; Thu, 4 May 2017 13:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=neustar.biz
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 5RC9xJy2pwpb for <sipbrandy@ietfa.amsl.com>; Thu, 4 May 2017 13:23:39 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 5DA2B127977 for <sipbrandy@ietf.org>; Thu, 4 May 2017 13:23:39 -0700 (PDT)
Received: from pps.filterd (m0078666.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v44KDMeP017359; Thu, 4 May 2017 16:23:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=neustar-biz; bh=6mQIpa7x9wC0P1si26Rb7A7A10FsjEi6F3UjA1/ArBw=; b=KdFEfqKGJQLjKJ3rTEGeu45Ve+j4f9+sYKrGiCZ8KL/86xi7/tXUie9DlEB/ma91GYBO ZbLbVN3ahRpwn1Q7jtAfn0a1YIbPn8DN5kRzJ61gdcYgaDWxnyUc26gdSuWeG6u/jmii TN/LaO7M+zzVZWyjpJ3dM55WAD+DjDPg3kX5Snix0WWXR2Eb+XKs4mN6U6IreDl+TlEZ p5EPXRD15qK71Taf6Z3+kRNZpVkQPJ19n4Te/52Mc3J97L1ZUrl7OY9VvtyP/c6XSh2e 3XGTYC352k1s/F1XehnJsG+Vl/S9RLr1+/NjokqQjglQti92A3E0NHdCi9BAi8UfgymV kg==
Received: from stntexhc10.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 2a72qhc9y4-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 04 May 2017 16:23:34 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.33]) by stntexhc10.cis.neustar.com ([169.254.4.170]) with mapi id 14.03.0279.002; Thu, 4 May 2017 16:23:32 -0400
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "sipbrandy@ietf.org" <sipbrandy@ietf.org>
Thread-Topic: [Sipbrandy] Status of our drafts
Thread-Index: AQHSiDPbX+QGh5qrxUua6j2r0pa6aKGYC9IAgE0MWgA=
Date: Thu, 04 May 2017 20:23:31 +0000
Message-ID: <D530FB31.1D979C%jon.peterson@neustar.biz>
References: <55773ace-3e3e-16b9-003d-7256e42342c8@ericsson.com> <a582e34c-c20b-374a-177a-97a425846d15@ericsson.com>
In-Reply-To: <a582e34c-c20b-374a-177a-97a425846d15@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [10.96.12.176]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25FD4562A2338F4DABD0DEB19C49417C@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-04_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705040292
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/MXnhZXH7EH4K5ktmYm2jlVr_Fmo>
Subject: Re: [Sipbrandy] Status of our drafts
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: Thu, 04 May 2017 20:23:42 -0000

Hello,

Although we did not meet in Chicago, I did submit a new version of
draft-ietf-sipbrandy-rtpsec before the meeting. This incorporated the
feedback from the previous session, as well as some other points that had
come up related to Adam Roach's comments on the interaction with connected
identity.

I have had one offline discussion recently about the need to get connected
identity right for core STIR, not exclusively for use with the SIPBRANDY
profile of STIR. I think there are probably some good reasons to try to
get that properly defined. We had talked a bit here about trying to patch
RFC4916 for STIR in the context of this working group, but probably I'll
submit that as an individual and at some point we can decide where that
work should live. The RTPSEC draft here should probably reference that
patch to connected identity. But other than that, I'm not sure I have a
lot of outstanding action items for the RTPSEC document. We set out to
define a pretty simple profile, just kind of a framework document for how
you combine a bunch of things we've defined elsewhere, and at this point I
think the big ideas are in place.

Jon Peterson
Neustar, Inc.

On 3/16/17, 11:47 AM, "Sipbrandy on behalf of Gonzalo Camarillo"
<sipbrandy-bounces@ietf.org on behalf of Gonzalo.Camarillo@ericsson.com>
wrote:

>Authors,
>
>could you please send us a status update per my email below?
>
>Thanks,
>
>Gonzalo
>
>On 16/02/2017 11:05 AM, Gonzalo Camarillo wrote:
>> Hi,
>> 
>> even if we will not have a SIPBRANDY session in Chicago, it would be
>> useful for the working group to discuss what are the next steps on the
>>list.
>> 
>> To start those discussions, we would like to ask the authors of our two
>> working group items below to let the list know what is the status of
>> their draft and what are the next steps:
>> 
>> https://datatracker.ietf.org/doc/draft-ietf-sipbrandy-osrtp/
>> https://datatracker.ietf.org/doc/draft-ietf-sipbrandy-rtpsec/
>> 
>> We would also like to ask the authors of the MMUSIC draft below, which
>> is related to the SIPBRANDY work, to give us a status update:
>> 
>> 
>>https://datatracker.ietf.org/doc/draft-hutton-mmusic-opportunistic-negoti
>>ation/
>> 
>> Thanks,
>> 
>> Gonzalo
>> 
>> _______________________________________________
>> Sipbrandy mailing list
>> Sipbrandy@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipbrandy
>> 
>
>_______________________________________________
>Sipbrandy mailing list
>Sipbrandy@ietf.org
>https://www.ietf.org/mailman/listinfo/sipbrandy

v2.23.0 | Report a Bug | By Email