
From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue Feb 15 11:44:32 2011
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 996D13A6D6D for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X+oX+lu0wXjE for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:44:31 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id 96EA83A6D10 for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:44:28 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id 0EF4A67E14 for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:44:54 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 5F36A67E0D for <ietf-nntp@lists.eyrie.org>; Tue, 15 Feb 2011 11:44:52 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 438898147; Tue, 15 Feb 2011 20:44:21 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuVnWQExDrv0; Tue, 15 Feb 2011 20:44:21 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-153-1-47-217.w83-200.abo.wanadoo.fr [83.200.15.217]) by denver.dinauz.org (Postfix) with ESMTPSA id DA12C8072; Tue, 15 Feb 2011 20:44:20 +0100 (CET)
Message-ID: <4D5AD794.5010902@trigofacile.com>
Date: Tue, 15 Feb 2011 20:44:20 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ah@tr-sys.de
Subject: [NNTP] Wording for the "x" status in RFC 6048
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: NNTP protocol discussion <ietf-nntp.lists.eyrie.org>
List-Unsubscribe: <http://lists.eyrie.org/mailman/options/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=unsubscribe>
List-Archive: <http://lists.eyrie.org/pipermail/ietf-nntp>
List-Post: <mailto:ietf-nntp@lists.eyrie.org>
List-Help: <mailto:ietf-nntp-request@lists.eyrie.org?subject=help>
List-Subscribe: <http://lists.eyrie.org/mailman/listinfo/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=subscribe>
Sender: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

Following a discussion with Alfred Hönes, who reported:

> The only place where I got stuck in RFC 6048 was in Section 3.1,
> in the 6th paragraph on page 17.  The RFC says:
> 
> |  A newsgroup with status "x" is a newsgroup with status "n", except
> |  that articles from peers are not accepted.  [...]
> 
> Given the definition from RFC 3977 that you quote slightly above,
> at the bottom of page 16,
> 
>     "n"  Posting is not permitted.
> 
> the "except that" does not make sense to me.
> 
> (In contrast, where the 7th paragraph says ...
> 
> |  A newsgroup with status "j" is a newsgroup with status "y", except
> |  that (1) local postings are not accepted, (2) articles received from
>     a peer that are crossposted to one or more valid groups are filed
>     only into those valid groups, and (3) articles received from a peer
>     that are not crossposted to any valid groups are not filed into any
>     newsgroup, but are still propagated to other peers, if appropriate.
> 
> ... "except that" makes perfect sense.)
> 
> Reading the subsequent explanations and examples, I conclude that
> the RFC 3977 status field values only affect local posting and
> are transparent to forwarding behavior.
> 
> Therefore, it would IMO have been less surprising/confusing if the
> 6th paragraph would have said:
>                                                                vvvvvvvvv
> |  A newsgroup with status "x" is a newsgroup with status "n", for which
> |  articles from peers also are not accepted.  [...]
>   ^                   ^^^^^^
> 
> Is that correct?
> Would it make sense to post that adjustment as an Errata Note?

What annoys me most here is that RFC 3977 is not clear enough
when it describes status field values.
"Posting" means "Injection" (USEPRO [RFC 5537] terminology).
We have in RFC 3977:

3.4.1.  Reading and Transit Servers

   NNTP is traditionally used in two different ways.  The first use is
   "reading", where the client fetches articles from a large store
   maintained by the server for immediate or later presentation to a
   user and sends articles created by that user back to the server (an
   action called "posting") to be stored and distributed to other stores
   and users.  The second use is for the bulk transfer of articles from
   one store to another.  Since the hosts making this transfer tend to
   be peers in a network that transmit articles among one another, and
   not end-user systems, this process is called "peering" or "transit".
   (Even so, one host is still the client and the other is the server).

So basically, "Posting is not permitted." means that injection is not
permitted while relaying is.
That's why I wrote "except that articles from peers are not accepted"
because "x" means that relaying is not allowed in a newsgroup whose
status is "x".


I also explicitly mentioned it before in RFC 6048, in the introduction,
Section 1:

   The ACTIVE variant was formalized in [RFC3977], but the meanings of
   only three status field values in LIST ACTIVE responses have been
   specified: "y", "n", and "m".  These statuses are particularly useful
   for readers, since they describe local posting rights.  However,
   several other statuses are in use that are primarily useful for peers
   as they mainly describe how remote articles coming from peers are
   locally handled by a given news server.  This memo defines three
   other values for the status field in LIST ACTIVE responses: "x", "j",
   and "=" followed by the name of a newsgroup.




The new wording Alfred suggests is correct.

I ask the working group:
After reading the explanations below, if you think that my wording
needs being changed in RFC 6048, please tell me and I will naturally
open an erratum.

-- 
Julien ÉLIE

« La science consiste à passer d'un étonnement à l'autre. »
  (Aristote)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue Feb 15 11:44:52 2011
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E72B23A6D10 for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QtZCR+GCHUwZ for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:44:52 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id E17D43A6C99 for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:44:51 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id 2FE2467E14 for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:45:18 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 6B7DB67E0D for <ietf-nntp@lists.eyrie.org>; Tue, 15 Feb 2011 11:45:16 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 174CD814B; Tue, 15 Feb 2011 20:44:46 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XfMN84-hgctq; Tue, 15 Feb 2011 20:44:46 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-153-1-47-217.w83-200.abo.wanadoo.fr [83.200.15.217]) by denver.dinauz.org (Postfix) with ESMTPSA id AE5C98072; Tue, 15 Feb 2011 20:44:45 +0100 (CET)
Message-ID: <4D5AD7AD.20305@trigofacile.com>
Date: Tue, 15 Feb 2011 20:44:45 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ah@tr-sys.de
Subject: [NNTP] Terminology valid/invalid in RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: NNTP protocol discussion <ietf-nntp.lists.eyrie.org>
List-Unsubscribe: <http://lists.eyrie.org/mailman/options/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=unsubscribe>
List-Archive: <http://lists.eyrie.org/pipermail/ietf-nntp>
List-Post: <mailto:ietf-nntp@lists.eyrie.org>
List-Help: <mailto:ietf-nntp-request@lists.eyrie.org?subject=help>
List-Subscribe: <http://lists.eyrie.org/mailman/listinfo/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=subscribe>
Sender: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

Following a discussion with Alfred Hönes, who reported:

> terminological overloading,
>     leading to ambiguity and under-specification
>
> Within the RFC text, the terms "valid", and in particular, "invalid",
> are used with three very distinct semantics.
> These terms could mean:
>
> a)
> conformance/non-conformance with the prescribed syntax (ABNF) for
> a message (command/reply), or one of its components, e.g., talking
> about a "valid response code" (Section 5.1.1 et al.)

I believe this one is pretty clear and without any ambiguity.

Let's deal with the other uses below.




> b)
> the special value "invalid" introduced in Section 6.1, on page 36,
> for the two NNTP session state variables specified:
>
>   The following commands are used to set the "currently selected
>   newsgroup" and the "current article number", which are used by
>   various commands.  At the start of an NNTP session, both of these
>   values are set to the special value "invalid".
>                                       ^^^^^^^^^

I think it is OK.




> c)
> the semantical validity of a newsgroup name or an article number
> (i.e., the 'existence' of a named group or article on the server);
> e.g. (second paragraph of Section 6.1.1.2, on page 36):
>
>   The required argument is the name of the newsgroup to be selected
>   (e.g., "news.software.nntp").  A list of valid newsgroups may be
>                                            ^^^^^
>   obtained by using the LIST ACTIVE command (see Section 7.6.3).
[...]
> The resulting ambiguity can perhaps most strikingly be seen from the
> second paragraph on page 38 (within the GROUP command Description,
> Section 6.1.1.2):
>
>           vvvvv
> |  When a valid group is selected by means of this command, the
>   currently selected newsgroup MUST be set to that group, and the
>   current article number MUST be set to the first article in the group
>   (this applies even if the group is already the currently selected
>   newsgroup).  If an empty newsgroup is selected, the current article
> |  number is made invalid.  If an invalid group is specified, the
>           !!!!!!!!!!!!!!!         ^^^^^^^
>   currently selected newsgroup and current article number MUST NOT be
>   changed.

Maybe it should be explained.  I do not know what is the best
thing to do here.  It is true that "valid" here means it is selectable
by a GROUP/LISTGROUP command and will lead to a valid currently
selected newsgroup.

(A suggestion was to use "undefined" instead of "invalid". Or to use
typographical enhancement to spell it:  `invalid' with surrounding
single back-quotes.)



> This also includes the situation where (at least) one of the above
> two state variables becomes 'lame' -- that is perhaps described best,
> for the latter variable, by the text on mid-page 47,
>               vvvvvvvvvvvvvvvv                           vvvvvvv
>  "Note that a previously valid article number MAY become invalid if the
>   article has been removed.  A previously invalid article number MAY
>   vvvvvvvvvvvv               ^^^^^^^^^^^^^^^^^^^^
>   become valid if the article has been reinstated, but this article
>   number MUST be no less than the reported low water mark for that
>   group."

You're right.  That is a very unfortunate use of "valid"/"invalid".
Taken into account in erratum 2037:

    http://www.rfc-editor.org/errata_search.php?eid=2037

New wording used:

   Note that a previously valid article number MAY cease to refer to any
   article if that article has been removed, in which case use of that
   article number (explicitly or implicitly) will cause a 423 response.  A
   previously removed article may be reinstated (but its number MUST be no
   less than the reported low water mark for that group), in which case
   that number will once again refer to that article.




To the working group:  do you think something should be changed
regarding the problem c) mentioned in this mail?

-- 
Julien ÉLIE

« La science consiste à passer d'un étonnement à l'autre. »
  (Aristote)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue Feb 15 11:45:43 2011
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C92D3A6C32 for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:45:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdbRiZ1DZjHy for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:45:42 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id 68DAF3A6A9E for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:45:42 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id B04CE67E1C for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:46:08 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 66CDB67E14 for <ietf-nntp@lists.eyrie.org>; Tue, 15 Feb 2011 11:46:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 146328147; Tue, 15 Feb 2011 20:45:36 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wikvfSGd5sKi; Tue, 15 Feb 2011 20:45:36 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-153-1-47-217.w83-200.abo.wanadoo.fr [83.200.15.217]) by denver.dinauz.org (Postfix) with ESMTPSA id BF4718072; Tue, 15 Feb 2011 20:45:35 +0100 (CET)
Message-ID: <4D5AD7DF.10506@trigofacile.com>
Date: Tue, 15 Feb 2011 20:45:35 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ah@tr-sys.de
Subject: [NNTP] Clarification of intra-document references in RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: NNTP protocol discussion <ietf-nntp.lists.eyrie.org>
List-Unsubscribe: <http://lists.eyrie.org/mailman/options/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=unsubscribe>
List-Archive: <http://lists.eyrie.org/pipermail/ietf-nntp>
List-Post: <mailto:ietf-nntp@lists.eyrie.org>
List-Help: <mailto:ietf-nntp-request@lists.eyrie.org?subject=help>
List-Subscribe: <http://lists.eyrie.org/mailman/listinfo/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=subscribe>
Sender: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

Following a discussion with Alfred Hönes, who reported:

 > clarification of intra-document ref.
 >
 > Within Section 2 of RFC 3977, the first paragraph on page 6 says:
 >
 >                       [...].  In some cases, however, they do assume that
 >     the currently selected newsgroup (see the GROUP command,
 >     Section 6.1.1) is invalid; when so, this is indicated at the start of
 >     the example.  [...]
 >
 > The "currently selected newsgroup" is introduced in Section 6.1 (see
 > next quotation below); as such, the clause therein,
 >
 >        (see the GROUP command, Section 6.1.1)
 >
 > should more appropriately have been replaced by:
 >
 >        (see Section 6.1)
 > or:
 >        (see Section 6.1 ff.)

I do not know well what to do with that.
Here is my answer to Alfred:

I do not think the text should be changed this way.
In Section 6.1.1, we have:

    The GROUP command selects a newsgroup as the currently selected
    newsgroup and returns summary information about it.
[...]
    When a valid group is selected by means of this command, the
    currently selected newsgroup MUST be set to that group


I see, like you, that the notion is introduced in Section 6.1,
but the meaning is not explained.  It is explained in Section 6.1.1.
Besides, Section 6.1 is too vague for a quick reference because
commands like NEXT or LAST are also described...

What I suggest, however, would be to mention GROUP *and* LISTGROUP
(Section 6.1.2) because the two commands can be used to select
a newsgroup.
Well, you're also right to say that we should point at Section 6.1
because of the introduction.  Maybe it should be mentioned
explicitly that the introduction of Section 6.1 and both Section
6.1.1 and 6.1.2 should be looked at (?)




To the working group:  Do you have a better wording?
Or do you think nothing should be changed?

-- 
Julien ÉLIE

« La science consiste à passer d'un étonnement à l'autre. »
   (Aristote)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue Feb 15 11:47:56 2011
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 767063A6C32 for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyqtYi3CmuKZ for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:47:55 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id B81293A6A9E for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:47:55 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id 0CBBE67E53 for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:48:22 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 1DBD567E4A for <ietf-nntp@lists.eyrie.org>; Tue, 15 Feb 2011 11:48:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id BC6858072; Tue, 15 Feb 2011 20:47:49 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnVZIq-ED3W1; Tue, 15 Feb 2011 20:47:49 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-153-1-47-217.w83-200.abo.wanadoo.fr [83.200.15.217]) by denver.dinauz.org (Postfix) with ESMTPSA id 80FD48071; Tue, 15 Feb 2011 20:47:49 +0100 (CET)
Message-ID: <4D5AD865.3010403@trigofacile.com>
Date: Tue, 15 Feb 2011 20:47:49 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org, ah@tr-sys.de
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: [NNTP] Consistency in replies to 420 in RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: NNTP protocol discussion <ietf-nntp.lists.eyrie.org>
List-Unsubscribe: <http://lists.eyrie.org/mailman/options/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=unsubscribe>
List-Archive: <http://lists.eyrie.org/pipermail/ietf-nntp>
List-Post: <mailto:ietf-nntp@lists.eyrie.org>
List-Help: <mailto:ietf-nntp-request@lists.eyrie.org?subject=help>
List-Subscribe: <http://lists.eyrie.org/mailman/listinfo/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=subscribe>
Sender: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

Following a discussion with Alfred Hönes, who reported:

> Appendix C, on page 119, says:
> 
>     Response code 412
>        Generated by: ARTICLE, BODY, GROUP, HDR, HEAD, LAST, LISTGROUP,
>        NEXT, OVER, STAT
>        Meaning: no newsgroup selected.
> 
>     Response code 420
>        Generated by: ARTICLE, BODY, HDR, HEAD, LAST, NEXT, OVER, STAT
>        Meaning: current article number is invalid.
> 
> Please be aware of the different wording used:
>        "no newsgroup selected" vs. "current article number is invalid"
> 
> These two phrases, respectively, are used in a totally consistent way,
> throughout the RFC, in the specification of possible command responses
> when it comes to referring to these two response codes.
>
> The text, "no newsgroup selected", also appears in all examples
> where response code 412 is returned by the server.
> 
> Interestingly enough, all examples in the RFC where the response
> code 420 is returned by the server consistently do *not* use the
> above quoted phrase from Appendix C, but instead say:
> 
>        [S] 420 No current article selected

Well seen :-)
Yet, the comment after the response code is only informative.
A news server can put anything it wants.  Even nothing.
I bet the wording "no current article selected" is more user-friendly
than "current article number is invalid".
The meaning in Appendix C can be worded differently.  I do not
see a problem here.
No need for an erratum.  The question could of course be risen
if RFC 3977 is moved to Draft Standard.


To the working group:  Where nits like these one should be kept
for future reference?  (Errata?)

-- 
Julien ÉLIE

« La science consiste à passer d'un étonnement à l'autre. »
  (Aristote)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue Feb 15 11:56:11 2011
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B1233A6D6E for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rzwS1b4LN07 for <ietfarch-nntpext-archive@core3.amsl.com>; Tue, 15 Feb 2011 11:56:10 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id 3BE0B3A6A9E for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:56:10 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id 8785567E1C for <nntpext-archive@ietf.org>; Tue, 15 Feb 2011 11:56:36 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 25C7667E14 for <ietf-nntp@lists.eyrie.org>; Tue, 15 Feb 2011 11:56:35 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id C695D8147; Tue, 15 Feb 2011 20:56:04 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wzo9wPfr6Mc; Tue, 15 Feb 2011 20:56:04 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-153-1-47-217.w83-200.abo.wanadoo.fr [83.200.15.217]) by denver.dinauz.org (Postfix) with ESMTPSA id 6A91E8072; Tue, 15 Feb 2011 20:56:04 +0100 (CET)
Message-ID: <4D5ADA54.1090705@trigofacile.com>
Date: Tue, 15 Feb 2011 20:56:04 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ah@tr-sys.de
Subject: [NNTP] Suggestion of examples for 412 semantics in RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: NNTP protocol discussion <ietf-nntp.lists.eyrie.org>
List-Unsubscribe: <http://lists.eyrie.org/mailman/options/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=unsubscribe>
List-Archive: <http://lists.eyrie.org/pipermail/ietf-nntp>
List-Post: <mailto:ietf-nntp@lists.eyrie.org>
List-Help: <mailto:ietf-nntp-request@lists.eyrie.org?subject=help>
List-Subscribe: <http://lists.eyrie.org/mailman/listinfo/ietf-nntp>, <mailto:ietf-nntp-request@lists.eyrie.org?subject=subscribe>
Sender: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

Just a few examples that could be added to RFC 3977.

Following a discussion with Alfred Hönes, who reported:

> (iv)  particulars of the 412 semantics
> 
> The LISTGROUP Usage (Section 6.1.2.1, on page 39) contains the note:
> 
>     [1] The 412 response can only occur if no group has been specified.
> 
> The LISTGROUP Description (Section 6.1.2.2, on mid-page 40) says:
> 
>     The LISTGROUP command selects a newsgroup in the same manner as the
>     GROUP command (see Section 6.1.1) but also provides a list of article
>     numbers in the newsgroup.  If no group is specified, the currently
>     selected newsgroup is used.
> 
> |  If the group specified is not available on the server, a 411 response
> |  MUST be returned.  If no group is specified and the currently
> |  selected newsgroup is invalid, a 412 response MUST be returned.
> 
> The second paragraph quoted could be interpreted to say, using the
> notation proposed above:
> 
>     If the group specified is not available on the server, a 411 response
> |  MUST be returned.  If no group is specified and the currently
> |  selected newsgroup is `invalid`, a 412 response MUST be returned.
> 
> And in this interpretation, it would have to be presumed that when
> (no group is specified and) the "currently selected newsgroup" has
> became lame (unavailable on the server), a 411 response should be
> returned as well.
> (Unfortunately, this case is not covered by any example in the RFC.)

Interesting scenario.
Here is what INN 2.5 answers:

[No trigofacile.abc group]

LISTGROUP trigofacile.abc
411 No such group trigofacile.abc

[I create the group]

LISTGROUP trigofacile.abc
211 0 1 0 trigofacile.abc
.

[I remove the group]

LISTGROUP
411 No such group trigofacile.abc
LISTGROUP trigofacile.abc
411 No such group trigofacile.abc
OVER
420 Current article number 0 is invalid
XOVER
420 Current article number 0 is invalid
OVER 1
423 No articles in 1
XOVER 1
224 No articles in 1
.

[I recreate the group]

LISTGROUP
211 0 1 0 trigofacile.abc
.



As far as I can see, when the group is selected, we are inside
it, with article number set to the first article (here, it is
empty, so the article number is 0 -- but it could have been 7
or any other number).

I think the behaviour is consistent.
Not available => 411
412 would be for an invalid currently selected newsgroup.  Yet,
the currently selected newsgroup is valid (the notion does not
deal with existing/not existing at one moment -- the currently
selected newsgroup does not become invalid if the newsgroup
disappears from the LIST ACTIVE result).

No interpretation here.  No quote around "invalid".





> Otherwise, that second paragraph could be interpreted as meaning
> (formulated verbously):
> 
>     If the group specified is not available on the server, a 411 response
> |  MUST be returned.  If no group is specified and the currently
> |  selected newsgroup is `invalid` (has never been set) or it has become
> |  unavalable on the server, a 412 response MUST be returned.
> 
> I conclude that the former interpretation must have been intended
> since the latter interpretation does not match the specified 412
>     Meaning: no newsgroup selected.

Yes.  That is not a valid interpretation.  There is no interpretation
to give to the word "invalid".  It means only one thing when it is
used for the currently selected newsgroup/article.





> The LAST Description (Section 6.1.3.2, page 42), and hence implicitely,
> by reference, the NEXT Description (Section 6.1.4.2,page 44) contains
> the sentence,
>                                                  [...].  If the currently
>     selected newsgroup is invalid, a 412 response MUST be returned.  [...]
> 
> According to (iii) above, this apparently should be interpreted to mean:
> 
>                                                         If the "currently
>     selected newsgroup" is `invalid`, a 412 response MUST be returned.
> 
> Again, it remains unclear what should be done when the "currently
> selected newsgroup" has become lame.
> All other response codes specified in the Usage clauses for LAST
> and NEXT are not appropriate for this case.  The solution proposed
> for LISTGROUP hence is not applicable; a gap in the specification
> remains.

Yes!
It is erratum 2003 (which I mentioned at the beginning of this mail).
It is one of the annoying gaps in RFC 3977:

    http://www.rfc-editor.org/errata_search.php?eid=2003

Paragraph reworded as follows:

   If the currently selected newsgroup is invalid, a 412 response MUST
   be returned.  If the currently selected newsgroup is valid but the
   current article number is invalid, a 420 response MUST be returned.
   If the current article number is valid and there is no previous article
   in the currently selected newsgroup, a 422 response MUST be returned.
   In all three cases, the currently selected newsgroup and current article
   number MUST NOT be altered.


I believe the issue you mention is fixed.
The correct answer in your case is 420 if the newsgroup was empty,
and 422 if it was not.

Just to be sure, I have just checked in INN 2.5:

[Group with one article]

GROUP trigofacile.abc
211 1 1 1 trigofacile.abc
OVER
224 Overview information for 1 follows
1       test    [...]
.

[I remove the group]

LAST
422 No previous article to retrieve
NEXT
421 No next article to retrieve
OVER
423 No such article number 1



I think this behaviour is fine and RFC-with-errata-compliant.
Feel free to tell me if you reckon it is not the case.

-- 
Julien ÉLIE

« La science consiste à passer d'un étonnement à l'autre. »
  (Aristote)

From johnbrun00@aol.co.uk  Fri Feb 25 14:21:26 2011
Return-Path: <johnbrun00@aol.co.uk>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E18C3A6A5B for <ietfarch-nntpext-archive@core3.amsl.com>; Fri, 25 Feb 2011 14:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.99
X-Spam-Level: ****
X-Spam-Status: No, score=4.99 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_60=1, FORGED_MUA_OUTLOOK=3.116, MSOE_MID_WRONG_CASE=0.82, SARE_RMML_Stock19=0.22]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rz3+uYk5IX4D for <ietfarch-nntpext-archive@core3.amsl.com>; Fri, 25 Feb 2011 14:21:26 -0800 (PST)
Received: from md8.zone.eu (md8.zone.eu [217.146.66.118]) by core3.amsl.com (Postfix) with ESMTP id 1735E3A6A53 for <nntpext-archive@ietf.org>; Fri, 25 Feb 2011 14:21:23 -0800 (PST)
Received: from User (adsl-66-137-191-34.dsl.spfdmo.swbell.net [66.137.191.34]) (Authenticated sender: info@sportlab.ee) by md8.zone.eu (Postfix) with ESMTP id E730418DB3D7; Fri, 25 Feb 2011 23:56:22 +0200 (EET)
Reply-To: <johnbrunnt@aol.co.uk>
From: "John Brunt"<johnbrun00@aol.co.uk>
Subject: From John Brunt
Date: Fri, 25 Feb 2011 15:57:01 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-Id: <20110225215622.E730418DB3D7@md8.zone.eu>
To: undisclosed-recipients:;

Hello Friend
 
Do accept my sincere apologies if my mail does not meet your personal ethics.I knew that this mail will come to you as a surprise, but please do not be discouraged with my proposal; it was due to how things are moving with me.

However, this correspondence is unofficial and private, and it should be treated as such. At first I will like to assure you that this transaction is 100% risk and trouble free to both parties

My name is Mr. John Brunt, a Fund Manager with Fidelity Investment, UK. I handle all our Investors Capital Project Funds which enabled me to divert 1.2% of Investors Excess Return Capital Funds to our Magellan Trust Funds Account where anyone can be presented to claim the funds.

Total sum of Fifteen Million, Seven Hundred and Forty Five Thousand British Pounds (15.745.000)BP has been diverted, representing 1.2% of Excess Return Capital Funds from the Investor Capital Project Funds for 2006/2007 fiscal year.

I need a reliable and trustworthy person with whom I can work this deal out so that we can claim the funds as mentioned above.

There is no risk attached and the funds in question can never be dictated or traced.

Sincerely,

John
