From mills at udel.edu  Thu Feb  1 10:24:26 2007
From: mills at udel.edu (David L. Mills)
Date: Thu, 01 Feb 2007 18:24:26 +0000
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>
References: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>
Message-ID: <45C2305A.5050307@udel.edu>

Odonoghue, Karen F CIV NSWCDD, W13 wrote:

> Thanks Harlan!
>
> Karen
>
> -----Original Message-----
> From: Harlan Stenn <stenn at ntp.isc.org>
> To: Brian Haberman <brian at innovationslab.net>
> CC: Harlan Stenn <stenn at ntp.isc.org>; Odonoghue, Karen F CIV NSWCDD, 
> W13; ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
> Sent: Wed Jan 31 21:48:04 2007
> Subject: Re: [ntpwg] updated ntpv4 draft available
>
> Brian,
>
> I've updated http://ntp.isc.org/IETF with the mailing list info.
>
> H
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070201/8ddcf410/attachment.html 

From mills at udel.edu  Thu Feb  1 11:00:16 2007
From: mills at udel.edu (David L. Mills)
Date: Thu, 01 Feb 2007 19:00:16 +0000
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>
References: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>
Message-ID: <45C238C0.2010008@udel.edu>

Guys,

I've reviewed about a third of the document and made lots and lots of 
markups. There are misplaced tables, figure descripancies and figure 
errors. These are all fixable, but does call into question the last call 
status. This is definitely not in last call status. The most serious 
problems are inconsistent variable names.

It would be a serious effort to list each and every markup; there are 
dozens and dozens of them. What I propose is to mark up a copy of the 
current document in ASCII and return it for diffing, further markup and 
reformatting. I can do the text part, but not the table and figure 
references and tables and figures themselves.

I could simply send the paper markup, but even this is a lot more work 
than I would like. I would rather speed through the edit with my 
favorite eye-friendly editor and search and destroy inconsistencies as I 
find them.

It would be polite to reference my earlier report as a source of much 
information included in the RFC. It would be of considerable help to a 
serious implementer to point out, maybe in a footnote, the detailed 
rationale and performance analysis for some of the more intricate 
algorithms can be found in my book and/or the NTP website.

Dave

 Odonoghue, Karen F CIV NSWCDD, W13 wrote:

> Thanks Harlan!
>
> Karen
>
> -----Original Message-----
> From: Harlan Stenn <stenn at ntp.isc.org>
> To: Brian Haberman <brian at innovationslab.net>
> CC: Harlan Stenn <stenn at ntp.isc.org>; Odonoghue, Karen F CIV NSWCDD, 
> W13; ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
> Sent: Wed Jan 31 21:48:04 2007
> Subject: Re: [ntpwg] updated ntpv4 draft available
>
> Brian,
>
> I've updated http://ntp.isc.org/IETF with the mailing list info.
>
> H
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070201/a63337c9/attachment.html 

From jim at daedelus.com  Thu Feb  1 11:37:53 2007
From: jim at daedelus.com (Jim Martin)
Date: Thu, 1 Feb 2007 11:37:53 -0800
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <45C238C0.2010008@udel.edu>
References: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>
	<45C238C0.2010008@udel.edu>
Message-ID: <DAAC924D-1AAA-41E9-8E13-667381CC86A6@daedelus.com>

Dr Mills,
	Thanks very much for starting the review. Your previous comments  
were very helpful in cleaning things up quite a bit. From todays  
comments,it seems there's more to be done, so I'd be happy to work  
with you in whatever way is easiest.

	As for the attribution, I think we'd be happy to reference your book  
as a non-normative informational reference, and your earlier report  
should indeed be mentioned in the acknowledgments.

	On a more general note to all list members, I just want to continue  
to stress the editing teams desire to finish up this document in a  
timely manner.  To that end, I again ask that people review and  
comment on the -04 draft and allow us to come up with a solid -05  
before the Prague cut off. That means getting reviews back with  
specific, detailed comments before February 26th, which would give  
the editors one week to integrate the changes and make the draft  
submission deadline. Karen, Brian, do you agree?

	- Jim

On Feb 1, 2007, at 11:00 AM, David L. Mills wrote:

> Guys,
>
> I've reviewed about a third of the document and made lots and lots  
> of markups. There are misplaced tables, figure descripancies and  
> figure errors. These are all fixable, but does call into question  
> the last call status. This is definitely not in last call status.  
> The most serious problems are inconsistent variable names.
>
> It would be a serious effort to list each and every markup; there  
> are dozens and dozens of them. What I propose is to mark up a copy  
> of the current document in ASCII and return it for diffing, further  
> markup and reformatting. I can do the text part, but not the table  
> and figure references and tables and figures themselves.
>
> I could simply send the paper markup, but even this is a lot more  
> work than I would like. I would rather speed through the edit with  
> my favorite eye-friendly editor and search and destroy  
> inconsistencies as I find them.
>
> It would be polite to reference my earlier report as a source of  
> much information included in the RFC. It would be of considerable  
> help to a serious implementer to point out, maybe in a footnote,  
> the detailed rationale and performance analysis for some of the  
> more intricate algorithms can be found in my book and/or the NTP  
> website.
>
> Dave
>
>  Odonoghue, Karen F CIV NSWCDD, W13 wrote:
>> Thanks Harlan!
>>
>> Karen
>>
>> -----Original Message-----
>> From: Harlan Stenn <stenn at ntp.isc.org>
>> To: Brian Haberman <brian at innovationslab.net>
>> CC: Harlan Stenn <stenn at ntp.isc.org>; Odonoghue, Karen F CIV  
>> NSWCDD, W13; ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
>> Sent: Wed Jan 31 21:48:04 2007
>> Subject: Re: [ntpwg] updated ntpv4 draft available
>>
>> Brian,
>>
>> I've updated http://ntp.isc.org/IETF with the mailing list info.
>>
>> H
>>
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg at lists.ntp.isc.org
>> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070201/1b9e5b3b/attachment.html 

From brian at innovationslab.net  Thu Feb  1 12:12:28 2007
From: brian at innovationslab.net (Brian Haberman)
Date: Thu, 01 Feb 2007 15:12:28 -0500
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <DAAC924D-1AAA-41E9-8E13-667381CC86A6@daedelus.com>
References: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>	<45C238C0.2010008@udel.edu>
	<DAAC924D-1AAA-41E9-8E13-667381CC86A6@daedelus.com>
Message-ID: <45C249AC.8040308@innovationslab.net>

Jim,
     Agree in principle.  I would *strongly* encourage people to get
comments to the editors or the mailing list by February 23.  That will
give the editors sufficient time to incorporate changes or engage people
in discussions on issues before making changes prior to the draft deadline.

Regards,
Brian


Jim Martin wrote:
> Dr Mills,
> Thanks very much for starting the review. Your previous comments were
> very helpful in cleaning things up quite a bit. From todays comments,it
> seems there's more to be done, so I'd be happy to work with you in
> whatever way is easiest. 
> 
> As for the attribution, I think we'd be happy to reference your book as
> a non-normative informational reference, and your earlier report should
> indeed be mentioned in the acknowledgments. 
> 
> On a more general note to all list members, I just want to continue to
> stress the editing teams desire to finish up this document in a timely
> manner.  To that end, I again ask that people review and comment on the
> -04 draft and allow us to come up with a solid -05 before the Prague cut
> off. That means getting reviews back with specific, detailed comments
> before February 26th, which would give the editors one week to integrate
> the changes and make the draft submission deadline. Karen, Brian, do you
> agree?
> 
> - Jim
> 
> On Feb 1, 2007, at 11:00 AM, David L. Mills wrote:
> 
>> Guys,
>>
>> I've reviewed about a third of the document and made lots and lots of
>> markups. There are misplaced tables, figure descripancies and figure
>> errors. These are all fixable, but does call into question the last
>> call status. This is definitely not in last call status. The most
>> serious problems are inconsistent variable names.
>>
>> It would be a serious effort to list each and every markup; there are
>> dozens and dozens of them. What I propose is to mark up a copy of the
>> current document in ASCII and return it for diffing, further markup
>> and reformatting. I can do the text part, but not the table and figure
>> references and tables and figures themselves.
>>
>> I could simply send the paper markup, but even this is a lot more work
>> than I would like. I would rather speed through the edit with my
>> favorite eye-friendly editor and search and destroy inconsistencies as
>> I find them.
>>
>> It would be polite to reference my earlier report as a source of much
>> information included in the RFC. It would be of considerable help to a
>> serious implementer to point out, maybe in a footnote, the detailed
>> rationale and performance analysis for some of the more intricate
>> algorithms can be found in my book and/or the NTP website.
>>
>> Dave
>>
>>  Odonoghue, Karen F CIV NSWCDD, W13 wrote:
>>> Thanks Harlan!
>>>
>>> Karen
>>>
>>> -----Original Message-----
>>> From: Harlan Stenn <stenn at ntp.isc.org>
>>> To: Brian Haberman <brian at innovationslab.net>
>>> CC: Harlan Stenn <stenn at ntp.isc.org>; Odonoghue, Karen F CIV NSWCDD,
>>> W13; ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
>>> Sent: Wed Jan 31 21:48:04 2007
>>> Subject: Re: [ntpwg] updated ntpv4 draft available
>>>
>>> Brian,
>>>
>>> I've updated http://ntp.isc.org/IETF with the mailing list info.
>>>
>>> H
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> ntpwg mailing list
>>> ntpwg at lists.ntp.isc.org
>>> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg at lists.ntp.isc.org <mailto:ntpwg at lists.ntp.isc.org>
>> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg

From mills at udel.edu  Fri Feb  2 10:14:33 2007
From: mills at udel.edu (David L. Mills)
Date: Fri, 02 Feb 2007 18:14:33 +0000
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <45C14014.8030409@innovationslab.net>
References: <20070131224658.BA2F939C99@ntp1.ntp.isc.org>
	<45C14014.8030409@innovationslab.net>
Message-ID: <45C37F89.8070106@udel.edu>

Brian,

Attached is a marked up version of the draft portion before the 
individual process descriptions. There are so manny errors and 
inconsistencies in the later material that I don't think a diff will be 
readable, so I may reformat it in paragraph lines. I do not anticipate 
marking up the appendix, but I do see my careful tab formatting has been 
lost and the code is very hard to read. It would not seem a problem to 
put the tabs or whitespace back in.

Dave

Brian Haberman wrote:

> Harlen,
> Comments should be made/discussed on ntpwg at ntp.isc.org (the
> official NTP WG mailing list).
>
> Regards,
> Brian
>
>
> Harlan Stenn wrote:
>
>> Hey Karen,
>>
>> I've put the information you mentioned on http://ntp.isc.org/IETF .
>>
>> You wrote:
>>
>>> Please review this document and send any comments to the list.
>>> Based on comments received, we will be proceeding to WG Last Call
>>> shortly.
>>
>> At the end of that first sentence, you asked people to send comments "to
>> the list".
>>
>> What is this list of which you speak? I'd like to leave better
>> instructions for folks who see this on our website.
>>
>> H
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg at lists.ntp.isc.org
>> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070202/77aa59ca/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: NTPV4.TXT
Url: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070202/77aa59ca/attachment-0001.ksh 

From mills at udel.edu  Mon Feb  5 11:23:13 2007
From: mills at udel.edu (David L. Mills)
Date: Mon, 05 Feb 2007 19:23:13 +0000
Subject: [ntpwg] updated ntpv4 draft available
In-Reply-To: <45C249AC.8040308@innovationslab.net>
References: <2E44C2268B59514C89AE2CB514D15ACA61D01B@NAEAMILLEX01VA.nadsusea.nads.navy.mil>	<45C238C0.2010008@udel.edu>
	<DAAC924D-1AAA-41E9-8E13-667381CC86A6@daedelus.com>
	<45C249AC.8040308@innovationslab.net>
Message-ID: <45C78421.7030701@udel.edu>

Brian,

On re-review I found additional serious errors in the draft.

1. Figure numbering is inconsistent and wrong in places. Figures 1 and 4 
are the same diagram.

2. The skeleton appendix is all messed up. Some tokens are joined, some 
lines are missing and some are broken in the middle of a token. There is 
a block of about 20 lines missing in the middle of a routine.

3. You guys did a commendable job in bashing the tables, which look just 
fine, and the figures, but some figures seriously resist bash and are 
really hard to decipher. One of the most important figures, that for the 
poll process, is missing.

4. Some variable names are confusing and some are inconsistent. For 
instance, the naming convention for upper case Greek is sometimes to 
precede the lower case name with cap, other cases simply capitalize the 
Greek name. I never did figure out where the variable varphi came from 
or that the prefix var means. There are several misuses of the Greek 
names phi and psi.

5. Reading carefully for content, there are several cases where the text 
is just plain wrong. Some of that is my fault in the original, some of 
it is lost in translation.

6. There are several places where figures and tables are broken between 
pages, but that's a formatting issue, presumably easily fixed.

Well, that's the bad news. Now for what I hope is good news.

I spent the last four days carefully reading and revising the text, 
repairing and verifying from the original the skeleton and revising the 
variable names for consistency and correctness. I took out all the 
Postel formatting, which would be useless anyway, removed the more 
obnoxious figures and revised the text to emphasize the skeleton for 
detail rather than the figures. Where figures really did help, I left 
them in.

ALong the way, I renumbered the tables and figures and left a list of 
each just before the document. I checked the table and figure referenced 
in the text and corrected what broke. I assume you can stuff the lists 
in at the right place and have your document processor do the formatting 
and page numbering.

I read every sentence in the draft and considered whether it was 
necessary, accurate or poorly written. I read the whole thing in part 
and in whole several times. Just like I did for my book.

I pulled out all references to my book and put a note near the beginning 
that additional information is available in the book, the UDel report 
and the web site.

I have a few residual concerns.

1. Those considering SNTP viz. full NTP will need to read up through the 
end of the on-wire section and they might not have the patience for 
that. Perhaps mention of this should be early in the presentation.

2. There remain a few inconsistencies between the variable names defined 
in the text and in those defined in the appendix. I am too exhausted to 
fix that. In any case the text is consistent and the appendix is consistent.

3. While I fixed the little broken things with the tables, the figures 
might be improved. I invite the graphic artists among us to help with that.

My expectation is that the text itself without the skeleton is 
sufficient for most folks who only want to know how it works and not the 
details. I read it through with this in mind and it works for me. The 
bottom line is whether a skilled programmer can engulf the thing and be 
able to implement a conforming implementation and verify with the 
reference implementation. I invite discussion on this point.

The latest draft is attached. It is a bit smaller than before, since I 
pulled out some extraneous material in the clock discipline section. It 
is in the classic form of one sentence per paragraph, which should be 
easy to format. May I suggest this as the basis for comments and markup 
and save the formatting for the final draft?

If you wish, I can do the markup, either in response to general guidance 
or specific typos. I encourage this, as the ancient text editor I use 
(word5!) is eye-friendly for folks with dim vision and modern editors 
are not. I'm not sure if diff works with long lines, but I do reserve 
the right to fix broken things that I might find myself.

If/when we all agree, you or designate can do the magic reformatting and 
distribute for last call. This can all happen by the deadline.

Dave

Brian Haberman wrote:

> Jim,
>      Agree in principle.  I would *strongly* encourage people to get
> comments to the editors or the mailing list by February 23.  That will
> give the editors sufficient time to incorporate changes or engage people
> in discussions on issues before making changes prior to the draft deadline.
> 
> Regards,
> Brian
> 
> 
> Jim Martin wrote:
> 
>>Dr Mills,
>>Thanks very much for starting the review. Your previous comments were
>>very helpful in cleaning things up quite a bit. From todays comments,it
>>seems there's more to be done, so I'd be happy to work with you in
>>whatever way is easiest. 
>>
>>As for the attribution, I think we'd be happy to reference your book as
>>a non-normative informational reference, and your earlier report should
>>indeed be mentioned in the acknowledgments. 
>>
>>On a more general note to all list members, I just want to continue to
>>stress the editing teams desire to finish up this document in a timely
>>manner.  To that end, I again ask that people review and comment on the
>>-04 draft and allow us to come up with a solid -05 before the Prague cut
>>off. That means getting reviews back with specific, detailed comments
>>before February 26th, which would give the editors one week to integrate
>>the changes and make the draft submission deadline. Karen, Brian, do you
>>agree?
>>
>>- Jim
>>
>>On Feb 1, 2007, at 11:00 AM, David L. Mills wrote:
>>
>>
>>>Guys,
>>>
>>>I've reviewed about a third of the document and made lots and lots of
>>>markups. There are misplaced tables, figure descripancies and figure
>>>errors. These are all fixable, but does call into question the last
>>>call status. This is definitely not in last call status. The most
>>>serious problems are inconsistent variable names.
>>>
>>>It would be a serious effort to list each and every markup; there are
>>>dozens and dozens of them. What I propose is to mark up a copy of the
>>>current document in ASCII and return it for diffing, further markup
>>>and reformatting. I can do the text part, but not the table and figure
>>>references and tables and figures themselves.
>>>
>>>I could simply send the paper markup, but even this is a lot more work
>>>than I would like. I would rather speed through the edit with my
>>>favorite eye-friendly editor and search and destroy inconsistencies as
>>>I find them.
>>>
>>>It would be polite to reference my earlier report as a source of much
>>>information included in the RFC. It would be of considerable help to a
>>>serious implementer to point out, maybe in a footnote, the detailed
>>>rationale and performance analysis for some of the more intricate
>>>algorithms can be found in my book and/or the NTP website.
>>>
>>>Dave
>>>
>>> Odonoghue, Karen F CIV NSWCDD, W13 wrote:
>>>
>>>>Thanks Harlan!
>>>>
>>>>Karen
>>>>
>>>>-----Original Message-----
>>>>From: Harlan Stenn <stenn at ntp.isc.org>
>>>>To: Brian Haberman <brian at innovationslab.net>
>>>>CC: Harlan Stenn <stenn at ntp.isc.org>; Odonoghue, Karen F CIV NSWCDD,
>>>>W13; ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
>>>>Sent: Wed Jan 31 21:48:04 2007
>>>>Subject: Re: [ntpwg] updated ntpv4 draft available
>>>>
>>>>Brian,
>>>>
>>>>I've updated http://ntp.isc.org/IETF with the mailing list info.
>>>>
>>>>H
>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>_______________________________________________
>>>>ntpwg mailing list
>>>>ntpwg at lists.ntp.isc.org
>>>>https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>>>
>>>_______________________________________________
>>>ntpwg mailing list
>>>ntpwg at lists.ntp.isc.org <mailto:ntpwg at lists.ntp.isc.org>
>>>https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>ntpwg mailing list
>>ntpwg at lists.ntp.isc.org
>>https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: NTPV4.TXT
Url: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070205/ab9d7f2e/attachment-0001.ksh 

From mills at udel.edu  Fri Feb  9 20:40:41 2007
From: mills at udel.edu (David L. Mills)
Date: Sat, 10 Feb 2007 04:40:41 +0000
Subject: [ntpwg] Updated draft
Message-ID: <45CD4CC9.1020405@udel.edu>

Guys,

An updated draft of the NTP document is linked from the NTP project page 
at www.ntp.org.

1. The manycast server discovery scheme has been added to the skeleton 
and the skeleton recomplied for error check. Several small details were 
changed to match corresponding changes in the reference implementation. 
The updated skeleton has been snipped into the draft.

2. Text has been added in various places to describe the manycast sheme 
and how it works.

3. The SNTP protocol subset now has a separate section. The implementer 
wishing to build SNTP can avoid eye fatigue with the full NTP prose.

4. Again once through the entire text picked up some weeds and 
wastewater, both flushed. Some figure numberring errors were fixed in 
the ToC.

It's still in unformatted format; the long lines are correctly wrapped 
in IE, but for some reason double spaced. Note that there is a generous 
helping of tab characters which hopefully the formatter will respect. 
They certainly were not respected in the orignal draft.

Dave

From mayer at ntp.isc.org  Sun Feb 11 13:51:40 2007
From: mayer at ntp.isc.org (Danny Mayer)
Date: Sun, 11 Feb 2007 16:51:40 -0500
Subject: [ntpwg] Updated draft
In-Reply-To: <45CD4CC9.1020405@udel.edu>
References: <45CD4CC9.1020405@udel.edu>
Message-ID: <45CF8FEC.1000007@ntp.isc.org>

That's exactly what I wanted. Otherwise I would have opposed it going
forward with it obsoleting RFC 4330. I think I'll start reviewing your
edited version instead.

Danny

David L. Mills wrote:
> 
> 3. The SNTP protocol subset now has a separate section. The implementer 
> wishing to build SNTP can avoid eye fatigue with the full NTP prose.
> 

From stbryant at cisco.com  Mon Feb 12 03:43:51 2007
From: stbryant at cisco.com (Stewart Bryant)
Date: Mon, 12 Feb 2007 11:43:51 +0000
Subject: [ntpwg] TICTOC scheduled for IETF68 (Prague)
Message-ID: <45D052F7.5000209@cisco.com>


The TICTOC BOF has been scheduled for Tuesday 20th March
0900 to 1130.

More information on TICTOC can be obtained from:

http://www1.tools.ietf.org/bof/trac/wiki#TimeframeIETF68Prague

It's not yet determined who will be chairing the BOF and
the detailed agenda is still being worked on. In the
meantime I suggest that those that wish to present on
this topic send requests to the TICTOC list.

Stewart


PS: for those not familiar with IETF procedures, the
IETF agenda will not be final until much closer to the
meeting, so please keep an eye on the IETF agenda page

https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=68

From Helen.Y.Chen at motorola.com  Mon Feb 12 07:45:59 2007
From: Helen.Y.Chen at motorola.com (Chen Helen-A12587)
Date: Mon, 12 Feb 2007 10:45:59 -0500
Subject: [ntpwg] Updated draft
In-Reply-To: <45CF8FEC.1000007@ntp.isc.org>
References: <45CD4CC9.1020405@udel.edu> <45CF8FEC.1000007@ntp.isc.org>
Message-ID: <655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>

Danny, David,

The link I tried (draft-ietf-ntp-ntpv4-proto-04) didn't work. I would
like to know if SNTPv4 includes the sutokey algorithm, or if the autokey
can only be implemented in NTPv4.

Thanks,
Helen Chen

-----Original Message-----
From: ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org
[mailto:ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org] On
Behalf Of Danny Mayer
Sent: Sunday, February 11, 2007 3:52 PM
To: David L. Mills
Cc: ntpwg at ntp.isc.org
Subject: Re: [ntpwg] Updated draft

That's exactly what I wanted. Otherwise I would have opposed it going
forward with it obsoleting RFC 4330. I think I'll start reviewing your
edited version instead.

Danny

David L. Mills wrote:
> 
> 3. The SNTP protocol subset now has a separate section. The 
> implementer wishing to build SNTP can avoid eye fatigue with the full
NTP prose.
> 
_______________________________________________
ntpwg mailing list
ntpwg at lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/ntpwg

From mills at udel.edu  Mon Feb 12 16:26:15 2007
From: mills at udel.edu (David L. Mills)
Date: Tue, 13 Feb 2007 00:26:15 +0000
Subject: [ntpwg] Updated draft
In-Reply-To: <655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
References: <45CD4CC9.1020405@udel.edu> <45CF8FEC.1000007@ntp.isc.org>
	<655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
Message-ID: <45D105A7.10603@udel.edu>

Chen,

The document is now restored. The Windwoes name was in upper case; the 
Unix link in lower case. Sign.

There is no provision for Autokey in the standards document. In 
prinicple there could be, but it doesn't seem useful to add all that 
baggage and not make a NTP-conformant version. I'm happy to add that 
option to the SNTP text if this seems desirable.

Dave

Chen Helen-A12587 wrote:

> Danny, David,
>
> The link I tried (draft-ietf-ntp-ntpv4-proto-04) didn't work. I would
> like to know if SNTPv4 includes the sutokey algorithm, or if the autokey
> can only be implemented in NTPv4.
>
> Thanks,
> Helen Chen
>
> -----Original Message-----
> From: ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org
> [mailto:ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org] On
> Behalf Of Danny Mayer
> Sent: Sunday, February 11, 2007 3:52 PM
> To: David L. Mills
> Cc: ntpwg at ntp.isc.org
> Subject: Re: [ntpwg] Updated draft
>
> That's exactly what I wanted. Otherwise I would have opposed it going
> forward with it obsoleting RFC 4330. I think I'll start reviewing your
> edited version instead.
>
> Danny
>
> David L. Mills wrote:
>
>> 3. The SNTP protocol subset now has a separate section. The
>> implementer wishing to build SNTP can avoid eye fatigue with the full
>
> NTP prose.
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070213/fc484fa4/attachment.html 

From mayer at ntp.isc.org  Mon Feb 12 19:23:37 2007
From: mayer at ntp.isc.org (Danny Mayer)
Date: Mon, 12 Feb 2007 22:23:37 -0500
Subject: [ntpwg] Updated draft
In-Reply-To: <655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
References: <45CD4CC9.1020405@udel.edu> <45CF8FEC.1000007@ntp.isc.org>
	<655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
Message-ID: <45D12F39.6010501@ntp.isc.org>

Chen Helen-A12587 wrote:
> Danny, David,
> 
> The link I tried (draft-ietf-ntp-ntpv4-proto-04) didn't work. I would
> like to know if SNTPv4 includes the sutokey algorithm, or if the autokey
> can only be implemented in NTPv4.
> 
> Thanks,
> Helen Chen

While I'm sure you could add autokey to SNTP, by the time you had done
so and incorporated all of the necessary machinery it might as well be
NTP rather than SNTP. Unlike SNTP, the autokey needs to have the client
exchange a flurry of packets with the server to authenticate the server
initially before it is willing to accept the time from that server. Dave
calls this the autokey dance, I believe. I see no reason why it can't be
done but I know of no such implementation.

I assume you want to supply accurate time to cell phones, but want to
make sure that it comes from an authenticated source? You also have a
key distribution problem to solve.

Danny

From GDowd at symmetricom.com  Thu Feb 15 14:00:22 2007
From: GDowd at symmetricom.com (Greg Dowd)
Date: Thu, 15 Feb 2007 14:00:22 -0800
Subject: [ntpwg] Timing Definitions
Message-ID: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com>

Some standard uses for reference with ntp:

precision:  This defines the smallest measurement which can actually be
made.  It helps to define the number of significant bits in a
measurement.
resolution:  This defines the total number of bits available to express
a measurement.  It tells you nothing about the value of any of those
bits.
accuracy:  This defines how well a measurement agrees with a timescale
(e.g., UTC).



Greg Dowd
gdowd at symmetricom dot com (antispam format)
Symmetricom, Inc. 
www.symmetricom.com
"The current implementation is non-obvious and may need to be improved."




-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070215/4b95419c/attachment.html 

From stenn at ntp.isc.org  Fri Feb 16 00:36:15 2007
From: stenn at ntp.isc.org (Harlan Stenn)
Date: Fri, 16 Feb 2007 08:36:15 +0000
Subject: [ntpwg] Document update
Message-ID: <20070216083626.51F2B39CE3@ntp1.ntp.isc.org>

The document needs to be checked against the latest ntp_loopfilter.c to
see if the changes for http://bugs.ntp.isc.org/778 need to be included.

H

From mills at udel.edu  Fri Feb 16 08:49:41 2007
From: mills at udel.edu (David L. Mills)
Date: Fri, 16 Feb 2007 16:49:41 +0000
Subject: [ntpwg] Document update
In-Reply-To: <20070216083626.51F2B39CE3@ntp1.ntp.isc.org>
References: <20070216083626.51F2B39CE3@ntp1.ntp.isc.org>
Message-ID: <45D5E0A5.10806@udel.edu>

Harlan,

No. The document does not discuss the kernel functions.

Dave

Harlan Stenn wrote:

> The document needs to be checked against the latest ntp_loopfilter.c to
> see if the changes for http://bugs.ntp.isc.org/778 need to be included.
>
> H
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg



From mills at udel.edu  Fri Feb 16 08:59:36 2007
From: mills at udel.edu (David L. Mills)
Date: Fri, 16 Feb 2007 16:59:36 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com>
References: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com>
Message-ID: <45D5E2F8.2010204@udel.edu>

Greg,

The terms resolution and precisions are defined very narrowly in the NTP 
documents. Resolution is the reciprocal of the system clock frequency, 
usually one nanosecond with modern hardware and operating systems 
(timespec). Precision is defined as the time to read the system clock, 
currently around 500 ns to 1000 ns with modern hardware and opeating 
systems. It is important to make that distinction when calibrating the 
residual errors for accuaracy assessment. The specification document is 
very clear about this.

Dave

Greg Dowd wrote:

> Some standard uses for reference with ntp:
>
> precision: This defines the smallest measurement which can actually be
> made. It helps to define the number of significant bits in a
> measurement.
> resolution: This defines the total number of bits available to express
> a measurement. It tells you nothing about the value of any of those
> bits.
> accuracy: This defines how well a measurement agrees with a timescale
> (e.g., UTC).
>
>
>
> Greg Dowd
> gdowd at symmetricom dot com (antispam format)
> Symmetricom, Inc.
> www.symmetricom.com
> "The current implementation is non-obvious and may need to be improved."
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070216/042452cd/attachment.html 

From karen.odonoghue at navy.mil  Fri Feb 16 15:46:58 2007
From: karen.odonoghue at navy.mil (Odonoghue, Karen F CIV NSWCDD, W13)
Date: Fri, 16 Feb 2007 17:46:58 -0600
Subject: [ntpwg] (no subject)
Message-ID: <2E44C2268B59514C89AE2CB514D15ACA61D040@NAEAMILLEX01VA.nadsusea.nads.navy.mil>



-----Original Message-----
From: ntpwg-bounces+karen.odonoghue=navy.mil at lists.ntp.isc.org <ntpwg-bounces+karen.odonoghue=navy.mil at lists.ntp.isc.org>
CC: ntpwg at ntp.isc.org <ntpwg at ntp.isc.org>
Sent: Fri Feb 16 11:49:41 2007
Subject: Re: [ntpwg] Document update

Harlan,

No. The document does not discuss the kernel functions.

Dave

Harlan Stenn wrote:

> The document needs to be checked against the latest ntp_loopfilter.c to
> see if the changes for http://bugs.ntp.isc.org/778 need to be included.
>
> H
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


_______________________________________________
ntpwg mailing list
ntpwg at lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070216/e4b088c3/attachment.html 

From karen.odonoghue at navy.mil  Fri Feb 16 16:14:13 2007
From: karen.odonoghue at navy.mil (Odonoghue, Karen F CIV NSWCDD, W13)
Date: Fri, 16 Feb 2007 18:14:13 -0600
Subject: [ntpwg] Schedule heads up
Message-ID: <2E44C2268B59514C89AE2CB514D15ACA61D041@NAEAMILLEX01VA.nadsusea.nads.navy.mil>

Folks,

Ignore the last message from me. Composing a real email msg on Blackberrys requires patience. Note to self, don't try to edit unrelated msg...

Anyhow, I just wanted to send out a heads up that the ntp wg meeting for the next IETF is currently on Monday 3/19 at roughly 300 pm in Prague. The other activity that is of interest to this group is the tictoc bof on Tuesday 3/20 at 900 am. I hope these are close enough to be convenient to folks that are only interested in time related topics. The only change I may pursue is later on Monday and Tuesday. This is a draft agenda so be forewarned. Check www.ietf.org for details. This is also almost late enough in Prague to support remote participation. 

