[Sip] Announcement of Real Time Security list
"Peterson, Jon" <jon.peterson@neustar.biz> Wed, 12 April 2006 18:13 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTjpx-0004YX-EY; Wed, 12 Apr 2006 14:13:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTjpv-0004Y7-Ah; Wed, 12 Apr 2006 14:13:03 -0400
Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTjpu-0007PC-2a; Wed, 12 Apr 2006 14:13:03 -0400
Received: from stntsmtp1.cis.neustar.com (smartexch.neustar.com [10.31.13.79]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k3CID1BW021739; Wed, 12 Apr 2006 18:13:01 GMT
Received: from stntexch03.cis.neustar.com ([10.31.13.45]) by stntsmtp1.cis.neustar.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Apr 2006 14:13:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Apr 2006 14:13:00 -0400
Message-ID: <24EAE5D4448B9D4592C6D234CBEBD597054F43E6@stntexch03.cis.neustar.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Announcement of Real Time Security list
Thread-Index: AcZeXHrJfzAz66E3Q72gu3thk4IDNQ==
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: sip@ietf.org, sipping@ietf.org, mmusic@ietf.irg, avt@ietf.org, msec@ietf.org
X-OriginalArrivalTime: 12 Apr 2006 18:13:01.0030 (UTC) FILETIME=[BBF90860:01C65E5C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: fluffy@cisco.com
Subject: [Sip] Announcement of Real Time Security list
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
Following our discussion in the RAI Open Area Meeting in Dallas a few weeks ago on the many strategies circulating for securing RTP, we've formed a new mailing list in order to further refine our understanding of the problem space and figure out a way forward.
Subscription information for the list is available here.
<http://www.imc.org/ietf-rtpsec/>
The agenda item from the RAI Open Meeting, including the list of associated drafts, is pasted below. Interested parties, please move discussion of these documents to this list.
Jon Peterson
NeuStar, Inc.
----
There are many proposal discussing keying for RTP when used with SIP.
These issues cross SIPPING, MMUSIC, AVT, and MSEC.
What are the common underling requirements driving these proposals?
At the high level what are the various architectures?
What cross WG architectural level question do we need to answer?
Can we come to consensus on high level approaches we would like to
investigate?
RFC 3830 (MIKEY)
RFC 3711 (SRTP)
draft-ietf-msec-mikey-rsa-r-02
draft-ietf-mmusic-sdescriptions-12
draft-ietf-mmusic-kmgmt-ext-15
draft-wing-mmusic-sdes-early-media-00
draft-mcgrew-srtp-ekt-00
draft-baugher-mmusic-sdp-dh-00
draft-zimmerman-avt-zrtp-00
draft-tschofenig-avt-rtp-dtls-00
draft-fischl-sipping-media-dtls-0
draft-fischl-mmusic-sdp-dtls-00
draft-rescorla-tls-partial-00
draft-modadugu-dtls-short-00
draft-fries-msec-mikey-applicability-00
draft-ietf-msec-mikey-dhhmac-11
draft-lehtovirta-srtp-rcc-01
draft-saito-mmusic-ipsec-negotiation-req-02
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip
- [Sip] Announcement of Real Time Security list Peterson, Jon