[MSEC] multicast security protocols
sampreeth ramavana <sampreeth@gmail.com> Tue, 23 August 2011 10:00 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 B105921F87E2 for <msec@ietfa.amsl.com>; Tue, 23 Aug 2011 03:00:14 -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 RK7Um+cIpPJw for <msec@ietfa.amsl.com>; Tue, 23 Aug 2011 03:00:14 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 384E121F87D9 for <msec@ietf.org>; Tue, 23 Aug 2011 03:00:14 -0700 (PDT)
Received: by yxj17 with SMTP id 17so3525804yxj.31 for <msec@ietf.org>; Tue, 23 Aug 2011 03:01:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=q+LDW27fa+++muti0N9LqfgDH9XknzedH4wlscoqFEg=; b=X4PvY7YSzEzBQW8IzjwHyP5JF8qCEb3YV/OYu0B7zuhl+e2fv62/4afO+BweylVh/A SxX+G0HTZoghPm+Ae6XS5qL78VYxVeEOwRzK5gPpwFdJSsErTKXRDiXjk6/CPD/AmRL+ cPz4n1gG7PY1dSu7qtLkIZqoT67avfXHqBbnQ=
MIME-Version: 1.0
Received: by 10.236.154.199 with SMTP id h47mr21742950yhk.81.1314093681429; Tue, 23 Aug 2011 03:01:21 -0700 (PDT)
Received: by 10.236.34.229 with HTTP; Tue, 23 Aug 2011 03:01:21 -0700 (PDT)
Date: Tue, 23 Aug 2011 15:31:21 +0530
Message-ID: <CAODMbr1Q4AjkPNAdnNnAM-Z=QDN_qThixiah7tTRiOspFQJ7dg@mail.gmail.com>
From: sampreeth ramavana <sampreeth@gmail.com>
To: msec@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [MSEC] multicast security protocols
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: Tue, 23 Aug 2011 10:01:36 -0000
Hi, For implementing multicast security at the application layer which key management protocol is recommended, in terms of widely used, deployed and more secure. I could see RFC's for GDOI, MIKey and GSAKMP. Your inputs are greatly appreciated. Thanks, Sampreeth
- [MSEC] multicast security protocols sampreeth ramavana