Additionally, you all have seen the -04 draft announcement and Dr. Mills' update. We are working the issues associated with generating another update. Please get your comments on the table now. 

Well, my thumbs are revolting. Have a nice weekend.

Karen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070216/0419e284/attachment.html 

From tglassey at earthlink.net  Sat Feb 17 16:26:23 2007
From: tglassey at earthlink.net (todd glassey)
Date: Sat, 17 Feb 2007 16:26:23 -0800
Subject: [ntpwg] Timing Definitions
References: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com>
	<45D5E2F8.2010204@udel.edu>
Message-ID: <024101c752f3$6dad1a20$2201a8c0@home.glassey.com>

Dave - 
  ----- Original Message ----- 
  From: David L. Mills 
  Cc: ntpwg at ntp.isc.org 
  Sent: Friday, February 16, 2007 8:59 AM
  Subject: Re: [ntpwg] Timing Definitions


  Greg,

  The terms resolution and precisions are defined very narrowly in the NTP documents. Resolution is the reciprocal of the system clock frequency, usually one nanosecond with modern hardware and operating systems (timespec). 

With the new architectures however the resolution will change. The question becomes one of how to notate that and where it should be disclosed.


  Precision is defined as the time to read the system clock, currently around 500 ns to 1000 ns with modern hardware and opeating systems. It is important to make that distinction when calibrating the residual errors for accuaracy assessment. 

These also are specific to current and previously available systems but the standards will change and since there is no process for characterizing a NTP Server yet this is a reasonable commentary of Greg's.

Symmetricom and all of the HW based Time Systems providers need these data points for creating characterizations of their systems and the performance and so these additions are reasonable and warranted for supporting the commercial users of NTP.

  The specification document is very clear about this.

  Dave

  Greg Dowd wrote:

    Some standard uses for reference with ntp:

    precision: This defines the smallest measurement which can actually be
    made. It helps to define the number of significant bits in a
    measurement.
    resolution: This defines the total number of bits available to express
    a measurement. It tells you nothing about the value of any of those
    bits.
    accuracy: This defines how well a measurement agrees with a timescale
    (e.g., UTC).



    Greg Dowd
    gdowd at symmetricom dot com (antispam format)
    Symmetricom, Inc. 
    www.symmetricom.com
    "The current implementation is non-obvious and may need to be improved."







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

    _______________________________________________
    ntpwg mailing list
    ntpwg at lists.ntp.isc.org
    https://lists.ntp.isc.org/mailman/listinfo/ntpwg




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


  _______________________________________________
  ntpwg mailing list
  ntpwg at lists.ntp.isc.org
  https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070217/ad68cace/attachment.html 

From mills at udel.edu  Sun Feb 18 10:22:44 2007
From: mills at udel.edu (David L. Mills)
Date: Sun, 18 Feb 2007 18:22:44 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <024101c752f3$6dad1a20$2201a8c0@home.glassey.com>
References: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com>
	<45D5E2F8.2010204@udel.edu>
	<024101c752f3$6dad1a20$2201a8c0@home.glassey.com>
Message-ID: <45D89974.7080505@udel.edu>

todd,

We are on a tangent here.

The definitions I use are deliberately measurable and unambiguous. They 
are also consistent with the intricately crafted statistics budget in 
the spec, the UDel report and the book. There is nothing specific to 
present or future architecture or product. The standard will not change 
with the introduction of new architecture or product. That's the 
rigorous intent of the specification in the first place.

If you find something in the budget in error, very please honk. If you 
find something inconsistent in the name or interpretation of the error 
statistics, very please honk. Whatever honk you find must be rock hard, 
measurable and consistent with analysis.

Dave

todd glassey wrote:

> Dave -
> ----- Original Message -----
> From: David L. Mills
> Cc: ntpwg at ntp.isc.org
> Sent: Friday, February 16, 2007 8:59 AM
> Subject: Re: [ntpwg] Timing Definitions
>
>
> Greg,
>
> The terms resolution and precisions are defined very narrowly in the 
> NTP documents. Resolution is the reciprocal of the system clock 
> frequency, usually one nanosecond with modern hardware and operating 
> systems (timespec).
>
> With the new architectures however the resolution will change. The 
> question becomes one of how to notate that and where it should be 
> disclosed.
>
>
> Precision is defined as the time to read the system clock, currently 
> around 500 ns to 1000 ns with modern hardware and opeating systems. It 
> is important to make that distinction when calibrating the residual 
> errors for accuaracy assessment.
>
> These also are specific to current and previously available systems 
> but the standards will change and since there is no process for 
> characterizing a NTP Server yet this is a reasonable commentary of Greg's.
>
> Symmetricom and all of the HW based Time Systems providers need these 
> data points for creating characterizations of their systems and the 
> performance and so these additions are reasonable and warranted for 
> supporting the commercial users of NTP.
>
> The specification document is very clear about this.
>
> Dave
>
> Greg Dowd wrote:
>
> Some standard uses for reference with ntp:
>
> precision: This defines the smallest measurement which can actually be
> made. It helps to define the number of significant bits in a
> measurement.
> resolution: This defines the total number of bits available to express
> a measurement. It tells you nothing about the value of any of those
> bits.
> accuracy: This defines how well a measurement agrees with a timescale
> (e.g., UTC).
>
>
>
> Greg Dowd
> gdowd at symmetricom dot com (antispam format)
> Symmetricom, Inc.
> www.symmetricom.com
> "The current implementation is non-obvious and may need to be improved."
>
>
>
>
>
>
>
> ----------------------------------------------------------------------------
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg



From tglassey at earthlink.net  Sun Feb 18 13:11:55 2007
From: tglassey at earthlink.net (todd glassey)
Date: Sun, 18 Feb 2007 13:11:55 -0800
Subject: [ntpwg] Timing Definitions
References: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com><45D5E2F8.2010204@udel.edu><024101c752f3$6dad1a20$2201a8c0@home.glassey.com>
	<45D89974.7080505@udel.edu>
Message-ID: <009801c753a1$cbb64a70$2101a8c0@home.glassey.com>

Dave - this was all about benchmarking NTP and setting a set of standards 
per those.

Todd


From mills at udel.edu  Sun Feb 18 14:33:38 2007
From: mills at udel.edu (David L. Mills)
Date: Sun, 18 Feb 2007 22:33:38 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
References: <4B73D9EBE2327E40B4D69822D7C45802068D0802@sjmail1.symmetricom.com><45D5E2F8.2010204@udel.edu><024101c752f3$6dad1a20$2201a8c0@home.glassey.com>
	<45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
Message-ID: <45D8D442.9090207@udel.edu>

todd,

That's exactly what I had in mind, and that's why I phrased the values 
as I did in the spec. Note also jitter and wander are formally defined 
and so is delay, dispersion and distance.

Dave

todd glassey wrote:

> Dave - this was all about benchmarking NTP and setting a set of 
> standards per those.
>
> Todd
>


From kurt at roeckx.be  Sun Feb 18 16:31:14 2007
From: kurt at roeckx.be (Kurt Roeckx)
Date: Mon, 19 Feb 2007 01:31:14 +0100
Subject: [ntpwg] Timing Definitions
In-Reply-To: <45D8D442.9090207@udel.edu>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu>
Message-ID: <20070219003114.GA17470@roeckx.be>

On Sun, Feb 18, 2007 at 10:33:38PM +0000, David L. Mills wrote:
> todd,
> 
> That's exactly what I had in mind, and that's why I phrased the values 
> as I did in the spec. Note also jitter and wander are formally defined 
> and so is delay, dispersion and distance.

I've looking for which terms are defined in the draft, and this is what
I came up with:
- resolution: Let p be the number of significant bits in the second
  fraction. The clock resolution is defined 2^(-p), in seconds.
- precision: The clock precision is defined as the running time to read the
  system clock, in seconds. Note that the precision defined in this way can
  be larger or smaller than the resolution. The term rho, representing the
  precision used in the protocol, is the larger of the two.
- offset: The offset theta represents the maximum-likelihood time offset of
  the server clock relative to the system clock.
- delay: The delay delta represents the roundtrip delay between the client
  and server.
- dispersion: The dispersion epsilon represents the maximum error inherent
  in the measurement. It increases at a rate equal to the maximum disciplined
  system clock frequency tolerance PHI, typically 15 PPM.
- jitter: The jitter psi, defined as the root-mean-square (RMS) average of
  the most recent time offset differences, represents the nominal error in
  estimating theta.
- wander: The RMS average of past frequency offset differences
  represents the oscillator frequency stability or frequency wander
  OMEGA
- distance: The synchronization distance LAMBDA = EPSILON + DELTA / 2
  represents the maximum error due all causes.


So, what I couldn't find was one for accuracy.  The distance is
probably closest to that.

But I want to give an example, so I know I understand things right.  If
my kernel returns the time in microseconds, but only updates it say at
100 Hz.  I think my resolution is 10 ms, but would set p to 6, so I get
.0156 seconds.  If I can read the clock say 1000 times a second, I think 
my precision would be 1 ms. But since I'd read the same value 10 times,
I'd have to set rho to the resolution.


Kurt


From mills at udel.edu  Sun Feb 18 21:32:44 2007
From: mills at udel.edu (David L. Mills)
Date: Mon, 19 Feb 2007 05:32:44 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <20070219003114.GA17470@roeckx.be>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu> <20070219003114.GA17470@roeckx.be>
Message-ID: <45D9367C.9090703@udel.edu>

Kurt,

You raise an important point. There is no such thing as accuracy in the 
product, only a statistical estimation of the resolution, precision and 
other statistics. There is no specific accuracy statement possible in 
this thing. It's like saying, how pretty is your girlfriend.

Dave

Kurt Roeckx wrote:

> On Sun, Feb 18, 2007 at 10:33:38PM +0000, David L. Mills wrote:
>
>> todd,
>>
>> That's exactly what I had in mind, and that's why I phrased the values
>> as I did in the spec. Note also jitter and wander are formally defined
>> and so is delay, dispersion and distance.
>
>
> I've looking for which terms are defined in the draft, and this is what
> I came up with:
> - resolution: Let p be the number of significant bits in the second
> fraction. The clock resolution is defined 2^(-p), in seconds.
> - precision: The clock precision is defined as the running time to 
> read the
> system clock, in seconds. Note that the precision defined in this way can
> be larger or smaller than the resolution. The term rho, representing the
> precision used in the protocol, is the larger of the two.
> - offset: The offset theta represents the maximum-likelihood time 
> offset of
> the server clock relative to the system clock.
> - delay: The delay delta represents the roundtrip delay between the client
> and server.
> - dispersion: The dispersion epsilon represents the maximum error inherent
> in the measurement. It increases at a rate equal to the maximum 
> disciplined
> system clock frequency tolerance PHI, typically 15 PPM.
> - jitter: The jitter psi, defined as the root-mean-square (RMS) average of
> the most recent time offset differences, represents the nominal error in
> estimating theta.
> - wander: The RMS average of past frequency offset differences
> represents the oscillator frequency stability or frequency wander
> OMEGA
> - distance: The synchronization distance LAMBDA = EPSILON + DELTA / 2
> represents the maximum error due all causes.
>
>
> So, what I couldn't find was one for accuracy. The distance is
> probably closest to that.
>
> But I want to give an example, so I know I understand things right. If
> my kernel returns the time in microseconds, but only updates it say at
> 100 Hz. I think my resolution is 10 ms, but would set p to 6, so I get
> .0156 seconds. If I can read the clock say 1000 times a second, I think
> my precision would be 1 ms. But since I'd read the same value 10 times,
> I'd have to set rho to the resolution.
>
>
> Kurt
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070219/dc803404/attachment.html 

From seaman at noao.edu  Mon Feb 19 06:35:40 2007
From: seaman at noao.edu (Rob Seaman)
Date: Mon, 19 Feb 2007 07:35:40 -0700
Subject: [ntpwg] Timing Definitions
In-Reply-To: <45D9367C.9090703@udel.edu>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu> <20070219003114.GA17470@roeckx.be>
	<45D9367C.9090703@udel.edu>
Message-ID: <F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>

On Feb 18, 2007, at 10:32 PM, David L. Mills wrote:

> There is no such thing as accuracy in the product, only a  
> statistical estimation of the resolution, precision and other  
> statistics. There is no specific accuracy statement possible in  
> this thing. It's like saying, how pretty is your girlfriend.

(One is tempted to point out that the way to answer the latter  
question is to ask one's wife.)

Isn't the same issue as traceability?  Perhaps convolved with the non- 
parametric nature of the clock discipline?  The whole point of  
timekeeping is to tie a remote clock to a master time standard.  This  
is distinct, say, from identifying physical limits on the accuracy of  
absolute intervals returned by an egg timer.

In general, unless a trusted measurement of whatever quantity is  
available, an estimate of accuracy is impossible.  The mental picture  
usually used to convey the difference between accuracy and precision  
is target practice.  Tight clustering of bullet holes is precision.   
Having the average pattern spread coincide with the center of the  
target is accuracy.

The two things missing from that last statement are first, an  
indication of the repeatability and reliability of the shooting/ 
measurement.  What did the same marksman do last time (to provide  
confidence for next time)?

And secondly, the point in contention with this thread is how do you  
know where the center of the target lies?  With target shooting the  
answer is that the target is much larger than the bullet in both  
absolute size and solid angle.  With timekeeping, we demand that our  
fiducial systems of time and our portable/remote estimates of same  
look and behave like the same things.  Our bullets and our targets  
are the same size.

There would be (relatively) little difficulty in using a nanosecond  
standard timekeeper to measure the accuracy of a tenth-second laptop  
clock - at least, little difficulty if you remove the vagaries of the  
intervening network in favor of something other than NTP...

Rob Seaman
National Optical Astronomy Observatory

-------------- next part --------------
A non-text attachment was scrubbed...
Name: accuracy_precise.gif
Type: image/gif
Size: 5481 bytes
Desc: not available
Url : https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070219/ed0157f9/attachment.gif 
-------------- next part --------------

(http://www.globalsecurity.org/military/library/policy/navy/misc/ 
image434.gif)

From kurt at roeckx.be  Mon Feb 19 10:18:54 2007
From: kurt at roeckx.be (Kurt Roeckx)
Date: Mon, 19 Feb 2007 19:18:54 +0100
Subject: [ntpwg] Timing Definitions
In-Reply-To: <F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu> <20070219003114.GA17470@roeckx.be>
	<45D9367C.9090703@udel.edu>
	<F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>
Message-ID: <20070219181854.GA14155@roeckx.be>

On Mon, Feb 19, 2007 at 07:35:40AM -0700, Rob Seaman wrote:
> On Feb 18, 2007, at 10:32 PM, David L. Mills wrote:
> 
> >There is no such thing as accuracy in the product, only a  
> >statistical estimation of the resolution, precision and other  
> >statistics. There is no specific accuracy statement possible in  
> >this thing. It's like saying, how pretty is your girlfriend.
> 
> Isn't the same issue as traceability?  Perhaps convolved with the non- 
> parametric nature of the clock discipline?  The whole point of  
> timekeeping is to tie a remote clock to a master time standard.  This  
> is distinct, say, from identifying physical limits on the accuracy of  
> absolute intervals returned by an egg timer.
> 
> In general, unless a trusted measurement of whatever quantity is  
> available, an estimate of accuracy is impossible.  The mental picture  
> usually used to convey the difference between accuracy and precision  
> is target practice.  Tight clustering of bullet holes is precision.   
> Having the average pattern spread coincide with the center of the  
> target is accuracy.

The maximum error in a measurement is the sum of the error caused by
accuracy and precision.  What we do is calculate the maximum error (and
estimate the error).  From this number you can't split it up in which
part is caused by the accuracy and which by the precision error.

If we could somehow calculate the accuracy error, and the resolution of
our clock is smaller than that, we could reduce it to something in the
order of our resolution.

Anyway, depending on the application, you're either interrested in the
maximum total error or in the precision.  I can't think of something
were you're interrested in the accuracy.


Kurt


From mills at udel.edu  Mon Feb 19 16:56:05 2007
From: mills at udel.edu (David L. Mills)
Date: Tue, 20 Feb 2007 00:56:05 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <20070219181854.GA14155@roeckx.be>
References: <45D89974.7080505@udel.edu>	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>	<45D8D442.9090207@udel.edu>
	<20070219003114.GA17470@roeckx.be>	<45D9367C.9090703@udel.edu>	<F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>
	<20070219181854.GA14155@roeckx.be>
Message-ID: <45DA4725.8020103@udel.edu>

Kurt,

A few years ago I was at a retreat in Dagstuhl, southern Genmany, 
jousting NTP with serious computer science theory folks. I was the only 
engineer in the room; the rest were theory cats and didn't know the 
difference betweena phase-lock loop and piston return spring. That was 
quite an education for both of us.

According to the theory cats, The dispersion increase (maximum error) 
would have to be at the frequency tolerance limit, assumed 500 PPM. 
However, this is unrealistic, so I settled on 15 PPM as the disciplined 
clock dispersion increase. From a rigorous computer science perspective, 
the NTP architecture is incorrect. My point being that the maximum 
assumed error depends on that assumption. Somebody else might make a 
different assumption, and yes, the increase can be tinkered.

As for extimated error, the error budget has been intricately crafted 
with painful attention to detail. A blow by blow breakdown about the 
various contributions is in the spec and in more detail in the report. 
The book contains even more mathematical detail and justification.

The interpretation of resolution and precision is very important, as the 
resolution depends on the tick interval in some machines, the system 
timer in others and the TSC in still others. The precision statistic is 
somewhat arbitrary, but would satisfy the theory cats, as the value of 
the system clock is indetermenant during the system call.

It is incorrect to describe the error as the sum of accuracy and 
precision. The expected error is the combined offset measured from the 
cluster algorithm survivors. This is the best estimate relative to the 
server(s), but does not take into account the server offset relative to 
its sources. The clock jitter is the estimated error of making that 
measurement and does take into account all the servers down to the 
reference clock(s), a most conservative statistic.

Stand next to Westminister Abbey and set your watch to Big Ben. Big Ben 
clockkeepers keep the clock in tune by listening to the BBC and putting 
coinage on the pendulum. Presumably, the "accuracy" of Big Ben depends 
on the residual frequency error and the interval between coinage 
updates. You set your watch to Big Ben and inherit its characteristics 
and some of your own. How "accurate" is your watch?

Dave

Kurt Roeckx wrote:

> On Mon, Feb 19, 2007 at 07:35:40AM -0700, Rob Seaman wrote:
>
>> On Feb 18, 2007, at 10:32 PM, David L. Mills wrote:
>>
>>> There is no such thing as accuracy in the product, only a
>>> statistical estimation of the resolution, precision and other
>>> statistics. There is no specific accuracy statement possible in
>>> this thing. It's like saying, how pretty is your girlfriend.
>>
>> Isn't the same issue as traceability? Perhaps convolved with the non-
>> parametric nature of the clock discipline? The whole point of
>> timekeeping is to tie a remote clock to a master time standard. This
>> is distinct, say, from identifying physical limits on the accuracy of
>> absolute intervals returned by an egg timer.
>>
>> In general, unless a trusted measurement of whatever quantity is
>> available, an estimate of accuracy is impossible. The mental picture
>> usually used to convey the difference between accuracy and precision
>> is target practice. Tight clustering of bullet holes is precision.
>> Having the average pattern spread coincide with the center of the
>> target is accuracy.
>
>
> The maximum error in a measurement is the sum of the error caused by
> accuracy and precision. What we do is calculate the maximum error (and
> estimate the error). From this number you can't split it up in which
> part is caused by the accuracy and which by the precision error.
>
> If we could somehow calculate the accuracy error, and the resolution of
> our clock is smaller than that, we could reduce it to something in the
> order of our resolution.
>
> Anyway, depending on the application, you're either interrested in the
> maximum total error or in the precision. I can't think of something
> were you're interrested in the accuracy.
>
>
> Kurt
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070220/e65a30fd/attachment.html 

From kurt at roeckx.be  Tue Feb 20 15:14:18 2007
From: kurt at roeckx.be (Kurt Roeckx)
Date: Wed, 21 Feb 2007 00:14:18 +0100
Subject: [ntpwg] Timing Definitions
In-Reply-To: <45DA4725.8020103@udel.edu>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu> <20070219003114.GA17470@roeckx.be>
	<45D9367C.9090703@udel.edu>
	<F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>
	<20070219181854.GA14155@roeckx.be> <45DA4725.8020103@udel.edu>
Message-ID: <20070220231418.GA18612@roeckx.be>

Hi Dave,

On Tue, Feb 20, 2007 at 12:56:05AM +0000, David L. Mills wrote:
> 
> Stand next to Westminister Abbey and set your watch to Big Ben. Big Ben 
> clockkeepers keep the clock in tune by listening to the BBC and putting 
> coinage on the pendulum. Presumably, the "accuracy" of Big Ben depends 
> on the residual frequency error and the interval between coinage 
> updates. You set your watch to Big Ben and inherit its characteristics 
> and some of your own. How "accurate" is your watch?

Since I have no idea about what the accuracy or precision is of Big
Ben, it's going to be rather hard to say anything about it.  And I
think that's the point we're both trying to make.

Anyway, there are 2 ways to synchronize your clock to Big Ben.  One
is looking at it and reading the time.  This is as far as I know with
a resolution of 1 minute, so a precision of atleast 1 minute.  But the
clock might be set with an accuracy in the order of a few seconds.  The
other is listening to it's bells which is going to have a higher
precision but a different accuracy.

To say anything useful about any of those 2 ways, you need to do
statistics by comparing it to a clock that has a small enough error.

If I'm going to set my watch by any of those 2 methods, what matters is
which way has the smallest total error.  The accuracy of my watch is
going to depend on that, and not how accurate the clock is or how
precise I can "read" it.

You can go and reduce the error caused by the precision by taking
more samples, but you can't compensate for the accuracy error.

Anyway, the definition of precision and accuracy I use might be a
little bit different than what you're used to when talking about NTP.
If you take some samples and compare it to a reference, the accuracy
would be the average difference between the samples and the reference,
the precision would be the standard error.

What you use in NTP for the precision is the highest of the resolution
and the time it takes to read the clock.  This is a reasonable estimate
for how precise you can measure the local system clock.  It's not a good
estimate for how precise a remote ntp daemon can come and read your
system clock since it doesn't only depend on your own system now.  It's
this "remote" precision that is used to synchronize the clock.  And I
think you try to estimate that by the jitter.


Kurt


From seaman at noao.edu  Tue Feb 20 17:01:52 2007
From: seaman at noao.edu (Rob Seaman)
Date: Tue, 20 Feb 2007 18:01:52 -0700
Subject: [ntpwg] Timing Definitions
In-Reply-To: <20070220231418.GA18612@roeckx.be>
References: <45D89974.7080505@udel.edu>
	<009801c753a1$cbb64a70$2101a8c0@home.glassey.com>
	<45D8D442.9090207@udel.edu> <20070219003114.GA17470@roeckx.be>
	<45D9367C.9090703@udel.edu>
	<F7D51E26-0E0D-4270-A3E7-CB695726A050@noao.edu>
	<20070219181854.GA14155@roeckx.be> <45DA4725.8020103@udel.edu>
	<20070220231418.GA18612@roeckx.be>
Message-ID: <F87CDCD8-CF4E-4019-BD50-BBB400DCD835@noao.edu>

On Feb 20, 2007, at 4:14 PM, Kurt Roeckx wrote:

> On Tue, Feb 20, 2007 at 12:56:05AM +0000, David L. Mills wrote:
>
>> Stand next to Westminister Abbey and set your watch to Big Ben.  
>> Big Ben
>> clockkeepers keep the clock in tune by listening to the BBC and  
>> putting
>> coinage on the pendulum. Presumably, the "accuracy" of Big Ben  
>> depends
>> on the residual frequency error and the interval between coinage
>> updates. You set your watch to Big Ben and inherit its  
>> characteristics
>> and some of your own. How "accurate" is your watch?

This example is also given in Dr. Mills' excellent book.

> Since I have no idea about what the accuracy or precision is of Big
> Ben, it's going to be rather hard to say anything about it.  And I
> think that's the point we're both trying to make.

I don't think so.  Some protocol could be implemented to convey  
information regarding Ben's current load of coinage and about how far  
it leads or lags the BBC.  It isn't ignorance of these metadata that  
causes trouble in estimating accuracy, it is the lack of a  
fundamental standard.

> Anyway, there are 2 ways to synchronize your clock to Big Ben.

I'm sure there are many more than two.  This reminds me of the  
barometer:

	http://www.snopes.com/college/exam/barometer.asp

I can even add one more.  I've got a nifty new MacBook with the  
accelerometer chip.  The SeisMac app comes with a library that can  
poll three axis values at a couple hundred Hz.  Placing a MacBook in  
close enough proximity to the tower's clock would allow ticks to be  
detected.  Ben is actually the name of the bell, and one might well  
be able to count the striking of the hours from outside the  
building.  Anybody in London want to try?

> If I'm going to set my watch by any of those 2 methods, what  
> matters is
> which way has the smallest total error.

What matters is whether you have a handy fundamental reference to  
consult - see the appended message from the leapsecs list, for  
example.  (Any followups about leap seconds should be directed that  
way - not for the faint of heart.)  The utility of NTP is precisely  
in conveying an estimate of a fundamental standard to a remote  
locale.  At NOAO we rely on NTP on Kitt Peak in Arizona and Cerro  
Tololo in Chile.  Imagine if the weights and measures folks had to  
recalibrate a meter, a liter or a kilo from 5000 miles away -  
continually, 24/7.  The nice thing about UTC (or other flavor of  
Universal Time) is that we're all sitting on top of the fundamental  
reference.

To return to the point in question.  The current draft looks good.   
Wrap it up with a pretty bow.  It's about time you guys started  
working on ntpv5...

Rob Seaman
National Optical Astronomy Observatory
------

  	From: 	  seaman at noao.edu
	Subject: 	Re: [LEAPSECS] how to reset a clock
	Date: 	January 4, 2007 8:15:41 AM MST
	To: 	  LEAPSECS at ROM.USNO.NAVY.MIL

Peter Bunclark wrote:

> Indeed isn't this Rob's ship's chronometer?

Actually, I think it was Mr. Harrison's.  (And Steve Allen has been  
basing his arguments more recently on this distinction.)  This  
healthy debate between astronomical time and clock time has happened  
before.  The answer is the same as before - both types of time are  
needed.  (Some things never change.)  I'm sure Pete is more familiar  
with this story than I am, but others may not be.

Harrison attempted to build a perfect clock to win the Longitude  
Prize.  Folks who haven't read Sobel's book should do so - my  
classmates at Villanova and I learned the story from an Augustinian  
priest who appeared old enough to have known Harrison personnally.   
Harrison's first glorious shipboard clock failed to take the prize  
due to a lack of compensation for centrifugal effects on a sailing  
vessel that must tack when sailing against the wind (or must wear  
through an even larger angle, bringing the wind across its stern).   
Compensation was needed for relativistic effects, if Newtonian rather  
than Einstein.  (Some things never change.)

Harrison invented or improved a variety of familiar mechanical  
doodads like the roller bearing and bimetallic temperature  
compensation.  He likely could have succeeded in solving this  
particular problem, but there would always have been another physical  
improvement needed.  (Some things never change.)  Each improvement  
would have made the clock more complicated and eventually too fragile  
to possibly work on a constantly moving platform buffeted and often  
bathed by the salty sea.

He created a second clock and was working on a third round of  
improvements when the idea we're discussing first occurred to him.   
He had been using a pocket watch as a mechanism to transfer time from  
stationary standard clocks (many built by himself) to his portable  
prototypes.  He would reset the clock in one place and physically  
carry it to where the time was needed.  If a roundtrip correction  
were needed, presumably he would note the time on either end and  
halve the difference.  This is the "standard synchrony" or  
"conventionality of simultaneity" of special relativity - familiar to  
anyone who has looked under the hood of NTP.  (Some things never  
change.)

What Harrison recognized was that he didn't need to build a perfect  
clock - he merely needed to quantify and log the error inherent in  
the clock.  By replacing a large and finicky "better" clock, with a  
small and robust, but more even-tempered, one, the rate of the clock  
could be regularized and its random and systematic errors could be  
minimized.  That the rate of the clock was now guaranteed not to  
match the rate of the spinning Earth was no longer a bug, but a  
feature.  By carefully calibrating the clock rate before leaving on a  
voyage, and checking it against astronomical observations throughout  
the voyage, it was possible to compute the mean solar time at the  
home port.  (Some things never change.)  Comparison with the local  
time, measured by sextant, then recovered the longitude directly.

And, of course, a ship would not carry a single clock, but two or  
more.  Friendly ships meeting at sea would also exchange clock  
readings - creating the first ensemble time scale.  (Some things  
never change.)

Thus was the chronometer born - and thus did Britannia rule the waves.

The point is that time isn't just an unending count of seconds - it  
is the epoch of when the count was zero.  That epoch often has  
significance in some periodic natural phenomena, usually related to  
Earth orientation.

Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070220/a103ca0e/attachment-0001.html 

From anthony.flavin at bt.com  Wed Feb 21 00:56:03 2007
From: anthony.flavin at bt.com (anthony.flavin at bt.com)
Date: Wed, 21 Feb 2007 08:56:03 -0000
Subject: [ntpwg] Timing Definitions
Message-ID: <3046C179E69FC24AB83536978A17614D0EE76DDB@i2km96-ukbr.domain1.systemhost.net>

This is an interesting discussion, but it should be well understood by
most people.

We are dealing with nothing more that sampling theorem. The fact that the
quantity we are sampling is time is irrelevant. Terms such as precision
and resolution are well understood here. As are error (noise).

If these terms have been re-defined within NTP, then that's fine and those
definitions should hold.

So what was the original question that was trying to be answered? Because
I have lost track....

Regards,


	Tony Flavin
	Core Networks Engineering Manager

	e-mail: anthony.flavin at bt.com
	tel: +44(0) 1473 609570
	mobile: +44(0) 7801 759596
	fax: +44(0) 1908 862752

	Orion 5,  pp11 , Adastral Park, Martlesham, Ipswich IP5 3RE, UK

P.s "Big Ben" is the bell not the clock:-

The Great Clock
Hands: Minute (copper) Length 4.3m (14 ft) Weight 101.6kg (2 cwt)
Hour (gunmetal) Length 2.7m (9 ft) Weight 304.8kg (6 cwt)
Pendulum: Total Length 4.4m (14 ft 5 in)
Length of Roman numerals: 61cm (2 ft)
Minute squares: 30.5cm (1 ft)
Number of panes of glass 312
in each clockface
The Bells
Big Ben (the Great Bell) Weight 13.8 tonnes 13 tons 10 cwt 99 lb
Note E: Hammer Weight 203.2kg 4 cwt
Quarter Bells
1 Note G sharp Weight 1 ton 1 cwt 23 lb 1.07 tonnes
2 Note F sharp Weight 1 ton 5 cwt 30 lb 1.28 tonnes
3 Note E Weight 1 ton 13 cwt 69 lb 1.71 tonnes
4 Note B Weight 3 tons 10 cwt 69 lb 3.59 tonnes
Time between Strikes:
>From start of chime to 12th strike = 95 seconds
Big Ben: From 1st strike to 12th strike 54 seconds, 5 seconds between
strikes



-----Original Message-----
From: ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.isc.org
[mailto:ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.isc.org] On Behalf
Of Kurt Roeckx
Sent: 20 February 2007 23:14
To: David L. Mills
Cc: ntpwg at ntp.isc.org
Subject: Re: [ntpwg] Timing Definitions


Hi Dave,

On Tue, Feb 20, 2007 at 12:56:05AM +0000, David L. Mills wrote:
>
> Stand next to Westminister Abbey and set your watch to Big Ben. Big
> Ben
> clockkeepers keep the clock in tune by listening to the BBC and putting
> coinage on the pendulum. Presumably, the "accuracy" of Big Ben depends
> on the residual frequency error and the interval between coinage
> updates. You set your watch to Big Ben and inherit its characteristics
> and some of your own. How "accurate" is your watch?

Since I have no idea about what the accuracy or precision is of Big Ben,
it's going to be rather hard to say anything about it.  And I think that's
the point we're both trying to make.

Anyway, there are 2 ways to synchronize your clock to Big Ben.  One is
looking at it and reading the time.  This is as far as I know with a
resolution of 1 minute, so a precision of atleast 1 minute.  But the clock
might be set with an accuracy in the order of a few seconds.  The other is
listening to it's bells which is going to have a higher precision but a
different accuracy.

To say anything useful about any of those 2 ways, you need to do
statistics by comparing it to a clock that has a small enough error.

If I'm going to set my watch by any of those 2 methods, what matters is
which way has the smallest total error.  The accuracy of my watch is going
to depend on that, and not how accurate the clock is or how precise I can
"read" it.

You can go and reduce the error caused by the precision by taking more
samples, but you can't compensate for the accuracy error.

Anyway, the definition of precision and accuracy I use might be a little
bit different than what you're used to when talking about NTP. If you take
some samples and compare it to a reference, the accuracy would be the
average difference between the samples and the reference, the precision
would be the standard error.

What you use in NTP for the precision is the highest of the resolution and
the time it takes to read the clock.  This is a reasonable estimate for
how precise you can measure the local system clock.  It's not a good
estimate for how precise a remote ntp daemon can come and read your system
clock since it doesn't only depend on your own system now.  It's this
"remote" precision that is used to synchronize the clock.  And I think you
try to estimate that by the jitter.


Kurt

_______________________________________________
ntpwg mailing list
ntpwg at lists.ntp.isc.org https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5938 bytes
Desc: not available
Url : https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070221/ee9c626a/attachment.bin 

From mills at udel.edu  Wed Feb 21 06:57:54 2007
From: mills at udel.edu (David L. Mills)
Date: Wed, 21 Feb 2007 14:57:54 +0000
Subject: [ntpwg] Timing Definitions
In-Reply-To: <3046C179E69FC24AB83536978A17614D0EE76DDB@i2km96-ukbr.domain1.systemhost.net>
References: <3046C179E69FC24AB83536978A17614D0EE76DDB@i2km96-ukbr.domain1.systemhost.net>
Message-ID: <45DC5DF2.2060801@udel.edu>

Tony,

Watch out for the sampling theorem. That has to do with the minimum 
frequency for sampling time-varying signals with specified bandwidth.

What set this discussion off was the notion on the part of some folks 
that accuracy could be defined in some arbitrary manner. Not so, and my 
carefully crafted error budget is the counter. I would take serious bets 
even now that few have actually seen and considered the draft 
specification. I have received no comments on the draft of any kind.

Dave

anthony.flavin at bt.com wrote:

> This is an interesting discussion, but it should be well understood by
> most people.
>
> We are dealing with nothing more that sampling theorem. The fact that the
> quantity we are sampling is time is irrelevant. Terms such as precision
> and resolution are well understood here. As are error (noise).
>
> If these terms have been re-defined within NTP, then that's fine and those
> definitions should hold.
>
> So what was the original question that was trying to be answered? Because
> I have lost track....
>
> Regards,
>
>
> Tony Flavin
> Core Networks Engineering Manager
>
> e-mail: anthony.flavin at bt.com
> tel: +44(0) 1473 609570
> mobile: +44(0) 7801 759596
> fax: +44(0) 1908 862752
>
> Orion 5, pp11 , Adastral Park, Martlesham, Ipswich IP5 3RE, UK
>
> P.s "Big Ben" is the bell not the clock:-
>
> The Great Clock
> Hands: Minute (copper) Length 4.3m (14 ft) Weight 101.6kg (2 cwt)
> Hour (gunmetal) Length 2.7m (9 ft) Weight 304.8kg (6 cwt)
> Pendulum: Total Length 4.4m (14 ft 5 in)
> Length of Roman numerals: 61cm (2 ft)
> Minute squares: 30.5cm (1 ft)
> Number of panes of glass 312
> in each clockface
> The Bells
> Big Ben (the Great Bell) Weight 13.8 tonnes 13 tons 10 cwt 99 lb
> Note E: Hammer Weight 203.2kg 4 cwt
> Quarter Bells
> 1 Note G sharp Weight 1 ton 1 cwt 23 lb 1.07 tonnes
> 2 Note F sharp Weight 1 ton 5 cwt 30 lb 1.28 tonnes
> 3 Note E Weight 1 ton 13 cwt 69 lb 1.71 tonnes
> 4 Note B Weight 3 tons 10 cwt 69 lb 3.59 tonnes
> Time between Strikes:
> From start of chime to 12th strike = 95 seconds
> Big Ben: From 1st strike to 12th strike 54 seconds, 5 seconds between
> strikes
>
>
>
> -----Original Message-----
> From: ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.isc.org
> [mailto:ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.isc.org] On Behalf
> Of Kurt Roeckx
> Sent: 20 February 2007 23:14
> To: David L. Mills
> Cc: ntpwg at ntp.isc.org
> Subject: Re: [ntpwg] Timing Definitions
>
>
> Hi Dave,
>
> On Tue, Feb 20, 2007 at 12:56:05AM +0000, David L. Mills wrote:
>
>> Stand next to Westminister Abbey and set your watch to Big Ben. Big
>> Ben
>> clockkeepers keep the clock in tune by listening to the BBC and putting
>> coinage on the pendulum. Presumably, the "accuracy" of Big Ben depends
>> on the residual frequency error and the interval between coinage
>> updates. You set your watch to Big Ben and inherit its characteristics
>> and some of your own. How "accurate" is your watch?
>
>
> Since I have no idea about what the accuracy or precision is of Big Ben,
> it's going to be rather hard to say anything about it. And I think that's
> the point we're both trying to make.
>
> Anyway, there are 2 ways to synchronize your clock to Big Ben. One is
> looking at it and reading the time. This is as far as I know with a
> resolution of 1 minute, so a precision of atleast 1 minute. But the clock
> might be set with an accuracy in the order of a few seconds. The other is
> listening to it's bells which is going to have a higher precision but a
> different accuracy.
>
> To say anything useful about any of those 2 ways, you need to do
> statistics by comparing it to a clock that has a small enough error.
>
> If I'm going to set my watch by any of those 2 methods, what matters is
> which way has the smallest total error. The accuracy of my watch is going
> to depend on that, and not how accurate the clock is or how precise I can
> "read" it.
>
> You can go and reduce the error caused by the precision by taking more
> samples, but you can't compensate for the accuracy error.
>
> Anyway, the definition of precision and accuracy I use might be a little
> bit different than what you're used to when talking about NTP. If you take
> some samples and compare it to a reference, the accuracy would be the
> average difference between the samples and the reference, the precision
> would be the standard error.
>
> What you use in NTP for the precision is the highest of the resolution and
> the time it takes to read the clock. This is a reasonable estimate for
> how precise you can measure the local system clock. It's not a good
> estimate for how precise a remote ntp daemon can come and read your system
> clock since it doesn't only depend on your own system now. It's this
> "remote" precision that is used to synchronize the clock. And I think you
> try to estimate that by the jitter.
>
>
> Kurt
>
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org https://lists.ntp.isc.org/mailman/listinfo/ntpwg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070221/79e1e236/attachment.html 

From jaredmorrisen at gmail.com  Wed Feb 21 14:42:58 2007
From: jaredmorrisen at gmail.com (Jared Morrisen)
Date: Wed, 21 Feb 2007 17:42:58 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax Technical
	Controls Have Enabled the Illegal Backdating of Stock Options
Message-ID: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>

Interesting piece...

*Weak Enforcement of Corporate Governance and Lax Technical Controls Have
Enabled the Illegal Backdating of Stock Options*

Feb 21, 2007
URL: http://www.wallstreetandtech.com/showArticle.jhtml?articleID=197007836<http://www.wallstreetandtech.com/showArticle.jhtml;jsessionid=EFGZH0BSWEZYAQSNDLRSKHSCJUNN2JVN?articleID=197007836>

In 2006 hundreds of companies were implicated in stock-option timing
scandals, and a number of executives were indicted for illegally backdating
stock options. While greed is the primary reason for backdating, it is
abetted by weak enforcement of corporate governance that should prevent the
practice in the first place. Often, there also is a lack of technical
controls on corporate networks to deter such activities.

Options backdating is the dating of employee stock options with an earlier
date than the actual date of the grant. The objective is to choose a date on
which the price of the underlying stock is lower than the current price,
resulting in an instant profit to the grantee. When dealing with tens or
hundreds of thousands of shares, and price differentials in the range of $50
a share, the amount of illicit gain can be immense.

This time distortion results not only in the value of the option being much
greater to the employee receiving it, but in a correlative detriment to
shareholders by way of stock price dilution. While backdating of stock
options is not necessarily illegal if the grantor of the stock options
properly discloses the backdating, it remains to be seen whether some other
fiduciary duty has been breached.

Most of the legal issues arising from backdating are a result of the grantor
falsifying documents to conceal the backdating. According to attorney Louis
Brilleman, counsel at Sichenzia Ross Friedman Ference in New York, a law
firm specializing in securities matters, backdating is illegal under most
circumstances. The practice usually leads to the creation of fraudulent
documents through the disclosure of misleading corporate earnings and the
improper reporting of the option grant under applicable tax rules, Brilleman
explains.

Options backdating has been going on for many years. The rules changed in
2002 with the passage of Sarbanes-Oxley, but even that did not stop some
companies from continuing backdating practices. Accurate timing of
transactions ? stock or otherwise ? is fundamental to any SOX report.
Further, beginning in August 2002, and pursuant to SOX and other securities
laws, the SEC started requiring companies to disclose their stock-option
awards within two days of options grants.

With new regulations in place, backdating now is a regulatory issue, and, as
such, companies can no longer bury their heads in the sand and hope no one
notices. It has become clear that the element of time is now an internal
control. Any weaknesses in tracking the time of stock-option grants must be
investigated, reported and corrected.

Companies now must take the necessary steps to ensure that any backdating
will be detected. Besides the development of policies, procedures and
standards around backdating, there are technical solutions that can be
implemented to support such an endeavor.

*Time Synchronization Is Imperative*

These technical solutions center on time synchronization. Companies must
proactively create a time-synchronization mandate and ensure that it is
correctly deployed throughout their IT environments. Fortunately, creating
such a time synchronization infrastructure is relatively easy, and the ROI
on such an undertaking can be significant.

As time-synchronization hardware is a needed investment, properly
communicating the need to management is crucial to getting funding for the
technology. Synchronizing time is a fundamental business and technology
decision that should be an integral part of an effective network and
security architecture.

The need for this is evident in that an enterprise information network and
security infrastructure is highly dependent on synchronized time. In
addition, there also are regulatory issues that require correct synchronized
time ? from NASD OATS, FFIEC and GLBA, to Visa CISP and many more. All of
these regulations recognize that correct time is critical for transactions
across a network. Many events on the network need the correct time to
initiate jobs, complete transactions, etc. Correct time is critical for
billing systems, authentication systems, manufacturing, forensics and more.

Common to all of these regulations is the requirement that financial
transactions and changes to electronic records be accurately time-stamped.
To provide accurate time stamps, all network devices must be synchronized
relative to national and international time standards.

At the application and operating system level, most applications and
networking protocols require correct synchronized time. Vendors such as
Microsoft, Cisco, Oracle, Red Hat, Novell and Baan all state that their
systems must be configured to an authoritative time server for proper and
secure use.

Time servers cost from $2,000 to $10,000, depending on the level of accuracy
and redundancy required. Time servers, which take but a few hours to
install, provide additional benefits, such as reduced downtime and the
ability to mitigate legal exposure.

Options backdating is the problem, and time synchronization is the solution.
But getting from solution to implementation takes proper planning and
project management. With that, the following five steps can be used as a
high-level framework for implementing synchronized time in your
organization.

*Step 1: Risks and Requirements*
The first step is to formally determine the risk to your company if you do
not have synchronized time. Don't underestimate the risks; if you don't
practice due care pertaining to the time on your network system, you can be
legally liable for negligence and held accountable for the ramifications of
that negligence.

Next, determine how accurate your clocks need to be. This can be anywhere
from milliseconds to a few seconds. Finally, advise management of the risks
of nonsynchronized time and get their approval for the purchase of
time-synchronization equipment and the initiation of a time-synchronization
project.

*Step 2: Hardware and Software*
Start meeting with vendors of time-synchronization equipment to determine
the solution that best fits your organization and specific needs. Some of
the leading vendors in this space include
Spectracom<http://www.spectracomcorp.com/>,
Symmetricom <http://www.symmetricom.com/> and EndRun Technologies.
<http://www.endruntechnologies.com/>

*Step 3: Policy*
If policies for time synchronization are not in place already, work with the
information security department to ensure that time synchronization becomes
part of the global enterprise information technology policy. Time
synchronization must be made part of the corporate IT systems and security
policies. Without a policy, there will be no impetus for staff to achieve
accurate, synchronized time. Often, a simple policy, such as, "Time
synchronization to an accurate time source is required on all enterprise
network devices," is a sufficient first step.

*Step 4: Architecture*
The first step to architecting an accurate time-synchronization solution is
to establish a network time source, known as a reference clock, for
tracability to national and international standards. A typical reference
clock would use GPS (Global Positioning System) to receive time from
satellites. Second, create a downstream topology for all network components
to use the reference clock as the network's master source of time.

*Step 5: Auditability*
Steps 1 through 4 are important from a technical perspective. But even with
the most sophisticated timing device, you still need to have independent and
auditable time controls in place. As part of this, you must be able to prove
to auditors and regulators that the time on any monitored system was
correctly synchronized with a specified time source.

Also, it is important to note that time synchronization will not magically
cure a regulatory material weakness leading to an internal controls problem.
Those in control of time synchronization still can manipulate time and/or
data. It becomes an issue, at least in part, of taking control over this
material weakness away from insiders. With that, it is imperative to ensure
that insiders are not engaging in any time-based data manipulation.

Also, if something goes to court, you need to prove that all your devices on
your network are synchronized and that all transactions that took place are
able to provide an accurate, authenticated time source. This requires that
all logs are handled within the context of digital forensics and staff
members are following the appropriate rules of evidence.

*Conclusion*
The backdating fiasco demonstrates that the need for synchronized time is a
crucial business and technology requirement. As such, it is an integral part
of an effective network and security architecture. Ensuring accurate time is
relatively inexpensive and offers a significant ROI. And it is a great way
to stop your company from getting negative press ? not to mention to keep
your management team from being indicted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070221/5dccb95f/attachment-0001.html 

From tglassey at earthlink.net  Wed Feb 21 17:42:34 2007
From: tglassey at earthlink.net (todd glassey)
Date: Wed, 21 Feb 2007 17:42:34 -0800
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
	TechnicalControls Have Enabled the Illegal Backdating of
	Stock Options
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
Message-ID: <009701c75624$3770f6f0$2101a8c0@home.glassey.com>

