IETF Logo Mail Archive

Re: [TICTOC] The draft for IPsec synchronization security

Xie Lei <xielei57471@huawei.com> Mon, 15 November 2010 07:03 UTC

Return-Path: <xielei57471@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 D38843A688E for <tictoc@core3.amsl.com>; Sun, 14 Nov 2010 23:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.594
X-Spam-Level:
X-Spam-Status: No, score=-0.594 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.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 Kd-wUB2uvkEc for <tictoc@core3.amsl.com>; Sun, 14 Nov 2010 23:03:17 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 620EB3A6C41 for <tictoc@ietf.org>; Sun, 14 Nov 2010 23:03:15 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LBW00621ZHLR1@szxga04-in.huawei.com> for tictoc@ietf.org; Mon, 15 Nov 2010 15:00:57 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LBW00CX0ZHLZV@szxga04-in.huawei.com> for tictoc@ietf.org; Mon, 15 Nov 2010 15:00:57 +0800 (CST)
Received: from x57471 ([10.111.16.81]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LBW005K9ZHK2R@szxml06-in.huawei.com> for tictoc@ietf.org; Mon, 15 Nov 2010 15:00:57 +0800 (CST)
Date: Mon, 15 Nov 2010 15:00:56 +0800
From: Xie Lei <xielei57471@huawei.com>
To: Jack Kohn <kohn.jack@gmail.com>
Message-id: <00a401cb8492$da18ef70$51106f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_184cV5pcuwbkJ0eDjm3oag)"
X-Priority: 3
X-MSMail-priority: Normal
References: <AANLkTi=M+JWv+REtvHMkc1+sAWZeSuWS1LiKNeqWV4CS@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: Mon, 15 Nov 2010 07:03:25 -0000


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