
From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Oct 18 05:30:26 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB6211E8287 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 18 Oct 2013 05:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.558
X-Spam-Level: 
X-Spam-Status: No, score=-104.558 tagged_above=-999 required=5 tests=[AWL=2.041, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 VmKHOh4LLQEv for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 18 Oct 2013 05:30:18 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 76A7F11E82AE for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 18 Oct 2013 05:29:40 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4667E86DAB1 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 18 Oct 2013 12:29:40 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2FD1286D333 for <ntpwg@lists.ntp.org>; Fri, 18 Oct 2013 12:29:22 +0000 (UTC)
Received: from mail.ietf.org ([2001:1890:123a::1:1e]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <internet-drafts@ietf.org>) id 1VX9BB-000AGt-Ip for ntpwg@lists.ntp.org; Fri, 18 Oct 2013 12:29:22 +0000
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7103711E824D for <ntpwg@lists.ntp.org>; Fri, 18 Oct 2013 05:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 tYVdl1s5qa7p; Fri, 18 Oct 2013 05:29:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AA11611E82A6; Fri, 18 Oct 2013 05:28:54 -0700 (PDT)
MIME-Version: 1.0
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131018122854.4105.34496.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 05:28:54 -0700
X-SA-Exim-Connect-IP: 2001:1890:123a::1:1e
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: internet-drafts@ietf.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: ntpwg@lists.ntp.org
Subject: [ntpwg] I-D Action: draft-ietf-ntp-network-time-security-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Network Time Protocol Working Group of the IETF.

	Title           : Network Time Security
	Author(s)       : Dieter Sibold
                          Stephen Roettger
                          Kristof Teichel
	Filename        : draft-ietf-ntp-network-time-security-01.txt
	Pages           : 13
	Date            : 2013-10-18

Abstract:
   This document describes the Network Time Security (NTS) protocol that
   enables secure authentication of time servers using Network Time
   Protocol (NTP) or Precision Time Protocol (PTP).  Its design
   considers the special requirements of precise timekeeping, which are
   described in Security Requirements of Time Protocols in Packet
   Switched Network [I-D.ietf-tictoc-security-requirements].



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ntp-network-time-security

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-ntp-network-time-security-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-network-time-security-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 21 02:03:50 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D3011E84B0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 21 Oct 2013 02:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.431
X-Spam-Level: 
X-Spam-Status: No, score=-4.431 tagged_above=-999 required=5 tests=[AWL=2.167, 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 BsC8BL7MdSD2 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 21 Oct 2013 02:03:35 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id C59B511E8371 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 21 Oct 2013 02:03:32 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2EFEA86DAAD for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 21 Oct 2013 09:03:32 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 1C0BA86D564 for <ntpwg@lists.ntp.org>; Mon, 21 Oct 2013 09:03:13 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VYBOK-000EL5-3V for ntpwg@lists.ntp.org; Mon, 21 Oct 2013 09:03:13 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9L93BXX006228 for <ntpwg@lists.ntp.org>; Mon, 21 Oct 2013 02:03:11 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1fm29dvysk-23 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ntpwg@lists.ntp.org>; Mon, 21 Oct 2013 02:03:10 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 21 Oct 2013 02:03:06 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Mon, 21 Oct 2013 10:59:35 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Date: Mon, 21 Oct 2013 11:59:33 +0200
Thread-Topic: New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7OO4c4HpIqBv2RTa67LJO0HOqoNA==
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-20_04:2013-10-18, 2013-10-20, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310210015
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7796671999671438972=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============7796671999671438972==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_74470498B659FA4687F0B0018C19A89C01B87D7A40A6ILMB01marve_"

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

Hi,

A new version is available:
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01

The most significant change since the last draft is that this draft is *not=
* intended for authenticated mode.
This was in response to security related concerns from Danny and Harlan.
I believe the current draft does not present a new security vulnerability c=
ompared to the existing NTPv4.

(I think) I managed to convince Harlan of this. I am not sure I convinced D=
anny yet...

Anyway, this issue was updated in:

1.  The security consideration section.

2.  Section 3.4 about using the checksum trailer with authentication.

Thanks,
Tal Mizrahi.


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.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;}
--></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 new vers=
ion is available:<o:p></o:p></p><p class=3DMsoNormal><a href=3D"http://tool=
s.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01">http://tools.ietf.or=
g/html/draft-mizrahi-ntp-checksum-trailer-01</a><o:p></o:p></p><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The most significant cha=
nge since the last draft is that this draft is *<b>not</b>* intended for au=
thenticated mode.<o:p></o:p></p><p class=3DMsoNormal>This was in response t=
o security related concerns from Danny and Harlan.<o:p></o:p></p><p class=
=3DMsoNormal>I believe the current draft does not present a new security vu=
lnerability compared to the existing NTPv4.<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>(I think) I managed to convin=
ce Harlan of this. I am not sure I convinced Danny yet&#8230;<o:p></o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Anyway, thi=
s issue was updated in:<o:p></o:p></p><p class=3DMsoPlainText>1.&nbsp; The =
security consideration section.<o:p></o:p></p><p class=3DMsoPlainText>2.&nb=
sp; Section 3.4 about using the checksum trailer with authentication.<o:p><=
/o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Tha=
nks,<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Arial","sans-serif"'>Tal Mizrahi.<o:p></o:p></span></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01B87D7A40A6ILMB01marve_--

--===============7796671999671438972==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============7796671999671438972==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sat Oct 26 14:16:44 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B822B11E81D1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sat, 26 Oct 2013 14:16:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blIS7ob7DVWe for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sat, 26 Oct 2013 14:16:40 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 3B11B11E8200 for <ntp-archives-ahFae6za@lists.ietf.org>; Sat, 26 Oct 2013 14:16:26 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 7936B86D90A for <ntp-archives-ahFae6za@lists.ietf.org>; Sat, 26 Oct 2013 21:16:24 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2488286D33D for <ntpwg@lists.ntp.org>; Sat, 26 Oct 2013 21:16:06 +0000 (UTC)
Received: from pool-173-76-231-254.bstnma.fios.verizon.net ([173.76.231.254] helo=[192.168.1.7]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VaBDI-000C2C-8C; Sat, 26 Oct 2013 21:16:05 +0000
Message-ID: <526C30F9.1040400@ntp.org>
Date: Sat, 26 Oct 2013 17:15:37 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>,  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 173.76.231.254
X-SA-Exim-Rcpt-To: talmi@marvell.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)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

T24gMTAvMjEvMjAxMyA1OjU5IEFNLCBUYWwgTWl6cmFoaSB3cm90ZToKPiBIaSwKPiBBIG5ldyB2
ZXJzaW9uIGlzIGF2YWlsYWJsZToKPiAKPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1taXpyYWhpLW50cC1jaGVja3N1bS10cmFpbGVyLTAxCj4gCj4gVGhlIG1vc3Qgc2lnbmlmaWNh
bnQgY2hhbmdlIHNpbmNlIHRoZSBsYXN0IGRyYWZ0IGlzIHRoYXQgdGhpcyBkcmFmdCBpcwo+ICoq
bm90KiogaW50ZW5kZWQgZm9yIGF1dGhlbnRpY2F0ZWQgbW9kZS4KPiAKPiBUaGlzIHdhcyBpbiBy
ZXNwb25zZSB0byBzZWN1cml0eSByZWxhdGVkIGNvbmNlcm5zIGZyb20gRGFubnkgYW5kIEhhcmxh
bi4KPiAKPiBJIGJlbGlldmUgdGhlIGN1cnJlbnQgZHJhZnQgZG9lcyBub3QgcHJlc2VudCBhIG5l
dyBzZWN1cml0eQo+IHZ1bG5lcmFiaWxpdHkgY29tcGFyZWQgdG8gdGhlIGV4aXN0aW5nIE5UUHY0
Lgo+IAo+IChJIHRoaW5rKSBJIG1hbmFnZWQgdG8gY29udmluY2UgSGFybGFuIG9mIHRoaXMuIEkg
YW0gbm90IHN1cmUgSQo+IGNvbnZpbmNlZCBEYW5ueSB5ZXTDgsKFCj4gCgpMZXQgbWUgdHJ5IGFu
ZCBleHBsYWluIG15IHdvcnJpZXMgYWJvdXQgdGhpcyBleHRlbnNpb24gZmllbGQuClRoZSBkcmFm
dCBpcyBtYXJrZWQgYXMgZXhwZXJpbWVudGFsIHNvIGl0IGZhbGxzIGludG8gdGhlIGNhdGVnb3J5
IG9mCnNvbWV0aGluZyBzb21lb25lIHdhbnQncyB0byB0cnkgYnV0IHdvbid0IG5lY2Vzc2FyaWx5
IG1ha2UgaXQgZnVydGhlcgp0aGFuIHRoYXQuCgpUaGUgcHJvcG9zYWwncyBpbnRlbnQgaXMgdG8g
YWxsb3cgdGhlIHBhY2tldCB0byBiZSBtb2RpZmllZCBpbi1mbGlnaHQgdG8KY2hhbmdlIHRoZSBw
cmV2aW91c2x5IHByb3ZpZGVkIHRpbWVzdGFtcCB3aXRoIGFub3RoZXIgb25lLiBXaGVuIG9uZSBk
b2VzCnRoYXQgdGhlIHBhY2tldCdzIGV4aXN0aW5nIFVEUCBjaGVja3N1bSBiZWNvbWVzIGludmFs
aWQuIEluIG9yZGVyIHRvCmRlYWwgd2l0aCB0aGlzLCBpbnN0ZWFkIG9mIHVwZGF0aW5nIHRoZSBV
RFAgY2hlY2tzdW0gaXRzZWxmLCB0aGUKZXh0ZW5zaW9uIGZpZWxkIGlzIGVpdGhlciBhZGRlZCwg
b3IgdXBkYXRlZCwgSSdtIG5vdCBjbGVhciB3aGljaCwgc28KdGhhdCB0aGUgYWRkaXRpb25hbCBz
ZXQgb2YgYml0cyBtYWtlcyB0aGUgb3JpZ2luYWwgVURQIGNoZWNrc3VtIGJlCmNvcnJlY3QuIFRo
ZSBkcmFmdCBkb2VzIG5vdCBzdGF0ZSB3aGV0aGVyIG9yIG5vdCB0aGUgc291cmNlIG9mIHRoZQpw
YWNrZXQgY3JlYXRlcyB0aGUgZXh0ZW5zaW9uIGZpZWxkIGJlZm9yZSBpdCBpcyBzZW50IHRvIHRo
ZSByZWNpcGllbnQuClRoYXQgbmVlZHMgdG8gYmUgY2xhcmlmaWVkLiBFaXRoZXIgd2F5IHRoZSBp
bnRlbnQgb2YgdGhlIGV4dGVuc2lvbiBmaWVsZAppcyBqdXN0IHRvIHByb3ZpZGUgYSBkZWx0YSBz
byB0aGF0IHRoZSBvcmlnaW5hdG9yJ3Mgb3JpZ2luYWwgVURQCmNoZWNrc3VtIHdvcmtzLiBJdCBo
YXMgbm8gb3RoZXIgZnVuY3Rpb24uIFBvdGVudGlhbGx5IHRoZSB0aW1lc3RhbXAKY291bGQgYmUg
dXBkYXRlZCBtdWx0aXBsZSB0aW1lcyBieSBpbnRlcm1lZGlhcmllcyBhbmQgdGhlIGV4dGVuc2lv
bgpmaWVsZCB1cGRhdGVkIGVhY2ggdGltZS4gVGhpcyBhbHNvIG1lYW5zIHRoYXQgYSBNQUMgY2Fu
bm90IGJlIHByZXNlbnQKdW5sZXNzIHRoZSBNQUMgaXMgdXBkYXRlZCBlYWNoIHRpbWUgYW5kIHNl
Y3VyaXR5IGxpa2UgYXV0b2tleSBjYW5ub3QgYmUKdXNlZC4KCk15IHdvcnJ5IGhlcmUgaXMgdGhh
dCB0aGlzIGp1c3QgcHJvdmlkZXMgYW5vdGhlciB3YXkgb2YgY2hhbmdpbmcgdGhlCmNvbnRlbnRz
IG9mIHRoZSBOVFAgcGFja2V0IHdpdGhvdXQgZGlzdHVyYmluZyB0aGUgb3JpZ2luYWwgVURQIGNo
ZWNrc3VtLgpJdCdzIG5vdCBzb21ldGhpbmcgSSB3b3VsZCB3YW50IHRvIGVuY291cmFnZS4gSSBh
bSBhd2FyZSB0aGF0IGl0IGlzIGVhc3kKZW5vdWdoIHRvIGNoYW5nZSB0aGUgY29udGVudHMgb2Yg
YSBwYWNrZXQgQU5EIHRoZSBVRFAgY2hlY2tzdW0gYW5kIG5vb25lCndvdWxkIGJlIHRoZSB3aXNl
ciBidXQgSSBkb24ndCB0aGluayB0aGF0IGl0J3MgZ29vZCBwb2xpY3kuCgoKRGFubnkKX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbnRwd2cgbWFpbGluZyBs
aXN0Cm50cHdnQGxpc3RzLm50cC5vcmcKaHR0cDovL2xpc3RzLm50cC5vcmcvbGlzdGluZm8vbnRw
d2c=

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Oct 27 00:58:52 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AC111E824A for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 00:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.865
X-Spam-Level: 
X-Spam-Status: No, score=-4.865 tagged_above=-999 required=5 tests=[AWL=1.734, BAYES_00=-2.599, 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 Jx6VWYvUWEWM for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 00:58:47 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 3A30111E822F for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 00:58:44 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id B674486DADA for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 07:58:43 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id A05A486D33D for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 07:58:28 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VaLEw-000FNu-PJ; Sun, 27 Oct 2013 07:58:28 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9R7wOAO019233; Sun, 27 Oct 2013 00:58:25 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1fr72uv22a-10 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 27 Oct 2013 00:58:25 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 27 Oct 2013 00:58:24 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Sun, 27 Oct 2013 09:58:21 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "mayer@ntp.org" <mayer@ntp.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Date: Sun, 27 Oct 2013 09:58:18 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7SkJgiA/cCIqidR7KVL0f/xqp05QAWBUhg
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org>
In-Reply-To: <526C30F9.1040400@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_01:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310270011
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

SGkgRGFubnksDQoNCj5UaGUgZHJhZnQgZG9lcyBub3Qgc3RhdGUgd2hldGhlciBvciBub3QgdGhl
IHNvdXJjZSBvZiB0aGUgcGFja2V0IGNyZWF0ZXMgdGhlIGV4dGVuc2lvbiBmaWVsZCBiZWZvcmUg
aXQgaXMgc2VudCB0byB0aGUgcmVjaXBpZW50Lg0KPlRoYXQgbmVlZHMgdG8gYmUgY2xhcmlmaWVk
Lg0KDQpUaGUgc291cmNlIHNob3VsZCBjcmVhdGUgdGhlIGV4dGVuc2lvbiBmaWVsZCBpbiBhZHZh
bmNlLiBJIHdpbGwgY2xhcmlmeSB0aGlzIGluIHRoZSBkcmFmdC4NCg0KDQo+SSBhbSBhd2FyZSB0
aGF0IGl0IGlzIGVhc3kgZW5vdWdoIHRvIGNoYW5nZSB0aGUgY29udGVudHMgb2YgYSBwYWNrZXQg
QU5EIHRoZSBVRFAgY2hlY2tzdW0gYW5kIG5vb25lIHdvdWxkIGJlIHRoZSB3aXNlciANCg0KUmln
aHQsIEkgY29tcGxldGVseSBhZ3JlZS4NCg0KPmJ1dCBJIGRvbid0IHRoaW5rIHRoYXQgaXQncyBn
b29kIHBvbGljeS4NCg0KDQpUaGFua3MsDQpUYWwuDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCkZyb206IERhbm55IE1heWVyIFttYWlsdG86bWF5ZXJAbnRwLm9yZ10gDQpTZW50OiBT
dW5kYXksIE9jdG9iZXIgMjcsIDIwMTMgMTI6MTYgQU0NClRvOiBUYWwgTWl6cmFoaTsgbnRwd2dA
bGlzdHMubnRwLm9yZw0KU3ViamVjdDogUmU6IFtudHB3Z10gTmV3IHZlcnNpb24gb2YgZHJhZnQt
bWl6cmFoaS1udHAtY2hlY2tzdW0tdHJhaWxlcg0KDQpPbiAxMC8yMS8yMDEzIDU6NTkgQU0sIFRh
bCBNaXpyYWhpIHdyb3RlOg0KPiBIaSwNCj4gQSBuZXcgdmVyc2lvbiBpcyBhdmFpbGFibGU6DQo+
IA0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1taXpyYWhpLW50cC1jaGVja3N1
bS10cmFpbGVyLTAxDQo+IA0KPiBUaGUgbW9zdCBzaWduaWZpY2FudCBjaGFuZ2Ugc2luY2UgdGhl
IGxhc3QgZHJhZnQgaXMgdGhhdCB0aGlzIGRyYWZ0IGlzDQo+ICoqbm90KiogaW50ZW5kZWQgZm9y
IGF1dGhlbnRpY2F0ZWQgbW9kZS4NCj4gDQo+IFRoaXMgd2FzIGluIHJlc3BvbnNlIHRvIHNlY3Vy
aXR5IHJlbGF0ZWQgY29uY2VybnMgZnJvbSBEYW5ueSBhbmQgSGFybGFuLg0KPiANCj4gSSBiZWxp
ZXZlIHRoZSBjdXJyZW50IGRyYWZ0IGRvZXMgbm90IHByZXNlbnQgYSBuZXcgc2VjdXJpdHkgDQo+
IHZ1bG5lcmFiaWxpdHkgY29tcGFyZWQgdG8gdGhlIGV4aXN0aW5nIE5UUHY0Lg0KPiANCj4gKEkg
dGhpbmspIEkgbWFuYWdlZCB0byBjb252aW5jZSBIYXJsYW4gb2YgdGhpcy4gSSBhbSBub3Qgc3Vy
ZSBJIA0KPiBjb252aW5jZWQgRGFubnkgeWV0w4LChQ0KPiANCg0KTGV0IG1lIHRyeSBhbmQgZXhw
bGFpbiBteSB3b3JyaWVzIGFib3V0IHRoaXMgZXh0ZW5zaW9uIGZpZWxkLg0KVGhlIGRyYWZ0IGlz
IG1hcmtlZCBhcyBleHBlcmltZW50YWwgc28gaXQgZmFsbHMgaW50byB0aGUgY2F0ZWdvcnkgb2Yg
c29tZXRoaW5nIHNvbWVvbmUgd2FudCdzIHRvIHRyeSBidXQgd29uJ3QgbmVjZXNzYXJpbHkgbWFr
ZSBpdCBmdXJ0aGVyIHRoYW4gdGhhdC4NCg0KVGhlIHByb3Bvc2FsJ3MgaW50ZW50IGlzIHRvIGFs
bG93IHRoZSBwYWNrZXQgdG8gYmUgbW9kaWZpZWQgaW4tZmxpZ2h0IHRvIGNoYW5nZSB0aGUgcHJl
dmlvdXNseSBwcm92aWRlZCB0aW1lc3RhbXAgd2l0aCBhbm90aGVyIG9uZS4gV2hlbiBvbmUgZG9l
cyB0aGF0IHRoZSBwYWNrZXQncyBleGlzdGluZyBVRFAgY2hlY2tzdW0gYmVjb21lcyBpbnZhbGlk
LiBJbiBvcmRlciB0byBkZWFsIHdpdGggdGhpcywgaW5zdGVhZCBvZiB1cGRhdGluZyB0aGUgVURQ
IGNoZWNrc3VtIGl0c2VsZiwgdGhlIGV4dGVuc2lvbiBmaWVsZCBpcyBlaXRoZXIgYWRkZWQsIG9y
IHVwZGF0ZWQsIEknbSBub3QgY2xlYXIgd2hpY2gsIHNvIHRoYXQgdGhlIGFkZGl0aW9uYWwgc2V0
IG9mIGJpdHMgbWFrZXMgdGhlIG9yaWdpbmFsIFVEUCBjaGVja3N1bSBiZSBjb3JyZWN0LiBUaGUg
ZHJhZnQgZG9lcyBub3Qgc3RhdGUgd2hldGhlciBvciBub3QgdGhlIHNvdXJjZSBvZiB0aGUgcGFj
a2V0IGNyZWF0ZXMgdGhlIGV4dGVuc2lvbiBmaWVsZCBiZWZvcmUgaXQgaXMgc2VudCB0byB0aGUg
cmVjaXBpZW50Lg0KVGhhdCBuZWVkcyB0byBiZSBjbGFyaWZpZWQuIEVpdGhlciB3YXkgdGhlIGlu
dGVudCBvZiB0aGUgZXh0ZW5zaW9uIGZpZWxkIGlzIGp1c3QgdG8gcHJvdmlkZSBhIGRlbHRhIHNv
IHRoYXQgdGhlIG9yaWdpbmF0b3IncyBvcmlnaW5hbCBVRFAgY2hlY2tzdW0gd29ya3MuIEl0IGhh
cyBubyBvdGhlciBmdW5jdGlvbi4gUG90ZW50aWFsbHkgdGhlIHRpbWVzdGFtcCBjb3VsZCBiZSB1
cGRhdGVkIG11bHRpcGxlIHRpbWVzIGJ5IGludGVybWVkaWFyaWVzIGFuZCB0aGUgZXh0ZW5zaW9u
IGZpZWxkIHVwZGF0ZWQgZWFjaCB0aW1lLiBUaGlzIGFsc28gbWVhbnMgdGhhdCBhIE1BQyBjYW5u
b3QgYmUgcHJlc2VudCB1bmxlc3MgdGhlIE1BQyBpcyB1cGRhdGVkIGVhY2ggdGltZSBhbmQgc2Vj
dXJpdHkgbGlrZSBhdXRva2V5IGNhbm5vdCBiZSB1c2VkLg0KDQpNeSB3b3JyeSBoZXJlIGlzIHRo
YXQgdGhpcyBqdXN0IHByb3ZpZGVzIGFub3RoZXIgd2F5IG9mIGNoYW5naW5nIHRoZSBjb250ZW50
cyBvZiB0aGUgTlRQIHBhY2tldCB3aXRob3V0IGRpc3R1cmJpbmcgdGhlIG9yaWdpbmFsIFVEUCBj
aGVja3N1bS4NCkl0J3Mgbm90IHNvbWV0aGluZyBJIHdvdWxkIHdhbnQgdG8gZW5jb3VyYWdlLiBJ
IGFtIGF3YXJlIHRoYXQgaXQgaXMgZWFzeSBlbm91Z2ggdG8gY2hhbmdlIHRoZSBjb250ZW50cyBv
ZiBhIHBhY2tldCBBTkQgdGhlIFVEUCBjaGVja3N1bSBhbmQgbm9vbmUgd291bGQgYmUgdGhlIHdp
c2VyIGJ1dCBJIGRvbid0IHRoaW5rIHRoYXQgaXQncyBnb29kIHBvbGljeS4NCg0KDQpEYW5ueQ0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbnRwd2cgbWFp
bGluZyBsaXN0Cm50cHdnQGxpc3RzLm50cC5vcmcKaHR0cDovL2xpc3RzLm50cC5vcmcvbGlzdGlu
Zm8vbnRwd2c=

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Oct 27 06:35:12 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B11F21E80BC for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 06:35:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtfuxR2YN25l for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 06:35:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id DCAE211E81D5 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 06:35:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 5B43886DAD5 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 13:35:07 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2F73C86D33D for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 13:34:50 +0000 (UTC)
Received: from pool-173-76-231-254.bstnma.fios.verizon.net ([173.76.231.254] helo=[192.168.1.7]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VaQUR-000LhP-Sg; Sun, 27 Oct 2013 13:34:49 +0000
Message-ID: <526D165D.3040902@ntp.org>
Date: Sun, 27 Oct 2013 09:34:21 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>,  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 173.76.231.254
X-SA-Exim-Rcpt-To: talmi@marvell.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)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
> Hi Danny,
> =

>> The draft does not state whether or not the source of the packet creates=
 the extension field before it is sent to the recipient.
>> That needs to be clarified.
> =

> The source should create the extension field in advance. I will clarify t=
his in the draft.
> =


That also means that the extension field MUST NOT be added by any
intermediate nodes if it does not exist.

Danny

> =

>> I am aware that it is easy enough to change the contents of a packet AND=
 the UDP checksum and noone would be the wiser =

> =

> Right, I completely agree.
> =

>> but I don't think that it's good policy.
> =

> =

> Thanks,
> Tal.
> =

> =

> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org] =

> Sent: Sunday, October 27, 2013 12:16 AM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
> =

> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>> Hi,
>> A new version is available:
>>
>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>
>> The most significant change since the last draft is that this draft is
>> **not** intended for authenticated mode.
>>
>> This was in response to security related concerns from Danny and Harlan.
>>
>> I believe the current draft does not present a new security =

>> vulnerability compared to the existing NTPv4.
>>
>> (I think) I managed to convince Harlan of this. I am not sure I =

>> convinced Danny yet=C3=82=C2=85
>>
> =

> Let me try and explain my worries about this extension field.
> The draft is marked as experimental so it falls into the category of some=
thing someone want's to try but won't necessarily make it further than that.
> =

> The proposal's intent is to allow the packet to be modified in-flight to =
change the previously provided timestamp with another one. When one does th=
at the packet's existing UDP checksum becomes invalid. In order to deal wit=
h this, instead of updating the UDP checksum itself, the extension field is=
 either added, or updated, I'm not clear which, so that the additional set =
of bits makes the original UDP checksum be correct. The draft does not stat=
e whether or not the source of the packet creates the extension field befor=
e it is sent to the recipient.
> That needs to be clarified. Either way the intent of the extension field =
is just to provide a delta so that the originator's original UDP checksum w=
orks. It has no other function. Potentially the timestamp could be updated =
multiple times by intermediaries and the extension field updated each time.=
 This also means that a MAC cannot be present unless the MAC is updated eac=
h time and security like autokey cannot be used.
> =

> My worry here is that this just provides another way of changing the cont=
ents of the NTP packet without disturbing the original UDP checksum.
> It's not something I would want to encourage. I am aware that it is easy =
enough to change the contents of a packet AND the UDP checksum and noone wo=
uld be the wiser but I don't think that it's good policy.
> =

> =

> Danny
> =


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Oct 27 06:43:06 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02EAA21E80BE for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 06:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.154
X-Spam-Level: 
X-Spam-Status: No, score=-5.154 tagged_above=-999 required=5 tests=[AWL=1.445, BAYES_00=-2.599, 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 zmR1K97-ASRI for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 06:43:00 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7A121E809D for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 06:42:59 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1B76586DAE3 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 13:42:59 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id F0D0586D33D for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 13:42:53 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VaQcG-000Lkb-6L; Sun, 27 Oct 2013 13:42:53 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9RDgoPn017295; Sun, 27 Oct 2013 06:42:50 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1fr72uvnds-31 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 27 Oct 2013 06:42:50 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 27 Oct 2013 06:42:48 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Sun, 27 Oct 2013 15:42:43 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "mayer@ntp.org" <mayer@ntp.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Date: Sun, 27 Oct 2013 15:42:40 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7TGVROIR4M8mJZS5WfzLNGGqyXPAAABTrw
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org>
In-Reply-To: <526D165D.3040902@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_01:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310270093
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Danny,

>That also means that the extension field MUST NOT be added by any intermed=
iate nodes if it does not exist.

I am not sure we want to go there, for 2 reasons:

1. Let's not forget that the source and the intermediate node are in fact t=
wo modules in the same client/server (see Figure 1 in the draft). From an i=
nteroperability perspective it would be exactly the same if the source crea=
ted the extension field, or the intermediate node did. Why would we mandate=
 a specific implementation detail that would be completely transparent to t=
he network?

2. A clock that receives an NTP message has no way of knowing whether an ex=
tension field was added by the source or by an intermediate node, and thus =
there is no way to enforce (enforce from a security perspective) the requir=
ement you suggested.

Tal.


-----Original Message-----
From: Danny Mayer [mailto:mayer@ntp.org] =

Sent: Sunday, October 27, 2013 3:34 PM
To: Tal Mizrahi; ntpwg@lists.ntp.org
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer

On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
> Hi Danny,
> =

>> The draft does not state whether or not the source of the packet creates=
 the extension field before it is sent to the recipient.
>> That needs to be clarified.
> =

> The source should create the extension field in advance. I will clarify t=
his in the draft.
> =


That also means that the extension field MUST NOT be added by any intermedi=
ate nodes if it does not exist.

Danny

> =

>> I am aware that it is easy enough to change the contents of a packet =

>> AND the UDP checksum and noone would be the wiser
> =

> Right, I completely agree.
> =

>> but I don't think that it's good policy.
> =

> =

> Thanks,
> Tal.
> =

> =

> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org]
> Sent: Sunday, October 27, 2013 12:16 AM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
> =

> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>> Hi,
>> A new version is available:
>>
>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>
>> The most significant change since the last draft is that this draft =

>> is
>> **not** intended for authenticated mode.
>>
>> This was in response to security related concerns from Danny and Harlan.
>>
>> I believe the current draft does not present a new security =

>> vulnerability compared to the existing NTPv4.
>>
>> (I think) I managed to convince Harlan of this. I am not sure I =

>> convinced Danny yet=C3,=C2.
>>
> =

> Let me try and explain my worries about this extension field.
> The draft is marked as experimental so it falls into the category of some=
thing someone want's to try but won't necessarily make it further than that.
> =

> The proposal's intent is to allow the packet to be modified in-flight to =
change the previously provided timestamp with another one. When one does th=
at the packet's existing UDP checksum becomes invalid. In order to deal wit=
h this, instead of updating the UDP checksum itself, the extension field is=
 either added, or updated, I'm not clear which, so that the additional set =
of bits makes the original UDP checksum be correct. The draft does not stat=
e whether or not the source of the packet creates the extension field befor=
e it is sent to the recipient.
> That needs to be clarified. Either way the intent of the extension field =
is just to provide a delta so that the originator's original UDP checksum w=
orks. It has no other function. Potentially the timestamp could be updated =
multiple times by intermediaries and the extension field updated each time.=
 This also means that a MAC cannot be present unless the MAC is updated eac=
h time and security like autokey cannot be used.
> =

> My worry here is that this just provides another way of changing the cont=
ents of the NTP packet without disturbing the original UDP checksum.
> It's not something I would want to encourage. I am aware that it is easy =
enough to change the contents of a packet AND the UDP checksum and noone wo=
uld be the wiser but I don't think that it's good policy.
> =

> =

> Danny
> =


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Oct 27 12:19:39 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD3C11E81EB for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 12:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, 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 7xMzbP7pi6jS for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 12:19:35 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id EA00911E80E9 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 12:19:34 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id ECF8E86DAE9 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 19:19:34 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8FC4986D33D for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 19:19:18 +0000 (UTC)
Received: from pool-173-76-231-254.bstnma.fios.verizon.net ([173.76.231.254] helo=[192.168.1.7]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VaVrn-000NWs-Sy; Sun, 27 Oct 2013 19:19:18 +0000
Message-ID: <526D671A.7050908@ntp.org>
Date: Sun, 27 Oct 2013 15:18:50 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>,  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 173.76.231.254
X-SA-Exim-Rcpt-To: talmi@marvell.com, ntpwg@lists.ntp.org, tictoc@ietf.org
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 10/27/2013 9:42 AM, Tal Mizrahi wrote:
> Hi Danny,
> =

>> That also means that the extension field MUST NOT be added by any interm=
ediate nodes if it does not exist.
> =

> I am not sure we want to go there, for 2 reasons:
> =

> 1. Let's not forget that the source and the intermediate node are in
fact two modules in the same client/server (see Figure 1 in the draft).
>From an interoperability perspective it would be exactly the same if the
source created the extension field, or the intermediate node did. Why
would we mandate a specific implementation detail that would be
completely transparent to the network?

Maybe I missed that in the draft, but don't you want the sending server
to decide whether or not it expects the timestamp be updated? Having
intermediate systems update the timestamp and extension field without
the originating server sanctioning it seems even worse (to me).

> =

> 2. A clock that receives an NTP message has no way of knowing
> whether
an extension field was added by the source or by an intermediate node,
and thus there is no way to enforce (enforce from a security
perspective) the requirement you suggested.
> =


True enough but don't you want the originator to have a say in this so
that this becomes a recommendation for developers?

I've added TICTOC to the discussion. It was not in the original mail.

Danny

> Tal.
> =

> =

> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org] =

> Sent: Sunday, October 27, 2013 3:34 PM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
> =

> On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> The draft does not state whether or not the source of the packet create=
s the extension field before it is sent to the recipient.
>>> That needs to be clarified.
>>
>> The source should create the extension field in advance. I will clarify =
this in the draft.
>>
> =

> That also means that the extension field MUST NOT be added by any interme=
diate nodes if it does not exist.
> =

> Danny
> =

>>
>>> I am aware that it is easy enough to change the contents of a packet =

>>> AND the UDP checksum and noone would be the wiser
>>
>> Right, I completely agree.
>>
>>> but I don't think that it's good policy.
>>
>>
>> Thanks,
>> Tal.
>>
>>
>> -----Original Message-----
>> From: Danny Mayer [mailto:mayer@ntp.org]
>> Sent: Sunday, October 27, 2013 12:16 AM
>> To: Tal Mizrahi; ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
>>
>> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>>> Hi,
>>> A new version is available:
>>>
>>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>>
>>> The most significant change since the last draft is that this draft =

>>> is
>>> **not** intended for authenticated mode.
>>>
>>> This was in response to security related concerns from Danny and Harlan.
>>>
>>> I believe the current draft does not present a new security =

>>> vulnerability compared to the existing NTPv4.
>>>
>>> (I think) I managed to convince Harlan of this. I am not sure I =

>>> convinced Danny yet=C3,=C2.
>>>
>>
>> Let me try and explain my worries about this extension field.
>> The draft is marked as experimental so it falls into the category of som=
ething someone want's to try but won't necessarily make it further than tha=
t.
>>
>> The proposal's intent is to allow the packet to be modified in-flight to=
 change the previously provided timestamp with another one. When one does t=
hat the packet's existing UDP checksum becomes invalid. In order to deal wi=
th this, instead of updating the UDP checksum itself, the extension field i=
s either added, or updated, I'm not clear which, so that the additional set=
 of bits makes the original UDP checksum be correct. The draft does not sta=
te whether or not the source of the packet creates the extension field befo=
re it is sent to the recipient.
>> That needs to be clarified. Either way the intent of the extension field=
 is just to provide a delta so that the originator's original UDP checksum =
works. It has no other function. Potentially the timestamp could be updated=
 multiple times by intermediaries and the extension field updated each time=
. This also means that a MAC cannot be present unless the MAC is updated ea=
ch time and security like autokey cannot be used.
>>
>> My worry here is that this just provides another way of changing the con=
tents of the NTP packet without disturbing the original UDP checksum.
>> It's not something I would want to encourage. I am aware that it is easy=
 enough to change the contents of a packet AND the UDP checksum and noone w=
ould be the wiser but I don't think that it's good policy.
>>
>>
>> Danny
>>
> =

> =

> =


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Oct 27 23:34:56 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E7021E8096 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 23:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.244
X-Spam-Level: 
X-Spam-Status: No, score=-5.244 tagged_above=-999 required=5 tests=[AWL=1.355, BAYES_00=-2.599, 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 Q4l25+HdWE7b for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun, 27 Oct 2013 23:34:51 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id CC53521E8093 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun, 27 Oct 2013 23:34:47 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8111386DAA7 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 06:34:47 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 1F2FB86D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 06:34:28 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VagPC-0001Cj-PN; Mon, 28 Oct 2013 06:34:28 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9S6YPol029707; Sun, 27 Oct 2013 23:34:25 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1fr72krp84-1 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 27 Oct 2013 23:34:25 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 27 Oct 2013 23:34:18 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Mon, 28 Oct 2013 08:34:15 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "mayer@ntp.org" <mayer@ntp.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Date: Mon, 28 Oct 2013 08:34:11 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7TSXDmU3Tqo1l/RNqHMSTqY7BmbgAXdwTw
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org>
In-Reply-To: <526D671A.7050908@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_03:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310270347
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Danny,

>> 2. A clock that receives an NTP message has no way of knowing whether
>>an extension field was added by the source or by an intermediate node, an=
d thus there is no way to enforce (enforce from a security
>>perspective) the requirement you suggested.

>True enough but don't you want the originator to have a say in this so tha=
t this becomes a recommendation for developers?

As a recommendation it makes sense, and indeed I will add it as a SHOULD. =


Thanks,
Tal.


-----Original Message-----
From: Danny Mayer [mailto:mayer@ntp.org] =

Sent: Sunday, October 27, 2013 9:19 PM
To: Tal Mizrahi; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer

On 10/27/2013 9:42 AM, Tal Mizrahi wrote:
> Hi Danny,
> =

>> That also means that the extension field MUST NOT be added by any interm=
ediate nodes if it does not exist.
> =

> I am not sure we want to go there, for 2 reasons:
> =

> 1. Let's not forget that the source and the intermediate node are in
fact two modules in the same client/server (see Figure 1 in the draft).
>From an interoperability perspective it would be exactly the same if the so=
urce created the extension field, or the intermediate node did. Why would w=
e mandate a specific implementation detail that would be completely transpa=
rent to the network?

Maybe I missed that in the draft, but don't you want the sending server to =
decide whether or not it expects the timestamp be updated? Having intermedi=
ate systems update the timestamp and extension field without the originatin=
g server sanctioning it seems even worse (to me).

> =

> 2. A clock that receives an NTP message has no way of knowing whether
an extension field was added by the source or by an intermediate node, and =
thus there is no way to enforce (enforce from a security
perspective) the requirement you suggested.
> =


True enough but don't you want the originator to have a say in this so that=
 this becomes a recommendation for developers?

I've added TICTOC to the discussion. It was not in the original mail.

Danny

> Tal.
> =

> =

> -----Original Message-----
> From: Danny Mayer [mailto:mayer@ntp.org]
> Sent: Sunday, October 27, 2013 3:34 PM
> To: Tal Mizrahi; ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
> =

> On 10/27/2013 3:58 AM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> The draft does not state whether or not the source of the packet create=
s the extension field before it is sent to the recipient.
>>> That needs to be clarified.
>>
>> The source should create the extension field in advance. I will clarify =
this in the draft.
>>
> =

> That also means that the extension field MUST NOT be added by any interme=
diate nodes if it does not exist.
> =

> Danny
> =

>>
>>> I am aware that it is easy enough to change the contents of a packet =

>>> AND the UDP checksum and noone would be the wiser
>>
>> Right, I completely agree.
>>
>>> but I don't think that it's good policy.
>>
>>
>> Thanks,
>> Tal.
>>
>>
>> -----Original Message-----
>> From: Danny Mayer [mailto:mayer@ntp.org]
>> Sent: Sunday, October 27, 2013 12:16 AM
>> To: Tal Mizrahi; ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] New version of =

>> draft-mizrahi-ntp-checksum-trailer
>>
>> On 10/21/2013 5:59 AM, Tal Mizrahi wrote:
>>> Hi,
>>> A new version is available:
>>>
>>> http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01
>>>
>>> The most significant change since the last draft is that this draft =

>>> is
>>> **not** intended for authenticated mode.
>>>
>>> This was in response to security related concerns from Danny and Harlan.
>>>
>>> I believe the current draft does not present a new security =

>>> vulnerability compared to the existing NTPv4.
>>>
>>> (I think) I managed to convince Harlan of this. I am not sure I =

>>> convinced Danny yet=C3,=C2.
>>>
>>
>> Let me try and explain my worries about this extension field.
>> The draft is marked as experimental so it falls into the category of som=
ething someone want's to try but won't necessarily make it further than tha=
t.
>>
>> The proposal's intent is to allow the packet to be modified in-flight to=
 change the previously provided timestamp with another one. When one does t=
hat the packet's existing UDP checksum becomes invalid. In order to deal wi=
th this, instead of updating the UDP checksum itself, the extension field i=
s either added, or updated, I'm not clear which, so that the additional set=
 of bits makes the original UDP checksum be correct. The draft does not sta=
te whether or not the source of the packet creates the extension field befo=
re it is sent to the recipient.
>> That needs to be clarified. Either way the intent of the extension field=
 is just to provide a delta so that the originator's original UDP checksum =
works. It has no other function. Potentially the timestamp could be updated=
 multiple times by intermediaries and the extension field updated each time=
. This also means that a MAC cannot be present unless the MAC is updated ea=
ch time and security like autokey cannot be used.
>>
>> My worry here is that this just provides another way of changing the con=
tents of the NTP packet without disturbing the original UDP checksum.
>> It's not something I would want to encourage. I am aware that it is easy=
 enough to change the contents of a packet AND the UDP checksum and noone w=
ould be the wiser but I don't think that it's good policy.
>>
>>
>> Danny
>>
> =

> =

> =


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 01:10:03 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B2E11E8229 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 01:10:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YIeCiYVgAauD for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 01:09:57 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 96A7111E8151 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 01:09:22 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8697486D763 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 08:09:22 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id ECFC886D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 08:09:11 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vahsr-000Kke-9c; Mon, 28 Oct 2013 08:09:09 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Tal Mizrahi <talmi@marvell.com>
In-reply-to: <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com>
Comments: In-reply-to Tal Mizrahi <talmi@marvell.com> message dated "Mon, 28 Oct 2013 08:34:11 +0200."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Mon, 28 Oct 2013 08:09:09 +0000
Message-Id: <E1Vahsr-000Kke-9c@stenn.ntp.org>
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel
and the new packet timestamp will be added by the hardware engine.  I
understand the following question is outside the scope of this document,
but how can one determine how well sync'd the internal clock is with the
clock in the accurate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use
NTP's interleave mode to communicate these timestamps as well.  Having
said that, I'm sure there is something to be learned from implementing
Tal's proposal.

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 01:40:40 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D68C11E81BC for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 01:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, 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 tqPWOuczuu46 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 01:40:34 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id C361021E808A for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 01:39:50 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id A566786DABB for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 08:39:49 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id EA77286D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 08:39:41 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VaiMO-0001pw-4o; Mon, 28 Oct 2013 08:39:41 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9S8db3L031234; Mon, 28 Oct 2013 01:39:37 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1fr72uxqx5-3 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Oct 2013 01:39:37 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 28 Oct 2013 01:39:35 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Mon, 28 Oct 2013 10:38:59 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Harlan Stenn <stenn@ntp.org>
Date: Mon, 28 Oct 2013 10:38:55 +0200
Thread-Topic: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7TtQETTHSIehLBQt2pl+Gi3LYL7wAAzUoQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org>
In-Reply-To: <E1Vahsr-000Kke-9c@stenn.ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-27_03:2013-10-26, 2013-10-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310280017
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, stenn@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and the new packet timestamp will be added by the hardware engine.  
>I understand the following question is outside the scope of this document, but how can one determine how well sync'd the internal clock is with the clock in the accurate timestamp engine?

Well, indeed it is strictly an implementation question. For example, in typical PTP implementations (that I am familiar with) the accurate clock is only maintained in one place, i.e., in the HW engine. The SW stack includes the servo algorithm; the SW stack regularly computes the necessary offset or frequency adjustments, and whenever necessary sends update commands to the HW engine about these adjustments. Thus, the SW stack does not need to maintain an additional clock, since all its computations are performed WRT the HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org] 
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer

Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and the new packet timestamp will be added by the hardware engine.  I understand the following question is outside the scope of this document, but how can one determine how well sync'd the internal clock is with the clock in the accurate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's interleave mode to communicate these timestamps as well.  Having said that, I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 09:34:50 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DED321E8083 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 09:34:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iC3XNsoxhcN for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 09:34:44 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id EC43811E8187 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 09:34:43 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id D2B7C86D766 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 16:34:43 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9282786D33D for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 14:11:06 +0000 (UTC)
Received: from smtp-gw21.han.skanova.net ([81.236.55.21]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <magnus@rubidium.dyndns.org>) id 1VaR3Z-000LuF-40 for ntpwg@lists.ntp.org; Sun, 27 Oct 2013 14:11:06 +0000
Received: from magda-gw (81.226.54.139) by smtp-gw21.han.skanova.net (8.5.133) id 52551723007DBC92 for ntpwg@lists.ntp.org; Sun, 27 Oct 2013 15:10:58 +0100
Received: from [192.168.0.10] (knapptop [192.168.0.10]) by magda-gw (Postfix) with ESMTPSA id 6F956548073 for <ntpwg@lists.ntp.org>; Sun, 27 Oct 2013 15:10:57 +0100 (CET)
Message-ID: <526D1EF0.4070208@rubidium.dyndns.org>
Date: Sun, 27 Oct 2013 15:10:56 +0100
From: Magnus Danielson <magnus@rubidium.dyndns.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com>
X-SA-Exim-Connect-IP: 81.236.55.21
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: magnus@rubidium.dyndns.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Mon, 28 Oct 2013 16:34:28 +0000
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 10/27/2013 02:42 PM, Tal Mizrahi wrote:
> Hi Danny,
>
>> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
> I am not sure we want to go there, for 2 reasons:
>
> 1. Let's not forget that the source and the intermediate node are in fact two modules in the same client/server (see Figure 1 in the draft). From an interoperability perspective it would be exactly the same if the source created the extension field, or the intermediate node did. Why would we mandate a specific implementation detail that would be completely transparent to the network?
>
> 2. A clock that receives an NTP message has no way of knowing whether an extension field was added by the source or by an intermediate node, and thus there is no way to enforce (enforce from a security perspective) the requirement you suggested.
I think this discussion would benefit from separating "interface node"
from "intermediate node" as these have different roles. The interface
node would add the output time-stamp of the sending node. If
intermediate nodes where allowed to add fields, we could have buffer
compensation in NTP just as in PTP's transparent clock.

