Re: [TICTOC] The draft for IPsec synchronization security

Michel Ouellette <michel.ouellette@huawei.com> Fri, 03 December 2010 18:48 UTC

Return-Path: <michel.ouellette@huawei.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 AD3B828C0CE for <tictoc@core3.amsl.com>; Fri, 3 Dec 2010 10:48:36 -0800 (PST)
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 i3QUiQs4xA4A for <tictoc@core3.amsl.com>; Fri, 3 Dec 2010 10:48:35 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id BF9053A698A for <tictoc@ietf.org>; Fri, 3 Dec 2010 10:48:35 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LCV006N88B4MQ@usaga02-in.huawei.com> for tictoc@ietf.org; Fri, 03 Dec 2010 10:49:53 -0800 (PST)
Received: from LapMOuellette ([10.193.133.201]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LCV00CBT8B48P@usaga02-in.huawei.com> for tictoc@ietf.org; Fri, 03 Dec 2010 10:49:52 -0800 (PST)
Date: Fri, 03 Dec 2010 13:49:52 -0500
From: Michel Ouellette <michel.ouellette@huawei.com>
In-reply-to: <AANLkTi=EXtnP5YO_qPEGk_yO3_K0qwXF2dVB7AcADaG0@mail.gmail.com>
To: 'Jack Kohn' <kohn.jack@gmail.com>
Message-id: <082B1A87E77649DEB574DD78E5F160D2@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
Thread-index: AcuTFbYq1oRRrk6iRJCl+jOnjVT6cAAAkSSw
References: <AANLkTi=M+JWv+REtvHMkc1+sAWZeSuWS1LiKNeqWV4CS@mail.gmail.com> <00a401cb8492$da18ef70$51106f0a@china.huawei.com> <AANLkTikeXMTm+kMt4E-gC8ygyxCxoYwCTPqrpqWG8b+S@mail.gmail.com> <CB45EB047BD43041BF1F4CC7D6DB21BF05DF6B26@sjmail2.symmetricom.com> <AANLkTi=EXtnP5YO_qPEGk_yO3_K0qwXF2dVB7AcADaG0@mail.gmail.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 18:48:36 -0000

Hi Jack,

Have a look at the following two internet-drafts for reference
http://tools.ietf.org/html/draft-xie-tictoc-femtocell-analysis-00
http://tools.ietf.org/html/draft-xu-tictoc-ipsec-security-for-synchronizatio
n-00

an example is 3GPP, "Security of Home Node B (HNB) / Home evolved Node B
(HeNB)", 3GPP TR 33.820 8.1.0, June 2009.

As Greg said, note that Annex K of IEEE1588 is an informative and
experimental Annex and might not represent the requirements of a particular
application like femtocells.

Can you clarify what you mean by "we need to provide security between the
master and the boundary clocks"?

Who is "we" and why do you think there is a need for security between a GM
and BC?

Bye.

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of
Jack Kohn
Sent: December 03, 2010 01:12 PM
To: Greg Dowd
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] The draft for IPsec synchronization security

Any pointers on where i can get the LTE standard for femto?

I was under the impression that this would also be used by 1588 for
delivering a solution for frequency distribution, when we need to
provide security between the master and the boundary clocks, etc.

On Fri, Dec 3, 2010 at 6:30 AM, Greg Dowd <GDowd@symmetricom.com> wrote:
> 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
>
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc