IETF Logo Mail Archive

Re: [TICTOC] The draft for IPsec synchronization security

Jack Kohn <kohn.jack@gmail.com> Fri, 03 December 2010 00:47 UTC

Return-Path: <kohn.jack@gmail.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 A19BE3A6A24 for <tictoc@core3.amsl.com>; Thu, 2 Dec 2010 16:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.729
X-Spam-Level:
X-Spam-Status: No, score=-2.729 tagged_above=-999 required=5 tests=[AWL=0.870, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 XwrJQfUOeGAY for <tictoc@core3.amsl.com>; Thu, 2 Dec 2010 16:47:18 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id AEDF13A6A22 for <tictoc@ietf.org>; Thu, 2 Dec 2010 16:47:18 -0800 (PST)
Received: by iwn40 with SMTP id 40so10950546iwn.31 for <tictoc@ietf.org>; Thu, 02 Dec 2010 16:48:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xzYmvf5rosbtrsAFwdbF612APyD/oDbaRbqW8Ywd2x0=; b=QLlhBOGUb6YRh4kv8m5DxaeA55EkveFA0ga+CdC0dOUwNJBChLmu/HriSTca7UZw0L yp+BOnGXBHsjq+KfkJbrTbHon+B5UKwTNhroPzOqxA+qrGsRXfGCtqtK4ZvPHXSjKhyz mrZo2mFk/Q48ndpbx4VnilxZYYdvZzUmUqaCg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CqxbsvTIOhfWzVA8NMuHwQ//+k8zZb+k3tNfkja7BjuU9lBUEsC1U8mTVJDlZryVLl CixSe2zHWM+AMVjNTF/KHpcqCBEQM6GuiKNo+ZFFikXA+lYAP/SfVn0qc9W/tnJ3Tpww LhokYC63OQQgYCAxa1bKYUiLW+WvL8h2YemEI=
MIME-Version: 1.0
Received: by 10.231.19.139 with SMTP id a11mr1012798ibb.81.1291337314123; Thu, 02 Dec 2010 16:48:34 -0800 (PST)
Received: by 10.231.187.162 with HTTP; Thu, 2 Dec 2010 16:48:34 -0800 (PST)
In-Reply-To: <00a401cb8492$da18ef70$51106f0a@china.huawei.com>
References: <AANLkTi=M+JWv+REtvHMkc1+sAWZeSuWS1LiKNeqWV4CS@mail.gmail.com> <00a401cb8492$da18ef70$51106f0a@china.huawei.com>
Date: Fri, 03 Dec 2010 06:18:34 +0530
Message-ID: <AANLkTikeXMTm+kMt4E-gC8ygyxCxoYwCTPqrpqWG8b+S@mail.gmail.com>
From: Jack Kohn <kohn.jack@gmail.com>
To: Xie Lei <xielei57471@huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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:47:19 -0000

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

v2.23.0 | Report a Bug | By Email