At the same time, as long as there is no authentication on this, any
intermediate node can create any form of modification that the receiver
node will accept, malicious or unintentional. Hence, there is only so
much protection you can create in the semantics.

Cheers,
Magnus
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 11:17:01 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C2921E80B5 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 11:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.431
X-Spam-Level: 
X-Spam-Status: No, score=-4.431 tagged_above=-999 required=5 tests=[AWL=2.167, 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 ZZturcXs+DML for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 11:16:46 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id D802C11E828D for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 11:16:43 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2100186DAB4 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 18:16:43 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2EACF86D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 18:16:28 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==013fb014d0b==gdowd@symmetricom.com>) id 1VarMR-0009Qj-Rn for ntpwg@lists.ntp.org; Mon, 28 Oct 2013 18:16:28 +0000
X-ASG-Debug-ID: 1382984173-05bdbc07004c3b90001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id dvc3tTEDzeG9DUA5 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 11:16:13 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 28 Oct 2013 11:16:13 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Kevin Stanton <kevin.b.stanton@gmail.com>, Tal Mizrahi <talmi@marvell.com>
Thread-Topic: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-ASG-Orig-Subj: RE: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: AQHO1AZ5DH+wauYAB0ajhRxEI/xQ5JoKaQjQ
Date: Mon, 28 Oct 2013 18:16:13 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED68392@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
In-Reply-To: <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1382984173
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==013fb014d0b==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [ntpwg] [TICTOC] New version of	draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2530152095523932111=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============2530152095523932111==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_"

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

There are a variety of different implementation techniques, some of which d=
o use free-running counters on the hw side, mapped to a software function u=
p higher.  Some NIC vendors are already doing that.  One of the challenges =
for that type of operation is that the entire system must be aware and desi=
gned for that purpose until kernels/drivers/applications catch up.  The bea=
uty of the "inline" function is that it can be inserted into the process, c=
orrecting errors on the input and/or output without changing the system at =
other layers.

The tight coupling of the servo to the timing hardware also tends to allow =
better precision in many cases, running in real-time or at high(er) data ra=
tes.  For some of our designs, we are synchronizing slave clocks in the sub=
 100ns (or better) in the presence of very high traffic loads.  Obviously, =
the application for this class of synchronization service is much more targ=
eted than Internet (capital I) but the market does exist so why not use the=
 technology.

From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Kevin Stanton
Sent: Monday, October 28, 2013 10:52 AM
To: Tal Mizrahi
Cc: ntpwg@lists.ntp.org; Harlan Stenn; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


--_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_
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";}
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;}
@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"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There are a variety of di=
fferent implementation techniques, some of which do use free-running counte=
rs on the hw side, mapped to a software function up higher.&nbsp;
 Some NIC vendors are already doing that.&nbsp; One of the challenges for t=
hat type of operation is that the entire system must be aware and designed =
for that purpose until kernels/drivers/applications catch up.&nbsp; The bea=
uty of the &#8220;inline&#8221; function is that it can
 be inserted into the process, correcting errors on the input and/or output=
 without changing the system at other layers.&nbsp;
<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">The tight coupling of the=
 servo to the timing hardware also tends to allow better precision in many =
cases, running in real-time or at high(er) data rates.&nbsp;
 For some of our designs, we are synchronizing slave clocks in the sub 100n=
s (or better) in the presence of very high traffic loads.&nbsp; Obviously, =
the application for this class of synchronization service is much more targ=
eted than Internet (capital I) but the
 market does exist so why not use the technology.<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></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 style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tictoc-b=
ounces@ietf.org [mailto:tictoc-bounces@ietf.org]
<b>On Behalf Of </b>Kevin Stanton<br>
<b>Sent:</b> Monday, October 28, 2013 10:52 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> ntpwg@lists.ntp.org; Harlan Stenn; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-check=
sum-trailer<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">This is a somewhat unrelated question, but why not e=
liminate the servo?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If a software entity is the consumer of PTP time, I =
wonder if the benefit of avoiding the y=3Dmx&#43;b computation (to compute =
PTP time from the time of the free-running LAN hardware counter) is worth t=
he trouble of disciplining the hardware
 clock.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, the hardware engine maintains a time=
 reference and software maintains the parameters for translating that time =
reference to PTP time (also for hardware-captured Rx and Tx timestamps). &n=
bsp;Of course, this doesn't apply to one-step
 master ports.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Kevin Stanton.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi Harlan,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps com=
e from the kernel and the new packet timestamp will be added by the hardwar=
e engine.<br>
&gt;I understand the following question is outside the scope of this docume=
nt, but how can one determine how well sync'd the internal clock is with th=
e clock in the accurate timestamp engine?<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">Well, indeed it is strictly an implementation questi=
on. For example, in typical PTP implementations (that I am familiar with) t=
he accurate clock is only maintained in one place, i.e., in the HW engine. =
The SW stack includes the servo algorithm;
 the SW stack regularly computes the necessary offset or frequency adjustme=
nts, and whenever necessary sends update commands to the HW engine about th=
ese adjustments. Thus, the SW stack does not need to maintain an additional=
 clock, since all its computations
 are performed WRT the HW clock.<br>
