IETF Logo Mail Archive

Re: [TICTOC] The draft for IPsec synchronization security

Jack Kohn <kohn.jack@gmail.com> Sat, 13 November 2010 04:30 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 A9BAE3A6947 for <tictoc@core3.amsl.com>; Fri, 12 Nov 2010 20:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level:
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[AWL=1.110, BAYES_00=-2.599]
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 9o+Fb-fZnedC for <tictoc@core3.amsl.com>; Fri, 12 Nov 2010 20:30:23 -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 F1A483A67D0 for <tictoc@ietf.org>; Fri, 12 Nov 2010 20:30:22 -0800 (PST)
Received: by iwn40 with SMTP id 40so4524876iwn.31 for <tictoc@ietf.org>; Fri, 12 Nov 2010 20:30:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=zWv9kIawYOO0wxuS6/RKQr3VovPaXhlryhBtCBh4Fcc=; b=OTiyIl3Avt2xSKO4hMXU9VGo7DWoBYkYOsbjtutfL+8XNBEl7HYNxCVfdFAYmekD8B /a7o7lBIRBxULz729Z1BaRHSW05/BykzBnnqaZ7RhhAvWSvQJRsVJxy2DcLyUihOuOh1 3a056Yta5qY6U6quHvIM3cV+xoZHNjhl0SERY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=J9KBiWJhS4Diee0GMF5jy9RiK8VdYz9f94FlffnkIeiyAz1XHrhnQtXVDiEUmjgrJf O+YheGHnLeybp15QkOxSchwtwMJ1dS9s/b+d+ZkhhZNo2jqqI18X/0Hv9kZ88fcFB3et Ewsk0Qq2LB/HXGxeS++3Imi7fhyK2F5E+0XZw=
MIME-Version: 1.0
Received: by 10.231.36.11 with SMTP id r11mr2690682ibd.125.1289622657341; Fri, 12 Nov 2010 20:30:57 -0800 (PST)
Received: by 10.231.167.81 with HTTP; Fri, 12 Nov 2010 20:30:57 -0800 (PST)
Date: Sat, 13 Nov 2010 10:00:57 +0530
Message-ID: <AANLkTi=M+JWv+REtvHMkc1+sAWZeSuWS1LiKNeqWV4CS@mail.gmail.com>
From: Jack Kohn <kohn.jack@gmail.com>
To: xielei57471@huawei.com, tictoc@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
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: Sat, 13 Nov 2010 04:30:26 -0000

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