RE: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-proto-00
"Burbank, Jack L." <Jack.Burbank@jhuapl.edu> Mon, 01 August 2005 17:22 UTC
Return-Path: <Jack.Burbank@jhuapl.edu>
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by ntp1.ntp.isc.org (Postfix) with ESMTP id 7B7FE39A57 for <ntpwg@lists.ntp.isc.org>; Mon, 1 Aug 2005 17:22:01 +0000 (UTC) (envelope-from Jack.Burbank@jhuapl.edu)
Received: from ntp1.ntp.isc.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13636-05 for <ntpwg@lists.ntp.isc.org>; Mon, 1 Aug 2005 17:21:59 +0000 (UTC)
Received: from APLESLIBERTY.dom1.jhuapl.edu (APLesliberty.dom1.jhuapl.edu [128.244.198.134]) by ntp1.ntp.isc.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Mon, 1 Aug 2005 17:21:59 +0000 (UTC) (envelope-from Jack.Burbank@jhuapl.edu)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-proto-00
Date: Mon, 01 Aug 2005 13:21:58 -0400
Message-ID: <79C724060977164B9F92367BE65372C7031476CB@aplesliberty.dom1.jhuapl.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-proto-00
Thread-Index: AcWWrzAKavArkpJTSRqDcw6E7lFdtAADF3AQ
From: "Burbank, Jack L." <Jack.Burbank@jhuapl.edu>
To: mayer@gis.net, "David L. Mills" <mills@udel.edu>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ntp1.isc.org
X-Spam-Status: No, hits=0.1 tagged_above=-999.0 required=5.0 tests=TW_TP
X-Spam-Level:
Cc: ntpwg@lists.ntp.isc.org, anycast@anarg.jp
X-BeenThere: ntpwg@lists.ntp.isc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.isc.org>
List-Unsubscribe: <https://lists.ntp.isc.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.isc.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.isc.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.isc.org>
List-Help: <mailto:ntpwg-request@lists.ntp.isc.org?subject=help>
List-Subscribe: <https://lists.ntp.isc.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.isc.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2005 17:22:02 -0000
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:mayer@gis.net] Sent: Monday, August 01, 2005 11:38 AM To: David L. Mills Cc: Hiroshi KITAMURA; Burbank, Jack L.; ntpwg@lists.ntp.isc.org; anycast@anarg.jp 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
- [ntpwg] anycast usage in draft-ietf-ntp-ntpv4-pro… Hiroshi KITAMURA
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Brad Knowles
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… David L. Mills
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Danny Mayer
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… David L. Mills
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Danny Mayer
- RE: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Odonoghue, Karen F CIV B35-Branch
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Danny Mayer
- RE: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Burbank, Jack L.
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Brian Haberman
- RE: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Burbank, Jack L.
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Danny Mayer
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… Brad Knowles
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… David L. Mills
- Re: [ntpwg] anycast usage in draft-ietf-ntp-ntpv4… David L. Mills