<br>
Thanks,<br>
Tal.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
<br>
-----Original Message-----<br>
From: Harlan Stenn [mailto:<a href=3D"mailto:stenn@ntp.org" target=3D"_blan=
k">stenn@ntp.org</a>]<br>
Sent: Monday, October 28, 2013 10:09 AM<br>
To: Tal Mizrahi<br>
Cc: <a href=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>; <=
a href=3D"mailto:ntpwg@lists.ntp.org" target=3D"_blank">
ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_blan=
k">tictoc@ietf.org</a><br>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer<o:p>=
</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Just some thoughts, and I hope I'm awake enough to t=
ype this...<br>
<br>
There seem to be several issues here.<br>
<br>
In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps come fr=
om the kernel and the new packet timestamp will be added by the hardware en=
gine. &nbsp;I understand the following question is outside the scope of thi=
s document, but how can one determine how well sync'd the
 internal clock is with the clock in the accurate timestamp engine?<br>
<br>
If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well. &nbsp;Having said t=
hat, I'm sure there is something to be learned from implementing Tal's prop=
osal.<br>
<br>
H<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB6ED68392SJCMBX01symmetr_--

--===============2530152095523932111==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============2530152095523932111==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 11:58:14 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D90711E80E7 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 11:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.334
X-Spam-Level: 
X-Spam-Status: No, score=-5.334 tagged_above=-999 required=5 tests=[AWL=1.264, 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 nM-jqNnPL79K for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 11:58:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 6F06111E8348 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 11:57:49 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id A1C0686D769 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 18:57:45 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id C8A1686D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 18:57:36 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1Vas0L-0009f7-IO; Mon, 28 Oct 2013 18:57:36 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9SIvUZx002631; Mon, 28 Oct 2013 11:57:30 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1fr72kvwkd-7 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Oct 2013 11:57:30 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 28 Oct 2013 11:57:30 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Mon, 28 Oct 2013 20:57:25 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Kevin Stanton <kevin.b.stanton@gmail.com>
Date: Mon, 28 Oct 2013 20:57:20 +0200
Thread-Topic: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: Ac7UBniVzuInGczdQHuhXb12t+vraAAB6piQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
In-Reply-To: <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-28_03:2013-10-28, 2013-10-28, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310280145
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: stenn@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0531711091537820057=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============0531711091537820057==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_"

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

Hi Kevin,

Just to make sure we are on the same page: this thread started out as a thr=
ead about NTP, and specifically about the following draft:
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01

I think the point you suggested is basically a religious discussion of one-=
step vs. two-step clocks in PTP.
The example I referred to in the thread below is a PTP slave as an analogou=
s example to an NTP client. Since NTP is always one-step (no two-step mode =
in NTP), in our context the actual time-of-day has to be maintained in HW.

Please let me know if this makes sense.

Thanks,
Tal.

From: Kevin Stanton [mailto:kevin.b.stanton@gmail.com]
Sent: Monday, October 28, 2013 7:52 PM
To: Tal Mizrahi
Cc: Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@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";}
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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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 lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kevin,=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>Just to make sure we are on the same page: t=
his thread started out as a thread about NTP, and specifically about the fo=
llowing draft:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href=3D"=
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01">http://to=
ols.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>I think the point you suggested is basically a religious dis=
cussion of one-step vs. two-step clocks in PTP.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D'>The example I referred to in the thread below is a PT=
P slave as an analogous example to an NTP client. Since NTP is always one-s=
tep (no two-step mode in NTP), in our context the actual time-of-day has to=
 be maintained in HW.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>Please let me know if t=
his makes sense.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","=
sans-serif";color:#1F497D'>Tal.<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Kevin Stanton [m=
ailto:kevin.b.stanton@gmail.com] <br><b>Sent:</b> Monday, October 28, 2013 =
7:52 PM<br><b>To:</b> Tal Mizrahi<br><b>Cc:</b> Harlan Stenn; ntpwg@lists.n=
tp.org; tictoc@ietf.org<br><b>Subject:</b> Re: [TICTOC] [ntpwg] New version=
 of draft-mizrahi-ntp-checksum-trailer<o:p></o:p></span></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>This is a somewha=
t unrelated question, but why not eliminate the servo?<o:p></o:p></p></div>=
<div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNor=
mal>If a software entity is the consumer of PTP time, I wonder if the benef=
it of avoiding the y=3Dmx+b computation (to compute PTP time from the time =
of the free-running LAN hardware counter) is worth the trouble of disciplin=
ing the hardware clock.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In other words, the hardwar=
e engine maintains a time reference and software maintains the parameters f=
or translating that time reference to PTP time (also for hardware-captured =
Rx and Tx timestamps). &nbsp;Of course, this doesn't apply to one-step mast=
er ports.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>Thoughts?<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Kevin S=
tanton.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-botto=
m:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Mon, Oct 28, 20=
13 at 1:38 AM, Tal Mizrahi &lt;<a href=3D"mailto:talmi@marvell.com" target=
=3D"_blank">talmi@marvell.com</a>&gt; wrote:<o:p></o:p></p><p class=3DMsoNo=
rmal>Hi Harlan,<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bot=
tom:12.0pt'><br>&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packe=
t timestamps come from the kernel and the new packet timestamp will be adde=
d by the hardware engine.<br>&gt;I understand the following question is out=
side the scope of this document, but how can one determine how well sync'd =
the internal clock is with the clock in the accurate timestamp engine?<o:p>=
</o:p></p></div><p class=3DMsoNormal>Well, indeed it is strictly an impleme=
ntation question. For example, in typical PTP implementations (that I am fa=
miliar with) the accurate clock is only maintained in one place, i.e., in t=
he HW engine. The SW stack includes the servo algorithm; the SW stack regul=
arly computes the necessary offset or frequency adjustments, and whenever n=
ecessary sends update commands to the HW engine about these adjustments. Th=
us, the SW stack does not need to maintain an additional clock, since all i=
ts computations are performed WRT the HW clock.<br><br>Thanks,<br>Tal.<o:p>=
</o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><br>=
-----Original Message-----<br>From: Harlan Stenn [mailto:<a href=3D"mailto:=
stenn@ntp.org" target=3D"_blank">stenn@ntp.org</a>]<br>Sent: Monday, Octobe=
r 28, 2013 10:09 AM<br>To: Tal Mizrahi<br>Cc: <a href=3D"mailto:mayer@ntp.o=
rg" target=3D"_blank">mayer@ntp.org</a>; <a href=3D"mailto:ntpwg@lists.ntp.=
org" target=3D"_blank">ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ie=
tf.org" target=3D"_blank">tictoc@ietf.org</a><br>Subject: Re: [ntpwg] New v=
ersion of draft-mizrahi-ntp-checksum-trailer<o:p></o:p></p></div><div><div>=
<p class=3DMsoNormal>Just some thoughts, and I hope I'm awake enough to typ=
e this...<br><br>There seem to be several issues here.<br><br>In the &quot;=
Figure 1&quot; case &quot;core&quot; packet timestamps come from the kernel=
 and the new packet timestamp will be added by the hardware engine. &nbsp;I=
 understand the following question is outside the scope of this document, b=
ut how can one determine how well sync'd the internal clock is with the clo=
ck in the accurate timestamp engine?<br><br>If we have TX and RX hardware t=
imestamping capabilities, we can use NTP's interleave mode to communicate t=
hese timestamps as well. &nbsp;Having said that, I'm sure there is somethin=
g to be learned from implementing Tal's proposal.<br><br>H<br>_____________=
__________________________________<br>TICTOC mailing list<br><a href=3D"mai=
lto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br><a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">https://www.i=
etf.org/mailman/listinfo/tictoc</a><o:p></o:p></p></div></div></div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01B87D832C14ILMB01marve_--

--===============0531711091537820057==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============0531711091537820057==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 12:13:59 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF1A21F9D52 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, 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 2ZCOVWaH8HJZ for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 12:13:55 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 26ACB11E819F for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 12:13:54 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1374D86DAB9 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 19:13:54 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 598DE86D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 19:13:48 +0000 (UTC)
Received: from [198.22.153.36] (helo=[10.2.64.81]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VasG3-0009mV-9E; Mon, 28 Oct 2013 19:13:48 +0000
Message-ID: <526EB751.9020308@ntp.org>
Date: Mon, 28 Oct 2013 15:13:21 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Magnus Danielson <magnus@rubidium.dyndns.org>, ntpwg@lists.ntp.org,  "tictoc@ietf.org" <tictoc@ietf.org>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com>	<526C30F9.1040400@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com>	<526D165D.3040902@ntp.org>	<74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D1EF0.4070208@rubidium.dyndns.org>
In-Reply-To: <526D1EF0.4070208@rubidium.dyndns.org>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: magnus@rubidium.dyndns.org, ntpwg@lists.ntp.org, tictoc@ietf.org
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 10/27/2013 10:10 AM, Magnus Danielson wrote:
> On 10/27/2013 02:42 PM, Tal Mizrahi wrote:
>> Hi Danny,
>>
>>> That also means that the extension field MUST NOT be added by any intermediate nodes if it does not exist.
>> I am not sure we want to go there, for 2 reasons:
>>
>> 1. Let's not forget that the source and the intermediate node are in fact two modules in the same client/server (see Figure 1 in the draft). From an interoperability perspective it would be exactly the same if the source created the extension field, or the intermediate node did. Why would we mandate a specific implementation detail that would be completely transparent to the network?
>>
>> 2. A clock that receives an NTP message has no way of knowing whether an extension field was added by the source or by an intermediate node, and thus there is no way to enforce (enforce from a security perspective) the requirement you suggested.
> I think this discussion would benefit from separating "interface node"
> from "intermediate node" as these have different roles. The interface
> node would add the output time-stamp of the sending node. If
> intermediate nodes where allowed to add fields, we could have buffer
> compensation in NTP just as in PTP's transparent clock.

I'm not sure that there's a real difference here. From a topological
point of view the interface node and an intermediate node are just a
node in the network. You are just calling it a different name.

> At the same time, as long as there is no authentication on this, any
> intermediate node can create any form of modification that the receiver
> node will accept, malicious or unintentional. Hence, there is only so
> much protection you can create in the semantics.
> 

There's no protection whatsoever here.

Danny

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Oct 28 13:26:16 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC51911E81CE for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 13:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.972
X-Spam-Level: 
X-Spam-Status: No, score=-4.972 tagged_above=-999 required=5 tests=[AWL=1.625, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=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 GqmGshKpvyKV for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 28 Oct 2013 13:26:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 7126611E81D9 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 13:26:05 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4DD8286D9AC for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 28 Oct 2013 20:26:05 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7AED186D33D for <ntpwg@lists.ntp.org>; Mon, 28 Oct 2013 20:25:49 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==013fb014d0b==gdowd@symmetricom.com>) id 1VatNc-000A8j-4y for ntpwg@lists.ntp.org; Mon, 28 Oct 2013 20:25:49 +0000
X-ASG-Debug-ID: 1382991934-05bdbc07004c5950001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id lDZvFzImYoo0mRke (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Oct 2013 13:25:34 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Mon, 28 Oct 2013 13:25:34 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Kevin Stanton <kevin.b.stanton@gmail.com>
Thread-Topic: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
X-ASG-Orig-Subj: RE: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
Thread-Index: AQHO1A+WN7xN4b2hsEWNxkF9hy9LW5oKjoCQ
Date: Mon, 28 Oct 2013 20:25:32 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6853E@SJC-MBX-01.symmetricom.com>
References: <74470498B659FA4687F0B0018C19A89C01B87D7A40A6@IL-MB01.marvell.com> <526C30F9.1040400@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4C6E@IL-MB01.marvell.com> <526D165D.3040902@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4DC7@IL-MB01.marvell.com> <526D671A.7050908@ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D7A4EB8@IL-MB01.marvell.com> <E1Vahsr-000Kke-9c@stenn.ntp.org> <74470498B659FA4687F0B0018C19A89C01B87D8329E8@IL-MB01.marvell.com> <CA++G9tCYC_fmMiXN-Y22EKLYU_hrXGyQGixNnyVjPx01ki1JmQ@mail.gmail.com> <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D832C14@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1382991934
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Barracuda-BRTS-Status: 1
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==013fb014d0b==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-trailer
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7234568623447354531=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============7234568623447354531==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_"

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

Actually, that's not completely correct.  While the NTP standard doesn't ha=
ve any definition of two-step, the reference implementation ntpd includes s=
upport for two-step operation in some modes.  It is called interleaved mode=
.  It still doesn't change any of your points but it is there.

From: ntpwg-bounces+gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bou=
nces+gdowd=3Dsymmetricom.com@lists.ntp.org] On Behalf Of Tal Mizrahi
Sent: Monday, October 28, 2013 11:57 AM
To: Kevin Stanton
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-checksum-tra=
iler

Hi Kevin,

Just to make sure we are on the same page: this thread started out as a thr=
ead about NTP, and specifically about the following draft:
http://tools.ietf.org/html/draft-mizrahi-ntp-checksum-trailer-01

I think the point you suggested is basically a religious discussion of one-=
step vs. two-step clocks in PTP.
The example I referred to in the thread below is a PTP slave as an analogou=
s example to an NTP client. Since NTP is always one-step (no two-step mode =
in NTP), in our context the actual time-of-day has to be maintained in HW.

Please let me know if this makes sense.

Thanks,
Tal.

From: Kevin Stanton [mailto:kevin.b.stanton@gmail.com]
Sent: Monday, October 28, 2013 7:52 PM
To: Tal Mizrahi
Cc: Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-checksum-tra=
iler

This is a somewhat unrelated question, but why not eliminate the servo?

If a software entity is the consumer of PTP time, I wonder if the benefit o=
f avoiding the y=3Dmx+b computation (to compute PTP time from the time of t=
he free-running LAN hardware counter) is worth the trouble of disciplining =
the hardware clock.

In other words, the hardware engine maintains a time reference and software=
 maintains the parameters for translating that time reference to PTP time (=
also for hardware-captured Rx and Tx timestamps).  Of course, this doesn't =
apply to one-step master ports.

Thoughts?

Kevin Stanton.

On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Harlan,

>In the "Figure 1" case "core" packet timestamps come from the kernel and t=
he new packet timestamp will be added by the hardware engine.
>I understand the following question is outside the scope of this document,=
 but how can one determine how well sync'd the internal clock is with the c=
lock in the accurate timestamp engine?
Well, indeed it is strictly an implementation question. For example, in typ=
ical PTP implementations (that I am familiar with) the accurate clock is on=
ly maintained in one place, i.e., in the HW engine. The SW stack includes t=
he servo algorithm; the SW stack regularly computes the necessary offset or=
 frequency adjustments, and whenever necessary sends update commands to the=
 HW engine about these adjustments. Thus, the SW stack does not need to mai=
ntain an additional clock, since all its computations are performed WRT the=
 HW clock.

Thanks,
Tal.


-----Original Message-----
From: Harlan Stenn [mailto:stenn@ntp.org<mailto:stenn@ntp.org>]
Sent: Monday, October 28, 2013 10:09 AM
To: Tal Mizrahi
Cc: mayer@ntp.org<mailto:mayer@ntp.org>; ntpwg@lists.ntp.org<mailto:ntpwg@l=
ists.ntp.org>; tictoc@ietf.org<mailto:tictoc@ietf.org>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer
Just some thoughts, and I hope I'm awake enough to type this...

There seem to be several issues here.

In the "Figure 1" case "core" packet timestamps come from the kernel and th=
e new packet timestamp will be added by the hardware engine.  I understand =
the following question is outside the scope of this document, but how can o=
ne determine how well sync'd the internal clock is with the clock in the ac=
curate timestamp engine?

If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well.  Having said that, =
I'm sure there is something to be learned from implementing Tal's proposal.

H
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc


--_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_
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";}
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:#1F497D;}
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 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 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">Actually, that&#8217;s no=
t completely correct.&nbsp; While the NTP standard doesn&#8217;t have any d=
efinition of two-step, the reference implementation ntpd includes support
 for two-step operation in some modes.&nbsp; It is called interleaved mode.=
&nbsp; It still doesn&#8217;t change any of your points but it is there.<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;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ntpwg-bo=
unces&#43;gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpwg-bounces&#43;g=
dowd=3Dsymmetricom.com@lists.ntp.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, October 28, 2013 11:57 AM<br>
<b>To:</b> Kevin Stanton<br>
<b>Cc:</b> ntpwg@lists.ntp.org; tictoc@ietf.org<br>
<b>Subject:</b> Re: [ntpwg] [TICTOC] New version of draft-mizrahi-ntp-check=
sum-trailer<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">Hi Kevin,<o:p></o:p></spa=
n></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">Just to make sure we are =
on the same page: this thread started out as a thread about NTP, and specif=
ically about the following draft:<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"><a href=3D"http://tools.i=
etf.org/html/draft-mizrahi-ntp-checksum-trailer-01">http://tools.ietf.org/h=
tml/draft-mizrahi-ntp-checksum-trailer-01</a><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">I think the point you sug=
gested is basically a religious discussion of one-step vs. two-step clocks =
in PTP.<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">The example I referred to=
 in the thread below is a PTP slave as an analogous example to an NTP clien=
t. Since NTP is always one-step (no two-step mode in NTP),
 in our context the actual time-of-day has to be maintained in HW.<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">Please let me know if thi=
s makes sense.<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">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<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"><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;"> Kevin St=
anton [mailto:kevin.b.stanton@gmail.com]
<br>
<b>Sent:</b> Monday, October 28, 2013 7:52 PM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> Harlan Stenn; ntpwg@lists.ntp.org; tictoc@ietf.org<br>
<b>Subject:</b> Re: [TICTOC] [ntpwg] New version of draft-mizrahi-ntp-check=
sum-trailer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">This is a somewhat unrelated question, but why not e=
liminate the servo?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If a software entity is the consumer of PTP time, I =
wonder if the benefit of avoiding the y=3Dmx&#43;b computation (to compute =
PTP time from the time of the free-running LAN hardware counter) is worth t=
he trouble of disciplining the hardware
 clock.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, the hardware engine maintains a time=
 reference and software maintains the parameters for translating that time =
reference to PTP time (also for hardware-captured Rx and Tx timestamps). &n=
bsp;Of course, this doesn't apply to one-step
 master ports.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Kevin Stanton.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Oct 28, 2013 at 1:38 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">Hi Harlan,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
&gt;In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps com=
e from the kernel and the new packet timestamp will be added by the hardwar=
e engine.<br>
&gt;I understand the following question is outside the scope of this docume=
nt, but how can one determine how well sync'd the internal clock is with th=
e clock in the accurate timestamp engine?<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">Well, indeed it is strictly an implementation questi=
on. For example, in typical PTP implementations (that I am familiar with) t=
he accurate clock is only maintained in one place, i.e., in the HW engine. =
The SW stack includes the servo algorithm;
 the SW stack regularly computes the necessary offset or frequency adjustme=
nts, and whenever necessary sends update commands to the HW engine about th=
ese adjustments. Thus, the SW stack does not need to maintain an additional=
 clock, since all its computations
 are performed WRT the HW clock.<br>
<br>
Thanks,<br>
Tal.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
<br>
-----Original Message-----<br>
From: Harlan Stenn [mailto:<a href=3D"mailto:stenn@ntp.org" target=3D"_blan=
k">stenn@ntp.org</a>]<br>
Sent: Monday, October 28, 2013 10:09 AM<br>
To: Tal Mizrahi<br>
Cc: <a href=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>; <=
a href=3D"mailto:ntpwg@lists.ntp.org" target=3D"_blank">
ntpwg@lists.ntp.org</a>; <a href=3D"mailto:tictoc@ietf.org" target=3D"_blan=
k">tictoc@ietf.org</a><br>
Subject: Re: [ntpwg] New version of draft-mizrahi-ntp-checksum-trailer<o:p>=
</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Just some thoughts, and I hope I'm awake enough to t=
ype this...<br>
<br>
There seem to be several issues here.<br>
<br>
In the &quot;Figure 1&quot; case &quot;core&quot; packet timestamps come fr=
om the kernel and the new packet timestamp will be added by the hardware en=
gine. &nbsp;I understand the following question is outside the scope of thi=
s document, but how can one determine how well sync'd the
 internal clock is with the clock in the accurate timestamp engine?<br>
<br>
If we have TX and RX hardware timestamping capabilities, we can use NTP's i=
nterleave mode to communicate these timestamps as well. &nbsp;Having said t=
hat, I'm sure there is something to be learned from implementing Tal's prop=
osal.<br>
<br>
H<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_26FBD265CD8D234EAF41115A180F92BB6ED6853ESJCMBX01symmetr_--

--===============7234568623447354531==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============7234568623447354531==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Oct 29 12:25:28 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DE711E822E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 29 Oct 2013 12:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.57
X-Spam-Level: 
X-Spam-Status: No, score=-104.57 tagged_above=-999 required=5 tests=[AWL=2.029, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 C8T9uw9Q+ycq for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 29 Oct 2013 12:25:23 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id EAC8911E819B for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 29 Oct 2013 12:25:22 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 83CD886D77A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 29 Oct 2013 19:25:22 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 6376886D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 19:24:56 +0000 (UTC)
Received: from uillean.fuaim.com ([206.197.161.140]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <brian@innovationslab.net>) id 1VbEuM-000MSw-SI for ntpwg@lists.ntp.org; Tue, 29 Oct 2013 19:24:56 +0000
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 6BC45880A4; Tue, 29 Oct 2013 12:24:49 -0700 (PDT)
Received: from 102527254.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 7EC2B130003; Tue, 29 Oct 2013 12:24:48 -0700 (PDT)
Message-ID: <52700B6A.5040204@innovationslab.net>
Date: Tue, 29 Oct 2013 15:24:26 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>, mills@udel.edu,  jrmii@isc.org, jack.burbank@jhuapl.edu, william.kasch@jhuapl.edu,  ted.lemon@nominum.com, odonoghue@isoc.org
References: <20130517162852.7C5D06210B@rfc-editor.org>
In-Reply-To: <20130517162852.7C5D06210B@rfc-editor.org>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 206.197.161.140
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: brian@innovationslab.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1330172291881926953=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============1330172291881926953==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="bSX93BdEuIl8RgpKL5FKAxQNKb567PwQO"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bSX93BdEuIl8RgpKL5FKAxQNKb567PwQO
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905,
> "Network Time Protocol Version 4: Protocol and Algorithms Specification=
".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D5905&eid=3D3627
>=20
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
>=20
> Section: 7.5
>=20
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header=
 and before the MAC, which is always present when an extension field is p=
resent.
>=20
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header=
 and before the MAC, if a MAC is present. If a MAC is not present, one or=
 more extension fields can be inserted after the header, according to the=
 following rules:
> o If the packet includes a single extension field, the length of the ex=
tension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of t=
he last extension field MUST be at least 28 octets. The length of the oth=
er extension fields in this case MUST be at least 16 octets each.
>=20
>=20
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned wit=
h Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the
sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last
followed by the MAC."

I don't think that changes the intent of your text, but it does leave
that text lacking in clarity saying that a MAC must be added after the
extension if it is not present.

Regards,
Brian


--bSX93BdEuIl8RgpKL5FKAxQNKb567PwQO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJScAtxAAoJEBOZRqCi7goqmikIALh2EZA89RcueTLiAjZKSXys
MICcm5QDn6YfUx6pdpgn80S+If6u6iMlTdjGVfZSpmdtSSsKxWpGEpNC60s/7ZIy
k8BIcSEnYR0pnVBF28NUZLYq+qeIBUoYHv29iMiBQQNYmcUmhUsxK0fs7J24fOr8
QZNJ0VzzrNfHFT8b3MXBH1Ea+VpyOwVkU/8kuyQY235T31wk+WXuxzvBzLTiLyvY
FbcUePT6ypKZHA2vi3fGXpfaIxJYVWUWKz1aXTlYropGCOc271YW27IO1J1psW26
wkhYJxvDRES7Sv4BBtPMUv1D/T3l9x2cpsdETczusPHvrvRV2OTVC9V2zNa23Lo=
=5m2D
-----END PGP SIGNATURE-----

--bSX93BdEuIl8RgpKL5FKAxQNKb567PwQO--

--===============1330172291881926953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============1330172291881926953==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Oct 29 12:58:57 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D25011E8292 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 29 Oct 2013 12:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.298
X-Spam-Level: 
X-Spam-Status: No, score=-5.298 tagged_above=-999 required=5 tests=[AWL=1.301, BAYES_00=-2.599, 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 XXLStqXXe+30 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 29 Oct 2013 12:58:53 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 185F011E8255 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 29 Oct 2013 12:58:53 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id C092A86D55D for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 29 Oct 2013 19:58:39 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4696686D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 19:58:30 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==0140a4e3460==gdowd@symmetricom.com>) id 1VbFQp-000MdR-PD for ntpwg@lists.ntp.org; Tue, 29 Oct 2013 19:58:30 +0000
X-ASG-Debug-ID: 1383076701-05bdbc07004d0e60001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id OiC7fJEg36FAvfQL (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 12:58:21 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 29 Oct 2013 12:58:21 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>, "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>,  "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHA=
Date: Tue, 29 Oct 2013 19:58:20 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net>
In-Reply-To: <52700B6A.5040204@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383076701
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==0140a4e3460==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last followed by the MAC."

I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 04:45:51 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CB821E808D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.66
X-Spam-Level: 
X-Spam-Status: No, score=-104.66 tagged_above=-999 required=5 tests=[AWL=1.939, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 HErwn9kxVoK7 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:45:41 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 96AF511E815A for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 04:45:34 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 80FA686DAE7 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 11:45:34 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 6451786D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 20:22:29 +0000 (UTC)
Received: from uillean.fuaim.com ([206.197.161.140]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <brian@innovationslab.net>) id 1VbFo2-000Mn2-Jf for ntpwg@lists.ntp.org; Tue, 29 Oct 2013 20:22:29 +0000
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 461858809F; Tue, 29 Oct 2013 13:22:21 -0700 (PDT)
Received: from 102527254.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 44891130003; Tue, 29 Oct 2013 13:22:20 -0700 (PDT)
Message-ID: <527018E7.3000406@innovationslab.net>
Date: Tue, 29 Oct 2013 16:21:59 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Danny Mayer <mayer@ntp.org>, Greg Dowd <gdowd@symmetricom.com>,  RFC Errata System <rfc-editor@rfc-editor.org>, "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>,  "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>,  "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
References: <20130517162852.7C5D06210B@rfc-editor.org>	<52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org>
In-Reply-To: <527014D6.20105@ntp.org>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 206.197.161.140
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: brian@innovationslab.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Wed, 30 Oct 2013 11:45:21 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7678806736927357392=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============7678806736927357392==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="vVsNjfapteR8JcqfWajtoiSUbEKwXrPoj"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--vVsNjfapteR8JcqfWajtoiSUbEKwXrPoj
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Danny,
     Having a new document that updates 5905 for this is fine.  The
question that Greg's statement raises is whether this erratum is valid
given it seems to miss details in other sections of the RFC.  Do we need
the erratum if we are going to be publishing a new RFC that specifies
the extension field behavior?  I am assuming that this new document will
be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when
> dealing with the MAC making it clear that it is optional. That document=

> is standards track. Tal did this errata as an additional item.
>=20
> Danny
>=20
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry =
is incomplete and ambiguous.  There are other places in 5905 which call o=
ut MAC and extensions which should also be addressed.  I have a little he=
artburn with the fact that it is using 5906, an informational RFC, as an =
argument for modifying a standards track document.  Also, it is disingenu=
ous to present 5906 as logic for removing MAC requirement.  5906 is entir=
ely predicated on the requirement that a MAC be present whenever extensio=
ns are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relatio=
nship but I think the errata should consider 2 elements, first a complete=
 review of 5905 for MAC/extensions details for consistency, including a b=
etter argument justifying the change, and second, an informal review of f=
uture-proofing the MAC by size since I see that Tal has allocated what ap=
pears to be 4 more bytes than absolutely necessary perhaps as a placehold=
er for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=3Dsymmetricom.com@lists.ntp.org [mailto:ntpw=
g-bounces+gdowd=3Dsymmetricom.com@lists.ntp.org] On Behalf Of Brian Haber=
man
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhu=
apl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.=
org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network =

>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=3D5905&eid=3D3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the head=
er and before the MAC, which is always present when an extension field is=
 present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the head=
er and before the MAC, if a MAC is present. If a MAC is not present, one =
or more extension fields can be inserted after the header, according to t=
he following rules:
>>> o If the packet includes a single extension field, the length of the =
extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of=
 the last extension field MUST be at least 28 octets. The length of the o=
ther extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned w=
ith Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sen=
tence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the las=
t followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave =
that text lacking in clarity saying that a MAC must be added after the ex=
tension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>


--vVsNjfapteR8JcqfWajtoiSUbEKwXrPoj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJScBjtAAoJEBOZRqCi7goqTAYH/1zyHeU5gGAgys0OXIXdfCgp
5DA6IISYMT+d2BIF1Vs4ljLVnBiRWuVwSrYN95DEcQSqaBIhiZnYvwkAOEPPZkgO
m3q1G71kxcB0otGvOWLA4dKiVuIjh3nWh9wJAt9X0pB8rSW8cjKP3eybFYVmCaRv
k62AqAvG6GT1S2bCuutlf8YgG813fG9pGvekCdMtN1wC7dq/jU9Bb3NRUT0yOoEt
daM+HZjIQUhlPSs8DaQ49Tgob8/91XQ+1LNslKBnqfJyqR6hRNBRgec6BQHvPKSF
9LD+EBw5ajsZW6Vvhfn02Dsu0M/cAkxHvHGfhXC5uA+Kfknhpm5f4QEDwGVdnH4=
=cMye
-----END PGP SIGNATURE-----

--vVsNjfapteR8JcqfWajtoiSUbEKwXrPoj--

--===============7678806736927357392==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============7678806736927357392==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 04:46:00 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5070711E81DB for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.515
X-Spam-Level: 
X-Spam-Status: No, score=-5.515 tagged_above=-999 required=5 tests=[AWL=1.084, BAYES_00=-2.599, 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 ADV0rRheWFIK for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:45:51 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 8888F11E8115 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 04:45:41 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 9C8F586DB3D for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 11:45:41 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9A91F86D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 20:18:18 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==0140a4e3460==gdowd@symmetricom.com>) id 1VbFjz-000Mkx-Td for ntpwg@lists.ntp.org; Tue, 29 Oct 2013 20:18:18 +0000
X-ASG-Debug-ID: 1383077889-05bdbc07004d1250001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id l8H7RywYXoYx56g5 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 13:18:09 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 29 Oct 2013 13:18:09 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: "mayer@ntp.org" <mayer@ntp.org>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>,  "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAP//i/Vg
Date: Tue, 29 Oct 2013 20:18:08 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED69367@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org>
In-Reply-To: <527014D6.20105@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383077889
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==0140a4e3460==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Wed, 30 Oct 2013 11:45:38 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

I'd like to see the extension field doc become a working group doc and completed and it can then become the logic for an errata against 5905.  Also, a quick look at the draft shows that a single extension field can be 16 bytes?  That doesn't seem right unless you also constrain the MAC to a minimum above that.  It also disagrees with Tal's errata?

-----Original Message-----
From: Danny Mayer [mailto:mayer@ntp.org] 
Sent: Tuesday, October 29, 2013 1:05 PM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I put into the extension field draft wording to update RFC 5905 when
dealing with the MAC making it clear that it is optional. That document
is standards track. Tal did this errata as an additional item.

Danny

On 10/29/2013 3:58 PM, Greg Dowd wrote:
> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
> 
> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
> 
> 
> -----Original Message-----
> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
> Sent: Tuesday, October 29, 2013 12:24 PM
> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
> Cc: ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
> 
> Hi Tal,
> 
> On 5/17/13 12:28 PM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC5905, "Network 
>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>
>> Section: 7.5
>>
>> Original Text
>> -------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>
>> Corrected Text
>> --------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>
>>
>> Notes
>> -----
>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>
> 
> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
> 
> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
> 
> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
> 
> Regards,
> Brian
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
> 
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 04:46:00 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1EE11E81E8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, 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 22AlzdDflhVh for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:45:54 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 99B8C11E8196 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 04:45:45 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id AFFDD86DAAC for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 11:45:45 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 98FC586D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 20:28:10 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==0140a4e3460==gdowd@symmetricom.com>) id 1VbFtX-000Mo8-4d for ntpwg@lists.ntp.org; Tue, 29 Oct 2013 20:28:10 +0000
X-ASG-Debug-ID: 1383078481-05bdbc07004d13e0001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id js6Q2ylKl6FQXhF5 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 13:28:01 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Tue, 29 Oct 2013 13:28:00 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>,  "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAIAABNmA//+L+DA=
Date: Tue, 29 Oct 2013 20:27:59 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED693E6@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net>
In-Reply-To: <527018E7.3000406@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383078481
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==0140a4e3460==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Wed, 30 Oct 2013 11:45:38 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Actually, that is a great point.  Looking at the extension draft, it should update 5905 and it does nicely cover the ground presented in this errata.  Is that sufficient?


-----Original Message-----
From: Brian Haberman [mailto:brian@innovationslab.net] 
Sent: Tuesday, October 29, 2013 1:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org 
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 04:46:19 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D17111E8115 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, 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 X9hBFKRc5S8X for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:14 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC6A11E8121 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 04:45:55 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 401D186DB42 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 11:45:55 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7190C86D33D for <ntpwg@lists.ntp.org>; Tue, 29 Oct 2013 20:05:13 +0000 (UTC)
Received: from [198.22.153.36] (helo=[10.2.64.81]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VbFXE-000MhF-Om; Tue, 29 Oct 2013 20:05:06 +0000
Message-ID: <527014D6.20105@ntp.org>
Date: Tue, 29 Oct 2013 16:04:38 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Greg Dowd <gdowd@symmetricom.com>,  Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>,  "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>,  "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>,  "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
References: <20130517162852.7C5D06210B@rfc-editor.org>	<52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: gdowd@symmetricom.com, brian@innovationslab.net, rfc-editor@rfc-editor.org, mills@udel.edu, jrmii@isc.org, jack.burbank@jhuapl.edu, william.kasch@jhuapl.edu, ted.lemon@nominum.com, odonoghue@isoc.org, 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)
X-Mailman-Approved-At: Wed, 30 Oct 2013 11:45:52 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

I put into the extension field draft wording to update RFC 5905 when
dealing with the MAC making it clear that it is optional. That document
is standards track. Tal did this errata as an additional item.

Danny

On 10/29/2013 3:58 PM, Greg Dowd wrote:
> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
> 
> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
> 
> 
> -----Original Message-----
> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
> Sent: Tuesday, October 29, 2013 12:24 PM
> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
> Cc: ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
> 
> Hi Tal,
> 
> On 5/17/13 12:28 PM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC5905, "Network 
>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>
>> Section: 7.5
>>
>> Original Text
>> -------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>
>> Corrected Text
>> --------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>
>>
>> Notes
>> -----
>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>
> 
> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
> 
> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
> 
> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
> 
> Regards,
> Brian
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
> 
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 04:46:27 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE47F21E8083 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:26 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSscW6Pa0KYG for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 04:46:21 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 5161C11E8115 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 04:46:21 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 61BD186DABF for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 11:46:21 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 94C1286D33D for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 07:38:01 +0000 (UTC)
Received: from rrzmta1.uni-regensburg.de ([194.94.155.51]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ulrich.Windl@rz.uni-regensburg.de>) id 1VbQLn-0000Id-9I for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 07:38:00 +0000
Received: from rrzmta1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8FCCA2ED9B for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 08:37:51 +0100 (CET)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gwsmtp.uni-regensburg.de", Issuer "Uni Regensburg CA - G01" (not verified)) by rrzmta1.uni-regensburg.de (Postfix) with ESMTPS id 4DB4A36210 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 08:37:51 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Wed, 30 Oct 2013 08:37:05 +0100
Message-Id: <5270C55A020000A100012F2E@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 12.0.2 
Date: Wed, 30 Oct 2013 08:37:46 +0100
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <ntpwg@lists.ntp.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=__PartA794885A.0__="
X-SA-Exim-Connect-IP: 194.94.155.51
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Wed, 30 Oct 2013 11:46:16 +0000
Subject: [ntpwg] Note on rfc1305 mode 6 messages
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__PartA794885A.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

I guess it's the wrong forum, but I discovered some bad specification in =
RFC1305 (or in the current ntpd):
The appendix on mode 6 control messages refers to "00" where in normal =
packets there is the "LI" (leap indicator). I found out that "00" does not =
contain "00" if ntpd (4.2.6p5) restarted. So to me it seems "00" in =
control messages still is the leap indicator. Compare page 50 to page 54. =
I'll attach the two pages as PDF for convenience.

Can anybody confirm? Or is it a bug in the implementation. I found out =
because my own program to query ntpd flagged a "bad packet" after ntpd was =
restarted.

Regards,
Ulrich



--=__PartA794885A.0__=
Content-Type: application/pdf; name="rfc1305.ps-X.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="rfc1305.ps-X.pdf"

JVBERi0xLjYNJeLjz9MNCjQzIDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9GaXJzdCAxNS9M
ZW5ndGggMjA2L04gMy9UeXBlL09ialN0bT4+c3RyZWFtDQpo3qSOywrCMBBFf2W+wDym1QpS8FUX
IhTrrnRR6iCCJKWJUP/eaVxUXQkuMmQyd04OgoQ5zBQkoFHCYiHW9m48aLG/nl2Z8PjIAa6VOND5
Wq9sX8qJhOHE85hrEumJrMTp0ZLI6wu5NGXM0hjrHSg57DLUeDJDr0I/oiBgBkjF2x2HAEPkSM7e
u4ZccLrZrmjrhkDpMN32flf42vPDK57xD6CicM872xTkS5FvMnGi3ldpOvq966H+1EP8Uw+jLz2M
Rz2c/qT3FGAAZ1x06A0KZW5kc3RyZWFtDWVuZG9iag00NCAwIG9iag08PC9GaWx0ZXIvRmxhdGVE
ZWNvZGUvRmlyc3QgNDAvTGVuZ3RoIDQ0MS9OIDYvVHlwZS9PYmpTdG0+PnN0cmVhbQ0KaN6sk11r
2zAUhv/KuWvCsHSko89RAqWl9Kadl7bsIvjCH/LiEezgOoP9+8lxSD1YA4NdSPDqPZbOex5MDhBI
AikC8kDagbSgtACBYL0C6cChh+trfpPG7QkUxi/WqxW/3QiGMC5kmPHbPuRD07V3+RAWd58lChJI
iI6McJ9QXCFeLfk9KP74sf30uNBFXlShqJJShzpRpasTT6ZKnBGFt0KgL/2SpzA2vuZptz/sx85H
8fWQV2nXtMPbRnjFjNBApBlpDxI1c/5dn32pGIqZP+mMr0M5xFsE087FU2LG6FjlmJd0vMUKyvjz
ofixeAj9z67fhiK0y/Fk+LUP/KH5vt3FNfCXxeuub8otfGvaarfkL6N907bdsFpt6BjjFCCLA76P
E+df9qGFOt+9BZ7mfWgHmOqmrrTXcehSTEmsHdUpV3Z+/ziYP956Ryj9PyNEcRHhzI4IK2Nqi1Ql
pqwxUaEuEye1T1BLaWSopC5pROhnCKX7G0KyGowlpo+ITNTmrM++kUzYmT/pGUJSLp4KFpuIVZ4p
pOMtzv4PhPF/GRFOAS4gnOrmCLWekkwIT7kuIfwtwAB8PvI+DQplbmRzdHJlYW0NZW5kb2JqDTQ1
IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9GaXJzdCAxNy9MZW5ndGggNDgwL04gMy9UeXBl
L09ialN0bT4+c3RyZWFtDQpo3pxUWWvCQBD+K/suks2xOaAI1SqFhpZa29qWPqQaakATMWmh/74z
szs5REQlfHvOzM7xZQIhhS+Uq4QStgxDcXVlDZMynRR5ZcV3o/e3l95tuv5Nq2yRWON8USyz/Nt6
zfLrvMzq/STbldVoleyE61ioe5OWi122rYqdsBW8MbXixEjYSlpPP1/V3za1ZjDYNJIW2F1Wq/LD
CUKBkEIpH0bw0Q9gdF1XI4yECj2SwT3Lo/QpqOXBBqN5JXAcAu582xYBSOJee4SnaCOEd0kSThu9
WsesI88zt3iqLehRmugIUnZ8q9f4KgDvccY392PB+Ome9aT2hGwauC7kytezPPMDm5+DQZsW9/PH
h3jUm2WbtOxPi02SX0iM8HxiKE0CcgwCoyJQOpkacO5DsEYOZ0pMKxnHUBMDbDCkiJymoAhaQzkx
3UwWpiXfhWZNpTByTB0mCAIJUhMOznUMOHp+RHF6IIG+tWcuesdnsw4OxMvetXPRJgnaBG1JefXs
E6lBXoKm1gY7e0SJ58Pn8azpH/1hsV5exhXHvqiJyFYLkR2WyE7z6PyMR9CNn+t2rGFoLWLEyQ3j
4E9YM45n9B3X3Fj4NZyRfXzHoKbZ0iNWtpumlOKyT7eIfwEGAGIGZFANCmVuZHN0cmVhbQ1lbmRv
YmoNMSAwIG9iag08PC9NZXRhZGF0YSAyIDAgUi9QYWdlcyAzIDAgUi9UeXBlL0NhdGFsb2c+Pg1l
bmRvYmoNMiAwIG9iag08PC9MZW5ndGggMzk4MC9TdWJ0eXBlL1hNTC9UeXBlL01ldGFkYXRhPj5z
dHJlYW0NCjw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlk
Ij8+Cjx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhN
UCBDb3JlIDQuMi4xLWMwNDMgNTIuMzcyNzI4LCAyMDA5LzAxLzE4LTE1OjA4OjA0ICAgICAgICAi
PgogICA8cmRmOlJERiB4bWxuczpyZGY9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkvMDIvMjItcmRm
LXN5bnRheC1ucyMiPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAg
ICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAgICA8
eG1wOk1vZGlmeURhdGU+MjAxMy0xMC0zMFQwODozNyswMTowMDwveG1wOk1vZGlmeURhdGU+CiAg
ICAgICAgIDx4bXA6Q3JlYXRlRGF0ZT4yMDEzLTEwLTMwVDA4OjM1OjE2KzAxOjAwPC94bXA6Q3Jl
YXRlRGF0ZT4KICAgICAgICAgPHhtcDpNZXRhZGF0YURhdGU+MjAxMy0xMC0zMFQwODozNyswMTow
MDwveG1wOk1ldGFkYXRhRGF0ZT4KICAgICAgICAgPHhtcDpDcmVhdG9yVG9vbD5yZmNjb252ZXJ0
LTMuNjwveG1wOkNyZWF0b3JUb29sPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJk
ZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZGM9Imh0dHA6Ly9w
dXJsLm9yZy9kYy9lbGVtZW50cy8xLjEvIj4KICAgICAgICAgPGRjOmZvcm1hdD5hcHBsaWNhdGlv
bi9wZGY8L2RjOmZvcm1hdD4KICAgICAgICAgPGRjOnRpdGxlPgogICAgICAgICAgICA8cmRmOkFs
dD4KICAgICAgICAgICAgICAgPHJkZjpsaSB4bWw6bGFuZz0ieC1kZWZhdWx0Ij5SRkMgMTMwNTog
TmV0d29yayBUaW1lIFByb3RvY29sIChWZXJzaW9uIDMpIFNwZWNpZmljYXRpb24sIEltcGxlbWVu
dGF0aW9uIGFuZCBBbmFseXNpczwvcmRmOmxpPgogICAgICAgICAgICA8L3JkZjpBbHQ+CiAgICAg
ICAgIDwvZGM6dGl0bGU+CiAgICAgICAgIDxkYzpkZXNjcmlwdGlvbj4KICAgICAgICAgICAgPHJk
ZjpBbHQ+CiAgICAgICAgICAgICAgIDxyZGY6bGkgeG1sOmxhbmc9IngtZGVmYXVsdCI+aXNzdWVk
OiBNYXJjaCAxOTkyLCBOVFBWMywgTlRQLCBzdGF0dXM6IERSQUZUIFNUQU5EQVJELCBwdWJsaWNh
dGlvbi1zdGF0dXM6IERSQUZUIFNUQU5EQVJELCBvYnNvbGV0ZXM6IFJGQyA5NTg7IFJGQyAxMDU5
OyBSRkMgMTExOTwvcmRmOmxpPgogICAgICAgICAgICA8L3JkZjpBbHQ+CiAgICAgICAgIDwvZGM6
ZGVzY3JpcHRpb24+CiAgICAgICAgIDxkYzpjcmVhdG9yPgogICAgICAgICAgICA8cmRmOlNlcT4K
ICAgICAgICAgICAgICAgPHJkZjpsaT5ELiBNaWxsczwvcmRmOmxpPgogICAgICAgICAgICA8L3Jk
ZjpTZXE+CiAgICAgICAgIDwvZGM6Y3JlYXRvcj4KICAgICAgPC9yZGY6RGVzY3JpcHRpb24+CiAg
ICAgIDxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSIiCiAgICAgICAgICAgIHhtbG5zOnhtcE1N
PSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvbW0vIj4KICAgICAgICAgPHhtcE1NOkRvY3Vt
ZW50SUQ+dXVpZDoxNTFlZDVmNi03NTk2LTQ2NzQtYWFjNi01NmI2NmE2MzRlNmQ8L3htcE1NOkRv
Y3VtZW50SUQ+CiAgICAgICAgIDx4bXBNTTpJbnN0YW5jZUlEPnV1aWQ6NWYxYTZhMzQtZjczYy00
ODc3LWI1NzUtNzkwNGQ4ZTg5OWQ3PC94bXBNTTpJbnN0YW5jZUlEPgogICAgICA8L3JkZjpEZXNj
cmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAg
eG1sbnM6cGRmPSJodHRwOi8vbnMuYWRvYmUuY29tL3BkZi8xLjMvIj4KICAgICAgICAgPHBkZjpQ
cm9kdWNlcj5HUEwgR2hvc3RzY3JpcHQgOC42MjwvcGRmOlByb2R1Y2VyPgogICAgICA8L3JkZjpE
ZXNjcmlwdGlvbj4KICAgPC9yZGY6UkRGPgo8L3g6eG1wbWV0YT4KICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAK
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgIAo8P3hwYWNrZXQgZW5kPSJ3Ij8+DQpl
bmRzdHJlYW0NZW5kb2JqDTQgMCBvYmoNPDwvQXV0aG9yKEQuIE1pbGxzKS9DcmVhdGlvbkRhdGUo
RDoyMDEzMTAzMDA4MzUxNiswMScwMCcpL0NyZWF0b3IocmZjY29udmVydC0zLjYpL01vZERhdGUo
RDoyMDEzMTAzMDA4MzcwMCswMScwMCcpL1Byb2R1Y2VyKEdQTCBHaG9zdHNjcmlwdCA4LjYyKS9T
dWJqZWN0KGlzc3VlZDogTWFyY2ggMTk5MiwgTlRQVjMsIE5UUCwgc3RhdHVzOiBEUkFGVCBTVEFO
REFSRCwgcHVibGljYXRpb24tc3RhdHVzOiBEUkFGVCBTVEFOREFSRCwgb2Jzb2xldGVzOiBSRkMg
OTU4OyBSRkMgMTA1OTsgUkZDIDExMTkpL1RpdGxlKFJGQyAxMzA1OiBOZXR3b3JrIFRpbWUgUHJv
dG9jb2wgXChWZXJzaW9uIDNcKSBTcGVjaWZpY2F0aW9uLCBJbXBsZW1lbnRhdGlvbiBhbmQgQW5h
bHlzaXMpPj4NZW5kb2JqDTExIDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggODA1
NT4+c3RyZWFtDQp4nL1dW5fbuJF+71+hR82eWMH9Mvs04yRn8zDOXLyzL36R1bRbG0lsS2p3Jr9+
AQIkQRIF9naJPtmT2ShqfalCoe5V+LIiG7oi/l/xn7vj3Z9/FYKvPl/c/2NXb3+7I6vf3r5r/sPu
4v7DZXe6+3JHmz9axX/sjqsf39+RDWGWCCVW73fu+5St3P+9/3QXfpmuNN0wKelKGLXRVK7eH+/e
uI9W75/v1r/Vx2r13fv/vfvr+7tf/t/Ibxy0pkozBUBTQjaSyxR6Xf1rVz1eX43pILnixEDUUk43
wsostfv69HpiHTDRWnNmIGRhNlrnkauv1el6+ROO1URZoriG4I3YMIDwy9PuAYdNqdYeLwvNiNkQ
mYfeXnAst1YyA7GcUbsxdAwsRIP8/FDhjtvJGdMQu5nQGzGBjjSjYB1RjIIUS7FREMWPVXVGHjNn
ArzNTKuN5XmSP1Y7p0oQZ+3RhbTN72bROSNjytfnart72H48LHbKXBGQZITidLDKcGkpCGs2dAIb
T7lGnjFjUhvojLl2N2qoRdZPp5bP1Z8QJFNGuAVghZgcbsdnHLWKSWs4CMsm9qne7Z7OS5HpzhUS
J+ShSkEg9Sw02Zihel5fHuvTdXuqcKBOigUkw5LyDR/z9uly+ANza2jp1nSOjmYbbQN3yUaYoJNP
9zitrDkREIct3VBv+QfAOhqDM05RlL0dZ3kZHSNHkk/1FSdUUlMK3h3K1Bh6fap21eWyPe9RGlm5
C0QgM0A1d2IAUPwH1skxHHSjqaEbJYf0bi8XDKDzVRV4f6hVwZ9L8OrdHudMGS0KzpTTwRbg7PZa
Ie6Pp9U7zxBvGef+6g5ofd6jgoSiEDHnqvPJhY2kIjzlWadRalh4EV5jE4hZmL1KBLOTsNe5a0cU
nUYrCekGZkVBlE73GxyLGVcWopVTvdEc0MU/IAKCNw3R3jmHkLkI8V/C5f3x8VCh+EwJDBgMXp5U
F29ur9iA1wUDoCwLysb6qT/j4xapig3XykKaSnC5kSNOV4dqh1EYRbfNXVsDkYpisDDMENhbjNmT
HOy1Rto6d3vBWMsjgsiX7Vdczsh5DZaDZ5sxeyhDQLwhEBp0jq0NcXyC97CYAZBEjtF6xiIzcdQp
ZAXJUueNp1fGJ6VwwZVUXgHNuOPSbBSP+vD0CamAnRsO0WjERowB6/Nxu2CysdWBPaITb4FPNnqH
SUpNQOeb0+BIJKS+nrNz6QjqLFsTQGbIRGYjirrAZ1RH7F2jIgunB7SwIFMlDZczgXN+73l1rq6Y
jADhkjV3Dogr7IaMZYgEjbCvvm4PK8dijLZv6DZUgM6amJDtzWHQ9ZULm7dIr8lRx4QAww4zEeUO
fnv547R7ONen+uniTsEnLS44LVm8VdzKya36sMZ6bwbMaFozvVaR8t32cHARFy4mKMaXgtuQtEiI
xYk5E1zB7qJQIeRKL9fjh++8dH+srw+bhXw3SWAVvZwkeTuvhke7/vti4awkNtS8MjQi767zw5mA
zJ+kEwF2gnt5fVJxzhB1LoUQbU6xN0SflovbjQ9nhc3iLnhFbeOzsRQWf0XhBFBXrU2pbIP2xwXN
PI1OcUrmclQ6oYWofFjQuFDOJ1SiVIIRTGoYTYfcQEZif0ZWVLSUDPRmhA5xRkLl9v4eJbSOUKtA
QpXxXv8AsHp9VrYpszNKNOgL64z4RMbiSt3F2gY1akxmr4EwpY0mdaiFgivORAf/NGHwY406UM0Y
A/Ps7r8LycoMpch6BpdO10IcZswGk53QeXo6fqyWKgYypUKRN0MoTpAYVRT09lX0FTKoe2z9nhRy
SsyQkB5N+HtfufAKlx51ZtmCxWzKQ94uR+sJU9BoiHUeGRhJcA0if0SkRmf7FSQH1T6yvuAceGEg
WeaKjuldP56rr6hylVJOoEBEE+OJBNFFiUtlgAkPwdJN7+psiEbU2Nb4us1i90UwBareI7aAXjRv
QsLI6Mp9qYihdagk5IwN0hskzj/jhTy3HCOvL9WXp+q0QzVlFAWqi5846bLAn1B3tMRcbWI+tkcj
Gy98Ptd9wPksxYDC6nBZEyoxRFLuNAPomLmgqckvJGBLaSFKZHDFUobqW7QPEWYoA/WC7zJpbmfm
IC8V0ikrdpZ2TSYZipGdpYJxAZ8qj21wyaneI8IKL7HE4YFBqZQbOxLZHcrHLip6qmBB2n9EOkZO
IQgJHqixQe1lkD9Wh/oZ0RrQtCx57Qf2KTMZ2oUTLr99OiMzKuUe4SakyCnAE+7eUCrBJk4fWfCR
NF2uqDpY0xgMhk6GhXaPBG8xV4xZHgKYmyrBOQeF2ZjXyBwlOv621lAD9gJTM2Hu5QnZvGMdLWDU
JGIHTU7nntEtds6ph6MINbYzvmKMSDaECRUj4HYhS8YGxrm6V5RPVIwMBaWgIC1ZMXZqKqQfU9dv
sUS9s6whDs3IEKZiPOfOCzn2/DrmYt35cteK4hN/4fWV6sYjk4YRBXatqNhImFNH1+qC9MmEVgSs
+gjLJrfUD3UhmSsF2DRDY2NdAoibIKPemIFVLTY9y319wnXKa6fCIbXXRWVUbYxOenNWC0YtsRiR
QC4XtcQe9R7rzW2SJ4RxpRlYGXCatnFyExrP1RU13OE4Sg0DKeU8+HsDSmlQez7fuEcOpDmvHiy8
qNg3l+Py9nBAKgQOqiLfF9/o3ITNpxqR1W3cBKsUBT1AEt3bBHF7WOG8BCIkIWA5jTEa4rP0ijbt
KLhcjVYS7hWPk34DSEybBKGKagoHDdHDzQnv6sf9FVkc8E3boJPLbGw4TYh1lwXXnUgYBds+OYkT
djlqnafgw6UnJMWylNngckrxp32FcxqocC4D7F2bybXxKun+9VYmFNW003uFjqrxvdk5B2X1/FDh
2jJLEYwQNCPKURc+YGdkiVRKgGPYQsYER6qcTivk1Puc/+n7jcZKGHeszr9nBqRSEjO2Nj56edii
9CHhnIFav/OSCBvOaqLsudOJ7jxBF4LQEAr3mL2WcPb8sj/tcNN9pWiGipjpGKDfqjrBjNRwY7OK
TZkJsw9bF1YsaWT9BgM55DbWyM4OZNFYKsixGMlgTiQBl0X4VCQf0erzSIvqRabihooctSi92PC5
MMrCjB7LU498rJEjsjNNANGPyt8ibHMzU8SA+oPz6GWkOutURWuAU9DUxeFgRpY7f6rpzBwAe/28
ws23h2C20AAmJJ8I9rm6f73f+iYsXlEWNEatZeAuEjG8PeGYDXlbH33pGrmFRDrPCkwYUBaaPYb4
ug378IOzUoMRpwznnED7se+lInkXInhvLksotqmQuYgP7Lkjjec6oLIdNV9s/I757iE6pjaK1QHX
xFPsUG1tQ5bNH5FWqRQUMW4bLZ2l+IKqWM2lxZ0aHR9xD43smCozWwenIwuMNA5USg5qDW8SR5dp
/e79Yg3BnBSkGdkR7CsBYLqY01AcTOn0i4oW0lGc8ybrl6UTsYCr8V6ZJkVbD0rwBTmtW8i/cUnH
BK/rMyKob7KcUihwbEmHjpcsoSd0hVBICXevOvd2LMXr7c5bgje7+oSbjSjPYjtDq6DrU+Oyq42a
AOt2SjQu5OD6IKMwqxgYmAjNJ2qp3lX3T2fUWE+5qV5SmvGg2ruzYMXZTzCNjtXvLkDGm/DAcOeq
ek+q7Tdsrw52XY/QCjRzloQJpgR4vX18PPzxn0v5iow0Aws5SpERFzVWg41ULJrzhM6H+rn6Wp2X
2l3mJ1AaA3dTSudyQ36OX+dB0akhTqSyILINCzZTDtePftXIFjObXWz54WE73O1lyRFS2HfIxfhg
nXK4/PPPyJUCZX80jkPnaMUu8SRSGwpvCbKhrDZAjlHHsdo9bE/7yxEj0MWKNJdTZuOSyc5VMwSM
KZ3LOhbjjtqnz5+rC3bhlTOzvuETrBOQ0IuYO+fqcKmeHypMVmy2YUWG1sSU3bhhjdKAst9kA2kr
XEmcOmsAuhXt4sO8ksROOzXLT0B/0bKm6SHl7329e0KWxYu+DBNjLbnGLnjhTPn0+IwzI/lGy9Y1
rXFDP8W2bKvCREGKiGnLnjHsNJRoE7RbNK7MWfY4DZ1FRZt2KTUFIzunoJvOrpS9u+3j9iNun6Mo
jXv6nKLvFMySu7/iMj/FkI6amDvNMhobsJem5agN7fcDPi8avvpF2b4qnaUVGb4SKjQr5BRpsHMJ
rU3Evlw06bcsaujeIodGyjnMUITP4iJzmMUSlx+tJZAkH+t7bMrYKi7h/BOZiFacm14q4OLCwnxe
0EFlYyajWibLHpNjOKyckLrJSg0HPdwJ8ejyeF9pMa7q0Bx6K64W5caE1cG3t+dUcQq2L3MjQ3Ir
B7urnzCTkHPRpCg5E9hSknSaAWwSZ1Ot8HRxIRXOHxW6sLu+i2kSzHqF66gT2lJwqaJQdnyy6/0R
tbe4OIQeN8XdWH7DjIwicEnfhubXkQlHlqrglS6S6InLsKS/IKmGLygySORSEnCFumwLvQmh2Gmn
ouPZRWx+vJXfwvGc7ey1jTlhA0jncKLG18oLgWjoY04BcZO7RGrNwL5pGgerUrzL9nN1WSFXB5YH
eKPH14PeyuObG+1qJ3iz0OrDd8j74kIJuCWexIA8YbUL1C643c+hpuD0HxjCiFidSiXqfrXoWium
p1K1aMxkdEiH5k4VuddKcgLn2G1YTZ/FPW9P7h5hJ8KlIV0Ki0AKkZqNiH3MP24oasqC+SZ8DgBa
353g63A94I1sOFNcaRDWr1EQZkDnO9zoSrJmZIxGScxEJmiv72xxaFK5UElDaDRmGBK0nxc7QEpt
yFd92wOkjIXiTELkWwwa16UD5DFfn6DVy4kLj/maBA01bsltMgg9QRNR4yRoKOPhQgQFkibCtsAU
7Izi5KCqM4Fr3YIEDpW6LV8FFZZi3f4qNAcoQNgw6ZgS+RNKOC01oIVwBAbjn6DhFjQV0cz0mqN8
V8GLaGF/783QyrS1We8EbbuYUmGEBjc1Qfu8GCf9C5hjhYnqlypePKcDQiLr5hevzFIaphlSIv+2
mA3quqBvZYO4V9QWQuNsolRQUbHk1ghIhbmIeeIgHXF3QRZMHpNh2v82Jq/p0eQSXKTa+tR+ZY5s
d1PEBcvv0a1JpXyKc679lU+AUemUuYl7EkKmHJ3HLa5XvhyBs5AHzAEjt6CXxxFDy1kOFlWX9vRy
TuAn/+IwYg743Xtk77rkCnxgi5oQhKcC9XbhOm1oX8weLaJMO1OFYWwiyjiXinBBJLzAgYfp4RyV
fqjnM3a0tdTgzHQo+6e0PlTb+wXrlSTUJQbk3mJqysWicH8bpZMjfUbV8cqVJs5CXJwjEtm3WGxk
4y6c4yOlj1xoYA0BXzb0y9HGbD0eq/s9tiW0sNPZZDjb3hbMHFrc3sDgIt7UwjmDekBFlFJwDS88
ZqKJX1PA+nmxpc5xvj7H2AVXlGnQeGOtKHeaD67iqeBP54D/+y9YK+o0Lpi2bxeGTTXuQgfbdkLm
SEWMgIVRN0vAXifJ6ZjF6z2yiZkqAzYcdZ624RvVxYHtM40P9TNufLH8aEvcRZxgL9hA3O4Qy1KK
HNJMcxbTYmJow0mpfH3IG69owbEPs/NDKtu9vJ+fkGsSZl7CpDJM7KS0yqXcEyrVBGypJ8CcGGfY
ilb0QR1oSkGGqtA3MRCeGpePJUbCLxvp0DeRFZ9D/bw/fV7wXREag+8ckzGt9rMrXFgYkMxSjXjz
Yq4XvW1sTU93yRXhfpm0GSlcxIrwSWk010VLRvTtMUtLZttn28AsJ0H41bjwiG1b+04prTG7ccvr
q/VCyqhoyJzVmegiXKNasauTTLX7Yl2dNKwazt7/5d5m8W8LqRGJuKc0qIHfUnbMztyN9qn3wz2m
ScLfDkXAV3G5kGPFvv5xuXDet8LxG7qVxbfG2i7rLFuRGdzi40UqbBNIqXyscbajyFUdHjm/GVcp
YQxe425Cm1aeq/v6hOwnslTC6xKygUI7xbo9/xM71Vl8rsQ/cqsgdOR7JYxaBj7S519gBQX539UZ
93w009z5QmBXMh37JQnNyBnW8kp7G56lSaV6uY48/5CwHunBBd09SSfe0BqRMAl9ukKDveySTYOV
r9U9TklQDk5FdLkLZTdyvFrTb0K8POBGI5rsCfE78sA6hH9dqHFTsv8bDs/bPy4r5JBE0YegOpqf
Hh/5vm/5USMTs6sJ3Ba3wbpodRghITJL8FB930wwAi+3JDFNPjjMbpAUPc7vE+Xw7gQeU8kpay+r
f2NTnBremK3IRHZqVN8qUe63yOx9FcZr5UF95/fqfNljIjR/tkwaeGCWhsmtHPi7ZtYQWQWxEt51
7FNVbAi+/rD+/d2H7xbzS/1OfTGmNy4u+H5BfRT7wVJKURvpiHdZwM1w1KqgjzJUorYzzOeqBAi8
bKoKJhj3OmtZD3M5liZcxysRVDHQCfbV/cb9T+AezlX1BmfYSk9GK1g9fNxjH432KV4wraLDMExK
6/50rT4vt98wrlPMyRByn0lpjMupjeD9DgjFbRmkRAo4NHdCy8Z3pe0n2F6xuexiwT0+lJBjMXYB
R3ElKDexNpwwecGVoH5Fs+V5FiPqwUHv676BezqUHJ2lDO5XrCsxv7CgXeWYcnnZhQXtMqCb31kX
YUkGv9MV+uRTOjGrv5sUpYsgwQCZTpyW9blCDXKU37xgU5WEbMJxogGjhVnvFO3w+kWR3QIpyLKE
pp8QWfR7GJCzwaU9vdRpgyYYTgCrCjPE2qTLtFDw4nQaixIJJP/wHW5XPBUaLmp1UYyzou0p/lTf
V9+v3i+348LPbjVxcAKK6wqx/rU8sOwcX3FP4RZ8SY6HIaDbEUecioFfPvTDYnaEt9pi10qU/Fna
2osEEefPNlRyR6YAh9h19AQSTO/J7pH73JzBMIXx6hgnJKDek8W/EUUEsRQ0VO0zySludPG8u4VK
GTlhYkKW6pTjq+K0wWb1dxQmV96ZBh1bEcxygnldHZ8u19XD9mvVkPwVtUqVSL+RAd7MEoaHEvw+
6flUrRSyQ477ySW4TkEnIuala4d8clcRaUBTKoyeqChM+NDk0v0rYGAunbDJEW9PK5wrL4y7QeB7
XDyW3BLE189Az+4RaZ0TavWNFtjN7hHxKUBfGE4hl90jwkO/bAqI3CNifFUYdIZE0L4pnh+FwOV0
/fwSmU3q+iHXdmXor0gi/e5o2F3oJKdH7LP0/qkvVItjsZGh9TZTYpdrZKAsDEumaEgj6sMFAW6E
iS9up3hX5Aoa7leGgK2xIgzYZk/y1w/fIfLUs9DSNq13WejfKuQzNcWdodo0GdwsMmZn6FyBn9rw
6EYWGFfgnx2rbB9CSkULu6aKWRelgT1yLCyESAFXu/qIKx4aDrfO+mqaGpHoXw1bqv2ZmZDFTfEw
2SfCjVbg0BIzMnNVo8u38g/SLSc8/qFdI28rPFxyCrqYnIU+jYHwLPlspZ98G0vrwm9D+/4xrseQ
uLyJ0FzMdmtQKTY8Av4Ve4gFqQkdZGyAd0ZKjaTagomhdrN4CugfvV5OTr1D27gjKSIy21Y8Q/8i
iw92B2eIKGIHl700/8BD2jsF/H71G7JSD/ZgeAeajhjqfAHsAnxZeGwmrttJEWtU08d8ytSEMYsh
JKZZfWbXgLsYcig0vd9RY9suiCUKzkaFBzpSSk/1+YhIjczeSSbCANbgTi645E9Gpy6VWOSqSu++
wnXy8MhiitfEXAu6Hja8TjeUn2/kelAxIRe9XpVKBnYKcWYm57lCaoMyhYKMbyfaTJadKwck5De7
IFyFdOG3uiDOmk10TnNBcEkYazScg+5cK555n/on5NPY5YQIiearR14yIRI781O0RRMiNAxjp3jo
hEhpHRCjTRUjf47L5kNEyP5moZfNh8SHnbLIi+ZDdGj5ygIvnA/pfKJEspB7phhjBB6MpGEwe0hr
a0MP2wuyw01TQRT8CN6E0etP2PfjlQVHo5iIUUqCt/18rE7XBZ0UHRZq5Rm8dH4khvI3EqZwoIVn
wnwnHxsSu14hnepi5YazMJaeAh5WqEfqCfVzDmCFVYR1dyngQ3VG5kd8Cgh8eqIz4u6qmjg984/H
6ozbClR8SpaSMICaQCbzDugWOhd+cQsPzoSZryz2W+yDQ8WhLypiFSfhNDJrIn1LPNz9EZPfg5N1
5nyhXkGf0gOPdclRpNC0nZK5ZOu/Ca8MZalctvc/viEwRP4WeypoeJg+SzKu+794YRiLhcHkZF+f
L5pP2zA5JnO9/1q9+bjcFDeToY85y1mcb1Seq5DhHbIBqSjBLU02MxWaSrKCG0YOsE8Wcgp2DbXv
NKS0Xh6r3f7TH8ttBOE8dN5lD3bJAYC45C/LauyStnJvPFciBFQ5aF8C9aOxyzX2CBpeYR4oi6cT
4nUVb185ZQLsCOOTS5To4/qEfP2Dut+Gu9EUyVypKF+/bw9PFe71pxe156esxrTnN56MVQqcdm77
81PAM+aB4Je2zKeAyJb5IoFtb5Gv5XULmRA7WWJkYzjsgoc+hQTwVN2v9qcdbsmX89TgPjgR3iPo
MZPuzfvQPrrcVIIvP3lvOKH4E26jGfHpJXgQ1oYlVAleWGQ2dL87GGdBnXsnV0q5o3F/537DkNW5
uvv0H8AXtWm+6L9W/mL8RfCLLmACoR31hvjOzJWyqvlvj3eMaWdS+08O/Sd+Dar2n3R/1X3ycPc/
q9Or+OyiV2IFeLA21EqUtz9xdSUhHZN/eTmt+S/OsXn8i/AX/ZowmM3tafVsFnLM5vaTns3tXyHZ
3JbgizsKvMJIufz7O5DLBVLzX4xcZuKFzIO/KOF79KU/rJ7Lyo653H7S8bT7q1sIc3GTpX9egY7Y
rCAucyJfxuXui60sE0hGxz8Jf1P4HBXMZ6NHfBY+XTjgc/dJz+f2r24gzYQ5cwCP6AZfNWXzb9WX
p+q0S2wQpKGd//0yDd0ykULCOv5J+JvdwWTAEx0dD/h4xxkPQhw/OfSfOM9npKO7T17PbursPoO3
5oexWSVUz+7r9vp0ARWIfqFod1+MdHIC6YXRL4JfLN0qJ9hyLNgdXzvB7j7pBVveTrAZZwZ+n8CE
hEIq2P94nJNod1EiqYqU5ZSFL/qiT1mi25+Ev9kqkBz4l9R/GCuQ+EmvQPws/lCi+09ezWcqkjft
pqWesJdXWtNV2/+CyJjP9mcwpRonJwXcYnvuGFHwWiBtmgRGCiiUWdW7a7Xc8s3YAJuCLrZ800mR
HGLdKFtdDvU4DyXRlMbj9l9JN+NYFRYcmvwXZ32p0S/CXyxoYacKOR/7UnasCrtPelXY/hVeFTIq
JZidaTvUUk3461+XklznbDQZihTtp1m1y1vNx8tqd16Zjn/yBWo3A96rXWnGarf9JFG73szxgdrt
Pnm9eeOCEHA80b911igI50iw+LbwD0/Xh+qEG8J07NJw76EOLxsloL2m2G2v2F5SZ2igcICTkPhK
6f2wrh+RncGlKojf16tGkPv6tD0g+63LzXnCBKWYgCIbngSTHC7sSznhq1WwDi5536+Mn8Y/+YJI
K+v6dzFT5/p3jlLn+nefdI5+91dI139+UNM5w00RL/X9f7ggB0xK260FneDVO5x2gB8B94KkhmhJ
afSKXS2oiD8gCDsuK04p/ftfEhHu1bnfK9Lm7pj1Krr95NB94kTWepFI4sLuk6XSHe3DqsqR0uXu
BhRwE4S/p6AV5p6CTryVX/XVRGCmTU60nyyVfRQkZh8TCjgdkNCmrpJDMFQMSWg/6f8H9wmvG5BQ
zjnJeGMSEsyQAkNHFHAuRxS0nyQUGPqNDqHtREspoGooR1yOSTB8TEL8JJEjLr8VCZJPDoGJ2VQU
E2V79PIE0/gnX5CKyoB/SZXHOEESP0kSJGQcuPefYPLYklswkOaRz8z0CZJPuK4S5Xxj+F1MESa+
U8BLEkJDnsbcyb7cfxj/5As8jezJdj5Dd7K94iVjT6M7x+6vbnCyVCgFNjL65xTViNFv66fTLKv7
BNQMq9sQaJ7V7U/OszoHnrCaTFhNxqzuc13tX2GzX826vMKrtpyF/QlSmanT8/P2/h614rLJoPhK
LnjQKlRyE3gXFKFnF4udxyZ0MKWQ9WUQL3y5azbZSLqSso2dpQxl0faTQ/eJMM4tts0n8a/6TxCp
YaIM6Bj7Cp5vP5W0T1H8zT/NhmObow3sQPXre33FP4WsVhK5Jc8PmYLaVoadbikicntRcRGpd9J8
vS7BS67CYvNPzrVqqrEpmW9x/T5awkstjJ0cY43rvpGaGdibC2u+sjw9Y96SjoUqDuaXvGbjI77+
hBzbo0o2eV4wWh1dyp5W/HPSTqfxwrJgOVEI/zV83LSJIbX1xkQbQfw/nVazTDYhZPzk0H2itNOT
ISMY/qj/AJEQdDehy7sKYHpBU9m9/fHr397iFhwKbWjXOTVGtN6dE2aASDlBparS/WhjPL/7yV/1
FA/1tqWLt7UAGdoumE/h3qEqPoT5B6UgdrK4/i3B6y/Ac33+5w0GmCDWMhUmvFNa3+9fv6onbAcy
8Fl6te01WwpYrX4+17jsFO3rwWNETsKW9yx7r/UOq00Hj3BPwHlYJJaS+8E/uYHTacYqkFy/DGl0
os1Sbo4e9IbOlNvQ6T0gEpUq97bYAGhCqwlLf9qiJj+aaRcIzrIxPxNTvHtAWidpOIf46muUY75S
a1nONlEasti9bWo/6W2TUe7fqeptU//B63M6znzrbv4Usk1KewJoOKv94YBczeViEVA6rGg2VqWI
P28/I9uIjRSQfEgaXIgU0Dn4ad7ql7v/A+93PjUNCmVuZHN0cmVhbQ1lbmRvYmoNMTIgMCBvYmoN
PDwvUjkgMjUgMCBSPj4NZW5kb2JqDTEzIDAgb2JqDTw8L1I0NDMgMjQgMCBSPj4NZW5kb2JqDTE0
IDAgb2JqDTw8L1IxMCA1IDAgUi9SMTIgNiAwIFIvUjE0IDcgMCBSPj4NZW5kb2JqDTE1IDAgb2Jq
DTw8L0FzY2VudCA3NDEvQ2FwSGVpZ2h0IDc0MS9DaGFyU2V0KC9BL0MvRC9FL0YvRy9IL0kvSy9M
L00vTi9PL1AvUi9TL1QvVS9WL1cvWC9aL2EvYW1wZXJzYW5kL2FzdGVyaXNrL2IvYmFyL2JyYWNl
bGVmdC9icmFjZXJpZ2h0L2JyYWNrZXRsZWZ0L2JyYWNrZXRyaWdodC9jL2NvbG9uL2NvbW1hL2Qv
ZS9laWdodC9lbmRhc2gvZXF1YWwvZXhjbGFtL2YvZml2ZS9mb3VyL2cvZ3JlYXRlci9oL2h5cGhl
bi9pL2ovay9sL2xlc3MvbS9uL25pbmUvbnVtYmVyc2lnbi9vL29uZS9wL3BhcmVubGVmdC9wYXJl
bnJpZ2h0L1wNcGVyaW9kL3BsdXMvcS9yL3Mvc2VtaWNvbG9uL3NldmVuL3NpeC9zbGFzaC9zcGFj
ZS90L3RocmVlL3R3by91L3Yvdy94L3kvei96ZXJvKS9EZXNjZW50IC0yMTgvRmxhZ3MgMzQvRm9u
dEJCb3hbLTE4IC0yMTggOTI5IDc0MV0vRm9udEZpbGUzIDE2IDAgUi9Gb250TmFtZS9MS0NaWVYr
SGVsdmV0aWNhL0l0YWxpY0FuZ2xlIDAvTWlzc2luZ1dpZHRoIDI3OC9TdGVtViAxMDQvVHlwZS9G
b250RGVzY3JpcHRvci9YSGVpZ2h0IDUzOT4+DWVuZG9iag0xNiAwIG9iag08PC9GaWx0ZXIvRmxh
dGVEZWNvZGUvTGVuZ3RoIDUwMzMvTWV0YWRhdGEgMTcgMCBSL1N1YnR5cGUvVHlwZTFDPj5zdHJl
YW0NCnicdVdnWFTX1j7jcIpKESZHRHQGwYKKoBQFEZBeQhMEpYkICCggAlIMGEuaHI1JroUQI4gN
SYyANRTBXoICioYRB3UGdFSMRs1dZ7KH3G+fITe5+fE98MzsvefsfdZ617vWu7aI0BtBiESiUQGp
mQWp+RnJScLMhjcX8RNG8BPFxSj7dydNMTmRCN77xIDTF3P6etUTxu404bON4ScjKBpDiEWiou0V
3mtyinMz0tLzLayjIpZMnznT5u+VOS4uLhYriv/7i4VPal5GWrbFVDwoSM1ck5OVmp3vauGNn87M
zEi2SMsszknPs0hKSUlNEbZFJ2Wmrrbwy8jMyMlZU2Bh7T3dwn727Dmz8Id9aEbWinV5FpFJ2XkW
wRYRqWnrMpNy/7FIEMSiYM/i7OSlIevXpIR656TGhvmsXRnum5vml5ce4Z+fERmwbtXiwILVUYWZ
SdHvF2WtWPLBgjlTS9zsS90drB2nO82ImzvTYp7NpATnWbtdbK3m27nOJohZhCURS4QRPoQLYUvE
EeGEL2FHTCYWEX6EKzGbmEJEEP7EHGIqEUkEENOIxUQg4UBYE1FEEOFITCeiifcJJ2IGsYQIJuYS
S4kQwouYR9gQMUQo4U04E/HERMKEoIkEQkpIiGWEjHiPGEmwxChiLDGaWECYEvqEiBhHGBAjCHfC
jDAk1hDjCSNCjzAnxhATCGMiAgcWT6X41d8QvaJpoiTRblHTCGJE4oiyEa/F74trxR16M/TS9Vr1
NKQ7uZI8QrlQCdQ1mqEL6RfMZMaH6WR+H+k0MnvktpHVIy+P1IxyGZU5avNo89Huo/NGH9XX04/T
36k/aDDKwNag3eCRgdYw0fCE4W2jSKMyo3NGv40JH1M65htjfWN7YyfjJOOPjb83vmESaBJnkmXy
wOSlJEqyVsJJWt4zgVpDvo1TaOhKUa9aDJ6aLNZ2KIuPUSAtZaix46ogVs7PrhTx2bCGvYfWkG8p
tFOTRSJ9CpUPZZG/UD2whoR/yVlUQoE+PCIN+c9QtkLzHt4zjq9i0RStDRrP25D2FPhqq1c7b1hZ
VJrOmX3IlW4v3sEspPdu3vvpfu4wV7Nz/zeH9lXs/+YUlGoMxwlmVfGLutMrTbp63B/C532mkpNd
+EDJ99qqh3CKlnT/+2LX45unkoOl6D99vAWtDLo41S0myytBKjmporEZ+T28TY+oVinmV8Nr9tNz
G78vrElrDq7x4hg0yQ7pIS/kNmABlmB8/x68t0s2jyqdtzzJh2PsFt+DMWB6Xv6k68wKr10yHRAa
H+yROT+KhTIAEokpFI4aUBg0kIik4BMEaLd2FAl4HA+XIA5dIoHGEN4d3nlPxX+lEvPpYyGJB1IL
Kk0WYmmUPmSEMjVGJGKHslQ8UJCsBQFBrps37BbxYdhfrbkXnKXQTa0+uZB370ZyGn7iDfBDbcP+
HVdCm1IMB/njLJpmb4l8kI/KEqbDtIF3sBACHd+imbJt7uyzi+5oLDJa5GZnG9EDEjC5JFfLhEPk
i6v4YDm4V5ocUkIrRrmE34JZ4IwOUOltkUd8MVgT7JEIucokzchXiUQw6U7L4fazUkmJ310areeT
2IFLrshY+NlgkauDXegDMATDaw+eSA01K4e9/1nFS1VizXh8roNWTWmNeTU5VfBYRfEGWhX5DgO1
Ml/BDypETWqxZgbPsdngaCdHjtx0bkFmVFigd5oVh0ZxSL9ucqfPxUV3cp5z4Me9erEfopiZ1JaY
TRkl2VlhIRlu2NwpdsBAEISpgIZJVy4UrzkqO5xbkbk7itH5y8+QY1KdF0h1Tmkq+f48ymYfwiHq
TFRzXgfHgHk/iAB72w0+TjACyXwiVoekYE7dd6cl7bA+mH16dT4yRqND5892WNQLRmB0uVelg7IH
AjrAsUd08rGY3wUbWK7346aShozHrq3TsVlTZ2HKLUQLn0yCaaDf1wFUFaZcvl98WgAXzS07sOZM
4dGPjpa1Mts72K8Gr9x4yDGKG/5OW7mtZVvx8cAp+OsKES/HIGr3u/C2lDZIe5104VsV2iCaD+Cv
koaafcMg1qv5CrWYN9MUsygVWSJbVISKAH/DStX9wy1XZPdvNQLJwWgGPkQymIVWSV30wP5XpI+C
kY8l/rJFdlY4nQMg4C3+spUJodS9v1/NT1CL+8fCMQqCgQQpFEIB0gMpCpGhY5R6yJzlr8NCGib/
PAOFomCP6Wiy7H9w/5NkPfwWDLvkrGa9py8t6bmQEn7UzxxJ5yASZ6X7Y0uQdrccutQgQ7U0mqpx
ZfsxxUyQ/l/8MrimeCozhFpcI/w7wLxbpOoTw26cLo4K6ofKb+u/+pwr2yftpIt2bNy2nmPcExIX
yux9/bu08X18vJIeLm0nFbBTIXqihv5BMXbmOgvF1CXu7N6GH86c2NfI3WJg4vweNFmKzg9lqSne
XA92QjTd3xbn6hodZ68rCwr4XAGlCtEALp7vwyOWn6TQToJSfrZCux3X0UqF1osyhMfYTC8V9r4T
s85UUtcp1LEaoY4dpLl7+5pP1DCSzkP7Dn55eRvziC7d/tG2jVwUt2J1nBsjqXuOa1kbyu4CYyHf
8SE1SjiJT3nAz8bHeNCSwetJS2sCzJHZHMQgd6dq39MxsobEi2svcDe5H4803mRyaM5n8/KC7HWZ
y4uXcqlcxq78b4sqtnz9SS0zl9pp3RMORpycu3Xw2KkTTRU3OTBi8OFB+GBUFMIOtHkgU2Qc5eEw
e7GucFyU9+voWAU//cN1eK1Ar7HrFgptqYDXXxW4UQmbcREO4g3Zsjf+l5EBTgbDBcEzXE6lwJgs
mbzocml1AZdqFhu7ymtZavn+AumGio8rPqljHKgdyKBjEUzEWTnuYftreeJpq4My133+32Tv5+rM
mk7Xdtw6nr14u/RPsbgDHpWirj6sFeIunCVDWX1YJwSVOHx4c0ml9MD6XbncSmZYLVTBF6Z4Lst/
P1YKR2ldoYIfFbBDYaJWAxqYP2gqeQehcIuFj6i+uuQ5MglfFsQt+1dieZYZkNVU+oGPDm0dLAP9
ouMLjjGSd4oT35/rGw8mCzqRlRT16/hioQc7YB3dyh3dUl14sKB8FZfIOCWmWEt1eRpcBQ0KOKww
OaPmNyhw2dXE8CyLLrlAbiGFa+nYmbOQmWfA4cbl0rjWbCU3wID/rzAKbEHcGzGrUvqcWgvWSO8R
cuXsOe/8iPh5vnGI5JApg/JhIpoNMb/cr7t/G5fp6hnkFUzC2vxufkaH6BFOlK8wcZxgsjOa7ON/
W2tBRR/Paq+s3P7FEWkXvfGzDWUfcEzapl11MkCPaUPIxdgWVkJIpegW3jsD73XWVvVRmiy9eZYP
hS4BF53XcpMmVaAaXqr81UJ2q/k9bBlYTe9DC3C0Ha1d0Dj7xsgXuTIIjCMl/U/zTq2MGM+lFCRn
rssuTNgYzi3govaln8r57sMftp3Fgd8WUJ5Yk9zi/zANxJySu13ZeLy5obadu8ENRN60Pozebx4n
6XE4sPrIxfF325tfAtMebbNtWHAEWjZVivqe8aNwDWzCzESP1JosW9ShHQ0duLt5Bo+ElMrvjhH8
Mmnvgx24IhXxBWP5KmfUQkvOWkT6OgYmnbgh5WlnrTXt2B75a0/z4c5mqaTISwAEZd/VTNAh0oWp
Joj0IL1k/fqln3HctvVSH3rX1i/KyjnmWXP9bZnGgIYkPWfLPkqXNBpKIYKvccr8W2POwhaFttMF
PhoyV1O6YiaI5atnYojG9J2FLRWSSIe+COrHQgJfRc6ikLXWDVnwbngIwdoq8r+PCOZcxgGaJKi3
wP3l1INe8EV15BsKrYIXWBIDSQsK5aJcUie3Gmml6JFah1KzICo76ek+YWhkVGL5wXRp2pH1ddwF
ht9pi9eR9W924AkeMOIZTJXyO4cTRjCLPzcWbHVmWWltJuM2bwo1TWtjgQd2FNhg655Rr3m737R2
pI5Hgn8dD8Vgg983bygLswfHocu3m5/dY3JKCeW6OHzXjIVh6+ZPuU/Msz+oOCSDa7TavwWxHsHr
UtKleTmbsrYuYR5SX/1UXyPnmHun1sTI1tFcekFJ4BY0qqT409UbQnMz4zl/RlJkczPst5tt1eev
SL+MPpR3ntvLlW8//BXWYvBnuTVb1ufmZ2Su+CCWY4JSa9su1B3pL5ep9ny740g583fPN2EsfIk7
XmsKLdMOoVX8EDmNggrc+/71yH0czoXwLxZG479dQhc4gkJtvA+0QIuuU/6PliR5ElNPTf8d0LNw
gAUf+FIIqQmKQCYQQdpQ4I12oRBUST6nwAwSwBQlkIPDfeSf3fBDyBH+TSXNOuZhEVHQkgc/X7jW
cf2H1AApGhIWhOm14ymBwpSfSD+Lap3um1QQHivNvJh0wJ/z5RLWLgtmJM136X/2gOf7oBU3RSXn
dfXz3i1a0hx6oi272xykA1jtvcDd6R2Sei/NCU+RQQ0NU1EVqx7uh0L+2Q/97jMMjqZkLIRg/Kwo
NF7bj+bz/Rg/NBcPJ+KhFQVhGMpfKZjHv4AF2heYJ0qU3q5pbReBQY8YarAhCZRfcpyzDLnSnG3R
qvAPGT/6yof7Mjg7Bi85n4jrlP7YXkLFlla04vJCc31rmyMPXTtQdZJ7yuB569cVzdIKzLQHZyGW
5UtRMnmf1krBmZeCkzAUVnQKosEXHdijEsMefjur3a7SxCyiM5GosARNWM8EC02DDqk/ukxaH36m
AM/7h3pNJSv5TaBkt6V9GFeYjsxg3ri3V46d5u4wT/3bbaSSbBsPP4f4fanX3WSS02iMd2rM7PFI
X7EAjJoby6uPS6vKv62or2Mk2dfdSBBRyBBm1l2qusldNUMnB9nQrs17uR+Y1mPHWlvq0mKX5Wa7
Yb0yQ42s5HR45PL8Jebe4Ze7LtaeeHIZN0PlmhhcPa6KX2HI/vC8+rsnju0DEHf92iXia+E3Vlvk
yxdRU/SGvwWPlfypHhHvMiDmP1ey2pHUzsvf1SnPvTo/7pfz57px2b2SdyGpPql+ybcB3BwuYHVK
WG7qxsSt3oyK+rzpy5o91dWnfzzUxjG9VyM8IlfFBafJ7JYg63nLA7ag2WZ8Ji5pSsEkEPWIa1A6
20h1nWjqkwEO49N9xy7tYTrpiD1Fx4QoudJ9yU2+0vigb6iWr0uWyBAOo8uhmItrI3PXxnLODJ4v
KS2JkX4ghJE/DpWsthSSyQU0L0XOWilyEobCio7NUH0PSnpMGlVQPuA3YCrhYS3I2d1U3TZS8m6w
JXGu/eJou5nxTW8+luEWI2LXyr2rj/t3pQ/iNmPqMyWMH0hvmVuDFf/moe9bbo8Hw/ndyBxZebih
mZ9JVdS20zsO7N5f2XDmwAWOkTcmLIwpzkr5QJa3KfPTkDIGN3uCz90PxLARx2EaMg1GQRyawyH7
GyjoFZbnC5QDWMXCAg4cOXBoBjcVWDI6/sH0+3wwxqsXU7AX3FnkrgL3d/ct+eVBNLqnjSBtaWi9
z6JcCnLhBvnnq8D7gViN4X0FpjcgiIM5HNgHQ9A0MGUWUypk1YwlGF+kkEMscnNAlsOXIFDKwU4p
4l1x7HM0Max2BBWtHUs+oE42H9uL/Xp+NchySnjITPf4ht4CjNKeRbvWVK09EXUnsxejZPXqLcwA
C9sXaEJM8oasFbIjEEtCEw6Omc4iR+z5F0hvUn1ROBBZfvYtaTfU123PHfftB+Jo0ZVJqV+AHja/
FqXf0dTfEf2EVetzvAWF/uEJoXcma+rfUMNWXpP3VT2Wi870w2ls6Ce43q0HxqMTEZwb55uaFJzo
V4g9Yzk0+luPU8H1Edcz5cINbvAVyGDcHDWS+C7OWZIq2waeF1+85q5zp1O+9mdwsXJiH7WF29iH
Bc13Cel4orp6TYlb2gebqiC0SwS7usQ4XypZlAzJvigZJfsC/ugCPBVUerjZfInB2ysAl+3ISyjk
hj72Q9bRqJR5RjVAYT8sAUfIYAQfp9X3V4qU78TKt6zV1WKa89tQGL+VSaW7fjj7WAb69F/CD2Ow
Mqbo7t5PqP0oj2yg9kMeiU7ozbN6SP0NF5j0iatxwCH0d08U6v1mqH7yn3B9dxfy5CZ1A0EDUIY/
TCVveHN+JCsZ7D5z4Pit8SB2lGOpMXZwQ+LAA2l3lkklb+anJIe7jUdjX84BC7B4OQDs/eQrLg1S
xMBuvPFeU6JfYGyip2fsmVsdzWfuylCLnuSN6mqk87ywyDlOYZf6+q5exNUeHsNH2LI6aGfRZm/Y
LBgkrPCX8Yr2hjd/408TI+RwvUdUPyAEtA3msnsR87MfEPj+cbv+5I2znZVKDlh8My3+OelGyqWQ
WuFCbz5jGpKhcQO28N6t5gMXfpSVIc/ImVO5EG55Q2kHA+/xq1jFdX87x9AQp7nRV54PXG1/oLsc
vhUp34ohEgNv9VZ4f2EVRHSAVwcIul6sCWHdqXS0lETG1HFYSnpQacLEwB8IKhN5kYjyf02lojTy
ZxzSNBLG/O9kZIclVQte5G8dtpS9P6t73pj6Dq/oXgydb0UwAr981fDL+So9nQ1QW1ilWYpjXSzw
fdPQJvICBZs0m8j/MoV3Fja+E8NqTHZhiyXq/H94I7SwvFwuOj0AdQNiOILZGMiFZa+MTQjJt9Fd
BLb0IgnYwAwFvreVgnTd0/ifpCtbwo8EcIyb3vPGmbjrSEiYNd02/iVEQ3Tj8+cyw/xqvkpoJYOr
KfmovtHyL/T1H+3UNyCI/wM4uVPrDQplbmRzdHJlYW0NZW5kb2JqDTE3IDAgb2JqDTw8L0ZpbHRl
ci9GbGF0ZURlY29kZS9MZW5ndGggNTA0Pj5zdHJlYW0NCkiJrFRLbtswEN3nFEQKlAkSipKcOJZi
ySgcGFnUReE6jbe0NJYJUaJA0Zbsq3XRI/UKpeRP08ItujAXwszovRm+ITn9QV2wKAWN5pDwPMA/
vn3HiMcBfr0f2+NiCEv+vFXwZftpGm3TyIvxILzoD1gs50BqVpAFFxpUiaCMgsvh5OPosgHUfp0V
GWiG6kzkpV8HuKX4xm7CFKMWotMAz8afkZZSpFwj1/IshzidW7RQLINKqhQ5VheblCpe+JOn0T6h
8QK81LrwKa2qyqo6llQJdTzPo7ZLXZcYBCk3uWY1yct3eM/jsyMtL612T1YkM8pn1LFseij0ZOQo
Xmguc9T4bC5XOsDd+27nzukBeejZMXEc8IhtFnF6sXvHvAev110cKhl1p0uZru1r9Q3Gn3ItIGyr
fhB6ZwjeJPEFy5MA1ySGBVsJjcNnEGvQPGJ9uoOFO6Ml0jfZ6B8iziprwpOlLv8tTrWYvcYdwR8z
lUIcTtUK2s3+Hn4DfClZAlNQWfmffRnKYtNWRFcvk9frm5vbX5HmSqD55vAHmR7wJEfvWVY8GmcN
QpqbmutHNDQMIXiEErEpliVicQxxQ/3KBKRoxAUvCrlGV8Nr5Nq2Q8zH/dtJnJBy4lDo/lY35vHN
hBfoTOt8ifrHQQG5mQ6VGQM/BRgA2cRIWQ0KZW5kc3RyZWFtDWVuZG9iag0xOCAwIG9iag08PC9B
c2NlbnQgNzI3L0NhcEhlaWdodCA2NzYvQ2hhclNldCgvQS9CL0MvRC9FL0YvRy9IL0kvSi9LL0wv
TS9OL08vUC9RL1IvUy9UL1UvVi9XL1gvWS9aL2EvYW1wZXJzYW5kL2FzY2lpY2lyY3VtL2FzY2lp
dGlsZGUvYXQvYi9iYXIvYnJhY2tldGxlZnQvYnJhY2tldHJpZ2h0L2MvY29sb24vY29tbWEvZC9k
b2xsYXIvZS9laWdodC9lbmRhc2gvZXF1YWwvZXhjbGFtL2YvZml2ZS9mb3VyL2cvZ3JlYXRlci9o
L2h5cGhlbi9pL2ovay9sL2xlc3MvbS9uL25pbmUvby9vbmUvcC9wYXJlbmxlZnQvcGFyZW5yaWdo
dC9cDXBlcmNlbnQvcGVyaW9kL3BsdXMvcS9xdW90ZWRibGxlZnQvcXVvdGVkYmxyaWdodC9xdW90
ZXJpZ2h0L3Ivcy9zZW1pY29sb24vc2V2ZW4vc2l4L3NsYXNoL3NwYWNlL3QvdGhyZWUvdHdvL3Uv
di93L3gveS96L3plcm8pL0Rlc2NlbnQgLTIxOC9GbGFncyAzNC9Gb250QkJveFstNzAgLTIxOCA5
MzIgNzI3XS9Gb250RmlsZTMgMTkgMCBSL0ZvbnROYW1lL05YUU9MQytUaW1lcy1Sb21hbi9JdGFs
aWNBbmdsZSAwL01pc3NpbmdXaWR0aCAyNTAvU3RlbVYgMTExL1R5cGUvRm9udERlc2NyaXB0b3Iv
WEhlaWdodCA0NjE+Pg1lbmRvYmoNMTkgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0
aCA4NDQwL01ldGFkYXRhIDIwIDAgUi9TdWJ0eXBlL1R5cGUxQz4+c3RyZWFtDQp4nJV5CVgTV//u
xJiZaau2kk5NUBNqa7V1t1rBfcEdFRCRRQSUsEPYSUISEiBshzUsgQBh3/d9Edxx3+qu1apdbWsX
vy5n6KH33hO83/f97/16n+f+n4clkJkzM+/v/b2/9z3hEJMnERwOZ4pTQIgkcpGjNMQ71Pz3QnYm
h501iZ3N3YpC/7QeC+LNJuzKuFPBFC6YMrli1ly1BXt5Oit4E468RXA5nM7Lj7dIw+QRAX7+UVbz
Dzge/HDBgoX//s8yGxsbqyPyf75jZSuJDPALtfoAv4iRBEvDQiShUWustuCjg4MDjlr5BcvD/COt
vH18JD7m05y9gyVBVtsCggPCwqQxVvO3fGi1fOnSZYvwj+VrrPZGh0gipAutAkJ9A0IDouRW3qE+
VvtCJH7eViHePhLzArYhAVERcqsVSwNC/3X23oCQI9GRVhOPbLVXamNlZ+Uo8YsO9o74z3cIgnC1
2yQPPeqyZ7NC6uO6d0uYxG2fbbiv/dYIP4dtkf6O26MC9u+IDnTaGRN0YFdssLfzblnIkYNrl32g
XLdcn7f+4/nqFR9uXJnv/skCq1UL3/WwXlR42Gbx6iXvr1k6lyAWEXMIN2IfYUvYEIuJ9wh3wp7Y
SqwmlhDvEw7ENmINsZSYSzgS24llxAfEfmIHsZyYRzgRO4mPifnEAWIXsYL4kHAmdhMriY+Ig4Qd
8QmxgHAh9hCbiVXEQsKV2EtsIayJ2YQFQREehIjgEzQRQIiJt4nXCE+CIV4n3iXeIWKJtcQMYgrB
IQTEVGISsZ4QEtMIKbGBsCTeJGYSbxE8YhYxnSAJN8waYjK+6WOcNZzWSbxJ9dy3uUPcvybvnHyO
t5rXSM4hqygOtZs6T2+ih19757XM12e9HveG6xs/Tjk05fepQVP/mAamff7msjdvvLXtre7ps6YH
TK+x4FoY+a/zHfnfvP3e22eYmUzTOyve+WrGxhmXZ3wjWCh4LhgXWgrDhJWWtOVcy1bLn2Z+NNNz
ZsUs31mfz7adHTr7sWiSiCdaJjoiqhZdEe8Te4pDxTlWhJXAao+Vj9Wf7+54t3FONsyaxkJgknWx
v5gsfno5gx/Gfgo3MwqJKkqp8PdxklsDege5WZ3bJmZDKHCzuPhhDm1CbTLqjq5IBbbS4/YUvwNs
VSk3J9MyCp/eRh6Dm3nTxnyBCbr2sO+Wc8acTczhLG2B/x2UyV4RxJLIZzx+N/ogPs49TSiDbibK
Pbao3pBVnFMkHoSv8aCR7FlgCNOHA5UQRCgSndNpGcyjxtWwgIEUrIc0qudNY1NR6Ev2mJHDSlln
Bs1Uks0lCXEp6brUJPFHqAFRMFdXnFIECoWgzKjvy6SN6IiKqk0p1eQpIInSBVmJxpB61xI/oBQC
ZZSdIkQVHi1TAR1IyNTmyPSKbAWgo2JjIwObI3qvHTsD3z8lhovZhUXNhQXVWUJ8fWBkLU9zPnsC
bZ9wS9g5TG5WQUYhoOvzlW5ilEEBR43KJYVWQn8j5ZKtNIB2GrZSxwYqDS2AHq4O3ilGEgrYqRWu
5oN8jJRbTrwBDNNQTn3neWaTR7Bi93bRQyop000eoHGKw1e0195ieQ2cmvtcdg5cyrhv9Yt0BPTS
3Z9B6h+nbz5qL9L4Fohzo/OkZfIKIKytNFWd2Tq0ys0l1u+I2NVTuh2spdE7DxdD7kB3SVO7qK7a
VNd4jp4olaxibJLJgl8xZjf2EYMSZOSptJIkEAWUGnmoH+IhkcD73N6nkX2gUgjKjXktGfUZAhM6
LaOupJYpf0RiyEErBGgZOrD83eQUlxRcVpWJcsiW54EqYDTWdAzCN+B8wffIqsWtLAAjzvcC8jht
QDrNr0gBmvR4c4lHTJRzrrLAaxQ5wToB/ADuuvKg3HA5Wzjtz6nANDbZxIGcfrbsJXfsE/ZTZtyV
Atbx6rWYdrDFRG3OURWDmzRrj0laVHQnF5PUnULh45kojs3kITcZ+Ti5KB5spsc/osD7Kpm1Dp8X
b6LWZyuqwC80O4+C2eNDvGJy2tgSDEcH7O2Ghg6ZyQLyXsLkl6shNYPfVorBkVFPkg0asMnMfLBJ
rbZONfNeAr8gH4CbFR2t7c3lA+AY6Jd3BzeE1IUZdpWcKKooqK6g+W01lcaOHks4efko2iSyQV8x
L8BgcruS5kvORtYdtbMEB2J8jkYFyY8k7gS0myq/WQx7JmM68D+p0OcbRf0kpC64L1/n7LlIjMkA
GlnLRg77CZzJyLO1rro4tUKoUgQkuAAaiUhYyX7IM6KfqVT0Oq+MzL9tNJ4HNBSRyDT+IU/JTqUw
g7X17PJ6TsPXsPhrLsxivRj0ztIFSIRmPv8AWkCLH36HIjhjyffobbFayjw5twDNRrzD2zf6+FZ3
x4ilJ+I+xYh/P3Txpsi81gnWsp5T9wzGPuHCF1oGzjvBK6Hk6WkgFdB+iYWDYvYylZzprvDX7lYI
46i8jFyQB+iOfO0RMVpKSZrDCo/iO6cWY7bNQW/fXQEnneksH2oV76YgZzJISorXauSxEdpQQFs7
fQbfhLzhO/dODh9yFk8QeIIe1zE39psJLJWRJ9JLE0Ek0CbHJyjReyhGgObDCE2JrnRCEYrzmzOz
QQEozMBEaZFRx9KKVT+jd+EM5CRAmymwQqtdmoIZcs5ELc9UGcA9GjpTcD6MufBlbeVxTMkxX02F
1nxVCzMpP+6fwR9gWQ3DVlHgfEGHqai4oDi7MxsvHi+jOlOLU4wJ5ap8P7CHRl9T4wwr46ENMrIP
FCd2H6LH91B82d+RchaFV92LaYlJqepnrSugTTcH6x93jMCalwBjeDGkLiYuPhYkAGWWMtetxDXv
ELAB1sF7nLbukSwGaBJY3LjyuOP5Xd9KfgKQB34avPCIlpdtst0ZYg2EdmB/uVen03Dw1wByabjz
OXwNzj17IuZot6g5yCg17aLNMhtSqiiDDs3stPMWd5/A6Gcz+Mp8djaTn6EH+YBu1WsPicf9Kf4w
OKjR2OtoBcVXwuQycmOGuhBcouEyqi2wWtuLyff6t3AynAvf2vrVR/s9Iw54iu9TuswDMf5qJ4UQ
frSRaTzTPnhneAOiEddt45ZDju2NIrPo3YChzZBq57ALoTXjvsErdDdwBF4NoWflnUktaRdoeIFM
vKJtiGgOafeoOAhcwSG5JODQkTBbYIM74dZKSH1/9xwkekXoAVzIFD5o7bgALoBqadEK2jz8OtnP
OznsTWjLKPZrY2KjIyM8VVhWUQHJ2rK/84zjVVQs2sCrJfOH88pLK6oaBoqv4ocJJ8d3jv+OO+kC
VQ1tzQNP1c7+j3ZOKyTZ9ZDkwr/GrBm0H81C7yOPRc1LTzmIR+2+8vkSn+oKZ0Er6PFT6FOn82K7
G6vaF+AOmTwIBuXtQafcmhYB9AawV2+LPZgQoYiIivL3Pyx3Bh7gcJl/08HBwF9wrcDL+he9Q3RX
33DlafC/FbyDfWrWq19fsiTkzOCX/go5DNgSr94wMZiDYQcJafBby8UzV851fAVegK9DHjid3n4D
cdrRbEDzS1GVjHyYlJ+Ape1lC8MPbirM63l2JS7gmOjBgZ6VABEAvX5k1epDLqEO8SsAfTQe69Mr
ekDHC6xFfWS5RfUzGPdkBv8RHGfXMfwXdR4h+T4z0fQFaDIGweLq8u9GT9ce6xcjrJz75UrbZFoB
NcWUkyExD/TS/Efs9xpqM/qcAZEpam1itCwwPhgEg7CC2PKghpgr4CrNfwFfP3nn6cWmwB2iafAZ
HsDzmjn/wHpz0WwB3oQ0OWpq6qwo1oaWiUrCDdpSQFeZyqraPWv37XEO8wgXh3sm+qWvoW2CHqNr
JNisid9inr1FRsomS1MI7tLwGpyGhfEk9i6V3XDEjOfPL2GcGc8X8DDsZ2rTStNrwQNwqqCv+nxz
+wVwFfSqOsMajvavqF+EUXyESmXkncQCLdhCj2+lwKpE7YakVxNqbZayGNym2ZjJGBm9vg7OvHjo
/Y/sXREVq8rIjBK9MmIdsK/nbjlc2Sl75cci2O/gOkZKuiLCKxK9B+gw0g145yTpk7PSCkEpDQFc
TD0GRnWRNV0FlVFk0pEUpUalVkgTD2ESL4YRJF9Rn5tbJ4IzSSwAlcrSZXQNye9Lhe/xxuvxzf7L
x/3bxSnYDnICX/jzj5x7T7h61pIpzsrPMAC6Jj/OU4yyKOCalLQ7HoOXZKS2ZymM4CwNo6nmvpG6
3PxkbaGoRFWoKwJ0tbG0viWmPMA7NMrWTfwtHgDO0X5qe5lwwr+dhZdqYGBXTr1F/aehn8Ot9+vq
ZvARG8gKmK71VCzWtFh9dJ4grCAsJxyDCxdv2rLUrk5yNVAsk8sVuuTAUHUsiAUxhvieWJqPbA+G
BfpaOj/w/P7ug9reE6LOptJm0AkuHurdlIWYXIFzZkQ+KAHlLW11efnp+vQsYEorSs8FHaDb2FTX
Um9sAyOgIblK1UyjpHFLpiXpM90woL9pUfs5bPBBvI8dGvqr9EW9I2I+zIHPmXP1bYNNtYqQElGZ
v8ED+ND7Q/099nlf+UGEOxJtLRvr/rccjDmgjxlEZq3pX/3b9aL20sHuO1c7v5mQXQ80C76PleKV
Vnh+2Ghzbreoy7s59mbkkJPg+lo41Qt+DIxYbPG0yiXR12OjTB8YlLUFn3JvXgAQD8wPnXvUw/fI
wSgn4A48S/2anYeCfgbwNfBDw489gz39QxWjWCUmaH3h/2DXb2wkjGMwbaj4NXLlGkyYuZgw9Tlm
usz6r3R58X/TBXPbWjOhLWZur8/G7usWDUPhXOoRKFUaVuPLCbWVcRXssnJ1pcXxi9DmU6xJ8Dq8
xvAXpsBZPA2ZlpaQlJ6eAoQ6oM3U5GAJyouOzg6fudbRZcv+5qNP3cWjgW2xpZEgWOgZJHUJCC6q
lIliahKq1GfpOJJvh5YWUfqC7EwDRqY4rUqHF9DV16WUzbx/efTTkciWfe1iRFyWlihrQJ2wu6l+
8GxjwPIq0SvnPvMU5/YTuBdrxzL4A9M72FjaBeiRGr+tYuRGge1atYPulXU/UKDLAzdo6E795n1q
tb135D4PETxLJWcFxEck7o8ThiXy4qjsjCyQA+i+vEQv8XgQ7iRdgkMiPj/YSDnkag34/Albyf7D
rCgvX0K1WVEGxuaZGElWbEFoKzoCcwXXihoNLXXNtaZeMAT61B3hDTT/fo/EunbRTP4AapCRdxML
NMD2Ffba+I1ms9CIsc9RF5mxd6XOZMIEdIEHV5Lj7uwzhn+/vjCvG04f9VrkGuPtJxN5hPvrFqSZ
x4WqG14qg9wK+FE3pxkz1OoFd8wV/sGgPDnZl2pINSQaE3KjgBeNPqGC9oZtQavmQRLu/a7+m/5h
Uf/wxbrr4AwYlnX5NUpLwmr20lVkIvTjRZM6mVwVA7QgLkuuP2z0yDuMGXUIu695yOvDuo1n7MXX
tv0ggZPAMwCnt3W30dCTAucMRaM59DTYhB3klGbOp7gkeVjOP8BqXpCepRMlJegSkrQSJy/3uBRN
ki4JJIPUjLSsNPokOkWuavQ6N9xZfaJFpC6MiVBoo4HQV1l3SQy7fqHwkrjQl15yvsdLbjG72yVO
PCU2nobMoox8IKyekDIlBbZoNdvMc0BrpHbmJBaYwYSUC4xhwqKipNLKqPqGqsqG+qiqUDzvTqor
YtrYPRVwQY/FzWdQ9csM/jC7H4/6GDIlSqNR4IfHyTHPt9g3Lwh4AU9FYKh/sNwbHARr+vfDyfa3
JCeO1Ejy1TkxIJLmK3e4emxebncaTnMVRZH84Ubkz6skM0yGYiPA6p5iSupUdid2Y89AffXwH4+d
riDBTfGcUe9+cIo+3dt5caBX5tcmagoqDi+xx236KnUP98MOE+ePl/DMSy6UQMRg6wpuFRbe12M7
2iSj7icVav45nrTx68wt3GSiNuZiGt2k4RF4Bh38u3fM0eo/V0HOE0FilGVKVcUWN5/AbU/MVjhy
hEkmPTTY9cMfKP59tFxBXkw1aIErjeIpIE1WqTRh0cHxIYD2CWrtFfMH4EP0gYo6llqsBB40yqHW
HnO53dFVUlcn6uvjWVPZaSPl7YXHi4W4qOyDlzgJ4poeYD2Y5Cz7KInaXo4TRU6GMdOYUQCEVfkK
3IZvUmBDaoQmVqdVJaqAEmj1igp5lSo/Dsd6uSI6qDvqFJx07h6cI3YZ2/B3pcbjmP2xlwP1GEb9
GMGMp1LgE43G2gzLgImyyVYVmed53ikKkqBSXoUm0dWkDq7njV8gdWg9r5qshpwqE5yMtRcP01cR
hcKLUWZntlEdvyr1Veq1yYqbcAYY4NvFRU/MqWFERj19FTMxuux2I4cNN1scsZJsTjVqgQxo07Qp
2vnIIJgL83XFqcUgH6eaQn1bFm1ELkqqM02vHXwfTkHdgkxdVlJWYq48NzEX5AJ9kbEDvg3vCBqu
5+obs+hXamhTzHmMx/wYl8GdgSGkWwrU7uLxGAocTE3dYh7zaiMVm3E0E1uYNiG0o6AV2peVkpma
mZqVKszTZulAMp2QoIsXyZQw1Eh6ZgWbvI+jRdBZ0FB38+rFwYY8oTG7OBMbsjwj8lKRXemFKUAF
EhNUqnicKqcJWGsqJVMSH5roECcMSZyw0/3smInz60v4Vz+XhayBAS8NJY8LMDhKGfVAVxIN5tEI
x63tSZK4kDD33cEbgS1wqw4bkjcndZiDx+0Jvn5m5mu7jHqow3zdTKMrFNr0yAauh5y7bde7RNW9
+YPgvnlaqTrZ/4kLZIsL1MSOMOB2YeEj8zZCt4x6/Orc8aPU4fiYcJUuryZJpG2LK8GmJCw6Ksy7
J2QUEhduwenmLDpRreu4WkqqNakgCSiAUhepCVuGIgSrYJRiEABQJASVhfohPa6Vp5LqSDFoyg/o
ZXpZrnwpchfMh8UpBWkFoEAIKgx5rdn4qB1KqiotT1vpAmei7wWGkDxVLp43eUWGWpyokgTfIE2x
b7YuFwj1ICe/pBvH9p8EZb1ZOeX4Eq90kPPjE64J1zeXLMwwZODg3VygwrktnAIHVGq7ZFxhjZGy
y44vAKdp9jtci4MKiXabYmLXaZQVVFt0fLntS/jeoxn85+zeq4xCFZ+sxI2UVNwvhlguTiQ3KKuj
271M9tin3V+0yc0uqjy2qrqivDI7PSddL07LT88DerquubJ7uC70gGgvhRbvUSR6SWj+8+hYVUCg
pV2/54X+nooTF0Q5B8tiekArfvi2ThotwXkgODkhJj5SJU2IAbS/tLVPnI3HRk87nNpPTwTxsakm
ztgec/D3lpGnU8s0QAriksLiQ9C8ca4ALYDfBN5OrAJGITAVF5iDf2FGsTn4m2TUMA7+fcth+vig
wEjCCHa05WFh4bEs4b83Fd56yWWXjc1gDOkFIBs0phkSseWMjgpxckFb0UoB9Kb+RZUOMzEN6n/O
aM2r3ak2E7XOvLV3m4b7qNqK3+fc23jKFkQKgUqVJE1PBhowsf01aqIOZqgKlr5AKpglgI7Q/vqV
krzrOUITMlKv2tTayIFN70APIxkMYkuC+9Hb0EXwOZxiqmssac4QGtFyJdWYVqDDnRUfHx0RnKyL
l6tjVeUCaa+8FRSB4iJ9Ywam01FlPtUIStRNh75D7wsQiWxCjmiTAlOFSjjXSEnjc4py9caicvFD
+OY3yCpbl6kDOiGQJ6UEmt2DCd/J7BOcZ0+gnfmLa2LnMEVZeea9z9r8OHcxyjWTSrk/HZMqwkg5
ZyoLQRcN2yiQmVeg19dU9ZW2Abq/0h97rRCcBDUaR/P0jTJSjhnKUnCRhjlUY19L2SCgz5aFWYuR
HwUcExMdkvBBUiMVnhmSqS4DXUJ4hIKv+5xf7+AS7nBAJD8bUHcAeAKpytqOvkslZbrIAjROSnPQ
0Dazb1zi3HgCY7/kwkVj65jkTG9lWOIhtTDUbN5yM7KBHtDd+Qne4vESKvhp4GdQ8BJOgu/BNzd8
N2+vg59brMh5ctdQ+4kHI+vQNMR1321z8HBVjWjan7avyPentZl8bjLyeDImXxiI0YVrpWg6+laA
BPC7tJyEyvQsYUKFzoSnenVVwSkz+cpl1Nn0goTWNS02AivUht5npySVpUxsT1UW649n4UPSZNTx
ZKO8YxE8MN5q5udidg1cMb6GZySfwuKCesiBQ6YThfknC7CAXWBbtMwtatwa7mfxNw+/zEEK3s5X
3OHAgGdc2G/ek9ixlKeiDDmF2dmZZfrSbKz2FfnKILF5QzUwMSouQZmgSvU2F6/BSK3NiCsAx2j2
BYXrrj7BTqqAoc2c3m+vP4TLTnLH3Nn1DAqOIUeSi7UgBHiFHdj9yf4bQcc9n11vrimtb6qoKmoD
LfTN/SNrV27fvlKSF1S3USSJfneviy1YJVx4xfH3R+drrt4VXdo1HD4KLoOzvY03lYWCoKPRaj+w
Hxxs8rjQf66mo+lU7aCguqfcMJJLj1sWMiGXtJ1ggD7W1Do42Orntt/fy8ZTtG0zcx6RbU5nt9of
OoodF73V/vL9y019X5wRT4OHVBVjs8s5165yr6mYq2PbdpIYMDjlKrS8ymGb2HeY8YydbAaJLCe/
emHG7B5bdYcDv3nGZaVwNqPO8XVUJxwGQpRIwrXQ9qvnXffAA+HPq++/53Qw+qivKChAGaSwrUgW
dP/Y3nwD0E/OOq5a57F41XIx2oYcePGsJVbiZ7+zW5lrLQMXwHl6xL/rsH9kVEBQlaw9V5+RkSvS
ZwKQgUdkri4xUOp3wNe8zdsHxc+hmAuX4NLtCDy8F+yjXdokA23VVa3NUSY/HY5Q2COnAZAO6ERd
bl5LffupDjGMNP03jsZY1GsZNgcqeFcxa/CvLRRrjfaP42/zJy3s+HkLeOuh5NYM/km4CH7OnANV
adUJNL/iYnSX4zbLVY67NoXF6qt9RSFlCr35cxOlKsa/L/rT+w9re4bEQz21o+AaOB43FNoUWykz
eJpo/skbQzUdpywf7T6zxNVTEeQnCglThkfvM6YIem4PtFwC9JUBTzs/pV9EhDgkRKrcHmn2UMcw
hY9hHDa5h4T7etiu8J8H0GsA8Ts+/HJuj3tt9IkgQ4lgzSVpW9jdyGuae+Bn8FvR47qL9Rcb22+N
4hbpZJ3gGSbcRxEfDGJATI4if/kQDirAAwTHeOw+FSSo7So1NIEKUJFcmvDVobKkATAImioGL0/Y
pAr4wWV2XTkHDt7nssE4N89lHTxJdG3cgbcbtqI19+GalxTacZlBSSRMgj/w8B1D92fcTrSVuXOs
sbZj8OYXbROxHL7t++Ljl0eOhVcebI6PE3xmV+dfv7F6R+EGMA+8p7YO2yu1C/Hb4kBP+3ORqgu+
0ccebuJA+gmcepOd2s0ds73NrPN3Ue/A4Wo9mgbfgpuft3939px4ePha3W2cFZbBd9Cb6MN5dh/t
DFcbm/QZORm54itQz9tGaiXRPcpCfyD0Av5xAQHOzsEbsLGx63Ib7h+qG2gV5Xp2hB4D9E9PIRcy
0Aa9B99Ge5An+gQtQQeRE1yB5sOjn44U9b8Qo3WsDVOfZoxM80lzV9iHH5L5hUaHAdo3quXEqbKR
1k5xfXNbeXXahIP97CEHjn3KhTvZzxjoQpaA7MwsfedXggS9MkabHIO7SkIiDtKmp2FmpgmTs1Pz
mruT1D0iSPme3APm0wv2blwXq9BXhoiCqqIKsA8IVcVHSIYi7z65VXd8RDw4UHEW3AO3ZIOuI579
jlXo9Qp8XfvGV81z9m+arlLW8R9NFyT1xU0HdbL/xtG4yGhpzVh+DefLe1x4As1gVpKBcaVt4rEV
VFNRUbPo6xrk99c56GfWFFU9O3mQ0/ocZn/NZR3HNjKI1DrINrsgYr09IgGyBCvqPu5z7fQ8FXkR
F/KtZ99jK/f25keI8oxJktiJ6+ACbPgIuKyWRkdQF/NsZAueMpN89m79+MB3cMnxvPpyo7iipCm/
zbzfcwFT1v0qB2Ze5cJM2MUg6U4oRWFXYRiUXkVSGIZV0PwBcGpiBXvrDoc9gIfYOEnao3mliX3X
y4pOAyEMIZHb+HPeFRL6j83BjM76HL37/yVg/0In4Q8OdIC2zADLx86zEBQLT8jqAwJjQw5F5dsU
bhHl78s1b8whQqBfx4RERQaHVEY3NldVNjZG1oT8F3jhunvcVgxvBPQbO4f8Ip5RLSUKf/FfK6hg
lTpYNIHu2LR6izP3tt6B0htO92bwv4J9LMXw7/90sq33uuXjLefnIc7qHUt3mUJ/WyLif4UIm+jg
7ZYfPdwOeXDK/av/uB8wjKZ+LZK/z9w+WI0HEL3r8OFdG1xGv7hc2Ts6JBq+j9daPuo3eMZydKDn
0vU+z22O0sOOElFyKgApqWaFgs6XOF2wgLGD6ZfMgxd6DHNg1mQ3NnUY/xkw9k4551s4wmBr0Qvf
Q7286yTayXJ4+/CvcY5ZaqG2j51cz2n8Fia94J6LZuDkotOm68O/3rsA3wJwJg1tlsDXEIPeWP4B
momm3VoNidO9JT0nRUfQKsS1QgvDaXgOjjEgNiVBkyCN9MWDlN7gfhe+cbbkfEWtuLS8prAB0F8M
rERrMbhZcPrPTEhEeHBoTURDU21NQ1N4rRn0Jg0WgAzI5cBZrOd/HoDQ5L876dWQhd3mUUUi+V/b
8PPhZzpx59dWSD7ksuvYVAZyqYB6L+OqAvpSgB1llyRNCAwPCIs9CrzAoRL/bt8GaaXy5lEatVGL
MpyHIn+jlegd8rxvr+ZJKr2i9QvqjqHJ0N7QUm/qAcdAa2J7fHlET1g5mvopDdOpJ9oB79JPaLRz
MWN9JrYGq/fp1tYbxXQbesE8d6gIA3vATj/fdUrzdpMO91E6fsI/MKFvtPad/xehowMC/9/t3sk+
+Bu8MPdqxyxqOdU/wKIfzLsF1owT8Fb4+jvslyBqYkhxWtBrQ/s7PI9HjoLjoK+0vW30dCekAZxK
Q++l8F00Q5QazjwZQDwkQRJPq5UrPf+APtB/AHKf4Vh5R12R2AgNrSXN0L+mulFXbnHhHoyouXIP
htfO4Mufji3DTEc8K/Qamr7umMutgY6StjbxyVMtj8AD+rqka5dIH8R0Nvt5OkZslxwSBx0NVWBi
+EXUdp6sf9xxQlzXXV/WhLPbmqfe8GvGhzzgclSxBxwFUfrIcpo/8rQyXJ0TPBORVugNxN960vFK
30B5W4v4xMnmh+A2KE4zJJeVJZWlNoB+UKvvrkK//kUKjpG/sGNMbmyWEqhoxLNB1Gr/yJr23vLr
dSOihlOdrU04xGam5yYXqw3JDYn0tNhy1rkcOpWTja8/faMxb8qUp2VTphLE/wKnf10HDQplbmRz
dHJlYW0NZW5kb2JqDTIwIDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9MZW5ndGggNTQxPj5z
dHJlYW0NCkiJrFTNUtswEL7zFDt0poIBWbYJITZxmE4YhkNDO2koXJVIcTTWj0dWiMOr9dBH6itU
dkJKO2mnB3Tw7K6/71vtStr+VV3SWcEdTHkudIZ+fPuOQLAMPZyPwlE55Atx+2z5l+e7yey5mCUM
XQ0O+leUmSnHNS3xXEjHbQW8mmWHw/HHm8MGUKe1KhV3FGoldZXWGWopqbebMEHQQlyRocfRZ3DG
yEI4iIMkiHB0dgpzSxVfGVtAFHSRl7Rsno6vb7aC3svQwrkyJWS1WgWrs8DYnERJkpAwJnGMPQJX
a+1ojXX1Dm154nFH01XQ7imYGUXEI4mCkLwkuvblWFE6YTQ0Pp2apctQ97x71ol6HF/0QoajiCc4
9AtHPRZ3aHKR9Lrzl0y+uv2pfNe2ufoek06Ek3zQZv0g3caQohFJJdV5hmrM+JwupUODiVC8wmOj
qO6TDXCwMVoqeaVH/ijjTQsbi3zhqn+XZ1vMtsoNIR1RW3A2mNglbzf7e/gV8L6iOZ9wq6r/7MzQ
lOs2Ixzdjx+OT05Of0WaSwHT9csf8D0QuYb3VJWX3nni0vi7qt0lDD1DSjGDXK7LRQWUMc4a6lcq
eQE3QoqyNE9wNDyGOAwj7D/xJdwtFbfmFISeCy3cGqhm8EnxnIKijDcC10o4u4ZOKPSO/bcj3NOD
PadJtg+iMXfPbXAAb7TeTqi/mzFc+8Gy8hPkpwADAL1uWxANCmVuZHN0cmVhbQ1lbmRvYmoNMjEg
MCBvYmoNPDwvQXNjZW50IDc0MS9DYXBIZWlnaHQgNzQxL0NoYXJTZXQoL0EvQi9DL0QvRS9GL0cv
SC9JL0ovTC9NL04vTy9QL1IvUy9UL1UvVi9XL2EvYi9jL2NvbW1hL2QvZS9laWdodC9lbmRhc2gv
Zi9maXZlL2ZvdXIvZy9oL2h5cGhlbi9pL2ovay9sL20vbi9uaW5lL251bWJlcnNpZ24vby9vbmUv
cC9wYXJlbmxlZnQvcGFyZW5yaWdodC9wZXJpb2QvcS9yL3Mvc2V2ZW4vc2l4L3NwYWNlL3QvdGhy
ZWUvdHdvL3Uvdi93L3gveS96KS9EZXNjZW50IC0yMTkvRmxhZ3MgMzQvRm9udEJCb3hbLTkgLTIx
OSA5MzIgNzQxXS9Gb250RmlsZTMgMjIgMCBSL0ZvbnROYW1lL0xYQlVFVCtIZWx2ZXRpY2EtQm9s
ZC9JdGFsaWNBbmdsZSAwL01pc3NpbmdXaWR0aCAyNzgvU3RlbVYgMTUwL1R5cGUvRm9udERlc2Ny
aXB0b3IvWEhlaWdodCA1NDk+Pg1lbmRvYmoNMjIgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2Rl
L0xlbmd0aCA0MzcwL01ldGFkYXRhIDIzIDAgUi9TdWJ0eXBlL1R5cGUxQz4+c3RyZWFtDQp4nF1X
d1wU1/afBXZ2pCzCOqCgu2uhC4qogOUpSFXBgoqC9LpKExCBWBBjVC4aoyg8UYqCKESB0AUVYnuC
UqJGTERfnlHRRCVYzpC7eZ/fnd1oXn5/wN65c8s53/M953tGQGlpUAKBQN8rKi4tKlUREWbrmhgX
yU9N5UwF3HgNboJmNk783WkkQziBWnp8UA/paiJdrdPjx4w35OYbQJs+ZI6mNAWC9Jz8RYlJGcmK
mNhUueXqlf5WNjZT/5qxd3Z2lodnfHwjd4tKUcQkyM3JIC0qLjEpPiohda58EVkdF6eIkMfEZSTF
psjDIiOjIvlta8LiojbKPRRxiqSkxDS55SIr+Yzp0+1tyb8Zvor48M0pcr+whBT5Ujlv/99mKIpa
uNQlIyHCxzUzMdJ3UVLUMrdN0cvdk2M8UmJXeqYq/Lw2b1jlnbZx9eItcWFr0uPD/e1nOFjOtJo1
W+441cn2qLPdZIqypSZRAdQyyo2yoyZTgdRyyp2aRk2hVlAe1HTKjFpJeVL2lDnlR3lRFtQqypty
oCyp1dRiaiZlRa2hllCzKGvKn1pKzaZsqLWUD+VKOVLrKF9qEeVEGVISagw1imIpbcqIMqYE1FhK
jxpHialEyoTSp7QoFxIn8jOJXH2SeipwFKQInmsYaARotGj8rOmqWaylpRWv1SaUCtcJjwu7aIbe
TVeL5or2MRJmL9PBPB+1ftT+UT3a2tq22h7aG7VLtZ/rmOsE6aTp6ura68bodupZ6UXr7dcbFCeI
y8SP9Vn9Tfpv9IdHm432Gf1w9JCBhkG6ATJ4BZViDhAYcA+LBT+CtSZkjsSz2PqPeG4PGODfaPFI
NCoBQ7LAu1jA7QMLthVbCMGOxgdH4oV4Do3z/4gXgi3dBmR6KxiweCX9EmqFYq4dJw6PjCa7pFwN
i7WUE7AON0GI7WgIUl4X5oj2itZGRQZk7co9mCGdJCrZm59zHJ1HDYdOHfmm8PjJk12QPCIZy1tX
wtmCTkKxYSfIIQTkxpLmTnKisoY89osk/V3NDT03zm5YIsU/kZn/ikDHuweLXAOSlkVIJc0PRMSS
VBDCaxAKzoFckyuCZ+xOGOvwAzZFDJ5lOxEvxR6Dk2EmGD97CGyBDJvQGe6JSasR4xba9e7Skdbj
VbLCs5WFdegqOp1U6MaIR+6hkhG3YsFtsObseNTiuFssGCtvCcGaBpa7JVTeAuuReJwmwmOU/Xgs
1y/EqX/Ek7c8oGAAK8ifMxgYDoA1lMJkLIYpxpJ3A0bwkH6MrhQ21TTVVNxE19CdyKvOrXdaKhrQ
TXQxuT28OrRmbeF8YvcDGqyxAQuOtITrrUlYvSY6wUOGHWlsoAWetOTd3doNPr5RG1xl2JMWc3sR
QaCbIMCF8NA5YSHsp3Ex7hZiIecHQnxaBCegm0QNPmJ1noB5iOAFHVwLi53NsQC7Y48hTMEccBoG
AbjAEssPeL4sFwvZ/oseE8393RcuWNs3PHyp775MddAo2xJuGoyCmcWGZ8hpWXzstnJWRiAn0Mhx
Ph3bsb7MizjDWuHR2NG11KXaXyZp86+5rbht2o0ulJ1vZ7A2p8d+d8FjilWgp7t7YO/rN619fTIV
LfkI9BD8WkgEuMNGKsCtlZ/TuIH7nPCMh5vL5QFPBUPuEIwRNJGFI//g0tgvOrfXxdX73bOvxwJy
fTgegy1wFt4OEmxBKOYNeu9gbp4Mm9PZdsvX2JEljOcLcIBZ3/0C2pcbM2IrZIVbDqfnRTLEzxTi
4XMYRQh67aOTzRDAc17+Rw6ZOU+fW9aa2IMYMPoFxOB0f/P9mIsySf+lGK9zi009UWCCYhkD2olq
LwM8PNwDe4aGWnuJl4S5H2DSIOh/EHAlkMbm5qOD6BDq2HVxe23Mq5nXVdZPm4q1sDd2eTERbEHv
Ve/7ShmW0pmhkclrUQTaeHzL2e3FX5zad4nZP8jmDZyvv0myrCqzOLFgy1dpB6IJmYtSYQx3kOBT
RwAz58E0GclgzZCjwsdrsXu0GSLXYEHNlFsenZ4DG96it2jg686ezu5v3qNhBHT0b4v7lvTOqZqE
mFw8hgX9BxZ4BraaY451sd7cIWKU7Y9DoCdTM59LAQNBP4naVXJRvxHU0qCJ+srbrl/rqXxNWIpA
K+71it6A6x5lWIt4R95bK4dYss1UBMIr8/AsPNNvHhbK/oZ8xSfkOUuC/FxSFq5vWHfWyxQb2WAx
dl5QuqA6QFa9tlvRhXrQxTNfX2cwIbhI0jySQ9bio5gi8HtOUpPsI/zwE6k9DoMv3wqe8olwmytn
ndrpivx/lucX5uzLl74Tbdofm5uOGLvgkOmyxQvs7iu9QM55PRKJR6aRsrmLJHkicfc+cfcIXybS
oICFZTSY/PQSLMHc6Uc8VYa/V9UFjtUia+WiH2tiF7pEx86V8Uf8VSgEP/D7M6Cbhd/4wgzOnB4Y
KE+RQt1AfmUkx8cRY8eBTF0ojSU1n4pknUjSO1BfP3DsSM7eIilMEu3K/QLtQUuQX1i8KyOpeU9K
JOCEp+8InM9UcJI6CdthnLHkITeVnOIkkvzaFRZU4WOKx9hgAzwXz3uCtWBcZ23R9csyV9HigGD3
NbGl9VlSbEbnhhUmVMc3xt7IfEQo7/jiLkhk5JxvyRn4KwJz32VXC6u1Xq7eQd2vfmv5rkemKvEk
idV+3uP9TOX9vEP8vEPm/kv8y1PXTr6Sa8A70DBsJRYuBlNswLs6xO3nNNh9QDv0YjPCmQmzPbBm
zNG4ojRZUfrx7MuZMNd/rGTwfFZ+1maTDZFbFsckHMrPkG49uvvo7jNkOf0l1v6PDzih79HVwrqq
uqpTF1E76ottdivB7pfGRubvPIxKmbNVxW1SyVA3+jolN4D5JEykugm6iTVrCEW6iXgSS3ldutnc
1Hn2VNbmQml+xpfbUCyDH6nUCXVntEZXxpUHHwtGHmhdYuRyBopFapktIRisJKJAhBgKYSoeA1bG
Eg4yoYGFhfStik2+u9HOnO2ynHSUgbKQ55ebi2IZmHWaTi3IPoaq9sDGPUfs6gaq6q+jn9G1Le2x
1RvOBRX6IEZpqubYDC1yvreoEZ3Yc2IrI3l3YmtessIExe5MzNz62bYtX4SiP8uBvARyiTGbYIxh
A1gbS9JHArnxLG4meM+h94TvTN68iZE0h8Ss2rTCFOvNfE8Mtu9/CZLLTVsTvpaVZBzNLIhiYCKd
QURK/BK7kaBE48l4Gt6CN8EUPAvWvbp9fuCKTJJ+wkb4lCaZxnkNCh6p5aacnQ9mRB/MPOx68b/p
2c1hzyvLDhwuk74Sbdu3K2cnYqKzj7bK4ALRdqgkUdhT3EWY083vjlDVXZ729Ei8FjmEEIRIwLRU
0CUVVFfQDJOhAyZrcm+5L1nUvbUppi6gY84ZUrvwInNnPAkLr64Cy0TZb1vepNckouXjfP2ip5ut
bHzwhZSoQR6e/mE2+BJeLwfNJySFRStuYNNyGaZL5SVxJah93Ldt5/tftke4HJSqQ9pJUPxKLVMN
fGX9Eh6z+LFKqmxwOa6Hcr7ZIm8fi1SSqWPDu6NSElWrk87VGnE1xI9npFYtCQ7zXBZfdUsKb4iP
uiKsc9sTRHfbTt+ok0rSl/BocMdVWPTxWESrsXhDx2VlxWfvzj2wU4q1RBV7z+8rRsx/qqufyEa6
PkGkovOPZCvs4O1kuSEWFCTzHpLXm5RDfPbxWPOa28mnqOLPPlGdlqogCGDYCHy5GiG2pLFAKcOj
OBk/hhXKGuHHRTC/WHCdty4QHrHcZKKRfL64i678C1icLQQnGq+Dn2EphAqxg1q8x3BDxaoaWslb
lksuVmaLHILDbG2DG55IuWwi+tki5Fy6oi2kPbB/0xP0BPWXt7e2NZVeQwMMl63uAFWnnCKnzObN
/5k/pVq0KiHef2VKRbe0D1svEqEFJ9Y3RjREXdnSS0Js9e9+GC/jqklyFqn940aMwJb3z4x2Vorn
cGIhlvOjWfzIjIapxE+YQv/EGTxUGgg/4aUmJo+Xyll1GRPaE2kBoUq5lsEEPtIlx9nkk58fQxUM
tItAY+EVbI7NF/hgg2wpmNKHrpw8QczqOJ0Rk5H92dZdsvSdCHlk+e0cK8/wX4WsUVBBVFkSycqN
lRfSW01voG/L2y4xknSUeGBnwWcMTKXxfIhnJc1zIoLc1ieU1TWUFl/Ll7bm1Rz6an/h4XEqyeLN
5SYawQG+ubehsYOyBc/mWvgx5JBG/69QA5Sx4AYlQjyPnokdHcCRH4EbLsFeuEwI8+jnMO8ZnseP
xL/rfWribxB/F6r/jCVtN/6nkX94u7ruxoUzSaFSrFTN/O2ZMxS9W3ITU56BKX5h0k2XVp/xQj4o
Ii1oFSNp6xb9/37z+qd+8/qfNZkIUNuacxeSe0yBfQX64Hh3872Yy7Lodu9z3sgLBSYrVjOQLwJt
fJHtbXO3sApw93Bb3zP8StUK/O6mBmckwQiCeXAceIo3ke60SUV3obKRdNKN/DyE819EpjTocLdB
rLz9J2ixgx8IbNk8F7K5baxyG+mC19mJNju6hmIxaSF4lvL9UQbQpBEzgSD+WyWP/6Bqp0/Ulha/
vQ/6T6s70C8MTLB9gq2wxayZ2Ho32pWbJQWTk/QPNS1dN2tD3eYnx+HpWFOKdZ2jl36OjRkuTc04
XUh6AesJ5eA9yPEolXBCPPSxbSgv59RuRjJ4YfvZcH8Tn5BgX++Y2rt7pHg8nYsnDc4AIqpg8+vP
IH0U0zH3G5lk6Hb96eZbJqDt8D2eMMcz0T9Cmhi7PRAtZXaAkSi39kDRoRMFlVVF9Yi5UqVY7hYe
4yTbwVf5kXUEgxA+FUTYJRBLEbZF2K4VS4E8M2/oiRCuAC0EFgjMzwH9HkIZFXowHhiOCC38S/0F
V866cF7YmXx9Kj2EWBtqsD0JuP09Ed4ADIt9aPCBK8KPF4rxehZE4NIKUgS2COwCQYrJM2NBv8fh
50ifiS0QNldgeiJWXciDdQo035FySNoscuO2kXWsUp9eqpQJwZA+dr6qqBEx3zWuneUUstbdV1F5
dS/fc+/Ho184kjtIsr19S/peM/s32Hh97I64cNlJsBRCy8dAFIDGw5IG8pFVBVKIg3FEF7hm9vOW
7JMZ5dGXFp/9B3JAiyJD3cI8MuchzCIsPragemW9973Ix+Twib+8BzsY7/gCi1dEZgaFyA58j9BX
Zwu66mqvoGZ0KuNEMGOF/dhbDWvnLwha5bMkpP37B00dt0hDW6nm4g3esTLepz2kvL+nQ4NmYzbR
J2BKsl06tuGFuwBS75IcnQchDNm1pVjQBeYsNv9prwh5JsUu38H4ieoPVhw9XVJX+c8a9IBwUvSn
b9tegi8hWSnhGEPSLAb0yC/h2jBnyxmxpwqOHjp6hJH8eub08cYWE9C0eYiN8VibOVjLsyK0SyGV
DDuHKFY7mmCTYTuwAsvhQTB5rOhwbpJiE9jMSn692Ri1anVIpK9PyDffdjTWdsr24XOsZLi3McjF
MyTY0zO0ue9OU0s3371DBJgK4BK8ZHEZNoUyHn6IeCvgOqCLVXZO5jr5mRRi9FhgoIgkXgWMg1jS
HtSCM3sAC57PBTF6hnprG+7UdJZ+IB87aDhzYGN78H33utmkZZhkbYYtCSoWYFh97khhqawg73De
yXIGm0Z5zQtQnG7YK33KrWB7GtY4zQ/xX7Ik4tLDgbrLN/lAEIILYAMPqjU2V4soLHwNtq8FYL6R
rSPyN0xH4FDhO5ofg85rC7oSbIUgeG1PnwNX4SRagV2FU/5njHUsX9Px2FZobdmv2kp65yvsWbJp
WDUtTj3J1fD6G3iSBm1tmKgD2nm6ujDxiK4eRf0fvBkCgA0KZW5kc3RyZWFtDWVuZG9iag0yMyAw
IG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoIDUwOD4+c3RyZWFtDQpIiaxUS27bMBDd
5xRECpQJEoqSnDiWYsloHRhZ1EXhOo23tDiWCVGiINGW7Ktl0SP1CqXkT9PCLboIF8LM6L0ZviE5
/UGdsygBjeYQiyzAP16+YyR4gJ9vx/Y4H8JSPG4L+Lr9PI22SeRxPAjP+gPG1RxIzXKyEFJDUSIo
o+B8OPk0Om8AtV+neQqaoTqVWenXAW4pvrGbMMWohegkwLPxF6SVkonQyLU8yyFO5xotCpZCpYoE
OVYXm5QFX/iTh9E+ofECvNQ69ymtqsqqOpYqYup4nkdtl7ouMQhSbjLNapKV7/CeJ2ZHWlZa7Z6s
SKVUzKhj2fRQ6MHIKUSuhcpQ47O5WukAd2+7nRunB+SuZ3PiOOAR2yzi9Lh7w7w7r9ddHCoZdadL
ma7ta/UNxp8KLSFsq36QemdI0STxJcviANeEw4KtpMbhI8g1aBEx8lFJ3qc7bLgzWjZ9lZL+oeRN
tU1EvNTlvxUWLWYvdEfwx6xIgIfTYgXtZn8PvwI+lSyGKRRp+Z/NGap801ZEF0+T58urq+tfkeZe
oPnm8AeZHog4Q+9Zmt8bZw1Smeua6Xs0NAwpRYRiucmXJWKcA2+o35iEBI2EFHmu1uhieIlc23aI
+bh/O4kTUk4cCt1f7cY8PpzwDL3RertE/eO0gMyMiMrMgp8CDADmQEoHDQplbmRzdHJlYW0NZW5k
b2JqDTI0IDAgb2JqDTw8L09QTSAxL1R5cGUvRXh0R1N0YXRlPj4NZW5kb2JqDTI1IDAgb2JqDVsv
SUNDQmFzZWQgMjYgMCBSXQ1lbmRvYmoNMjYgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xl
bmd0aCAxNzAyL04gMT4+c3RyZWFtDQpIiZxUeVCTZxp/vy9f7vsi9wmEQCAk4QjIfSMBwhkJIVxJ
uJNwhCOIGI9Wp7XaVtcDXXaddrbqVqEU6lBn16PCUndblepYq+sF3d1aqbWprl2rbKjb7h/bnZ3Z
3zO/9/k9xzwzz/PHCwB2AAQASwHosbm688oyzFXmail2HkAB+wENtp7O5wqgwH8CBsBf/kMvFDT3
M/X/BcTu6LEF/GSA9f2eTk9gECugWbbO7hWtDGhyhi5TE9AJAGBS/9W/AkyDvcVt+2+T/0+s7P9c
/Xsvj2PAs5JxuV2OFe9s8uhWPIRaBj/e6Sf8XAyv3Gl5+afMSowOGAYQABGQACNgLMAHQiAGIUAB
IoAG6IAepIB0kAsMwAhMwALqQQvoAN1gCKwHL4DXwOtgBBwCb4FxcBL8DvwBXAWXwS3gB0vgO4gG
YSEWFAXJIS1UCKVCxVAHZIGc0CuQN8BxaC90DLoETUMXoO+ga5AflkJPYS6cB8vgFLgTzoXt8H64
A94Gz8I74SnYD5+Ab6Jk8CKKiCpBUVB6lA+ViLKjJlBNqJ2oxQDPIFzUaZQfKUJ9jYQimxAZUoWc
QMqQlxE/shk5hY5CjiOP0M3IPXQU+g20DO1A30KvQY9ixOjt6E8xVvQshokZRS9jjJibmETMNqwc
48H8EevAjGMJ2COYJWwB9musCvsyTo9tw36EW489gqPh5rB3cRV4Bi4Stw9vxblxN/GHcRN4Bf4R
7hHeRcjBJ+OPE3bhNxIgwiL+Q4KBGE+gE/YQtxKqCYvE64Q3iTqSlnCf6CO9SFxFvED6M3ELSUqO
I14idZNfIclJZ8l/DSgOJZN0htxBGSUzyacp/yDbKRxqFfk4xUU9TiFSZmlcSh1VQhugTFG9tM+o
ROon9BRqI01DP0h9n7aNgaaxaHcZ7TQnPZ8xT3tIv8J00UsZCcwr9GOMEVYGg8j4nvU2o41Zx+Yy
PmR+wH6BGc5Ssr9lvsTaHmRj3mM9DPqEVcy2crJYE+wZzhQ7KCiaq2SvDdrHPcC+zUF49KB8Thdv
S9AY5wbvKYfLNfB7ORu47/OXOF/yIgTNXBNvRHCbe5pPFFp5av6w8CpvP/+ByMTHC+yiy/wBwVVx
Bf9vQqP4ksAsnJFUCs6JUiRXhMmiKalFOCZWS2+IgsWHZDbRXolc9oWYLBmVu8WbpQL538VPpPuC
10u6ZZwQnORL2e6QndImOTtULL0l3x16RGYJ5ij0sivBI4oZeXmIKKxcfjHkYNhCsDE0VOkJ/jj0
t+HokGKFLnxvyMeK6QhVqDEsI+Jk6HzYOVWFolJZrrqr+FR5I3JDmDW8NYoXdif8YdQ7ypaITWqD
8r6Kpv48vE/1q+gN4cuRao04YmvkSc0JFSOqRGtWHYi6o30cqVR7dHsiJ6NxMQlRGdEHYj6LOq/R
xQ6prZq5OIn6nrYu7oPoIe2j+FYNRbdDT9H8Okapn9LqYs4kWLUzsdZEtM4c+zhxTPdV3K5V5phN
8bokJJYXfz5pPHZc70q2xuUlUFIIcbcSjqVMx3sTjamtembigzSe/uiqXWnnElYn6dPXJXyedC1D
k7gx2ZexsEqSosjcm0ROlWYdTjqaOpddl1yU1pXDSf4qXZBzPuXV9Jncram6jM68zNTLmcK8p2ne
zLn86XRJVu/qvvSz2cEFMRlt2fMF32TSczYa3smcztUVdmU15C4U6bIJeb8o8mdP5ucXv5dTm//E
OJhLWD1Wkpb7XoG9FMlrNPBLz+XTDBfKXs3/feHW8qrVzqL0CmmBqOhxxd2Cj4onKicNw8YO03Ch
pkS5pqDwTsliFadod+nBqsXigrJa80Txs3Jh9QbjZPk1S2lJe8X+GnmpvNJS4y+9ahJaZ8teN92o
3VduWHOwzlmBVNnrsypOmpUN3MpB81LDfVN89buNs6ZvLF7b6JrxmnR7f5XLinOUmiOtF5tU5nu1
I82Y6rfrHM0LFme9tuVUjbr++9Zf1jxomGsbsk427m631Pbb7B3Jdcl2nVNUDzsg57P6Oce863bD
9qY33GcbK5s9nUdsopbcrh22v7Tyuj32sdalHovD23bGk9WU3b6nV9VM7XD2sZqvO7P7nrUccgn6
v2jtc307cKkt2/0n76l2Zudbg0fbF7o2rt3f8W63degl5+aexHVel8nDHm5zKz3+9Rb3k96LPtB5
oW/MB7re7N/hA92DA24f6DF6S3zAoxjUBd6na9k+0Ht57WMf6Ds2dN0H+resO+UDAw3Dv/EB72Ef
8IHnv/+P/KcAAwA2lyBtDQplbmRzdHJlYW0NZW5kb2JqDTI5IDAgb2JqDTw8L0JCb3hbMC4wIDAu
MCAxOC4wNTUxIDEyLjA0ODVdL0Zvcm1UeXBlIDEvTGVuZ3RoIDIwL01hdHJpeFsxLjAgMC4wIDAu
MCAxLjAgMC4wIDAuMF0vUmVzb3VyY2VzPDwvRXh0R1N0YXRlPDwvUjA8PC9BSVMgZmFsc2UvQk0v
TXVsdGlwbHkvVHlwZS9FeHRHU3RhdGU+Pj4+L1Byb2NTZXRbL1BERl0vWE9iamVjdDw8L01XRk9G
b3JtIDMwIDAgUj4+Pj4vU3VidHlwZS9Gb3JtL1R5cGUvWE9iamVjdD4+c3RyZWFtDQovUjAgZ3MK
L01XRk9Gb3JtIERvCg0KZW5kc3RyZWFtDWVuZG9iag0zMCAwIG9iag08PC9CQm94WzAuMCAwLjAg
MTguMDU1MSAxMi4wNDg1XS9Gb3JtVHlwZSAxL0dyb3VwPDwvUy9UcmFuc3BhcmVuY3k+Pi9MZW5n
dGggOS9NYXRyaXhbMS4wIDAuMCAwLjAgMS4wIDAuMCAwLjBdL1Jlc291cmNlczw8L1Byb2NTZXRb
L1BERl0vWE9iamVjdDw8L0Zvcm0gMzEgMCBSPj4+Pi9TdWJ0eXBlL0Zvcm0vVHlwZS9YT2JqZWN0
Pj5zdHJlYW0NCi9Gb3JtIERvCg0KZW5kc3RyZWFtDWVuZG9iag0zMSAwIG9iag08PC9CQm94WzE5
MS4zNDggNjYxLjgyNSAyMDkuNDAzIDY3My44NzNdL0ZpbHRlci9GbGF0ZURlY29kZS9Gb3JtVHlw
ZSAxL0xlbmd0aCAxMDEvTWF0cml4WzEuMCAwLjAgMC4wIDEuMCAtMTkxLjM0OCAtNjYxLjgyNV0v
UmVzb3VyY2VzPDwvUHJvY1NldFsvUERGXT4+L1N1YnR5cGUvRm9ybS9UeXBlL1hPYmplY3Q+PnN0
cmVhbQ0KSIlEzjEOxDAIRNGeU8wJEOPYBs4TKWmSZpu9/nqLhPahP4IgDJ9TTN3C8RVm180H5mxK
T+JexHVtbVnXGEyUuGn0SbyZbzoYiV2azT952bUs1XqMCkue8eqeF3Y55CfAAC3IIVgNCmVuZHN0
cmVhbQ1lbmRvYmoNMzMgMCBvYmoNPDwvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aCA1MTM4Pj5z
dHJlYW0NCnicvV1Lk9tGkr73r8CxvWFz6v3wzWOvYybC1si21nvRhSIhNXfZZKtJSaP59VOFwiNZ
QBY5TKLDB9kQyc+Zle/MSnys2IJXLP7T/rl6vPvL74rr6sMh/IuvfvzjjlV//Piq+Y/VIfzHYbW7
+3jHmy9V7R+rx+qvb+7YgjEmPWPh629W4Rvhb7mo3ry/S7/NK8sXQmteGScWWodPPd7d/7D45s3/
3f33m7vfrgEUihkhETgnR3DfsYVQ1Zsvd/fV1bDxN4w0FoU1C2n1KZEUMGm5URwB82phM7AnChiX
BTDO+MLKG6IpyZ3FpIUzt/AZWj0fbVwveMbJ3WzHxoUYCcmaJJFce+lQNL+QGSc3JE760rlJsVD6
FO2fsyk5lyMpiYLlZlZyrvjC8RtqefkAdfOBE7T57CbXMheXF2GpNiMiX82n70YtTIb2hoKmTfB9
FkOzY3F5Pd8BWh8930s7Pu7GRu2n+dyDZyPXtySJi9aWobR5u2DZAR5nM6GCsYXTt6LtnLgIZmfS
96IPFHxs1H6eTd8FtyP/vifRpqw3HkMTaqQKzzOiuYXxp2iP8wmn9CNVmE/xhNIL5W+leGdVQY0i
pVupgi8RqcVIFb6bj0itc2d0E/fAF0xJjyqgHofzf84npCbQ6G+YPJQV0I49H0ndy7RZM1L3w2yx
pwhpdG44SclD2SmE7Fn4G5rpslPwMg+UCEnfOb2TwaurUVh2C+NSFBfJRuH8vaQQyZ30thMXgdV4
DA//W21c/VBX7/fXK0TAlKz5sUlIztrYbIDszdnj8kjjrNaSSww4+N1G7QGt+/cEMrlg0mNgIdEV
CJXXkxhYa5jwAuVtyHN1RuIxHOerN6+rXymMZVIxzVFivVkwPU1sfTgsP9S0U4VGIccWko1Odb0k
xRzSSGEthqfaGt4ErUtathaYLDFFFSHLV6fydL8k6agIZkiiVJpgfWRGZfxIPNHlt9WXh83qgUYt
9GI5vOR84bNDJXmxoKiOacwySK4XzJ/CPT7W6w1NjoTCxUhqk3LGKZXZfqVawSF4HQFblQPfU4wg
40JojmmntG2uMyFH++12/+VQRftEojZYHwxeybYEDoj9n58opZySzQ/RQkp+bmrzo/Rqb4TGREmF
UD0/0Yd6ua5J5kFrpQWmn8oz1Dx8W20ONGqlMNxiLk4zl/ua+8PD/gspEFROOIYdax8jKbsQNkvA
NjsarYIZh/q2EMsrrzxEvv958+ETLTYzWkgMkTOf3AxArCs1l35yIVNuC+Cur5RHfnJtLCo7XLSp
GICrft5vSUaeOe0wPeFKL4zW06ITrN9m94EUDAruUB3ljqec+gS7VdKgooRgJWqMCMEKGpMxnvwp
4PO6piW9xeCoqxYCvBUpow8WxjFUjoRo016At3k60iKUIEdSK4OGnSLEwaeQ+11FyF8aS6utEiik
saNTrDaUiIjLcIyo0Nixcl4vMmVPLYJuqJFu3MJVl3MV19aZAYnviVIjLEfF1LfZIDTm2/WB1os0
VqIE9q5S6M45D3z9pV4+zRfXehf1Q0Do+7/TXLNz0mPKEYcrmgwFwO3Wm9XySKqcFEsKqrWqU8yl
RSEqnKnC4kuu5IjUt/e/kAAtV8ygvA1xdFPng0f59huK1FoRbLbC8ExbM51i7PfzmQNu2mAL0Hl9
UzsaAx8CAoWSGQ0sR8h8oATtTRbIDV558zInFETQNOBysYapVIWbAqZVa4IhZB5jteBthwGc7PHL
/rt31xv7c0IsgpZqTIgJVdUoVjpoK8eBfYrhp4BX+zU1u5daoxGKHRuKL8SqmOdCoXFmkGOGkboj
BfPnitcyhLg5qbMVr4NGzeFpmpKYVGi2JIXPHQ3QVlqifdJzGQErlYJrwNzN9S35xhzK2MTBa3+o
IX6qQxhBTAuZd7bA5hQqZfBtY2tLCtLOhPhKsBTiAz5TQnzGojihx6pEW4+bIrRe7XdrWgpcKhop
bXJSgTnez6dEyrSN+yngdzRjXKzZKydzo0Go2TeSpAQqSc7kjv1+N1+BQXXzZACOVl49aT2Pa5xm
ZI9I42ssxH7aYLKqY9EvO7l6/Zc1bXy7lKxpqUeRL2mChgsh0WjM+TYr5Wxhc5XY1sd6RjsQB9Ub
SqewycVjb/EiFQ9OvKk9DshNL5hU7XRKeIOG+cqlrgBAXN5u1GWcJrrkRiGB5HIYXho3bS8JwFWP
xOpNYKY2Ak3Y2klPgLj7dKypVT+vtbIYaJzz9DmZNLaGTIkxHK+t3QK8IKUrapOjoJNCtb55Sief
6x0tW5Iu2FpMRUTwzgKDXi+/fksLDDwL7v9cNXAK+svmSGjnN/2AQm4a++sOM4LvNkR+C2lQ0y8l
nzC/bROEVUtqCFik2jBczKhUu3h3D+/xG1zKOEHGms4I5x6tFUo3ku+gUYenekXojqQqD0dBY5wv
NELu53pL0arGSvMQrmk0NtRtn21KxGL9Y10tqQ1xbQUq4sqPDvv+/X5LcvPNzVDcR2gu0sQBgLx+
7DMwizmJ8ldzNwL7Ml9UoaUYsfN7Gi9tcEWqFKZF/6eD5vh23pMxmr/l3Dk0qDCpkATxdvuKWDYL
gSHn6FhivCAT85kTzM3uw0uw1ap+jJZxEqAIkRoejHZsHfBAjrE80Ky9iPYereu7FM5MQj9umoiR
WMsSeCwlRBMunoK31u8hGD7DZysnhQNpRjHhGZMMA1NMabxpbFIABeGaKhKthHWhHJsmpW5A+fXm
4XI5HvBeXI6noF9Mjk/AgRxrP78cgzOmybH2xqDT2r0cA7gkx7Qe66WSrPTCdpJ8vUVuusixxIS2
rTtJBnjLLcHNNXU0byzeKHe6qRJCxMcqcpYW+0qnPSo7cYLOn2CCOvNmT6gwNeRyjbakurt+k9Bv
71fb/er/qa3dEFegvb90m2MSfbcn2amytvrUvYGnTNRWpg1anJUsZbAQ7utu9UCTY1mqB0uR6ngQ
cr/b/KteEw2EEWa4dI/NDukg0Z63M8U2GeA/6+cDVZaFCOEnXqZNnd0p8FefHt/Vz8QMzmuHW6p2
lQIAD/rz56s5R15cK1WQ3jjsNPPEi0u5HKR0zomX9l7SFJWzDrwIrlDgWeddBE4w8XJSKWcWbTsH
HiutZKy4ERwtGcvWPgG4h+e6JnWQiqU8YXDzQKrkNbZBWo7PcFqfgjVA62Z3rD+Q2o/F4Q8uUhg+
IUM0Qo003qE3hXgbBJ8QSoucONMKL8/KVDWcOtPV8kgezS9d/jJt7DLBYvJ1qDhFhNLs0mAPZPIr
kgF2SmiLmUHF2qRqgsWviRMugbsMLYlymSLTCdzP1FDifN9OaZEiRMDlXRNEfDvXzTMv8gjiNjrL
g9UT5yrPkE5i3y44c4v2lzUfBS2xXTdfKViMTRLxQmjhTp0WPmVyAG37lWZwg4xqzLN0UxFx+kN3
1BHTCiW1x6MxljbNQcC6rt7eEydblEHtHedpohBCyrff0K6YiWC+0QZvl8WoYGmVTIi/7tf19xVp
XRlTQS/wa3TBZUdBhaAxviWOX+E5cFwaGA07BJzrrg6Xtpm7AFi3uvYQV5vgkzuKNVYc0rgkTkIU
w9pgaZsuyckpzhrWdjcCJlk7b1zLW48FiaXGte2gm0X1RAjdDNRA0GrWIDOOmnhMeKlR5tkRsJg8
xHAP0hvjS9Joc3G+RTLdGNxJeoMZnHG+JU6PR283CU2bb0mMZoGd6ER3Cjghoz8vt5/qQ7WuSdsV
mLVW4vfw2UiLwB3f3eyjBzJtd4BkU0cPtJIWrR+p9mYYBNzPOAygrBoRSBwGKA5WdD0SZfRCt8MH
tFkA44IRPjcLAOGe6wPRBAsZYhV8VRBrcgYI+bm+fpnyf8BTPSyMoLWdirtkep4CuMPXx8f6SBto
LA04C5Z2PAJMMGS8olkA7rxEDZ8QaREIpHa5Om4+Xz87/h+cqDT9iI54gRMFcC92ogPmbU707OqG
7kABsU+0Ie6QFVrN0Dt8so1BIXdfSH7iWvcW8voVe00HT2iLdip7+QFwq+2m3pFqCZfSyOzCt6Ck
NS7BMTu0C92TCNCCG/lMuyNzIYnSy96VaGLyYAOZZ2iEcO+e98v1anl4iZMMRrg3sWb+mADC3SAm
KLW4u5gAQoaYoCIFzsbJwtQEV42VA4ggTSH0epsuh2QMzcjCYSqPAMctjcQikVFoiztuEMzlaLXf
EZxYWwzDezrCpitIEHK/paWfxRtIwvuR8NL2DjEekl20iiFZWkA9eZzkvZdMaGcs2jCTMse+fxus
bl398NRcIibFCIX+oE9jehD3n9VfqbNjl9lAo/ogwb6ADQRwL2UDAeQL2cAB8TY2sAmomWcGn1Jo
jSCg9el585mwbTPx1xi0+RC3qMtTau/r6tPhNM7sUbjncf1yJWPJMPwZfsKx6rm+e/9fyAcVaz4Y
P1b+YPuL6AdD6I9CB+KtUs3fatf87eNd4KZa+OHJdngSIu8Fj0/6b/VPHu7+t9pd52SKu4J8ek+L
jJv22oLJL8Mapt8uJ3X6g+e4nP8i/sG4BB7ncndYA5eVzrncPRm43H3rRlzG954EtxNbIpDLf75C
uVwgdfqDLZdDHHMZ8/AP6hKX+8MauGxHXLY5l/tv3YDLOs6qoWNGwjX9Ssjl2MrD+Bxs7WV87j/Y
8lkrhH35L6IfVLEhh/JZqlyaQwwVRzsBn/snPVf7b9H5zOOkNhpPmDQrB9n8muhptcWXBsUFyLmJ
qlebOBSCnSxQ7Au9QXsOQohz7qD9SfyT/dlOgAN/0MoSONv2yXC2wpnMHwxPrtehQKtz+H3n9MoG
yVzP7N/3+2P1U319l6A54nDC6H0zydoQFaAuv1ImDZqymZb49JpQTZ8PIkoBYuLcVjB9oa3oPnjW
VmS/eLFRyWyys5mtkDaPL/ong03uvkW0FUmcOFqdDH+ZYlZoK2DDCVHcIOcXKu5Zdcx/8rziToED
xW2PAShu+wQornG54vZPrmY0F8Jo/EpSWnYhQlpi8mZqo8C0+TkZzhmvVFjbTEJNgv+0OTzdYoRP
SK3QK1JSpgk+8H8QcuuSQndiwZVrDzsGRQX54dZdKGndT56XtCnwQdK4N5mkdU8GSePx9TMnkjY8
mSllECqtSeCmudGV7gSQ6sblBodOi1sh3JK4Oqo4G2/SvnqIRyqAacMtxzcipkIJQAN9I6LWqvDL
eK3PpWHJk2OkLdErlvo6Hw/xiCvGy28kGZNHXMlVKtZKnoZBT6T08WnWEEalqgyENOq8xRPyQosX
NOFS3yovtXhT4B9heJtZvO4J8K0it3jDk+sTHgVevDp1fSWW+oQeGP07cUpIMO7xSl9b+wKAg1Go
n+vdilinPmMY0pZjSO68hsHn1M5rGMbkzWkY2ggYws1tGHTa3gEhLzIM7FLDcFbd85+8wDBMgAPD
oEeGQY9CIT8KhTw9FJKlff0ylfXiDEbH6H88bz7QdsxxozS6ilaYlLdCyN3yWBOn1bUNdhbt0ekm
RIGQm8f6cFySXoJbvggQL3tF5wZBZ/amqXgIAS9Rmi4tOK80Z1Xh8kyjzx8mwIHSiJHSiJHSmJHS
mJsoDT6XERefxyHn2EEb3Omq3nyeV4rTK+Ih6gtIcbohAEFnlmI94m1Jikv1/ukPtmUthfZpsl9E
P1iqqH28C6Y1L2uFJDEra3VPhrKWvF2roRwjmbR0DNa1/qCNF7Jm7WbpZTsiK4Ivj58ez/p048oH
e3l57PK0oPfpE+AfYW8zL6S1T0Cwr0fBvqabp7jWAl1fF1/cFFcexJZZXwGv3xNnCeLtU9wimjQF
AyGbIJ/2PpxyT9+nMgfEXNe744aU1ygdrBPayBHppeEAEtQ6qBs7yvVBld4fBakd1QeBaJo4M9g0
OMOjKG7dk+3wJC5ROG3W90+urvGeG6tx6X5QfP9BRwY7oUC6tvnUU9ArV0/BULcO8atvLGn3rf4J
gYLiUinF0vojSIHkJyT0zerhEGxOQv+kZ/nQ4p77EGJaJTIS3CkFjmcUyOA34ZPt8KRnef+t2Q8h
rihqxvwABdycypHUOQnO5SR0TwY56r41Pwlaj0gQ6mywzi8t9p8t4ec/eUGwPgEOiv1mVOw3o2Cd
BRm3J8F6/4QQrCvG0DE3IdNNZS6HgPKHT8eH6ClINwODvhZWhaVJNwB6cgmTOuymJLoKotveBel9
e79/Iu6pL3liKdK9ZQi52e+WW8KEZgo5JEcvInbpLgSdtyalR3z1JnO/ulGUeIM8fNpHXdA6da67
J9v+iZF8EbQ0Pmm/NTy5vgxceumQaPc9eLsw3bt9SfeJmCiUgKVpNs4MYCBU+vDpmbZZs7iMPI6A
eARaLYi7yOO+CVTrdYYbB+xpbevoU9FXQsYQOJoZAFj9Wh9o22Hjtq+CqqeXyE+xljx8zo2S+AYj
lVa/AFr/dvrK8RT/+uhNgmVm8c+gfz7ewB+ebPsnxjoR/9x2XxoeEFwR16ZvBCtkU4fluqfh959/
vH7bQup0O94vuM0RfXxRXrAoEDEYMJKRDALZd9ZzvLj9JNaTIR7tgpSHL0jJ4bqldxDuVU1bmGOM
Yhg7YyyhT8kDF/73z4Tlo8nfaeYw1sYdujFzgrRSmlppw4DDzzK+sTheCIWAdfX6mbJ2P3YNXZ/j
5oixjxY3z02y97hf7bc33CwwApfpHXWQ3LdxDSj1KrNByW3f1gERmymj62+Gdp1K7ExjddFkZ0oL
0uKgrUPQlDUjlv66JEUczfJNDM6LnJ+D+DyviNs4uHZSYnyNr6fI+cq9F1O+ifOQ+Zz4pu7J4Jtc
iJ00N4NvGh5cn49KxW3/BmTMN5nGvfJ0VpvtltTG5lw6gUqHV+ktGwDx9fL6NzSkEprTCpMPzVN4
BgHrSsPy0293/wa5pYusDQplbmRzdHJlYW0NZW5kb2JqDTM0IDAgb2JqDTw8L1I5IDI1IDAgUj4+
DWVuZG9iag0zNSAwIG9iag08PC9SNDE1IDM3IDAgUj4+DWVuZG9iag0zNiAwIG9iag08PC9SMTAg
NSAwIFIvUjEyIDYgMCBSL1IxNCA3IDAgUj4+DWVuZG9iag0zNyAwIG9iag08PC9PUE0gMS9UeXBl
L0V4dEdTdGF0ZT4+DWVuZG9iag00MCAwIG9iag08PC9CQm94WzAuMCAwLjAgMTcuMzM0NyAxMi4w
NDg1XS9Gb3JtVHlwZSAxL0xlbmd0aCAyMC9NYXRyaXhbMS4wIDAuMCAwLjAgMS4wIDAuMCAwLjBd
L1Jlc291cmNlczw8L0V4dEdTdGF0ZTw8L1IwPDwvQUlTIGZhbHNlL0JNL011bHRpcGx5L1R5cGUv
RXh0R1N0YXRlPj4+Pi9Qcm9jU2V0Wy9QREZdL1hPYmplY3Q8PC9NV0ZPRm9ybSA0MSAwIFI+Pj4+
L1N1YnR5cGUvRm9ybS9UeXBlL1hPYmplY3Q+PnN0cmVhbQ0KL1IwIGdzCi9NV0ZPRm9ybSBEbwoN
CmVuZHN0cmVhbQ1lbmRvYmoNNDEgMCBvYmoNPDwvQkJveFswLjAgMC4wIDE3LjMzNDcgMTIuMDQ4
NV0vRm9ybVR5cGUgMS9Hcm91cDw8L1MvVHJhbnNwYXJlbmN5Pj4vTGVuZ3RoIDkvTWF0cml4WzEu
MCAwLjAgMC4wIDEuMCAwLjAgMC4wXS9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREZdL1hPYmplY3Q8
PC9Gb3JtIDQyIDAgUj4+Pj4vU3VidHlwZS9Gb3JtL1R5cGUvWE9iamVjdD4+c3RyZWFtDQovRm9y
bSBEbwoNCmVuZHN0cmVhbQ1lbmRvYmoNNDIgMCBvYmoNPDwvQkJveFsxOTEuNTg4IDMyMy42NjUg
MjA4LjkyMyAzMzUuNzEzXS9GaWx0ZXIvRmxhdGVEZWNvZGUvRm9ybVR5cGUgMS9MZW5ndGggMTAy
L01hdHJpeFsxLjAgMC4wIDAuMCAxLjAgLTE5MS41ODggLTMyMy42NjVdL1Jlc291cmNlczw8L1By
b2NTZXRbL1BERl0+Pi9TdWJ0eXBlL0Zvcm0vVHlwZS9YT2JqZWN0Pj5zdHJlYW0NCkiJTM4xDsNA
CETRnlNwghGwgOE8luImadz4+t7CyaZ90h+NsrLweZBgk9r4Im1HavAwh2gbfyYp2s2mJXLSgmHI
SuVfNQIjqnknk0B1+LL3tEJk/YVLnu2VfQ/s9KJbgAEA4Lkg0g0KZW5kc3RyZWFtDWVuZG9iag00
NiAwIG9iag08PC9EZWNvZGVQYXJtczw8L0NvbHVtbnMgNC9QcmVkaWN0b3IgMTI+Pi9GaWx0ZXIv
RmxhdGVEZWNvZGUvSURbPEVGNzUyMkI5N0FGNzlBNEU4QjhDQjcwOUFCRjZFMjI0Pjw4OUIwREM1
RTM1ODBENzQwOTdBNkIyNzU1RDU1QjI3Mj5dL0luZm8gNCAwIFIvTGVuZ3RoIDE2NC9Sb290IDEg
MCBSL1NpemUgNDcvVHlwZS9YUmVmL1dbMSAyIDFdPj5zdHJlYW0NCmjeYmIAAiZG1ikMTAwMNkDW
72gGpv+idUDW6xYmoBjDfxjxD85lZGb6L87zh4lBfh9QG6M8SK8iiDAGEkw6QEKEH8SyAxLMMUBC
MQ7ETQYRa4GEUAWI5QTSoQUilIG2lVYyg4xnYvo/qeI30FBpkMmvgBI5zYxM/6fuBNorGglSjGIb
Y1g1A1TbqvX/kLQxhBiAWLogiySAxOoTDAABBgBuuCIrDQplbmRzdHJlYW0NZW5kb2JqDXN0YXJ0
eHJlZg0KNDQ1NzMNCiUlRU9GDQo=

--=__PartA794885A.0__=
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--=__PartA794885A.0__=--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 05:05:56 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C5B11E816F for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 05:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.432
X-Spam-Level: 
X-Spam-Status: No, score=-5.432 tagged_above=-999 required=5 tests=[AWL=1.167, BAYES_00=-2.599, 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 vTlykfg0Ts75 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 05:05:47 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id EAC6F11E8167 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 05:05:46 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1321286DADB for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 12:05:46 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 57DBC86D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 12:05:40 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbUWn-0006VW-RW; Wed, 30 Oct 2013 12:05:40 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9UC5UgO005624; Wed, 30 Oct 2013 05:05:31 -0700
Received: from sc-owa02.marvell.com ([199.233.58.137]) by mx0b-0016f401.pphosted.com with ESMTP id 1ftb2mmrvy-12 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Oct 2013 05:05:30 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 30 Oct 2013 05:05:29 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Wed, 30 Oct 2013 14:05:24 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, Greg Dowd <gdowd@symmetricom.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Wed, 30 Oct 2013 14:05:23 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: Ac7VZY7WYbfvxbEySQGFtmnk1Or/WQAAGPTw
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net>
In-Reply-To: <527018E7.3000406@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-30_04:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310300062
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Brian, 

The draft is indeed intended to update RFC 5905.

The reason for the erratum is that there currently seems to be a conflict between RFC5905 and RFC5906. It seems that this conflict should be documented as an erratum to allow the (innocent) reader to resolve this conflict.

One of Greg's points was that RFC5906 is informational, and thus should not be weighed against RFC5905 (standard track). And yet it seems that the problem is in fact in RFC5905, and hence I believe this erratum makes sense.

Thanks,
Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 10:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org 
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 09:28:47 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D390111E8267 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.515
X-Spam-Level: 
X-Spam-Status: No, score=-5.515 tagged_above=-999 required=5 tests=[AWL=1.084, BAYES_00=-2.599, 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 ZcEK6zmMNyFD for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:28:43 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 2554111E80F8 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 09:28:40 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id E26A786DAD3 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 16:28:39 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 29B8F86D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 16:28:27 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbYd7-0007tn-2v for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 16:28:27 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9UGS2do020210; Wed, 30 Oct 2013 09:28:19 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0b-0016f401.pphosted.com with ESMTP id 1ftb2mp35w-1 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Oct 2013 09:28:19 -0700
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 30 Oct 2013 09:28:18 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Wed, 30 Oct 2013 18:28:14 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <gdowd@symmetricom.com>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Wed, 30 Oct 2013 18:28:10 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAQ1X8IAARuWQgAACdfA=
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D8331B2@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A044@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED6A044@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-30_05:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310300123
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Greg,

>It's a nit I guess but I still don't get 28 from the quoted language.  I see text that says "if greater than 22 bytes, an extension is 
>present" and "extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is there another rule forcing this minimum of 
>28?  I can see needing a couple padding bytes if there is a 22byte MAC but that is padding.

The text in RFC5906 is a bit confusing (to me); I believe 22 is a typo, and it should be 24 instead. The text below seems to say that the "remaining length" is 160/8+4= 24 bytes. So correct me if I am wrong, but it seems that 22 is a typo. That is why it must be greater the 8 (words) and a multiple of 4, i.e., 28.

Quoting RFC5906:
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID)

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Wednesday, October 30, 2013 6:14 PM
To: Tal Mizrahi; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

It's a nit I guess but I still don't get 28 from the quoted language.  I see text that says "if greater than 22 bytes, an extension is present" and "extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is there another rule forcing this minimum of 28?  I can see needing a couple padding bytes if there is a 22byte MAC but that is padding.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 4:59 AM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg, 

>I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?

The minimal length of 28 bytes is applicable when there is a single extension field, or when there is more than one extension field the last one must be at least 28 bytes long. The 28 byte minimum was not intended as a placeholder, but as a lower bound that is intended to be backward compatible with the parsing rules defined in section 10 of RFC5906:

   One or more extension fields follow the NTP packet header and the
   last followed by the MAC.  The extension field parser initializes a
   pointer to the first octet beyond the NTP packet header and
   calculates the number of octets remaining to the end of the packet If
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID), the remaining data are the MAC
   and parsing is complete.  If the remaining length is greater than 22,
   an extension field is present.  If the remaining length is less than
   8 or not a multiple of 4, a format error has occurred and the packet
   is discarded; otherwise, the parser increments the pointer by the
   extension field length and then uses the same rules as above to
   determine whether a MAC is present or another extension field.


Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg Dowd
Sent: Tuesday, October 29, 2013 9:58 PM
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last followed by the MAC."

I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 09:34:27 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5468F21E80B6 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.786
X-Spam-Level: 
X-Spam-Status: No, score=-5.786 tagged_above=-999 required=5 tests=[AWL=0.813, BAYES_00=-2.599, 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 2Xds9DpRzI-f for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:34:22 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id B392D11E817E for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 09:34:12 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 86A8B86DB01 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 16:34:12 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id AB49C86D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 16:34:06 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==01531eb1d8d==gdowd@symmetricom.com>) id 1VbYiZ-0007xI-8j for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 16:34:06 +0000
X-ASG-Debug-ID: 1383150837-05bdbc07004d9220001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id XZ2TE1Agnx4uQC13 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 09:33:57 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Wed, 30 Oct 2013 09:33:56 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAIAABNmAgAEHloD//9HdEA==
Date: Wed, 30 Oct 2013 16:33:56 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6A093@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net> <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383150837
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==01531eb1d8d==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In my opinion, 5906 is the wrong source to point to when talking about extensions without MACs.  Section 4 says that the MAC is checked on every packet, with or without extensions.  The entire autokey protocol mandates MACs on every packet.  Section 9 has mechanisms defined for client and server operations, all of which include generating a MAC.  Section 10 specifies one or more extension fields "and the last followed by a MAC".

Again, I'm in favor of the new draft defining mechanisms for using extensions outside of autokey, I just don't think this errata is correctly framed.  By this argument, 5905 and 5906 are both "in error" because, honestly, the goal of the ntp working group in v4 was to document the existing mechanism and the existing mechanism mandates MAC with extensions.  It wasn't really a mistake and I don't see a conflict.  Instead, we now want to broaden the capabilities of the protocol.

Can you clarify where exactly you see the justification in Section 10 of 5906?  And how it would counteract all of the other language in 5906 mandating or implicitly requiring MACs?  Maybe I am missing something?  Otherwise, I would again vote to use your draft as the clarifying text once published.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com] 
Sent: Wednesday, October 30, 2013 5:05 AM
To: Brian Haberman; Danny Mayer; Greg Dowd; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Brian, 

The draft is indeed intended to update RFC 5905.

The reason for the erratum is that there currently seems to be a conflict between RFC5905 and RFC5906. It seems that this conflict should be documented as an erratum to allow the (innocent) reader to resolve this conflict.

One of Greg's points was that RFC5906 is informational, and thus should not be weighed against RFC5905 (standard track). And yet it seems that the problem is in fact in RFC5905, and hence I believe this erratum makes sense.

Thanks,
Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 10:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org 
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 09:37:20 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB37421E8140 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.876
X-Spam-Level: 
X-Spam-Status: No, score=-5.876 tagged_above=-999 required=5 tests=[AWL=0.723, BAYES_00=-2.599, 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 th3xvqbyTsbx for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 09:37:15 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 57A0A11E8294 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 09:36:30 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1D9A486DB09 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 16:36:08 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D744286D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 16:36:02 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==01531eb1d8d==gdowd@symmetricom.com>) id 1VbYkR-0007zg-P8 for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 16:36:02 +0000
X-ASG-Debug-ID: 1383150953-05bdbc07004d92f0001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id DUvdx4S1MHJ4SpkJ (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 09:35:54 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Wed, 30 Oct 2013 09:35:53 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>,  "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAQ1X8IAARuWQgAACdfCAAAUHcA==
Date: Wed, 30 Oct 2013 16:35:53 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6A0B3@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A044@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D8331B2@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D8331B2@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383150954
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==01531eb1d8d==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Ah, good catch.  Okay, I support an errata on that :-)

-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com] 
Sent: Wednesday, October 30, 2013 9:28 AM
To: Greg Dowd; Brian Haberman; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg,

>It's a nit I guess but I still don't get 28 from the quoted language.  I see text that says "if greater than 22 bytes, an extension is 
>present" and "extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is there another rule forcing this minimum of 
>28?  I can see needing a couple padding bytes if there is a 22byte MAC but that is padding.

The text in RFC5906 is a bit confusing (to me); I believe 22 is a typo, and it should be 24 instead. The text below seems to say that the "remaining length" is 160/8+4= 24 bytes. So correct me if I am wrong, but it seems that 22 is a typo. That is why it must be greater the 8 (words) and a multiple of 4, i.e., 28.

Quoting RFC5906:
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID)

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Wednesday, October 30, 2013 6:14 PM
To: Tal Mizrahi; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

It's a nit I guess but I still don't get 28 from the quoted language.  I see text that says "if greater than 22 bytes, an extension is present" and "extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is there another rule forcing this minimum of 28?  I can see needing a couple padding bytes if there is a 22byte MAC but that is padding.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 4:59 AM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg, 

>I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?

The minimal length of 28 bytes is applicable when there is a single extension field, or when there is more than one extension field the last one must be at least 28 bytes long. The 28 byte minimum was not intended as a placeholder, but as a lower bound that is intended to be backward compatible with the parsing rules defined in section 10 of RFC5906:

   One or more extension fields follow the NTP packet header and the
   last followed by the MAC.  The extension field parser initializes a
   pointer to the first octet beyond the NTP packet header and
   calculates the number of octets remaining to the end of the packet If
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID), the remaining data are the MAC
   and parsing is complete.  If the remaining length is greater than 22,
   an extension field is present.  If the remaining length is less than
   8 or not a multiple of 4, a format error has occurred and the packet
   is discarded; otherwise, the parser increments the pointer by the
   extension field length and then uses the same rules as above to
   determine whether a MAC is present or another extension field.


Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg Dowd
Sent: Tuesday, October 29, 2013 9:58 PM
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last followed by the MAC."

I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 12:15:15 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8166621E8091 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 12:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPLkRKe2Myr4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 12:15:09 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 07B7321E813A for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 12:15:03 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 7F69486DB03 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 19:15:03 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4027686D4E3; Wed, 30 Oct 2013 19:14:47 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.106]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <dieter.sibold@ptb.de>) id 1VbbE0-0009pE-Cs; Wed, 30 Oct 2013 19:14:47 +0000
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 36362CFF989; Wed, 30 Oct 2013 20:14:34 +0100 (CET)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 1EE02CFF988; Wed, 30 Oct 2013 20:14:34 +0100 (CET)
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D8331B2@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org>	<52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>	<74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A044@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D8331B2@IL-MB01.marvell.com>
To: Tal Mizrahi <talmi@marvell.com>
MIME-Version: 1.0
X-KeepSent: E9344E1D:B8A5C082-C1257C14:00695881; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0 March 08, 2013
Message-ID: <OFE9344E1D.B8A5C082-ONC1257C14.00695881-C1257C14.0069B2C1@ptb.de>
From: dieter.sibold@ptb.de
Date: Wed, 30 Oct 2013 20:14:30 +0100
X-MIMETrack: S/MIME Sign by Notes Client on Dieter Sibold/PTB(Release 9.0|March 08, 2013) at 30.10.2013 20:14:30, Serialize by Notes Client on Dieter Sibold/PTB(Release 9.0|March 08, 2013) at 30.10.2013 20:14:30, Serialize complete at 30.10.2013 20:14:30, Itemize by Notes Client on Dieter Sibold/PTB(Release 9.0|March 08, 2013) at 30.10.2013 20:14:32, S/MIME Sign complete at 30.10.2013 20:14:32, Serialize by Router on ROSE/PTB(Release 8.5.3FP3HF370 | April 24, 2013) at 10/30/2013 20:14:33, Serialize complete at 10/30/2013 20:14:33
X-SA-Exim-Connect-IP: 192.53.103.106
X-SA-Exim-Rcpt-To: ntpwg-bounces+dieter.sibold=ptb.de@lists.ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dieter.sibold@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "odonoghue@isoc.org" <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, ntpwg-bounces+dieter.sibold=ptb.de@lists.ntp.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============4544944100036012686=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is an S/MIME signed message.

