[Sipbrandy] hello world (was re: New Version Notification for draft-peterson-sipbrandy-rtpsec-00.txt)

"Peterson, Jon" <jon.peterson@neustar.biz> Fri, 08 July 2016 23:25 UTC

Return-Path: <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 4953D12B01F for <sipbrandy@ietfa.amsl.com>; Fri, 8 Jul 2016 16:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 O1RAspTiuWv9 for <sipbrandy@ietfa.amsl.com>; Fri, 8 Jul 2016 16:25:52 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0b-0018ba01.pphosted.com [67.231.157.90]) (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 3A06212D529 for <sipbrandy@ietf.org>; Fri, 8 Jul 2016 16:25:52 -0700 (PDT)
Received: from pps.filterd (m0078668.ppops.net [127.0.0.1]) by mx0b-0018ba01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u68Mh7Hq011338 for <sipbrandy@ietf.org>; Fri, 8 Jul 2016 18:51:48 -0400
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by mx0b-0018ba01.pphosted.com with ESMTP id 2425d323mu-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT) for <sipbrandy@ietf.org>; Fri, 08 Jul 2016 18:51:47 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.94]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Fri, 8 Jul 2016 18:51:46 -0400
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "sipbrandy@ietf.org" <sipbrandy@ietf.org>
Thread-Topic: hello world (was re: New Version Notification for draft-peterson-sipbrandy-rtpsec-00.txt)
Thread-Index: AQHR2WtO33zy4QO7hk6gSo1LDURjng==
Date: Fri, 08 Jul 2016 22:51:46 +0000
Message-ID: <D3A57C91.1A583F%jon.peterson@neustar.biz>
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.104]
Content-Type: multipart/alternative; boundary="_000_D3A57C911A583Fjonpetersonneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-07-08_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607080223
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/dcDSwTvGGgQbDbua86ljJBjn7RI>
Subject: [Sipbrandy] hello world (was re: New Version Notification for draft-peterson-sipbrandy-rtpsec-00.txt)
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: Fri, 08 Jul 2016 23:25:54 -0000

I just posted a new version of the RTPSEC draft, now branded for the brand-new SIPBRANDY working group. For those just joining us, this specification is intended to define best practices for SIP user agents to keep media confidential, with special concern for the threat of pervasive monitoring. As such, this is mostly an umbrella draft collecting existing work and explaining how these pieces come together to provide the needed properties. You can find the draft here:

<https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt><https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt>https://www.ietf.org/id/draft-peterson-sipbrandy-rtpsec-00.txt

Notable changes from the previous (dispatch) version include the following:

- As we heard some interest in making sure this played well with conferencing, there's now a mandate for perc-double, though not much supporting text yet.

- There's now a mandate for ICE, and moreover for STUN consent freshness, as we heard some concern about voice hammering and related attacks.

- The draft now permits the use of self-signed keys to sign rfc4474bis within a "STIR profile for media confidentiality", which also requires that UAs implement the authentication and verification service roles of STIR. That entailed a number of related behaviors.

- There's some tentative text about the interaction between rfc4916 connected identity, ICE, and rfc4474bis, though this clearly requires some more thinking. For now I'm happy to just have some preliminary text there.

- Perhaps most notably, the draft mandates support for DTLS-SRTP, and makes support for other confidentiality mechanisms optional.

At this stage, I want to make sure we've captured the requirements space, and that we're not missing anything in terms of behavior we need to incorporate. But certainly we'd be happy to hear any other comments about the draft.

Jon Peterson
Neustar, Inc.