IETF Logo Mail Archive

SNTP implementation recommendations (was "Re: [ntpwg] SNTP clients")

Dave Plonka <plonka@doit.wisc.edu> Thu, 28 April 2005 15:35 UTC

Return-Path: <dplonka@mil.doit.wisc.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 D977C39A66 for <ntpwg@lists.ntp.isc.org>; Thu, 28 Apr 2005 15:35:42 +0000 (UTC) (envelope-from dplonka@mil.doit.wisc.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 73416-01 for <ntpwg@lists.ntp.isc.org>; Thu, 28 Apr 2005 15:35:40 +0000 (UTC)
Received: from mil.doit.wisc.edu (mil.doit.wisc.edu [128.104.31.31]) by ntp1.ntp.isc.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Thu, 28 Apr 2005 15:35:37 +0000 (UTC) (envelope-from dplonka@mil.doit.wisc.edu)
Received: from dplonka by mil.doit.wisc.edu with local (Exim 3.13 #1) id 1DRB3A-0007l1-00; Thu, 28 Apr 2005 10:35:36 -0500
Date: Thu, 28 Apr 2005 10:35:36 -0500
From: Dave Plonka <plonka@doit.wisc.edu>
To: ntpwg@lists.ntp.isc.org
Subject: SNTP implementation recommendations (was "Re: [ntpwg] SNTP clients")
Message-ID: <20050428103536.A21974@doit.wisc.edu>
References: <41B9D8A6CE9E0A4583291742EECF3CCB05173B0B@mail.wirelessworld.airvananet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <41B9D8A6CE9E0A4583291742EECF3CCB05173B0B@mail.wirelessworld.airvananet.com>; from jterry@airvananet.com on Thu, Apr 28, 2005 at 09:37:24AM -0400
X-Organization: University of Wisconsin-Madison, DoIT Network Services
X-Organization-Too: Wisconsin Advanced Internet Laboratory (WAIL)
X-URL: http://net.doit.wisc.edu/~plonka/
X-VMS-Error: %SYSTEM-F-SUBRNG4, subscript 4 range error, PC=00000000, PS=0000058C
X-Shakespearean-Insult: Thou gleeking unchin-snouted whey-face
Sender: Dave Plonka <dplonka@mil.doit.wisc.edu>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ntp1.isc.org
X-Spam-Status: No, hits=-1.0 tagged_above=-999.0 required=5.0 tests=X_URL
X-Spam-Level:
Cc:
X-BeenThere: ntpwg@lists.ntp.isc.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: plonka@doit.wisc.edu
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: <https://lists.ntp.isc.org/mailman/private/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: Thu, 28 Apr 2005 15:35:43 -0000

Hi Jason,

On Thu, Apr 28, 2005 at 09:37:24AM -0400, Jason Terry wrote:
> 
> I am trying to improve an SNTP client implementation.  I was wondering
> if anyone could point me to a resource that has information on the
> real-world issues developers face when implementing an SNTP client.

I made some comments/recommendations in this BCP RFC (numbers yet to be
assigned):

   http://www.ietf.org/internet-drafts/draft-ietf-grow-embed-addr-05.txt

Also, I believe one of the vendor consortiums (perhaps DOCSIS?)
codified some of our recommendations in their specs, but I've lots the
reference.  If someone knows where I can find it, please let me know.

In addtion to RFC2030:

   ftp://ftp.rfc-editor.org/in-notes/rfc2030.txt

we worked on this updated draft which is probably closest to what you want:

   http://www.eecis.udel.edu/~mills/database/rfc/draft-mills-sntp-v4-00.txt

Dave

P.S. You might also find this backgroun info pertient - in my technical
report here:

   http://www.cs.wisc.edu/~plonka/netgear-sntp/

and in the related presentations, for instance at LISA and NANOG:

   http://net.doit.wisc.edu/~plonka/lisa/lisa2003/
   http://www.nanog.org/mtg-0310/plonka.html

-- 
plonka@doit.wisc.edu  http://net.doit.wisc.edu/~plonka  ARS:N9HZF  Madison, WI

v2.23.0 | Report a Bug | By Email