IETF Logo Mail Archive

Re: [MMUSIC] Thinking about best-effort encryption

Colin Perkins <csp@csperkins.org> Thu, 02 November 2006 22:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GflBD-0003AA-80; Thu, 02 Nov 2006 17:36:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GflBC-00036D-1i for mmusic@ietf.org; Thu, 02 Nov 2006 17:36:58 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GflBA-0001RA-OI for mmusic@ietf.org; Thu, 02 Nov 2006 17:36:58 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61241 helo=[192.168.0.3]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1GflB9-0005AN-3w; Thu, 02 Nov 2006 22:36:56 +0000
In-Reply-To: <0b2d01c6fecc$c0c0c480$c6666b80@amer.cisco.com>
References: <0b2d01c6fecc$c0c0c480$c6666b80@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <E0C6D238-050E-44CE-8328-DBDA8A873F9E@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Thinking about best-effort encryption
Date: Thu, 02 Nov 2006 22:36:52 +0000
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: MMusic <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

On 2 Nov 2006, at 22:17, Dan Wing wrote:
>> Regardless of which key management protocol we ultimately
>> choose, we need to sort the fundamental architectural issue of:
>>
>>    Does the signalling (SDP) have to reflect RTP/SAVP?
>
> This isn't just a question applicable to security -- this question is
> also applicable to all other RTP profiles with offer/answer, such as
> sending an offer where you want the RTP feedback profile (RTP/AVPF) if
> the answerer supports it, otherwise you will accept RTP without
> feedback (RTP/AVP).
>
> Applicable to security, I expect RTP/AVPFCC
> (draft-ietf-avt-tfrc-profile-06.txt) will also need an RTP/SAVPFCC
> profile (it handwaves at such a thing in its section 3.  Eventually
> there will be a profile for running RTP directly over DCCP, too
> (without UDP, as is done by draft-ietf-avt-tfrc-profile-06).

That'd be draft-ietf-dccp-rtp-01.txt

Colin

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email