Re: ietf-nntp Comments on "NNTP LIST additions"

Brian Hernacki <bhern@netscape.com> Wed, 11 December 1996 17:27 UTC

Received: from cnri by ietf.org id aa00612; 11 Dec 96 12:27 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa06653; 11 Dec 96 12:27 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id LAA03213 for ietf-nntp-outgoing; Wed, 11 Dec 1996 11:22:46 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id LAA03208 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 11 Dec 1996 11:22:37 -0600 (CST)
Received: from c3po.mcom.com (h-205-217-237-46.netscape.com [205.217.237.46]) by academ.com (8.8.3/8.7.1) with ESMTP id LAA05244 for <ietf-nntp@academ.com>; Wed, 11 Dec 1996 11:22:29 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by c3po.mcom.com (8.7.5/8.7.3) with ESMTP id JAA20167 for <ietf-nntp@academ.com>; Wed, 11 Dec 1996 09:21:56 -0800 (PST)
Received: from ventnor.mcom.com ([207.1.137.53]) by dredd.mcom.com (Netscape Mail Server v2.02) with SMTP id AAA22255; Wed, 11 Dec 1996 09:21:57 -0800
Message-ID: <32AEEDEC.630A@netscape.com>
Date: Wed, 11 Dec 1996 09:22:52 -0800
From: Brian Hernacki <bhern@netscape.com>
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.0GoldC (X11; U; SunOS 5.5 sun4u)
MIME-Version: 1.0
To: Rich Salz <rsalz@osf.org>
CC: ietf-nntp@academ.com
Subject: Re: ietf-nntp Comments on "NNTP LIST additions"
References: <9612071900.AA13151@sulphur.osf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Rich Salz wrote:
> 
> 3.3, 3.4:  Why "listsubscr" and "listpnames"?  Why not use the long form
> that is used in the command itself "LISTSUBSCRIPTIONS" and "LISTPRETTYNAMES"
> I don't see a need to be terse and introduce aliases.

In the NNTP revision draft that specifies LIST EXTENSIONS, there is (or
was) a length limit on extension names. Originally, I did have the names
you suggested, but cut them down to fit the draft.


> 4.1:  I think 977 uses the term "multi-line text response" which is
> how the data is returned.  "May be multiline" is misleading -- even if
> it's one line, it is a mltr :)

Good point. I'll change it.

> 4.7:  I think DISPLAYNAMES is marginally better (less judgemental :)
> than PRETTYNAMES, but that's a nit.  How is the codeset identified
> even if its an 8bit charset, e.g., the different european variants?
> Should it also follow the =?8890?= encoding rules?

I forget exactly how that arrived, but people just started calling them
PRETTYNAMES and the term stuck. If anyone has a real problem with the
term, I'm not that attached to it.

As for charset, I was trying to leave it open enough that people could
use it as they saw fit, but I see your point. I will try to clarify
that. Suggestions (from anyone) are welcome.

> I think there should be a short explanation of why this command is
> needed in addition to XGTITLE.

I'll add that.

--brian