--===============4544944100036012686==
Content-Type: multipart/signed;
	 protocol="application/x-pkcs7-signature";
	 micalg=sha1;
	 boundary=-------z47980_boundary_sign

This is an S/MIME signed message.

---------z47980_boundary_sign
Content-Type: multipart/alternative; boundary="=_alternative 0069B2BFC1257C14_="

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0069B2BFC1257C14_=
Content-Type: text/plain; charset="US-ASCII"

I also support this errata. As far as I remembered this was also the 
recommendation at the last meeting in Atlanta. 

//Dieter





Von:    Tal Mizrahi <talmi@marvell.com>
An:     Greg Dowd <gdowd@symmetricom.com>, Brian Haberman 
<brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>, 
"odonoghue@isoc.org" <odonoghue@isoc.org>
Kopie:  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Datum:  30.10.2013 17:28
Betreff:        Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Gesendet von:   ntpwg-bounces+dieter.sibold=ptb.de@lists.ntp.org



Hi Greg,

>It's a nit I guess but I still don't get 28 from the quoted language.  I 
see text that says "if greater than 22 bytes, an extension is 
>present" and "extension must be greater than 8 and multiple of 4".  Hence 
24, no?  Is there another rule forcing this minimum of 
>28?  I can see needing a couple padding bytes if there is a 22byte MAC 
but that is padding.

The text in RFC5906 is a bit confusing (to me); I believe 22 is a typo, 
and it should be 24 instead. The text below seems to say that the 
"remaining length" is 160/8+4= 24 bytes. So correct me if I am wrong, but 
it seems that 22 is a typo. That is why it must be greater the 8 (words) 
and a multiple of 4, i.e., 28.

Quoting RFC5906:
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID)

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Wednesday, October 30, 2013 6:14 PM
To: Tal Mizrahi; Brian Haberman; RFC Errata System; mills@udel.edu; 
jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

It's a nit I guess but I still don't get 28 from the quoted language.  I 
see text that says "if greater than 22 bytes, an extension is present" and 
"extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is 
there another rule forcing this minimum of 28?  I can see needing a couple 
padding bytes if there is a 22byte MAC but that is padding.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 4:59 AM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; 
jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg, 

>I see that Tal has allocated what appears to be 4 more bytes than 
absolutely necessary perhaps as a placeholder for a different MAC schema?

The minimal length of 28 bytes is applicable when there is a single 
extension field, or when there is more than one extension field the last 
one must be at least 28 bytes long. The 28 byte minimum was not intended 
as a placeholder, but as a lower bound that is intended to be backward 
compatible with the parsing rules defined in section 10 of RFC5906:

   One or more extension fields follow the NTP packet header and the
   last followed by the MAC.  The extension field parser initializes a
   pointer to the first octet beyond the NTP packet header and
   calculates the number of octets remaining to the end of the packet If
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID), the remaining data are the MAC
   and parsing is complete.  If the remaining length is greater than 22,
   an extension field is present.  If the remaining length is less than
   8 or not a multiple of 4, a format error has occurred and the packet
   is discarded; otherwise, the parser increments the pointer by the
   extension field length and then uses the same rules as above to
   determine whether a MAC is present or another extension field.


Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [
mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg 
Dowd
Sent: Tuesday, October 29, 2013 9:58 PM
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; 
jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; 
odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I don't think this is a bad idea per se but I think this errata entry is 
incomplete and ambiguous.  There are other places in 5905 which call out 
MAC and extensions which should also be addressed.  I have a little 
heartburn with the fact that it is using 5906, an informational RFC, as an 
argument for modifying a standards track document.  Also, it is 
disingenuous to present 5906 as logic for removing MAC requirement.  5906 
is entirely predicated on the requirement that a MAC be present whenever 
extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC 
relationship but I think the errata should consider 2 elements, first a 
complete review of 5905 for MAC/extensions details for consistency, 
including a better argument justifying the change, and second, an informal 
review of future-proofing the MAC by size since I see that Tal has 
allocated what appears to be 4 more bytes than absolutely necessary 
perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [
mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of 
Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; 
odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header 
and before the MAC, which is always present when an extension field is 
present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header 
and before the MAC, if a MAC is present. If a MAC is not present, one or 
more extension fields can be inserted after the header, according to the 
following rules:
> o If the packet includes a single extension field, the length of the 
extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of 
the last extension field MUST be at least 28 octets. The length of the 
other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with 
Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the 
sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last 
followed by the MAC."

I don't think that changes the intent of your text, but it does leave that 
text lacking in clarity saying that a MAC must be added after the 
extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg


--=_alternative 0069B2BFC1257C14_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>I also support this errata.</font></tt><tt><font size=2>
As far as I remembered this was also the recommendation at the last meeting
in Atlanta. </font></tt>
<br>
<br><font size=2 face="sans-serif">//Dieter</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">Von: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">Tal Mizrahi &lt;talmi@marvell.com&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">An: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">Greg Dowd &lt;gdowd@symmetricom.com&gt;,
Brian Haberman &lt;brian@innovationslab.net&gt;, RFC Errata System &lt;rfc-editor@rfc-editor.org&gt;,
&quot;odonoghue@isoc.org&quot; &lt;odonoghue@isoc.org&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Kopie: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;ntpwg@lists.ntp.org&quot;
&lt;ntpwg@lists.ntp.org&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Datum: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">30.10.2013 17:28</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Betreff: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">Re: [ntpwg]
[Technical Errata Reported] RFC5905 (3627)</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Gesendet von: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">ntpwg-bounces+dieter.sibold=ptb.de@lists.ntp.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi Greg,<br>
<br>
&gt;It's a nit I guess but I still don't get 28 from the quoted language.
&nbsp;I see text that says &quot;if greater than 22 bytes, an extension
is <br>
&gt;present&quot; and &quot;extension must be greater than 8 and multiple
of 4&quot;. &nbsp;Hence 24, no? &nbsp;Is there another rule forcing this
minimum of <br>
&gt;28? &nbsp;I can see needing a couple padding bytes if there is a 22byte
MAC but that is padding.<br>
<br>
The text in RFC5906 is a bit confusing (to me); I believe 22 is a typo,
and it should be 24 instead. The text below seems to say that the &quot;remaining
length&quot; is 160/8+4= 24 bytes. So correct me if I am wrong, but it
seems that 22 is a typo. That is why it must be greater the 8 (words) and
a multiple of 4, i.e., 28.<br>
<br>
Quoting RFC5906:<br>
 &nbsp; the remaining length is 20 (128-bit digest plus 4-octet key ID)
or 22<br>
 &nbsp; (160-bit digest plus 4-octet key ID)<br>
<br>
Tal.<br>
<br>
<br>
-----Original Message-----<br>
From: Greg Dowd [</font></tt><a href=mailto:gdowd@symmetricom.com><tt><font size=2>mailto:gdowd@symmetricom.com</font></tt></a><tt><font size=2>]
<br>
Sent: Wednesday, October 30, 2013 6:14 PM<br>
To: Tal Mizrahi; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org;
jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com;
odonoghue@isoc.org<br>
Cc: ntpwg@lists.ntp.org<br>
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)<br>
<br>
It's a nit I guess but I still don't get 28 from the quoted language. &nbsp;I
see text that says &quot;if greater than 22 bytes, an extension is present&quot;
and &quot;extension must be greater than 8 and multiple of 4&quot;. &nbsp;Hence
24, no? &nbsp;Is there another rule forcing this minimum of 28? &nbsp;I
can see needing a couple padding bytes if there is a 22byte MAC but that
is padding.<br>
<br>
<br>
-----Original Message-----<br>
From: Tal Mizrahi [</font></tt><a href=mailto:talmi@marvell.com><tt><font size=2>mailto:talmi@marvell.com</font></tt></a><tt><font size=2>]<br>
Sent: Wednesday, October 30, 2013 4:59 AM<br>
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org;
jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com;
odonoghue@isoc.org<br>
Cc: ntpwg@lists.ntp.org<br>
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)<br>
<br>
Hi Greg, <br>
<br>
&gt;I see that Tal has allocated what appears to be 4 more bytes than absolutely
necessary perhaps as a placeholder for a different MAC schema?<br>
<br>
The minimal length of 28 bytes is applicable when there is a single extension
field, or when there is more than one extension field the last one must
be at least 28 bytes long. The 28 byte minimum was not intended as a placeholder,
but as a lower bound that is intended to be backward compatible with the
parsing rules defined in section 10 of RFC5906:<br>
<br>
 &nbsp; One or more extension fields follow the NTP packet header and the<br>
 &nbsp; last followed by the MAC. &nbsp;The extension field parser initializes