Totally off topic - and my apologies for that,  but Jared ...if you are interested this is more about Governance Processes failures for reporting and registering stock transactions and what it forced, that being a 48 hour reporting window for documenting the issuance of an option or stock grant - check out PCAOB...  (http://www.pcaobus.com/) which is now responsible for auditing those public company's and they are where the fire happens in this type of thing.

PCAOB has created a set of key documents called AS#, and AS-2 and AS-4 are the current key operating documents for the audit process. Likewise, www.coso.org (*the Treadway Commission) also has more info on this.

Todd
  ----- Original Message ----- 
  From: Jared Morrisen 
  To: ntpwg at ntp.isc.org ; mills at udel.edu 
  Sent: Wednesday, February 21, 2007 2:42 PM
  Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax TechnicalControls Have Enabled the Illegal Backdating of Stock Options


  Interesting piece...

  Weak Enforcement of Corporate Governance and Lax Technical Controls Have Enabled the Illegal Backdating of Stock Options

  Feb 21, 2007
  URL: http://www.wallstreetandtech.com/showArticle.jhtml?articleID=197007836 

  In 2006 hundreds of companies were implicated in stock-option timing scandals, and a number of executives were indicted for illegally backdating stock options. While greed is the primary reason for backdating, it is abetted by weak enforcement of corporate governance that should prevent the practice in the first place. Often, there also is a lack of technical controls on corporate networks to deter such activities. 

  Options backdating is the dating of employee stock options with an earlier date than the actual date of the grant. The objective is to choose a date on which the price of the underlying stock is lower than the current price, resulting in an instant profit to the grantee. When dealing with tens or hundreds of thousands of shares, and price differentials in the range of $50 a share, the amount of illicit gain can be immense. 

  This time distortion results not only in the value of the option being much greater to the employee receiving it, but in a correlative detriment to shareholders by way of stock price dilution. While backdating of stock options is not necessarily illegal if the grantor of the stock options properly discloses the backdating, it remains to be seen whether some other fiduciary duty has been breached. 

  Most of the legal issues arising from backdating are a result of the grantor falsifying documents to conceal the backdating. According to attorney Louis Brilleman, counsel at Sichenzia Ross Friedman Ference in New York, a law firm specializing in securities matters, backdating is illegal under most circumstances. The practice usually leads to the creation of fraudulent documents through the disclosure of misleading corporate earnings and the improper reporting of the option grant under applicable tax rules, Brilleman explains. 

  Options backdating has been going on for many years. The rules changed in 2002 with the passage of Sarbanes-Oxley, but even that did not stop some companies from continuing backdating practices. Accurate timing of transactions ? stock or otherwise ? is fundamental to any SOX report. Further, beginning in August 2002, and pursuant to SOX and other securities laws, the SEC started requiring companies to disclose their stock-option awards within two days of options grants. 

  With new regulations in place, backdating now is a regulatory issue, and, as such, companies can no longer bury their heads in the sand and hope no one notices. It has become clear that the element of time is now an internal control. Any weaknesses in tracking the time of stock-option grants must be investigated, reported and corrected. 

  Companies now must take the necessary steps to ensure that any backdating will be detected. Besides the development of policies, procedures and standards around backdating, there are technical solutions that can be implemented to support such an endeavor. 

  Time Synchronization Is Imperative


  These technical solutions center on time synchronization. Companies must proactively create a time-synchronization mandate and ensure that it is correctly deployed throughout their IT environments. Fortunately, creating such a time synchronization infrastructure is relatively easy, and the ROI on such an undertaking can be significant. 

  As time-synchronization hardware is a needed investment, properly communicating the need to management is crucial to getting funding for the technology. Synchronizing time is a fundamental business and technology decision that should be an integral part of an effective network and security architecture. 

  The need for this is evident in that an enterprise information network and security infrastructure is highly dependent on synchronized time. In addition, there also are regulatory issues that require correct synchronized time ? from NASD OATS, FFIEC and GLBA, to Visa CISP and many more. All of these regulations recognize that correct time is critical for transactions across a network. Many events on the network need the correct time to initiate jobs, complete transactions, etc. Correct time is critical for billing systems, authentication systems, manufacturing, forensics and more. 

  Common to all of these regulations is the requirement that financial transactions and changes to electronic records be accurately time-stamped. To provide accurate time stamps, all network devices must be synchronized relative to national and international time standards. 

  At the application and operating system level, most applications and networking protocols require correct synchronized time. Vendors such as Microsoft, Cisco, Oracle, Red Hat, Novell and Baan all state that their systems must be configured to an authoritative time server for proper and secure use. 

  Time servers cost from $2,000 to $10,000, depending on the level of accuracy and redundancy required. Time servers, which take but a few hours to install, provide additional benefits, such as reduced downtime and the ability to mitigate legal exposure. 

  Options backdating is the problem, and time synchronization is the solution. But getting from solution to implementation takes proper planning and project management. With that, the following five steps can be used as a high-level framework for implementing synchronized time in your organization. 

  Step 1: Risks and Requirements
  The first step is to formally determine the risk to your company if you do not have synchronized time. Don't underestimate the risks; if you don't practice due care pertaining to the time on your network system, you can be legally liable for negligence and held accountable for the ramifications of that negligence. 

  Next, determine how accurate your clocks need to be. This can be anywhere from milliseconds to a few seconds. Finally, advise management of the risks of nonsynchronized time and get their approval for the purchase of time-synchronization equipment and the initiation of a time-synchronization project. 

  Step 2: Hardware and Software
  Start meeting with vendors of time-synchronization equipment to determine the solution that best fits your organization and specific needs. Some of the leading vendors in this space include Spectracom, Symmetricom and EndRun Technologies. 

  Step 3: Policy
  If policies for time synchronization are not in place already, work with the information security department to ensure that time synchronization becomes part of the global enterprise information technology policy. Time synchronization must be made part of the corporate IT systems and security policies. Without a policy, there will be no impetus for staff to achieve accurate, synchronized time. Often, a simple policy, such as, "Time synchronization to an accurate time source is required on all enterprise network devices," is a sufficient first step. 

  Step 4: Architecture
  The first step to architecting an accurate time-synchronization solution is to establish a network time source, known as a reference clock, for tracability to national and international standards. A typical reference clock would use GPS (Global Positioning System) to receive time from satellites. Second, create a downstream topology for all network components to use the reference clock as the network's master source of time. 

  Step 5: Auditability
  Steps 1 through 4 are important from a technical perspective. But even with the most sophisticated timing device, you still need to have independent and auditable time controls in place. As part of this, you must be able to prove to auditors and regulators that the time on any monitored system was correctly synchronized with a specified time source. 

  Also, it is important to note that time synchronization will not magically cure a regulatory material weakness leading to an internal controls problem. Those in control of time synchronization still can manipulate time and/or data. It becomes an issue, at least in part, of taking control over this material weakness away from insiders. With that, it is imperative to ensure that insiders are not engaging in any time-based data manipulation. 

  Also, if something goes to court, you need to prove that all your devices on your network are synchronized and that all transactions that took place are able to provide an accurate, authenticated time source. This requires that all logs are handled within the context of digital forensics and staff members are following the appropriate rules of evidence. 

  Conclusion
  The backdating fiasco demonstrates that the need for synchronized time is a crucial business and technology requirement. As such, it is an integral part of an effective network and security architecture. Ensuring accurate time is relatively inexpensive and offers a significant ROI. And it is a great way to stop your company from getting negative press ? not to mention to keep your management team from being indicted. 



















































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


  _______________________________________________
  ntpwg mailing list
  ntpwg at lists.ntp.isc.org
  https://lists.ntp.isc.org/mailman/listinfo/ntpwg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070221/5104e4d5/attachment.html 

From brian.utterback at sun.com  Thu Feb 22 05:48:05 2007
From: brian.utterback at sun.com (Brian Utterback)
Date: Thu, 22 Feb 2007 08:48:05 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
In-Reply-To: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
Message-ID: <45DD9F15.2090201@sun.com>

I don't buy this at all. I think we all agree that time sync has
the benfits listed at the end, i.e. "integral part of an effective 
network and security architecture". But I fail to see how synchronized
clocks on the network would prevent the backdating of stock options. I
guarantee that none of the options in question got the date filled in
by reading the system clock.

Jared Morrisen wrote:
> Interesting piece...
>  
> *Weak Enforcement of Corporate Governance and Lax Technical Controls 
> Have Enabled the Illegal Backdating of Stock Options*
> 
> Feb 21, 2007
> URL: 
> http://www.wallstreetandtech.com/showArticle.jhtml?articleID=197007836 
> <http://www.wallstreetandtech.com/showArticle.jhtml;jsessionid=EFGZH0BSWEZYAQSNDLRSKHSCJUNN2JVN?articleID=197007836> 
> 
> 
> In 2006 hundreds of companies were implicated in stock-option timing 
> scandals, and a number of executives were indicted for illegally 
> backdating stock options. While greed is the primary reason for 
> backdating, it is abetted by weak enforcement of corporate governance 
> that should prevent the practice in the first place. Often, there also 
> is a lack of technical controls on corporate networks to deter such 
> activities.
> 
> Options backdating is the dating of employee stock options with an 
> earlier date than the actual date of the grant. The objective is to 
> choose a date on which the price of the underlying stock is lower than 
> the current price, resulting in an instant profit to the grantee. When 
> dealing with tens or hundreds of thousands of shares, and price 
> differentials in the range of $50 a share, the amount of illicit gain 
> can be immense.
> 
> This time distortion results not only in the value of the option being 
> much greater to the employee receiving it, but in a correlative 
> detriment to shareholders by way of stock price dilution. While 
> backdating of stock options is not necessarily illegal if the grantor of 
> the stock options properly discloses the backdating, it remains to be 
> seen whether some other fiduciary duty has been breached.
> 
> Most of the legal issues arising from backdating are a result of the 
> grantor falsifying documents to conceal the backdating. According to 
> attorney Louis Brilleman, counsel at Sichenzia Ross Friedman Ference in 
> New York, a law firm specializing in securities matters, backdating is 
> illegal under most circumstances. The practice usually leads to the 
> creation of fraudulent documents through the disclosure of misleading 
> corporate earnings and the improper reporting of the option grant under 
> applicable tax rules, Brilleman explains.
> 
> Options backdating has been going on for many years. The rules changed 
> in 2002 with the passage of Sarbanes-Oxley, but even that did not stop 
> some companies from continuing backdating practices. Accurate timing of 
> transactions ? stock or otherwise ? is fundamental to any SOX report. 
> Further, beginning in August 2002, and pursuant to SOX and other 
> securities laws, the SEC started requiring companies to disclose their 
> stock-option awards within two days of options grants.
> 
> With new regulations in place, backdating now is a regulatory issue, 
> and, as such, companies can no longer bury their heads in the sand and 
> hope no one notices. It has become clear that the element of time is now 
> an internal control. Any weaknesses in tracking the time of stock-option 
> grants must be investigated, reported and corrected.
> 
> Companies now must take the necessary steps to ensure that any 
> backdating will be detected. Besides the development of policies, 
> procedures and standards around backdating, there are technical 
> solutions that can be implemented to support such an endeavor.
> 
> *Time Synchronization Is Imperative*
> 
> These technical solutions center on time synchronization. Companies must 
> proactively create a time-synchronization mandate and ensure that it is 
> correctly deployed throughout their IT environments. Fortunately, 
> creating such a time synchronization infrastructure is relatively easy, 
> and the ROI on such an undertaking can be significant.
> 
> As time-synchronization hardware is a needed investment, properly 
> communicating the need to management is crucial to getting funding for 
> the technology. Synchronizing time is a fundamental business and 
> technology decision that should be an integral part of an effective 
> network and security architecture.
> 
> The need for this is evident in that an enterprise information network 
> and security infrastructure is highly dependent on synchronized time. In 
> addition, there also are regulatory issues that require correct 
> synchronized time ? from NASD OATS, FFIEC and GLBA, to Visa CISP and 
> many more. All of these regulations recognize that correct time is 
> critical for transactions across a network. Many events on the network 
> need the correct time to initiate jobs, complete transactions, etc. 
> Correct time is critical for billing systems, authentication systems, 
> manufacturing, forensics and more.
> 
> Common to all of these regulations is the requirement that financial 
> transactions and changes to electronic records be accurately 
> time-stamped. To provide accurate time stamps, all network devices must 
> be synchronized relative to national and international time standards.
> 
> At the application and operating system level, most applications and 
> networking protocols require correct synchronized time. Vendors such as 
> Microsoft, Cisco, Oracle, Red Hat, Novell and Baan all state that their 
> systems must be configured to an authoritative time server for proper 
> and secure use.
> 
> Time servers cost from $2,000 to $10,000, depending on the level of 
> accuracy and redundancy required. Time servers, which take but a few 
> hours to install, provide additional benefits, such as reduced downtime 
> and the ability to mitigate legal exposure.
> 
> Options backdating is the problem, and time synchronization is the 
> solution. But getting from solution to implementation takes proper 
> planning and project management. With that, the following five steps can 
> be used as a high-level framework for implementing synchronized time in 
> your organization.
> 
> *Step 1: Risks and Requirements*
> The first step is to formally determine the risk to your company if you 
> do not have synchronized time. Don't underestimate the risks; if you 
> don't practice due care pertaining to the time on your network system, 
> you can be legally liable for negligence and held accountable for the 
> ramifications of that negligence.
> 
> Next, determine how accurate your clocks need to be. This can be 
> anywhere from milliseconds to a few seconds. Finally, advise management 
> of the risks of nonsynchronized time and get their approval for the 
> purchase of time-synchronization equipment and the initiation of a 
> time-synchronization project.
> 
> *Step 2: Hardware and Software*
> Start meeting with vendors of time-synchronization equipment to 
> determine the solution that best fits your organization and specific 
> needs. Some of the leading vendors in this space include Spectracom 
> <http://www.spectracomcorp.com/>, Symmetricom 
> <http://www.symmetricom.com/> and EndRun Technologies. 
> <http://www.endruntechnologies.com/>
> 
> *Step 3: Policy*
> If policies for time synchronization are not in place already, work with 
> the information security department to ensure that time synchronization 
> becomes part of the global enterprise information technology policy. 
> Time synchronization must be made part of the corporate IT systems and 
> security policies. Without a policy, there will be no impetus for staff 
> to achieve accurate, synchronized time. Often, a simple policy, such as, 
> "Time synchronization to an accurate time source is required on all 
> enterprise network devices," is a sufficient first step.
> 
> *Step 4: Architecture*
> The first step to architecting an accurate time-synchronization solution 
> is to establish a network time source, known as a reference clock, for 
> tracability to national and international standards. A typical reference 
> clock would use GPS (Global Positioning System) to receive time from 
> satellites. Second, create a downstream topology for all network 
> components to use the reference clock as the network's master source of 
> time.
> 
> *Step 5: Auditability*
> Steps 1 through 4 are important from a technical perspective. But even 
> with the most sophisticated timing device, you still need to have 
> independent and auditable time controls in place. As part of this, you 
> must be able to prove to auditors and regulators that the time on any 
> monitored system was correctly synchronized with a specified time source.
> 
> Also, it is important to note that time synchronization will not 
> magically cure a regulatory material weakness leading to an internal 
> controls problem. Those in control of time synchronization still can 
> manipulate time and/or data. It becomes an issue, at least in part, of 
> taking control over this material weakness away from insiders. With 
> that, it is imperative to ensure that insiders are not engaging in any 
> time-based data manipulation.
> 
> Also, if something goes to court, you need to prove that all your 
> devices on your network are synchronized and that all transactions that 
> took place are able to provide an accurate, authenticated time source. 
> This requires that all logs are handled within the context of digital 
> forensics and staff members are following the appropriate rules of 
> evidence.
> 
> *Conclusion*
> The backdating fiasco demonstrates that the need for synchronized time 
> is a crucial business and technology requirement. As such, it is an 
> integral part of an effective network and security architecture. 
> Ensuring accurate time is relatively inexpensive and offers a 
> significant ROI. And it is a great way to stop your company from getting 
> negative press ? not to mention to keep your management team from being 
> indicted.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg

-- 
blu

"Remember 'A Thousand Points of Light'? With a network, we now have
a thousand points of failure."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

From jaredmorrisen at gmail.com  Thu Feb 22 07:29:35 2007
From: jaredmorrisen at gmail.com (Jared Morrisen)
Date: Thu, 22 Feb 2007 10:29:35 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
	Technical Controls Have Enabled the Illegal Backdating of
	Stock Options
In-Reply-To: <45DD9F15.2090201@sun.com>
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
	<45DD9F15.2090201@sun.com>
Message-ID: <ae8e42e00702220729kfdd151hc73c511ee00d7e90@mail.gmail.com>

>>>>But I fail to see how synchronized clocks on the network would prevent
the backdating of stock options. I guarantee that none of the options in
question got the date filled in by reading the system clock.

i think that it is based on the assumption that since the timestamp is from
a trusted and audited source, then it is the accurate one.

/jared



On 2/22/07, Brian Utterback <brian.utterback at sun.com> wrote:
>
> I don't buy this at all. I think we all agree that time sync has
> the benfits listed at the end, i.e. "integral part of an effective
> network and security architecture". But I fail to see how synchronized
> clocks on the network would prevent the backdating of stock options. I
> guarantee that none of the options in question got the date filled in
> by reading the system clock.
>
> Jared Morrisen wrote:
> > Interesting piece...
> >
> > *Weak Enforcement of Corporate Governance and Lax Technical Controls
> > Have Enabled the Illegal Backdating of Stock Options*
> >
> > Feb 21, 2007
> > URL:
> > http://www.wallstreetandtech.com/showArticle.jhtml?articleID=197007836
> > <
> http://www.wallstreetandtech.com/showArticle.jhtml;jsessionid=EFGZH0BSWEZYAQSNDLRSKHSCJUNN2JVN?articleID=197007836
> >
> >
> >
> > In 2006 hundreds of companies were implicated in stock-option timing
> > scandals, and a number of executives were indicted for illegally
> > backdating stock options. While greed is the primary reason for
> > backdating, it is abetted by weak enforcement of corporate governance
> > that should prevent the practice in the first place. Often, there also
> > is a lack of technical controls on corporate networks to deter such
> > activities.
> >
> > Options backdating is the dating of employee stock options with an
> > earlier date than the actual date of the grant. The objective is to
> > choose a date on which the price of the underlying stock is lower than
> > the current price, resulting in an instant profit to the grantee. When
> > dealing with tens or hundreds of thousands of shares, and price
> > differentials in the range of $50 a share, the amount of illicit gain
> > can be immense.
> >
> > This time distortion results not only in the value of the option being
> > much greater to the employee receiving it, but in a correlative
> > detriment to shareholders by way of stock price dilution. While
> > backdating of stock options is not necessarily illegal if the grantor of
> > the stock options properly discloses the backdating, it remains to be
> > seen whether some other fiduciary duty has been breached.
> >
> > Most of the legal issues arising from backdating are a result of the
> > grantor falsifying documents to conceal the backdating. According to
> > attorney Louis Brilleman, counsel at Sichenzia Ross Friedman Ference in
> > New York, a law firm specializing in securities matters, backdating is
> > illegal under most circumstances. The practice usually leads to the
> > creation of fraudulent documents through the disclosure of misleading
> > corporate earnings and the improper reporting of the option grant under
> > applicable tax rules, Brilleman explains.
> >
> > Options backdating has been going on for many years. The rules changed
> > in 2002 with the passage of Sarbanes-Oxley, but even that did not stop
> > some companies from continuing backdating practices. Accurate timing of
> > transactions ? stock or otherwise ? is fundamental to any SOX report.
> > Further, beginning in August 2002, and pursuant to SOX and other
> > securities laws, the SEC started requiring companies to disclose their
> > stock-option awards within two days of options grants.
> >
> > With new regulations in place, backdating now is a regulatory issue,
> > and, as such, companies can no longer bury their heads in the sand and
> > hope no one notices. It has become clear that the element of time is now
> > an internal control. Any weaknesses in tracking the time of stock-option
> > grants must be investigated, reported and corrected.
> >
> > Companies now must take the necessary steps to ensure that any
> > backdating will be detected. Besides the development of policies,
> > procedures and standards around backdating, there are technical
> > solutions that can be implemented to support such an endeavor.
> >
> > *Time Synchronization Is Imperative*
> >
> > These technical solutions center on time synchronization. Companies must
> > proactively create a time-synchronization mandate and ensure that it is
> > correctly deployed throughout their IT environments. Fortunately,
> > creating such a time synchronization infrastructure is relatively easy,
> > and the ROI on such an undertaking can be significant.
> >
> > As time-synchronization hardware is a needed investment, properly
> > communicating the need to management is crucial to getting funding for
> > the technology. Synchronizing time is a fundamental business and
> > technology decision that should be an integral part of an effective
> > network and security architecture.
> >
> > The need for this is evident in that an enterprise information network
> > and security infrastructure is highly dependent on synchronized time. In
> > addition, there also are regulatory issues that require correct
> > synchronized time ? from NASD OATS, FFIEC and GLBA, to Visa CISP and
> > many more. All of these regulations recognize that correct time is
> > critical for transactions across a network. Many events on the network
> > need the correct time to initiate jobs, complete transactions, etc.
> > Correct time is critical for billing systems, authentication systems,
> > manufacturing, forensics and more.
> >
> > Common to all of these regulations is the requirement that financial
> > transactions and changes to electronic records be accurately
> > time-stamped. To provide accurate time stamps, all network devices must
> > be synchronized relative to national and international time standards.
> >
> > At the application and operating system level, most applications and
> > networking protocols require correct synchronized time. Vendors such as
> > Microsoft, Cisco, Oracle, Red Hat, Novell and Baan all state that their
> > systems must be configured to an authoritative time server for proper
> > and secure use.
> >
> > Time servers cost from $2,000 to $10,000, depending on the level of
> > accuracy and redundancy required. Time servers, which take but a few
> > hours to install, provide additional benefits, such as reduced downtime
> > and the ability to mitigate legal exposure.
> >
> > Options backdating is the problem, and time synchronization is the
> > solution. But getting from solution to implementation takes proper
> > planning and project management. With that, the following five steps can
> > be used as a high-level framework for implementing synchronized time in
> > your organization.
> >
> > *Step 1: Risks and Requirements*
> > The first step is to formally determine the risk to your company if you
> > do not have synchronized time. Don't underestimate the risks; if you
> > don't practice due care pertaining to the time on your network system,
> > you can be legally liable for negligence and held accountable for the
> > ramifications of that negligence.
> >
> > Next, determine how accurate your clocks need to be. This can be
> > anywhere from milliseconds to a few seconds. Finally, advise management
> > of the risks of nonsynchronized time and get their approval for the
> > purchase of time-synchronization equipment and the initiation of a
> > time-synchronization project.
> >
> > *Step 2: Hardware and Software*
> > Start meeting with vendors of time-synchronization equipment to
> > determine the solution that best fits your organization and specific
> > needs. Some of the leading vendors in this space include Spectracom
> > <http://www.spectracomcorp.com/>, Symmetricom
> > <http://www.symmetricom.com/> and EndRun Technologies.
> > <http://www.endruntechnologies.com/>
> >
> > *Step 3: Policy*
> > If policies for time synchronization are not in place already, work with
> > the information security department to ensure that time synchronization
> > becomes part of the global enterprise information technology policy.
> > Time synchronization must be made part of the corporate IT systems and
> > security policies. Without a policy, there will be no impetus for staff
> > to achieve accurate, synchronized time. Often, a simple policy, such as,
> > "Time synchronization to an accurate time source is required on all
> > enterprise network devices," is a sufficient first step.
> >
> > *Step 4: Architecture*
> > The first step to architecting an accurate time-synchronization solution
> > is to establish a network time source, known as a reference clock, for
> > tracability to national and international standards. A typical reference
> > clock would use GPS (Global Positioning System) to receive time from
> > satellites. Second, create a downstream topology for all network
> > components to use the reference clock as the network's master source of
> > time.
> >
> > *Step 5: Auditability*
> > Steps 1 through 4 are important from a technical perspective. But even
> > with the most sophisticated timing device, you still need to have
> > independent and auditable time controls in place. As part of this, you
> > must be able to prove to auditors and regulators that the time on any
> > monitored system was correctly synchronized with a specified time
> source.
> >
> > Also, it is important to note that time synchronization will not
> > magically cure a regulatory material weakness leading to an internal
> > controls problem. Those in control of time synchronization still can
> > manipulate time and/or data. It becomes an issue, at least in part, of
> > taking control over this material weakness away from insiders. With
> > that, it is imperative to ensure that insiders are not engaging in any
> > time-based data manipulation.
> >
> > Also, if something goes to court, you need to prove that all your
> > devices on your network are synchronized and that all transactions that
> > took place are able to provide an accurate, authenticated time source.
> > This requires that all logs are handled within the context of digital
> > forensics and staff members are following the appropriate rules of
> > evidence.
> >
> > *Conclusion*
> > The backdating fiasco demonstrates that the need for synchronized time
> > is a crucial business and technology requirement. As such, it is an
> > integral part of an effective network and security architecture.
> > Ensuring accurate time is relatively inexpensive and offers a
> > significant ROI. And it is a great way to stop your company from getting
> > negative press ? not to mention to keep your management team from being
> > indicted.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > ntpwg mailing list
> > ntpwg at lists.ntp.isc.org
> > https://lists.ntp.isc.org/mailman/listinfo/ntpwg
>
> --
> blu
>
> "Remember 'A Thousand Points of Light'? With a network, we now have
> a thousand points of failure."
> ----------------------------------------------------------------------
> Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
> Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070222/3bd03265/attachment-0001.html 

From brian.utterback at sun.com  Thu Feb 22 08:07:51 2007
From: brian.utterback at sun.com (Brian Utterback)
Date: Thu, 22 Feb 2007 11:07:51 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
In-Reply-To: <ae8e42e00702220729kfdd151hc73c511ee00d7e90@mail.gmail.com>
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
	<45DD9F15.2090201@sun.com>
	<ae8e42e00702220729kfdd151hc73c511ee00d7e90@mail.gmail.com>
Message-ID: <45DDBFD7.2000504@sun.com>

So, all timestamps will henceforth be only from audit-able sources? As
almost all articles on option backdating have stated, it is not the
backdating that is illegal, it is doing it without disclosure. The value
of the start date has to be arbitrary, although it could default to
the current date. Are we saying that the programs that handle this data
flag any date field whose default is "now" that has its default 
overridden? It just doesn't seem to make any sense.

Jared Morrisen wrote:
>  >>>>But I fail to see how synchronized clocks on the network would 
> prevent the backdating of stock options. I guarantee that none of the 
> options in question got the date filled in by reading the system clock.
>  
> i think that it is based on the assumption that since the timestamp is 
> from a trusted and audited source, then it is the accurate one.
>  
> /jared
> 
> 
>  
> On 2/22/07, *Brian Utterback* <brian.utterback at sun.com 
> <mailto:brian.utterback at sun.com>> wrote:
> 
>     I don't buy this at all. I think we all agree that time sync has
>     the benfits listed at the end, i.e . "integral part of an effective
>     network and security architecture". But I fail to see how synchronized
>     clocks on the network would prevent the backdating of stock options. I
>     guarantee that none of the options in question got the date filled in
>     by reading the system clock.
> 
>     Jared Morrisen wrote:
>      > Interesting piece...
>      >
>      > *Weak Enforcement of Corporate Governance and Lax Technical Controls
>      > Have Enabled the Illegal Backdating of Stock Options*
>      >
>      > Feb 21, 2007
>      > URL:
>      >
>     http://www.wallstreetandtech.com/showArticle.jhtml?articleID=197007836
>      > <
>     http://www.wallstreetandtech.com/showArticle.jhtml;jsessionid=EFGZH0BSWEZYAQSNDLRSKHSCJUNN2JVN?articleID=197007836>
>      >
>      >
>      > In 2006 hundreds of companies were implicated in stock-option timing
>      > scandals, and a number of executives were indicted for illegally
>      > backdating stock options. While greed is the primary reason for
>      > backdating, it is abetted by weak enforcement of corporate governance
>      > that should prevent the practice in the first place. Often, there
>     also
>      > is a lack of technical controls on corporate networks to deter such
>      > activities.
>      >
>      > Options backdating is the dating of employee stock options with an
>      > earlier date than the actual date of the grant. The objective is to
>      > choose a date on which the price of the underlying stock is lower
>     than
>      > the current price, resulting in an instant profit to the grantee.
>     When
>      > dealing with tens or hundreds of thousands of shares, and price
>      > differentials in the range of $50 a share, the amount of illicit gain
>      > can be immense.
>      >
>      > This time distortion results not only in the value of the option
>     being
>      > much greater to the employee receiving it, but in a correlative
>      > detriment to shareholders by way of stock price dilution. While
>      > backdating of stock options is not necessarily illegal if the
>     grantor of
>      > the stock options properly discloses the backdating, it remains
>     to be
>      > seen whether some other fiduciary duty has been breached.
>      >
>      > Most of the legal issues arising from backdating are a result of the
>      > grantor falsifying documents to conceal the backdating. According to
>      > attorney Louis Brilleman, counsel at Sichenzia Ross Friedman
>     Ference in
>      > New York, a law firm specializing in securities matters,
>     backdating is
>      > illegal under most circumstances. The practice usually leads to the
>      > creation of fraudulent documents through the disclosure of misleading
>      > corporate earnings and the improper reporting of the option grant
>     under
>      > applicable tax rules, Brilleman explains.
>      >
>      > Options backdating has been going on for many years. The rules
>     changed
>      > in 2002 with the passage of Sarbanes-Oxley, but even that did not
>     stop
>      > some companies from continuing backdating practices. Accurate
>     timing of
>      > transactions ? stock or otherwise ? is fundamental to any SOX
>     report.
>      > Further, beginning in August 2002, and pursuant to SOX and other
>      > securities laws, the SEC started requiring companies to disclose
>     their
>      > stock-option awards within two days of options grants.
>      >
>      > With new regulations in place, backdating now is a regulatory issue,
>      > and, as such, companies can no longer bury their heads in the
>     sand and
>      > hope no one notices. It has become clear that the element of time
>     is now
>      > an internal control. Any weaknesses in tracking the time of
>     stock-option
>      > grants must be investigated, reported and corrected.
>      >
>      > Companies now must take the necessary steps to ensure that any
>      > backdating will be detected. Besides the development of policies,
>      > procedures and standards around backdating, there are technical
>      > solutions that can be implemented to support such an endeavor.
>      >
>      > *Time Synchronization Is Imperative*
>      >
>      > These technical solutions center on time synchronization.
>     Companies must
>      > proactively create a time-synchronization mandate and ensure that
>     it is
>      > correctly deployed throughout their IT environments. Fortunately,
>      > creating such a time synchronization infrastructure is relatively
>     easy,
>      > and the ROI on such an undertaking can be significant.
>      >
>      > As time-synchronization hardware is a needed investment, properly
>      > communicating the need to management is crucial to getting
>     funding for
>      > the technology. Synchronizing time is a fundamental business and
>      > technology decision that should be an integral part of an effective
>      > network and security architecture.
>      >
>      > The need for this is evident in that an enterprise information
>     network
>      > and security infrastructure is highly dependent on synchronized
>     time. In
>      > addition, there also are regulatory issues that require correct
>      > synchronized time ? from NASD OATS, FFIEC and GLBA, to Visa CISP and
>      > many more. All of these regulations recognize that correct time is
>      > critical for transactions across a network. Many events on the
>     network
>      > need the correct time to initiate jobs, complete transactions, etc.
>      > Correct time is critical for billing systems, authentication
>     systems,
>      > manufacturing, forensics and more.
>      >
>      > Common to all of these regulations is the requirement that financial
>      > transactions and changes to electronic records be accurately
>      > time-stamped. To provide accurate time stamps, all network
>     devices must
>      > be synchronized relative to national and international time
>     standards.
>      >
>      > At the application and operating system level, most applications and
>      > networking protocols require correct synchronized time. Vendors
>     such as
>      > Microsoft, Cisco, Oracle, Red Hat, Novell and Baan all state that
>     their
>      > systems must be configured to an authoritative time server for proper
>      > and secure use.
>      >
>      > Time servers cost from $2,000 to $10,000, depending on the level of
>      > accuracy and redundancy required. Time servers, which take but a few
>      > hours to install, provide additional benefits, such as reduced
>     downtime
>      > and the ability to mitigate legal exposure.
>      >
>      > Options backdating is the problem, and time synchronization is the
>      > solution. But getting from solution to implementation takes proper
>      > planning and project management. With that, the following five
>     steps can
>      > be used as a high-level framework for implementing synchronized
>     time in
>      > your organization.
>      >
>      > *Step 1: Risks and Requirements*
>      > The first step is to formally determine the risk to your company
>     if you
>      > do not have synchronized time. Don't underestimate the risks; if you
>      > don't practice due care pertaining to the time on your network
>     system,
>      > you can be legally liable for negligence and held accountable for
>     the
>      > ramifications of that negligence.
>      >
>      > Next, determine how accurate your clocks need to be. This can be
>      > anywhere from milliseconds to a few seconds. Finally, advise
>     management
>      > of the risks of nonsynchronized time and get their approval for the
>      > purchase of time-synchronization equipment and the initiation of a
>      > time-synchronization project.
>      >
>      > *Step 2: Hardware and Software*
>      > Start meeting with vendors of time-synchronization equipment to
>      > determine the solution that best fits your organization and specific
>      > needs. Some of the leading vendors in this space include Spectracom
>      > <http://www.spectracomcorp.com/
>     <http://www.spectracomcorp.com/>>, Symmetricom
>      > <http://www.symmetricom.com/> and EndRun Technologies.
>      > <http://www.endruntechnologies.com/
>     <http://www.endruntechnologies.com/>>
>      >
>      > *Step 3: Policy*
>      > If policies for time synchronization are not in place already,
>     work with
>      > the information security department to ensure that time
>     synchronization
>      > becomes part of the global enterprise information technology policy.
>      > Time synchronization must be made part of the corporate IT
>     systems and
>      > security policies. Without a policy, there will be no impetus for
>     staff
>      > to achieve accurate, synchronized time. Often, a simple policy,
>     such as,
>      > "Time synchronization to an accurate time source is required on all
>      > enterprise network devices," is a sufficient first step.
>      >
>      > *Step 4: Architecture*
>      > The first step to architecting an accurate time-synchronization
>     solution
>      > is to establish a network time source, known as a reference
>     clock, for
>      > tracability to national and international standards. A typical
>     reference
>      > clock would use GPS (Global Positioning System) to receive time from
>      > satellites. Second, create a downstream topology for all network
>      > components to use the reference clock as the network's master
>     source of
>      > time.
>      >
>      > *Step 5: Auditability*
>      > Steps 1 through 4 are important from a technical perspective. But
>     even
>      > with the most sophisticated timing device, you still need to have
>      > independent and auditable time controls in place. As part of
>     this, you
>      > must be able to prove to auditors and regulators that the time on
>     any
>      > monitored system was correctly synchronized with a specified time
>     source.
>      >
>      > Also, it is important to note that time synchronization will not
>      > magically cure a regulatory material weakness leading to an internal
>      > controls problem. Those in control of time synchronization still can
>      > manipulate time and/or data. It becomes an issue, at least in
>     part, of
>      > taking control over this material weakness away from insiders. With
>      > that, it is imperative to ensure that insiders are not engaging
>     in any
>      > time-based data manipulation.
>      >
>      > Also, if something goes to court, you need to prove that all your
>      > devices on your network are synchronized and that all
>     transactions that
>      > took place are able to provide an accurate, authenticated time
>     source.
>      > This requires that all logs are handled within the context of digital
>      > forensics and staff members are following the appropriate rules of
>      > evidence.
>      >
>      > *Conclusion*
>      > The backdating fiasco demonstrates that the need for synchronized
>     time
>      > is a crucial business and technology requirement. As such, it is an
>      > integral part of an effective network and security architecture.
>      > Ensuring accurate time is relatively inexpensive and offers a
>      > significant ROI. And it is a great way to stop your company from
>     getting
>      > negative press ? not to mention to keep your management team from
>     being
>      > indicted.
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      > _______________________________________________
>      > ntpwg mailing list
>      > ntpwg at lists.ntp.isc.org <mailto:ntpwg at lists.ntp.isc.org>
>      > https://lists.ntp.isc.org/mailman/listinfo/ntpwg
> 
>     --
>     blu
> 
>     "Remember 'A Thousand Points of Light'? With a network, we now have
>     a thousand points of failure."
>     ----------------------------------------------------------------------
>     Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
>     Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
> 
> 

-- 
blu

"Remember 'A Thousand Points of Light'? With a network, we now have
a thousand points of failure."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

From tglassey at earthlink.net  Thu Feb 22 09:13:42 2007
From: tglassey at earthlink.net (Todd Glassey)
Date: Thu, 22 Feb 2007 09:13:42 -0800 (GMT-08:00)
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
Message-ID: <8784343.1172164422429.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>


BLU

-----Original Message-----
>From: Brian Utterback <brian.utterback at sun.com>
>Sent: Feb 22, 2007 8:07 AM
>To: Jared Morrisen <jaredmorrisen at gmail.com>
>Cc: ntpwg at ntp.isc.org
>Subject: Re: [ntpwg] Weak Enforcement of Corporate Governance and Lax Technical Controls Have Enabled the Illegal Backdating of Stock Options
>
>So, all timestamps will henceforth be only from audit-able sources? 

YES - what a great idea...

> As
>almost all articles on option backdating have stated, it is not the
>backdating that is illegal, it is doing it without disclosure. 

As I understand it Options MUST be reported now within 48 hours to the corporate register. If those dont appear within 48 Hours in the register the option may be considered null and void aside from the other issues this would create for the Corporate Secretary. This is specifically being done to prevent Back-Dataing.

> The value
>of the start date has to be arbitrary, although it could default to
>the current date. Are we saying that the programs that handle this data
>flag any date field whose default is "now" that has its default 
>overridden? It just doesn't seem to make any sense.
>
>Jared Morrisen wrote:
>>  >>>>But I fail to see how synchronized clocks on the network would 
>> prevent the backdating of stock options. I guarantee that none of the 
>> options in question got the date filled in by reading the system clock.

They dont - but as part of an enterprise wide security and digital document processing regimen this matter is addresses IF those options are filed within the 48 hour time window required.

>>  
>> i think that it is based on the assumption that since the timestamp is 
>> from a trusted and audited source, then it is the accurate one.

Amen.

>>  
>> /jared
>> 
>> 
>>  

SNIP

From brian.utterback at sun.com  Thu Feb 22 09:44:07 2007
From: brian.utterback at sun.com (Brian Utterback)
Date: Thu, 22 Feb 2007 12:44:07 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
In-Reply-To: <8784343.1172164422429.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>
References: <8784343.1172164422429.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>
Message-ID: <45DDD667.9040505@sun.com>



Todd Glassey wrote:

>> As
>> almost all articles on option backdating have stated, it is not the
>> backdating that is illegal, it is doing it without disclosure. 
> 
> As I understand it Options MUST be reported now within 48 hours to the corporate register. If those dont appear within 48 Hours in the register the option may be considered null and void aside from the other issues this would create for the Corporate Secretary. This is specifically being done to prevent Back-Dataing.
> 

Right. And this is the best solution to the problem. If a filing is
made for an option whose start date is more than 48 hours old then
set the bells a-ringing. Either it is a back date or they waited too
long to file. Either way, get out the magnifying glass.

-- 
blu

"Remember 'A Thousand Points of Light'? With a network, we now have
a thousand points of failure."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

From mayer at ntp.isc.org  Thu Feb 22 20:48:37 2007
From: mayer at ntp.isc.org (Danny Mayer)
Date: Thu, 22 Feb 2007 23:48:37 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
In-Reply-To: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
Message-ID: <45DE7225.3070309@ntp.isc.org>

Jared Morrisen wrote:
> Interesting piece...
>  
> *Weak Enforcement of Corporate Governance and Lax Technical Controls
> Have Enabled the Illegal Backdating of Stock Options*
> 

Please take this elsewhere. This has nothing to do with NTP which deals
with technical issues involving millisecond accuracy while you are
foisting stories on social/governance issues involving days and weeks.

Danny

From brian.utterback at sun.com  Fri Feb 23 06:06:40 2007
From: brian.utterback at sun.com (Brian Utterback)
Date: Fri, 23 Feb 2007 09:06:40 -0500
Subject: [ntpwg] Weak Enforcement of Corporate Governance and Lax
 Technical Controls Have Enabled the Illegal Backdating of Stock Options
In-Reply-To: <45DE7225.3070309@ntp.isc.org>
References: <ae8e42e00702211442y6718ab8cua6433ef4312f0ca8@mail.gmail.com>
	<45DE7225.3070309@ntp.isc.org>
Message-ID: <45DEF4F0.3020709@sun.com>

Well, the article is pretty explicitly talking about NTP, so it does
have to do with NTP. However, I agree that it doesn't have anything to
do with the technical issues involved with NTP implementation.

Danny Mayer wrote:
> Jared Morrisen wrote:
>> Interesting piece...
>>  
>> *Weak Enforcement of Corporate Governance and Lax Technical Controls
>> Have Enabled the Illegal Backdating of Stock Options*
>>
> 
> Please take this elsewhere. This has nothing to do with NTP which deals
> with technical issues involving millisecond accuracy while you are
> foisting stories on social/governance issues involving days and weeks.
> 
> Danny
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg

-- 
blu

"Remember 'A Thousand Points of Light'? With a network, we now have
a thousand points of failure."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

From Helen.Y.Chen at motorola.com  Wed Feb 28 15:22:26 2007
From: Helen.Y.Chen at motorola.com (Chen Helen-A12587)
Date: Wed, 28 Feb 2007 18:22:26 -0500
Subject: [ntpwg] Updated draft
In-Reply-To: <45D105A7.10603@udel.edu>
References: <45CD4CC9.1020405@udel.edu> <45CF8FEC.1000007@ntp.isc.org>
	<655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
	<45D105A7.10603@udel.edu>
Message-ID: <655403F33031E14DB1EDF142287304750180970F@de01exm68.ds.mot.com>

Dave,

Thank you. I have a few questions related to the autokey protocol
document:

*	The autokey protocol assumes server is polled 1/minute. Would
the performance become unacceptable if the server is polled more often
than once per minute, e.g. in the order of 300 polls per minute?
*	From what I read off the NTP Project website, it seems that your
team has done performance analysis on NTPv4 and/or the autokey protocol.
Would it be possible to share the outcome of the analysis?
*	Autokey dance at beginning of protocol requires several
exchanges to establish various keys, cookies, identity scheme, etc. Are
ALL 5 exchanges (Parameter, Certificate, Identity, Values and Signature
Exchanges) mandatory for the autokey protocol to work?
*	From what I read, it seems that the autokey authentication is
performed for each request, correct?

Thanks,
Helen

-----Original Message-----
From: David L. Mills [mailto:mills at udel.edu]
Sent: Monday, February 12, 2007 6:26 PM
To: Chen Helen-A12587
Cc: mayer at ntp.isc.org; ntpwg at ntp.isc.org
Subject: Re: [ntpwg] Updated draft

Chen,

The document is now restored. The Windwoes name was in upper case; the
Unix link in lower case. Sign.

There is no provision for Autokey in the standards document. In
prinicple there could be, but it doesn't seem useful to add all that
baggage and not make a NTP-conformant version. I'm happy to add that
option to the SNTP text if this seems desirable.

Dave

Chen Helen-A12587 wrote:

> Danny, David,
>
> The link I tried (draft-ietf-ntp-ntpv4-proto-04) didn't work. I would
> like to know if SNTPv4 includes the sutokey algorithm, or if the
> autokey can only be implemented in NTPv4.
>
> Thanks,
> Helen Chen
>
> -----Original Message-----
> From: ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org
> [mailto:ntpwg-bounces+helen.y.chen=motorola.com at lists.ntp.isc.org] On
> Behalf Of Danny Mayer
> Sent: Sunday, February 11, 2007 3:52 PM
> To: David L. Mills
> Cc: ntpwg at ntp.isc.org
> Subject: Re: [ntpwg] Updated draft
>
> That's exactly what I wanted. Otherwise I would have opposed it going
> forward with it obsoleting RFC 4330. I think I'll start reviewing your
> edited version instead.
>
> Danny
>
> David L. Mills wrote:
>
>> 3. The SNTP protocol subset now has a separate section. The
>> implementer wishing to build SNTP can avoid eye fatigue with the full
>
> NTP prose.
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/ntpwg



-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ntp.isc.org/pipermail/ntpwg/attachments/20070228/f1493660/attachment.html 

From mayer at ntp.isc.org  Wed Feb 28 20:47:50 2007
From: mayer at ntp.isc.org (Danny Mayer)
Date: Wed, 28 Feb 2007 23:47:50 -0500
Subject: [ntpwg] Updated draft
In-Reply-To: <655403F33031E14DB1EDF142287304750180970F@de01exm68.ds.mot.com>
References: <45CD4CC9.1020405@udel.edu> <45CF8FEC.1000007@ntp.isc.org>
	<655403F33031E14DB1EDF142287304750175AC88@de01exm68.ds.mot.com>
	<45D105A7.10603@udel.edu>
	<655403F33031E14DB1EDF142287304750180970F@de01exm68.ds.mot.com>
Message-ID: <45E65AF6.6040002@ntp.isc.org>

Chen Helen-A12587 wrote:
> Dave,
> 
> Thank you. I have a few questions related to the autokey protocol document:
> 
>     * The autokey protocol assumes server is polled 1/minute.

I doubt that you will find that to be true. Can you point to any
document that says that? The autokey protocol has no need to make that
assumption. When the client receives the first packet with the autokey,
it immediately sends back a packet to that server asking for further
information (described in the autokey protocol). The server responds
with that information and the client immediately asks additional
information of the server until it has satisfied itself that the server
is authenticated or not. This is known as the autokey dance. After that
it will accept the NTP packets from that specific server as long as the
authentication information is found in the packet and follows the
autokey requirements.

> Would the
>       performance become unacceptable if the server is polled more often
>       than once per minute, e.g. in the order of 300 polls per minute?

Why would you ever do that? Or are you asking if multiple clients make
requests and the server needs to handle 300 requests/minute? I stress
test servers and it sends much more than that from multiple places and
the load is barely visible and certainly not noticeable.

>     * Autokey dance at beginning of protocol requires several exchanges
>       to establish various keys, cookies, identity scheme, etc. Are ALL
>       5 exchanges (Parameter, Certificate, Identity, Values and
>       Signature Exchanges) mandatory for the autokey protocol to work?

Yes. It stops as soon as it has determined that the server is authentic
(or not).

>     * From what I read, it seems that the autokey authentication is
>       performed for each request, correct?

Yes, in the sense that it checks and validates the authentication part o
the header each time that it receives the packet.

Danny

