Re: [Ntp] Last Call: <draft-ietf-ntp-mode-6-cmds-08.txt> (Control Messages Protocol for Use with Network Time Protocol Version 4) to Historic RFC

Pete Resnick <resnick@episteme.net> Tue, 02 June 2020 17:17 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2DAB3A0CAF; Tue, 2 Jun 2020 10:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ja88mrDvl7R; Tue, 2 Jun 2020 10:17:49 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30E1D3A0CB2; Tue, 2 Jun 2020 10:17:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 59EC2AF354AD; Tue, 2 Jun 2020 12:17:48 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNhYVuK_M36Y; Tue, 2 Jun 2020 12:17:46 -0500 (CDT)
Received: from [172.16.1.29] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id C6781AF3549F; Tue, 2 Jun 2020 12:17:46 -0500 (CDT)
From: "Pete Resnick" <resnick@episteme.net>
To: last-call@ietf.org
Cc: ntp@ietf.org, ek.ietf@gmail.com, ntp-chairs@ietf.org, draft-ietf-ntp-mode-6-cmds@ietf.org, "Karen O'Donoghue" <odonoghue@isoc.org>
Date: Tue, 02 Jun 2020 12:17:24 -0500
X-Mailer: MailMate (1.13.1r5683)
Message-ID: <45F5F313-BFC6-48BB-B5A3-D47C48AE87D6@episteme.net>
In-Reply-To: <159103987149.20717.15985853306560767734@ietfa.amsl.com>
References: <159103987149.20717.15985853306560767734@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/TrUZAT47Q2IwSYyPq3gHo7zlj3I>
X-Mailman-Approved-At: Tue, 02 Jun 2020 12:00:07 -0700
Subject: Re: [Ntp] Last Call: <draft-ietf-ntp-mode-6-cmds-08.txt> (Control Messages Protocol for Use with Network Time Protocol Version 4) to Historic RFC
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2020 17:17:51 -0000

This use of the "Historic" status seems utterly bizarre to me. It's 
certainly not how it's described in 2026.

1305 has already been obsoleted by 5905. This document simply gives 
information about what those control messages were and indicates that 
they ought no longer be used. This sounds like a fine candidate for 
Informational status. When 5905 (or it's successors) advance to 
Standard, this document can be included in the STD.

If eventually you want to move a document to Historic, it would be 1305.

I don't think publishing this straight to Historic makes sense.

pr

On 1 Jun 2020, at 14:31, The IESG wrote:

> The IESG has received a request from the Network Time Protocol WG 
> (ntp) to
> consider the following document: - 'Control Messages Protocol for Use 
> with
> Network Time Protocol Version 4'
>   <draft-ietf-ntp-mode-6-cmds-08.txt> as Historic RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits 
> final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2020-06-15. Exceptionally, 
> comments may
> be sent to iesg@ietf.org instead. In either case, please retain the 
> beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes the structure of the control messages that
>    were historically used with the Network Time Protocol before the
>    advent of more modern control and management approaches.  These
>    control messages have been used to monitor and control the Network
>    Time Protocol application running on any IP network attached
>    computer.  The information in this document was originally 
> described
>    in Appendix B of RFC 1305.  The goal of this document is to provide 
> a
>    current, but historic, description of the control messages as
>    described in RFC 1305 and any additional commands implemented in 
> NTP.
>
>    The publication of this document is not meant to encourage the
>    developement and deployment of these control messages.  This 
> document
>    is only providing a current reference for these control messages
>    given the current status of RFC 1305.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-ntp-mode-6-cmds/
>
>
>
> No IPR declarations have been submitted directly on this I-D.


-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best