a<br>
 &nbsp; pointer to the first octet beyond the NTP packet header and<br>
 &nbsp; calculates the number of octets remaining to the end of the packet
If<br>
 &nbsp; the remaining length is 20 (128-bit digest plus 4-octet key ID)
or 22<br>
 &nbsp; (160-bit digest plus 4-octet key ID), the remaining data are the
MAC<br>
 &nbsp; and parsing is complete. &nbsp;If the remaining length is greater
than 22,<br>
 &nbsp; an extension field is present. &nbsp;If the remaining length is
less than<br>
 &nbsp; 8 or not a multiple of 4, a format error has occurred and the packet<br>
 &nbsp; is discarded; otherwise, the parser increments the pointer by the<br>
 &nbsp; extension field length and then uses the same rules as above to<br>
 &nbsp; determine whether a MAC is present or another extension field.<br>
<br>
<br>
Tal.<br>
<br>
<br>
-----Original Message-----<br>
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [</font></tt><a href="mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org"><tt><font size=2>mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org</font></tt></a><tt><font size=2>]
On Behalf Of Greg Dowd<br>
Sent: Tuesday, October 29, 2013 9:58 PM<br>
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu;
william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org<br>
Cc: ntpwg@lists.ntp.org<br>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)<br>
<br>
I don't think this is a bad idea per se but I think this errata entry is
incomplete and ambiguous. &nbsp;There are other places in 5905 which call
out MAC and extensions which should also be addressed. &nbsp;I have a little
heartburn with the fact that it is using 5906, an informational RFC, as
an argument for modifying a standards track document. &nbsp;Also, it is
disingenuous to present 5906 as logic for removing MAC requirement. &nbsp;5906
is entirely predicated on the requirement that a MAC be present whenever
extensions are present.<br>
<br>
In conclusion, I like the idea of clarifying the extension/MAC relationship
but I think the errata should consider 2 elements, first a complete review
of 5905 for MAC/extensions details for consistency, including a better
argument justifying the change, and second, an informal review of future-proofing
the MAC by size since I see that Tal has allocated what appears to be 4
more bytes than absolutely necessary perhaps as a placeholder for a different
MAC schema?<br>
<br>
<br>
-----Original Message-----<br>
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [</font></tt><a href="mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org"><tt><font size=2>mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org</font></tt></a><tt><font size=2>]
On Behalf Of Brian Haberman<br>
Sent: Tuesday, October 29, 2013 12:24 PM<br>
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu;
william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org<br>
Cc: ntpwg@lists.ntp.org<br>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)<br>
<br>
Hi Tal,<br>
<br>
On 5/17/13 12:28 PM, RFC Errata System wrote:<br>
&gt; The following errata report has been submitted for RFC5905, &quot;Network
<br>
&gt; Time Protocol Version 4: Protocol and Algorithms Specification&quot;.<br>
&gt; <br>
&gt; --------------------------------------<br>
&gt; You may review the report below and at:<br>
&gt; </font></tt><a href="http://www.rfc-editor.org/errata_search.php?rfc=5905&amp;eid=3627"><tt><font size=2>http://www.rfc-editor.org/errata_search.php?rfc=5905&amp;eid=3627</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; --------------------------------------<br>
&gt; Type: Technical<br>
&gt; Reported by: Tal Mizrahi &lt;talmi@marvell.com&gt;<br>
&gt; <br>
&gt; Section: 7.5<br>
&gt; <br>
&gt; Original Text<br>
&gt; -------------<br>
&gt; In NTPv4, one or more extension fields can be inserted after the header
and before the MAC, which is always present when an extension field is
present.<br>
&gt; <br>
&gt; Corrected Text<br>
&gt; --------------<br>
&gt; In NTPv4, one or more extension fields can be inserted after the header
and before the MAC, if a MAC is present. If a MAC is not present, one or
more extension fields can be inserted after the header, according to the
following rules:<br>
&gt; o If the packet includes a single extension field, the length of the
extension field MUST be at least 7 words, i.e., at least 28 octets.<br>
&gt; o If the packet includes more than one extension field, the length
of the last extension field MUST be at least 28 octets. The length of the
other extension fields in this case MUST be at least 16 octets each.<br>
&gt; <br>
&gt; <br>
&gt; Notes<br>
&gt; -----<br>
&gt; The usage of NTP extension fields without authentication is aligned
with Section 10 of RFC 5906:<br>
&gt;<br>
<br>
While the text you quote below is correct, it does not include the sentence
immediately precedes it. &nbsp;That sentence states:<br>
<br>
&quot;One or more extension fields follow the NTP packet header and the
last followed by the MAC.&quot;<br>
<br>
I don't think that changes the intent of your text, but it does leave that
text lacking in clarity saying that a MAC must be added after the extension
if it is not present.<br>
<br>
Regards,<br>
Brian<br>
<br>
_______________________________________________<br>
ntpwg mailing list<br>
ntpwg@lists.ntp.org<br>
</font></tt><a href=http://lists.ntp.org/listinfo/ntpwg><tt><font size=2>http://lists.ntp.org/listinfo/ntpwg</font></tt></a><tt><font size=2><br>
_______________________________________________<br>
ntpwg mailing list<br>
ntpwg@lists.ntp.org<br>
</font></tt><a href=http://lists.ntp.org/listinfo/ntpwg><tt><font size=2>http://lists.ntp.org/listinfo/ntpwg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
--=_alternative 0069B2BFC1257C14_=--

