IETF Logo Mail Archive

Re: [TICTOC] The draft for IPsec synchronization security

"Greg Dowd" <GDowd@symmetricom.com> Fri, 03 December 2010 00:59 UTC

Return-Path: <btv1==953f33c537b==GDowd@symmetricom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CF1E3A6403 for <tictoc@core3.amsl.com>; Thu, 2 Dec 2010 16:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level:
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 BD0hP899vXDw for <tictoc@core3.amsl.com>; Thu, 2 Dec 2010 16:59:18 -0800 (PST)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by core3.amsl.com (Postfix) with ESMTP id 51CBC3A6836 for <tictoc@ietf.org>; Thu, 2 Dec 2010 16:59:18 -0800 (PST)
X-ASG-Debug-ID: 1291338033-5aa92b2f0001-4wH9i1
Received: from sjowa.symmetricom.com ([192.168.10.41]) by mail5.symmetricom.com with ESMTP id 8B1G6Ip6LWQgN8gG; Thu, 02 Dec 2010 17:00:33 -0800 (PST)
X-Barracuda-Envelope-From: GDowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from sjmail2.symmetricom.com ([192.168.10.66]) by sjowa.symmetricom.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 2 Dec 2010 17:00:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 Dec 2010 17:00:32 -0800
X-ASG-Orig-Subj: RE: [TICTOC] The draft for IPsec synchronization security
Message-ID: <CB45EB047BD43041BF1F4CC7D6DB21BF05DF6B26@sjmail2.symmetricom.com>
In-Reply-To: <AANLkTikeXMTm+kMt4E-gC8ygyxCxoYwCTPqrpqWG8b+S@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [TICTOC] The draft for IPsec synchronization security
Thread-Index: AcuSg9N0T/yT38xWSnKJ0xjZX3f75gAAYm0A
References: <AANLkTi=M+JWv+REtvHMkc1+sAWZeSuWS1LiKNeqWV4CS@mail.gmail.com><00a401cb8492$da18ef70$51106f0a@china.huawei.com> <AANLkTikeXMTm+kMt4E-gC8ygyxCxoYwCTPqrpqWG8b+S@mail.gmail.com>
From: Greg Dowd <GDowd@symmetricom.com>
To: Jack Kohn <kohn.jack@gmail.com>, Xie Lei <xielei57471@huawei.com>
X-OriginalArrivalTime: 03 Dec 2010 01:00:33.0820 (UTC) FILETIME=[7D26EDC0:01CB9285]
X-Barracuda-Connect: UNKNOWN[192.168.10.41]
X-Barracuda-Start-Time: 1291338033
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] The draft for IPsec synchronization security
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Dec 2010 00:59:48 -0000

I believe the goal was not to suggest a method for adding security but a method for handling the security imposed by the LTE standard for femto.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Jack Kohn
Sent: Thursday, December 02, 2010 4:49 PM
To: Xie Lei
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] The draft for IPsec synchronization security

Xie,

Is there a reason why you cant use the Security mechanism described in
Annex K of IEEE std 1588-2008?

Jack

On Mon, Nov 15, 2010 at 12:30 PM, Xie Lei <xielei57471@huawei.com> wrote:
>
>
> Hi Jack
>
> Thanks for your information, i had discussed with RFC5840 authors in IETF
> 79# meeting. It is possible to use RFC5840 to fulfill this synchronization
> requirements. I will follow the progress and provide more information to
> Tictoc group.
>
> BR
>
> Rock
>
> ----- Original Message -----
> From: Jack Kohn
> To: xielei57471@huawei.com ; tictoc@ietf.org
> Sent: Saturday, November 13, 2010 12:30 PM
> Subject: RE: The draft for IPsec synchronization security
> Xie:
>
> While i understand your motivation to secure the timing packets, you
> really dont need the extensions that you have defined in the below
> draft. You must look at RFC 5840 that extends ESP and see how that can
> be used for achieving the same functionality as you desire.
>
> Jack
>
>> Hi Yaakov and all
>> Huawei has submitted one draft for IPSec synchronization security, you can
>> find it in following link
>>
>> http://www.ietf.org/id/draft-xu-tictoc-ipsec-security-for-synchronization-00.txt
>>
>> We also attach one discussion document in this email, i hope we can
>> present it in IETF Beijing meeting.
>>
>> BR
>> Rock
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

v2.23.0 | Report a Bug | By Email