Re: [MSEC] Review of draft-ietf-msec-tesla-for-alc-norm-05.txt

<L.Liang@surrey.ac.uk> Fri, 24 October 2008 09:07 UTC

Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE16F3A6A74; Fri, 24 Oct 2008 02:07:11 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25CA83A6A74 for <msec@core3.amsl.com>; Fri, 24 Oct 2008 02:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hoDd+cL55qYg for <msec@core3.amsl.com>; Fri, 24 Oct 2008 02:07:09 -0700 (PDT)
Received: from mail83.messagelabs.com (mail83.messagelabs.com [195.245.231.83]) by core3.amsl.com (Postfix) with SMTP id BFA813A6A6A for <msec@ietf.org>; Fri, 24 Oct 2008 02:07:08 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: L.Liang@surrey.ac.uk
X-Msg-Ref: server-9.tower-83.messagelabs.com!1224839306!53581985!6
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [131.227.102.140]
Received: (qmail 21961 invoked from network); 24 Oct 2008 09:08:29 -0000
Received: from ads40.surrey.ac.uk (HELO ads40.surrey.ac.uk) (131.227.102.140) by server-9.tower-83.messagelabs.com with SMTP; 24 Oct 2008 09:08:29 -0000
Received: from EVS-EC1-NODE1.surrey.ac.uk ([131.227.102.136]) by ads40.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.3959); Fri, 24 Oct 2008 10:08:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 10:08:30 +0100
Message-ID: <9AAD79EF034F824CA410417194F5F987097AFE@EVS-EC1-NODE1.surrey.ac.uk>
In-Reply-To: <490189D0.7030305@inrialpes.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MSEC] Review of draft-ietf-msec-tesla-for-alc-norm-05.txt
Thread-Index: Ack1tBb0sJ34AS32ShS9r9/SJAyEiwAA9cRQ
From: L.Liang@surrey.ac.uk
To: vincent.roca@inrialpes.fr
X-OriginalArrivalTime: 24 Oct 2008 09:08:27.0703 (UTC) FILETIME=[13AB7C70:01C935B8]
Cc: H.Cruickshank@surrey.ac.uk, msec@ietf.org, vincent.roca@inria.fr, aurelien.francillon@inria.fr, faurite@lcpc.fr
Subject: Re: [MSEC] Review of draft-ietf-msec-tesla-for-alc-norm-05.txt
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Hi, Vincent,
  Thanks a lot for your comments. We are working on them and will let
you know the answers as soon as possible.

Regards,
Lei

-----Original Message-----
From: msec-bounces@ietf.org [mailto:msec-bounces@ietf.org] On Behalf Of
Vincent Roca
Sent: 24 October 2008 09:40
To: Liang L Mr (CCSR)
Cc: Cruickshank HS Dr (CCSR); msec@ietf.org; vincent.roca@inria.fr;
aurelien.francillon@inria.fr; faurite@lcpc.fr
Subject: Re: [MSEC] Review of draft-ietf-msec-tesla-for-alc-norm-05.txt

Dear Lei,

Thanks a lot for your interest in TESLA and support.

Concerning your proposal, we don't agree with your idea,
but maybe we can discuss this offline.

Best regards,

  Vincent


L.Liang@surrey.ac.uk wrote:
> Dear Vincent, Aurelien and Faurite,
>   My name is Lei Liang from University of surrey, UK. As my colleague
> Dr. Haitham Cruickshank talked with Vincent in the last IETF meeting,
we
> are working on a new TESLA synchronization method while integrating
with
> FLUTE, which is built on ALC, in a UK EPSRC project called
> Satellite-Based Secure Multicast employing Hybrid Reliability. We
think
> your ID is definitely very interesting and we used it as a very
> important reference in our study. So you have our support here :).
>   The new synchronization method we proposed is trying to eliminate
the
> bidirectional channel requested by the direct synchronization as
stated
> in the TESLA RFC because the ALC does not need it, especially in a
> satellite network. It is trying to take use of the FDT function in the
> FLUTE protocol to deliver the TESLA bootstrapping message and the
> information needed for synchronization. This can be achieved as long
as
> the FDT is periodically broadcasted or mulicasted to a well-known
> address. This synchronization information is not a strong overhead but
> the interval index in which the source is when sending the
bootstrapping
> message. It can also solve the scalability problem on the source when
> the multicast group is big. We published our initial study in ICC'2008
> and are implementing and validating the method now. Please find the
> enclosed pdf version of the paper that has the detailed description. 
>   I hope it can provide some useful thought for your ID and your
> comments are more than welcome.
> 
> 
> Best regards,
> 
> Lei Liang

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec