Re: ietf-nntp Three proposals
Brian Hernacki <bhern@netscape.com> Fri, 13 December 1996 06:12 UTC
Received: from cnri by ietf.org id aa22000; 13 Dec 96 1:12 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa02934;
13 Dec 96 1:12 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id
AAA08719 for ietf-nntp-outgoing; Fri, 13 Dec 1996 00:10:27 -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 AAA08714 for
<ietf-nntp@ACADEM2.ACADEM.COM>; Fri, 13 Dec 1996 00:10:25 -0600 (CST)
Received: from r2d2.mcom.com (h-205-217-237-47.netscape.com [205.217.237.47])
by academ.com (8.8.3/8.7.1) with ESMTP id AAA11531 for <ietf-nntp@academ.com>;
Fri, 13 Dec 1996 00:10:23 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by
r2d2.mcom.com (8.7.5/8.7.3) with ESMTP id WAA26219 for <ietf-nntp@academ.com>;
Thu, 12 Dec 1996 22:09:50 -0800 (PST)
Received: from ventnor.mcom.com ([207.1.137.53]) by dredd.mcom.com
(Netscape Mail Server v2.02) with SMTP id AAA15830;
Thu, 12 Dec 1996 22:09:51 -0800
Message-ID: <32B0F363.799A@netscape.com>
Date: Thu, 12 Dec 1996 22:10:44 -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: "David Johnson (Exchange)" <djohnson@exchange.microsoft.com>
CC: ietf-nntp@academ.com, 'Ben Polk' <bpolk@netscape.com>
Subject: Re: ietf-nntp Three proposals
References: <2FBF98FC7852CF11912A0000000000010360557B@DINO>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
David Johnson (Exchange) wrote: > I think we should be careful about which commands are made mandatory. In > my opinion XPAT is only marginally useful, so why should it be required? > I would like to see a list of the newsreaders that won't function > without XPAT support. If this list is some number greater than one then > maybe it should be required. On the other hand, I have seen many clients > that won't function without XOVER, so it is reasonable to make this a > required command. We need to define a criteria for taking a de-facto extension and making it a required part of the base protocol. > I made the assertion at the BOF that "X" and "X-" naming conventions > don't work and I still stand by that. We should document the commands as > they exist. The only reliable way to prevent namespace problems is to > establish a registry for extensions. It does seem a bit silly to rename and bust clients...or even encourgae folks to develop implementations that would bust existing clients (what I think will happen if we rename). But if we allow X-commands to become "real"..then we might as well scrap the idea of X-commands being "local" or "experimental". It shoudl be one way or ther other. I think the plan for the extensions mechanism was to have some semi-formal way of registering names for new extensions, so it seems like only existing extensions are in question. --brian
- ietf-nntp Three proposals Ben Polk
- Re: ietf-nntp Three proposals coneill
- Re: ietf-nntp Three proposals Clive D.W. Feather
- RE: ietf-nntp Three proposals David Johnson (Exchange)
- Re: ietf-nntp Three proposals Brian Hernacki
- Re: ietf-nntp Three proposals Petter Nilsen
- Re: ietf-nntp Three proposals Chris Lewis
- RE: ietf-nntp Three proposals Ian King
- Re: ietf-nntp Three proposals Ofer Inbar
- Re: ietf-nntp Three proposals Ben Polk
- Re: ietf-nntp Three proposals Ofer Inbar