Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-proto-00

["David L. Mills" <[e-mail]>]

Jack,

There once was a 01 draft which superseeded the 00 draft. I don't know 
where it went, but it left my warm soft hands. I suspect the draft I 
sent, which was not in pure Postel ASCII was not purified like the first 
draft was. Most of you know my violent, serious objections about purity. 
Send me PDF so I can mark it up. I can't do that effectively in ROFFed text.

Dave

Burbank, Jack L. wrote:

> Hi All:
>
> The text referring to anycast came from the I-D
> <draft-mills-sntp-v4-00.txt> which is currently in the RFC-Editor queue
> to be published as an Informational RFC as an update to RFC 2030.
>
> The overall approach to writing this draft we have been taking is as
> follows:
>
> -take material as closely to 'as-is' as possible from existing NTP
> documentation. The overall structure of the document is based on the
> structure of <draft-mills-sntp-v4-00.txt> (per recommendations from the
> group during the Washington DC BOF). The material in the 00 draft is
> largely based on material from <draft-mills-sntp-v4-00.txt>, RFC 2030
> (the original SNTPv4 spec), and RFC 1305 (NTPv3 specification) (more so
> on <draft-mills-sntp-v4-00.txt> and RFC 2030. Several documents from
> the NTP.org website was also used. This document could then be used as
> a consolidated basis from which the working group can prepare the
> document for publication.
>
> -add any material that needs to be added to take into account the
> differences between NTPv4 and SNTPv4, and add any other details that are
> missing
>
> -correct and clean up text as necessary. For example, there were
> several IESG comments on <draft-mills-sntp-v4-00.txt> that the group now
> needs to address. In particular, a couple of IESG members cited the
> need to clean up language on anycast, multicast, and broadcast. For
> example, the text currently refers to IPv6 broadcast addresses, which
> does not exist.
>
> Jack
>
>
>
> -----Original Message-----
> From: Danny Mayer [mailto:[e-mail]]
> Sent: Monday, August 01, 2005 11:38 AM
> To: David L. Mills
> Cc: Hiroshi KITAMURA; Burbank, Jack L.; [e-mail];
> [e-mail]
> Subject: Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-proto-00
>
>
> David L. Mills wrote:
>
>> Danny,
>>
>> Are you guys using the "official" document at
>> www.eecis.udel.edu/~mills/database/reports/stime.pdf? There is no
>> mention of anycast anywhere, only manycast. The only reference to
>> multicast is to say any reference to broadcast implies multicast as
>> well. A number of typos were found at the last review, long since
>
> fixed.
>
>> Dave
>>
> Dave,
>
> I'm talking about a draft put together by Jack Burbank and Jim Martin. I
>
> had never seen it before or been notified about it as far as I can
> recall. I don't believe a note was sent to the NTP Working Group about
> it though one should have been. The URL for this document is:
>
> http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-proto-00.txt
>
> Jack could you please say something about this document?
>
> Danny