
From yaakov_s@rad.com  Wed Aug  1 13:58:30 2012
Return-Path: <yaakov_s@rad.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 ABAF911E82F8 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 13:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 8LuRCxauoKw5 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 13:58:30 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id 143D211E82ED for <tictoc@ietf.org>; Wed,  1 Aug 2012 13:58:23 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 1 Aug 2012 23:18:31 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Wed, 1 Aug 2012 23:58:20 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: PTP over MPLS draft
Thread-Index: AQHNcChhJlajhsBmXkGiIbKE3fSOvQ==
Date: Wed, 1 Aug 2012 20:58:19 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90452C95D@EXRAD5.ad.rad.co.il>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com>
In-Reply-To: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {D7866DAA-FD77-4439-B1E8-676A7027F512}
x-cr-hashedpuzzle: Axas BlHt E/dg IOKY IdGZ MGp7 MJaO NEPe RCde SKZf SfuU UEkQ UMRM UNq1 VEx1 VoNC; 2; ZABhAHYAYQByAGkAQABiAHIAbwBhAGQAYwBvAG0ALgBjAG8AbQA7AHQAaQBjAHQAbwBjAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {D7866DAA-FD77-4439-B1E8-676A7027F512}; eQBhAGEAawBvAHYAXwBzAEAAcgBhAGQALgBjAG8AbQA=; Wed, 01 Aug 2012 20:58:10 GMT;UABUAFAAIABvAHYAZQByACAATQBQAEwAUwAgAGQAcgBhAGYAdAA=
x-originating-ip: [207.232.33.112]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC90452C95DEXRAD5adradcoil_"
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A020202.5019986D.0078,ss=1,fgs=0
Subject: [TICTOC] PTP over MPLS 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: Wed, 01 Aug 2012 20:58:30 -0000

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

Shahram,

Karen just remarked to me that with the draft becoming more generic,
the new version really needs to be renamed something like
"Transporting Timing Flows over MPLS".

Y(J)S

--_000_07F7D7DED63154409F13298786A2ADC90452C95DEXRAD5adradcoil_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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)">
<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:0cm;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1360282173;
	mso-list-type:hybrid;
	mso-list-template-ids:-789962778 466019428 1316780848 1321392198 -20490353=
36 1939888188 1296344838 -102624414 -400270498 -1523913190;}
@list l0:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1766220544;
	mso-list-template-ids:2078035082;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1033" />
</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"Section1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Shahram, <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">Karen just remarked to=
 me that with the draft becoming more generic,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">the new version really=
 needs to be renamed something like<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&quot;Transporting Tim=
ing Flows over MPLS&quot;.<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">Y(J)S<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC90452C95DEXRAD5adradcoil_--

From yaakov_s@rad.com  Wed Aug  1 14:10:58 2012
Return-Path: <yaakov_s@rad.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 C0DB211E82E8 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 ZdonSOduwJN7 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:10:54 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id D016111E8256 for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:10:52 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 1 Aug 2012 23:31:01 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 00:10:50 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Questions regaridng 1588 over MPLS
Thread-Index: Ac1vX/3cqELPcksBSQ64WClgxq4MoQAyGCBA
Date: Wed, 1 Aug 2012 21:10:50 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com>
In-Reply-To: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC90452C9A0EXRAD5adradcoil_"
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090205.50199B5B.0040,ss=1,fgs=0
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
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: Wed, 01 Aug 2012 21:10:58 -0000

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

During today's TICTOC meeting I raised the following questions. We need you=
r feedback on these questions in order to progress this draft.


  1.  Should CW be mandatory?
     *   If not, then a PTP-LSP needs to carry only one type of PW (either =
with CW or without CW) but not mix so that LSRs can correctly parse the pac=
ket
     *
     *   Without PW the job of LSRs becomes more complex to identify the OA=
M packets
[YJS] I believe that it is fine to require a CW. RFC 5994 makes the CW mand=
atory for Ethernet PWs over MPLS-TP,
I believe that TP will be the main use case.


  1.  Should ECMP/Entropy be disallowed?
     *   The current consensus is yes, no ECMP or Entropy shall be used.
[YJS] entropy labels should be disallowed.
Obviously timing flows should in general should not be shifted from one pat=
h
to another path with different delay, if undetected the delay jump will cau=
se
an accumulating phase error.
I understand that with TC this point is less important, but this draft expl=
icitly speaks of only partial on-path support.

Should PHP (Penultimate Hop Popping) be allowed?
[YJS] Once again, if the main use case is MPLS-TP, then this may be automat=
ic

  1.  How to transport 1588 messages that don't need TS or CF update?
     *   Send them over non-PTP LSP?
     *   Let the LSRs do the parsing and perform TS or CF updated based on =
message type?
[YJS] They should be sent over the same PW.
Since the setup specifies the timing flow type,
the regular 1588 parser will be called anyway.


  1.  Should P2MP LSP & P2MP PW be supported?
[YJS] No strong opinion.


  1.  Should protection be supported for PTP-LSP?
     *   FRR, 1:1 and 1+1
[YJS] Similar to my response above, protection should NOT be supported,
as a change of path means a change in delay, which if undetected can be wor=
se than losing the timing flow
and going into holdover.


  1.  How does LSP/PW connectivity failure interact with 1588?
     *   Does the Slave select another master when a failure happens?
     *   Can the protection make the failure invisible to Salve clock?
[YJS] b. should never be allowed. a. is a configuration option.


  1.  Should only VCCV1 and VCCV4 be allowed?
     *   If not then the VCCV type needs to be the same for all PW in the P=
TP-LSP so that LSRs can correctly parse the packet
[YJS] We are presently in the process of obsoleting type 2 anyway.
So we are left with the issue of type 3, which is mostly for MS-PWs.
Do you see this being used for the MS case ?



--_000_07F7D7DED63154409F13298786A2ADC90452C9A0EXRAD5adradcoil_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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)">
<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:0cm;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:654260675;
	mso-list-template-ids:1689797028;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1360282173;
	mso-list-type:hybrid;
	mso-list-template-ids:-789962778 466019428 1316780848 1321392198 -20490353=
36 1939888188 1296344838 -102624414 -400270498 -1523913190;}
@list l1:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1033" />
</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"Section1">
<p class=3D"MsoNormal">During today&#8217;s TICTOC meeting I raised the fol=
lowing questions. We need your feedback on these questions in order to prog=
ress this draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Should CW be mand=
atory? <o:p>
</o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">If not, then a PT=
P-LSP needs to carry only one type of PW (either with CW or without CW) but=
 not mix so that LSRs can correctly parse the packet<o:p></o:p>
</li><li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3"><o:p>&nbsp;<=
/o:p> </li><li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">Withou=
t PW the job of LSRs becomes more complex to identify the OAM packets<o:p><=
/o:p>
</li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] I believe that i=
t is fine to require a CW. RFC 5994 makes the CW mandatory for Ethernet PWs=
 over MPLS-TP,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I believe that TP will=
 be the main use case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"2" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Should ECMP/Entro=
py be disallowed?
<o:p></o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">The current conse=
nsus is yes, no ECMP or Entropy shall be used.<o:p></o:p>
</li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] entropy labels s=
hould be disallowed.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Obviously timing flows=
 should in general should not be shifted from one path<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">to another path with d=
ifferent delay, if undetected the delay jump will cause<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">an accumulating phase =
error.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I understand that with=
 TC this point is less important, but this draft explicitly speaks of only =
partial on-path support.<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">Should PHP (Penultimate Hop Popping) be allowed?<o:p=
></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] Once again, if t=
he main use case is MPLS-TP, then this may be automatic<o:p></o:p></span></=
p>
<ol style=3D"margin-top:0cm" start=3D"3" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">How to transport =
1588 messages that don&#8217;t need TS or CF update?
<o:p></o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">Send them over no=
n-PTP LSP?<o:p></o:p>
</li><li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">Let the LSRs=
 do the parsing and perform TS or CF updated based on message type?
<o:p></o:p></li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] They should be s=
ent over the same PW.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Since the setup specif=
ies the timing flow type,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">the regular 1588 parse=
r will be called anyway.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"4" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Should P2MP LSP &=
amp; P2MP PW be supported?<o:p></o:p>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] No strong opinio=
n.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"5" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Should protection=
 be supported for PTP-LSP?
<o:p></o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">FRR, 1:1 and 1&#4=
3;1<o:p></o:p>
</li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] Similar to my re=
sponse above, protection should NOT be supported,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">as a change of path me=
ans a change in delay, which if undetected can be worse than losing the tim=
ing flow<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">and going into holdove=
r.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"6" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">How does LSP/PW c=
onnectivity failure interact with 1588?
<o:p></o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">Does the Slave se=
lect another master when a failure happens?<o:p></o:p>
</li><li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">Can the prot=
ection make the failure invisible to Salve clock?<o:p></o:p>
</li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] b. should never =
be allowed. a. is a configuration option.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"7" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Should only VCCV1=
 and VCCV4 be allowed?
<o:p></o:p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo3">If not then the V=
CCV type needs to be the same for all PW in the PTP-LSP so that LSRs can co=
rrectly parse the packet<o:p></o:p>
</li></ol>
</li></ol>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[YJS] We are presently=
 in the process of obsoleting type 2 anyway.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">So we are left with th=
e issue of type 3, which is mostly for MS-PWs.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Do you see this being =
used for the MS case ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC90452C9A0EXRAD5adradcoil_--

From stbryant@cisco.com  Wed Aug  1 14:18:00 2012
Return-Path: <stbryant@cisco.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 64B1B11E832A for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.57
X-Spam-Level: 
X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 tu0J94yv3P9i for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:17:59 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id A08A711E8322 for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1700; q=dns/txt; s=iport; t=1343855879; x=1345065479; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=M8LPJF+MFQAmIeWi5cCCqbaa6Qzq3xGtCLpCkp2Gv+w=; b=lZ04QEyl94TpqdxrdBnXVuZ0Mri8ijJiD/iz4YlTjzez1WYovIDN01u9 v77vFl2ZdiZz9ThbBFaVqvboEitpSDJjaBmT140zPNs+rOU/XghSLNBn7 DzSKVe3AVVUy+tNmbmR46/8soWqTPHw0nENYAo5tLSlC5MPfv4Xiq6ds2 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FABacGVCQ/khM/2dsb2JhbABFtVyDNYEHghcJAQEBBBIBAmMBEAsDARQJFg8JAwIBAgFFBg0BBwEBHodrnQKDSBCcaotJhwkDlUeOJ4EEYoJg
X-IronPort-AV: E=Sophos;i="4.77,696,1336348800"; d="scan'208,217";a="7064005"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 01 Aug 2012 21:17:58 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q71LHwiI031051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Aug 2012 21:17:58 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q71LHrSX013877; Wed, 1 Aug 2012 22:17:55 +0100 (BST)
Message-ID: <50199D01.1010601@cisco.com>
Date: Wed, 01 Aug 2012 22:17:53 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
Content-Type: multipart/alternative; boundary="------------000401090805080602030205"
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
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: Wed, 01 Aug 2012 21:18:00 -0000

This is a multi-part message in MIME format.
--------------000401090805080602030205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 01/08/2012 22:10, Yaakov Stein wrote:
>
> Should PHP (Penultimate Hop Popping) be allowed?
>
> [YJS] Once again, if the main use case is MPLS-TP, then this may be 
> automatic
>
Wrong way about.

MPLS-TP does not support PHP.

You should not all PHP of these LSP'S since you need to trap these pkts 
in the receiving PE

- Stewart

--------------000401090805080602030205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 01/08/2012 22:10, Yaakov Stein
      wrote:<span style="color:#1F497D"><o:p> <br>
        </o:p></span></div>
    <blockquote
      cite="mid:07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il"
      type="cite">
      <div class="Section1">
        <p class="MsoNormal">Should PHP (Penultimate Hop Popping) be
          allowed?<o:p></o:p></p>
        <p class="MsoNormal"><span style="color:#1F497D">[YJS] Once
            again, if the main use case is MPLS-TP, then this may be
            automatic</span></p>
      </div>
    </blockquote>
    Wrong way about.<br>
    <br>
    MPLS-TP does not support PHP.<br>
    <br>
    You should not all PHP of these LSP'S since you need to trap these
    pkts in the receiving PE<br>
    <br>
    - Stewart<br>
  </body>
</html>

--------------000401090805080602030205--

From davari@broadcom.com  Wed Aug  1 14:20:45 2012
Return-Path: <davari@broadcom.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 9566811E8350 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.388
X-Spam-Level: 
X-Spam-Status: No, score=-5.388 tagged_above=-999 required=5 tests=[AWL=1.210,  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 xEWuvflibNZM for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:20:44 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 8C43711E8339 for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:20:44 -0700 (PDT)
Received: from [10.16.192.232] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 01 Aug 2012 14:19:05 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS02.corp.ad.broadcom.com (10.16.192.37) by SJEXCHHUB02.corp.ad.broadcom.com (10.16.192.232) with Microsoft SMTP Server (TLS) id 8.2.247.2; Wed, 1 Aug 2012 14:20:40 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by sjexchcas02.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0355.002; Wed, 1 Aug 2012 14:20:19 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: PTP over MPLS draft
Thread-Index: AQHNcChp86a22F4Pu0uh7YaaUgaQ+JdFdn3Q
Date: Wed, 1 Aug 2012 21:20:18 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F280699F9@SJEXCHMB12.corp.ad.broadcom.com>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C95D@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90452C95D@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.240.250.28]
MIME-Version: 1.0
X-WSS-ID: 7C0742C349815118203-01-01
Content-Type: multipart/alternative; boundary=_000_4A6CE49E6084B141B15C0713B8993F280699F9SJEXCHMB12corpadb_
Subject: Re: [TICTOC] PTP over MPLS 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: Wed, 01 Aug 2012 21:20:45 -0000

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

Hi Yaakov,

Yes, that is what I had in mind as well.

Thx
SD

From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Wednesday, August 01, 2012 1:58 PM
To: Shahram Davari; tictoc@ietf.org
Subject: PTP over MPLS draft

Shahram,

Karen just remarked to me that with the draft becoming more generic,
the new version really needs to be renamed something like
"Transporting Timing Flows over MPLS".

Y(J)S

--_000_4A6CE49E6084B141B15C0713B8993F280699F9SJEXCHMB12corpadb_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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)">
<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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{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.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Yaakov,<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">Yes, that is what I ha=
d in mind as well.<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">Thx<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">SD<o:p></o:p></span></=
p>
<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;"> Yaakov S=
tein [mailto:yaakov_s@rad.com]
<br>
<b>Sent:</b> Wednesday, August 01, 2012 1:58 PM<br>
<b>To:</b> Shahram Davari; tictoc@ietf.org<br>
<b>Subject:</b> PTP over MPLS draft<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Shahram, <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">Karen just remarked to=
 me that with the draft becoming more generic,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">the new version really=
 needs to be renamed something like<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&quot;Transporting Tim=
ing Flows over MPLS&quot;.<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">Y(J)S<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_4A6CE49E6084B141B15C0713B8993F280699F9SJEXCHMB12corpadb_--


From stbryant@cisco.com  Wed Aug  1 14:21:15 2012
Return-Path: <stbryant@cisco.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 55F4B11E834B for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.57
X-Spam-Level: 
X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 xLqKRkijjFMu for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:21:14 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 68C5A11E8339 for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=669; q=dns/txt; s=iport; t=1343856074; x=1345065674; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=H1rBU+1epLN2/L6CQLMUUigf7iVTcJ/YLKw6KUSN8UM=; b=MUWeFpslwTVck2wCQK8aQudNbckmJzYssz3AeUBlxx8cOExa2pkCUo0g 93cNqgZ0UtaCzVYoHOuqZ6fU+PC/5EURBuR/qGZsH7eNzGVM1xqv3IOHS mtR6325kRon6KJW1WEjA//BwPwJXoAuEXVpx8VB1+Z7aYEbQ8G0VWggS4 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAEqcGVCQ/khM/2dsb2JhbABFtVyDNYEHgiABAQEEEgECI0ABEAsYCRYPCQMCAQIBRRMBBwEBHodrnQKDSBCcaotJFINZgxwDlUeOJ4EECFqCYIFV
X-IronPort-AV: E=Sophos;i="4.77,696,1336348800"; d="scan'208";a="75726276"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 01 Aug 2012 21:21:13 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q71LLDiW031597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Aug 2012 21:21:13 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q71LL9RO014131; Wed, 1 Aug 2012 22:21:10 +0100 (BST)
Message-ID: <50199DC5.8070405@cisco.com>
Date: Wed, 01 Aug 2012 22:21:09 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: stbryant@cisco.com
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il> <50199D01.1010601@cisco.com>
In-Reply-To: <50199D01.1010601@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
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: Wed, 01 Aug 2012 21:21:15 -0000

On 01/08/2012 22:17, Stewart Bryant wrote:
> On 01/08/2012 22:10, Yaakov Stein wrote:
>>
>> Should PHP (Penultimate Hop Popping) be allowed?
>>
>> [YJS] Once again, if the main use case is MPLS-TP, then this may be 
>> automatic
>>
> Wrong way about.
>
> MPLS-TP does not support PHP.
>
> You should not all PHP of these LSP'S since you need to trap these 
> pkts in the receiving PE
>
> - Stewart

That last incoherent sentence should read, that you cannot PHP since you 
need
to trap these packets at the ingress PE.

This also means that you can avoid burning the limited number of PTP labels
by allocating them to both LSP and PW.

Stewart



From yaakov_s@rad.com  Wed Aug  1 14:28:24 2012
Return-Path: <yaakov_s@rad.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 BBA3D21F8A23 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 Fg+Zcwr0eEKS for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:28:24 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE7321F8A1C for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:28:22 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 1 Aug 2012 23:48:30 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 00:28:19 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Thread-Topic: [TICTOC] Questions regaridng 1588 over MPLS
Thread-Index: Ac1vX/3cqELPcksBSQ64WClgxq4MoQAyGCBA///TMYD//8sMkA==
Date: Wed, 1 Aug 2012 21:28:19 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90452CA27@EXRAD5.ad.rad.co.il>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il> <50199D01.1010601@cisco.com>
In-Reply-To: <50199D01.1010601@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC90452CA27EXRAD5adradcoil_"
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090203.50199F74.0093,ss=1,fgs=0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
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: Wed, 01 Aug 2012 21:28:24 -0000

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

Stewart

Sorry for the unfortunate wording on my part.

What I meant is that automatically you DON'T have PHPing.

So I think we are in agreement.

Y(J)S

From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Thursday, August 02, 2012 00:18
To: Yaakov Stein
Cc: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS

On 01/08/2012 22:10, Yaakov Stein wrote:

Should PHP (Penultimate Hop Popping) be allowed?
[YJS] Once again, if the main use case is MPLS-TP, then this may be automat=
ic
Wrong way about.

MPLS-TP does not support PHP.

You should not all PHP of these LSP'S since you need to trap these pkts in =
the receiving PE

- Stewart

--_000_07F7D7DED63154409F13298786A2ADC90452CA27EXRAD5adradcoil_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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)">
<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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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 bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Stewart<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Sorry for the unfortunate wording on my part.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">What I meant is that automatically you DON'T have PHPing.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">So I think we are in agreement.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;
color:windowtext">From:</span></b><span style=3D"font-size:10.0pt;font-fami=
ly:
&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext"> Stewart Bryant=
 [mailto:stbryant@cisco.com]
<br>
<b>Sent:</b> Thursday, August 02, 2012 00:18<br>
<b>To:</b> Yaakov Stein<br>
<b>Cc:</b> Shahram Davari; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] Questions regaridng 1588 over MPLS<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 01/08/2012 22:10, Yaakov Stein wrote:<span style=
=3D"color:#1F497D">
<br>
<br>
</span><o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Should PHP (Penultimate Hop Popping) be allowed?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">[YJS] Once again, if the main use ca=
se is MPLS-TP, then this may be automatic</span><o:p></o:p></p>
</div>
</blockquote>
<p class=3D"MsoNormal">Wrong way about.<br>
<br>
MPLS-TP does not support PHP.<br>
<br>
You should not all PHP of these LSP'S since you need to trap these pkts in =
the receiving PE<br>
<br>
- Stewart<o:p></o:p></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC90452CA27EXRAD5adradcoil_--

From davari@broadcom.com  Wed Aug  1 14:30:31 2012
Return-Path: <davari@broadcom.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 E3A7011E8183 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.993
X-Spam-Level: 
X-Spam-Status: No, score=-5.993 tagged_above=-999 required=5 tests=[AWL=0.605,  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 IrTd7PJRRSxU for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:30:31 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 53E7511E817B for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:30:31 -0700 (PDT)
Received: from [10.16.192.232] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 01 Aug 2012 14:28:51 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS01.corp.ad.broadcom.com (10.16.192.31) by SJEXCHHUB02.corp.ad.broadcom.com (10.16.192.232) with Microsoft SMTP Server (TLS) id 8.2.247.2; Wed, 1 Aug 2012 14:30:25 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by sjexchcas01.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0355.002; Wed, 1 Aug 2012 14:30:04 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Thread-Topic: [TICTOC] Questions regaridng 1588 over MPLS
Thread-Index: Ac1vX/3cqELPcksBSQ64WClgxq4MoQAyGCBAAA9aqYAAAF1IgAAOo+pA
Date: Wed, 1 Aug 2012 21:30:04 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F28069A8A@SJEXCHMB12.corp.ad.broadcom.com>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il> <50199D01.1010601@cisco.com> <07F7D7DED63154409F13298786A2ADC90452CA27@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90452CA27@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.240.250.28]
MIME-Version: 1.0
X-WSS-ID: 7C07401949815120839-01-01
Content-Type: multipart/alternative; boundary=_000_4A6CE49E6084B141B15C0713B8993F28069A8ASJEXCHMB12corpadb_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
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: Wed, 01 Aug 2012 21:30:32 -0000

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

Yaakov,

This brings an interesting question. Can we say UDP/IP encap is for MPLS an=
d PW Encap is for MPLS-TP?

Thx
SD

From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Wednesday, August 01, 2012 2:28 PM
To: stbryant@cisco.com
Cc: Shahram Davari; tictoc@ietf.org
Subject: RE: [TICTOC] Questions regaridng 1588 over MPLS

Stewart

Sorry for the unfortunate wording on my part.

What I meant is that automatically you DON'T have PHPing.

So I think we are in agreement.

Y(J)S

From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Thursday, August 02, 2012 00:18
To: Yaakov Stein
Cc: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS

On 01/08/2012 22:10, Yaakov Stein wrote:
Should PHP (Penultimate Hop Popping) be allowed?
[YJS] Once again, if the main use case is MPLS-TP, then this may be automat=
ic
Wrong way about.

MPLS-TP does not support PHP.

You should not all PHP of these LSP'S since you need to trap these pkts in =
the receiving PE

- Stewart

--_000_4A6CE49E6084B141B15C0713B8993F28069A8ASJEXCHMB12corpadb_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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)">
<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:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{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;}
--></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 bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yaakov,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This brings an interestin=
g question. Can we say UDP/IP encap is for MPLS and PW Encap is for MPLS-TP=
?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thx<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">SD<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/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;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Yaakov Stein [mailto:yaakov_s@rad.com]
<br>
<b>Sent:</b> Wednesday, August 01, 2012 2:28 PM<br>
<b>To:</b> stbryant@cisco.com<br>
<b>Cc:</b> Shahram Davari; tictoc@ietf.org<br>
<b>Subject:</b> RE: [TICTOC] Questions regaridng 1588 over MPLS<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Stewart<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Sorry for the unfortunate=
 wording on my part.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">What I meant is that auto=
matically you DON'T have PHPing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So I think we are in agre=
ement.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Y(J)S<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/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;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Stewart Bryant [mailto:stbryant@cisco.com]
<br>
<b>Sent:</b> Thursday, August 02, 2012 00:18<br>
<b>To:</b> Yaakov Stein<br>
<b>Cc:</b> Shahram Davari; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] Questions regaridng 1588 over MPLS<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">On 01/08/2012 22:10, =
Yaakov Stein wrote:<span style=3D"color:#1F497D">
</span><o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Should PHP (Penultimate Hop Popping) be allowed?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">[YJS] Once again, if the main use ca=
se is MPLS-TP, then this may be automatic</span><o:p></o:p></p>
</div>
</blockquote>
<p class=3D"MsoNormal">Wrong way about.<br>
<br>
MPLS-TP does not support PHP.<br>
<br>
You should not all PHP of these LSP'S since you need to trap these pkts in =
the receiving PE<br>
<br>
- Stewart<o:p></o:p></p>
</div>
</body>
</html>

--_000_4A6CE49E6084B141B15C0713B8993F28069A8ASJEXCHMB12corpadb_--


From stbryant@cisco.com  Wed Aug  1 14:30:37 2012
Return-Path: <stbryant@cisco.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 622FE11E82AE for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.571
X-Spam-Level: 
X-Spam-Status: No, score=-110.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 lTHVP69hZ++1 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:30:36 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 82EB211E81BE for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:30:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=280; q=dns/txt; s=iport; t=1343856636; x=1345066236; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Xz/RpHE5pOWDXafkXnlMA53ANn96uGOeNHRlRs6qe50=; b=QqKKoz9PgkOkq/02JE2j8tcp18tTIcRWL0VdXF9bazsuosmO/D1aF29D dZ0NOETHTYcC5J9aCfKC+tOlZHkKXfqAcYxUmA9gDwtl5V1UbNbhmwQ/8 alVSAke2L9moUA89zGX8K7Draoebg/AuKjP06pot1InJ/tEG1dNyPkUbo s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAHefGVCQ/khM/2dsb2JhbABFtVyDNYEHgiABAQEEEgECI0ABEAsYCRYPCQMCAQIBRQYNAQcBAR6Ha5x9g0gQnGuLSYcJA5VHjieBBGKCYA
X-IronPort-AV: E=Sophos;i="4.77,696,1336348800"; d="scan'208";a="141907936"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 01 Aug 2012 21:30:35 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q71LUZTX000890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Aug 2012 21:30:35 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q71LUVnC014662; Wed, 1 Aug 2012 22:30:32 +0100 (BST)
Message-ID: <50199FF7.7080103@cisco.com>
Date: Wed, 01 Aug 2012 22:30:31 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il> <50199D01.1010601@cisco.com> <07F7D7DED63154409F13298786A2ADC90452CA27@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90452CA27@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
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: Wed, 01 Aug 2012 21:30:37 -0000

On 01/08/2012 22:28, Yaakov Stein wrote:
>
> Stewart
>
> Sorry for the unfortunate wording on my part.
>
> What I meant is that automatically you DON'T have PHPing.
>
> So I think we are in agreement.
>
Approximately, I don't see why we wouldn't forbid PHP.

Stewart

From gregory.mirsky@ericsson.com  Wed Aug  1 14:44:04 2012
Return-Path: <gregory.mirsky@ericsson.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 1ED4311E8155 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:44:04 -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=[AWL=-0.000, 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 imGuOIPRqaj9 for <tictoc@ietfa.amsl.com>; Wed,  1 Aug 2012 14:44:03 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4B72B11E8124 for <tictoc@ietf.org>; Wed,  1 Aug 2012 14:44:03 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q71Lhvwb005156; Wed, 1 Aug 2012 16:43:59 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.13]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 1 Aug 2012 17:43:54 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Yaakov Stein <yaakov_s@rad.com>, Shahram Davari <davari@broadcom.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Wed, 1 Aug 2012 17:43:52 -0400
Thread-Topic: Questions regaridng 1588 over MPLS
Thread-Index: Ac1vX/3cqELPcksBSQ64WClgxq4MoQAyGCBAAAE44QA=
Message-ID: <FE60A4E52763E84B935532D7D9294FF13924D6DAA6@EUSAACMS0715.eamcs.ericsson.se>
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
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_FE60A4E52763E84B935532D7D9294FF13924D6DAA6EUSAACMS0715e_"
MIME-Version: 1.0
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
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: Wed, 01 Aug 2012 21:44:04 -0000

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

Dear Yaakov, Sharham, et al.,
________________________________
Should CW be mandatory?

 1.
    *   If not, then a PTP-LSP needs to carry only one type of PW (either w=
ith CW or without CW) but not mix so that LSRs can correctly parse the pack=
et
    *
    *   Without PW the job of LSRs becomes more complex to identify the OAM=
 packets
[YJS] I believe that it is fine to require a CW. RFC 5994 makes the CW mand=
atory for Ethernet PWs over MPLS-TP,
I believe that TP will be the main use case.

GIM>> I think that with upcoming introduction of PW VCCV CC Type 4 requirem=
ent to use CW, Section 2 of RFC 5994, can be relaxed. As result use of CW i=
n MPLS-TP PW can not be expected.

    Regards,
        Greg

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6002.18616" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt;=
 }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.EmailStyle19 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal
}
SPAN.EmailStyle20 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1033" />
</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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D609153321-01082012><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Dear Yaakov, Sharham, et al.,</FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
Should CW be mandatory? <o:p></o:p></DIV>
<DIV class=3DSection1>
<OL style=3D"MARGIN-TOP: 0cm" type=3D1>
  <LI class=3DMsoNormal style=3D"mso-list: l1 level1 lfo3">
  <OL style=3D"MARGIN-TOP: 0cm" type=3Da>
    <LI class=3DMsoNormal style=3D"mso-list: l1 level2 lfo3">If not, then a=
 PTP-LSP=20
    needs to carry only one type of PW (either with CW or without CW) but n=
ot=20
    mix so that LSRs can correctly parse the packet<o:p></o:p>=20
    <LI class=3DMsoNormal style=3D"mso-list: l1 level2 lfo3"><o:p>&nbsp;</o=
:p>=20
    <LI class=3DMsoNormal style=3D"mso-list: l1 level2 lfo3">Without PW the=
 job of=20
    LSRs becomes more complex to identify the OAM packets<o:p></o:p>=20
  </LI></OL></LI></OL>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">[YJS] I believe that it=
 is fine=20
to require a CW. RFC 5994 makes the CW mandatory for Ethernet PWs over=20
MPLS-TP,<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">I believe that TP will =
be the=20
main use case.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN=
></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN class=3D609153321-01082012>GIM&gt;&gt; I thi=
nk that=20
with upcoming introduction of PW VCCV CC Type 4 requirement to use CW, Sect=
ion 2=20
of RFC 5994, can be relaxed. As result use of CW in MPLS-TP PW can not be=20
expected.</SPAN></FONT></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN=20
class=3D609153321-01082012></SPAN></FONT></o:p></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN class=3D609153321-01082012>&nbsp;&nbsp;&nbsp=
;=20
Regards,</SPAN></FONT></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN=20
class=3D609153321-01082012>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Greg</SPAN></FONT></o:p></SPAN></P></DIV></BODY></HTML>

--_000_FE60A4E52763E84B935532D7D9294FF13924D6DAA6EUSAACMS0715e_--

From talmi@marvell.com  Thu Aug  2 09:10:47 2012
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 7023E21F85F3 for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, 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 LuSuPbxtyVTf for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:10:46 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9336121F849D for <tictoc@ietf.org>; Thu,  2 Aug 2012 09:10:45 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 2 Aug 2012 19:10:39 +0300
Thread-Topic: TICTOC Security Requirements
Thread-Index: Ac1wyL10ho4n+FERQfO8uMrUHl9L0A==
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8891597@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_74470498B659FA4687F0B0018C19A89C01A0F8891597ILMB01marve_"
MIME-Version: 1.0
Subject: [TICTOC] 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, 02 Aug 2012 16:10:47 -0000

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

Hi,

http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02

Following this week's TICTOC meeting:

1.       We plan to release draft 03 within a month, and proceed to WG last=
 call.

2.       Therefore, I will appreciate if people can send any comments they =
may have by Aug 22.

3.       There was some discussion about the "proventication" requirement. =
I would like to suggest to change the terminology in the document, since I =
understand this term is not very popular.
However, I believe that the requirement for a chain of trust is still an im=
portant and valid requirement. Please comment if you think otherwise.

Thanks,
Tal.