---------z47980_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
Kw4DAhoFAKCCASowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMx
MDMwMTkxNDMzWjAjBgkqhkiG9w0BCQQxFgQUOFfCbVCNuXzHeLtecQHuTULfGkkwQwYJKoZIhvcN
AQkPMTYwNDAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYIKoZIhvcNAwcwDQYIKoZIhvcNAwIC
ASgwgYUGCyqGSIb3DQEJEAILMXagdDBpMQswCQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxp
c2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcN
AQkBFgpwa2lAcHRiLmRlAgcTdVEDgnMGMA0GCSqGSIb3DQEBAQUABIIBAI1wya3BtyDfv5O3Jbp2
fFcAsgYHeuklQUWxKSUkyN5HiHiiUhNyzPlJZ1qg62tAtCGELslq+gPxHVBsbHMfF5MLUxZFM02L
ekEXdvwfPM0A7IDyy/4qo9hX9tfzbMnEBTw7RTWO9YysKHpyB7vs2mlsCMfUjrQi+hj+9HZqST88
JUKwE+CjHcXjsaTyV2s6uqfCuiQvHMAom5asH/uWdujxNgwL7Mf7W4H7fPsBoFHhjDBl4ZlLwsrU
6srlPAMuod7KG9ali+MrBfu6+ixLi34IqLPtCVaYmez1GNQgImJEb5fgpCUAyMJCffLRXC7ptL8S
FsE8aiea2gDUtE2FJg0AAAAA

---------z47980_boundary_sign--

--===============4544944100036012686==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============4544944100036012686==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 14:20:05 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FF411E8274 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 14:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 tagged_above=-999 required=5 tests=[AWL=1.011, BAYES_00=-2.599, 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 04ZUmkpQ13x0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 14:20:01 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id E04EA11E826B for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 14:20:00 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8DC4B86DAB9 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 21:20:00 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9393C86D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 21:19:41 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbdAv-000Ecj-Gg; Wed, 30 Oct 2013 21:19:40 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9ULJUHM026028; Wed, 30 Oct 2013 14:19:30 -0700
Received: from sc-owa02.marvell.com ([199.233.58.137]) by mx0b-0016f401.pphosted.com with ESMTP id 1ftb2mqhay-27 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Oct 2013 14:19:30 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 30 Oct 2013 14:19:27 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Wed, 30 Oct 2013 23:19:23 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <gdowd@symmetricom.com>, Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Wed, 30 Oct 2013 23:19:19 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAIAABNmAgAEHloD//9HdEIAAUKzA
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D8331E3@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net> <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A093@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED6A093@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-30_06:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310300185
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Greg,

> Can you clarify where exactly you see the justification in Section 10 of 5906?

Quoting section 10: "If the remaining length is greater than 22, an extension field is present."
(as we discussed it should be 24 rather than 22 - I think it was Dieter's catch BTW).

So based on this sentence (and the rest of the paragraph it is taken from), if you have a long extension field at the end of the packet, i.e., 7 words or longer, the parser processes it without looking for a MAC.

These parsing rules essentially allow you to use an extension field without a MAC, provided the extension field is long enough. Any implementation that complies to these parsing rules in fact already allows an extension field in the absence of a MAC.

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Wednesday, October 30, 2013 6:34 PM
To: Tal Mizrahi; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

In my opinion, 5906 is the wrong source to point to when talking about extensions without MACs.  Section 4 says that the MAC is checked on every packet, with or without extensions.  The entire autokey protocol mandates MACs on every packet.  Section 9 has mechanisms defined for client and server operations, all of which include generating a MAC.  Section 10 specifies one or more extension fields "and the last followed by a MAC".

Again, I'm in favor of the new draft defining mechanisms for using extensions outside of autokey, I just don't think this errata is correctly framed.  By this argument, 5905 and 5906 are both "in error" because, honestly, the goal of the ntp working group in v4 was to document the existing mechanism and the existing mechanism mandates MAC with extensions.  It wasn't really a mistake and I don't see a conflict.  Instead, we now want to broaden the capabilities of the protocol.

Can you clarify where exactly you see the justification in Section 10 of 5906?  And how it would counteract all of the other language in 5906 mandating or implicitly requiring MACs?  Maybe I am missing something?  Otherwise, I would again vote to use your draft as the clarifying text once published.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 5:05 AM
To: Brian Haberman; Danny Mayer; Greg Dowd; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Brian, 

The draft is indeed intended to update RFC 5905.

The reason for the erratum is that there currently seems to be a conflict between RFC5905 and RFC5906. It seems that this conflict should be documented as an erratum to allow the (innocent) reader to resolve this conflict.

One of Greg's points was that RFC5906 is informational, and thus should not be weighed against RFC5905 (standard track). And yet it seems that the problem is in fact in RFC5905, and hence I believe this erratum makes sense.

Thanks,
Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 10:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Oct 30 16:21:01 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5429211E81D9 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 16:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, 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 C1G7dccVBouY for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 30 Oct 2013 16:20:56 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id D182B11E8186 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 16:20:56 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 74B3B86DADA for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 30 Oct 2013 23:20:56 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8D44286D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 23:20:42 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==01531eb1d8d==gdowd@symmetricom.com>) id 1Vbf41-000J7v-9W for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 23:20:42 +0000
X-ASG-Debug-ID: 1383175231-05bdbc07004de470001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id gBGbT8RhCsfOoAwp (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 16:20:31 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Wed, 30 Oct 2013 16:20:30 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAIAABNmAgAEHloD//9HdEIAAUKzAgAAiFdA=
Date: Wed, 30 Oct 2013 23:20:30 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6B1A2@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net> <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A093@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D8331E3@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D8331E3@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383175231
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==01531eb1d8d==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

I understand that this sentence describes how to distinguish a MAC from an extension field.  I see nothing which indicates whether either should or should not be included, it is ambiguous in that respect.  Instead, I find very specific language just before that which indicates that the presence of a MAC is mandatory, no?  

Is there a particular reason to submit RFC5906 as the justification for the errata instead of the upcoming extension draft?

BTW, I'm going to drop the wider email list in favor of just Tal and the wg mailer so it doesn't keep getting stuck in the moderator queue after this.  Be forewarned :-)



-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com] 
Sent: Wednesday, October 30, 2013 2:19 PM
To: Greg Dowd; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg,

> Can you clarify where exactly you see the justification in Section 10 of 5906?

Quoting section 10: "If the remaining length is greater than 22, an extension field is present."
(as we discussed it should be 24 rather than 22 - I think it was Dieter's catch BTW).

So based on this sentence (and the rest of the paragraph it is taken from), if you have a long extension field at the end of the packet, i.e., 7 words or longer, the parser processes it without looking for a MAC.

These parsing rules essentially allow you to use an extension field without a MAC, provided the extension field is long enough. Any implementation that complies to these parsing rules in fact already allows an extension field in the absence of a MAC.

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Wednesday, October 30, 2013 6:34 PM
To: Tal Mizrahi; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

In my opinion, 5906 is the wrong source to point to when talking about extensions without MACs.  Section 4 says that the MAC is checked on every packet, with or without extensions.  The entire autokey protocol mandates MACs on every packet.  Section 9 has mechanisms defined for client and server operations, all of which include generating a MAC.  Section 10 specifies one or more extension fields "and the last followed by a MAC".

Again, I'm in favor of the new draft defining mechanisms for using extensions outside of autokey, I just don't think this errata is correctly framed.  By this argument, 5905 and 5906 are both "in error" because, honestly, the goal of the ntp working group in v4 was to document the existing mechanism and the existing mechanism mandates MAC with extensions.  It wasn't really a mistake and I don't see a conflict.  Instead, we now want to broaden the capabilities of the protocol.

Can you clarify where exactly you see the justification in Section 10 of 5906?  And how it would counteract all of the other language in 5906 mandating or implicitly requiring MACs?  Maybe I am missing something?  Otherwise, I would again vote to use your draft as the clarifying text once published.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 5:05 AM
To: Brian Haberman; Danny Mayer; Greg Dowd; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Brian, 

The draft is indeed intended to update RFC 5905.

The reason for the erratum is that there currently seems to be a conflict between RFC5905 and RFC5906. It seems that this conflict should be documented as an erratum to allow the (innocent) reader to resolve this conflict.

One of Greg's points was that RFC5906 is informational, and thus should not be weighed against RFC5905 (standard track). And yet it seems that the problem is in fact in RFC5905, and hence I believe this erratum makes sense.

Thanks,
Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 10:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Oct 31 00:42:44 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF4811E820C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 00:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.651
X-Spam-Level: 
X-Spam-Status: No, score=-5.651 tagged_above=-999 required=5 tests=[AWL=0.948, BAYES_00=-2.599, 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 abwVFw9vlyPS for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 00:42:40 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id CD52311E8132 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 00:42:37 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 9C04A86D78B for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 07:42:37 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 1BC5686D4E3 for <ntpwg@lists.ntp.org>; Thu, 31 Oct 2013 07:42:22 +0000 (UTC)
Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbmtW-0001kD-Bt; Thu, 31 Oct 2013 07:42:22 +0000
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9V7gBbK000320; Thu, 31 Oct 2013 00:42:11 -0700
Received: from sc-owa02.marvell.com ([199.233.58.137]) by mx0b-0016f401.pphosted.com with ESMTP id 1ftb2ms87w-9 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 31 Oct 2013 00:42:10 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 31 Oct 2013 00:42:10 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Thu, 31 Oct 2013 09:42:05 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <gdowd@symmetricom.com>, Brian Haberman <brian@innovationslab.net>, Danny Mayer <mayer@ntp.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Thu, 31 Oct 2013 09:41:59 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAIAABNmAgAEHloD//9HdEIAAUKzAgAAiFdCAAIgWwA==
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D833239@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <527018E7.3000406@innovationslab.net> <74470498B659FA4687F0B0018C19A89C01B87D83309E@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6A093@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D8331E3@IL-MB01.marvell.com> <26FBD265CD8D234EAF41115A180F92BB6ED6B1A2@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED6B1A2@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-31_03:2013-10-31, 2013-10-31, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310310007
X-SA-Exim-Connect-IP: 67.231.156.173
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Greg,

>I understand that this sentence describes how to distinguish a MAC from an extension field.  I see nothing which indicates whether 
>either should or should not be included, it is ambiguous in that respect.  Instead, I find very specific language just before that which 
>indicates that the presence of a MAC is mandatory, no?  

>Is there a particular reason to submit RFC5906 as the justification for the errata instead of the upcoming extension draft?

Well, as an innocent reader and an implementer I found these conflicting descriptions very confusing. We have had quite a bit of discussions on the NTP mailing list about whether it was possible to use an extension field without authentication according to the *existing* RFCs, and whether existing implementations would support this, and we found there were different interpretations by different people. 
For example, see the following thread from a couple of years ago:
http://lists.ntp.org/pipermail/ntpwg/2011-July/001698.html

My feeling is that the current text is not satisfactorily clear, and we need an immediate solution in the form of an erratum to clarify the ambiguity. The draft is a longer term solution, which also adds additional functionality that is not currently in RFC5905.

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com] 
Sent: Thursday, October 31, 2013 1:21 AM
To: Tal Mizrahi; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I understand that this sentence describes how to distinguish a MAC from an extension field.  I see nothing which indicates whether either should or should not be included, it is ambiguous in that respect.  Instead, I find very specific language just before that which indicates that the presence of a MAC is mandatory, no?  

Is there a particular reason to submit RFC5906 as the justification for the errata instead of the upcoming extension draft?

BTW, I'm going to drop the wider email list in favor of just Tal and the wg mailer so it doesn't keep getting stuck in the moderator queue after this.  Be forewarned :-)



-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 2:19 PM
To: Greg Dowd; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg,

> Can you clarify where exactly you see the justification in Section 10 of 5906?

Quoting section 10: "If the remaining length is greater than 22, an extension field is present."
(as we discussed it should be 24 rather than 22 - I think it was Dieter's catch BTW).

So based on this sentence (and the rest of the paragraph it is taken from), if you have a long extension field at the end of the packet, i.e., 7 words or longer, the parser processes it without looking for a MAC.

These parsing rules essentially allow you to use an extension field without a MAC, provided the extension field is long enough. Any implementation that complies to these parsing rules in fact already allows an extension field in the absence of a MAC.

Tal.


-----Original Message-----
From: Greg Dowd [mailto:gdowd@symmetricom.com]
Sent: Wednesday, October 30, 2013 6:34 PM
To: Tal Mizrahi; Brian Haberman; Danny Mayer; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

In my opinion, 5906 is the wrong source to point to when talking about extensions without MACs.  Section 4 says that the MAC is checked on every packet, with or without extensions.  The entire autokey protocol mandates MACs on every packet.  Section 9 has mechanisms defined for client and server operations, all of which include generating a MAC.  Section 10 specifies one or more extension fields "and the last followed by a MAC".

Again, I'm in favor of the new draft defining mechanisms for using extensions outside of autokey, I just don't think this errata is correctly framed.  By this argument, 5905 and 5906 are both "in error" because, honestly, the goal of the ntp working group in v4 was to document the existing mechanism and the existing mechanism mandates MAC with extensions.  It wasn't really a mistake and I don't see a conflict.  Instead, we now want to broaden the capabilities of the protocol.

Can you clarify where exactly you see the justification in Section 10 of 5906?  And how it would counteract all of the other language in 5906 mandating or implicitly requiring MACs?  Maybe I am missing something?  Otherwise, I would again vote to use your draft as the clarifying text once published.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Wednesday, October 30, 2013 5:05 AM
To: Brian Haberman; Danny Mayer; Greg Dowd; RFC Errata System; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Brian, 

The draft is indeed intended to update RFC 5905.

The reason for the erratum is that there currently seems to be a conflict between RFC5905 and RFC5906. It seems that this conflict should be documented as an erratum to allow the (innocent) reader to resolve this conflict.

One of Greg's points was that RFC5906 is informational, and thus should not be weighed against RFC5905 (standard track). And yet it seems that the problem is in fact in RFC5905, and hence I believe this erratum makes sense.

Thanks,
Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 10:22 PM
To: Danny Mayer; Greg Dowd; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Danny,
     Having a new document that updates 5905 for this is fine.  The question that Greg's statement raises is whether this erratum is valid given it seems to miss details in other sections of the RFC.  Do we need the erratum if we are going to be publishing a new RFC that specifies the extension field behavior?  I am assuming that this new document will be marked as updating 5905.

Regards,
Brian

On 10/29/13 4:04 PM, Danny Mayer wrote:
> I put into the extension field draft wording to update RFC 5905 when 
> dealing with the MAC making it clear that it is optional. That 
> document is standards track. Tal did this errata as an additional item.
> 
> Danny
> 
> On 10/29/2013 3:58 PM, Greg Dowd wrote:
>> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
>>
>> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
>>
>>
>> -----Original Message-----
>> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org
>> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
>> Of Brian Haberman
>> Sent: Tuesday, October 29, 2013 12:24 PM
>> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
>> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
>> ted.lemon@nominum.com; odonoghue@isoc.org
>> Cc: ntpwg@lists.ntp.org
>> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
>>
>> Hi Tal,
>>
>> On 5/17/13 12:28 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5905, "Network 
>>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>>
>>> Section: 7.5
>>>
>>> Original Text
>>> -------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>>
>>> Corrected Text
>>> --------------
>>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>>
>>>
>>> Notes
>>> -----
>>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>>
>>
>> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
>>
>> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
>>
>> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
>>
>> Regards,
>> Brian
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg
>>
>>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Oct 31 06:59:55 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFE0221E805D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 06:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.008
X-Spam-Level: 
X-Spam-Status: No, score=-6.008 tagged_above=-999 required=5 tests=[AWL=0.591, BAYES_00=-2.599, 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 0tD9H94QkEvX for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 06:59:50 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 684D311E822B for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 06:59:50 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4D5E586D5BF for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 13:59:50 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4A8D786D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 16:13:58 +0000 (UTC)
Received: from mail5.symmetricom.com ([69.25.98.10]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <btv1==01531eb1d8d==gdowd@symmetricom.com>) id 1VbYP5-0007pa-8U for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 16:13:58 +0000
X-ASG-Debug-ID: 1383149628-05bdbc07004d8e30001-dac64w
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id amHwFrhFJdQme6ez (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 09:13:48 -0700 (PDT)
X-Barracuda-Envelope-From: gdowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.121]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Wed, 30 Oct 2013 09:13:48 -0700
From: Greg Dowd <gdowd@symmetricom.com>
To: Tal Mizrahi <talmi@marvell.com>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>,  "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-ASG-Orig-Subj: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAQ1X8IAARuWQ
Date: Wed, 30 Oct 2013 16:13:48 +0000
Message-ID: <26FBD265CD8D234EAF41115A180F92BB6ED6A044@SJC-MBX-01.symmetricom.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.3.29]
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1383149628
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
X-SA-Exim-Connect-IP: 69.25.98.10
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: btv1==01531eb1d8d==gdowd@symmetricom.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 31 Oct 2013 13:59:32 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

It's a nit I guess but I still don't get 28 from the quoted language.  I see text that says "if greater than 22 bytes, an extension is present" and "extension must be greater than 8 and multiple of 4".  Hence 24, no?  Is there another rule forcing this minimum of 28?  I can see needing a couple padding bytes if there is a 22byte MAC but that is padding.


-----Original Message-----
From: Tal Mizrahi [mailto:talmi@marvell.com] 
Sent: Wednesday, October 30, 2013 4:59 AM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: RE: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Greg, 

>I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?

The minimal length of 28 bytes is applicable when there is a single extension field, or when there is more than one extension field the last one must be at least 28 bytes long. The 28 byte minimum was not intended as a placeholder, but as a lower bound that is intended to be backward compatible with the parsing rules defined in section 10 of RFC5906:

   One or more extension fields follow the NTP packet header and the
   last followed by the MAC.  The extension field parser initializes a
   pointer to the first octet beyond the NTP packet header and
   calculates the number of octets remaining to the end of the packet If
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID), the remaining data are the MAC
   and parsing is complete.  If the remaining length is greater than 22,
   an extension field is present.  If the remaining length is less than
   8 or not a multiple of 4, a format error has occurred and the packet
   is discarded; otherwise, the parser increments the pointer by the
   extension field length and then uses the same rules as above to
   determine whether a MAC is present or another extension field.


Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg Dowd
Sent: Tuesday, October 29, 2013 9:58 PM
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last followed by the MAC."

I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Oct 31 07:00:02 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1D721E805D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 07:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.636
X-Spam-Level: 
X-Spam-Status: No, score=-5.636 tagged_above=-999 required=5 tests=[AWL=0.963, BAYES_00=-2.599, 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 AXyB9MFcpBd4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 06:59:57 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 5315711E8196 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 06:59:57 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 0606486DB42 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 13:59:57 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 08A2386D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 11:58:35 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbUPx-0006Rd-E4 for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 11:58:35 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9UBw6xs026919; Wed, 30 Oct 2013 04:58:06 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1ftb2tng48-13 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Oct 2013 04:58:06 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 30 Oct 2013 04:58:01 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Wed, 30 Oct 2013 13:54:33 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <gdowd@symmetricom.com>, "mayer@ntp.org" <mayer@ntp.org>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>, "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Wed, 30 Oct 2013 13:54:31 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAHkjAP//i/VggAEHKoA=
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D83307C@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com> <527014D6.20105@ntp.org> <26FBD265CD8D234EAF41115A180F92BB6ED69367@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED69367@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-30_04:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310300060
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 31 Oct 2013 13:59:38 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Greg, 

As clarified in draft-mizrahi-ntp-extension-field:

- the minimal length of an extension field is 16 bytes.
- *specifically* in the absence of a MAC (section 3.2 in the draft):
   o If the packet includes a single extension field, the length of the
      extension field MUST be at least 7 words, i.e., at least 28
      octets.

   o If the packet includes more than one extension field, the length
      of the last extension field MUST be at least 28 octets. The length
      of the other extension fields in this case MUST be at least 16
      octets each, as defined in [RFC5905].


Does this make sense?

Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg Dowd
Sent: Tuesday, October 29, 2013 10:18 PM
To: mayer@ntp.org; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I'd like to see the extension field doc become a working group doc and completed and it can then become the logic for an errata against 5905.  Also, a quick look at the draft shows that a single extension field can be 16 bytes?  That doesn't seem right unless you also constrain the MAC to a minimum above that.  It also disagrees with Tal's errata?

-----Original Message-----
From: Danny Mayer [mailto:mayer@ntp.org]
Sent: Tuesday, October 29, 2013 1:05 PM
To: Greg Dowd; Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I put into the extension field draft wording to update RFC 5905 when dealing with the MAC making it clear that it is optional. That document is standards track. Tal did this errata as an additional item.

Danny

On 10/29/2013 3:58 PM, Greg Dowd wrote:
> I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.
> 
> In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?
> 
> 
> -----Original Message-----
> From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org 
> [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf 
> Of Brian Haberman
> Sent: Tuesday, October 29, 2013 12:24 PM
> To: RFC Errata System; mills@udel.edu; jrmii@isc.org; 
> jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; 
> ted.lemon@nominum.com; odonoghue@isoc.org
> Cc: ntpwg@lists.ntp.org
> Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
> 
> Hi Tal,
> 
> On 5/17/13 12:28 PM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC5905, "Network 
>> Time Protocol Version 4: Protocol and Algorithms Specification".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Tal Mizrahi <talmi@marvell.com>
>>
>> Section: 7.5
>>
>> Original Text
>> -------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
>>
>> Corrected Text
>> --------------
>> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
>> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
>> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
>>
>>
>> Notes
>> -----
>> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>>
> 
> While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:
> 
> "One or more extension fields follow the NTP packet header and the last followed by the MAC."
> 
> I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.
> 
> Regards,
> Brian
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
> 
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Oct 31 07:00:06 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5E321E805D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 07:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.686
X-Spam-Level: 
X-Spam-Status: No, score=-5.686 tagged_above=-999 required=5 tests=[AWL=0.913, BAYES_00=-2.599, 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 9IXaV4WMGJui for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 31 Oct 2013 07:00:00 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id B608911E8226 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 07:00:00 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id B5B6F86DB19 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 31 Oct 2013 14:00:00 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id BE9E486D4E3 for <ntpwg@lists.ntp.org>; Wed, 30 Oct 2013 11:59:07 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1VbUQT-0006Rr-EQ for ntpwg@lists.ntp.org; Wed, 30 Oct 2013 11:59:07 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id r9UBwkXb027266; Wed, 30 Oct 2013 04:58:46 -0700
Received: from sc-owa01.marvell.com ([199.233.58.136]) by mx0a-0016f401.pphosted.com with ESMTP id 1ftb2tng73-25 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Oct 2013 04:58:46 -0700
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 30 Oct 2013 04:58:46 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Wed, 30 Oct 2013 13:58:39 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Greg Dowd <gdowd@symmetricom.com>, Brian Haberman <brian@innovationslab.net>, RFC Errata System <rfc-editor@rfc-editor.org>, "mills@udel.edu" <mills@udel.edu>, "jrmii@isc.org" <jrmii@isc.org>, "jack.burbank@jhuapl.edu" <jack.burbank@jhuapl.edu>, "william.kasch@jhuapl.edu" <william.kasch@jhuapl.edu>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Date: Wed, 30 Oct 2013 13:58:38 +0200
Thread-Topic: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
Thread-Index: AQHOU9JxFVfavEgcaE6yN/rEMIS1F5oNhqkA//+SGHCAAQ1X8A==
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D833082@IL-MB01.marvell.com>
References: <20130517162852.7C5D06210B@rfc-editor.org> <52700B6A.5040204@innovationslab.net> <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>
In-Reply-To: <26FBD265CD8D234EAF41115A180F92BB6ED692B4@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-30_04:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1310300060
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 31 Oct 2013 13:59:38 +0000
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi Greg, 

>I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?

The minimal length of 28 bytes is applicable when there is a single extension field, or when there is more than one extension field the last one must be at least 28 bytes long. The 28 byte minimum was not intended as a placeholder, but as a lower bound that is intended to be backward compatible with the parsing rules defined in section 10 of RFC5906:

   One or more extension fields follow the NTP packet header and the
   last followed by the MAC.  The extension field parser initializes a
   pointer to the first octet beyond the NTP packet header and
   calculates the number of octets remaining to the end of the packet If
   the remaining length is 20 (128-bit digest plus 4-octet key ID) or 22
   (160-bit digest plus 4-octet key ID), the remaining data are the MAC
   and parsing is complete.  If the remaining length is greater than 22,
   an extension field is present.  If the remaining length is less than
   8 or not a multiple of 4, a format error has occurred and the packet
   is discarded; otherwise, the parser increments the pointer by the
   extension field length and then uses the same rules as above to
   determine whether a MAC is present or another extension field.


Tal.


-----Original Message-----
From: ntpwg-bounces+talmi=marvell.com@lists.ntp.org [mailto:ntpwg-bounces+talmi=marvell.com@lists.ntp.org] On Behalf Of Greg Dowd
Sent: Tuesday, October 29, 2013 9:58 PM
To: Brian Haberman; RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

I don't think this is a bad idea per se but I think this errata entry is incomplete and ambiguous.  There are other places in 5905 which call out MAC and extensions which should also be addressed.  I have a little heartburn with the fact that it is using 5906, an informational RFC, as an argument for modifying a standards track document.  Also, it is disingenuous to present 5906 as logic for removing MAC requirement.  5906 is entirely predicated on the requirement that a MAC be present whenever extensions are present.

In conclusion, I like the idea of clarifying the extension/MAC relationship but I think the errata should consider 2 elements, first a complete review of 5905 for MAC/extensions details for consistency, including a better argument justifying the change, and second, an informal review of future-proofing the MAC by size since I see that Tal has allocated what appears to be 4 more bytes than absolutely necessary perhaps as a placeholder for a different MAC schema?


-----Original Message-----
From: ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf Of Brian Haberman
Sent: Tuesday, October 29, 2013 12:24 PM
To: RFC Errata System; mills@udel.edu; jrmii@isc.org; jack.burbank@jhuapl.edu; william.kasch@jhuapl.edu; ted.lemon@nominum.com; odonoghue@isoc.org
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] [Technical Errata Reported] RFC5905 (3627)

Hi Tal,

On 5/17/13 12:28 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5905, "Network 
> Time Protocol Version 4: Protocol and Algorithms Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5905&eid=3627
> 
> --------------------------------------
> Type: Technical
> Reported by: Tal Mizrahi <talmi@marvell.com>
> 
> Section: 7.5
> 
> Original Text
> -------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, which is always present when an extension field is present.
> 
> Corrected Text
> --------------
> In NTPv4, one or more extension fields can be inserted after the header and before the MAC, if a MAC is present. If a MAC is not present, one or more extension fields can be inserted after the header, according to the following rules:
> o If the packet includes a single extension field, the length of the extension field MUST be at least 7 words, i.e., at least 28 octets.
> o If the packet includes more than one extension field, the length of the last extension field MUST be at least 28 octets. The length of the other extension fields in this case MUST be at least 16 octets each.
> 
> 
> Notes
> -----
> The usage of NTP extension fields without authentication is aligned with Section 10 of RFC 5906:
>

While the text you quote below is correct, it does not include the sentence immediately precedes it.  That sentence states:

"One or more extension fields follow the NTP packet header and the last followed by the MAC."

I don't think that changes the intent of your text, but it does leave that text lacking in clarity saying that a MAC must be added after the extension if it is not present.

Regards,
Brian

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
