Re: [ntpwg] slight modification to charter based on comments received

Thomas Narten <narten@us.ibm.com> Tue, 15 February 2005 02:48 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: ntpwg@ntp.isc.org
Delivered-To: ntpwg@ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by ntp1.ntp.isc.org (Postfix) with ESMTP id BA9DC115E9; Tue, 15 Feb 2005 02:48:32 +0000 (UTC) (envelope-from narten@us.ibm.com)
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 39695-07; Tue, 15 Feb 2005 02:48:31 +0000 (UTC)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by ntp1.ntp.isc.org (Postfix) with ESMTP; Tue, 15 Feb 2005 02:48:30 +0000 (UTC) (envelope-from narten@us.ibm.com)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j1F2mTua475828; Mon, 14 Feb 2005 21:48:29 -0500
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay05.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j1F2mSoO266214; Mon, 14 Feb 2005 19:48:28 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j1F2mSGn014523; Mon, 14 Feb 2005 19:48:28 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-250-225.mts.ibm.com [9.65.250.225]) by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j1F2mRVG014510; Mon, 14 Feb 2005 19:48:27 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j1F2mHYm006231; Mon, 14 Feb 2005 21:48:17 -0500
Message-Id: <200502150248.j1F2mHYm006231@cichlid.raleigh.ibm.com>
To: "Odonoghue, Karen F CIV B35-Branch" <karen.odonoghue@navy.mil>
Subject: Re: [ntpwg] slight modification to charter based on comments received
In-Reply-To: Message from "Odonoghue, Karen F CIV B35-Branch" <karen.odonoghue@navy.mil> of "Mon, 14 Feb 2005 01:39:19 CST." <1929B8C5B318524495727D8A241DAFB201C84B47@NAEAMILLEX03VA.nadsusea.nads.navy.mil>
Date: Mon, 14 Feb 2005 21:48:17 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ntp1.isc.org
X-Spam-Status: No, hits=0.0 tagged_above=-999.0 required=5.0 tests=
X-Spam-Level:
Cc: ntpwg@ntp.isc.org, mills@udel.edu
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: <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: Tue, 15 Feb 2005 02:48:33 -0000

> I believe the plan for SNTP based on my examination of the
> id-tracker is...

> Work with Dave Mills do some cleanup and publish an Informational
> RFC update to SNTP as soon as possible.

Actually, it was my understanding that (per the last BOF), the RFC
editor would publish draft-mills-sntp-v4-00.txt pretty much straight
away (as an informational document), and the WG would not be involved
in work on that document per se.

Or did I get this wrong?

> Pursue a more robust standards track SNTP specification as
> part of the NTPv4 protocol specification.

I think this would then be your first work item.

> I have pulled the comments from the IESG out of the id-tracker and
> attached them below.

These comments were the result of the IESG review of draft-mills. The
IESG intends to notify the RFC Editor that the document can be
published and that publication of the document does not conflict with
this WG. It is then between the RFC Editor (and the author) how the
IESG comments are to be resolved (per RFC 3932).

It is also my understanding that the RFC Editor has been working with
Dave Mills and that version 01 is in the works (or has already been
done) that addresses most of the issues that were raised in the IESG
review.

Thomas