--_000_74470498B659FA4687F0B0018C19A89C01A0F8891597ILMB01marve_
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;}
/* 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:881134412;
	mso-list-type:hybrid;
	mso-list-template-ids:-2073008548 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><a href=3D=
"http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02">htt=
p://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02</a><o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Fo=
llowing this week&#8217;s TICTOC meeting:<o:p></o:p></p><p class=3DMsoListP=
aragraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !suppor=
tLists]><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><s=
pan dir=3DLTR></span>We plan to release draft 03 within a month, and procee=
d to WG last call.<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>Th=
erefore, I will appreciate if people can send any comments they may have by=
 Aug 22.<o:p></o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.2=
5in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:I=
gnore'>3.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>There was so=
me discussion about the &#8220;proventication&#8221; requirement. I would l=
ike to suggest to change the terminology in the document, since I understan=
d this term is not very popular.<br>However, I believe that the requirement=
 for a chain of trust is still an important and valid requirement. Please c=
omment if you think otherwise.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>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_74470498B659FA4687F0B0018C19A89C01A0F8891597ILMB01marve_--

From brian@innovationslab.net  Thu Aug  2 09:34:36 2012
Return-Path: <brian@innovationslab.net>
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 0AE2511E80FA for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 g-PeE7bNnfTY for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:34:35 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1346E11E80E9 for <tictoc@ietf.org>; Thu,  2 Aug 2012 09:34:35 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 04BCF880E7 for <tictoc@ietf.org>; Thu,  2 Aug 2012 09:34:32 -0700 (PDT)
Received: from dhcp-5588.meeting.ietf.org (unknown [IPv6:2001:df8:0:80:2963:ed71:42ce:d9b7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id DBAD1130018 for <tictoc@ietf.org>; Thu,  2 Aug 2012 09:34:31 -0700 (PDT)
Message-ID: <501AAC19.8070103@innovationslab.net>
Date: Thu, 02 Aug 2012 12:34:33 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: tictoc@ietf.org
References: <74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] 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, 02 Aug 2012 16:34:36 -0000

Hi Tal,

On 8/2/12 12:10 PM, Tal Mizrahi wrote:
> Hi,
>
> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>
> Following this week's TICTOC meeting:
>
> 1.       We plan to release draft 03 within a month, and proceed to WG last call.
>
> 2.       Therefore, I will appreciate if people can send any comments they may have by Aug 22.
>
> 3.       There was some discussion about the "proventication" requirement. I would like to suggest to change the terminology in the document, since I understand this term is not very popular.
> However, I believe that the requirement for a chain of trust is still an important and valid requirement. Please comment if you think otherwise.
>

Given that proventic/proventicate/proventication was defined and used in 
RFC 5906, I would suggest that this work and the Autokey revision work 
coordinate on what terminology to use.  It will be good to ensure that 
they are in sync since the issues are essentially the same.

Regards,
Brian


From ldg004@earthlink.net  Thu Aug  2 09:50:25 2012
Return-Path: <ldg004@earthlink.net>
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 8689911E8156 for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.394
X-Spam-Level: 
X-Spam-Status: No, score=-1.394 tagged_above=-999 required=5 tests=[AWL=1.205,  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 7jxIcL6GvQVS for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 09:50:24 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 749DC21E8088 for <tictoc@ietf.org>; Thu,  2 Aug 2012 09:50:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ZF+o1gyZxyeX2UDqNGxr0F8wkd2/6XG/2h98+xlULzq5l4AcBvbyqmWdNY12gCTl; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [108.49.37.59] (helo=[192.168.1.3]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ldg004@earthlink.net>) id 1Swyb3-0004Xh-Rf for tictoc@ietf.org; Thu, 02 Aug 2012 12:50:01 -0400
Message-ID: <501AAFB1.50104@earthlink.net>
Date: Thu, 02 Aug 2012 12:49:53 -0400
From: Dan Grossman <ldg004@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: tictoc@ietf.org
References: <mailman.2909.1343923847.3364.tictoc@ietf.org>
In-Reply-To: <mailman.2909.1343923847.3364.tictoc@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 5fd9b736a583489594f5150ab1c16ac0485087bba56e60095d6ba2796d7e1662780345c02ca78ce6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 108.49.37.59
Subject: [TICTOC]  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, 02 Aug 2012 16:50:25 -0000

Tal,
I wasn't able to get meeting audio, so don't know whether this was 
discussed.

My main concern with the draft concerns transparent clocks, as in 
section 4.1.4.  A  PTP transparent clock is really just a Layer 2 or IP 
forwarder with a timestamping mechanism based on a syntonized timebase.  
Every forwarder on the master-slave path with significant queueing and 
other variable delays must have the transparent clock mechanism, else 
there will be loss of accuracy.   Any forwarder can mount a MITM DOS 
attack on a secured clock correction field by corrupting it. To say 
nothing of greatly complicating the forwarding process and perhaps even 
adding inaccuracy.

Which leads me to suggest that perhaps rather than trying to 
authenticate the TC and protect the clock correction field as security 
mechanisms in the PTP or its encapsulation  might cause more problems 
and risks than the threats they eliminates.    Maybe it would be better 
to think about this as a secure routing or signaling problem, and use 
signaling or routing to constrain the set of feasible paths to those 
which have a trusted, authenticated TC on each hop.  This becomes a 
problem for RSVP or LDP for the MPLS encapsulation, and OSPF and ISIS 
for IP tunneling.   I suspect (have not dug into it, though) that most 
of the mechanisms we'd need already exist.

Dan

On 8/2/2012 12:10 PM, tictoc-request@ietf.org wrote:
>
>
> Date: Thu, 2 Aug 2012 19:10:39 +0300
> From: Tal Mizrahi <talmi@marvell.com>
> To: "tictoc@ietf.org" <tictoc@ietf.org>
> Subject: [TICTOC] TICTOC Security Requirements
> Message-ID:
> 	<74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>
> Following this week's TICTOC meeting:
>
> 1.       We plan to release draft 03 within a month, and proceed to WG last call.
>
> 2.       Therefore, I will appreciate if people can send any comments they may have by Aug 22.
>
> 3.       There was some discussion about the "proventication" requirement. I would like to suggest to change the terminology in the document, since I understand this term is not very popular.
> However, I believe that the requirement for a chain of trust is still an important and valid requirement. Please comment if you think otherwise.
>
> Thanks,
> Tal.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840b451f/attachment.htm>
>
> ------------------------------
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
> End of TICTOC Digest, Vol 68, Issue 10
> **************************************
>


From talmi@marvell.com  Thu Aug  2 10:17:14 2012
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 D277921E80FA for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 10:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  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 OlJybacgexbr for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 10:17:14 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id 882AD21E80DE for <tictoc@ietf.org>; Thu,  2 Aug 2012 10:17:13 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: Dan Grossman <ldg004@earthlink.net>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 2 Aug 2012 20:17:07 +0300
Thread-Topic: [TICTOC]  TICTOC Security Requirements
Thread-Index: Ac1wzxmeM7eyTcQOS3muVcezkvuDUwAAVnGQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F88915A2@IL-MB01.marvell.com>
References: <mailman.2909.1343923847.3364.tictoc@ietf.org> <501AAFB1.50104@earthlink.net>
In-Reply-To: <501AAFB1.50104@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [TICTOC] 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, 02 Aug 2012 17:17:15 -0000

Hi Dan,

I understand your concern: basically the synchronization protocol can be co=
mpromised by a MITM attack even if the TCs are authenticated.
However, it sounds like you are suggesting a solution, and this document at=
tempts to focus on requirements and not solutions.
Authenticating the TC prevents simple attacks that can be performed by "wea=
k" attackers, referred to in the document as external injector attackers. I=
t does not prevent more advanced attacks from "advanced" attackers, e.g., i=
nternal attackers, or MITM delay attacks. I find it essential to require th=
at the security mechanism prevents the easiest-to-implement attacks, as the=
se are the most likely ones.

I suggest to add a description to this section in the document, and clarify=
 the point above.

Tal.


-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Dan Grossman
Sent: Thursday, August 02, 2012 9:50 AM
To: tictoc@ietf.org
Subject: [TICTOC] TICTOC Security Requirements

Tal,
I wasn't able to get meeting audio, so don't know whether this was discusse=
d.

My main concern with the draft concerns transparent clocks, as in section 4=
.1.4.  A  PTP transparent clock is really just a Layer 2 or IP forwarder wi=
th a timestamping mechanism based on a syntonized timebase. =20
Every forwarder on the master-slave path with significant queueing and othe=
r variable delays must have the transparent clock mechanism, else=20
there will be loss of accuracy.   Any forwarder can mount a MITM DOS=20
attack on a secured clock correction field by corrupting it. To say nothing=
 of greatly complicating the forwarding process and perhaps even adding ina=
ccuracy.

Which leads me to suggest that perhaps rather than trying to authenticate t=
he TC and protect the clock correction field as security mechanisms in the =
PTP or its encapsulation  might cause more problems=20
and risks than the threats they eliminates.    Maybe it would be better=20
to think about this as a secure routing or signaling problem, and use signa=
ling or routing to constrain the set of feasible paths to those which have =
a trusted, authenticated TC on each hop.  This becomes a problem for RSVP o=
r LDP for the MPLS encapsulation, and OSPF and ISIS=20
for IP tunneling.   I suspect (have not dug into it, though) that most=20
of the mechanisms we'd need already exist.

Dan

On 8/2/2012 12:10 PM, tictoc-request@ietf.org wrote:
>
>
> Date: Thu, 2 Aug 2012 19:10:39 +0300
> From: Tal Mizrahi <talmi@marvell.com>
> To: "tictoc@ietf.org" <tictoc@ietf.org>
> Subject: [TICTOC] TICTOC Security Requirements
> Message-ID:
> 	<74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
> Content-Type: text/plain; charset=3D"us-ascii"
>
> Hi,
>
> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>
> Following this week's TICTOC meeting:
>
> 1.       We plan to release draft 03 within a month, and proceed to WG la=
st call.
>
> 2.       Therefore, I will appreciate if people can send any comments the=
y may have by Aug 22.
>
> 3.       There was some discussion about the "proventication" requirement=
. I would like to suggest to change the terminology in the document, since =
I understand this term is not very popular.
> However, I believe that the requirement for a chain of trust is still an =
important and valid requirement. Please comment if you think otherwise.
>
> Thanks,
> Tal.
>
> -------------- next part -------------- An HTML attachment was=20
> scrubbed...
> URL:=20
> <http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840b
> 451f/attachment.htm>
>
> ------------------------------
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>
> End of TICTOC Digest, Vol 68, Issue 10
> **************************************
>

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From internet-drafts@ietf.org  Thu Aug  2 11:58:06 2012
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 6289F11E8104; Thu,  2 Aug 2012 11:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, 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 IkQ6svcVfBOV; Thu,  2 Aug 2012 11:58:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE51C11E818D; Thu,  2 Aug 2012 11:58:05 -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.33
Message-ID: <20120802185805.24036.33724.idtracker@ietfa.amsl.com>
Date: Thu, 02 Aug 2012 11:58:05 -0700
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-03.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, 02 Aug 2012 18:58:06 -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           : Precision Time Protocol Version 2 (PTPv2) Management Inf=
ormation Base
	Author(s)       : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-03.txt
	Pages           : 65
	Date            : 2012-07-31

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing networks using
   Precision Time Protocol.

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03

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


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


From ldg004@earthlink.net  Thu Aug  2 12:48:48 2012
Return-Path: <ldg004@earthlink.net>
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 690AE11E818C for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 12:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level: 
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[AWL=0.803,  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 vn4mHh4Qpgcd for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 12:48:46 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 98AB811E8183 for <tictoc@ietf.org>; Thu,  2 Aug 2012 12:48:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XIArKR5moeDc2pl/UB1IQ7VLDpOGgLHX8gO7/Jq0gHPrNVhAhkP80c132ZGTwP3c; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [108.49.37.59] (helo=[192.168.1.3]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ldg004@earthlink.net>) id 1Sx1O1-0002XW-6w; Thu, 02 Aug 2012 15:48:45 -0400
Message-ID: <501AD99B.1090103@earthlink.net>
Date: Thu, 02 Aug 2012 15:48:43 -0400
From: Dan Grossman <ldg004@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>
References: <mailman.2909.1343923847.3364.tictoc@ietf.org> <501AAFB1.50104@earthlink.net> <74470498B659FA4687F0B0018C19A89C01A0F88915A2@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F88915A2@IL-MB01.marvell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 5fd9b736a583489594f5150ab1c16ac0485087bba56e60094c0c4f2e9954f40c01702d9b73cf2121350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 108.49.37.59
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 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, 02 Aug 2012 19:48:48 -0000

Hi Tal,

I appreciate the need to avoid crossing the line between requirements 
and mechanisms, and was trying hard not to.  If anything, I had the 
sense that Section 4.1.4 was hinting at particular mechanisms.

Thanks for explaining your rationale for  TC authentication.  It makes 
more sense to me now. You're right, more detail is needed here.  
However, I'm wondering if it wouldn't be redundant with Master 
authentication, at least for end-to-end transparent clocks.  After all, 
an injection attack would also have to spoof an authenticated master.  
Am I missing something?

Rgds
Dan
On 8/2/2012 1:17 PM, Tal Mizrahi wrote:
> Hi Dan,
>
> I understand your concern: basically the synchronization protocol can be compromised by a MITM attack even if the TCs are authenticated.
> However, it sounds like you are suggesting a solution, and this document attempts to focus on requirements and not solutions.
> Authenticating the TC prevents simple attacks that can be performed by "weak" attackers, referred to in the document as external injector attackers. It does not prevent more advanced attacks from "advanced" attackers, e.g., internal attackers, or MITM delay attacks. I find it essential to require that the security mechanism prevents the easiest-to-implement attacks, as these are the most likely ones.
>
> I suggest to add a description to this section in the document, and clarify the point above.
>
> Tal.
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of Dan Grossman
> Sent: Thursday, August 02, 2012 9:50 AM
> To: tictoc@ietf.org
> Subject: [TICTOC] TICTOC Security Requirements
>
> Tal,
> I wasn't able to get meeting audio, so don't know whether this was discussed.
>
> My main concern with the draft concerns transparent clocks, as in section 4.1.4.  A  PTP transparent clock is really just a Layer 2 or IP forwarder with a timestamping mechanism based on a syntonized timebase.
> Every forwarder on the master-slave path with significant queueing and other variable delays must have the transparent clock mechanism, else
> there will be loss of accuracy.   Any forwarder can mount a MITM DOS
> attack on a secured clock correction field by corrupting it. To say nothing of greatly complicating the forwarding process and perhaps even adding inaccuracy.
>
> Which leads me to suggest that perhaps rather than trying to authenticate the TC and protect the clock correction field as security mechanisms in the PTP or its encapsulation  might cause more problems
> and risks than the threats they eliminates.    Maybe it would be better
> to think about this as a secure routing or signaling problem, and use signaling or routing to constrain the set of feasible paths to those which have a trusted, authenticated TC on each hop.  This becomes a problem for RSVP or LDP for the MPLS encapsulation, and OSPF and ISIS
> for IP tunneling.   I suspect (have not dug into it, though) that most
> of the mechanisms we'd need already exist.
>
> Dan
>
> On 8/2/2012 12:10 PM, tictoc-request@ietf.org wrote:
>>
>> Date: Thu, 2 Aug 2012 19:10:39 +0300
>> From: Tal Mizrahi <talmi@marvell.com>
>> To: "tictoc@ietf.org" <tictoc@ietf.org>
>> Subject: [TICTOC] TICTOC Security Requirements
>> Message-ID:
>> 	<74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>>
>> Following this week's TICTOC meeting:
>>
>> 1.       We plan to release draft 03 within a month, and proceed to WG last call.
>>
>> 2.       Therefore, I will appreciate if people can send any comments they may have by Aug 22.
>>
>> 3.       There was some discussion about the "proventication" requirement. I would like to suggest to change the terminology in the document, since I understand this term is not very popular.
>> However, I believe that the requirement for a chain of trust is still an important and valid requirement. Please comment if you think otherwise.
>>
>> Thanks,
>> Tal.
>>
>> -------------- next part -------------- An HTML attachment was
>> scrubbed...
>> URL:
>> <http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840b
>> 451f/attachment.htm>
>>
>> ------------------------------
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>>
>> End of TICTOC Digest, Vol 68, Issue 10
>> **************************************
>>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


From talmi@marvell.com  Thu Aug  2 14:49:01 2012
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 86D1521E8093 for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 14:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level: 
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.024,  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 Wui4X8+Gu4RT for <tictoc@ietfa.amsl.com>; Thu,  2 Aug 2012 14:49:00 -0700 (PDT)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id AC38511E8117 for <tictoc@ietf.org>; Thu,  2 Aug 2012 14:48:59 -0700 (PDT)
From: Tal Mizrahi <talmi@marvell.com>
To: Dan Grossman <ldg004@earthlink.net>
Date: Fri, 3 Aug 2012 00:48:48 +0300
Thread-Topic: [TICTOC]  TICTOC Security Requirements
Thread-Index: Ac1w59aIjP3tixuaTbS91t1Ov8T9iAADwMTg
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F88915C7@IL-MB01.marvell.com>
References: <mailman.2909.1343923847.3364.tictoc@ietf.org> <501AAFB1.50104@earthlink.net> <74470498B659FA4687F0B0018C19A89C01A0F88915A2@IL-MB01.marvell.com> <501AD99B.1090103@earthlink.net>
In-Reply-To: <501AD99B.1090103@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 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, 02 Aug 2012 21:49:01 -0000

Dan,

> However, I'm wondering if it wouldn't be redundant with Master authentica=
tion, at least for end-to-end transparent clocks. =20
>After all, an injection attack would also have to spoof an authenticated m=
aster.

Your point is well taken. An external injector cannot masquerade an E2E TC.
I suggest to elaborate the description, and emphasize the difference betwee=
n an E2E TC and a P2P TC in this aspect.

Your point referred to section 4.1.4, which is currently a SHOULD (not a MU=
ST). Do you see a problem to leave it a SHOULD?

Tal.


-----Original Message-----
From: Dan Grossman [mailto:ldg004@earthlink.net]=20
Sent: Thursday, August 02, 2012 12:49 PM
To: Tal Mizrahi
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] TICTOC Security Requirements

Hi Tal,

I appreciate the need to avoid crossing the line between requirements and m=
echanisms, and was trying hard not to.  If anything, I had the sense that S=
ection 4.1.4 was hinting at particular mechanisms.

Thanks for explaining your rationale for  TC authentication.  It makes more=
 sense to me now. You're right, more detail is needed here. =20
However, I'm wondering if it wouldn't be redundant with Master authenticati=
on, at least for end-to-end transparent clocks.  After all, an injection at=
tack would also have to spoof an authenticated master. =20
Am I missing something?

Rgds
Dan
On 8/2/2012 1:17 PM, Tal Mizrahi wrote:
> Hi Dan,
>
> I understand your concern: basically the synchronization protocol can be =
compromised by a MITM attack even if the TCs are authenticated.
> However, it sounds like you are suggesting a solution, and this document =
attempts to focus on requirements and not solutions.
> Authenticating the TC prevents simple attacks that can be performed by "w=
eak" attackers, referred to in the document as external injector attackers.=
 It does not prevent more advanced attacks from "advanced" attackers, e.g.,=
 internal attackers, or MITM delay attacks. I find it essential to require =
that the security mechanism prevents the easiest-to-implement attacks, as t=
hese are the most likely ones.
>
> I suggest to add a description to this section in the document, and clari=
fy the point above.
>
> Tal.
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On=20
> Behalf Of Dan Grossman
> Sent: Thursday, August 02, 2012 9:50 AM
> To: tictoc@ietf.org
> Subject: [TICTOC] TICTOC Security Requirements
>
> Tal,
> I wasn't able to get meeting audio, so don't know whether this was discus=
sed.
>
> My main concern with the draft concerns transparent clocks, as in section=
 4.1.4.  A  PTP transparent clock is really just a Layer 2 or IP forwarder =
with a timestamping mechanism based on a syntonized timebase.
> Every forwarder on the master-slave path with significant queueing and ot=
her variable delays must have the transparent clock mechanism, else
> there will be loss of accuracy.   Any forwarder can mount a MITM DOS
> attack on a secured clock correction field by corrupting it. To say nothi=
ng of greatly complicating the forwarding process and perhaps even adding i=
naccuracy.
>
> Which leads me to suggest that perhaps rather than trying to authenticate=
 the TC and protect the clock correction field as security mechanisms in th=
e PTP or its encapsulation  might cause more problems
> and risks than the threats they eliminates.    Maybe it would be better
> to think about this as a secure routing or signaling problem, and use sig=
naling or routing to constrain the set of feasible paths to those which hav=
e a trusted, authenticated TC on each hop.  This becomes a problem for RSVP=
 or LDP for the MPLS encapsulation, and OSPF and ISIS
> for IP tunneling.   I suspect (have not dug into it, though) that most
> of the mechanisms we'd need already exist.
>
> Dan
>
> On 8/2/2012 12:10 PM, tictoc-request@ietf.org wrote:
>>
>> Date: Thu, 2 Aug 2012 19:10:39 +0300
>> From: Tal Mizrahi <talmi@marvell.com>
>> To: "tictoc@ietf.org" <tictoc@ietf.org>
>> Subject: [TICTOC] TICTOC Security Requirements
>> Message-ID:
>> 	<74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
>> Content-Type: text/plain; charset=3D"us-ascii"
>>
>> Hi,
>>
>> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>>
>> Following this week's TICTOC meeting:
>>
>> 1.       We plan to release draft 03 within a month, and proceed to WG l=
ast call.
>>
>> 2.       Therefore, I will appreciate if people can send any comments th=
ey may have by Aug 22.
>>
>> 3.       There was some discussion about the "proventication" requiremen=
t. I would like to suggest to change the terminology in the document, since=
 I understand this term is not very popular.
>> However, I believe that the requirement for a chain of trust is still an=
 important and valid requirement. Please comment if you think otherwise.
>>
>> Thanks,
>> Tal.
>>
>> -------------- next part -------------- An HTML attachment was=20
>> scrubbed...
>> URL:
>> <http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840
>> b
>> 451f/attachment.htm>
>>
>> ------------------------------
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>>
>> End of TICTOC Digest, Vol 68, Issue 10
>> **************************************
>>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


From dieter.sibold@ptb.de  Fri Aug  3 06:38:34 2012
Return-Path: <dieter.sibold@ptb.de>
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 1907421F8D65 for <tictoc@ietfa.amsl.com>; Fri,  3 Aug 2012 06:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 y3NfUT7NiCoQ for <tictoc@ietfa.amsl.com>; Fri,  3 Aug 2012 06:38:33 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.106]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF6721F8D5D for <tictoc@ietf.org>; Fri,  3 Aug 2012 06:38:33 -0700 (PDT)
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 34A22B61393; Fri,  3 Aug 2012 15:38:32 +0200 (CEST)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 1CE2CBC2142; Fri,  3 Aug 2012 15:38:32 +0200 (CEST)
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
To: Tal Mizrahi <talmi@marvell.com>
MIME-Version: 1.0
X-KeepSent: 35B87DA9:3581BE5B-C1257A4F:004A99D1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
Message-ID: <OF35B87DA9.3581BE5B-ONC1257A4F.004A99D1-C1257A4F.004AEF98@ptb.de>
From: dieter.sibold@ptb.de
Date: Fri, 3 Aug 2012 15:38:29 +0200
X-MIMETrack: S/MIME Sign by Notes Client on Dieter Sibold/PTB(Release 8.5.3|September 15, 2011) at 03.08.2012 15:38:30, Serialize by Notes Client on Dieter Sibold/PTB(Release 8.5.3|September 15, 2011) at 03.08.2012 15:38:30, Serialize complete at 03.08.2012 15:38:30, Itemize by Notes Client on Dieter Sibold/PTB(Release 8.5.3|September 15, 2011) at 03.08.2012 15:38:31, S/MIME Sign complete at 03.08.2012 15:38:31, Serialize by Router on ROSE/PTB(Release 8.5.3|September 15, 2011) at 08/03/2012 15:38:31, Serialize complete at 08/03/2012 15:38:31
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z28263_boundary_sign
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 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: Fri, 03 Aug 2012 13:38:34 -0000

This is an S/MIME signed message.

---------z28263_boundary_sign
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

SGVsbG8uDQoNClJlZ2FyZGluZyBwcm92ZW50aWNhdGlvbi4NCkkgc3VnZ2VzdCB0byBhdm9pZCB0
aGlzIHRlcm0gYXMgSSBhbHJlYWR5IG1lbnRpb25lZCBpbiB0aGUgd29ya2luZyBncm91cCANCnNl
c3Npb24uDQoNClJlZ2FyZGluZyA0LjEuMi4NCkkgYWdyZWUgdGhhdCB0aGUgY2hhaW4gb2YgdHJ1
c3QgaXMgbmVjZXNzYXJ5LiAgQnV0IEkgc3Ryb25nbHkgc3VnZ2VzdCBub3QgDQp0byByZXF1aXJl
IHRoYXQgdGhlIGNoYWluIG9mIHRydXN0IGhhcyB0byBiZSBpZGVudGljYWwgdG8gdGhlIGNoYWlu
IG9mIA0KdGltZSBzeW5jaHJvbml6YXRpb24uIEkgYWdyZWUgdGhhdCB0aGUgc2VjdXJpdHkgbWVj
aGFuaXNtIE1VU1Qgc3VwcG9ydCBhbiANCm9wZXJhdGlvbmFsIG1vZGUgaW4gd2hpY2ggdGhlIGNo
YWluIG9mIHRpbWUgc3luY2hyb25pemF0aW9uIGlzIGluY2x1ZGVkIGluIA0KdGhlIGNoYWluIG9m
IHRydXN0IGJ1dCBpdCBzaG91bGQgbm90IGJlIG1hbmRhdG9yeSBtb2RlLiANCg0KU28gdGhlIHJl
cXVpcmVtZW50IGlzIHRoYXQgdGhlIHNlY3VyaXR5IG1lY2hhbmlzbSBNVVNUIHN1cHBvcnQgYW4g
DQpvcGVyYXRpb25hbCBtb2RlIGluIHdoaWNoIHRoZSBjaGFpbiBvZiB0cnVzdCBpbmNsdWRlcyB0
aGUgdGltZSBtYXN0ZXIgaW4gDQpjYXNlcyB3aGVyZSBhbiBlbmQtdG8tZW5kIGF1dGhlbnRpY2F0
aW9uIG9mIHRoZSBtYXN0ZXIgaXMgbm90IHBvc3NpYmxlLg0KDQpEaWV0ZXINCg0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVz
YW5zdGFsdA0KUS40MiAtIFNlcnZlciBBZG1pbmlzdHJhdGlvbg0KQnVuZGVzYWxsZWUgMTAwIA0K
RC0zODExNiBCcmF1bnNjaHdlaWcNClRlbDogICAgKzQ5LTUzMS01OTItODQgMjANCkUtTWFpbDog
ZGlldGVyLnNpYm9sZEBwdGIuZGUNCg0KDQoNClZvbjogICAgVGFsIE1penJhaGkgPHRhbG1pQG1h
cnZlbGwuY29tPg0KQW46ICAgICAidGljdG9jQGlldGYub3JnIiA8dGljdG9jQGlldGYub3JnPiwg
DQpEYXR1bTogIDAyLjA4LjIwMTIgMTg6MTANCkJldHJlZmY6ICAgICAgICBbVElDVE9DXSBUSUNU
T0MgU2VjdXJpdHkgUmVxdWlyZW1lbnRzDQpHZXNlbmRldCB2b246ICAgdGljdG9jLWJvdW5jZXNA
aWV0Zi5vcmcNCg0KDQoNCkhpLA0KIA0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
aWV0Zi10aWN0b2Mtc2VjdXJpdHktcmVxdWlyZW1lbnRzLTAyDQogDQpGb2xsb3dpbmcgdGhpcyB3
ZWVr4oCZcyBUSUNUT0MgbWVldGluZzoNCjEuICAgICAgIFdlIHBsYW4gdG8gcmVsZWFzZSBkcmFm
dCAwMyB3aXRoaW4gYSBtb250aCwgYW5kIHByb2NlZWQgdG8gV0cgDQpsYXN0IGNhbGwuDQoyLiAg
ICAgICBUaGVyZWZvcmUsIEkgd2lsbCBhcHByZWNpYXRlIGlmIHBlb3BsZSBjYW4gc2VuZCBhbnkg
Y29tbWVudHMgdGhleSANCm1heSBoYXZlIGJ5IEF1ZyAyMi4NCjMuICAgICAgIFRoZXJlIHdhcyBz
b21lIGRpc2N1c3Npb24gYWJvdXQgdGhlIOKAnHByb3ZlbnRpY2F0aW9u4oCdIHJlcXVpcmVtZW50
LiANCkkgd291bGQgbGlrZSB0byBzdWdnZXN0IHRvIGNoYW5nZSB0aGUgdGVybWlub2xvZ3kgaW4g
dGhlIGRvY3VtZW50LCBzaW5jZSBJIA0KdW5kZXJzdGFuZCB0aGlzIHRlcm0gaXMgbm90IHZlcnkg
cG9wdWxhci4NCkhvd2V2ZXIsIEkgYmVsaWV2ZSB0aGF0IHRoZSByZXF1aXJlbWVudCBmb3IgYSBj
aGFpbiBvZiB0cnVzdCBpcyBzdGlsbCBhbiANCmltcG9ydGFudCBhbmQgdmFsaWQgcmVxdWlyZW1l
bnQuIFBsZWFzZSBjb21tZW50IGlmIHlvdSB0aGluayBvdGhlcndpc2UuDQogDQpUaGFua3MsDQpU
YWwuDQogX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClRJ
Q1RPQyBtYWlsaW5nIGxpc3QNClRJQ1RPQ0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby90aWN0b2MNCg0KDQo=

---------z28263_boundary_sign
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIImgAIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBoIIjkjCCA58w
ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz
Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT
GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw
MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT
FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD
QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu
3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp
I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB
PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP
GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq
B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw
BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL
E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH
YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ
5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f
uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj
KIaS8xiE2PvRzwVWZFcwggOfMIICh6ADAgECAgEmMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYT
AkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1
c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw05OTA3MDkx
MjExMDBaFw0xOTA3MDkyMzU5MDBaMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBU
ZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0
c2NoZSBUZWxla29tIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKsL
ozXgiykUsRSFrzwQ5DlvNV1Krt3qYY2VSfRvZKMaYGakqUAihNnUpeV4kw5oAa25TVw6ztO4qEJA
38+juoJZapIbrBya2ggrJSf5aSNH8eDrLHqb9RMC0H40fMKePABZq/XaDPUyPCusUNrWw96DlMqo
DJkyDghIVltq+9rhWFgBSV9yQTwVBgGOXa2quJO0zZ7rp+hqLVI02zrvXHVR2tvzMfnucZgyxFQV
RAz5m1Xtrd8YCKCjhopJ7lMFjxlM1d5YeZvSahxCq8XVp89oD5bk4WGYdmHIkXzWPgDikVCH4Z0K
5q2X0h3GOn3LvNoDNNWOWwH1age3FrZuSn8CAwEAAaNCMEAwHQYDVR0OBBYEFDHDeRu69VPXF+CJ
ei0XbAqzK50zMA8GA1UdEwQIMAYBAf8CAQUwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUA
A4IBAQCUZFmtOWTnKesT/lrDixNXyAQk8HR3wGDjZ/vpiaaDv5aCfG7Uwz3vnoBuuym0mHqxO1Tr
ORdHfhqOC/wfMVkxBLLOF/Msx2I2VeIi2IlVtJhIqmT61hw22ER4WlojOleX9XowT66fakxLK46g
A+M+4KnU0nvSs6jicjytnv+AWeSbRbT2O7DNORmYMuXqIWGQ5DEhjjSx9y81SoUQ2ueKNyG+WWPg
8oWIMVPUVBSFcHn0LgZ3J3UvH7iK+f7Futg25IPs52W3v2Na80avgZQ31EGM1iPWHs/1aBtEY6Ja
uqc1WaHlcAWbDiNXmZQKbbo5YyiGkvMYhNj70c8FVmRXMIIEITCCAwmgAwIBAgICAMcwDQYJKoZI
hvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAd
BgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20g
Um9vdCBDQSAyMB4XDTA2MTIxOTEwMjkwMFoXDTE5MDYzMDIzNTkwMFowWjELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkRGTi1WZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJl
aW4gUENBIEdsb2JhbCAtIEcwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOmbw2eF
+Q2u9Y1Uw5ZQNT1i6W5M7ZTXAFuVInTUIOs0j9bswDEEC5mB4qYU0lKgKCOEi3SJBF5b4OJ4wXjL
FssoNTl7LZBF0O2gAHp8v0oOGwDDhulcKzERewzzgiRDjBw4i2poAJru3E94q9LGE5t2re7eJujv
Aa90D8EJovZrzr3TzRQwT/Xl46TIYpuCGgMnMA0CZWBN7dEJIyqWNVgn03bGcbaQHcTt/zWGfW8z
s9sPxRHCioOhlF1Ba9jSEPVM/cpRrNm975KDu9rrixZWVkPP4dUTPaYfJzDNSVTbyRM0mnF1xWzq
pwuY+SGdJ68+ozk5SGqMrcmZ+8MS8r0CAwEAAaOB2TCB1jBwBgNVHR8EaTBnMGWgY6Bhhl9odHRw
Oi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNybD8tY3Js
X2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjAdBgNVHQ4EFgQUSbfGz+g9H3/qRHsT
KffxCnA+3mQwHwYDVR0jBBgwFoAUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDgYDVR0PAQH/BAQDAgEG
MBIGA1UdEwEB/wQIMAYBAf8CAQIwDQYJKoZIhvcNAQEFBQADggEBADvhWnfASBfcqRjsga9aifC9
KJKmylkYEnDsKPLnrn+WLOfyXRkx9hMrdL29gLK592fJOaJ5O+EREe5reJEzfjtfJid1U2WOM2Pu
z3PDsJIjSSFQdSOhHxjilIU9PzPpdyCNor3moYUpQPY/czJYDQlrptqFbMA/u41mZFYkTq4NPzI1
AVvpjILZcllPsYaF8XSFVuXD+Fzzje5Hs1MFcOflTYppgyjhEwmGnl7I6lgeDB/5pNRaBGj9KD6L
ArZYtfahLDdXAGerI2iNY6XvmWtc/UtW9qtAhzTUEZJs7IfFCgsHM3K0bwwdVCzYUcfMvzDTQ3Lx
Mr+MzkljqAD38hwwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJE
RTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0
IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5MTAy
OTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcAW5Ui
dNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4bAMOG
6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXjpMhi
m4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9ylGs
2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7wxLy
vQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9jZ2kt
YmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1ZXI9
RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAWgBQx
w3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBAjAN
BgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/JdGTH2
Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/M+l3
II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4XPON
7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Za1z9
S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBO8wggPXoAMC
AQICBA0hCk0wDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1WZXJl
aW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAtIEcw
MTAeFw0wODEwMjQwODUyMTNaFw0xOTA2MzAwMDAwMDBaMGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQK
EyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0Ex
GTAXBgkqhkiG9w0BCQEWCnBraUBwdGIuZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQC8CsKDOSrDYswBi5TfxUlODIYEL4+n66/DnYua0jowQyIWvTFjpITNhwMbfPk1KiFmKx2cvtu7
wR7swUPdNlfWNUGJ7/9Q0AmpdsedTMTyFslgJHnJ1v1aojOhPk/MbTuolZuVuJ1ytlVwJAR5/1XU
JpHJ9e6qJJM6CJuo4Ms/3w3uMwgibPaKlSAx2gbI6BKH+p2zlIzoJSDAx64njZClg2i32uLUgoDB
7KEghrdMA2y7nqxzL4Vzb5dY5+y4iZ54txqK7ock+TpfnlBP6RZoChB/qonIle/xv+fqXWeZMhTY
BjYHkSc7+shP4Nb4wnLvv8c77uu3BrOe6e1cyDK3AgMBAAGjggGsMIIBqDASBgNVHRMBAf8ECDAG
AQH/AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwFQYDVR0RBA4wDIEKcGtpQHB0Yi5kZTCBiAYDVR0f
BIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2Ny
bC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev
cHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUFBzAChjtodHRwOi8v
Y2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBHBggr
BgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAJ3KSKdj6GjgE6pSuE74pBcKLfmC2Phy1Gfj
83Lzx9leQX67sL6uTIV5NTQgQDsjTlqyxRQJ5eYhj+ZjwfVS02pDdD+trg2iGp1WdFFsqyhts+oS
M4SpRUuZ83FHEieuWq9teT7bcWPUzckYy4k17u9LAp7+V1h7s6aOpk9RCyA1sSlFTP33O9tpLwXq
KpXHK+zG9JOV7kPDHYLAi2Krw5LB91EBSyXWLu7xK4i6prEUGRWVblckx116ikhBFy3cNr2NGfhh
KiOCphAeIFPCCxOEvRk/LkZRnZaMnHQsUHVuAs2SBB08coYSjF7/NZAXprZlpI2KZiUfeo6JU9bS
UbowggTvMIID16ADAgECAgQNIQpNMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYD
VQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBD
QSBHbG9iYWwgLSBHMDEwHhcNMDgxMDI0MDg1MjEzWhcNMTkwNjMwMDAwMDAwWjBpMQswCQYDVQQG
EwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0G
A1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAvArCgzkqw2LMAYuU38VJTgyGBC+Pp+uvw52LmtI6MEMiFr0xY6SEzYcD
G3z5NSohZisdnL7bu8Ee7MFD3TZX1jVBie//UNAJqXbHnUzE8hbJYCR5ydb9WqIzoT5PzG07qJWb
lbidcrZVcCQEef9V1CaRyfXuqiSTOgibqODLP98N7jMIImz2ipUgMdoGyOgSh/qds5SM6CUgwMeu
J42QpYNot9ri1IKAweyhIIa3TANsu56scy+Fc2+XWOfsuImeeLcaiu6HJPk6X55QT+kWaAoQf6qJ
yJXv8b/n6l1nmTIU2AY2B5EnO/rIT+DW+MJy77/HO+7rtwaznuntXMgytwIDAQABo4IBrDCCAagw
EgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8EBAMCAQYwHQYDVR0OBBYEFMSA0G4oFWgxWuxwX3iO
4TBDOOo0MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBUGA1UdEQQOMAyBCnBraUBw
dGIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2ds
b2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEF
BQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2Nh
Y2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3Qt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCdykinY+ho4BOqUrhO
+KQXCi35gtj4ctRn4/Ny88fZXkF+u7C+rkyFeTU0IEA7I05assUUCeXmIY/mY8H1UtNqQ3Q/ra4N
ohqdVnRRbKsobbPqEjOEqUVLmfNxRxInrlqvbXk+23Fj1M3JGMuJNe7vSwKe/ldYe7OmjqZPUQsg
NbEpRUz99zvbaS8F6iqVxyvsxvSTle5Dwx2CwItiq8OSwfdRAUsl1i7u8SuIuqaxFBkVlW5XJMdd
eopIQRct3Da9jRn4YSojgqYQHiBTwgsThL0ZPy5GUZ2WjJx0LFB1bgLNkgQdPHKGEoxe/zWQF6a2
ZaSNimYlH3qOiVPW0lG6MIIFCjCCA/KgAwIBAgIHE3VRA4JzBjANBgkqhkiG9w0BAQUFADBpMQsw
CQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFs
dDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMB4XDTEyMDMwNjA5
MDU1NVoXDTE1MDMwNjA5MDU1NVowaDELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNj
aC1UZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDTALBgNVBAsTBFEuNDIxGjAYBgNVBAMTEURyLiBE
aWV0ZXIgU2lib2xkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3A4qPUWvMdRKdf6n
8n4ILMz17CkFLSBykOfvNqK0Xki5G1uEN0Lm4B9OznfnLLetkncla3k/LUVI7CfjFoYM/CS3BfQg
gO9sTHi9oTyusMCm+to0JeEJ5oIijmGzIPLRGTXjQP1Hy/HFcRHvSbGNGK2S6hOBiM7Upn1bnZLc
3Y8Cd0SW9Dk0ZB1LfBi4sy+cqzTi0YU5LTfg2blwWJPoZW1zxCerdPMnoAu+EcD3naDjjR6K0A6H
0KIMmb3JsGBW7Uz7yyAllmF3QUpFGL2I6vHdSYBqIaxxv7qsly6juExhZqsxKpyZYeECs+W2fz8B
Nzf2nxGHlGDqvzje5gEpUQIDAQABo4IBtjCCAbIwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwKQYD
VR0lBCIwIAYIKwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBSMITESopjC
ckNxeIcM6c7MrI80gzAfBgNVHSMEGDAWgBTEgNBuKBVoMVrscF94juEwQzjqNDAfBgNVHREEGDAW
gRRkaWV0ZXIuc2lib2xkQHB0Yi5kZTB3BgNVHR8EcDBuMDWgM6Axhi9odHRwOi8vY2RwMS5wY2Eu
ZGZuLmRlL3B0Yi1jYS9wdWIvY3JsL2NhY3JsLmNybDA1oDOgMYYvaHR0cDovL2NkcDIucGNhLmRm
bi5kZS9wdGItY2EvcHViL2NybC9jYWNybC5jcmwwgZIGCCsGAQUFBwEBBIGFMIGCMD8GCCsGAQUF
BzAChjNodHRwOi8vY2RwMS5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQw
PwYIKwYBBQUHMAKGM2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvcHRiLWNhL3B1Yi9jYWNlcnQvY2Fj
ZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEADZnBfu/SYDcvnobrn/SPrQkf/b9cXJOiZDDTsT5C
TG6M9tP6vp6Ng1JmecoDHesQG4zOBMGo2Bop9lQiXfEXAQlmJL1aE/F+bdFoJ8OLd1+CQOdciKwY
ndt+fXP6eZNUPE366bOYM9EFOU0HxjyzJSaZO7aa+POXFeA8teX/KmWuCvLbPAedZBIbj9lcZMwa
c1zoLgoHOk+jywDfbNnU8y8KFW6lZ/rpL8L2VUqIVBrdoUkau4Hc2LJ3bRYfU8Usx29sJHMOrW3c
k4E63FoujxLVLl9uxsdEN20TJQaY9RsVzTnOJmqa2mLlcG6EkUGOivnP24Wueo2Go+8rT+LuEzCC
BQowggPyoAMCAQICBxN1UQOCcwYwDQYJKoZIhvcNAQEFBQAwaTELMAkGA1UEBhMCREUxLjAsBgNV
BAoTJVBoeXNpa2FsaXNjaC1UZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDzANBgNVBAMTBlBUQiBD
QTEZMBcGCSqGSIb3DQEJARYKcGtpQHB0Yi5kZTAeFw0xMjAzMDYwOTA1NTVaFw0xNTAzMDYwOTA1
NTVaMGgxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5k
ZXNhbnN0YWx0MQ0wCwYDVQQLEwRRLjQyMRowGAYDVQQDExFEci4gRGlldGVyIFNpYm9sZDCCASIw
DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANwOKj1FrzHUSnX+p/J+CCzM9ewpBS0gcpDn7zai
tF5IuRtbhDdC5uAfTs535yy3rZJ3JWt5Py1FSOwn4xaGDPwktwX0IIDvbEx4vaE8rrDApvraNCXh
CeaCIo5hsyDy0Rk140D9R8vxxXER70mxjRitkuoTgYjO1KZ9W52S3N2PAndElvQ5NGQdS3wYuLMv
nKs04tGFOS034Nm5cFiT6GVtc8Qnq3TzJ6ALvhHA952g440eitAOh9CiDJm9ybBgVu1M+8sgJZZh
d0FKRRi9iOrx3UmAaiGscb+6rJcuo7hMYWarMSqcmWHhArPltn8/ATc39p8Rh5Rg6r843uYBKVEC
AwEAAaOCAbYwggGyMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1UdJQQiMCAGCCsGAQUFBwMC
BggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQUjCExEqKYwnJDcXiHDOnOzKyPNIMwHwYD
VR0jBBgwFoAUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0RBBgwFoEUZGlldGVyLnNpYm9sZEBw
dGIuZGUwdwYDVR0fBHAwbjA1oDOgMYYvaHR0cDovL2NkcDEucGNhLmRmbi5kZS9wdGItY2EvcHVi
L2NybC9jYWNybC5jcmwwNaAzoDGGL2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvcHRiLWNhL3B1Yi9j
cmwvY2FjcmwuY3JsMIGSBggrBgEFBQcBAQSBhTCBgjA/BggrBgEFBQcwAoYzaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9wdGItY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MD8GCCsGAQUFBzAChjNodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcN
AQEFBQADggEBAA2ZwX7v0mA3L56G65/0j60JH/2/XFyTomQw07E+QkxujPbT+r6ejYNSZnnKAx3r
EBuMzgTBqNgaKfZUIl3xFwEJZiS9WhPxfm3RaCfDi3dfgkDnXIisGJ3bfn1z+nmTVDxN+umzmDPR
BTlNB8Y8syUmmTu2mvjzlxXgPLXl/yplrgry2zwHnWQSG4/ZXGTMGnNc6C4KBzpPo8sA32zZ1PMv
ChVupWf66S/C9lVKiFQa3aFJGruB3Niyd20WH1PFLMdvbCRzDq1t3JOBOtxaLo8S1S5fbsbHRDdt
EyUGmPUbFc05ziZqmtpi5XBuhJFBjor5z9uFrnqNhqPvK0/i7hMxggLJMIICxQIBATB0MGkxCzAJ
BgNVBAYTAkRFMS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0
MQ8wDQYDVQQDEwZQVEIgQ0ExGTAXBgkqhkiG9w0BCQEWCnBraUBwdGIuZGUCBxN1UQOCcwYwCQYF
Kw4DAhoFAKCCASowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIw
ODAzMTMzODMxWjAjBgkqhkiG9w0BCQQxFgQU5NJd6D/Rd/zyDSnLszf/ISn85cIwQwYJKoZIhvcN
AQkPMTYwNDAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYIKoZIhvcNAwcwDQYIKoZIhvcNAwIC
ASgwgYUGCyqGSIb3DQEJEAILMXagdDBpMQswCQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxp
c2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcN
AQkBFgpwa2lAcHRiLmRlAgcTdVEDgnMGMA0GCSqGSIb3DQEBAQUABIIBAHp5zkmLbVzc8w8/AJWd
NLi+1E6OsP87FTtnwQ0yFgV18l8z9e6Pnl97WCrk0gaf/e7khiGbktz10NaC8C39LNQ3XqQ4VYkv
e97O9qGYC+YxFjdqHdGcEkoKnzSfO8lNNpRXF6W84zne9YDtBeMHJq9w8ag195dmzmovXgjuuPwe
E/HGSZiK6m/nSjD9U7caTZDrd+4hUWe4Nfa1JGDmdxxCrRSciug/1DnfJAHRdwWDBrksy25qad86
diIzoMwoAyvE2bheUYi+o4xI8Wje/FZdyOOYJ/aLL+6G5BtavN+UC/BUNTcuznkliM1zHcq1l4yK
q7z+XUNg7O15Uv+ShzIAAAAA

---------z28263_boundary_sign--

From ldg004@earthlink.net  Mon Aug  6 13:00:29 2012
Return-Path: <ldg004@earthlink.net>
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 23D2F11E809A for <tictoc@ietfa.amsl.com>; Mon,  6 Aug 2012 13:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.602,  BAYES_00=-2.599, 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 8hjh6wLQv6gK for <tictoc@ietfa.amsl.com>; Mon,  6 Aug 2012 13:00:27 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 5B59821F84C4 for <tictoc@ietf.org>; Mon,  6 Aug 2012 13:00:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=PKFeb2Odp6p/M14gsNUzYxXJmAwCzgjCN9T85Rx7DnGdBgf5OtyhoEXoSwgS87gv; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [108.49.37.59] (helo=[192.168.1.3]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ldg004@earthlink.net>) id 1SyTTW-0007FN-Py; Mon, 06 Aug 2012 16:00:27 -0400
Message-ID: <5020224F.8030706@earthlink.net>
Date: Mon, 06 Aug 2012 16:00:15 -0400
From: Dan Grossman <ldg004@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>
References: <mailman.2909.1343923847.3364.tictoc@ietf.org> <501AAFB1.50104@earthlink.net> <74470498B659FA4687F0B0018C19A89C01A0F88915A2@IL-MB01.marvell.com> <501AD99B.1090103@earthlink.net> <74470498B659FA4687F0B0018C19A89C01A0F88915C7@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F88915C7@IL-MB01.marvell.com>
Content-Type: multipart/alternative; boundary="------------040507090001000101080301"
X-ELNK-Trace: 5fd9b736a583489594f5150ab1c16ac0485087bba56e6009c294ef908bd0f9db6b436a75f7bb5b32350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 108.49.37.59
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] 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: Mon, 06 Aug 2012 20:00:29 -0000

This is a multi-part message in MIME format.
--------------040507090001000101080301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tal,
Let me suggest some words.  This isn't exactly parallel construction 
with the rest of this section, but I think the subject is different 
enough to justify that:

4.1.4 
<http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02#section-4.1.4>. 
PTP: Authentication of Transparent Clocks



Requirement

    The combination of security mechanisms for PTP, and routing and control plane mechanisms
    SHOULD provide a means to authenticate TCs along the Master-Slave path.

Discussion

    Correct PTP operation depends upon trusted transparent clocks at each hop along the
    Master-Slave path (except for hops which have negligible variable latency, such as hubs).
    The accuracy of the PTP can be attacked by malicious TCs which deliberately
    manipulate the correctionField, by inserting forwarders which are not TCs
    in the path, or (for Peer-to-Peer TCs) manipulate Pdelay_Req, Pdelay_Resp or
    Pdelay_Follow-up messages. Malicious TCs (and other forwarders) can also be used for MITM
    attacks, including DoS and accuracy attacks.

    Note that determination of the Master-Slave path is outside the scope of PTP.   Therefore,
    this requirement will need to be addressed at least in part by mechanisms congruent to
    path determination, i.e., routing and control plane.
     

Does this make sense?
Dan

On 8/2/2012 5:48 PM, Tal Mizrahi wrote:
> Dan,
>
>> However, I'm wondering if it wouldn't be redundant with Master authentication, at least for end-to-end transparent clocks.
>> After all, an injection attack would also have to spoof an authenticated master.
> Your point is well taken. An external injector cannot masquerade an E2E TC.
> I suggest to elaborate the description, and emphasize the difference between an E2E TC and a P2P TC in this aspect.
>
> Your point referred to section 4.1.4, which is currently a SHOULD (not a MUST). Do you see a problem to leave it a SHOULD?
>
> Tal.
>
>
> -----Original Message-----
> From: Dan Grossman [mailto:ldg004@earthlink.net]
> Sent: Thursday, August 02, 2012 12:49 PM
> To: Tal Mizrahi
> Cc: tictoc@ietf.org
> Subject: Re: [TICTOC] TICTOC Security Requirements
>
> Hi Tal,
>
> I appreciate the need to avoid crossing the line between requirements and mechanisms, and was trying hard not to.  If anything, I had the sense that Section 4.1.4 was hinting at particular mechanisms.
>
> Thanks for explaining your rationale for  TC authentication.  It makes more sense to me now. You're right, more detail is needed here.
> However, I'm wondering if it wouldn't be redundant with Master authentication, at least for end-to-end transparent clocks.  After all, an injection attack would also have to spoof an authenticated master.
> Am I missing something?
>
> Rgds
> Dan
> On 8/2/2012 1:17 PM, Tal Mizrahi wrote:
>> Hi Dan,
>>
>> I understand your concern: basically the synchronization protocol can be compromised by a MITM attack even if the TCs are authenticated.
>> However, it sounds like you are suggesting a solution, and this document attempts to focus on requirements and not solutions.
>> Authenticating the TC prevents simple attacks that can be performed by "weak" attackers, referred to in the document as external injector attackers. It does not prevent more advanced attacks from "advanced" attackers, e.g., internal attackers, or MITM delay attacks. I find it essential to require that the security mechanism prevents the easiest-to-implement attacks, as these are the most likely ones.
>>
>> I suggest to add a description to this section in the document, and clarify the point above.
>>
>> Tal.
>>
>>
>> -----Original Message-----
>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On
>> Behalf Of Dan Grossman
>> Sent: Thursday, August 02, 2012 9:50 AM
>> To: tictoc@ietf.org
>> Subject: [TICTOC] TICTOC Security Requirements
>>
>> Tal,
>> I wasn't able to get meeting audio, so don't know whether this was discussed.
>>
>> My main concern with the draft concerns transparent clocks, as in section 4.1.4.  A  PTP transparent clock is really just a Layer 2 or IP forwarder with a timestamping mechanism based on a syntonized timebase.
>> Every forwarder on the master-slave path with significant queueing and other variable delays must have the transparent clock mechanism, else
>> there will be loss of accuracy.   Any forwarder can mount a MITM DOS
>> attack on a secured clock correction field by corrupting it. To say nothing of greatly complicating the forwarding process and perhaps even adding inaccuracy.
>>
>> Which leads me to suggest that perhaps rather than trying to authenticate the TC and protect the clock correction field as security mechanisms in the PTP or its encapsulation  might cause more problems
>> and risks than the threats they eliminates.    Maybe it would be better
>> to think about this as a secure routing or signaling problem, and use signaling or routing to constrain the set of feasible paths to those which have a trusted, authenticated TC on each hop.  This becomes a problem for RSVP or LDP for the MPLS encapsulation, and OSPF and ISIS
>> for IP tunneling.   I suspect (have not dug into it, though) that most
>> of the mechanisms we'd need already exist.
>>
>> Dan
>>
>> On 8/2/2012 12:10 PM, tictoc-request@ietf.org wrote:
>>> Date: Thu, 2 Aug 2012 19:10:39 +0300
>>> From: Tal Mizrahi <talmi@marvell.com>
>>> To: "tictoc@ietf.org" <tictoc@ietf.org>
>>> Subject: [TICTOC] TICTOC Security Requirements
>>> Message-ID:
>>> 	<74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi,
>>>
>>> http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02
>>>
>>> Following this week's TICTOC meeting:
>>>
>>> 1.       We plan to release draft 03 within a month, and proceed to WG last call.
>>>
>>> 2.       Therefore, I will appreciate if people can send any comments they may have by Aug 22.
>>>
>>> 3.       There was some discussion about the "proventication" requirement. I would like to suggest to change the terminology in the document, since I understand this term is not very popular.
>>> However, I believe that the requirement for a chain of trust is still an important and valid requirement. Please comment if you think otherwise.
>>>
>>> Thanks,
>>> Tal.
>>>
>>> -------------- next part -------------- An HTML attachment was
>>> scrubbed...
>>> URL:
>>> <http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840
>>> b
>>> 451f/attachment.htm>
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> TICTOC mailing list
>>> TICTOC@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tictoc
>>>
>>>
>>> End of TICTOC Digest, Vol 68, Issue 10
>>> **************************************
>>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>
>


--------------040507090001000101080301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Tal,<br>
      Let me suggest some words.&nbsp; This isn't exactly parallel
      construction with the rest of this section, but I think the
      subject is different enough to justify that:<br>
      <br>
      <a class="selflink" name="section-4.1.4"
href="http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02#section-4.1.4">4.1.4</a>.
      PTP: Authentication of Transparent Clocks<br>
      <pre class="newpage"><span class="h4"></span>

Requirement

   The combination of security mechanisms for PTP, and routing and control plane mechanisms
 &nbsp; SHOULD provide a means to authenticate TCs along the Master-Slave path.  

Discussion

   Correct PTP operation depends upon trusted transparent clocks at each hop along the
  &nbsp;Master-Slave path (except for hops which have negligible variable latency, such as hubs). 
   The accuracy of the PTP can be attacked by malicious TCs which deliberately
  &nbsp;manipulate the correctionField, by inserting forwarders which are not TCs
   in the path, or (for Peer-to-Peer TCs) manipulate Pdelay_Req, Pdelay_Resp or
   Pdelay_Follow-up messages. Malicious TCs (and other forwarders) can also be used for MITM
   attacks, including DoS and accuracy attacks.

   Note that determination of the Master-Slave path is outside the scope of PTP.   Therefore,
   this requirement will need to be addressed at least in part by mechanisms congruent to
   path determination, i.e., routing and control plane.
    
</pre>
      Does this make sense?<br>
      Dan<br>
      <br>
      On 8/2/2012 5:48 PM, Tal Mizrahi wrote:<br>
    </div>
    <blockquote
cite="mid:74470498B659FA4687F0B0018C19A89C01A0F88915C7@IL-MB01.marvell.com"
      type="cite">
      <pre wrap="">Dan,

</pre>
      <blockquote type="cite">
        <pre wrap="">However, I'm wondering if it wouldn't be redundant with Master authentication, at least for end-to-end transparent clocks.  
After all, an injection attack would also have to spoof an authenticated master.
</pre>
      </blockquote>
      <pre wrap="">
Your point is well taken. An external injector cannot masquerade an E2E TC.
I suggest to elaborate the description, and emphasize the difference between an E2E TC and a P2P TC in this aspect.

Your point referred to section 4.1.4, which is currently a SHOULD (not a MUST). Do you see a problem to leave it a SHOULD?

Tal.


-----Original Message-----
From: Dan Grossman [<a class="moz-txt-link-freetext" href="mailto:ldg004@earthlink.net">mailto:ldg004@earthlink.net</a>] 
Sent: Thursday, August 02, 2012 12:49 PM
To: Tal Mizrahi
Cc: <a class="moz-txt-link-abbreviated" href="mailto:tictoc@ietf.org">tictoc@ietf.org</a>
Subject: Re: [TICTOC] TICTOC Security Requirements

Hi Tal,

I appreciate the need to avoid crossing the line between requirements and mechanisms, and was trying hard not to.  If anything, I had the sense that Section 4.1.4 was hinting at particular mechanisms.

Thanks for explaining your rationale for  TC authentication.  It makes more sense to me now. You're right, more detail is needed here.  
However, I'm wondering if it wouldn't be redundant with Master authentication, at least for end-to-end transparent clocks.  After all, an injection attack would also have to spoof an authenticated master.  
Am I missing something?

Rgds
Dan
On 8/2/2012 1:17 PM, Tal Mizrahi wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi Dan,

I understand your concern: basically the synchronization protocol can be compromised by a MITM attack even if the TCs are authenticated.
However, it sounds like you are suggesting a solution, and this document attempts to focus on requirements and not solutions.
Authenticating the TC prevents simple attacks that can be performed by "weak" attackers, referred to in the document as external injector attackers. It does not prevent more advanced attacks from "advanced" attackers, e.g., internal attackers, or MITM delay attacks. I find it essential to require that the security mechanism prevents the easiest-to-implement attacks, as these are the most likely ones.

I suggest to add a description to this section in the document, and clarify the point above.

Tal.


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:tictoc-bounces@ietf.org">mailto:tictoc-bounces@ietf.org</a>] On 
Behalf Of Dan Grossman
Sent: Thursday, August 02, 2012 9:50 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:tictoc@ietf.org">tictoc@ietf.org</a>
Subject: [TICTOC] TICTOC Security Requirements

Tal,
I wasn't able to get meeting audio, so don't know whether this was discussed.

My main concern with the draft concerns transparent clocks, as in section 4.1.4.  A  PTP transparent clock is really just a Layer 2 or IP forwarder with a timestamping mechanism based on a syntonized timebase.
Every forwarder on the master-slave path with significant queueing and other variable delays must have the transparent clock mechanism, else
there will be loss of accuracy.   Any forwarder can mount a MITM DOS
attack on a secured clock correction field by corrupting it. To say nothing of greatly complicating the forwarding process and perhaps even adding inaccuracy.

Which leads me to suggest that perhaps rather than trying to authenticate the TC and protect the clock correction field as security mechanisms in the PTP or its encapsulation  might cause more problems
and risks than the threats they eliminates.    Maybe it would be better
to think about this as a secure routing or signaling problem, and use signaling or routing to constrain the set of feasible paths to those which have a trusted, authenticated TC on each hop.  This becomes a problem for RSVP or LDP for the MPLS encapsulation, and OSPF and ISIS
for IP tunneling.   I suspect (have not dug into it, though) that most
of the mechanisms we'd need already exist.

Dan

On 8/2/2012 12:10 PM, <a class="moz-txt-link-abbreviated" href="mailto:tictoc-request@ietf.org">tictoc-request@ietf.org</a> wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">
Date: Thu, 2 Aug 2012 19:10:39 +0300
From: Tal Mizrahi <a class="moz-txt-link-rfc2396E" href="mailto:talmi@marvell.com">&lt;talmi@marvell.com&gt;</a>
To: <a class="moz-txt-link-rfc2396E" href="mailto:tictoc@ietf.org">"tictoc@ietf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:tictoc@ietf.org">&lt;tictoc@ietf.org&gt;</a>
Subject: [TICTOC] TICTOC Security Requirements
Message-ID:
	<a class="moz-txt-link-rfc2396E" href="mailto:74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com">&lt;74470498B659FA4687F0B0018C19A89C01A0F8891597@IL-MB01.marvell.com&gt;</a>
Content-Type: text/plain; charset="us-ascii"

Hi,

<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02">http://tools.ietf.org/html/draft-ietf-tictoc-security-requirements-02</a>

Following this week's TICTOC meeting:

1.       We plan to release draft 03 within a month, and proceed to WG last call.

2.       Therefore, I will appreciate if people can send any comments they may have by Aug 22.

3.       There was some discussion about the "proventication" requirement. I would like to suggest to change the terminology in the document, since I understand this term is not very popular.
However, I believe that the requirement for a chain of trust is still an important and valid requirement. Please comment if you think otherwise.

Thanks,
Tal.

-------------- next part -------------- An HTML attachment was 
scrubbed...
URL:
<a class="moz-txt-link-rfc2396E" href="http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840b451f/attachment.htm">&lt;http://www.ietf.org/mail-archive/web/tictoc/attachments/20120802/840
b
451f/attachment.htm&gt;</a>

------------------------------

_______________________________________________
TICTOC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a>


End of TICTOC Digest, Vol 68, Issue 10
**************************************

</pre>
        </blockquote>
        <pre wrap="">_______________________________________________
TICTOC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a>

</pre>
      </blockquote>
      <pre wrap="">


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040507090001000101080301--

From Peter.Meyer@microsemi.com  Tue Aug 14 08:20:57 2012
Return-Path: <Peter.Meyer@microsemi.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 3AA4B21F84CF for <tictoc@ietfa.amsl.com>; Tue, 14 Aug 2012 08:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-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 o47E500JNgRz for <tictoc@ietfa.amsl.com>; Tue, 14 Aug 2012 08:20:55 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id F274E21F847B for <tictoc@ietf.org>; Tue, 14 Aug 2012 08:20:54 -0700 (PDT)
Received: from mail67-co1-R.bigfish.com (10.243.78.228) by CO1EHSOBE014.bigfish.com (10.243.66.77) with Microsoft SMTP Server id 14.1.225.23; Tue, 14 Aug 2012 15:20:53 +0000
Received: from mail67-co1 (localhost [127.0.0.1])	by mail67-co1-R.bigfish.com (Postfix) with ESMTP id A2E56740347; Tue, 14 Aug 2012 15:20:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:208.19.100.20; KIP:(null); UIP:(null); IPV:NLI; H:avsrv0100.microsemi.net; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VS-21(zz9371Ic85fhzz1202hzz1033IL8275bh8275dhz2dh668h839hd25hf0ah107ah)
Received: from mail67-co1 (localhost.localdomain [127.0.0.1]) by mail67-co1 (MessageSwitch) id 134495765154300_9673; Tue, 14 Aug 2012 15:20:51 +0000 (UTC)
Received: from CO1EHSMHS031.bigfish.com (unknown [10.243.78.231])	by mail67-co1.bigfish.com (Postfix) with ESMTP id 01B4454004A; Tue, 14 Aug 2012 15:20:51 +0000 (UTC)
Received: from avsrv0100.microsemi.net (208.19.100.20) by CO1EHSMHS031.bigfish.com (10.243.66.41) with Microsoft SMTP Server id 14.1.225.23; Tue, 14 Aug 2012 15:20:48 +0000
Received: from avsrv0110.microsemi.net ([10.100.34.110]) by avsrv0100.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 14 Aug 2012 08:20:48 -0700
Received: from ottsrv0015.microsemi.net ([134.199.15.151]) by avsrv0110.microsemi.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 14 Aug 2012 08:20:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD7A30.5901087C"
Date: Tue, 14 Aug 2012 11:20:43 -0400
Message-ID: <64683B4805156847B0ED373DAB3057CA935110@ottsrv0015.microsemi.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [TICTOC] Questions regaridng 1588 over MPLS
Thread-Index: Ac1vX/3cqELPcksBSQ64WClgxq4MoQAyGCBAAoHjwSA=
References: <4A6CE49E6084B141B15C0713B8993F280687F1@SJEXCHMB12.corp.ad.broadcom.com> <07F7D7DED63154409F13298786A2ADC90452C9A0@EXRAD5.ad.rad.co.il>
From: "Meyer, Peter" <Peter.Meyer@microsemi.com>
To: Yaakov Stein <yaakov_s@rad.com>, Shahram Davari <davari@broadcom.com>, <tictoc@ietf.org>
X-OriginalArrivalTime: 14 Aug 2012 15:20:34.0446 (UTC) FILETIME=[59A29AE0:01CD7A30]
X-OriginatorOrg: microsemi.com
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS
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: Tue, 14 Aug 2012 15:20:57 -0000

------_=_NextPart_001_01CD7A30.5901087C
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Shahram,

=20

I think another topic that would be good to progress was discussed on
the exploder in March -- how to handle packets that do not flow through
the network element, but are generated & terminated each node (e.g.
peer-delay messages).  These packets (similar to point 3 below) may be
event or general messages.  Refer to last e-mail of chain on March 22,
subject "[TICTOC] Updated 1588 over MPLS draf-03".

=20

Regards,

Peter

=20

=20

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
Of Yaakov Stein
Sent: August 1, 2012 5:11 PM
To: Shahram Davari; tictoc@ietf.org
Subject: Re: [TICTOC] Questions regaridng 1588 over MPLS

=20

During today's TICTOC meeting I raised the following questions. We need
your feedback on these questions in order to progress this draft.

=20

1.	Should CW be mandatory?=20

	a.	If not, then a PTP-LSP needs to carry only one type of
PW (either with CW or without CW) but not mix so that LSRs can correctly
parse the packet=20
	b.	=20
	c.	Without PW the job of LSRs becomes more complex to
identify the OAM packets=20

[YJS] I believe that it is fine to require a CW. RFC 5994 makes the CW
mandatory for Ethernet PWs over MPLS-TP,

I believe that TP will be the main use case.

=20

2.	Should ECMP/Entropy be disallowed?=20

	a.	The current consensus is yes, no ECMP or Entropy shall
be used.=20

[YJS] entropy labels should be disallowed.=20

Obviously timing flows should in general should not be shifted from one
path

to another path with different delay, if undetected the delay jump will
cause

an accumulating phase error.

I understand that with TC this point is less important, but this draft
explicitly speaks of only partial on-path support.

=20

Should PHP (Penultimate Hop Popping) be allowed?

[YJS] Once again, if the main use case is MPLS-TP, then this may be
automatic

3.	How to transport 1588 messages that don't need TS or CF update?=20

	a.	Send them over non-PTP LSP?=20
	b.	Let the LSRs do the parsing and perform TS or CF updated
based on message type?=20

[YJS] They should be sent over the same PW.

Since the setup specifies the timing flow type,

the regular 1588 parser will be called anyway.

=20

4.	Should P2MP LSP & P2MP PW be supported?=20

[YJS] No strong opinion.

=20

5.	Should protection be supported for PTP-LSP?=20

	a.	FRR, 1:1 and 1+1=20

[YJS] Similar to my response above, protection should NOT be supported,

as a change of path means a change in delay, which if undetected can be
worse than losing the timing flow

and going into holdover.

=20

6.	How does LSP/PW connectivity failure interact with 1588?=20

	a.	Does the Slave select another master when a failure
happens?=20
	b.	Can the protection make the failure invisible to Salve
clock?=20

[YJS] b. should never be allowed. a. is a configuration option.

=20

7.	Should only VCCV1 and VCCV4 be allowed?=20

	a.	If not then the VCCV type needs to be the same for all
PW in the PTP-LSP so that LSRs can correctly parse the packet=20

[YJS] We are presently in the process of obsoleting type 2 anyway.

So we are left with the issue of type 3, which is mostly for MS-PWs.

Do you see this being used for the MS case ?

=20

=20


------_=_NextPart_001_01CD7A30.5901087C
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-microsoft-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"Microsoft Word 12 =
(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:0cm;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:161824352;
	mso-list-template-ids:1271434634;}
@list l0:level1
	{mso-level-start-at:7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:172110370;
	mso-list-template-ids:-443375676;}
@list l1:level1
	{mso-level-start-at:4;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:426927436;
	mso-list-template-ids:-600167242;}
@list l2:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:924805987;
	mso-list-template-ids:150642650;}
@list l3:level1
	{mso-level-start-at:6;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4
	{mso-list-id:1336959428;
	mso-list-template-ids:-710243444;}
@list l4:level1
	{mso-level-start-at:3;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5
	{mso-list-id:1360282173;
	mso-list-type:hybrid;
	mso-list-template-ids:-789962778 466019428 1316780848 1321392198 =
-2049035336 1939888188 1296344838 -102624414 -400270498 -1523913190;}
@list l5:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6
	{mso-list-id:1385832963;
	mso-list-template-ids:775312432;}
@list l6:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7
	{mso-list-id:1573002393;
	mso-list-template-ids:-1260649448;}
@list l7:level1
	{mso-level-start-at:5;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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 =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Shahram,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I think another topic =
that would be good to progress was discussed on the exploder in March -- =
how to handle packets that do not flow through the network element, but =
are generated &amp; terminated each node (e.g. peer-delay messages). =
&nbsp;These packets (similar to point 3 below) may be event or general =
messages.&nbsp; Refer to last e-mail of chain on March 22, subject =
&#8220;[TICTOC] Updated 1588 over MPLS =
draf-03&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Peter<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] <b>On Behalf Of =
</b>Yaakov Stein<br><b>Sent:</b> August 1, 2012 5:11 PM<br><b>To:</b> =
Shahram Davari; tictoc@ietf.org<br><b>Subject:</b> Re: [TICTOC] =
Questions regaridng 1588 over MPLS<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>During =
today&#8217;s TICTOC meeting I raised the following questions. We need =
your feedback on these questions in order to progress this =
draft.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><ol =
style=3D'margin-top:0cm' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>Should CW be mandatory? =
<o:p></o:p></li><ol style=3D'margin-top:0cm' start=3D1 type=3Da><li =
class=3DMsoNormal style=3D'mso-list:l5 level2 lfo3'>If not, then a =
PTP-LSP needs to carry only one type of PW (either with CW or without =
CW) but not mix so that LSRs can correctly parse the packet =
<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l5 level2 =
lfo3'><o:p>&nbsp;</o:p></li><li class=3DMsoNormal style=3D'mso-list:l5 =
level2 lfo3'>Without PW the job of LSRs becomes more complex to identify =
the OAM packets <o:p></o:p></li></ol></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] I believe that it is fine to require a CW. =
RFC 5994 makes the CW mandatory for Ethernet PWs over =
MPLS-TP,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I believe that TP will be the main use =
case.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D2 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>Should ECMP/Entropy be disallowed? =
<o:p></o:p></li><ol style=3D'margin-top:0cm' start=3D1 type=3Da><li =
class=3DMsoNormal style=3D'mso-list:l5 level2 lfo3'>The current =
consensus is yes, no ECMP or Entropy shall be used. =
<o:p></o:p></li></ol></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] entropy labels should be disallowed. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Obviously timing flows should in general should =
not be shifted from one path<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>to another path with =
different delay, if undetected the delay jump will =
cause<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>an accumulating phase =
error.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I understand that with TC this point is less =
important, but this draft explicitly speaks of only partial on-path =
support.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>Should PHP (Penultimate Hop Popping) be =
allowed?<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] Once again, if the main use case is =
MPLS-TP, then this may be automatic<o:p></o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D3 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>How to transport 1588 messages that =
don&#8217;t need TS or CF update? <o:p></o:p></li><ol =
style=3D'margin-top:0cm' start=3D1 type=3Da><li class=3DMsoNormal =
style=3D'mso-list:l5 level2 lfo3'>Send them over non-PTP LSP? =
<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l5 level2 =
lfo3'>Let the LSRs do the parsing and perform TS or CF updated based on =
message type? <o:p></o:p></li></ol></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] They should be sent over the same =
PW.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Since the setup specifies the timing flow =
type,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>the regular 1588 parser will be called =
anyway.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D4 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>Should P2MP LSP &amp; P2MP PW be =
supported? <o:p></o:p></li></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] No strong opinion.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D5 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>Should protection be supported for =
PTP-LSP? <o:p></o:p></li><ol style=3D'margin-top:0cm' start=3D1 =
type=3Da><li class=3DMsoNormal style=3D'mso-list:l5 level2 lfo3'>FRR, =
1:1 and 1+1 <o:p></o:p></li></ol></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] Similar to my response above, protection =
should NOT be supported,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>as a change of path means a change in delay, =
which if undetected can be worse than losing the timing =
flow<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>and going into holdover.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D6 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>How does LSP/PW connectivity failure =
interact with 1588? <o:p></o:p></li><ol style=3D'margin-top:0cm' =
start=3D1 type=3Da><li class=3DMsoNormal style=3D'mso-list:l5 level2 =
lfo3'>Does the Slave select another master when a failure happens? =
<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l5 level2 =
lfo3'>Can the protection make the failure invisible to Salve clock? =
<o:p></o:p></li></ol></ol><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>[YJS] b. should never be allowed. a. is a =
configuration option.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D7 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l5 level1 lfo3'>Should only VCCV1 and VCCV4 be =
allowed? <o:p></o:p></li><ol style=3D'margin-top:0cm' start=3D1 =
type=3Da><li class=3DMsoNormal style=3D'mso-list:l5 level2 lfo3'>If not =
then the VCCV type needs to be the same for all PW in the PTP-LSP so =
that LSRs can correctly parse the packet <o:p></o:p></li></ol></ol><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>[YJS] We are presently =
in the process of obsoleting type 2 anyway.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>So we are left with the =
issue of type 3, which is mostly for MS-PWs.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Do you see this being =
used for the MS case ?<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------_=_NextPart_001_01CD7A30.5901087C--

From mayer@ntp.org  Wed Aug 29 14:44:15 2012
Return-Path: <mayer@ntp.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 B478E11E80A5 for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 14:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level: 
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1r51ovX+tH0 for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 14:44:14 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0C57711E8099 for <tictoc@ietf.org>; Wed, 29 Aug 2012 14:44:13 -0700 (PDT)
Received: from static-108-1-142-136.bstnma.east.verizon.net ([108.1.142.136] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1T6q3M-000Cij-F1; Wed, 29 Aug 2012 21:44:03 +0000
Message-ID: <503E8CF4.7030602@ntp.org>
Date: Wed, 29 Aug 2012 17:43:16 -0400
From: Danny Mayer <mayer@ntp.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Cui Yang <cuiyang@huawei.com>
References: <8CC0CB0BCAE52F46882E17828A9AE2161A032B90@SZXEML508-MBS.china.huawei.com> <4F575AF0.2060600@ntp.org> <8CC0CB0BCAE52F46882E17828A9AE2161A032D59@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC9043207DE@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A173D46@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904322E18@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A1756E8@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904324409@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A181BFC@SZXEML508-MBS.china.huawei.com>
In-Reply-To: <8CC0CB0BCAE52F46882E17828A9AE2161A181BFC@SZXEML508-MBS.china.huawei.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 108.1.142.136
X-SA-Exim-Rcpt-To: cuiyang@huawei.com, yaakov_s@rad.com, tictoc@ietf.org, zhangdacheng@huawei.com, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
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: Wed, 29 Aug 2012 21:44:15 -0000

I know that this is a rather old email message but when I was reviewing
it, it occurred to me that if IPSec requires accurate clocks to set
itself up then this won't work and you need, at least initially, to do
without IPSec.

Danny
On 3/19/2012 12:14 AM, Cui Yang wrote:
> Hi, Yaakov,
> 
> I said the IPsec tunnel “functionality” is mandatory to achieve, which means the device MUST support IPsec ESP tunnel (confidentiality and integrity).  
> 
> More specifically, TS 33.320 does explicitly describe security requirement for time synchronization, where 
> -Sec.6.3.1, Clock Synchronization Security Mechanisms for H(e)NB 
> -“The H(e)NB requires time synchronization with a time server. The H(e)NB SHALL support receiving time synchronisation messages over the secure backhaul link between H(e)NB and the SeGW”
> - “Optionally other secure clock servers may be used, which do not use the secure backhaul link. In this case the communication between these clock server(s) and H(e)NB SHALL be secured.”
> 
> From the above, my interpretation is,
> -synchronization MUST be adequately protected
> -synchronization mechanism MUST be supported by IPsec ESP tunnel mode (for devices)
> -In the case that IPsec is not chosen to use (though the devices do support), separate secured clock mechanism MUST be used.
> 
> Therefore, if IPsec tunnel is deployed, then synchronization protocol must support it; 
> otherwise different security mechanism is deployed, and a separate secure protection (more than IPsec AH) for synchronization must be provided.
> From a vendor’s point of view, it is required to investigate this problem and compare the performances of different approaches. 
> 
> Finally, answering your question, Autokey is designed “based on the premise that IPsec schemes cannot be adopted intact, since that would preclude stateless servers and severely compromise timekeeping accuracy”[RFC5906].
> But, what if the IPsec tunnel is available already? Is there any evaluation on this “severely” compromising accuracy? I wonder whether there is any benefit to setting up separate security mechanism, if the device already has end-to-end IPsec tunnel connection. 
> And I believe that our investigation and analysis on this practical problem is necessary and meaningful, which still could be greatly improved via the discussion with you all.
> 
> Thanks,
> Yang
> ==================
>  Yang Cui,  Ph.D.
>  Huawei Technologies
>  cuiyang@huawei.com
> 
>> -----邮件原件-----
>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>> 发送时间: 2012年3月18日 22:22
>> 收件人: Cui Yang
>> 抄送: tictoc@ietf.org; Danny Mayer
>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>> Synchronization Protocol
>>
>> Yang
>>
>> What do you mean by "mandatory to achieve".
>>
>> What 33.320 says is that IPsec is mandatory to implement in HW,
>> but optional to use.
>> Furthermore, my interpretation is that timing packets are explicitly not
>> covered,
>> since they mention which types of packets should be protected,
>> and none of the types mentioned describe timing packets.
>>
>> I have a question for you.
>> Were we to use NTP with Autokey and thus provide strong proventication,
>> would you see any benefit to using IPsec ?
>> Do you agree that there is a drawback to its use ?
>>
>> Y(J)S
>>
>> -----Original Message-----
>> From: Cui Yang [mailto:cuiyang@huawei.com]
>> Sent: Thursday, March 15, 2012 05:30
>> To: Yaakov Stein
>> Cc: tictoc@ietf.org; Danny Mayer
>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted
>> Synchronization Protocol
>>
>> Hi, Yaakov,
>>
>> Thanks for your comments. Please find my answer in the following.
>>
>> The IPsec tunnel functionality in backhaul link between femto and SeGW are
>> mandatory to achieve by 3GPP Technical Specification TS.33.320
>> http://www.3gpp.org/ftp/specs/html-info/33320.htm
>> -4.3.1 Backhaul link
>> -4.4.5 Requirements on Backhaul Link
>> -7.4 IPsec Tunnel Establishment
>> -etc.
>>
>> This requirement is originated from the typical use case of home based
>> wireless base station (Femto), where the backhaul cable connection is
>> commonly leased by telecom operator and through insecure networks, not
>> belonging to operator’s own network. Since the regulation and laws on
>> information security and privacy are strict in many countries, vendors are
>> requested to set up this IPsec tunnel functionality to avoid the risk of
>> information or privacy leakage. The contents encrypted in IPsec tunnel
>> include not only data plane, but also control plane, where the former carries
>> the customer’s data and voice, and the latter carries sensitive information,
>> such as the secret keys for air interface encryption. For most of operators
>> and vendors, it is considered necessary and responsible to protect customers’
>> privacy and communication security, where the best way known is IPsec
>> tunnel.
>>
>> Best regards,
>> Yang
>> ==================
>>  Yang Cui,  Ph.D.
>>  Huawei Technologies
>>  cuiyang@huawei.com
>>
>>> -----邮件原件-----
>>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>>> 发送时间: 2012年3月15日 2:36
>>> 收件人: Cui Yang
>>> 抄送: tictoc@ietf.org; Danny Mayer
>>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>> Synchronization Protocol
>>>
>>> Yang
>>>
>>> Yes, I fully appreciate the scenario you are discussing,
>>> where ALL packets MUST be encrypted.
>>>
>>> I am just questioning whether such a scenario is really mandated by any
>>> standard (I believe it is not),
>>> in which case one can simply NOT encrypt the timing packets (even if you
>>> choose to encrypt the other packets).
>>>
>>> Y(J)S
>>>
>>> -----Original Message-----
>>> From: Cui Yang [mailto:cuiyang@huawei.com]
>>> Sent: Tuesday, March 13, 2012 04:51
>>> To: Yaakov Stein; Danny Mayer
>>> Cc: tictoc@ietf.org
>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>> Synchronization Protocol
>>>
>>> Hi, Yaakov,
>>>
>>> Maybe my unclear description in the draft causes some confusion. Sorry for
>>> that.
>>> In the second motivation, we didn’t try to argue there is a scenario where
>>> timing packets must be encrypted.
>>> In contrast, we try to discuss the conditions where timing packets are
>>> transported in an insecure network and there are already IPsec ESP tunnel
>>> provided.
>>> When we try to transport the timing packets in a secure way, we can reuse
>>> the existing IPsec ESP tunnel even though the timing packets may not be
>>> confidential itself (But integrity protection is necessary, anyway).
>>>
>>> Best regards,
>>> Yang
>>> ==================
>>>  Yang Cui,  Ph.D.
>>>  Huawei Technologies
>>>  cuiyang@huawei.com
>>>
>>>> -----邮件原件-----
>>>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>>>> 发送时间: 2012年3月13日 0:47
>>>> 收件人: Cui Yang; Danny Mayer
>>>> 抄送: tictoc@ietf.org
>>>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>>> Synchronization Protocol
>>>>
>>>> Yang
>>>>
>>>> I fully understand your motivation (actually the 2nd motivation in your
>>> draft)
>>>> to handle cases where encryption of ALL packets is mandatory, including
>>>> timing ones.
>>>>
>>>> However, I am not sure that TS 33.320 really mandates encryption of
>> timing
>>>> packets.
>>>>
>>>> First, 33.320 clearly states that while implementation of IPsec is
>> mandatory,
>>>> usage is optional and based on operator policy
>>>> (with the possible exception of direct links between H(e)NBs, but these
>>> links
>>>> are optional too).
>>>> If IPsec is not used, then a lower layer mechanism can be used
>>>> (w/o any specification of what exactly this lower layer mechanism needs
>> to
>>>> do),
>>>> a method assumedly running in HW and adding almost no delay and
>>>> absolutely no delay variation.
>>>>
>>>> Second, even if the operator decides to use IPsec, then the standard
>> states
>>>> "All signalling, user, and management plane traffic over the interface
>>>> between H(e)NB and SeGW shall be sent through an IPsec ESP tunnel".
>>>> I think we can make the case that timing is neither signaling, nor user, nor
>>>> management traffic,
>>>> and thus exempt from the IPsec requirement.
>>>> Perhaps we should send 3GPP a liaison to that effect, and get an explicit
>>>> waiver.
>>>>
>>>> So, we are left with no use case mandating encrypting of timing packets,
>>>> and the problem goes away.
>>>>
>>>> Y(J)S
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On
>> Behalf
>>> Of
>>>> Cui Yang
>>>> Sent: Thursday, March 08, 2012 03:44
>>>> To: Danny Mayer
>>>> Cc: tictoc@ietf.org
>>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for
>> Encrypted
>>>> Synchronization Protocol
>>>>
>>>> Danny,
>>>>
>>>> Thanks for your comments. I will respond inline.
>>>>
>>>>> -----邮件原件-----
>>>>> 发件人: Danny Mayer [mailto:mayer@ntp.org]
>>>>> 发送时间: 2012年3月7日 20:56
>>>>> 收件人: Cui Yang
>>>>> 抄送: tictoc@ietf.org
>>>>> 主题: Re: [TICTOC] Please Comment on Practical Solutions for
>> Encrypted
>>>>> Synchronization Protocol
>>>>>
>>>>> I have already said this before and I will repeat this for the purposes
>>>>> of feedback.
>>>>>
>>>>> Time packets do not need to be encrypted as not only do they not
>>> contain
>>>>> anything secret, even if you knew the contents they are useless
>> anytime
>>>>> after the packet has been delivered.
>>>>
>>>> [Cui Yang] I will repeat our motivation.
>>>> According to globally used 3GPP standard, there is a need for establish
>>> IPsec
>>>> ESP tunnel for small home base station connecting to Security GW or
>> other
>>>> core network devices.
>>>> There have existed such a great number of IPsec ESP tunnels in the
>>>> underlying use case.
>>>> For meeting the least security requirement, it is needed to set up IPsec
>> AH
>>> or
>>>> IPsec ESP-NULL for the integrity protection.
>>>> Then it will increase the security cost.
>>>>
>>>> If there is a simple and practical solution for this problem, then why not
>> let
>>> it
>>>> be clarified?
>>>> So that, many engineers and customers can benefit from single IPsec
>>> tunnel
>>>> protection each user, which saves the cost for both.
>>>>
>>>>> You do yourself a disfavor in encrypting something that is not worth
>>>>> encrypting. It takes processing overhead, increases packet size, and
>>>>> there is no gain in doing so. You need to justify encrypting something
>>>>
>>>> [Cui Yang] I am not doing myself a disfavor, but going to provide a solution
>>> for
>>>> the practical and technical problem.
>>>> Integrity protection takes overhead, as well.
>>>> In case confidentiality is mandatory, is it a good idea to protect integrity
>>>> separately?
>>>> What we need to do, is to investigate and reduce the cost as small as
>>> possible
>>>> first, and see whether it is acceptable or not.
>>>> That is our motivation of the new draft.
>>>>
>>>>> and please don't say that it is because some other document says to
>>>>> encrypt everything. I want to know what is the benefit from doing so,
>>>>
>>>> [Cui Yang] I just answered your previous email providing the referred
>>> section
>>>> and document as you required, yesterday.
>>>>
>>>>> what are the risks in not doing so and what is the cost of doing so,
>>>>> particularly in loss of accuracy, increased error budget, etc.
>>>>
>>>> [Cui Yang] That is our new draft trying to explain, please check it before
>>>> posting your opinion.
>>>>
>>>>> The whole thing is a bad idea from what I can tell.
>>>>>
>>>>> Danny
>>>>>
>>>>
>>>> Thanks,
>>>> Yang
>>>>
>>>>
>>>>> On 3/6/2012 10:35 PM, Cui Yang wrote:
>>>>>> Hi, all,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have posted a new draft that discusses the practical solutions for
>>>>>> encrypted synchronization protocols.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Since we have discussed a lot on this problem, and the security
>>>>>> requirement of synchronization also noted that confidentiality may
>>> need
>>>>>> protection, especially in case that the confidentiality protection is
>>>>>> mandatory. Synchronization should be available when the traffic is
>>>>>> encrypted. The influences by the encryption are explained, and
>> several
>>>>>> possible solutions have been discussed.
>>>>>>
>>>>>> The URL is below, please review and comment.
>>>>>>
>>>>>>
>>>>>>
>>>>>>     Title      : Practical solutions for encrypted synchronization
>>>> protocol
>>>>>>
>>>>>> Author(s)  : Y. Cui,
>>>>>>
>>>>>> M. Bhatia,
>>>>>>
>>>>>> D. Zhang
>>>>>>
>>>>>> Filename   : draft-cui-tictoc-encrypted-synchronization-00.txt
>>>>>>
>>>>>> Pages     : 10
>>>>>>
>>>>>> Date      : Mar. 1, 2012
>>>>>>
>>>>>>    This informational document analyzes the accuracy issues with
>> time
>>>>>>
>>>>>>    synchronization protocols when time synchronization packets are
>>>>>>
>>>>>>    encrypted during transmission. In addition, several candidate
>>>>>>
>>>>>>   solutions on such issues are introduced.
>>>>>>
>>>>>>
>>>>>>
>>>>>> A URL for this Internet-Draft is:
>>>>>>
>>>>>>
>>>>
>> http://datatracker.ietf.org/doc/draft-cui-tictoc-encrypted-synchronization
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Yang
>>>>>>
>>>>>> ==================
>>>>>>
>>>>>> Yang Cui,  Ph.D.
>>>>>>
>>>>>> Huawei Technologies
>>>>>>
>>>>>> cuiyang@huawei.com
>>>> _______________________________________________
>>>> TICTOC mailing list
>>>> TICTOC@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tictoc


From ynir@checkpoint.com  Wed Aug 29 14:57:42 2012
Return-Path: <ynir@checkpoint.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 91F0921F8458 for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 14:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.273
X-Spam-Level: 
X-Spam-Status: No, score=-10.273 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, CN_BODY_35=0.339, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VktswkGkefNM for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 14:57:40 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 621D911E80EA for <tictoc@ietf.org>; Wed, 29 Aug 2012 14:57:39 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q7TLvN7p024843; Thu, 30 Aug 2012 00:57:23 +0300
X-CheckPoint: {503E8C4B-2-1B221DC2-4FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 30 Aug 2012 00:57:22 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 30 Aug 2012 00:57:22 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Danny Mayer <mayer@ntp.org>
Date: Thu, 30 Aug 2012 00:57:27 +0300
Thread-Topic: [TICTOC] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
Thread-Index: Ac2GMUQO+MYVmOE+SLyGDuXrKLx+YQ==
Message-ID: <5203A602-5BCC-4793-8B32-759E9EEF7026@checkpoint.com>
References: <8CC0CB0BCAE52F46882E17828A9AE2161A032B90@SZXEML508-MBS.china.huawei.com> <4F575AF0.2060600@ntp.org> <8CC0CB0BCAE52F46882E17828A9AE2161A032D59@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC9043207DE@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A173D46@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904322E18@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A1756E8@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904324409@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A181BFC@SZXEML508-MBS.china.huawei.com> <503E8CF4.7030602@ntp.org>
In-Reply-To: <503E8CF4.7030602@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
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: Wed, 29 Aug 2012 21:57:42 -0000

Hi Danny

I'm not sure where this is coming from, but to clarify, IPsec does not need=
 accurate clocks to set itself up.

The H(e)NB requires time synchronization for other purposes, not for settin=
g up IPsec tunnels.

Yoav

On Aug 30, 2012, at 12:43 AM, Danny Mayer wrote:

> I know that this is a rather old email message but when I was reviewing
> it, it occurred to me that if IPSec requires accurate clocks to set
> itself up then this won't work and you need, at least initially, to do
> without IPSec.
>
> Danny
> On 3/19/2012 12:14 AM, Cui Yang wrote:
>> Hi, Yaakov,
>>
>> I said the IPsec tunnel =A1=B0functionality=A1=B1 is mandatory to achiev=
e, which means the device MUST support IPsec ESP tunnel (confidentiality an=
d integrity).
>>
>> More specifically, TS 33.320 does explicitly describe security requireme=
nt for time synchronization, where
>> -Sec.6.3.1, Clock Synchronization Security Mechanisms for H(e)NB
>> -=A1=B0The H(e)NB requires time synchronization with a time server. The =
H(e)NB SHALL support receiving time synchronisation messages over the secur=
e backhaul link between H(e)NB and the SeGW=A1=B1
>> - =A1=B0Optionally other secure clock servers may be used, which do not =
use the secure backhaul link. In this case the communication between these =
clock server(s) and H(e)NB SHALL be secured.=A1=B1
>>
>> From the above, my interpretation is,
>> -synchronization MUST be adequately protected
>> -synchronization mechanism MUST be supported by IPsec ESP tunnel mode (f=
or devices)
>> -In the case that IPsec is not chosen to use (though the devices do supp=
ort), separate secured clock mechanism MUST be used.
>>
>> Therefore, if IPsec tunnel is deployed, then synchronization protocol mu=
st support it;
>> otherwise different security mechanism is deployed, and a separate secur=
e protection (more than IPsec AH) for synchronization must be provided.
>> From a vendor=A1=AFs point of view, it is required to investigate this p=
roblem and compare the performances of different approaches.
>>
>> Finally, answering your question, Autokey is designed =A1=B0based on the=
 premise that IPsec schemes cannot be adopted intact, since that would prec=
lude stateless servers and severely compromise timekeeping accuracy=A1=B1[R=
FC5906].
>> But, what if the IPsec tunnel is available already? Is there any evaluat=
ion on this =A1=B0severely=A1=B1 compromising accuracy? I wonder whether th=
ere is any benefit to setting up separate security mechanism, if the device=
 already has end-to-end IPsec tunnel connection.
>> And I believe that our investigation and analysis on this practical prob=
lem is necessary and meaningful, which still could be greatly improved via =
the discussion with you all.
>>
>> Thanks,
>> Yang
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Yang Cui,  Ph.D.
>> Huawei Technologies
>> cuiyang@huawei.com
>>
>>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>>> =B7=A2=BC=FE=C8=CB: Yaakov Stein [mailto:yaakov_s@rad.com]
>>> =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA3=D4=C218=C8=D5 22:22
>>> =CA=D5=BC=FE=C8=CB: Cui Yang
>>> =B3=AD=CB=CD: tictoc@ietf.org; Danny Mayer
>>> =D6=F7=CC=E2: RE: [TICTOC] Please Comment on Practical Solutions for En=
crypted
>>> Synchronization Protocol
>>>
>>> Yang
>>>
>>> What do you mean by "mandatory to achieve".
>>>
>>> What 33.320 says is that IPsec is mandatory to implement in HW,
>>> but optional to use.
>>> Furthermore, my interpretation is that timing packets are explicitly no=
t
>>> covered,
>>> since they mention which types of packets should be protected,
>>> and none of the types mentioned describe timing packets.
>>>
>>> I have a question for you.
>>> Were we to use NTP with Autokey and thus provide strong proventication,
>>> would you see any benefit to using IPsec ?
>>> Do you agree that there is a drawback to its use ?
>>>
>>> Y(J)S
>>>
>>> -----Original Message-----
>>> From: Cui Yang [mailto:cuiyang@huawei.com]
>>> Sent: Thursday, March 15, 2012 05:30
>>> To: Yaakov Stein
>>> Cc: tictoc@ietf.org; Danny Mayer
>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypt=
ed
>>> Synchronization Protocol
>>>
>>> Hi, Yaakov,
>>>
>>> Thanks for your comments. Please find my answer in the following.
>>>
>>> The IPsec tunnel functionality in backhaul link between femto and SeGW =
are
>>> mandatory to achieve by 3GPP Technical Specification TS.33.320
>>> http://www.3gpp.org/ftp/specs/html-info/33320.htm
>>> -4.3.1 Backhaul link
>>> -4.4.5 Requirements on Backhaul Link
>>> -7.4 IPsec Tunnel Establishment
>>> -etc.
>>>
>>> This requirement is originated from the typical use case of home based
>>> wireless base station (Femto), where the backhaul cable connection is
>>> commonly leased by telecom operator and through insecure networks, not
>>> belonging to operator=A1=AFs own network. Since the regulation and laws=
 on
>>> information security and privacy are strict in many countries, vendors =
are
>>> requested to set up this IPsec tunnel functionality to avoid the risk o=
f
>>> information or privacy leakage. The contents encrypted in IPsec tunnel
>>> include not only data plane, but also control plane, where the former c=
arries
>>> the customer=A1=AFs data and voice, and the latter carries sensitive in=
formation,
>>> such as the secret keys for air interface encryption. For most of opera=
tors
>>> and vendors, it is considered necessary and responsible to protect cust=
omers=A1=AF
>>> privacy and communication security, where the best way known is IPsec
>>> tunnel.
>>>
>>> Best regards,
>>> Yang
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> Yang Cui,  Ph.D.
>>> Huawei Technologies
>>> cuiyang@huawei.com
>>>
>>>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>>>> =B7=A2=BC=FE=C8=CB: Yaakov Stein [mailto:yaakov_s@rad.com]
>>>> =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA3=D4=C215=C8=D5 2:36
>>>> =CA=D5=BC=FE=C8=CB: Cui Yang
>>>> =B3=AD=CB=CD: tictoc@ietf.org; Danny Mayer
>>>> =D6=F7=CC=E2: RE: [TICTOC] Please Comment on Practical Solutions for E=
ncrypted
>>>> Synchronization Protocol
>>>>
>>>> Yang
>>>>
>>>> Yes, I fully appreciate the scenario you are discussing,
>>>> where ALL packets MUST be encrypted.
>>>>
>>>> I am just questioning whether such a scenario is really mandated by an=
y
>>>> standard (I believe it is not),
>>>> in which case one can simply NOT encrypt the timing packets (even if y=
ou
>>>> choose to encrypt the other packets).
>>>>
>>>> Y(J)S
>>>>
>>>> -----Original Message-----
>>>> From: Cui Yang [mailto:cuiyang@huawei.com]
>>>> Sent: Tuesday, March 13, 2012 04:51
>>>> To: Yaakov Stein; Danny Mayer
>>>> Cc: tictoc@ietf.org
>>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encryp=
ted
>>>> Synchronization Protocol
>>>>
>>>> Hi, Yaakov,
>>>>
>>>> Maybe my unclear description in the draft causes some confusion. Sorry=
 for
>>>> that.
>>>> In the second motivation, we didn=A1=AFt try to argue there is a scena=
rio where
>>>> timing packets must be encrypted.
>>>> In contrast, we try to discuss the conditions where timing packets are
>>>> transported in an insecure network and there are already IPsec ESP tun=
nel
>>>> provided.
>>>> When we try to transport the timing packets in a secure way, we can re=
use
>>>> the existing IPsec ESP tunnel even though the timing packets may not b=
e
>>>> confidential itself (But integrity protection is necessary, anyway).
>>>>
>>>> Best regards,
>>>> Yang
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> Yang Cui,  Ph.D.
>>>> Huawei Technologies
>>>> cuiyang@huawei.com
>>>>
>>>>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>>>>> =B7=A2=BC=FE=C8=CB: Yaakov Stein [mailto:yaakov_s@rad.com]
>>>>> =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA3=D4=C213=C8=D5 0:47
>>>>> =CA=D5=BC=FE=C8=CB: Cui Yang; Danny Mayer
>>>>> =B3=AD=CB=CD: tictoc@ietf.org
>>>>> =D6=F7=CC=E2: RE: [TICTOC] Please Comment on Practical Solutions for =
Encrypted
>>>>> Synchronization Protocol
>>>>>
>>>>> Yang
>>>>>
>>>>> I fully understand your motivation (actually the 2nd motivation in yo=
ur
>>>> draft)
>>>>> to handle cases where encryption of ALL packets is mandatory, includi=
ng
>>>>> timing ones.
>>>>>
>>>>> However, I am not sure that TS 33.320 really mandates encryption of
>>> timing
>>>>> packets.
>>>>>
>>>>> First, 33.320 clearly states that while implementation of IPsec is
>>> mandatory,
>>>>> usage is optional and based on operator policy
>>>>> (with the possible exception of direct links between H(e)NBs, but the=
se
>>>> links
>>>>> are optional too).
>>>>> If IPsec is not used, then a lower layer mechanism can be used
>>>>> (w/o any specification of what exactly this lower layer mechanism nee=
ds
>>> to
>>>>> do),
>>>>> a method assumedly running in HW and adding almost no delay and
>>>>> absolutely no delay variation.
>>>>>
>>>>> Second, even if the operator decides to use IPsec, then the standard
>>> states
>>>>> "All signalling, user, and management plane traffic over the interfac=
e
>>>>> between H(e)NB and SeGW shall be sent through an IPsec ESP tunnel".
>>>>> I think we can make the case that timing is neither signaling, nor us=
er, nor
>>>>> management traffic,
>>>>> and thus exempt from the IPsec requirement.
>>>>> Perhaps we should send 3GPP a liaison to that effect, and get an expl=
icit
>>>>> waiver.
>>>>>
>>>>> So, we are left with no use case mandating encrypting of timing packe=
ts,
>>>>> and the problem goes away.
>>>>>
>>>>> Y(J)S
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On
>>> Behalf
>>>> Of
>>>>> Cui Yang
>>>>> Sent: Thursday, March 08, 2012 03:44
>>>>> To: Danny Mayer
>>>>> Cc: tictoc@ietf.org
>>>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for
>>> Encrypted
>>>>> Synchronization Protocol
>>>>>
>>>>> Danny,
>>>>>
>>>>> Thanks for your comments. I will respond inline.
>>>>>
>>>>>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>>>>>> =B7=A2=BC=FE=C8=CB: Danny Mayer [mailto:mayer@ntp.org]
>>>>>> =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA3=D4=C27=C8=D5 20:56
>>>>>> =CA=D5=BC=FE=C8=CB: Cui Yang
>>>>>> =B3=AD=CB=CD: tictoc@ietf.org
>>>>>> =D6=F7=CC=E2: Re: [TICTOC] Please Comment on Practical Solutions for
>>> Encrypted
>>>>>> Synchronization Protocol
>>>>>>
>>>>>> I have already said this before and I will repeat this for the purpo=
ses
>>>>>> of feedback.
>>>>>>
>>>>>> Time packets do not need to be encrypted as not only do they not
>>>> contain
>>>>>> anything secret, even if you knew the contents they are useless
>>> anytime
>>>>>> after the packet has been delivered.
>>>>>
>>>>> [Cui Yang] I will repeat our motivation.
>>>>> According to globally used 3GPP standard, there is a need for establi=
sh
>>>> IPsec
>>>>> ESP tunnel for small home base station connecting to Security GW or
>>> other
>>>>> core network devices.
>>>>> There have existed such a great number of IPsec ESP tunnels in the
>>>>> underlying use case.
>>>>> For meeting the least security requirement, it is needed to set up IP=
sec
>>> AH
>>>> or
>>>>> IPsec ESP-NULL for the integrity protection.
>>>>> Then it will increase the security cost.
>>>>>
>>>>> If there is a simple and practical solution for this problem, then wh=
y not
>>> let
>>>> it
>>>>> be clarified?
>>>>> So that, many engineers and customers can benefit from single IPsec
>>>> tunnel
>>>>> protection each user, which saves the cost for both.
>>>>>
>>>>>> You do yourself a disfavor in encrypting something that is not worth
>>>>>> encrypting. It takes processing overhead, increases packet size, and
>>>>>> there is no gain in doing so. You need to justify encrypting somethi=
ng
>>>>>
>>>>> [Cui Yang] I am not doing myself a disfavor, but going to provide a s=
olution
>>>> for
>>>>> the practical and technical problem.
>>>>> Integrity protection takes overhead, as well.
>>>>> In case confidentiality is mandatory, is it a good idea to protect in=
tegrity
>>>>> separately?
>>>>> What we need to do, is to investigate and reduce the cost as small as
>>>> possible
>>>>> first, and see whether it is acceptable or not.
>>>>> That is our motivation of the new draft.
>>>>>
>>>>>> and please don't say that it is because some other document says to
>>>>>> encrypt everything. I want to know what is the benefit from doing so=
,
>>>>>
>>>>> [Cui Yang] I just answered your previous email providing the referred
>>>> section
>>>>> and document as you required, yesterday.
>>>>>
>>>>>> what are the risks in not doing so and what is the cost of doing so,
>>>>>> particularly in loss of accuracy, increased error budget, etc.
>>>>>
>>>>> [Cui Yang] That is our new draft trying to explain, please check it b=
efore
>>>>> posting your opinion.
>>>>>
>>>>>> The whole thing is a bad idea from what I can tell.
>>>>>>
>>>>>> Danny
>>>>>>
>>>>>
>>>>> Thanks,
>>>>> Yang
>>>>>
>>>>>
>>>>>> On 3/6/2012 10:35 PM, Cui Yang wrote:
>>>>>>> Hi, all,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I have posted a new draft that discusses the practical solutions fo=
r
>>>>>>> encrypted synchronization protocols.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Since we have discussed a lot on this problem, and the security
>>>>>>> requirement of synchronization also noted that confidentiality may
>>>> need
>>>>>>> protection, especially in case that the confidentiality protection =
is
>>>>>>> mandatory. Synchronization should be available when the traffic is
>>>>>>> encrypted. The influences by the encryption are explained, and
>>> several
>>>>>>> possible solutions have been discussed.
>>>>>>>
>>>>>>> The URL is below, please review and comment.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>    Title      : Practical solutions for encrypted synchronization
>>>>> protocol
>>>>>>>
>>>>>>> Author(s)  : Y. Cui,
>>>>>>>
>>>>>>> M. Bhatia,
>>>>>>>
>>>>>>> D. Zhang
>>>>>>>
>>>>>>> Filename   : draft-cui-tictoc-encrypted-synchronization-00.txt
>>>>>>>
>>>>>>> Pages     : 10
>>>>>>>
>>>>>>> Date      : Mar. 1, 2012
>>>>>>>
>>>>>>>   This informational document analyzes the accuracy issues with
>>> time
>>>>>>>
>>>>>>>   synchronization protocols when time synchronization packets are
>>>>>>>
>>>>>>>   encrypted during transmission. In addition, several candidate
>>>>>>>
>>>>>>>  solutions on such issues are introduced.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A URL for this Internet-Draft is:
>>>>>>>
>>>>>>>
>>>>>
>>> http://datatracker.ietf.org/doc/draft-cui-tictoc-encrypted-synchronizat=
ion
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Yang
>>>>>>>
>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>>
>>>>>>> Yang Cui,  Ph.D.
>>>>>>>
>>>>>>> Huawei Technologies
>>>>>>>
>>>>>>> cuiyang@huawei.com
>>>>> _______________________________________________
>>>>> 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
>
> Scanned by Check Point Total Security Gateway.


From cuiyang@huawei.com  Wed Aug 29 19:50:55 2012
Return-Path: <cuiyang@huawei.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 A217121F8539 for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 19:50:55 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eqYucRdnE75s for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 19:50:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9410721F852C for <tictoc@ietf.org>; Wed, 29 Aug 2012 19:50:50 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKB66819; Thu, 30 Aug 2012 02:50:47 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 30 Aug 2012 03:50:15 +0100
Received: from SZXEML426-HUB.china.huawei.com (10.72.61.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 30 Aug 2012 03:50:44 +0100
Received: from SZXEML508-MBS.china.huawei.com ([169.254.6.203]) by szxeml426-hub.china.huawei.com ([10.72.61.34]) with mapi id 14.01.0323.003; Thu, 30 Aug 2012 10:50:38 +0800
From: Cuiyang <cuiyang@huawei.com>
To: Yoav Nir <ynir@checkpoint.com>, Danny Mayer <mayer@ntp.org>
Thread-Topic: [TICTOC] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
Thread-Index: AQHNhjFRZNnN0QHKzUuipAJ6ZnWUdZdxprGA
Date: Thu, 30 Aug 2012 02:50:37 +0000
Message-ID: <8CC0CB0BCAE52F46882E17828A9AE216368615B5@SZXEML508-MBS.china.huawei.com>
References: <8CC0CB0BCAE52F46882E17828A9AE2161A032B90@SZXEML508-MBS.china.huawei.com> <4F575AF0.2060600@ntp.org> <8CC0CB0BCAE52F46882E17828A9AE2161A032D59@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC9043207DE@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A173D46@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904322E18@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A1756E8@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904324409@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A181BFC@SZXEML508-MBS.china.huawei.com> <503E8CF4.7030602@ntp.org> <5203A602-5BCC-4793-8B32-759E9EEF7026@checkpoint.com>
In-Reply-To: <5203A602-5BCC-4793-8B32-759E9EEF7026@checkpoint.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: Dawd MvNH VFVq YaGZ Zcay gebp gqlZ jSmG pJh4 reH3 sMZ0 sqnb unXf wTHP xih8 xxAS; 4; bQBhAHkAZQByAEAAbgB0AHAALgBvAHIAZwA7AG4AdABwAHcAZwBAAGwAaQBzAHQAcwAuAG4AdABwAC4AbwByAGcAOwB0AGkAYwB0AG8AYwBAAGkAZQB0AGYALgBvAHIAZwA7AHkAbgBpAHIAQABjAGgAZQBjAGsAcABvAGkAbgB0AC4AYwBvAG0A; Sosha1_v1; 7; {DE12BDB6-D4C7-49B5-9901-D883683D5BE7}; YwB1AGkAeQBhAG4AZwBAAGgAdQBhAHcAZQBpAC4AYwBvAG0A; Thu, 30 Aug 2012 02:50:27 GMT; UgBlADoAIABbAFQASQBDAFQATwBDAF0AIABQAGwAZQBhAHMAZQAgAEMAbwBtAG0AZQBuAHQAIABvAG4AIABQAHIAYQBjAHQAaQBjAGEAbAAgAFMAbwBsAHUAdABpAG8AbgBzACAAZgBvAHIAIABFAG4AYwByAHkAcAB0AGUAZAAgAFMAeQBuAGMAaAByAG8AbgBpAHoAYQB0AGkAbwBuACAAUAByAG8AdABvAGMAbwBsAA==
x-cr-puzzleid: {DE12BDB6-D4C7-49B5-9901-D883683D5BE7}
x-originating-ip: [10.111.48.119]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
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, 30 Aug 2012 02:50:56 -0000

SGksIFlvYXYsDQoNClJpZ2h0LCBJUHNlYyBkb2VzIG5vdCBuZWVkIHByZWNpc2Ugc3luY2hyb25p
emF0aW9uIGFzIGluIHRoaXMgZHJhZnQuDQpBY3R1YWxseSwgdGhpcyBpcyBjb21pbmcgZnJvbSB0
aGUgcmVxdWlyZW1lbnQgdGhhdCBzeW5jaHJvbml6YXRpb24gaW4gSVBzZWMgdHVubmVsIHdoZXJl
IGVuY3J5cHRpb24gaGFzIGJlZW4gZW5hYmxlZCwgc3VjaCBhcyBIKGUpTkIuDQoNCllhbmcNCj09
PT09PT09PT09PT09PT09PQ0KIFlhbmcgQ3VpLCAgUGguRC4NCiBIdWF3ZWkgVGVjaG5vbG9naWVz
DQogY3VpeWFuZ0BodWF3ZWkuY29tDQoNCj4gLS0tLS3pgq7ku7bljp/ku7YtLS0tLQ0KPiDlj5Hk
u7bkuro6IFlvYXYgTmlyIFttYWlsdG86eW5pckBjaGVja3BvaW50LmNvbV0NCj4g5Y+R6YCB5pe2
6Ze0OiAyMDEy5bm0OOaciDMw5pelIDU6NTcNCj4g5pS25Lu25Lq6OiBEYW5ueSBNYXllcg0KPiDm
ioTpgIE6IEN1aXlhbmc7IE5UUCBXb3JraW5nIEdyb3VwOyB0aWN0b2NAaWV0Zi5vcmcNCj4g5Li7
6aKYOiBSZTogW1RJQ1RPQ10gUGxlYXNlIENvbW1lbnQgb24gUHJhY3RpY2FsIFNvbHV0aW9ucyBm
b3IgRW5jcnlwdGVkDQo+IFN5bmNocm9uaXphdGlvbiBQcm90b2NvbA0KPiANCj4gSGkgRGFubnkN
Cj4gDQo+IEknbSBub3Qgc3VyZSB3aGVyZSB0aGlzIGlzIGNvbWluZyBmcm9tLCBidXQgdG8gY2xh
cmlmeSwgSVBzZWMgZG9lcyBub3QgbmVlZA0KPiBhY2N1cmF0ZSBjbG9ja3MgdG8gc2V0IGl0c2Vs
ZiB1cC4NCj4gDQo+IFRoZSBIKGUpTkIgcmVxdWlyZXMgdGltZSBzeW5jaHJvbml6YXRpb24gZm9y
IG90aGVyIHB1cnBvc2VzLCBub3QgZm9yIHNldHRpbmcNCj4gdXAgSVBzZWMgdHVubmVscy4NCj4g
DQo+IFlvYXYNCj4gDQo+IE9uIEF1ZyAzMCwgMjAxMiwgYXQgMTI6NDMgQU0sIERhbm55IE1heWVy
IHdyb3RlOg0KPiANCj4gPiBJIGtub3cgdGhhdCB0aGlzIGlzIGEgcmF0aGVyIG9sZCBlbWFpbCBt
ZXNzYWdlIGJ1dCB3aGVuIEkgd2FzIHJldmlld2luZw0KPiA+IGl0LCBpdCBvY2N1cnJlZCB0byBt
ZSB0aGF0IGlmIElQU2VjIHJlcXVpcmVzIGFjY3VyYXRlIGNsb2NrcyB0byBzZXQNCj4gPiBpdHNl
bGYgdXAgdGhlbiB0aGlzIHdvbid0IHdvcmsgYW5kIHlvdSBuZWVkLCBhdCBsZWFzdCBpbml0aWFs
bHksIHRvIGRvDQo+ID4gd2l0aG91dCBJUFNlYy4NCj4gPg0KPiA+IERhbm55DQo+ID4gT24gMy8x
OS8yMDEyIDEyOjE0IEFNLCBDdWkgWWFuZyB3cm90ZToNCj4gPj4gSGksIFlhYWtvdiwNCj4gPj4N
Cj4gPj4gSSBzYWlkIHRoZSBJUHNlYyB0dW5uZWwgwqHCsGZ1bmN0aW9uYWxpdHnCocKxIGlzIG1h
bmRhdG9yeSB0byBhY2hpZXZlLCB3aGljaA0KPiBtZWFucyB0aGUgZGV2aWNlIE1VU1Qgc3VwcG9y
dCBJUHNlYyBFU1AgdHVubmVsIChjb25maWRlbnRpYWxpdHkgYW5kDQo+IGludGVncml0eSkuDQo+
ID4+DQo+ID4+IE1vcmUgc3BlY2lmaWNhbGx5LCBUUyAzMy4zMjAgZG9lcyBleHBsaWNpdGx5IGRl
c2NyaWJlIHNlY3VyaXR5IHJlcXVpcmVtZW50DQo+IGZvciB0aW1lIHN5bmNocm9uaXphdGlvbiwg
d2hlcmUNCj4gPj4gLVNlYy42LjMuMSwgQ2xvY2sgU3luY2hyb25pemF0aW9uIFNlY3VyaXR5IE1l
Y2hhbmlzbXMgZm9yIEgoZSlOQg0KPiA+PiAtwqHCsFRoZSBIKGUpTkIgcmVxdWlyZXMgdGltZSBz
eW5jaHJvbml6YXRpb24gd2l0aCBhIHRpbWUgc2VydmVyLiBUaGUNCj4gSChlKU5CIFNIQUxMIHN1
cHBvcnQgcmVjZWl2aW5nIHRpbWUgc3luY2hyb25pc2F0aW9uIG1lc3NhZ2VzIG92ZXIgdGhlDQo+
IHNlY3VyZSBiYWNraGF1bCBsaW5rIGJldHdlZW4gSChlKU5CIGFuZCB0aGUgU2VHV8KhwrENCj4g
Pj4gLSDCocKwT3B0aW9uYWxseSBvdGhlciBzZWN1cmUgY2xvY2sgc2VydmVycyBtYXkgYmUgdXNl
ZCwgd2hpY2ggZG8gbm90IHVzZQ0KPiB0aGUgc2VjdXJlIGJhY2toYXVsIGxpbmsuIEluIHRoaXMg
Y2FzZSB0aGUgY29tbXVuaWNhdGlvbiBiZXR3ZWVuIHRoZXNlIGNsb2NrDQo+IHNlcnZlcihzKSBh
bmQgSChlKU5CIFNIQUxMIGJlIHNlY3VyZWQuwqHCsQ0KPiA+Pg0KPiA+PiBGcm9tIHRoZSBhYm92
ZSwgbXkgaW50ZXJwcmV0YXRpb24gaXMsDQo+ID4+IC1zeW5jaHJvbml6YXRpb24gTVVTVCBiZSBh
ZGVxdWF0ZWx5IHByb3RlY3RlZA0KPiA+PiAtc3luY2hyb25pemF0aW9uIG1lY2hhbmlzbSBNVVNU
IGJlIHN1cHBvcnRlZCBieSBJUHNlYyBFU1AgdHVubmVsDQo+IG1vZGUgKGZvciBkZXZpY2VzKQ0K
PiA+PiAtSW4gdGhlIGNhc2UgdGhhdCBJUHNlYyBpcyBub3QgY2hvc2VuIHRvIHVzZSAodGhvdWdo
IHRoZSBkZXZpY2VzIGRvDQo+IHN1cHBvcnQpLCBzZXBhcmF0ZSBzZWN1cmVkIGNsb2NrIG1lY2hh
bmlzbSBNVVNUIGJlIHVzZWQuDQo+ID4+DQo+ID4+IFRoZXJlZm9yZSwgaWYgSVBzZWMgdHVubmVs
IGlzIGRlcGxveWVkLCB0aGVuIHN5bmNocm9uaXphdGlvbiBwcm90b2NvbCBtdXN0DQo+IHN1cHBv
cnQgaXQ7DQo+ID4+IG90aGVyd2lzZSBkaWZmZXJlbnQgc2VjdXJpdHkgbWVjaGFuaXNtIGlzIGRl
cGxveWVkLCBhbmQgYSBzZXBhcmF0ZQ0KPiBzZWN1cmUgcHJvdGVjdGlvbiAobW9yZSB0aGFuIElQ
c2VjIEFIKSBmb3Igc3luY2hyb25pemF0aW9uIG11c3QgYmUNCj4gcHJvdmlkZWQuDQo+ID4+IEZy
b20gYSB2ZW5kb3LCocKvcyBwb2ludCBvZiB2aWV3LCBpdCBpcyByZXF1aXJlZCB0byBpbnZlc3Rp
Z2F0ZSB0aGlzIHByb2JsZW0NCj4gYW5kIGNvbXBhcmUgdGhlIHBlcmZvcm1hbmNlcyBvZiBkaWZm
ZXJlbnQgYXBwcm9hY2hlcy4NCj4gPj4NCj4gPj4gRmluYWxseSwgYW5zd2VyaW5nIHlvdXIgcXVl
c3Rpb24sIEF1dG9rZXkgaXMgZGVzaWduZWQgwqHCsGJhc2VkIG9uIHRoZQ0KPiBwcmVtaXNlIHRo
YXQgSVBzZWMgc2NoZW1lcyBjYW5ub3QgYmUgYWRvcHRlZCBpbnRhY3QsIHNpbmNlIHRoYXQgd291
bGQNCj4gcHJlY2x1ZGUgc3RhdGVsZXNzIHNlcnZlcnMgYW5kIHNldmVyZWx5IGNvbXByb21pc2Ug
dGltZWtlZXBpbmcNCj4gYWNjdXJhY3nCocKxW1JGQzU5MDZdLg0KPiA+PiBCdXQsIHdoYXQgaWYg
dGhlIElQc2VjIHR1bm5lbCBpcyBhdmFpbGFibGUgYWxyZWFkeT8gSXMgdGhlcmUgYW55IGV2YWx1
YXRpb24NCj4gb24gdGhpcyDCocKwc2V2ZXJlbHnCocKxIGNvbXByb21pc2luZyBhY2N1cmFjeT8g
SSB3b25kZXIgd2hldGhlciB0aGVyZSBpcyBhbnkNCj4gYmVuZWZpdCB0byBzZXR0aW5nIHVwIHNl
cGFyYXRlIHNlY3VyaXR5IG1lY2hhbmlzbSwgaWYgdGhlIGRldmljZSBhbHJlYWR5IGhhcw0KPiBl
bmQtdG8tZW5kIElQc2VjIHR1bm5lbCBjb25uZWN0aW9uLg0KPiA+PiBBbmQgSSBiZWxpZXZlIHRo
YXQgb3VyIGludmVzdGlnYXRpb24gYW5kIGFuYWx5c2lzIG9uIHRoaXMgcHJhY3RpY2FsIHByb2Js
ZW0NCj4gaXMgbmVjZXNzYXJ5IGFuZCBtZWFuaW5nZnVsLCB3aGljaCBzdGlsbCBjb3VsZCBiZSBn
cmVhdGx5IGltcHJvdmVkIHZpYSB0aGUNCj4gZGlzY3Vzc2lvbiB3aXRoIHlvdSBhbGwuDQo+ID4+
DQo+ID4+IFRoYW5rcywNCj4gPj4gWWFuZw0KPiA+PiA9PT09PT09PT09PT09PT09PT0NCj4gPj4g
WWFuZyBDdWksICBQaC5ELg0KPiA+PiBIdWF3ZWkgVGVjaG5vbG9naWVzDQo+ID4+IGN1aXlhbmdA
aHVhd2VpLmNvbQ0KPiA+Pg0KPiA+Pj4gLS0tLS3Dk8OKwrzDvsOUwq3CvMO+LS0tLS0NCj4gPj4+
IMK3wqLCvMO+w4jDizogWWFha292IFN0ZWluIFttYWlsdG86eWFha292X3NAcmFkLmNvbV0NCj4g
Pj4+IMK3wqLDi8ONw4rCscK8w6Q6IDIwMTLDhMOqM8OUw4IxOMOIw5UgMjI6MjINCj4gPj4+IMOK
w5XCvMO+w4jDizogQ3VpIFlhbmcNCj4gPj4+IMKzwq3Di8ONOiB0aWN0b2NAaWV0Zi5vcmc7IERh
bm55IE1heWVyDQo+ID4+PiDDlsO3w4zDojogUkU6IFtUSUNUT0NdIFBsZWFzZSBDb21tZW50IG9u
IFByYWN0aWNhbCBTb2x1dGlvbnMgZm9yIEVuY3J5cHRlZA0KPiA+Pj4gU3luY2hyb25pemF0aW9u
IFByb3RvY29sDQo+ID4+Pg0KPiA+Pj4gWWFuZw0KPiA+Pj4NCj4gPj4+IFdoYXQgZG8geW91IG1l
YW4gYnkgIm1hbmRhdG9yeSB0byBhY2hpZXZlIi4NCj4gPj4+DQo+ID4+PiBXaGF0IDMzLjMyMCBz
YXlzIGlzIHRoYXQgSVBzZWMgaXMgbWFuZGF0b3J5IHRvIGltcGxlbWVudCBpbiBIVywNCj4gPj4+
IGJ1dCBvcHRpb25hbCB0byB1c2UuDQo+ID4+PiBGdXJ0aGVybW9yZSwgbXkgaW50ZXJwcmV0YXRp
b24gaXMgdGhhdCB0aW1pbmcgcGFja2V0cyBhcmUgZXhwbGljaXRseSBub3QNCj4gPj4+IGNvdmVy
ZWQsDQo+ID4+PiBzaW5jZSB0aGV5IG1lbnRpb24gd2hpY2ggdHlwZXMgb2YgcGFja2V0cyBzaG91
bGQgYmUgcHJvdGVjdGVkLA0KPiA+Pj4gYW5kIG5vbmUgb2YgdGhlIHR5cGVzIG1lbnRpb25lZCBk
ZXNjcmliZSB0aW1pbmcgcGFja2V0cy4NCj4gPj4+DQo+ID4+PiBJIGhhdmUgYSBxdWVzdGlvbiBm
b3IgeW91Lg0KPiA+Pj4gV2VyZSB3ZSB0byB1c2UgTlRQIHdpdGggQXV0b2tleSBhbmQgdGh1cyBw
cm92aWRlIHN0cm9uZw0KPiBwcm92ZW50aWNhdGlvbiwNCj4gPj4+IHdvdWxkIHlvdSBzZWUgYW55
IGJlbmVmaXQgdG8gdXNpbmcgSVBzZWMgPw0KPiA+Pj4gRG8geW91IGFncmVlIHRoYXQgdGhlcmUg
aXMgYSBkcmF3YmFjayB0byBpdHMgdXNlID8NCj4gPj4+DQo+ID4+PiBZKEopUw0KPiA+Pj4NCj4g
Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+PiBGcm9tOiBDdWkgWWFuZyBbbWFp
bHRvOmN1aXlhbmdAaHVhd2VpLmNvbV0NCj4gPj4+IFNlbnQ6IFRodXJzZGF5LCBNYXJjaCAxNSwg
MjAxMiAwNTozMA0KPiA+Pj4gVG86IFlhYWtvdiBTdGVpbg0KPiA+Pj4gQ2M6IHRpY3RvY0BpZXRm
Lm9yZzsgRGFubnkgTWF5ZXINCj4gPj4+IFN1YmplY3Q6IFJlOiBbVElDVE9DXSBQbGVhc2UgQ29t
bWVudCBvbiBQcmFjdGljYWwgU29sdXRpb25zIGZvcg0KPiBFbmNyeXB0ZWQNCj4gPj4+IFN5bmNo
cm9uaXphdGlvbiBQcm90b2NvbA0KPiA+Pj4NCj4gPj4+IEhpLCBZYWFrb3YsDQo+ID4+Pg0KPiA+
Pj4gVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLiBQbGVhc2UgZmluZCBteSBhbnN3ZXIgaW4gdGhl
IGZvbGxvd2luZy4NCj4gPj4+DQo+ID4+PiBUaGUgSVBzZWMgdHVubmVsIGZ1bmN0aW9uYWxpdHkg
aW4gYmFja2hhdWwgbGluayBiZXR3ZWVuIGZlbXRvIGFuZCBTZUdXDQo+IGFyZQ0KPiA+Pj4gbWFu
ZGF0b3J5IHRvIGFjaGlldmUgYnkgM0dQUCBUZWNobmljYWwgU3BlY2lmaWNhdGlvbiBUUy4zMy4z
MjANCj4gPj4+IGh0dHA6Ly93d3cuM2dwcC5vcmcvZnRwL3NwZWNzL2h0bWwtaW5mby8zMzMyMC5o
dG0NCj4gPj4+IC00LjMuMSBCYWNraGF1bCBsaW5rDQo+ID4+PiAtNC40LjUgUmVxdWlyZW1lbnRz
IG9uIEJhY2toYXVsIExpbmsNCj4gPj4+IC03LjQgSVBzZWMgVHVubmVsIEVzdGFibGlzaG1lbnQN
Cj4gPj4+IC1ldGMuDQo+ID4+Pg0KPiA+Pj4gVGhpcyByZXF1aXJlbWVudCBpcyBvcmlnaW5hdGVk
IGZyb20gdGhlIHR5cGljYWwgdXNlIGNhc2Ugb2YgaG9tZSBiYXNlZA0KPiA+Pj4gd2lyZWxlc3Mg
YmFzZSBzdGF0aW9uIChGZW10byksIHdoZXJlIHRoZSBiYWNraGF1bCBjYWJsZSBjb25uZWN0aW9u
IGlzDQo+ID4+PiBjb21tb25seSBsZWFzZWQgYnkgdGVsZWNvbSBvcGVyYXRvciBhbmQgdGhyb3Vn
aCBpbnNlY3VyZSBuZXR3b3JrcywNCj4gbm90DQo+ID4+PiBiZWxvbmdpbmcgdG8gb3BlcmF0b3LC
ocKvcyBvd24gbmV0d29yay4gU2luY2UgdGhlIHJlZ3VsYXRpb24gYW5kIGxhd3MNCj4gb24NCj4g
Pj4+IGluZm9ybWF0aW9uIHNlY3VyaXR5IGFuZCBwcml2YWN5IGFyZSBzdHJpY3QgaW4gbWFueSBj
b3VudHJpZXMsIHZlbmRvcnMNCj4gYXJlDQo+ID4+PiByZXF1ZXN0ZWQgdG8gc2V0IHVwIHRoaXMg
SVBzZWMgdHVubmVsIGZ1bmN0aW9uYWxpdHkgdG8gYXZvaWQgdGhlIHJpc2sgb2YNCj4gPj4+IGlu
Zm9ybWF0aW9uIG9yIHByaXZhY3kgbGVha2FnZS4gVGhlIGNvbnRlbnRzIGVuY3J5cHRlZCBpbiBJ
UHNlYyB0dW5uZWwNCj4gPj4+IGluY2x1ZGUgbm90IG9ubHkgZGF0YSBwbGFuZSwgYnV0IGFsc28g
Y29udHJvbCBwbGFuZSwgd2hlcmUgdGhlIGZvcm1lcg0KPiBjYXJyaWVzDQo+ID4+PiB0aGUgY3Vz
dG9tZXLCocKvcyBkYXRhIGFuZCB2b2ljZSwgYW5kIHRoZSBsYXR0ZXIgY2FycmllcyBzZW5zaXRp
dmUNCj4gaW5mb3JtYXRpb24sDQo+ID4+PiBzdWNoIGFzIHRoZSBzZWNyZXQga2V5cyBmb3IgYWly
IGludGVyZmFjZSBlbmNyeXB0aW9uLiBGb3IgbW9zdCBvZg0KPiBvcGVyYXRvcnMNCj4gPj4+IGFu
ZCB2ZW5kb3JzLCBpdCBpcyBjb25zaWRlcmVkIG5lY2Vzc2FyeSBhbmQgcmVzcG9uc2libGUgdG8g
cHJvdGVjdA0KPiBjdXN0b21lcnPCocKvDQo+ID4+PiBwcml2YWN5IGFuZCBjb21tdW5pY2F0aW9u
IHNlY3VyaXR5LCB3aGVyZSB0aGUgYmVzdCB3YXkga25vd24gaXMgSVBzZWMNCj4gPj4+IHR1bm5l
bC4NCj4gPj4+DQo+ID4+PiBCZXN0IHJlZ2FyZHMsDQo+ID4+PiBZYW5nDQo+ID4+PiA9PT09PT09
PT09PT09PT09PT0NCj4gPj4+IFlhbmcgQ3VpLCAgUGguRC4NCj4gPj4+IEh1YXdlaSBUZWNobm9s
b2dpZXMNCj4gPj4+IGN1aXlhbmdAaHVhd2VpLmNvbQ0KPiA+Pj4NCj4gPj4+PiAtLS0tLcOTw4rC
vMO+w5TCrcK8w74tLS0tLQ0KPiA+Pj4+IMK3wqLCvMO+w4jDizogWWFha292IFN0ZWluIFttYWls
dG86eWFha292X3NAcmFkLmNvbV0NCj4gPj4+PiDCt8Kiw4vDjcOKwrHCvMOkOiAyMDEyw4TDqjPD
lMOCMTXDiMOVIDI6MzYNCj4gPj4+PiDDisOVwrzDvsOIw4s6IEN1aSBZYW5nDQo+ID4+Pj4gwrPC
rcOLw406IHRpY3RvY0BpZXRmLm9yZzsgRGFubnkgTWF5ZXINCj4gPj4+PiDDlsO3w4zDojogUkU6
IFtUSUNUT0NdIFBsZWFzZSBDb21tZW50IG9uIFByYWN0aWNhbCBTb2x1dGlvbnMgZm9yDQo+IEVu
Y3J5cHRlZA0KPiA+Pj4+IFN5bmNocm9uaXphdGlvbiBQcm90b2NvbA0KPiA+Pj4+DQo+ID4+Pj4g
WWFuZw0KPiA+Pj4+DQo+ID4+Pj4gWWVzLCBJIGZ1bGx5IGFwcHJlY2lhdGUgdGhlIHNjZW5hcmlv
IHlvdSBhcmUgZGlzY3Vzc2luZywNCj4gPj4+PiB3aGVyZSBBTEwgcGFja2V0cyBNVVNUIGJlIGVu
Y3J5cHRlZC4NCj4gPj4+Pg0KPiA+Pj4+IEkgYW0ganVzdCBxdWVzdGlvbmluZyB3aGV0aGVyIHN1
Y2ggYSBzY2VuYXJpbyBpcyByZWFsbHkgbWFuZGF0ZWQgYnkNCj4gYW55DQo+ID4+Pj4gc3RhbmRh
cmQgKEkgYmVsaWV2ZSBpdCBpcyBub3QpLA0KPiA+Pj4+IGluIHdoaWNoIGNhc2Ugb25lIGNhbiBz
aW1wbHkgTk9UIGVuY3J5cHQgdGhlIHRpbWluZyBwYWNrZXRzIChldmVuIGlmDQo+IHlvdQ0KPiA+
Pj4+IGNob29zZSB0byBlbmNyeXB0IHRoZSBvdGhlciBwYWNrZXRzKS4NCj4gPj4+Pg0KPiA+Pj4+
IFkoSilTDQo+ID4+Pj4NCj4gPj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+
IEZyb206IEN1aSBZYW5nIFttYWlsdG86Y3VpeWFuZ0BodWF3ZWkuY29tXQ0KPiA+Pj4+IFNlbnQ6
IFR1ZXNkYXksIE1hcmNoIDEzLCAyMDEyIDA0OjUxDQo+ID4+Pj4gVG86IFlhYWtvdiBTdGVpbjsg
RGFubnkgTWF5ZXINCj4gPj4+PiBDYzogdGljdG9jQGlldGYub3JnDQo+ID4+Pj4gU3ViamVjdDog
UmU6IFtUSUNUT0NdIFBsZWFzZSBDb21tZW50IG9uIFByYWN0aWNhbCBTb2x1dGlvbnMgZm9yDQo+
IEVuY3J5cHRlZA0KPiA+Pj4+IFN5bmNocm9uaXphdGlvbiBQcm90b2NvbA0KPiA+Pj4+DQo+ID4+
Pj4gSGksIFlhYWtvdiwNCj4gPj4+Pg0KPiA+Pj4+IE1heWJlIG15IHVuY2xlYXIgZGVzY3JpcHRp
b24gaW4gdGhlIGRyYWZ0IGNhdXNlcyBzb21lIGNvbmZ1c2lvbi4NCj4gU29ycnkgZm9yDQo+ID4+
Pj4gdGhhdC4NCj4gPj4+PiBJbiB0aGUgc2Vjb25kIG1vdGl2YXRpb24sIHdlIGRpZG7CocKvdCB0
cnkgdG8gYXJndWUgdGhlcmUgaXMgYSBzY2VuYXJpbw0KPiB3aGVyZQ0KPiA+Pj4+IHRpbWluZyBw
YWNrZXRzIG11c3QgYmUgZW5jcnlwdGVkLg0KPiA+Pj4+IEluIGNvbnRyYXN0LCB3ZSB0cnkgdG8g
ZGlzY3VzcyB0aGUgY29uZGl0aW9ucyB3aGVyZSB0aW1pbmcgcGFja2V0cyBhcmUNCj4gPj4+PiB0
cmFuc3BvcnRlZCBpbiBhbiBpbnNlY3VyZSBuZXR3b3JrIGFuZCB0aGVyZSBhcmUgYWxyZWFkeSBJ
UHNlYyBFU1ANCj4gdHVubmVsDQo+ID4+Pj4gcHJvdmlkZWQuDQo+ID4+Pj4gV2hlbiB3ZSB0cnkg
dG8gdHJhbnNwb3J0IHRoZSB0aW1pbmcgcGFja2V0cyBpbiBhIHNlY3VyZSB3YXksIHdlIGNhbg0K
PiByZXVzZQ0KPiA+Pj4+IHRoZSBleGlzdGluZyBJUHNlYyBFU1AgdHVubmVsIGV2ZW4gdGhvdWdo
IHRoZSB0aW1pbmcgcGFja2V0cyBtYXkgbm90DQo+IGJlDQo+ID4+Pj4gY29uZmlkZW50aWFsIGl0
c2VsZiAoQnV0IGludGVncml0eSBwcm90ZWN0aW9uIGlzIG5lY2Vzc2FyeSwgYW55d2F5KS4NCj4g
Pj4+Pg0KPiA+Pj4+IEJlc3QgcmVnYXJkcywNCj4gPj4+PiBZYW5nDQo+ID4+Pj4gPT09PT09PT09
PT09PT09PT09DQo+ID4+Pj4gWWFuZyBDdWksICBQaC5ELg0KPiA+Pj4+IEh1YXdlaSBUZWNobm9s
b2dpZXMNCj4gPj4+PiBjdWl5YW5nQGh1YXdlaS5jb20NCj4gPj4+Pg0KPiA+Pj4+PiAtLS0tLcOT
w4rCvMO+w5TCrcK8w74tLS0tLQ0KPiA+Pj4+PiDCt8KiwrzDvsOIw4s6IFlhYWtvdiBTdGVpbiBb
bWFpbHRvOnlhYWtvdl9zQHJhZC5jb21dDQo+ID4+Pj4+IMK3wqLDi8ONw4rCscK8w6Q6IDIwMTLD
hMOqM8OUw4IxM8OIw5UgMDo0Nw0KPiA+Pj4+PiDDisOVwrzDvsOIw4s6IEN1aSBZYW5nOyBEYW5u
eSBNYXllcg0KPiA+Pj4+PiDCs8Ktw4vDjTogdGljdG9jQGlldGYub3JnDQo+ID4+Pj4+IMOWw7fD
jMOiOiBSRTogW1RJQ1RPQ10gUGxlYXNlIENvbW1lbnQgb24gUHJhY3RpY2FsIFNvbHV0aW9ucyBm
b3INCj4gRW5jcnlwdGVkDQo+ID4+Pj4+IFN5bmNocm9uaXphdGlvbiBQcm90b2NvbA0KPiA+Pj4+
Pg0KPiA+Pj4+PiBZYW5nDQo+ID4+Pj4+DQo+ID4+Pj4+IEkgZnVsbHkgdW5kZXJzdGFuZCB5b3Vy
IG1vdGl2YXRpb24gKGFjdHVhbGx5IHRoZSAybmQgbW90aXZhdGlvbiBpbg0KPiB5b3VyDQo+ID4+
Pj4gZHJhZnQpDQo+ID4+Pj4+IHRvIGhhbmRsZSBjYXNlcyB3aGVyZSBlbmNyeXB0aW9uIG9mIEFM
TCBwYWNrZXRzIGlzIG1hbmRhdG9yeSwNCj4gaW5jbHVkaW5nDQo+ID4+Pj4+IHRpbWluZyBvbmVz
Lg0KPiA+Pj4+Pg0KPiA+Pj4+PiBIb3dldmVyLCBJIGFtIG5vdCBzdXJlIHRoYXQgVFMgMzMuMzIw
IHJlYWxseSBtYW5kYXRlcyBlbmNyeXB0aW9uIG9mDQo+ID4+PiB0aW1pbmcNCj4gPj4+Pj4gcGFj
a2V0cy4NCj4gPj4+Pj4NCj4gPj4+Pj4gRmlyc3QsIDMzLjMyMCBjbGVhcmx5IHN0YXRlcyB0aGF0
IHdoaWxlIGltcGxlbWVudGF0aW9uIG9mIElQc2VjIGlzDQo+ID4+PiBtYW5kYXRvcnksDQo+ID4+
Pj4+IHVzYWdlIGlzIG9wdGlvbmFsIGFuZCBiYXNlZCBvbiBvcGVyYXRvciBwb2xpY3kNCj4gPj4+
Pj4gKHdpdGggdGhlIHBvc3NpYmxlIGV4Y2VwdGlvbiBvZiBkaXJlY3QgbGlua3MgYmV0d2VlbiBI
KGUpTkJzLCBidXQNCj4gdGhlc2UNCj4gPj4+PiBsaW5rcw0KPiA+Pj4+PiBhcmUgb3B0aW9uYWwg
dG9vKS4NCj4gPj4+Pj4gSWYgSVBzZWMgaXMgbm90IHVzZWQsIHRoZW4gYSBsb3dlciBsYXllciBt
ZWNoYW5pc20gY2FuIGJlIHVzZWQNCj4gPj4+Pj4gKHcvbyBhbnkgc3BlY2lmaWNhdGlvbiBvZiB3
aGF0IGV4YWN0bHkgdGhpcyBsb3dlciBsYXllciBtZWNoYW5pc20NCj4gbmVlZHMNCj4gPj4+IHRv
DQo+ID4+Pj4+IGRvKSwNCj4gPj4+Pj4gYSBtZXRob2QgYXNzdW1lZGx5IHJ1bm5pbmcgaW4gSFcg
YW5kIGFkZGluZyBhbG1vc3Qgbm8gZGVsYXkgYW5kDQo+ID4+Pj4+IGFic29sdXRlbHkgbm8gZGVs
YXkgdmFyaWF0aW9uLg0KPiA+Pj4+Pg0KPiA+Pj4+PiBTZWNvbmQsIGV2ZW4gaWYgdGhlIG9wZXJh
dG9yIGRlY2lkZXMgdG8gdXNlIElQc2VjLCB0aGVuIHRoZSBzdGFuZGFyZA0KPiA+Pj4gc3RhdGVz
DQo+ID4+Pj4+ICJBbGwgc2lnbmFsbGluZywgdXNlciwgYW5kIG1hbmFnZW1lbnQgcGxhbmUgdHJh
ZmZpYyBvdmVyIHRoZSBpbnRlcmZhY2UNCj4gPj4+Pj4gYmV0d2VlbiBIKGUpTkIgYW5kIFNlR1cg
c2hhbGwgYmUgc2VudCB0aHJvdWdoIGFuIElQc2VjIEVTUCB0dW5uZWwiLg0KPiA+Pj4+PiBJIHRo
aW5rIHdlIGNhbiBtYWtlIHRoZSBjYXNlIHRoYXQgdGltaW5nIGlzIG5laXRoZXIgc2lnbmFsaW5n
LCBub3IgdXNlciwNCj4gbm9yDQo+ID4+Pj4+IG1hbmFnZW1lbnQgdHJhZmZpYywNCj4gPj4+Pj4g
YW5kIHRodXMgZXhlbXB0IGZyb20gdGhlIElQc2VjIHJlcXVpcmVtZW50Lg0KPiA+Pj4+PiBQZXJo
YXBzIHdlIHNob3VsZCBzZW5kIDNHUFAgYSBsaWFpc29uIHRvIHRoYXQgZWZmZWN0LCBhbmQgZ2V0
IGFuDQo+IGV4cGxpY2l0DQo+ID4+Pj4+IHdhaXZlci4NCj4gPj4+Pj4NCj4gPj4+Pj4gU28sIHdl
IGFyZSBsZWZ0IHdpdGggbm8gdXNlIGNhc2UgbWFuZGF0aW5nIGVuY3J5cHRpbmcgb2YgdGltaW5n
DQo+IHBhY2tldHMsDQo+ID4+Pj4+IGFuZCB0aGUgcHJvYmxlbSBnb2VzIGF3YXkuDQo+ID4+Pj4+
DQo+ID4+Pj4+IFkoSilTDQo+ID4+Pj4+DQo+ID4+Pj4+DQo+ID4+Pj4+IC0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQo+ID4+Pj4+IEZyb206IHRpY3RvYy1ib3VuY2VzQGlldGYub3JnIFttYWls
dG86dGljdG9jLWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+ID4+PiBCZWhhbGYNCj4gPj4+PiBPZg0K
PiA+Pj4+PiBDdWkgWWFuZw0KPiA+Pj4+PiBTZW50OiBUaHVyc2RheSwgTWFyY2ggMDgsIDIwMTIg
MDM6NDQNCj4gPj4+Pj4gVG86IERhbm55IE1heWVyDQo+ID4+Pj4+IENjOiB0aWN0b2NAaWV0Zi5v
cmcNCj4gPj4+Pj4gU3ViamVjdDogUmU6IFtUSUNUT0NdIFBsZWFzZSBDb21tZW50IG9uIFByYWN0
aWNhbCBTb2x1dGlvbnMgZm9yDQo+ID4+PiBFbmNyeXB0ZWQNCj4gPj4+Pj4gU3luY2hyb25pemF0
aW9uIFByb3RvY29sDQo+ID4+Pj4+DQo+ID4+Pj4+IERhbm55LA0KPiA+Pj4+Pg0KPiA+Pj4+PiBU
aGFua3MgZm9yIHlvdXIgY29tbWVudHMuIEkgd2lsbCByZXNwb25kIGlubGluZS4NCj4gPj4+Pj4N
Cj4gPj4+Pj4+IC0tLS0tw5PDisK8w77DlMKtwrzDvi0tLS0tDQo+ID4+Pj4+PiDCt8KiwrzDvsOI
w4s6IERhbm55IE1heWVyIFttYWlsdG86bWF5ZXJAbnRwLm9yZ10NCj4gPj4+Pj4+IMK3wqLDi8ON
w4rCscK8w6Q6IDIwMTLDhMOqM8OUw4I3w4jDlSAyMDo1Ng0KPiA+Pj4+Pj4gw4rDlcK8w77DiMOL
OiBDdWkgWWFuZw0KPiA+Pj4+Pj4gwrPCrcOLw406IHRpY3RvY0BpZXRmLm9yZw0KPiA+Pj4+Pj4g
w5bDt8OMw6I6IFJlOiBbVElDVE9DXSBQbGVhc2UgQ29tbWVudCBvbiBQcmFjdGljYWwgU29sdXRp
b25zIGZvcg0KPiA+Pj4gRW5jcnlwdGVkDQo+ID4+Pj4+PiBTeW5jaHJvbml6YXRpb24gUHJvdG9j
b2wNCj4gPj4+Pj4+DQo+ID4+Pj4+PiBJIGhhdmUgYWxyZWFkeSBzYWlkIHRoaXMgYmVmb3JlIGFu
ZCBJIHdpbGwgcmVwZWF0IHRoaXMgZm9yIHRoZSBwdXJwb3Nlcw0KPiA+Pj4+Pj4gb2YgZmVlZGJh
Y2suDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVGltZSBwYWNrZXRzIGRvIG5vdCBuZWVkIHRvIGJlIGVu
Y3J5cHRlZCBhcyBub3Qgb25seSBkbyB0aGV5IG5vdA0KPiA+Pj4+IGNvbnRhaW4NCj4gPj4+Pj4+
IGFueXRoaW5nIHNlY3JldCwgZXZlbiBpZiB5b3Uga25ldyB0aGUgY29udGVudHMgdGhleSBhcmUg
dXNlbGVzcw0KPiA+Pj4gYW55dGltZQ0KPiA+Pj4+Pj4gYWZ0ZXIgdGhlIHBhY2tldCBoYXMgYmVl
biBkZWxpdmVyZWQuDQo+ID4+Pj4+DQo+ID4+Pj4+IFtDdWkgWWFuZ10gSSB3aWxsIHJlcGVhdCBv
dXIgbW90aXZhdGlvbi4NCj4gPj4+Pj4gQWNjb3JkaW5nIHRvIGdsb2JhbGx5IHVzZWQgM0dQUCBz
dGFuZGFyZCwgdGhlcmUgaXMgYSBuZWVkIGZvcg0KPiBlc3RhYmxpc2gNCj4gPj4+PiBJUHNlYw0K
PiA+Pj4+PiBFU1AgdHVubmVsIGZvciBzbWFsbCBob21lIGJhc2Ugc3RhdGlvbiBjb25uZWN0aW5n
IHRvIFNlY3VyaXR5IEdXIG9yDQo+ID4+PiBvdGhlcg0KPiA+Pj4+PiBjb3JlIG5ldHdvcmsgZGV2
aWNlcy4NCj4gPj4+Pj4gVGhlcmUgaGF2ZSBleGlzdGVkIHN1Y2ggYSBncmVhdCBudW1iZXIgb2Yg
SVBzZWMgRVNQIHR1bm5lbHMgaW4gdGhlDQo+ID4+Pj4+IHVuZGVybHlpbmcgdXNlIGNhc2UuDQo+
ID4+Pj4+IEZvciBtZWV0aW5nIHRoZSBsZWFzdCBzZWN1cml0eSByZXF1aXJlbWVudCwgaXQgaXMg
bmVlZGVkIHRvIHNldCB1cA0KPiBJUHNlYw0KPiA+Pj4gQUgNCj4gPj4+PiBvcg0KPiA+Pj4+PiBJ
UHNlYyBFU1AtTlVMTCBmb3IgdGhlIGludGVncml0eSBwcm90ZWN0aW9uLg0KPiA+Pj4+PiBUaGVu
IGl0IHdpbGwgaW5jcmVhc2UgdGhlIHNlY3VyaXR5IGNvc3QuDQo+ID4+Pj4+DQo+ID4+Pj4+IElm
IHRoZXJlIGlzIGEgc2ltcGxlIGFuZCBwcmFjdGljYWwgc29sdXRpb24gZm9yIHRoaXMgcHJvYmxl
bSwgdGhlbiB3aHkNCj4gbm90DQo+ID4+PiBsZXQNCj4gPj4+PiBpdA0KPiA+Pj4+PiBiZSBjbGFy
aWZpZWQ/DQo+ID4+Pj4+IFNvIHRoYXQsIG1hbnkgZW5naW5lZXJzIGFuZCBjdXN0b21lcnMgY2Fu
IGJlbmVmaXQgZnJvbSBzaW5nbGUgSVBzZWMNCj4gPj4+PiB0dW5uZWwNCj4gPj4+Pj4gcHJvdGVj
dGlvbiBlYWNoIHVzZXIsIHdoaWNoIHNhdmVzIHRoZSBjb3N0IGZvciBib3RoLg0KPiA+Pj4+Pg0K
PiA+Pj4+Pj4gWW91IGRvIHlvdXJzZWxmIGEgZGlzZmF2b3IgaW4gZW5jcnlwdGluZyBzb21ldGhp
bmcgdGhhdCBpcyBub3Qgd29ydGgNCj4gPj4+Pj4+IGVuY3J5cHRpbmcuIEl0IHRha2VzIHByb2Nl
c3Npbmcgb3ZlcmhlYWQsIGluY3JlYXNlcyBwYWNrZXQgc2l6ZSwgYW5kDQo+ID4+Pj4+PiB0aGVy
ZSBpcyBubyBnYWluIGluIGRvaW5nIHNvLiBZb3UgbmVlZCB0byBqdXN0aWZ5IGVuY3J5cHRpbmcg
c29tZXRoaW5nDQo+ID4+Pj4+DQo+ID4+Pj4+IFtDdWkgWWFuZ10gSSBhbSBub3QgZG9pbmcgbXlz
ZWxmIGEgZGlzZmF2b3IsIGJ1dCBnb2luZyB0byBwcm92aWRlIGENCj4gc29sdXRpb24NCj4gPj4+
PiBmb3INCj4gPj4+Pj4gdGhlIHByYWN0aWNhbCBhbmQgdGVjaG5pY2FsIHByb2JsZW0uDQo+ID4+
Pj4+IEludGVncml0eSBwcm90ZWN0aW9uIHRha2VzIG92ZXJoZWFkLCBhcyB3ZWxsLg0KPiA+Pj4+
PiBJbiBjYXNlIGNvbmZpZGVudGlhbGl0eSBpcyBtYW5kYXRvcnksIGlzIGl0IGEgZ29vZCBpZGVh
IHRvIHByb3RlY3QNCj4gaW50ZWdyaXR5DQo+ID4+Pj4+IHNlcGFyYXRlbHk/DQo+ID4+Pj4+IFdo
YXQgd2UgbmVlZCB0byBkbywgaXMgdG8gaW52ZXN0aWdhdGUgYW5kIHJlZHVjZSB0aGUgY29zdCBh
cyBzbWFsbCBhcw0KPiA+Pj4+IHBvc3NpYmxlDQo+ID4+Pj4+IGZpcnN0LCBhbmQgc2VlIHdoZXRo
ZXIgaXQgaXMgYWNjZXB0YWJsZSBvciBub3QuDQo+ID4+Pj4+IFRoYXQgaXMgb3VyIG1vdGl2YXRp
b24gb2YgdGhlIG5ldyBkcmFmdC4NCj4gPj4+Pj4NCj4gPj4+Pj4+IGFuZCBwbGVhc2UgZG9uJ3Qg
c2F5IHRoYXQgaXQgaXMgYmVjYXVzZSBzb21lIG90aGVyIGRvY3VtZW50IHNheXMgdG8NCj4gPj4+
Pj4+IGVuY3J5cHQgZXZlcnl0aGluZy4gSSB3YW50IHRvIGtub3cgd2hhdCBpcyB0aGUgYmVuZWZp
dCBmcm9tIGRvaW5nDQo+IHNvLA0KPiA+Pj4+Pg0KPiA+Pj4+PiBbQ3VpIFlhbmddIEkganVzdCBh
bnN3ZXJlZCB5b3VyIHByZXZpb3VzIGVtYWlsIHByb3ZpZGluZyB0aGUgcmVmZXJyZWQNCj4gPj4+
PiBzZWN0aW9uDQo+ID4+Pj4+IGFuZCBkb2N1bWVudCBhcyB5b3UgcmVxdWlyZWQsIHllc3RlcmRh
eS4NCj4gPj4+Pj4NCj4gPj4+Pj4+IHdoYXQgYXJlIHRoZSByaXNrcyBpbiBub3QgZG9pbmcgc28g
YW5kIHdoYXQgaXMgdGhlIGNvc3Qgb2YgZG9pbmcgc28sDQo+ID4+Pj4+PiBwYXJ0aWN1bGFybHkg
aW4gbG9zcyBvZiBhY2N1cmFjeSwgaW5jcmVhc2VkIGVycm9yIGJ1ZGdldCwgZXRjLg0KPiA+Pj4+
Pg0KPiA+Pj4+PiBbQ3VpIFlhbmddIFRoYXQgaXMgb3VyIG5ldyBkcmFmdCB0cnlpbmcgdG8gZXhw
bGFpbiwgcGxlYXNlIGNoZWNrIGl0DQo+IGJlZm9yZQ0KPiA+Pj4+PiBwb3N0aW5nIHlvdXIgb3Bp
bmlvbi4NCj4gPj4+Pj4NCj4gPj4+Pj4+IFRoZSB3aG9sZSB0aGluZyBpcyBhIGJhZCBpZGVhIGZy
b20gd2hhdCBJIGNhbiB0ZWxsLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IERhbm55DQo+ID4+Pj4+Pg0K
PiA+Pj4+Pg0KPiA+Pj4+PiBUaGFua3MsDQo+ID4+Pj4+IFlhbmcNCj4gPj4+Pj4NCj4gPj4+Pj4N
Cj4gPj4+Pj4+IE9uIDMvNi8yMDEyIDEwOjM1IFBNLCBDdWkgWWFuZyB3cm90ZToNCj4gPj4+Pj4+
PiBIaSwgYWxsLA0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IEkg
aGF2ZSBwb3N0ZWQgYSBuZXcgZHJhZnQgdGhhdCBkaXNjdXNzZXMgdGhlIHByYWN0aWNhbCBzb2x1
dGlvbnMgZm9yDQo+ID4+Pj4+Pj4gZW5jcnlwdGVkIHN5bmNocm9uaXphdGlvbiBwcm90b2NvbHMu
DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gU2luY2Ugd2UgaGF2
ZSBkaXNjdXNzZWQgYSBsb3Qgb24gdGhpcyBwcm9ibGVtLCBhbmQgdGhlIHNlY3VyaXR5DQo+ID4+
Pj4+Pj4gcmVxdWlyZW1lbnQgb2Ygc3luY2hyb25pemF0aW9uIGFsc28gbm90ZWQgdGhhdCBjb25m
aWRlbnRpYWxpdHkgbWF5DQo+ID4+Pj4gbmVlZA0KPiA+Pj4+Pj4+IHByb3RlY3Rpb24sIGVzcGVj
aWFsbHkgaW4gY2FzZSB0aGF0IHRoZSBjb25maWRlbnRpYWxpdHkgcHJvdGVjdGlvbiBpcw0KPiA+
Pj4+Pj4+IG1hbmRhdG9yeS4gU3luY2hyb25pemF0aW9uIHNob3VsZCBiZSBhdmFpbGFibGUgd2hl
biB0aGUgdHJhZmZpYyBpcw0KPiA+Pj4+Pj4+IGVuY3J5cHRlZC4gVGhlIGluZmx1ZW5jZXMgYnkg
dGhlIGVuY3J5cHRpb24gYXJlIGV4cGxhaW5lZCwgYW5kDQo+ID4+PiBzZXZlcmFsDQo+ID4+Pj4+
Pj4gcG9zc2libGUgc29sdXRpb25zIGhhdmUgYmVlbiBkaXNjdXNzZWQuDQo+ID4+Pj4+Pj4NCj4g
Pj4+Pj4+PiBUaGUgVVJMIGlzIGJlbG93LCBwbGVhc2UgcmV2aWV3IGFuZCBjb21tZW50Lg0KPiA+
Pj4+Pj4+DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+ICAgIFRpdGxlICAgICAgOiBQ
cmFjdGljYWwgc29sdXRpb25zIGZvciBlbmNyeXB0ZWQgc3luY2hyb25pemF0aW9uDQo+ID4+Pj4+
IHByb3RvY29sDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiBBdXRob3IocykgIDogWS4gQ3VpLA0KPiA+
Pj4+Pj4+DQo+ID4+Pj4+Pj4gTS4gQmhhdGlhLA0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gRC4gWmhh
bmcNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IEZpbGVuYW1lICAgOiBkcmFmdC1jdWktdGljdG9jLWVu
Y3J5cHRlZC1zeW5jaHJvbml6YXRpb24tMDAudHh0DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiBQYWdl
cyAgICAgOiAxMA0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gRGF0ZSAgICAgIDogTWFyLiAxLCAyMDEy
DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiAgIFRoaXMgaW5mb3JtYXRpb25hbCBkb2N1bWVudCBhbmFs
eXplcyB0aGUgYWNjdXJhY3kgaXNzdWVzIHdpdGgNCj4gPj4+IHRpbWUNCj4gPj4+Pj4+Pg0KPiA+
Pj4+Pj4+ICAgc3luY2hyb25pemF0aW9uIHByb3RvY29scyB3aGVuIHRpbWUgc3luY2hyb25pemF0
aW9uIHBhY2tldHMNCj4gYXJlDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiAgIGVuY3J5cHRlZCBkdXJp
bmcgdHJhbnNtaXNzaW9uLiBJbiBhZGRpdGlvbiwgc2V2ZXJhbCBjYW5kaWRhdGUNCj4gPj4+Pj4+
Pg0KPiA+Pj4+Pj4+ICBzb2x1dGlvbnMgb24gc3VjaCBpc3N1ZXMgYXJlIGludHJvZHVjZWQuDQo+
ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gQSBVUkwgZm9yIHRoaXMg
SW50ZXJuZXQtRHJhZnQgaXM6DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4N
Cj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1jdWktdGljdG9jLWVuY3J5
cHRlZC1zeW5jaHJvbml6YXRpb24NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4NCj4g
Pj4+Pj4+PiBUaGFua3MsDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiBZYW5nDQo+ID4+Pj4+Pj4NCj4g
Pj4+Pj4+PiA9PT09PT09PT09PT09PT09PT0NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IFlhbmcgQ3Vp
LCAgUGguRC4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IEh1YXdlaSBUZWNobm9sb2dpZXMNCj4gPj4+
Pj4+Pg0KPiA+Pj4+Pj4+IGN1aXlhbmdAaHVhd2VpLmNvbQ0KPiA+Pj4+PiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+PiBUSUNUT0MgbWFpbGlu
ZyBsaXN0DQo+ID4+Pj4+IFRJQ1RPQ0BpZXRmLm9yZw0KPiA+Pj4+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RpY3RvYw0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBUSUNUT0MgbWFpbGluZyBsaXN0DQo+
ID4gVElDVE9DQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby90aWN0b2MNCj4gPg0KPiA+IFNjYW5uZWQgYnkgQ2hlY2sgUG9pbnQgVG90YWwgU2VjdXJp
dHkgR2F0ZXdheS4NCg0K

From brian.utterback@oracle.com  Wed Aug 29 23:23:34 2012
Return-Path: <brian.utterback@oracle.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 761DB11E80D3 for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 23:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.26
X-Spam-Level: 
X-Spam-Status: No, score=-10.26 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXJm-Ij313+H for <tictoc@ietfa.amsl.com>; Wed, 29 Aug 2012 23:23:32 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id 72C0811E80BA for <tictoc@ietf.org>; Wed, 29 Aug 2012 23:23:32 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q7U6NPlp004423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Aug 2012 06:23:26 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q7U6NOjg006998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Aug 2012 06:23:24 GMT
Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q7U6NNnt025831; Thu, 30 Aug 2012 01:23:23 -0500
Received: from [10.195.0.201] (/10.195.0.201) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 29 Aug 2012 23:23:23 -0700
Message-ID: <503F06DA.3040204@oracle.com>
Date: Thu, 30 Aug 2012 02:23:22 -0400
From: Brian Utterback <brian.utterback@oracle.com>
Organization: Oracle
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:6.0) Gecko/20110814 Thunderbird/6.0
MIME-Version: 1.0
To: Danny Mayer <mayer@ntp.org>
References: <8CC0CB0BCAE52F46882E17828A9AE2161A032B90@SZXEML508-MBS.china.huawei.com> <4F575AF0.2060600@ntp.org> <8CC0CB0BCAE52F46882E17828A9AE2161A032D59@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC9043207DE@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A173D46@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904322E18@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A1756E8@SZXEML508-MBS.china.huawei.com> <07F7D7DED63154409F13298786A2ADC904324409@EXRAD5.ad.rad.co.il> <8CC0CB0BCAE52F46882E17828A9AE2161A181BFC@SZXEML508-MBS.china.huawei.com> <503E8CF4.7030602@ntp.org>
In-Reply-To: <503E8CF4.7030602@ntp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] Please Comment on Practical Solutions for Encrypted Synchronization Protocol
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, 30 Aug 2012 06:23:34 -0000

One can easily imagine a two step boot process, one where the time is 
roughly determined using Autokey, and then the IPsec tunnel is set up, 
and then further timing packets sent over the tunnel. I don't know the 
precision of the timestamps,  in IPsec certificates, but I doubt that it 
is more than to the second, and more likely it is to the minute. If all 
you care about is the validity of the certs, then it shouldn't take a 
long time to get the time accurate to this level. If it were not for the 
possibility of reverse engineering the femto station, the original auth 
key scheme would work even better. But since the femto stations are 
distributed to untrusted users (I use one for instance, and who would 
trust me?) that wouldn't work.

On 08/29/12 17:43, Danny Mayer wrote:
> I know that this is a rather old email message but when I was reviewing
> it, it occurred to me that if IPSec requires accurate clocks to set
> itself up then this won't work and you need, at least initially, to do
> without IPSec.
>
> Danny
> On 3/19/2012 12:14 AM, Cui Yang wrote:
>> Hi, Yaakov,
>>
>> I said the IPsec tunnel “functionality” is mandatory to achieve, which means the device MUST support IPsec ESP tunnel (confidentiality and integrity).
>>
>> More specifically, TS 33.320 does explicitly describe security requirement for time synchronization, where
>> -Sec.6.3.1, Clock Synchronization Security Mechanisms for H(e)NB
>> -“The H(e)NB requires time synchronization with a time server. The H(e)NB SHALL support receiving time synchronisation messages over the secure backhaul link between H(e)NB and the SeGW”
>> - “Optionally other secure clock servers may be used, which do not use the secure backhaul link. In this case the communication between these clock server(s) and H(e)NB SHALL be secured.”
>>
>>  From the above, my interpretation is,
>> -synchronization MUST be adequately protected
>> -synchronization mechanism MUST be supported by IPsec ESP tunnel mode (for devices)
>> -In the case that IPsec is not chosen to use (though the devices do support), separate secured clock mechanism MUST be used.
>>
>> Therefore, if IPsec tunnel is deployed, then synchronization protocol must support it;
>> otherwise different security mechanism is deployed, and a separate secure protection (more than IPsec AH) for synchronization must be provided.
>>  From a vendor’s point of view, it is required to investigate this problem and compare the performances of different approaches.
>>
>> Finally, answering your question, Autokey is designed “based on the premise that IPsec schemes cannot be adopted intact, since that would preclude stateless servers and severely compromise timekeeping accuracy”[RFC5906].
>> But, what if the IPsec tunnel is available already? Is there any evaluation on this “severely” compromising accuracy? I wonder whether there is any benefit to setting up separate security mechanism, if the device already has end-to-end IPsec tunnel connection.
>> And I believe that our investigation and analysis on this practical problem is necessary and meaningful, which still could be greatly improved via the discussion with you all.
>>
>> Thanks,
>> Yang
>> ==================
>>   Yang Cui,  Ph.D.
>>   Huawei Technologies
>>   cuiyang@huawei.com
>>
>>> -----邮件原件-----
>>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>>> 发送时间: 2012年3月18日 22:22
>>> 收件人: Cui Yang
>>> 抄送: tictoc@ietf.org; Danny Mayer
>>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>> Synchronization Protocol
>>>
>>> Yang
>>>
>>> What do you mean by "mandatory to achieve".
>>>
>>> What 33.320 says is that IPsec is mandatory to implement in HW,
>>> but optional to use.
>>> Furthermore, my interpretation is that timing packets are explicitly not
>>> covered,
>>> since they mention which types of packets should be protected,
>>> and none of the types mentioned describe timing packets.
>>>
>>> I have a question for you.
>>> Were we to use NTP with Autokey and thus provide strong proventication,
>>> would you see any benefit to using IPsec ?
>>> Do you agree that there is a drawback to its use ?
>>>
>>> Y(J)S
>>>
>>> -----Original Message-----
>>> From: Cui Yang [mailto:cuiyang@huawei.com]
>>> Sent: Thursday, March 15, 2012 05:30
>>> To: Yaakov Stein
>>> Cc: tictoc@ietf.org; Danny Mayer
>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>> Synchronization Protocol
>>>
>>> Hi, Yaakov,
>>>
>>> Thanks for your comments. Please find my answer in the following.
>>>
>>> The IPsec tunnel functionality in backhaul link between femto and SeGW are
>>> mandatory to achieve by 3GPP Technical Specification TS.33.320
>>> http://www.3gpp.org/ftp/specs/html-info/33320.htm
>>> -4.3.1 Backhaul link
>>> -4.4.5 Requirements on Backhaul Link
>>> -7.4 IPsec Tunnel Establishment
>>> -etc.
>>>
>>> This requirement is originated from the typical use case of home based
>>> wireless base station (Femto), where the backhaul cable connection is
>>> commonly leased by telecom operator and through insecure networks, not
>>> belonging to operator’s own network. Since the regulation and laws on
>>> information security and privacy are strict in many countries, vendors are
>>> requested to set up this IPsec tunnel functionality to avoid the risk of
>>> information or privacy leakage. The contents encrypted in IPsec tunnel
>>> include not only data plane, but also control plane, where the former carries
>>> the customer’s data and voice, and the latter carries sensitive information,
>>> such as the secret keys for air interface encryption. For most of operators
>>> and vendors, it is considered necessary and responsible to protect customers’
>>> privacy and communication security, where the best way known is IPsec
>>> tunnel.
>>>
>>> Best regards,
>>> Yang
>>> ==================
>>>   Yang Cui,  Ph.D.
>>>   Huawei Technologies
>>>   cuiyang@huawei.com
>>>
>>>> -----邮件原件-----
>>>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>>>> 发送时间: 2012年3月15日 2:36
>>>> 收件人: Cui Yang
>>>> 抄送: tictoc@ietf.org; Danny Mayer
>>>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>>> Synchronization Protocol
>>>>
>>>> Yang
>>>>
>>>> Yes, I fully appreciate the scenario you are discussing,
>>>> where ALL packets MUST be encrypted.
>>>>
>>>> I am just questioning whether such a scenario is really mandated by any
>>>> standard (I believe it is not),
>>>> in which case one can simply NOT encrypt the timing packets (even if you
>>>> choose to encrypt the other packets).
>>>>
>>>> Y(J)S
>>>>
>>>> -----Original Message-----
>>>> From: Cui Yang [mailto:cuiyang@huawei.com]
>>>> Sent: Tuesday, March 13, 2012 04:51
>>>> To: Yaakov Stein; Danny Mayer
>>>> Cc: tictoc@ietf.org
>>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>>> Synchronization Protocol
>>>>
>>>> Hi, Yaakov,
>>>>
>>>> Maybe my unclear description in the draft causes some confusion. Sorry for
>>>> that.
>>>> In the second motivation, we didn’t try to argue there is a scenario where
>>>> timing packets must be encrypted.
>>>> In contrast, we try to discuss the conditions where timing packets are
>>>> transported in an insecure network and there are already IPsec ESP tunnel
>>>> provided.
>>>> When we try to transport the timing packets in a secure way, we can reuse
>>>> the existing IPsec ESP tunnel even though the timing packets may not be
>>>> confidential itself (But integrity protection is necessary, anyway).
>>>>
>>>> Best regards,
>>>> Yang
>>>> ==================
>>>>   Yang Cui,  Ph.D.
>>>>   Huawei Technologies
>>>>   cuiyang@huawei.com
>>>>
>>>>> -----邮件原件-----
>>>>> 发件人: Yaakov Stein [mailto:yaakov_s@rad.com]
>>>>> 发送时间: 2012年3月13日 0:47
>>>>> 收件人: Cui Yang; Danny Mayer
>>>>> 抄送: tictoc@ietf.org
>>>>> 主题: RE: [TICTOC] Please Comment on Practical Solutions for Encrypted
>>>>> Synchronization Protocol
>>>>>
>>>>> Yang
>>>>>
>>>>> I fully understand your motivation (actually the 2nd motivation in your
>>>> draft)
>>>>> to handle cases where encryption of ALL packets is mandatory, including
>>>>> timing ones.
>>>>>
>>>>> However, I am not sure that TS 33.320 really mandates encryption of
>>> timing
>>>>> packets.
>>>>>
>>>>> First, 33.320 clearly states that while implementation of IPsec is
>>> mandatory,
>>>>> usage is optional and based on operator policy
>>>>> (with the possible exception of direct links between H(e)NBs, but these
>>>> links
>>>>> are optional too).
>>>>> If IPsec is not used, then a lower layer mechanism can be used
>>>>> (w/o any specification of what exactly this lower layer mechanism needs
>>> to
>>>>> do),
>>>>> a method assumedly running in HW and adding almost no delay and
>>>>> absolutely no delay variation.
>>>>>
>>>>> Second, even if the operator decides to use IPsec, then the standard
>>> states
>>>>> "All signalling, user, and management plane traffic over the interface
>>>>> between H(e)NB and SeGW shall be sent through an IPsec ESP tunnel".
>>>>> I think we can make the case that timing is neither signaling, nor user, nor
>>>>> management traffic,
>>>>> and thus exempt from the IPsec requirement.
>>>>> Perhaps we should send 3GPP a liaison to that effect, and get an explicit
>>>>> waiver.
>>>>>
>>>>> So, we are left with no use case mandating encrypting of timing packets,
>>>>> and the problem goes away.
>>>>>
>>>>> Y(J)S
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On
>>> Behalf
>>>> Of
>>>>> Cui Yang
>>>>> Sent: Thursday, March 08, 2012 03:44
>>>>> To: Danny Mayer
>>>>> Cc: tictoc@ietf.org
>>>>> Subject: Re: [TICTOC] Please Comment on Practical Solutions for
>>> Encrypted
>>>>> Synchronization Protocol
>>>>>
>>>>> Danny,
>>>>>
>>>>> Thanks for your comments. I will respond inline.
>>>>>
>>>>>> -----邮件原件-----
>>>>>> 发件人: Danny Mayer [mailto:mayer@ntp.org]
>>>>>> 发送时间: 2012年3月7日 20:56
>>>>>> 收件人: Cui Yang
>>>>>> 抄送: tictoc@ietf.org
>>>>>> 主题: Re: [TICTOC] Please Comment on Practical Solutions for
>>> Encrypted
>>>>>> Synchronization Protocol
>>>>>>
>>>>>> I have already said this before and I will repeat this for the purposes
>>>>>> of feedback.
>>>>>>
>>>>>> Time packets do not need to be encrypted as not only do they not
>>>> contain
>>>>>> anything secret, even if you knew the contents they are useless
>>> anytime
>>>>>> after the packet has been delivered.
>>>>> [Cui Yang] I will repeat our motivation.
>>>>> According to globally used 3GPP standard, there is a need for establish
>>>> IPsec
>>>>> ESP tunnel for small home base station connecting to Security GW or
>>> other
>>>>> core network devices.
>>>>> There have existed such a great number of IPsec ESP tunnels in the
>>>>> underlying use case.
>>>>> For meeting the least security requirement, it is needed to set up IPsec
>>> AH
>>>> or
>>>>> IPsec ESP-NULL for the integrity protection.
>>>>> Then it will increase the security cost.
>>>>>
>>>>> If there is a simple and practical solution for this problem, then why not
>>> let
>>>> it
>>>>> be clarified?
>>>>> So that, many engineers and customers can benefit from single IPsec
>>>> tunnel
>>>>> protection each user, which saves the cost for both.
>>>>>
>>>>>> You do yourself a disfavor in encrypting something that is not worth
>>>>>> encrypting. It takes processing overhead, increases packet size, and
>>>>>> there is no gain in doing so. You need to justify encrypting something
>>>>> [Cui Yang] I am not doing myself a disfavor, but going to provide a solution
>>>> for
>>>>> the practical and technical problem.
>>>>> Integrity protection takes overhead, as well.
>>>>> In case confidentiality is mandatory, is it a good idea to protect integrity
>>>>> separately?
>>>>> What we need to do, is to investigate and reduce the cost as small as
>>>> possible
>>>>> first, and see whether it is acceptable or not.
>>>>> That is our motivation of the new draft.
>>>>>
>>>>>> and please don't say that it is because some other document says to
>>>>>> encrypt everything. I want to know what is the benefit from doing so,
>>>>> [Cui Yang] I just answered your previous email providing the referred
>>>> section
>>>>> and document as you required, yesterday.
>>>>>
>>>>>> what are the risks in not doing so and what is the cost of doing so,
>>>>>> particularly in loss of accuracy, increased error budget, etc.
>>>>> [Cui Yang] That is our new draft trying to explain, please check it before
>>>>> posting your opinion.
>>>>>
>>>>>> The whole thing is a bad idea from what I can tell.
>>>>>>
>>>>>> Danny
>>>>>>
>>>>> Thanks,
>>>>> Yang
>>>>>
>>>>>
>>>>>> On 3/6/2012 10:35 PM, Cui Yang wrote:
>>>>>>> Hi, all,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I have posted a new draft that discusses the practical solutions for
>>>>>>> encrypted synchronization protocols.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Since we have discussed a lot on this problem, and the security
>>>>>>> requirement of synchronization also noted that confidentiality may
>>>> need
>>>>>>> protection, especially in case that the confidentiality protection is
>>>>>>> mandatory. Synchronization should be available when the traffic is
>>>>>>> encrypted. The influences by the encryption are explained, and
>>> several
>>>>>>> possible solutions have been discussed.
>>>>>>>
>>>>>>> The URL is below, please review and comment.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>      Title      : Practical solutions for encrypted synchronization
>>>>> protocol
>>>>>>> Author(s)  : Y. Cui,
>>>>>>>
>>>>>>> M. Bhatia,
>>>>>>>
>>>>>>> D. Zhang
>>>>>>>
>>>>>>> Filename   : draft-cui-tictoc-encrypted-synchronization-00.txt
>>>>>>>
>>>>>>> Pages     : 10
>>>>>>>
>>>>>>> Date      : Mar. 1, 2012
>>>>>>>
>>>>>>>     This informational document analyzes the accuracy issues with
>>> time
>>>>>>>     synchronization protocols when time synchronization packets are
>>>>>>>
>>>>>>>     encrypted during transmission. In addition, several candidate
>>>>>>>
>>>>>>>    solutions on such issues are introduced.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A URL for this Internet-Draft is:
>>>>>>>
>>>>>>>
>>> http://datatracker.ietf.org/doc/draft-cui-tictoc-encrypted-synchronization
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Yang
>>>>>>>
>>>>>>> ==================
>>>>>>>
>>>>>>> Yang Cui,  Ph.D.
>>>>>>>
>>>>>>> Huawei Technologies
>>>>>>>
>>>>>>> cuiyang@huawei.com
>>>>> _______________________________________________
>>>>> TICTOC mailing list
>>>>> TICTOC@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg


-- 
blu

Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. - Martin Golding
-----------------------------------------------------------------------|
Brian Utterback - Solaris RPE, Oracle Corporation.
Ph:603-262-3916, Em:brian.utterback@oracle.com

