headers
Dan Wing | 11 May 2007 02:05
Picon
Favicon

RE: [Fwd: I-D ACTION:draft-wing-media-security-requirements-02.txt]


It's so quiet I don't even hear the crickets.

Is everyone satisified that -02 captures your requirements and that the
various DTLS specifications should move forward based on exactly those
requirements?

-d

> -----Original Message-----
> From: owner-ietf-rtpsec <at> mail.imc.org 
> [mailto:owner-ietf-rtpsec <at> mail.imc.org] On Behalf Of Hannes Tschofenig
> Sent: Friday, April 20, 2007 8:15 AM
> To: ietf-rtpsec <at> imc.org
> Subject: [Fwd: I-D 
> ACTION:draft-wing-media-security-requirements-02.txt]
> 
> 
> Another intermediate draft update...
> 
> -------- Original Message --------
> Subject: 	I-D ACTION:draft-wing-media-security-requirements-02.txt
> Date: 	Fri, 20 Apr 2007 10:50:02 -0400
> From: 	Internet-Drafts <at> ietf.org
> Reply-To: 	internet-drafts <at> ietf.org
> To: 	i-d-announce <at> ietf.org
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
(Continue reading)

Permalink | Reply | 0 comments |
headers
Cullen Jennings | 11 May 2007 19:42
Picon
Favicon
Gravatar

Plan for moving forward


Hi All,

I have talked to the RAI and SEC ADs and here is the rough plan for  
how I would like to move forward with this. I would like to split the  
work off into the following working groups.

TLS
Make any modifications that may be required to DTLS to allow DTLS to  
generate the keys for SRTP.

AVT
Describe how DTLS is used to key SRTP and how SRTP is used in  
combination with DTLS. This includes the issues of multiplexing DTLS  
and SRTP on one port. draft-mcgrew-tls-srtp will be the starting  
draft for this.

MMUSIC
Provide a scheme for transporting DTLS fingerprints in SDP offer/ 
answer (suspect this is already done but it not, MMUSIC does it).   
Provide a scheme that allow an offer to say it is willing to do SRTP  
or RTP but would prefer SRTP.  The ongoing draft-ietf-mmusic-sdp- 
media-capabilities work should meet this need.

RAI/SEC
Write overview document on how SIP UA can secure media using  
combination of DTLS/SRTP, SDP Fingerprint, Identity, Outbound, and  
Digest and TLS for SIP. This document will not describe new  
mechanisms, it just provides the roadmap of how they all fit  
together. Jon Peterson has the token to start this.
(Continue reading)

Permalink | Reply | 100 comments |
headers
Hannes Tschofenig | 29 May 2007 23:33
Picon

Media Security Requirements Draft


Hi all,

we have published another version of the requirements draft:
http://tools.ietf.org/id/draft-wing-media-security-requirements-03.txt

The changes in the draft are focused on the following requirement:

R27:   If SRTP keying is performed over the media path, the keying
           packets MUST NOT pass the RTP validity check defined in
           Appendix A.1 of [RFC3550 
<http://www.rfc-editor.org/rfc/rfc3550.txt>]

It seems that we are getting to an end with the requirements work.

Ciao
Hannes
Permalink | Reply | 18 comments |
headers
Hannes Tschofenig | 29 May 2007 23:33
Picon

Media Security Requirements Draft


Hi all,

we have published another version of the requirements draft:
http://tools.ietf.org/id/draft-wing-media-security-requirements-03.txt

The changes in the draft are focused on the following requirement:

R27:   If SRTP keying is performed over the media path, the keying
           packets MUST NOT pass the RTP validity check defined in
           Appendix A.1 of [RFC3550 
<http://www.rfc-editor.org/rfc/rfc3550.txt>]

It seems that we are getting to an end with the requirements work.

Ciao
Hannes
Permalink | Reply | 0 comments |

Gmane