Re: [MSEC] Application layer multicast security protocol

sampreeth ramavana <sampreeth@gmail.com> Thu, 25 August 2011 09:50 UTC

Return-Path: <sampreeth@gmail.com>
X-Original-To: msec@ietfa.amsl.com
Delivered-To: msec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036EC21F8562 for <msec@ietfa.amsl.com>; Thu, 25 Aug 2011 02:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgMlDuGUVsrw for <msec@ietfa.amsl.com>; Thu, 25 Aug 2011 02:50:07 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4E12421F850B for <msec@ietf.org>; Thu, 25 Aug 2011 02:50:07 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1889922gwb.31 for <msec@ietf.org>; Thu, 25 Aug 2011 02:51:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uUwlq4iDjrF8Q8yy9tst0dNqMtnfxBLEfVUTgRXiVuk=; b=s90VAfaIJfocExvkBABuEzwzHccBbjhgfsqJxrEjZQepF8dujGNGeXg/igC+vMwpXK rdYhfr0/njcVW6j+KmKp56CkOHNRtbPPJxYr8SUcXRkZLesoAHjjYYzoOzlekvADXIW7 Eh7CvlBselmd6gToTlqdI+CZ35ITphDO0ooaU=
MIME-Version: 1.0
Received: by 10.236.116.194 with SMTP id g42mr39177096yhh.0.1314265880195; Thu, 25 Aug 2011 02:51:20 -0700 (PDT)
Received: by 10.236.34.229 with HTTP; Thu, 25 Aug 2011 02:51:20 -0700 (PDT)
In-Reply-To: <1F9250DB00086D4E90A7FBC13C5EAF540F1847AA@de01exm70.ds.mot.com>
References: <CAODMbr0VCDd+m+3VunK8HOx1r+cmncQubWQAH0hCweVMqrpOzg@mail.gmail.com> <4E54A020.4020600@codelabs.ch> <1F9250DB00086D4E90A7FBC13C5EAF540F1847AA@de01exm70.ds.mot.com>
Date: Thu, 25 Aug 2011 15:21:20 +0530
Message-ID: <CAODMbr0pY8LxCeQWKQ-SrDmOy0q+0WnEBiQved_Z2po3ceZM=Q@mail.gmail.com>
From: sampreeth ramavana <sampreeth@gmail.com>
To: msec@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Lewis Adam-CAL022 <Adam.Lewis@motorolasolutions.com>
Subject: Re: [MSEC] Application layer multicast security protocol
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 09:50:08 -0000

Hi All,

Thanks for all the responses. SRTP along with MIKey/GDOI seems to fit
well. Are there any open source implementations on MIKey?

Also is SRTP tested if it is useful for streaming media. Am asking
this coz most of the references to SRTP were for VoIP applications.

Thanks,
Sampreeth

On Wed, Aug 24, 2011 at 5:44 PM, Lewis Adam-CAL022
<Adam.Lewis@motorolasolutions.com> wrote:
> You can also take a look at MIKEY (rfc3830).
>
> MIKEY can bootstrap SRTP/SRTCP, but it's really a very generic key
> transport protocol that transports a crypto key (could be a group key)
> from point A to point B.  Your application can use the key as it sees
> fit.
>
> adam
>
>
>
> -----Original Message-----
> From: msec-bounces@ietf.org [mailto:msec-bounces@ietf.org] On Behalf Of
> Adrian-Ken Rueegsegger
> Sent: Wednesday, August 24, 2011 1:54 AM
> To: sampreeth ramavana
> Cc: msec@ietf.org
> Subject: Re: [MSEC] Application layer multicast security protocol
>
> Hi Sampreeth,
>
> On 08/24/2011 07:35 AM, sampreeth ramavana wrote:
>> Hi All,
>>
>> Is there any multicast security protocol that can be implemented in
>> the application layer?
>>
>> I was seeing the GDOI protocol was mainly talking about implementing
>> using the IPSec at the IP layer. Can GDOI protocol also be useful if
>> implemented at application layer.
>
> GDOI can be extended to provide key material for other protocols. Mark,
> Sheela and I wrote a draft (which has since expired) which specifies the
> usage of GDOI with SRTP [1].
>
> Regards,
> Adrian
>
> [1] - http://tools.ietf.org/html/draft-ietf-msec-gdoi-srtp
> _______________________________________________
> MSEC mailing list
> MSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/msec
>



-- 
--------------------------
SAMPREETH
--------------------------