
From kevin.gross@avanw.com  Wed Apr 24 17:15:09 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18C221F870F for <tictoc@ietfa.amsl.com>; Wed, 24 Apr 2013 17:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.514
X-Spam-Level: *
X-Spam-Status: No, score=1.514 tagged_above=-999 required=5 tests=[AWL=1.328,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNScy48hnzRw for <tictoc@ietfa.amsl.com>; Wed, 24 Apr 2013 17:15:07 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 83F8C21F86EA for <tictoc@ietf.org>; Wed, 24 Apr 2013 17:15:03 -0700 (PDT)
Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta01.emeryville.ca.mail.comcast.net with comcast id Tst01l00t1bwxycA10F3bk; Thu, 25 Apr 2013 00:15:03 +0000
Received: from mail-ie0-x236.google.com ([IPv6:2607:f8b0:4001:c03::236]) by omta18.emeryville.ca.mail.comcast.net with comcast id U0F21l00e251pGM8e0F32p; Thu, 25 Apr 2013 00:15:03 +0000
Received: by mail-ie0-f182.google.com with SMTP id bn7so2912826ieb.13 for <tictoc@ietf.org>; Wed, 24 Apr 2013 17:15:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=UnUl907w2dfKUtQKQlgb0Xw+yn94cTNEwhFP4+8VAUA=; b=dvZf0N8QoynD/RMaVKjkozFWX/sOK3Ww8j8m60lrKop0AfB/1gfeL0MIxRbLkKLzso 64NMytqWe2NxCmfgwEhrOPCmo/s3D4JcorLb1tUsU/yd826W/A5QwzRYFSOEzKwZwfBa Xy1nG4xhL4AsU0qfi1umuvX24yqitsJD1Jtc1oDY2k5eaPNZpwt+vww752ruJdq473bY emaw+HGBYcdOK4YmovKHsPPQ5rYr7geyVzBHAMG/WpmltoMvQDzW5kkYZZjsGPVzAov6 SdClsIMqPxEEFuQQlhIKQWTZwaFSmQ3tiA7FXw6CQESHMCON8t5ieNoBcmicHr+N7q1x gqkw==
MIME-Version: 1.0
X-Received: by 10.50.108.235 with SMTP id hn11mr22871217igb.107.1366848902564;  Wed, 24 Apr 2013 17:15:02 -0700 (PDT)
Received: by 10.50.180.201 with HTTP; Wed, 24 Apr 2013 17:15:02 -0700 (PDT)
In-Reply-To: <CALw1_Q2SbZpPrOptB7g5g7Cq-3DM9A83M-ufnfby9CYW3v6=Ug@mail.gmail.com>
References: <D2CC4074A4E35B43A4EE2CA7859D567B75169077@SJC-MBX-01.symmetricom.com> <512C0C00.7050906@pobox.com> <CALw1_Q2SbZpPrOptB7g5g7Cq-3DM9A83M-ufnfby9CYW3v6=Ug@mail.gmail.com>
Date: Wed, 24 Apr 2013 18:15:02 -0600
Message-ID: <CALw1_Q3EfKn+Arkjy0RwyC7Ut=6bSKpJQqfrfKct9y7GLjkYmQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Karen ODonoghue <kodonog@pobox.com>
Content-Type: multipart/alternative; boundary=f46d0402aeef4c954604db244f3f
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366848903; bh=UnUl907w2dfKUtQKQlgb0Xw+yn94cTNEwhFP4+8VAUA=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=fqgPg7hhyfQFadMqxmcviJMNo+QqQo90zBtUHaCWXHgdHpaxkCCUzSdE6mzAtgoQj KOiDB93zcKpV87xi1rKg/ErSvhnFWog67imNavwxwrm87IcGmZHODFj0muuDnd0LFA g+obbNd/7OnEm/dT6yVZh2gqyhk8RDmXSoYVpc8t2ov3j6MgFUKLOM13vrceH+dFkW GQDb5HhjLICSwQA3jd3mAcIzAKawtfXqBtr8JREXgUfL9H1ljPljeYMOdm3JINF+Jb X+LRctVYE87aeO0tkWhBM/MgWfIaqQSpzwKSiwjDoGthOw+rNJYMTDw11qjH0+Ks/E kUBJpach5iABw==
Cc: "TICTOC@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] PTP Enterprise Profile draft
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 25 Apr 2013 00:15:09 -0000

--f46d0402aeef4c954604db244f3f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I did not see a response from anyone. Is there a snag in this work or can I
refer people to the copy in the email archive -
http://www.ietf.org/mail-archive/web/tictoc/current/msg01356.html?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Mar 18, 2013 at 1:41 PM, Kevin Gross <kevin.gross@avanw.com> wrote:

> Can we get this draft submitted to the I-D system. I'd like to direct som=
e
> more eyeballs at it and that's cumbersome to do as an e-mail attachment.
>
> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org
>
>
> On Mon, Feb 25, 2013 at 6:12 PM, Karen O'Donoghue <kodonog@pobox.com>wrot=
e:
>
>>  TICTOC working group members,
>>
>> This document will be on the agenda for the upcoming meeting in Orlando.
>> Because of incomplete guidance from me as working group co-chair, the
>> document was not submitted correctly and will not be in the internet-dra=
fts
>> repository in time for the meeting. I will provide a link to the email
>> including the document as part of the meeting agenda. Please review and
>> come prepared to discuss the contents.
>>
>> Regards,
>> Karen
>>
>>
>>
>> On 2/25/13 4:52 PM, Doug Arnold wrote:
>>
>>  Here is a first cut at a draft of a PTP profile foe enterprise
>> networks.  Any feedback/suggestions would be much appreciated.  ****
>>
>> ** **
>>
>> I enclose both a MS Word version and a pure text version, since I used
>> the Joe Touch=92s template.****
>>
>> ** **
>>
>> //Doug****
>>
>> ** **
>>
>>
>> _______________________________________________
>> TICTOC mailing listTICTOC@ietf.orghttps://www.ietf.org/mailman/listinfo/=
tictoc
>>
>>
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>>
>

--f46d0402aeef4c954604db244f3f
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I did not see a response from anyone. Is there a snag in t=
his work or can I refer people to the copy in the email archive -=A0<a href=
=3D"http://www.ietf.org/mail-archive/web/tictoc/current/msg01356.html">http=
://www.ietf.org/mail-archive/web/tictoc/current/msg01356.html</a>?</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div>Kevin Gross<br><div>+1-30=
3-447-0517</div><div>Media Network Consultant<br><div>AVA Networks -=A0<a h=
ref=3D"http://www.avanw.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a hre=
f=3D"http://www.X192.org" target=3D"_blank">www.X192.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Mon, Mar 18, 2013 at 1:41 PM, Kevin G=
ross <span dir=3D"ltr">&lt;<a href=3D"mailto:kevin.gross@avanw.com" target=
=3D"_blank">kevin.gross@avanw.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
Can we get this draft submitted to the I-D system. I&#39;d like to direct s=
ome more eyeballs at it and that&#39;s cumbersome to do as an e-mail attach=
ment.<div><span class=3D"HOEnZb"><font color=3D"#888888"><br clear=3D"all">=
<div>
Kevin Gross<br><div><a href=3D"tel:%2B1-303-447-0517" value=3D"+13034470517=
" target=3D"_blank">+1-303-447-0517</a></div>
<div>Media Network Consultant<br><div>AVA Networks -=A0<a href=3D"http://ww=
w.avanw.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.=
X192.org" target=3D"_blank">www.X192.org</a></div></div></div></font></span=
><div><div class=3D"h5">

<br><br><div class=3D"gmail_quote">On Mon, Feb 25, 2013 at 6:12 PM, Karen O=
&#39;Donoghue <span dir=3D"ltr">&lt;<a href=3D"mailto:kodonog@pobox.com" ta=
rget=3D"_blank">kodonog@pobox.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">


 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>TICTOC working group members,<br>
      <br>
      This document will be on the agenda for the upcoming meeting in
      Orlando. Because of incomplete guidance from me as working group
      co-chair, the document was not submitted correctly and will not be
      in the internet-drafts repository in time for the meeting. I will
      provide a link to the email including the document as part of the
      meeting agenda. Please review and come prepared to discuss the
      contents. <br>
      <br>
      Regards,<br>
      Karen<div><div><br>
      <br>
      <br>
      On 2/25/13 4:52 PM, Doug Arnold wrote:<br>
    </div></div></div>
    <blockquote type=3D"cite"><div><div>
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal">Here is a first cut at a draft of a PTP
          profile foe enterprise networks.=A0 Any feedback/suggestions
          would be much appreciated.=A0
          <u></u><u></u></p>
        <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
        <p class=3D"MsoNormal">I enclose both a MS Word version and a pure
          text version, since I used the Joe Touch=92s template.<u></u><u><=
/u></p>
        <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
        <p class=3D"MsoNormal">//Doug<u></u><u></u></p>
        <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>_______________________________________________
TICTOC mailing list
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div>

--f46d0402aeef4c954604db244f3f--

From internet-drafts@ietf.org  Thu Apr 25 06:30:55 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88D121F960D; Thu, 25 Apr 2013 06:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eBj91Xyp1z5; Thu, 25 Apr 2013 06:30:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5871221F8976; Thu, 25 Apr 2013 06:30:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p4
Message-ID: <20130425133055.23490.84519.idtracker@ietfa.amsl.com>
Date: Thu, 25 Apr 2013 06:30:55 -0700
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-security-requirements-05.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 25 Apr 2013 13:30:55 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Timing over IP Connection and Transfer of=
 Clock Working Group of the IETF.

	Title           : Security Requirements of Time Protocols in Packet Switch=
ed Networks
	Author(s)       : Tal Mizrahi
	Filename        : draft-ietf-tictoc-security-requirements-05.txt
	Pages           : 33
	Date            : 2013-04-25

Abstract:
   As time and frequency distribution protocols are becoming
   increasingly common and widely deployed, concern about their exposure
   to various security threats is increasing. This document defines a
   set of security requirements for time protocols, focusing on the
   Precision Time Protocol (PTP) and the Network Time Protocol (NTP).
   This document also discusses the security impacts of time protocol
   practices, the performance implications of external security
   practices on time protocols and the dependencies between other
   security services and time synchronization.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-security-requirements

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-security-requirements-=
05


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From talmi@marvell.com  Thu Apr 25 06:50:30 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55B121F8A18 for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 06:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNk0P2M2asjB for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 06:50:29 -0700 (PDT)
Received: from na3sys009aog112.obsmtp.com (na3sys009aog112.obsmtp.com [74.125.149.207]) by ietfa.amsl.com (Postfix) with ESMTP id 87DF721F88EA for <tictoc@ietf.org>; Thu, 25 Apr 2013 06:50:29 -0700 (PDT)
Received: from sc-owa02.marvell.com ([199.233.58.137]) (using TLSv1) by na3sys009aob112.postini.com ([74.125.148.12]) with SMTP ID DSNKUXk0lwwT/kCBeS3/3QZ07eLd9jRWA433@postini.com; Thu, 25 Apr 2013 06:50:29 PDT
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 25 Apr 2013 06:49:57 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Thu, 25 Apr 2013 16:49:53 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>, "Yaakov Stein (yaakov_s@rad.com)" <yaakov_s@rad.com>
Date: Thu, 25 Apr 2013 16:49:51 +0300
Thread-Topic: Updated TICTOC Security Requirements
Thread-Index: Ac5BuiZMjCtSCoq1RjSqII8TtL5nOg==
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F9A356C3@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F9A356C3ILMB01marve_"
MIME-Version: 1.0
Subject: [TICTOC] Updated TICTOC Security Requirements
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 25 Apr 2013 13:50:30 -0000

--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356C3ILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Following the comments received on the WGLC I updated the draft - mostly mi=
nor editorial updates.
The most notable changes compared to draft 04:


1.       I added some text in the introduction about the target audience of=
 the document.

2.       I changed "time synchronization protocols" to "time protocols", as=
 this seems to be the common grounds of NTP and PTP, both of which end with=
 a TP (Time Protocol). Seems like a fair compromise between Yaakov's sugges=
tion and Kevin's (http://www.ietf.org/mail-archive/web/tictoc/current/msg01=
382.html).

The current draft can be found in:
http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-05

Thanks,
Tal.


--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356C3ILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:755202621;
	mso-list-type:hybrid;
	mso-list-template-ids:-1788948682 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Following =
the comments received on the WGLC I updated the draft &#8211; mostly minor =
editorial updates.<o:p></o:p></p><p class=3DMsoNormal>The most notable chan=
ges compared to draft 04:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span s=
tyle=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>I added some text in the int=
roduction about the target audience of the document.<o:p></o:p></p><p class=
=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><!=
[if !supportLists]><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.=
0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><=
![endif]><span dir=3DLTR></span>I changed &#8220;time synchronization proto=
cols&#8221; to &#8220;time protocols&#8221;, as this seems to be the common=
 grounds of NTP and PTP, both of which end with a TP (Time Protocol). Seems=
 like a fair compromise between Yaakov&#8217;s suggestion and Kevin&#8217;s=
 (<a href=3D"http://www.ietf.org/mail-archive/web/tictoc/current/msg01382.h=
tml">http://www.ietf.org/mail-archive/web/tictoc/current/msg01382.html</a>)=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>The current draft can be found in:<o:p></o:p></p><p class=3DMsoNormal><=
a href=3D"http://tools.ietf.org/html/draft-ietf-tictoc-security-requirement=
s-05">http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-05=
</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMso=
Normal>Thanks,<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Arial","sans-serif"'>Tal.<o:p></o:p></span></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356C3ILMB01marve_--

From talmi@marvell.com  Thu Apr 25 06:55:58 2013
Return-Path: <talmi@marvell.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F4721F9057 for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 06:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJhm38e1zOtc for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 06:55:57 -0700 (PDT)
Received: from na3sys009aog118.obsmtp.com (na3sys009aog118.obsmtp.com [74.125.149.244]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD0821F8F28 for <tictoc@ietf.org>; Thu, 25 Apr 2013 06:55:56 -0700 (PDT)
Received: from SC-OWA01.marvell.com ([199.233.58.136]) (using TLSv1) by na3sys009aob118.postini.com ([74.125.148.12]) with SMTP ID DSNKUXk14J3lm0TzuCrmxSiI2P8pIm51B3VA@postini.com; Thu, 25 Apr 2013 06:55:56 PDT
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 25 Apr 2013 06:54:36 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Thu, 25 Apr 2013 16:54:32 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>, "Yaakov Stein (yaakov_s@rad.com)" <yaakov_s@rad.com>
Date: Thu, 25 Apr 2013 16:54:30 +0300
Thread-Topic: Updated TICTOC Security Requirements
Thread-Index: Ac5BuiZMjCtSCoq1RjSqII8TtL5nOgAAhyJQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F9A356CA@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F9A356C3@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F9A356C3@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F9A356CAILMB01marve_"
MIME-Version: 1.0
Subject: Re: [TICTOC] Updated TICTOC Security Requirements
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 25 Apr 2013 13:55:58 -0000

--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356CAILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Karen, Yaakov,

I guess WGLC has ended. As far as I am concerned, we are ready to proceed.

Thanks,
Tal.

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Thursday, April 25, 2013 4:50 PM
To: tictoc@ietf.org; odonoghue@isoc.org; Yaakov Stein (yaakov_s@rad.com)
Subject: [TICTOC] Updated TICTOC Security Requirements

Hi,

Following the comments received on the WGLC I updated the draft - mostly mi=
nor editorial updates.
The most notable changes compared to draft 04:


1.       I added some text in the introduction about the target audience of=
 the document.

2.       I changed "time synchronization protocols" to "time protocols", as=
 this seems to be the common grounds of NTP and PTP, both of which end with=
 a TP (Time Protocol). Seems like a fair compromise between Yaakov's sugges=
tion and Kevin's (http://www.ietf.org/mail-archive/web/tictoc/current/msg01=
382.html).

The current draft can be found in:
http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-05

Thanks,
Tal.


--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356CAILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:755202621;
	mso-list-type:hybrid;
	mso-list-template-ids:-1788948682 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Hi Karen, Yaakov,<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'color:#1F497D'>I guess WGLC has ended. As far as I am con=
cerned, we are ready to proceed.<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNor=
mal><span style=3D'color:#1F497D'>Thanks,<o:p></o:p></span></p><div><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-ser=
if";color:#1F497D'>Tal.<o:p></o:p></span></p></div><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'b=
order:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p cla=
ss=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'> tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org]=
 <b>On Behalf Of </b>Tal Mizrahi<br><b>Sent:</b> Thursday, April 25, 2013 4=
:50 PM<br><b>To:</b> tictoc@ietf.org; odonoghue@isoc.org; Yaakov Stein (yaa=
kov_s@rad.com)<br><b>Subject:</b> [TICTOC] Updated TICTOC Security Requirem=
ents<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>Following the comments received on the WGLC=
 I updated the draft &#8211; mostly minor editorial updates.<o:p></o:p></p>=
<p class=3DMsoNormal>The most notable changes compared to draft 04:<o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagrap=
h style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]=
><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New Rom=
an"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span dir=
=3DLTR></span>I added some text in the introduction about the target audien=
ce of the document.<o:p></o:p></p><p class=3DMsoListParagraph style=3D'text=
-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D=
'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>I=
 changed &#8220;time synchronization protocols&#8221; to &#8220;time protoc=
ols&#8221;, as this seems to be the common grounds of NTP and PTP, both of =
which end with a TP (Time Protocol). Seems like a fair compromise between Y=
aakov&#8217;s suggestion and Kevin&#8217;s (<a href=3D"http://www.ietf.org/=
mail-archive/web/tictoc/current/msg01382.html">http://www.ietf.org/mail-arc=
hive/web/tictoc/current/msg01382.html</a>).<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The current draft can be foun=
d in:<o:p></o:p></p><p class=3DMsoNormal><a href=3D"http://tools.ietf.org/h=
tml/draft-ietf-tictoc-security-requirements-05">http://tools.ietf.org/html/=
draft-ietf-tictoc-security-requirements-05</a><o:p></o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks,<o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-=
serif"'>Tal.<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01A0F9A356CAILMB01marve_--

From Russell.Smiley@idt.com  Thu Apr 25 10:56:14 2013
Return-Path: <Russell.Smiley@idt.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E4F21F9619 for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 10:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zf9gKOGX2EEZ for <tictoc@ietfa.amsl.com>; Thu, 25 Apr 2013 10:56:11 -0700 (PDT)
Received: from mxout1.idt.com (mxout1.idt.com [157.165.5.25]) by ietfa.amsl.com (Postfix) with ESMTP id A73FC21F960C for <tictoc@ietf.org>; Thu, 25 Apr 2013 10:56:11 -0700 (PDT)
Received: from mail.idt.com (localhost [127.0.0.1]) by mxout1.idt.com (8.13.1/8.13.1) with ESMTP id r3PHuAel015279; Thu, 25 Apr 2013 10:56:10 -0700
Received: from corpml1.corp.idt.com (corpml1.corp.idt.com [157.165.140.20]) by mail.idt.com (8.13.8/8.13.8) with ESMTP id r3PHu81A014001; Thu, 25 Apr 2013 10:56:08 -0700 (PDT)
Received: from corpmail2.na.ads.idt.com (localhost [127.0.0.1]) by corpml1.corp.idt.com (8.11.7p1+Sun/8.11.7) with ESMTP id r3PHtE612634; Thu, 25 Apr 2013 10:55:14 -0700 (PDT)
Received: from CORPMAIL1.na.ads.idt.com ([fe80::f9ec:4643:471e:dd33]) by corpmail2.na.ads.idt.com ([fe80::7d1f:86ad:31c6:5aee%20]) with mapi id 14.02.0318.001; Thu, 25 Apr 2013 10:55:13 -0700
From: "Smiley, Russell" <Russell.Smiley@idt.com>
To: Tal Mizrahi <talmi@marvell.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Updated TICTOC Security Requirements
Thread-Index: Ac5BuiZMjCtSCoq1RjSqII8TtL5nOgAIazEQ
Date: Thu, 25 Apr 2013 17:55:12 +0000
Message-ID: <3EB7D1CECF89334E9B5A0D6E60B9518F207EB050@corpmail1.na.ads.idt.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F9A356C3@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F9A356C3@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [157.165.140.139]
Content-Type: multipart/related; boundary="_004_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_"; type="multipart/alternative"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.43
Subject: Re: [TICTOC] Updated TICTOC Security Requirements
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 25 Apr 2013 17:56:14 -0000

--_004_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_
Content-Type: multipart/alternative;
	boundary="_000_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_"

--_000_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Tal,

Here are some comments on your draft. In general I find your idea of a fram=
ework for defining the necessary security support in timing protocols very =
helpful. I hope it will be a useful basis for the IEEE 1588 working group b=
eing convened when considering how to implement security functions in PTP.

Section 5.1
[Comment] It would be good to have each requirement statement uniquely numb=
ered to make it easy for implementors to reference the requirements directl=
y.


Section 5.1.3
[Comment] Not clear here, if authorization is implicitly included in the au=
thentication requirement, or if it is implicitly excluded from the authenti=
cation requirement and is not addressed in 5.1.3.

"(Requirement Level) Its low impact, i.e., in the absence of this requireme=
nt the protocol is only exposed to DoS"

[Comment] Disagree. Absence of authentication of slaves may enable MITM att=
acks delaying delay_req packets and thereby distorting the delay_req packet=
 arrival times and subsequent departure of delay_resp. The resulting asymme=
try could distort the subsequent slave clock offset calculations.
Slaves don't necessarily require authorization though.

"(Discussion)Slaves are authenticated by masters in order to verify that th=
e slave is authorized to receive timing services from the master."

[Comment] This conflation of authentication and authorization is not helpfu=
l. Slaves could be authenticated to prevent MITM attacks against delay_req =
packets without authorization. Authorization could be added for the purpose=
 of controlling master load and preventing DoS attacks as described in the =
text.

Suggest the following:

[Modify 'authenticate' to 'authorize']
    Requirement
    The security mechanism MAY provide a means for a master to authorize it=
s slaves.
[Add]
    Requirement
    The security mechanism MUST provide a means for a master to authenticat=
e its slaves.


Section 5.1.4
[Comment] Same motivation as 5.1.3 applies here. Suggest the same changes i=
n terms of MAY/MUST for  authorization and authentication respectively.


Section 7.3
"The usage of intermediate nodes implies that if a security mechanism is de=
ployed in the network, all intermediate nodes must possess the security key=
"

[Comment] This is not true in the BC case since a BC fully terminates the s=
ync connection. A slave's master is just the next adjacent BC. In the BC ca=
se the session key does not need to be shared across all nodes; each node c=
an have a unique key. In the TC case the nodes must have a shared session k=
ey, at least for modification of the correction field as discussed earlier.

Hope this helps.

Russell.



Russell Smiley
Principal Systems Engineer
+1 613 592 0859 x1831 direct
+1 613 322 9433 mobile

[cid:image002.jpg@01CDC41A.21180AF0]
Integrated Device Technology, Canada Inc.
603 March Rd, Ottawa, Ontario Canada K2K 2M5
www.IDT.com NASDAQ: IDTI

CONFIDENTIAL COMMUNICATION: This email and any attachments thereto may cont=
ain private and confidential material for the sole use of the intended reci=
pient. Any review, copying, or distribution of this email (or any attachmen=
ts thereto) by others is strictly prohibited. If you are not the intended r=
ecipient, please contact the sender immediately and permanently delete the =
original and any copies of this email and any attachments thereto.

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Thursday, April 25, 2013 9:50 AM
To: tictoc@ietf.org; odonoghue@isoc.org; Yaakov Stein (yaakov_s@rad.com)
Subject: [TICTOC] Updated TICTOC Security Requirements

Hi,

Following the comments received on the WGLC I updated the draft - mostly mi=
nor editorial updates.
The most notable changes compared to draft 04:


1.       I added some text in the introduction about the target audience of=
 the document.

2.       I changed "time synchronization protocols" to "time protocols", as=
 this seems to be the common grounds of NTP and PTP, both of which end with=
 a TP (Time Protocol). Seems like a fair compromise between Yaakov's sugges=
tion and Kevin's (http://www.ietf.org/mail-archive/web/tictoc/current/msg01=
382.html).

The current draft can be found in:
http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-05

Thanks,
Tal.


--_000_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:755202621;
	mso-list-type:hybrid;
	mso-list-template-ids:-1788948682 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tal,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Here are some comments=
 on your draft. In general I find your idea of a framework for defining the=
 necessary security support in timing protocols very helpful. I hope it wil=
l be a useful basis for the IEEE 1588
 working group being convened when considering how to implement security fu=
nctions in PTP.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Section 5.1<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] It would be good to have each requirement statement uniquely=
 numbered to make it easy for implementors to reference the requirements di=
rectly.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Section 5.1.3<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] Not clear here, if authorization is implicitly included in t=
he authentication requirement, or if it is implicitly excluded from the aut=
hentication requirement and is not addressed
 in 5.1.3. <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&quot;(Requirement Level) Its low impact, i.e., in the absence of thi=
s requirement the protocol is only exposed to DoS&quot;<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] Disagree. Absence of authentication of slaves may enable MIT=
M attacks delaying delay_req packets and thereby distorting the delay_req p=
acket arrival times and subsequent departure
 of delay_resp. The resulting asymmetry could distort the subsequent slave =
clock offset calculations.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Slaves don't necessarily require authorization though.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&quot;(Discussion)Slaves are authenticated by masters in order to ver=
ify that the slave is authorized to receive timing services from the master=
.&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] This conflation of authentication and authorization is not h=
elpful. Slaves could be authenticated to prevent MITM attacks against delay=
_req packets without authorization. Authorization
 could be added for the purpose of controlling master load and preventing D=
oS attacks as described in the text.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Suggest the following:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">[Modify 'authenticate' to 'authorize']&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&nbsp;&nbsp;&nbsp;&nbsp;Requirement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&nbsp;&nbsp;&nbsp; The security mechanism MAY provide a means for a m=
aster to authorize its slaves.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">[Add]<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&nbsp;&nbsp;&nbsp; Requirement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"color:#1F=
497D">&nbsp;&nbsp;&nbsp; The security mechanism MUST provide a means for a =
master to authenticate its slaves.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Section 5.1.4<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] Same motivation as 5.1.3 applies here. Suggest the same chan=
ges in terms of MAY/MUST for &nbsp;authorization and authentication respect=
ively.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Section 7.3<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">&quot;The usage of intermediate nodes implies that if a security mecha=
nism is deployed in the network, all intermediate nodes must possess the se=
curity key&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">[Comment] This is not true in the BC case since a BC fully terminates =
the sync connection. A slave's master is just the next adjacent BC. In the =
BC case the session key does not need
 to be shared across all nodes; each node can have a unique key. In the TC =
case the nodes must have a shared session key, at least for modification of=
 the correction field as discussed earlier.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hope this helps.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Russell.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;color:black"><o:p>&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;color:black"><o:p>&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;color:black">Russell Smiley
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;color:black">Principal Systems Engineer
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:10.0pt;color:black">&#43;1 613 592 0859 x1831 direct<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:10.0pt;color:black">&#43;1 613 322 9433 mobile
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:10.0pt;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;color:black"><img width=3D"79" height=3D"30" id=3D"Picture_x00=
20_1" src=3D"cid:image001.jpg@01CE41BA.FBEB08D0" alt=3D"cid:image002.jpg@01=
CDC41A.21180AF0"></span></b><span style=3D"font-size:10.0pt;color:black"><o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray=
">Integrated Device Technology, Canada Inc.
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray">6=
03 March Rd, Ottawa, Ontario Canada K2K 2M5
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">w=
ww.IDT.com
</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:gray">NASDAQ: IDTI
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:9.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;;color:gray">CONFIDENTIAL COMMUNICATION:
</span></b><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&qu=
ot;sans-serif&quot;;color:gray">This email and any attachments thereto may =
contain private and confidential material for the sole use of the intended =
recipient. Any review, copying, or distribution of this
 email (or any attachments thereto) by others is strictly prohibited. If yo=
u are not the intended recipient, please contact the sender immediately and=
 permanently delete the original and any copies of this email and any attac=
hments thereto.</span><span style=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Thursday, April 25, 2013 9:50 AM<br>
<b>To:</b> tictoc@ietf.org; odonoghue@isoc.org; Yaakov Stein (yaakov_s@rad.=
com)<br>
<b>Subject:</b> [TICTOC] Updated TICTOC Security Requirements<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Following the comments received on the WGLC I update=
d the draft &#8211; mostly minor editorial updates.<o:p></o:p></p>
<p class=3D"MsoNormal">The most notable changes compared to draft 04:<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>I added some text in the introduction about the tar=
get audience of the document.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>I changed &#8220;time synchronization protocols&#82=
21; to &#8220;time protocols&#8221;, as this seems to be the common grounds=
 of NTP and PTP, both of which end with a TP (Time Protocol). Seems like a =
fair compromise between Yaakov&#8217;s suggestion and Kevin&#8217;s
 (<a href=3D"http://www.ietf.org/mail-archive/web/tictoc/current/msg01382.h=
tml">http://www.ietf.org/mail-archive/web/tictoc/current/msg01382.html</a>)=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The current draft can be found in:<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-tic=
toc-security-requirements-05">http://tools.ietf.org/html/draft-ietf-tictoc-=
security-requirements-05</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_--

--_004_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1563;
	creation-date="Thu, 25 Apr 2013 17:55:12 GMT";
	modification-date="Thu, 25 Apr 2013 17:55:12 GMT"
Content-ID: <image001.jpg@01CE41BA.FBEB08D0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAeAE8DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDrPiH8
RE8JxrYWCJPqky7gG5WFezMO59B/k+YeH73XfHHjGysNR1m9kjmkLShZigCKCzAAYA6Y/GsPxLqU
ur+JdRv5WLNNcPjPZQcKPwAFdJ8IAD8QICe1vKR+Qr3Y0I0KDklrYi92elTeK5bGF7C0tkia3lKR
tnK7FOMEHnPvXS6JrMOs2nmoNkqcSR5+6f8ACvOb3m/uf+uz/wDoRrU8I3LW+vxID8s6lGHrxkfy
rwyi3rvxX0fQNcudJubG9kmt2Cs0artOQDxk+9WfFPxJ0vwpqaafeWl3LI8IlDQhSMEkdyPSvH/i
T/yUbVv+u0f/AKAla3xn/wCRwt/+vBP/AEJq9WOEpNw81/kK52kPxt8OPIFls9QiU/xGNTj8mrqX
8Y6O3hm58QWdx9ttLZNziH749iDjB9jXE6d8J9B1vwdY3cLT2l/cWqSecJCylyoPKntn0xXnfh6a
TRfE8mj6kGNpdS/YdQhViAyltufqDyD/AI1Kw9Cpf2d7rdBdnpv/AAvDQP8AoHaj/wB8p/8AFVNa
/GjQrq5SBNP1AM+cEqmOBn+97VwnxS8LaT4W1HT4NJheJJ4XZw0hbJBAHWuv8A/D7w7qfhXTNYur
WRryVGLOJmAJ3MvTOOlOdLDRpKpZ2YXZ5d4t0mXRPFWo2EilQk7NHn+JGOVP5Guh+DwJ8fxEdraU
n9K9S8d+AbTxlapIsgtdRgUiKfGQR/dYdx/KjTvAGnaHcx6jo8SW16tkbYgsTGzHGXPfPB+uaqWM
hKhyvdqwW1OSuGDXUzDoZGP6mtnwfZtca4k2Pkt1LMfcjAH+fSrI8C3+Rm7t8dz8x/pXV6VpVvpF
mLeDJJOXc9XPrXkDPn34k/8AJRtW/wCu0f8A6Ala3xn/AORwt/8ArwT/ANCauj8WfCfWNf8AFV7q
1tf2UcVw6sqSb9wwoHOB7Ve8e/DXVPFmuxahZ3tpDGlssRWbdnIJOeB05r24VoJ09dl/kI2ND8Va
HofgPS5r/U7dPLso8xrIGkJ2jgKOc141pcVx4w+IUbxxENe35uHA58tN24k/QV1MPwM1kyDztWsE
TuyI7H8iB/OvSPB/gXS/B8D/AGXdPdyjEt1IPmYegH8I9qydSlh1Jxd5MNzzz46f8hjSf+veT/0I
V33wx/5J1pH/AFzf/wBDasr4jeANR8Y39lcWV3awLbRMjCbdkkkHjAPpW34b0DVNB8OaXpYvIN1o
riYqpKvkkjGRnvWNSUZYWEb63/zDqf/Z

--_004_3EB7D1CECF89334E9B5A0D6E60B9518F207EB050corpmail1naadsi_--


From hammondjohnson@hushmail.com  Sat Apr 27 15:48:33 2013
Return-Path: <hammondjohnson@hushmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16BC21F93B7 for <tictoc@ietfa.amsl.com>; Sat, 27 Apr 2013 15:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sndiTK3c8THs for <tictoc@ietfa.amsl.com>; Sat, 27 Apr 2013 15:48:33 -0700 (PDT)
Received: from smtp1.hushmail.com (smtp1a.hushmail.com [65.39.178.236]) by ietfa.amsl.com (Postfix) with ESMTP id 6B00521F9446 for <tictoc@ietf.org>; Sat, 27 Apr 2013 15:48:33 -0700 (PDT)
Received: from smtp1.hushmail.com (smtp1a.hushmail.com [65.39.178.236]) by smtp1.hushmail.com (Postfix) with SMTP id 30D6B310FB for <tictoc@ietf.org>; Sat, 27 Apr 2013 17:52:15 +0000 (UTC)
X-hush-relay-time: 215
X-hush-relay-id: b1bd903faba185ee07e5a0ed3a1fde37
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp1.hushmail.com (Postfix) with ESMTP for <tictoc@ietf.org>; Sat, 27 Apr 2013 17:52:14 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id D6A44E6736; Sat, 27 Apr 2013 17:52:14 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 27 Apr 2013 13:52:14 -0400
To: tictoc@ietf.org
From: hammondjohnson@hushmail.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20130427175214.D6A44E6736@smtp.hushmail.com>
Subject: [TICTOC] Biggest Fake Conference in Computer Science
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Apr 2013 22:48:33 -0000

We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.


We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware


Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 


We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
http://sites.google.com/site/dumpconf for comments from well-known researchers 
about WORLDCOMP. 


The status of your WORLDCOMP papers can be changed from scientific
to other (i.e., junk or non-technical) at any time. Better not to have a paper than 
having it in WORLDCOMP and spoil the resume and peace of mind forever!


Our study revealed that WORLDCOMP is a money making business, 
using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing 
out a small chunk of that money (around 20 dollars per paper published 
in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) 
who publicizes WORLDCOMP and also defends it at various forums, using 
fake/anonymous names. The puppet uses fake names and defames other conferences
to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to 
threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). 
That is, the puppet does all his best to get a maximum number of papers published 
at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. 


Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has 
refused to provide the venue for WORLDCOMP’13 because of the fears of their image 
being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 
is taking place at a different resort. WORLDCOMP will not be held after 2013. 


The draft paper submission deadline is over but still there are no committee 
members, no reviewers, and there is no conference Chairman. The only contact 
details available on WORLDCOMP’s website is just an email address! 

Let us make a direct request to Prof. Hamid arabnia: publish all reviews for 
all the papers (after blocking identifiable details) since 2000 conference. Reveal 
the names and affiliations of all the reviewers (for each year) and how many 
papers each reviewer had reviewed on average. We also request him to look at 
the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 


Sorry for posting to multiple lists. Spreading the word is the only way to stop 
this bogus conference. Please forward this message to other mailing lists and people. 


We are shocked with Prof. Hamid Arabnia and his puppet’s activities 
http://worldcomp-fake-bogus.blogspot.com   Search Google using the 
keyword worldcomp fake for additional links.

