Re: ietf-nntp Thoughts on renaming X commands

NetWin Support <netwin@world.std.com> Wed, 16 October 1996 02:31 UTC

Received: from cnri by ietf.org id aa29412; 15 Oct 96 22:31 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa28470; 15 Oct 96 22:31 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id VAA18134 for ietf-nntp-outgoing; Tue, 15 Oct 1996 21:28:09 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id VAA18130 for <ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 15 Oct 1996 21:28:07 -0500
Received: from ring.netwin.co.nz (netwin.internet.co.nz [202.37.144.132]) by academ.com (8.7.6/8.7.1) with SMTP id VAA01534 for <ietf-nntp@academ.com>; Tue, 15 Oct 1996 21:26:45 -0500 (CDT)
Received: from BALL (BALL [161.29.2.5]) by ring.netwin.co.nz (NTMail 3.02.10) with ESMTP id ha004817 for <ietf-nntp@academ.com>; Wed, 16 Oct 1996 15:28:23 +0100
Comments: Authenticated sender is <netwin@iconz.co.nz>
From: NetWin Support <netwin@world.std.com>
To: ietf-nntp@academ.com
Date: Wed, 16 Oct 1996 15:28:12 +0000
Subject: Re: ietf-nntp Thoughts on renaming X commands
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42)
Message-Id: <02282368500021@netwin.co.nz>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> >the purpose of the doing this work in the first place.
> 
> To document existing practice and define a mechanism for future work?
> 

I'd like to add my vote to this concept, the purpose should
be to document existing practice.  Currently its very difficult
producing software that works with any server/reader when there
is no documented standard.  (I remember discovering the xhdr
command by spying on ethernet packets a few years ago)

I think the real problem is the current state of 'x' commands
is a mess, but it cannot be tidied up just by 
re-writing the standard and ignoring reality.  
The standard must include the current state to
be useful to developers of servers and readers
in the future.

The non 'x' commands can be added, but the common 'x' commands must
also be documented.

Just wanted to register my opinion even if it doesn't do any good.

          ChrisP, NetWin Ltd.

 
Customer Support
http://netwinsite.com