
From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Sun May 13 12:17:33 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD2B21F846B for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 12:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GT6Hfv6k4tJB for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 12:17:33 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id E0CB221F846A for <nntpext-archive@ietf.org>; Sun, 13 May 2012 12:17:29 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id A7EFA67E4E for <nntpext-archive@ietf.org>; Sun, 13 May 2012 12:17:28 -0700 (PDT)
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 4D27C67D2E for <ietf-nntp@lists.eyrie.org>; Sun, 13 May 2012 12:17:26 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 4E4A98177; Sun, 13 May 2012 21:17:25 +0200 (CEST)
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 0nivSl9MxP5k; Sun, 13 May 2012 21:17:25 +0200 (CEST)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-100-201.w83-114.abo.wanadoo.fr [83.114.195.201]) by denver.dinauz.org (Postfix) with ESMTPSA id DBCB4805C; Sun, 13 May 2012 21:17:24 +0200 (CEST)
Message-ID: <4FB008C4.3000009@trigofacile.com>
Date: Sun, 13 May 2012 21:17:24 +0200
From: =?UTF-8?B?SnVsaWVuIMOJTElF?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: barryleiba@computer.org
References: <20120512183346.A53E262180@rfc-editor.org>
In-Reply-To: <20120512183346.A53E262180@rfc-editor.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Russ ALLBERY <rra@stanford.edu>, ietf-nntp@lists.eyrie.org, clive@davros.org, iesg@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Dear Barry Leiba,

I have just been aware that erratum 2004 was rejected.
Yet, I do not understand why.

> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3977&eid=2004
> --------------------------------------
> Status: Rejected
> Type: Technical
>
> Reported by: Julien Ã‰lie
> Date Reported: 2010-01-14
> Rejected by: Barry Leiba (IESG)



The given reason is:

> --VERIFIER NOTES-- Section 6.2.1.2 paragraph 6 says "a previously
> valid article number MAY become invalid if the article has been
> removed". Therefore the correct response in the situation being
> addressed would be 420, not 423.
>
> This could be a case that might be considered if the document is
> updated, but certainly it's not a simple error in the document.

We are not speaking about the situation you mention.  There is a 
difference between valid/invalid article numbers and valid/invalid 
*current* article numbers.
Section 6.2.1.2 speaks about valid/invalid article numbers, and in this 
situation, we are in the *second* form (article number specified) of the 
ARTICLE command.  The possible answers are:

    Second form (article number specified)
      220 n message-id      Article follows (multi-line)
      412                   No newsgroup selected
      423                   No article with that number

The 423 response code is therefore sent here, for the second form.

In Section 6.2.1.3:

    Example of an unsuccessful retrieval of an article by number:

       [C] GROUP misc.test
       [S] 211 1234 3000234 3002322 news.groups
       [C] ARTICLE 300256
       [S] 423 No article with that number




The erratum I filled is related to the *third* form (current article 
number used), that is to say when no article number is specified.  The 
possible answers mentioned in RFC 3977 are:

    Third form (current article number used)
      220 n message-id      Article follows (multi-line)
      412                   No newsgroup selected
      420                   Current article number is invalid

However, the 423 response code is also a valid response code in the 
third form.
Returning 420 in the case of a removed article is wrong because it would 
imply that the current article number is invalid whereas it *is* valid 
(and properly set to the article number of a removed article).

The validity of the *current* article number does not depend on the fact 
that the article number is valid or invalid.  These are two different 
things.

That's why the 423 response code MUST be sent in such a situation, using 
the *third* form of the command.


Please have a look at the discussion we had in January 2010 in the IETF 
NNTP working group.

   http://lists.eyrie.org/pipermail/ietf-nntp/2010-January/006145.html

Clive D.W. Feather (the author of RFC 3977) explains in the above 
message the reason why 423 is a valid answer for the third form and that 
it is "a corner case that we don't seem to have thought of" when writing 
RFC 3977.
This code was allowed in RFC 977 (obsoleted by 3977), per Section 3.1.3 
of RFC 977.  When the response codes were reworded to distinguish three 
forms in RFC 3977, this corner case of 423 for the third form was 
technically forgotten and not mentioned whereas it is the response code 
that has *always* been implemented in NNTP servers for this situation, 
in the third form.  No change was meant to be done in the NNTP protocol 
by RFC 3977 about this behaviour.  It would otherwise have been 
mentioned in Appendix D of RFC 3977!  That's why it is a genuine erratum 
that must be considered in RFC 3977.

I am at your disposal if you need more information or have any question.

-- 
Julien Ã‰LIE

Â« It's documented in The Book, somewhereâ€¦ Â» (Larry Wall)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Sun May 13 17:01:05 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2F421F8470 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 17:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9AGcV-QzkoP for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 17:01:04 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEAA21F846C for <nntpext-archive@ietf.org>; Sun, 13 May 2012 17:01:04 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id A4B8567D2E for <nntpext-archive@ietf.org>; Sun, 13 May 2012 17:01:03 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by hope.eyrie.org (Postfix) with ESMTP id 2494667D00 for <ietf-nntp@lists.eyrie.org>; Sun, 13 May 2012 15:16:41 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so8958581obb.18 for <ietf-nntp@lists.eyrie.org>; Sun, 13 May 2012 15:16:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OF2ePJQT+ueDvRz17PbjDcZW6yefYUJGWejoTkf/W5w=; b=ZMH/PuFlDiOo/WmqoQE/Vf6lol8xHKfeR+sL5hES2JaEncxZDX/XvplH0LaC+cdOsq kQw8vEVyPQSO1LUx0pSVpy79wOth4+1y8IYCgj4ZSvXfIEj264hZUo9J68Ta3efY+Xjh Qk1KdyRB/t0PtCblvQ4nlttXauP7wrcVGerQJAzHjZ9NEnpqREFsjjKdUXjWsnDvltxj kNPTmzQ6Cvd3KUuEVZo6AZrLgfFRVlpPAeyRnwZaWwHrw4uUeKw1z9i8S7CsW9RZu9XG B3zhwGZtae9dZzJP1EgGpRXokyRJW3E6/1iJ0/Ly2YqnFMM5eV0/z2BUk9Lo05DKClQn UdfA==
MIME-Version: 1.0
Received: by 10.60.9.163 with SMTP id a3mr8707883oeb.71.1336947400596; Sun, 13 May 2012 15:16:40 -0700 (PDT)
Received: by 10.60.10.68 with HTTP; Sun, 13 May 2012 15:16:40 -0700 (PDT)
In-Reply-To: <4FB008C4.3000009@trigofacile.com>
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com>
Date: Sun, 13 May 2012 18:16:40 -0400
X-Google-Sender-Auth: z4dsLBcNyastdNo6nbnhDn6LQto
Message-ID: <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sun, 13 May 2012 17:01:01 -0700
Cc: Russ ALLBERY <rra@stanford.edu>, RFC Errata System <rfc-editor@rfc-editor.org>, clive@davros.org, iesg@ietf.org, ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

> I have just been aware that erratum 2004 was rejected.
> Yet, I do not understand why.

Well, the response in the rejection reason is taken directly from an
exchange I had with Clive.  Now, he did also suggest that I might pass
it by Russ Allbery, which I have not yet done.  Since he's copied on
this exchange, he can comment.  Clive's point wasn't meant to say that
your suggestion in the errata report wasn't good, but that it's not
bringing up an *error* in the original spec.  If what you suggest is
an appropriate change, it might be considered if there's work done to
revise the document.

I'd be happy, if Clive, Russ, and Julien all think it's the right
approach, to change the erratum to "hold for document update".  Russ
Allbery, do you have a comment on this?

Barry Leiba, Applications Area Director

>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3D3977&eid=3D2004
>> --------------------------------------
>> Status: Rejected
>> Type: Technical
>>
>> Reported by: Julien =C9lie
>> Date Reported: 2010-01-14
>> Rejected by: Barry Leiba (IESG)
>
>
> The given reason is:
>
>> --VERIFIER NOTES-- Section 6.2.1.2 paragraph 6 says "a previously
>> valid article number MAY become invalid if the article has been
>> removed". Therefore the correct response in the situation being
>> addressed would be 420, not 423.
>>
>> This could be a case that might be considered if the document is
>> updated, but certainly it's not a simple error in the document.
>
>
> We are not speaking about the situation you mention. =A0There is a differ=
ence
> between valid/invalid article numbers and valid/invalid *current* article
> numbers.
> Section 6.2.1.2 speaks about valid/invalid article numbers, and in this
> situation, we are in the *second* form (article number specified) of the
> ARTICLE command. =A0The possible answers are:
>
> =A0 Second form (article number specified)
> =A0 =A0 220 n message-id =A0 =A0 =A0Article follows (multi-line)
> =A0 =A0 412 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 No newsgroup selected
> =A0 =A0 423 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 No article with that numb=
er
>
> The 423 response code is therefore sent here, for the second form.
>
> In Section 6.2.1.3:
>
> =A0 Example of an unsuccessful retrieval of an article by number:
>
> =A0 =A0 =A0[C] GROUP misc.test
> =A0 =A0 =A0[S] 211 1234 3000234 3002322 news.groups
> =A0 =A0 =A0[C] ARTICLE 300256
> =A0 =A0 =A0[S] 423 No article with that number
>
>
>
>
> The erratum I filled is related to the *third* form (current article numb=
er
> used), that is to say when no article number is specified. =A0The possibl=
e
> answers mentioned in RFC 3977 are:
>
> =A0 Third form (current article number used)
> =A0 =A0 220 n message-id =A0 =A0 =A0Article follows (multi-line)
> =A0 =A0 412 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 No newsgroup selected
> =A0 =A0 420 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Current article number is=
 invalid
>
> However, the 423 response code is also a valid response code in the third
> form.
> Returning 420 in the case of a removed article is wrong because it would
> imply that the current article number is invalid whereas it *is* valid (a=
nd
> properly set to the article number of a removed article).
>
> The validity of the *current* article number does not depend on the fact
> that the article number is valid or invalid. =A0These are two different
> things.
>
> That's why the 423 response code MUST be sent in such a situation, using =
the
> *third* form of the command.
>
>
> Please have a look at the discussion we had in January 2010 in the IETF N=
NTP
> working group.
>
> =A0http://lists.eyrie.org/pipermail/ietf-nntp/2010-January/006145.html
>
> Clive D.W. Feather (the author of RFC 3977) explains in the above message
> the reason why 423 is a valid answer for the third form and that it is "a
> corner case that we don't seem to have thought of" when writing RFC 3977.
> This code was allowed in RFC 977 (obsoleted by 3977), per Section 3.1.3 o=
f
> RFC 977. =A0When the response codes were reworded to distinguish three fo=
rms
> in RFC 3977, this corner case of 423 for the third form was technically
> forgotten and not mentioned whereas it is the response code that has
> *always* been implemented in NNTP servers for this situation, in the thir=
d
> form. =A0No change was meant to be done in the NNTP protocol by RFC 3977 =
about
> this behaviour. =A0It would otherwise have been mentioned in Appendix D o=
f RFC
> 3977! =A0That's why it is a genuine erratum that must be considered in RF=
C
> 3977.
>
> I am at your disposal if you need more information or have any question.
>
> --
> Julien =C9LIE

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Sun May 13 17:09:14 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF1221F84AA for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 17:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLYUjMPGto+x for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun, 13 May 2012 17:09:14 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id EDD9E21F84A1 for <nntpext-archive@ietf.org>; Sun, 13 May 2012 17:09:13 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 9BB7C67E4E for <nntpext-archive@ietf.org>; Sun, 13 May 2012 17:09:13 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from smtp.stanford.edu (smtp3.Stanford.EDU [171.67.219.83]) by hope.eyrie.org (Postfix) with ESMTP id A50CC67D2E for <ietf-nntp@lists.eyrie.org>; Sun, 13 May 2012 17:09:11 -0700 (PDT)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 50A5C455870; Sun, 13 May 2012 17:09:11 -0700 (PDT)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id 70E2445583D; Sun, 13 May 2012 17:09:09 -0700 (PDT)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id 3B1112F46A; Sun, 13 May 2012 17:09:09 -0700 (PDT)
From: Russ Allbery <rra@stanford.edu>
To: Barry Leiba <barryleiba@computer.org>
In-Reply-To: <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com> (Barry Leiba's message of "Sun, 13 May 2012 18:16:40 -0400")
Organization: The Eyrie
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com> <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Sun, 13 May 2012 17:09:08 -0700
Message-ID: <877gwfk4ij.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Julien =?utf-8?Q?=C3=89LIE?= <julien@trigofacile.com>, clive@davros.org, iesg@ietf.org, ietf-nntp@lists.eyrie.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Barry Leiba <barryleiba@computer.org> writes:

> Well, the response in the rejection reason is taken directly from an
> exchange I had with Clive.  Now, he did also suggest that I might pass
> it by Russ Allbery, which I have not yet done.  Since he's copied on
> this exchange, he can comment.  Clive's point wasn't meant to say that
> your suggestion in the errata report wasn't good, but that it's not
> bringing up an *error* in the original spec.  If what you suggest is an
> appropriate change, it might be considered if there's work done to
> revise the document.

I reluctantly agree.  I believe this is quite obviously an error in RFC
3977, but RFC 3977 is also quite explicit that 423 is not a permissible
response code for ARTICLE without an argument.  My understanding is that
errata can't be used to correct the clear statement of the specification,
even if that clear statement is wrong based on existing deployed code and
consistency of semantics through the specification.

> I'd be happy, if Clive, Russ, and Julien all think it's the right
> approach, to change the erratum to "hold for document update".  Russ
> Allbery, do you have a comment on this?

Yes, please.  We would clearly want to fix this in any revision of RFC
3977.  Personally, I would recommend that any implementor use 423 as
described in Julien's analysis despite the wording of RFC 3977.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Mon May 14 04:12:13 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C784D21F86C6 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 04:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level: 
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kANLf-F156iD for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 04:12:07 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 68B1521F86C5 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 04:12:07 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 891A167E4E for <nntpext-archive@ietf.org>; Mon, 14 May 2012 04:12:06 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from outbound-queue-2.mail.thdo.gradwell.net (outbound-queue-2.mail.thdo.gradwell.net [212.11.70.35]) by hope.eyrie.org (Postfix) with ESMTP id 35C7E67D09 for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 04:12:05 -0700 (PDT)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-2.mail.thdo.gradwell.net (Postfix) with ESMTP id C4CC822504 for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 12:12:02 +0100 (BST)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 14 May 2012 12:12:02 +0100
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id q4EBC22x006973 for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 12:12:02 +0100 (BST)
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id q4EBC2Oj006969 for ietf-nntp@lists.eyrie.org; Mon, 14 May 2012 12:12:02 +0100 (BST)
To: ietf-nntp@lists.eyrie.org
Xref: clerew local.nntp:5272
Path: clerew!chl
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Message-ID: <M40BsH.1uv@clerew.man.ac.uk>
X-Newsreader: NN version 6.5.2 (NOV)
References: <2
Date: Mon, 14 May 2012 10:00:17 GMT
Lines: 23
X-Gradwell-MongoId: 4fb0e882.122cd-7029-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [NNTP] Babble from Russ Allbery <rra@stanford.edu>
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Russ Allbery <rra@stanford.edu> writes:

>Yes, please.  We would clearly want to fix this in any revision of RFC
>3977.  Personally, I would recommend that any implementor use 423 as
>described in Julien's analysis despite the wording of RFC 3977.

Yes, but a revision is unlikely in the foreseeeable future. Is there any
mechanism whereby a NOTE can be added as an erratum pointing out that
"With hindsight it might have been better to ..., and this should be
revisited in any revision of this document"? As least that would alert
people to the issue and hint that they might want to reconsider how to
cope with it in their implementation.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131            Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Mon May 14 04:26:05 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD21921F86EB for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 04:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxL61Mtnh6o3 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 04:26:05 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id EF24421F86A5 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 04:26:04 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 9DC3467E4E for <nntpext-archive@ietf.org>; Mon, 14 May 2012 04:26:04 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by hope.eyrie.org (Postfix) with ESMTP id F26A467D09 for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 04:26:02 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so10133948obb.18 for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 04:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=G7qj+r7IscSOYDysrkBsDA7zP6I1aIK5UobrfgXlZK4=; b=VwTGJ7u0eADALQrpwnVreAhAo8z8jW6ooB+ylomcz671H1v3gANy1uqz5PjXPrkLJM 8RUjWS4Vlm5uZuALnuAr0IZhgKGxyau4OTiLVKCaYn+0AwvL/vj3GqnnDa1OHqEH1caB m2unYnJNg5wxuFj3bw/VBXYsqh+v4WuPuK/ZfjLbTK990OyEuwnjaXM/BfWKMggNykkG 3NUjml+MsqJJ40SaDKquMB+cTWCBIeojcF8pko1ALDlEAhUu++D93zQftgCCmknfH/+x sZGREueYjaimli4zJNKcmDA7XHJJskHPAgpyEI4+pUnuuiy9PLWPKkLNfmMOJGM9Cple D2ow==
MIME-Version: 1.0
Received: by 10.182.167.104 with SMTP id zn8mr10740198obb.62.1336994762601; Mon, 14 May 2012 04:26:02 -0700 (PDT)
Received: by 10.60.10.68 with HTTP; Mon, 14 May 2012 04:26:02 -0700 (PDT)
In-Reply-To: <877gwfk4ij.fsf@windlord.stanford.edu>
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com> <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com> <877gwfk4ij.fsf@windlord.stanford.edu>
Date: Mon, 14 May 2012 07:26:02 -0400
X-Google-Sender-Auth: SDS96SEtJtXUsxbwPH7LJdG1E3U
Message-ID: <CALaySJK6brcCEtjOrcgmjUs1EgXXuh_h913CQonV35-NyyGwOQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Russ Allbery <rra@stanford.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>, clive@davros.org, iesg@ietf.org, ietf-nntp@lists.eyrie.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

>> I'd be happy, if Clive, Russ, and Julien all think it's the right
>> approach, to change the erratum to "hold for document update". =A0Russ
>> Allbery, do you have a comment on this?
>
> Yes, please. =A0We would clearly want to fix this in any revision of RFC
> 3977. =A0Personally, I would recommend that any implementor use 423 as
> described in Julien's analysis despite the wording of RFC 3977.

OK, that works for me.

RFC Editor, will you please switch errata #2004 from "rejected" to
"hold for document update"?  Thanks.

Barry

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Mon May 14 14:28:44 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D169E21F889C for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 14:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLEojqZUxBiF for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 14:28:44 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 888C721F889B for <nntpext-archive@ietf.org>; Mon, 14 May 2012 14:28:44 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id F040A67E62 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 14:28:43 -0700 (PDT)
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 C2B1467E4E for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 14:28:42 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 0562A8177; Mon, 14 May 2012 23:28:41 +0200 (CEST)
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 A-1UnNwOCCkl; Mon, 14 May 2012 23:28:40 +0200 (CEST)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-100-201.w83-114.abo.wanadoo.fr [83.114.195.201]) by denver.dinauz.org (Postfix) with ESMTPSA id 9CF2B805C; Mon, 14 May 2012 23:28:40 +0200 (CEST)
Message-ID: <4FB17907.6080701@trigofacile.com>
Date: Mon, 14 May 2012 23:28:39 +0200
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.7; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: Alice Russo <arusso@amsl.com>, Barry Leiba <barryleiba@computer.org>,  Russ Allbery <rra@stanford.edu>, "Clive D.W. Feather" <clive@davros.org>
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com> <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com> <877gwfk4ij.fsf@windlord.stanford.edu> <CALaySJK6brcCEtjOrcgmjUs1EgXXuh_h913CQonV35-NyyGwOQ@mail.gmail.com> <75DF3FCB-DB7D-4C3B-A4C8-3960947DE6F1@amsl.com>
In-Reply-To: <75DF3FCB-DB7D-4C3B-A4C8-3960947DE6F1@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, The IESG <iesg@ietf.org>, ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Hi all,

[Russ]
>>> Yes, please.  We would clearly want to fix this in any revision of RFC
>>> 3977.  Personally, I would recommend that any implementor use 423 as
>>> described in Julien's analysis despite the wording of RFC 3977.

[Barry]
>> RFC Editor, will you please switch errata #2004 from "rejected" to
>> "hold for document update"?  Thanks.

[Alice]
> The status has been changed as requested:
> http://www.rfc-editor.org/errata_search.php?eid=2004

And also [Clive] of course, thanks to all of you!
The "hold for document update" status is pretty fine.



[Charles]
> a revision [of RFC3977] is unlikely in the foreseeeable future. Is there
> any mechanism whereby a NOTE can be added as an erratum pointing out
> that "With hindsight it might have been better to ..., and this
> should be revisited in any revision of this document"? As least that
> would alert people to the issue and hint that they might want to
> reconsider how to cope with it in their implementation.

I do not believe such a mechanism exists.  Unfortunately.
One has to go to the HTML version of the IETF site:
     http://tools.ietf.org/html/rfc3977
and pay attention to the two red words "Errata Exist".  Then, carefully 
read through all the submitted errata.

-- 
Julien ÉLIE

« Mieux vaut allumer une bougie que maudire les ténèbres. » (Lao
   Zi)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Mon May 14 14:41:46 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6569421F88B8 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 14:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFkwrxRkVOX1 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 14:41:45 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 10A7521F88B4 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 14:41:39 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id B615667E62 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 14:41:38 -0700 (PDT)
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 D983C67E4E for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 14:41:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 805098177; Mon, 14 May 2012 23:41:36 +0200 (CEST)
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 o0LPfcYCdofO; Mon, 14 May 2012 23:41:36 +0200 (CEST)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-100-201.w83-114.abo.wanadoo.fr [83.114.195.201]) by denver.dinauz.org (Postfix) with ESMTPSA id B7238805C; Mon, 14 May 2012 23:41:35 +0200 (CEST)
Message-ID: <4FB17C0F.7030602@trigofacile.com>
Date: Mon, 14 May 2012 23:41:35 +0200
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.7; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/mixed; boundary="------------060901060601060507060507"
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, ietf-nntp@lists.eyrie.org
Subject: [NNTP] Errata 1707 and 1527 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

This is a multi-part message in MIME format.
--------------060901060601060507060507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Barry,

As I see that you are currently pretty active on errata for RFC 3977, I 
believe it could be time to properly close the two remaining subjects 
that weren't updated two years ago.


* Could the following rationale be added to erratum 1707 for RFC 3977 so 
as to explain the reason of the reject?

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

    The high water mark is one less than the low water mark for empty
    newsgroups.  A major reason for doing it this way was to deal with
    clusters of servers.  If they're not perfectly synchronized, then
    a cancel might be visible on one and not another.  So if you connect
    to the second one, it looks as if the article has been reinstated.
    Wording it like this meant we didn't need special treatment of such
    clusters.  The low water mark cannot decrease.  [Clive D.W. Feather]




* Could erratum 1527 for RFC 3977 be updated and its status changed to 
"VERIFIED" so that it could be properly reviewed when the NNTP protocol 
moves from proposed standard to draft standard?

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

The new wording is better than what was originally suggested as
erratum.  **It fixes exactly the same issue.**
You can see that the current erratum about section 3.2.1 deals with
MODE-READER.  It appeared after discussing with Russ and Clive that
it was better to change section 3.4.2 (mine was just a remark
on section 3.2.1 without any corrected text -- now we have a corrected
text, for 3.4.2).  In fact, I did not know where to put my remark when
I first submitted the bug report.  Clive found a place in RFC 3977
to put it directly in the text, which is far better!


The following sections should be changed (with line breaks removed
in the notes section only, because they are otherwise put at wrong
places in the web version):

Section
-------
3.4.2

Original Text
-------------
However, the server MAY cease to advertise the MODE-READER
capability after the client uses any command except CAPABILITIES.

Corrected Text
--------------
If the client uses a command which will be available in reading mode
and the server will continue to advertise the MODE-READER capability
after responding to that command, the response code 401, with
MODE-READER as the first argument, MUST be returned.  However, the
server MAY cease to advertise the MODE-READER capability after the
client uses any command except CAPABILITIES, in which case the
response code 502 MUST be returned for such commands.

Notes
-----
Here are two examples to illustrate Section 5.3.3 with that clarification.

Example of the 401 response code to indicate that MODE READER is needed:

   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] MODE-READER
   [S] .
   [C] POST
   [S] 401 MODE-READER
   [C] MODE READER
   [S] 200 Reader mode, posting permitted
   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] READER
   [S] LIST ACTIVE NEWSGROUPS
   [S] POST
   [S] .

Example of a mode-switching server which does not allow any reader
command to be used, even unsuccessfully, in transit mode:

   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] MODE-READER
   [S] .
   [C] POST
   [S] 502 Transit service only
   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] .
   [C] MODE READER
   [S] 502 Transit service only
   [Server closes connection.]






Many thanks beforehand,

-- 
Julien ÉLIE

« Mieux vaut allumer une bougie que maudire les ténèbres. » (Lao
   Zi)

--------------060901060601060507060507
Content-Type: message/rfc822;
 name="Message joint"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
 filename="Message joint"

X-Mozilla-Keys: 
Return-Path: <ietf-nntp-bounces+julien=trigofacile.com@lists.eyrie.org>
Delivered-To: julien@trigofacile.com
Received: from b0.ovh.net (HELO queue) (213.186.33.50)
	by b0.ovh.net with SMTP; 23 Jan 2010 12:58:56 -0000
Received: from hope.eyrie.org (166.84.7.155)
  by mx0.ovh.net with SMTP; 23 Jan 2010 12:58:56 -0000
Received: from hope.eyrie.org (localhost [127.0.0.1])
	by hope.eyrie.org (Postfix) with ESMTP id A5B4567E60
	for <julien@trigofacile.com>; Sat, 23 Jan 2010 04:58:55 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from 30.mail-out.ovh.net (30.mail-out.ovh.net [213.186.62.213])
	by hope.eyrie.org (Postfix) with SMTP id 9D2AF67D9D
	for <ietf-nntp@lists.eyrie.org>; Sat, 23 Jan 2010 04:58:53 -0800 (PST)
Received: (qmail 1274 invoked by uid 503); 23 Jan 2010 12:59:02 -0000
Received: from b7.ovh.net (HELO mail436.ha.ovh.net) (213.186.33.57)
	by 30.mail-out.ovh.net with SMTP; 23 Jan 2010 12:59:01 -0000
Received: from b0.ovh.net (HELO queueout) (213.186.33.50)
	by b0.ovh.net with SMTP; 23 Jan 2010 12:58:52 -0000
Received: from aaubervilliers-151-1-29-164.w83-112.abo.wanadoo.fr (HELO
	Iulius) (julien%trigofacile.com@83.112.20.164)
	by ns0.ovh.net with SMTP; 23 Jan 2010 12:58:51 -0000
Message-ID: <81F509814C884A988687249A804C8A6A@Iulius>
From: =?Windows-1252?Q?Julien_=C9LIE?= <julien@trigofacile.com>
To: <ietf-nntp@lists.eyrie.org>
Date: Sat, 23 Jan 2010 13:58:51 +0100
Organization: TrigoFACILE -- http://www.trigofacile.com/
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
X-Ovh-Tracer-Id: 17477062780172238215
X-Ovh-Remote: 83.112.20.164
	(aaubervilliers-151-1-29-164.w83-112.abo.wanadoo.fr)
X-Ovh-Local: 213.186.33.20 (ns0.ovh.net)
X-Spam-Check: DONE|U 0.5/N
Subject: [NNTP] Tr: [Errata Held for Document Update] RFC3977 (1707) --
	archive of rationale
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+julien=trigofacile.com@lists.eyrie.org
Errors-To: ietf-nntp-bounces+julien=trigofacile.com@lists.eyrie.org
X-Ovh-Tracer-Id: 17478470155541129214
X-Ovh-Remote: 166.84.7.155 (hope.eyrie.org)
X-Ovh-Local: 213.186.33.32 (mx0.ovh.net)
X-Spam-Check: DONE|U 0.5/N

Hi,

The rationale for which erratum 1707 for RFC 3977 was "Rejected"
<http://www.rfc-editor.org/errata_search.php?eid=1707> is:

    The high water mark is one less than the low water mark for empty
    newsgroups.  A major reason for doing it this way was to deal with
    clusters of servers.  If they're not perfectly synchronized, then
    a cancel might be visible on one and not another.  So if you connect
    to the second one, it looks as if the article has been reinstated.
    Wording it like this meant we didn't need special treatment of such
    clusters.  The low water mark cannot decrease.


I post it here for the archives (because there is currently no public
trace of the rationale Clive judiciously gave).

Note that the erratum was previously marked as held for document update
but that is currently no longer the case, which is right.  This
erratum must not be verified.

Julien


----- Message d'origine ----- 
De : "RFC Errata System"
À : Clive, Chris, Lisa, Ned, Russ
Cc : Julien, RFC Editor
Envoyé : lundi 23 novembre 2009 22:14
Objet : [Errata Held for Document Update] RFC3977 (1707)


>
> The following errata report has been held for document update
> for RFC3977, "Network News Transfer Protocol (NNTP)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3977&eid=1707
>
> --------------------------------------
> Status: Held for Document Update
> Type: Technical
>
> Reported by: Julien Élie
> Date Reported: 2009-03-05
> Held by: Lisa Dusseault (IESG)
>
> Section: 6.1.1.2
>
> Original Text
> -------------
> The successful selection response will return the article numbers of
> the first and last articles in the group at the moment of selection
> (these numbers are referred to as the "reported low water mark" and
> the "reported high water mark") and an estimate of the number of
> articles in the group currently available.
>
> Corrected Text
> --------------
> The successful selection response will return the article numbers of
> the first and last articles in the group at the moment of selection
> (these numbers are referred to as the "reported low water mark" and
> the "reported high water mark" when the group is not empty) and an
> estimate of the number of articles in the group currently available.
>
>
> Notes
> -----
> The notion of "first and last articles" does not exist when a newsgroup is empty. 
> The meaning of the "reported low water mark" and the "reported high water mark" is 
> explained in a special paragraph afterwards.
>
> To be more precise, if at a given time we have only one article in misc.test and 
> the following answer to a GROUP command:
>
>      [C] GROUP misc.test
>      [S] 211 1 12 12 misc.test
>
> After cancelling this article, the same GROUP command SHOULD give:
>
>      [C] GROUP misc.test
>      [S] 211 0 13 12 misc.test
>
> The low water mark is one more than the high water mark (that is to say that the 
> low water mark has increased, and the high water mark has not decreased).  It will 
> permit the following article arrival to be handled by incrementing the high water 
> mark and leaving the low water mark unchanged.
>
> --------------------------------------
> RFC3977 (draft-ietf-nntpext-base-27)
> --------------------------------------
> Title               : Network News Transfer Protocol (NNTP)
> Publication Date    : October 2006
> Author(s)           : C. Feather
> Category            : PROPOSED STANDARD
> Source              : NNTP Extensions
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
> 


--------------060901060601060507060507
Content-Type: message/rfc822;
 name="Message joint"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
 filename="Message joint"

X-Mozilla-Keys: 
Return-Path: <ietf-nntp-bounces+julien=trigofacile.com@lists.eyrie.org>
Delivered-To: julien@trigofacile.com
Received: from b0.ovh.net (HELO queue) (213.186.33.50)
	by b0.ovh.net with SMTP; 23 Jan 2010 12:49:02 -0000
Received: from hope.eyrie.org (166.84.7.155)
  by mx0.ovh.net with SMTP; 23 Jan 2010 12:49:00 -0000
Received: from hope.eyrie.org (localhost [127.0.0.1])
	by hope.eyrie.org (Postfix) with ESMTP id F2C5D67E14
	for <julien@trigofacile.com>; Sat, 23 Jan 2010 04:48:59 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from 30.mail-out.ovh.net (30.mail-out.ovh.net [213.186.62.213])
	by hope.eyrie.org (Postfix) with SMTP id 92B1467E0A
	for <ietf-nntp@lists.eyrie.org>; Sat, 23 Jan 2010 04:48:57 -0800 (PST)
Received: (qmail 24814 invoked by uid 503); 23 Jan 2010 12:49:05 -0000
Received: from b7.ovh.net (HELO mail436.ha.ovh.net) (213.186.33.57)
	by 30.mail-out.ovh.net with SMTP; 23 Jan 2010 12:49:05 -0000
Received: from b0.ovh.net (HELO queueout) (213.186.33.50)
	by b0.ovh.net with SMTP; 23 Jan 2010 12:48:56 -0000
Received: from aaubervilliers-151-1-29-164.w83-112.abo.wanadoo.fr (HELO
	Iulius) (julien%trigofacile.com@83.112.20.164)
	by ns0.ovh.net with SMTP; 23 Jan 2010 12:48:52 -0000
Message-ID: <0FFC6AD152234D1E886C1DD2F4CAABCA@Iulius>
From: =?Windows-1252?Q?Julien_=C9LIE?= <julien@trigofacile.com>
To: <ietf-nntp@lists.eyrie.org>
Date: Sat, 23 Jan 2010 13:48:52 +0100
Organization: TrigoFACILE -- http://www.trigofacile.com/
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
X-Ovh-Tracer-Id: 17308459269698682247
X-Ovh-Remote: 83.112.20.164
	(aaubervilliers-151-1-29-164.w83-112.abo.wanadoo.fr)
X-Ovh-Local: 213.186.33.20 (ns0.ovh.net)
X-Spam-Check: DONE|U 0.5/N
Subject: [NNTP] Tr: [Technical Errata Reported] RFC3977 (1527) -- archive
	for draft standard
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+julien=trigofacile.com@lists.eyrie.org
Errors-To: ietf-nntp-bounces+julien=trigofacile.com@lists.eyrie.org
X-Ovh-Tracer-Id: 17310711067950360574
X-Ovh-Remote: 166.84.7.155 (hope.eyrie.org)
X-Ovh-Local: 213.186.33.32 (mx0.ovh.net)
X-Spam-Check: DONE|U 0.5/N

Hi,

As erratum 1527 for RFC 3977 was put in the "Held for Document Update"
state <http://www.rfc-editor.org/errata_search.php?eid=1527>, here
is the preferred wording that Clive suggested but that we unfortunately
could not put in the final erratum.

I post it here for the archives (because there is currently no public
trace of that new wording), so that it could be properly reviewed
when the NNTP protocol moves from proposed standard to draft standard.


-----------------------------------------------------------------------
RFC 3977 - Erratum 1527
-----------------------------------------------------------------------

It should be VERIFIED.

The new wording is better than what was originally suggested as
erratum.  It fixes exactly the same issue.
You can see that the current erratum about section 3.2.1 deals with
MODE-READER.  It appeared after discussing with Russ and Clive that
it was better to change section 3.4.2 (mine was just a remark
on section 3.2.1 without any corrected text -- now we have a corrected
text, for 3.4.2).  In fact, I did not know where to put my remark when
I first submitted the bug report.  Clive found a place in RFC 3977
to put it directly in the text, which is far better!

The following sections should be changed (with line breaks removed
in the notes section only, because they are otherwise put at wrong
places in the web version):

Section
-------
3.4.2

Original Text
-------------
However, the server MAY cease to advertise the MODE-READER
capability after the client uses any command except CAPABILITIES.

Corrected Text
--------------
If the client uses a command which will be available in reading mode
and the server will continue to advertise the MODE-READER capability
after responding to that command, the response code 401, with
MODE-READER as the first argument, MUST be returned.  However, the
server MAY cease to advertise the MODE-READER capability after the
client uses any command except CAPABILITIES, in which case the
response code 502 MUST be returned for such commands.

Notes
-----
Here are two examples to illustrate Section 5.3.3 with that clarification.

Example of the 401 response code to indicate that MODE READER is needed:

   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] MODE-READER
   [S] .
   [C] POST
   [S] 401 MODE-READER
   [C] MODE READER
   [S] 200 Reader mode, posting permitted
   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] READER
   [S] LIST ACTIVE NEWSGROUPS
   [S] POST
   [S] .

Example of a mode-switching server which does not allow any reader
command to be used, even unsuccessfully, in transit mode:

   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] MODE-READER
   [S] .
   [C] POST
   [S] 502 Transit service only
   [C] CAPABILITIES
   [S] 101 Capability list:
   [S] VERSION 2
   [S] IHAVE
   [S] .
   [C] MODE READER
   [S] 502 Transit service only
   [Server closes connection.]






----- Message d'origine ----- 
De : RFC Errata System
À : Clive, Chris, Lisa, Ned, Russ
Cc : Julien, RFC Editor
Envoyé : mercredi 24 septembre 2008 19:34
Objet : [Technical Errata Reported] RFC3977 (1527)


>
> The following errata report has been submitted for RFC3977,
> "Network News Transfer Protocol (NNTP)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3977&eid=1527
>
> --------------------------------------
> Type: Technical
> Reported by: Julien Élie
>
> Section: 3.2.1
>
> Original Text
> -------------
> 401: The client must change the state of the connection in some other
>   manner.  The first argument of the response MUST be the capability
>   label (see Section 5.2) of the facility that provides the
>   necessary mechanism (usually an extension, which may be a private
>   extension).  The server MUST NOT use this response code except as
>   specified by the definition of the capability in question.
>
> Corrected Text
> --------------
>
>
> Notes
> -----
> The 401 code is never dealt with in the whole RFC 3977.  Even the definition of 
> the MODE-READER capability does not indicate when the 401 return code should be 
> used.
> It should be said that it MUST be used in answers to commands only available after 
> having sent MODE READER.  Maybe section 5.3.2 that described the MODE READER 
> command, is the right place to use in order to specify that behaviour.
>
> [C] CAPABILITIES
> [S] 101 Capability list:
> [S] VERSION 2
> [S] IHAVE
> [S] MODE-READER
> [S] .
> [C] POST
> [S] 401 MODE-READER
> [C] MODE READER
> [S] 200 Reader mode, posting permitted
> [C] CAPABILITIES
> [S] 101 Capability list:
> [S] VERSION 2
> [S] READER
> [S] POST
> [S] .
> [C] POST
> [S] 340 Input article; end with <CR-LF>.<CR-LF>
> [C] From: "Demo User" <nobody@example.net>
> [C] Newsgroups: misc.test
> [C] Subject: I am just a test article
> [C] Organization: An Example Net
> [C]
> [C] This is just a test article.
> [C] .
> [S] 240 Article received OK
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC3977 (draft-ietf-nntpext-base-27)
> --------------------------------------
> Title               : Network News Transfer Protocol (NNTP)
> Publication Date    : October 2006
> Author(s)           : C. Feather
> Category            : PROPOSED STANDARD
> Source              : NNTP Extensions
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
> 



--------------060901060601060507060507--

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Mon May 14 18:02:45 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2455421F851B for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 18:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DU6oxyhwWNT for <ietfarch-nntpext-archive@ietfa.amsl.com>; Mon, 14 May 2012 18:02:44 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 8208C21F8503 for <nntpext-archive@ietf.org>; Mon, 14 May 2012 18:02:44 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id EC3A867E6D for <nntpext-archive@ietf.org>; Mon, 14 May 2012 18:02:43 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by hope.eyrie.org (Postfix) with ESMTP id 89CF267E4A for <ietf-nntp@lists.eyrie.org>; Mon, 14 May 2012 06:15:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D9E4112C770; Mon, 14 May 2012 06:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEIFxMkQ-o6E; Mon, 14 May 2012 06:15:57 -0700 (PDT)
Received: from rfc2.home (pool-74-96-66-108.washdc.fios.verizon.net [74.96.66.108]) by c8a.amsl.com (Postfix) with ESMTPSA id 0BE0512C76F; Mon, 14 May 2012 06:15:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <CALaySJK6brcCEtjOrcgmjUs1EgXXuh_h913CQonV35-NyyGwOQ@mail.gmail.com>
Date: Mon, 14 May 2012 09:15:59 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <75DF3FCB-DB7D-4C3B-A4C8-3960947DE6F1@amsl.com>
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com> <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com> <877gwfk4ij.fsf@windlord.stanford.edu> <CALaySJK6brcCEtjOrcgmjUs1EgXXuh_h913CQonV35-NyyGwOQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Mon, 14 May 2012 18:02:42 -0700
Cc: Russ Allbery <rra@stanford.edu>, =?iso-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>, The IESG <iesg@ietf.org>, ietf-nntp@lists.eyrie.org, "Clive D.W. Feather" <clive@davros.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Barry,

The status has been changed as requested:
http://www.rfc-editor.org/errata_search.php?eid=2004

Thank you.
RFC Editor/ar

On May 14, 2012, at 7:26 AM, Barry Leiba wrote:

>>> I'd be happy, if Clive, Russ, and Julien all think it's the right
>>> approach, to change the erratum to "hold for document update".  Russ
>>> Allbery, do you have a comment on this?
>> 
>> Yes, please.  We would clearly want to fix this in any revision of RFC
>> 3977.  Personally, I would recommend that any implementor use 423 as
>> described in Julien's analysis despite the wording of RFC 3977.
> 
> OK, that works for me.
> 
> RFC Editor, will you please switch errata #2004 from "rejected" to
> "hold for document update"?  Thanks.
> 
> Barry
> 


From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 04:07:48 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA9221F862F for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 04:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_56=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0FutzMa-546 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 04:07:47 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 75C0521F84D5 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 04:07:47 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id CAF1567D06 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 04:07:46 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from nyder.davros.org (nyder.davros.org [82.68.24.146]) by hope.eyrie.org (Postfix) with ESMTP id C7ACA67D00 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 04:07:44 -0700 (PDT)
Received: from nyder.davros.org (localhost [127.0.0.1]) by nyder.davros.org (8.14.4/8.14.4) with ESMTP id q4FB7g3f027229; Tue, 15 May 2012 12:07:43 +0100 (BST) (envelope-from clive@nyder.davros.org)
Received: (from clive@localhost) by nyder.davros.org (8.14.4/8.14.4/Submit) id q4FB7gdK027228; Tue, 15 May 2012 12:07:42 +0100 (BST) (envelope-from clive)
Date: Tue, 15 May 2012 12:07:42 +0100
From: "Clive D.W. Feather" <clive@davros.org>
To: Julien =?iso-8859-1?Q?=C9LIE?= <julien@trigofacile.com>
Message-ID: <20120515110742.GA25534@davros.org>
References: <2958FE1C9A0446E39943C89CE0C53924@Iulius>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2958FE1C9A0446E39943C89CE0C53924@Iulius>
User-Agent: Mutt/1.4.2.3i
Cc: ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] Interoperability with 502 answer to GROUP command
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Julien LIE said:
> We had a question on inn-workers about the response code a news server
> should give to a GROUP command for an existing newsgroup to which the
> client does not have access:
>    https://lists.isc.org/pipermail/inn-workers/2010-September/017275.html

Hi,

Found this while looking into the errata.

> It appears that INN answers 480/502 (depending on the state of 
> authentication)
> but a few news clients (amongst them are tin and Thunderbird) immediately
> close the connection.
> As a matter of fact, according to RFC 3977:
> 
>   502:  It is necessary to terminate the connection and to start a new
>                            ^^^^^^^^^^^^^^^^^^^^^^^^
>         one with the appropriate authority before the command can be used.

That's for a *command*, not for a specific set of parameters.

> Suppose we have three groups on a news server :
> * group.public, readable by everybody
> * group.auth1, readable by user1
> * group.auth2, readable by user2
> 
> Are the following answers the right ones?
> 
> 200 Hello!
> 
> LIST ACTIVE
> 215 Newsgroups in form "group high low status"
> group.public 0000000003 0000000001 y
> .

Whether you list group.auth[12] depends on whether you want to publish the
fact of existence to people who don't have authority to read it. There
isn't a "right" answer.

> GROUP group.auth2
> 480 Read access denied

Correct.

> AUTHINFO USER user1
> 381 Enter password
> AUTHINFO PASS pass1
> 281 Authentication succeeded
> 
> LIST ACTIVE
> 215 Newsgroups in form "group high low status"
> group.public 0000000003 0000000001 y
> group.auth1 0000000003 0000000001 y
> .

Fine.

> GROUP group.auth2
> 502 Read access denied

No, this should be another 480. After all, in principle you could
reauthenticate as user2.

>  Another possibility would be 411 but it would mean that the
>  newsgroup is unknown (and therefore does not exist).  It is not
>  the case.

If you want to hide the presence of group.auth2 entirely from people who
don't have access to it, you could use a 411. But then why did you return
480 to group.auth1?

You need to decide one of:
(1) People can know about groups they don't have access to. They appear
in LIST ACTIVE. You return 480 to any attempt to get at the group with
authority.
(2) People can't know about groups they don't have access to. They don't
appear in LIST ACTIVE and you return 411 to attempts to get them. The user
has to know that she needs to authenticate and they will magically appear.
(3) Any mix of the above.

-- 
Clive D.W. Feather          | If you lie to the compiler,
Email: clive@davros.org     | it will get its revenge.
Web: http://www.davros.org  |   - Henry Spencer
Mobile: +44 7973 377646

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 05:04:23 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B086E21F8806 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2z5SJYT+km1I for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:04:22 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id BE85621F8803 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:04:22 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 34A2D67D06 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:04:22 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from nyder.davros.org (nyder.davros.org [82.68.24.146]) by hope.eyrie.org (Postfix) with ESMTP id 2AEFF67CF7 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 05:04:19 -0700 (PDT)
Received: from nyder.davros.org (localhost [127.0.0.1]) by nyder.davros.org (8.14.4/8.14.4) with ESMTP id q4FC4FpF027961; Tue, 15 May 2012 13:04:15 +0100 (BST) (envelope-from clive@nyder.davros.org)
Received: (from clive@localhost) by nyder.davros.org (8.14.4/8.14.4/Submit) id q4FC4EVA027960; Tue, 15 May 2012 13:04:14 +0100 (BST) (envelope-from clive)
Date: Tue, 15 May 2012 13:04:14 +0100
From: "Clive D.W. Feather" <clive@davros.org>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20120515120414.GB25534@davros.org>
References: <4FB17C0F.7030602@trigofacile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FB17C0F.7030602@trigofacile.com>
User-Agent: Mutt/1.4.2.3i
Cc: ietf-nntp@lists.eyrie.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: [NNTP] Errata 1522 and 2719 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

I'm not clear why these are Held for Document Update - they should be
Verified.

-- 
Clive D.W. Feather          | If you lie to the compiler,
Email: clive@davros.org     | it will get its revenge.
Web: http://www.davros.org  |   - Henry Spencer
Mobile: +44 7973 377646

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 05:38:05 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD9321F8952 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.954
X-Spam-Level: 
X-Spam-Status: No, score=-102.954 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t95L1GETIID9 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:38:05 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id F3E3321F894E for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:38:04 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 3DB5C67D0E for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:38:04 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by hope.eyrie.org (Postfix) with ESMTP id 7C37067D02 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 05:38:02 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so12272231obb.18 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 05:38:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kiElchXNWoMQU/C/GDBSXwghvg1Z+PK1lJjjHWJw3gM=; b=In82ckFTdq3FzOB2f9QxADCUzaLM1W7/komTf7nqkTRci/5pBo9DcenPhZONYWHj6c Tv6A4oVUN/il36hFEKC9UF5PTlhqWSD5B3vvWCTxS8048SQUC1loAayh0axqmUOoOh0D cvaCrf+xm+30FjlHyF9QtrI7k9GmvcThLZCTrSBjuXQqBQciHIwyF/H8hy/bJRc53yBc 3962MXnvJ7bGQr5+MPqyzTokSC4n4v/txJ7zLP/ZvwbjEoovd97888Hnf7pPzHxYJrro 2HZ2Zoj7AR60zxUsr22Hxkin04TikGulJlB4vQXuVxGkDhTT3AhVxjik3HcoW2rRqkYX UuNw==
MIME-Version: 1.0
Received: by 10.182.12.6 with SMTP id u6mr17152173obb.12.1337085482033; Tue, 15 May 2012 05:38:02 -0700 (PDT)
Received: by 10.60.10.68 with HTTP; Tue, 15 May 2012 05:38:01 -0700 (PDT)
In-Reply-To: <20120515120414.GB25534@davros.org>
References: <4FB17C0F.7030602@trigofacile.com> <20120515120414.GB25534@davros.org>
Date: Tue, 15 May 2012 08:38:01 -0400
X-Google-Sender-Auth: inRO-E0ljmZ4_j8TVmMwhVwEkB8
Message-ID: <CALaySJLFyVMTqT74+BkmsCnX1i2JHgp94dQHeGcOgvYryDoc8A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Clive D.W. Feather" <clive@davros.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf-nntp@lists.eyrie.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] Errata 1522 and 2719 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Hi, Clive.

> I'm not clear why these are Held for Document Update - they should be
> Verified.

See the IESG statement on processing of errata:
https://www.ietf.org/iesg/statement/errata-processing.html

In particular:

> 1. Only errors that could cause implementation or deployment problems or
> significant confusion should be Approved.

...and...

> 5. Typographical errors which would not cause any confusions to implementation
> or deployments should be Hold for Document Update.

So Lisa and Peter, respectively, were correct in their handling of those two.

Barry

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 05:41:32 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B192721F898E for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKsWQbhPLlzX for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 05:41:32 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 21E4921F898B for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:41:32 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id CA54567D2E for <nntpext-archive@ietf.org>; Tue, 15 May 2012 05:41:31 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from nyder.davros.org (nyder.davros.org [82.68.24.146]) by hope.eyrie.org (Postfix) with ESMTP id 4508167D09 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 05:41:30 -0700 (PDT)
Received: from nyder.davros.org (localhost [127.0.0.1]) by nyder.davros.org (8.14.4/8.14.4) with ESMTP id q4FCfQ9N032369; Tue, 15 May 2012 13:41:27 +0100 (BST) (envelope-from clive@nyder.davros.org)
Received: (from clive@localhost) by nyder.davros.org (8.14.4/8.14.4/Submit) id q4FCfQ7G032368; Tue, 15 May 2012 13:41:26 +0100 (BST) (envelope-from clive)
Date: Tue, 15 May 2012 13:41:26 +0100
From: "Clive D.W. Feather" <clive@davros.org>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20120515124126.GC25534@davros.org>
References: <4FB17C0F.7030602@trigofacile.com> <20120515120414.GB25534@davros.org> <CALaySJLFyVMTqT74+BkmsCnX1i2JHgp94dQHeGcOgvYryDoc8A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALaySJLFyVMTqT74+BkmsCnX1i2JHgp94dQHeGcOgvYryDoc8A@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] Errata 1522 and 2719 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Barry Leiba said:
>> 1. Only errors that could cause implementation or deployment problems or
>> significant confusion should be Approved.
> ...and...
>> 5. Typographical errors which would not cause any confusions to implementation
>> or deployments should be Hold for Document Update.
> So Lisa and Peter, respectively, were correct in their handling of those two.

Okay.

-- 
Clive D.W. Feather          | If you lie to the compiler,
Email: clive@davros.org     | it will get its revenge.
Web: http://www.davros.org  |   - Henry Spencer
Mobile: +44 7973 377646

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 06:08:26 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 224C421F8967 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 06:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJQUvmghBdX2 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 06:08:26 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id E42E721F893A for <nntpext-archive@ietf.org>; Tue, 15 May 2012 06:08:25 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 2E8FE67E4E for <nntpext-archive@ietf.org>; Tue, 15 May 2012 06:08:25 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from nyder.davros.org (nyder.davros.org [82.68.24.146]) by hope.eyrie.org (Postfix) with ESMTP id C193B67D0E for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 06:08:22 -0700 (PDT)
Received: from nyder.davros.org (localhost [127.0.0.1]) by nyder.davros.org (8.14.4/8.14.4) with ESMTP id q4FD82uL032932; Tue, 15 May 2012 14:08:03 +0100 (BST) (envelope-from clive@nyder.davros.org)
Received: (from clive@localhost) by nyder.davros.org (8.14.4/8.14.4/Submit) id q4FD82jn032931; Tue, 15 May 2012 14:08:02 +0100 (BST) (envelope-from clive)
Date: Tue, 15 May 2012 14:08:02 +0100
From: "Clive D.W. Feather" <clive@davros.org>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20120515130802.GE25534@davros.org>
References: <20120512183346.A53E262180@rfc-editor.org> <4FB008C4.3000009@trigofacile.com> <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALaySJK8+hTNf-r+uw1g_nGJXDCAu0Ga5_ZaM3n+OLchOy4ysg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Russ ALLBERY <rra@stanford.edu>, Julien =?iso-8859-1?Q?=C9LIE?= <julien@trigofacile.com>, iesg@ietf.org, ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] [Errata Rejected] RFC3977 (2004)
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Barry Leiba said:
> Well, the response in the rejection reason is taken directly from an
> exchange I had with Clive.  Now, he did also suggest that I might pass
> it by Russ Allbery, which I have not yet done.  Since he's copied on
> this exchange, he can comment.  Clive's point wasn't meant to say that
> your suggestion in the errata report wasn't good, but that it's not
> bringing up an *error* in the original spec.

To be honest, I'd forgotten that earlier discussion.

> I'd be happy, if Clive, Russ, and Julien all think it's the right
> approach, to change the erratum to "hold for document update".

I think we've all now agreed this is the right approach.

-- 
Clive D.W. Feather          | If you lie to the compiler,
Email: clive@davros.org     | it will get its revenge.
Web: http://www.davros.org  |   - Henry Spencer
Mobile: +44 7973 377646

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 09:34:45 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E3421F89A5 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 09:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.806
X-Spam-Level: 
X-Spam-Status: No, score=-102.806 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+GLLjcp1j46 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 09:34:44 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 907BA21F899E for <nntpext-archive@ietf.org>; Tue, 15 May 2012 09:34:44 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id D660867E64 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 09:34:43 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by hope.eyrie.org (Postfix) with ESMTP id 1220A67E4E for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 09:34:43 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so12600716obb.18 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 09:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=P8y925OQwbFb7ggkY0ingdiBeMvX94SXdcLlE6PC7nk=; b=BMqw0vAPY9S2YEZvqEG8FaLGA4Use42lrfAihY8EhbnQy2lpFmH9vD5sLFbD1uNdpJ CRSDVBM5pRSNy9+JBMT4wZTfYt1G0g5TmFTESENeh2M3jyWP0UpGVjYcF9QXQXAGh9Mk Lg1bt0wYRpAl6IZMGu3ZBkgWMhkmetG9Z2hPDi7E9fsyhO324F1q0wtzlTL3vLvDXSGR xEDBFDRC/2nA6tUSKhFRMAvwLdDlDT2erNMlrY0YeaYdP/6TY10hRnYTkA93wgb8jUst 0G9mLXi2SqYpRfOsuje6CXdHwaLa4ahBZI1kp7EfbwyGRclTARJa6nIUo8ItkyGDMh+r 9+9Q==
MIME-Version: 1.0
Received: by 10.182.37.37 with SMTP id v5mr4068038obj.51.1337099682592; Tue, 15 May 2012 09:34:42 -0700 (PDT)
Received: by 10.60.10.68 with HTTP; Tue, 15 May 2012 09:34:42 -0700 (PDT)
In-Reply-To: <4FB17C0F.7030602@trigofacile.com>
References: <4FB17C0F.7030602@trigofacile.com>
Date: Tue, 15 May 2012 12:34:42 -0400
X-Google-Sender-Auth: rgd7taMCjpQjCzr1LWZQdTCsG6U
Message-ID: <CALaySJKutjT-J+8nU+FAGqvC+DiCQOM-gXHqOm5nEWBN=FFJ6A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, ietf-nntp@lists.eyrie.org
Subject: Re: [NNTP] Errata 1707 and 1527 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

> As I see that you are currently pretty active on errata for RFC 3977, I
> believe it could be time to properly close the two remaining subjects that
> weren't updated two years ago.

Well, I've been trying to address "reported" errata that haven't been
classified, not trying to spin up more work.  :-)  But still....

> * Could the following rationale be added to erratum 1707 for RFC 3977 so as
> to explain the reason of the reject?

I have asked the RFC Editor to help me with this, off list.  We'll get
it sorted out.

> * Could erratum 1527 for RFC 3977 be updated and its status changed to
> "VERIFIED" so that it could be properly reviewed when the NNTP protocol
> moves from proposed standard to draft standard?

No, I'm afraid this isn't what errata are for.  The IESG reserves
"Verified" for this:

1. The report is correct, AND
2. the error would have been considered an error in the original
document, had it been noticed then (that is, this didn't come up
because things have changed since then, or "we don't really do it that
way in practice"), AND
3. implementors or deployers MUST see the correction, or they will
face implementation/deployment problems.

See the IESG statement on errata handling for more information:
http://www.ietf.org/iesg/statement/errata-processing.html

This one appears to be exactly what "held for document update" is for:
It's flagged for review if/when the document is ever updated or
advanced on the standards track.  That seems to be just what you want
anyway, so there's no reason to change the status.

Barry

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 10:00:15 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99FF21F882D for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 10:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BdM2H-KIVpC8 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 10:00:13 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id 5483621F87CD for <nntpext-archive@ietf.org>; Tue, 15 May 2012 10:00:13 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 0748C67E64 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 10:00:13 -0700 (PDT)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from smtp.stanford.edu (smtp3.Stanford.EDU [171.67.219.83]) by hope.eyrie.org (Postfix) with ESMTP id 2DAF367D0E for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 10:00:12 -0700 (PDT)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id B5A4C45604C for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 10:00:11 -0700 (PDT)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id D715F45655D for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 10:00:10 -0700 (PDT)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id 9807E2F45F; Tue, 15 May 2012 10:00:10 -0700 (PDT)
From: Russ Allbery <rra@stanford.edu>
To: ietf-nntp@lists.eyrie.org
In-Reply-To: <20120515110742.GA25534@davros.org> (Clive D. W. Feather's message of "Tue, 15 May 2012 12:07:42 +0100")
Organization: The Eyrie
References: <2958FE1C9A0446E39943C89CE0C53924@Iulius> <20120515110742.GA25534@davros.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Tue, 15 May 2012 10:00:10 -0700
Message-ID: <87zk99wfad.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [NNTP] Interoperability with 502 answer to GROUP command
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

"Clive D.W. Feather" <clive@davros.org> writes:
> Julien LIE said:

>> GROUP group.auth2
>> 502 Read access denied

> No, this should be another 480. After all, in principle you could
> reauthenticate as user2.

No, you can't; see RFC 4643:

   After a successful authentication, the client MUST NOT issue another
   AUTHINFO command in the same session.  A server MUST NOT return the
   AUTHINFO capability in response to a CAPABILITIES command, and a
   server MUST reject any subsequent AUTHINFO commands with a 502
   response.

After you've authenticated, if you still can't read the group but the
group is not hidden, "permission denied" is the correct error code so far
as I can see.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 14:27:08 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C80811E80B2 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 14:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUftuJ04PXvl for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 14:27:07 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id CA17611E8074 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 14:27:07 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 44D3F67E70 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 14:27:07 -0700 (PDT)
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 06EE567E64 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 14:27:04 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 967E88177 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 23:27:03 +0200 (CEST)
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 byZFLlhFQDK4 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 23:27:03 +0200 (CEST)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-100-201.w83-114.abo.wanadoo.fr [83.114.195.201]) by denver.dinauz.org (Postfix) with ESMTPSA id 5F2C9805C for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 23:27:03 +0200 (CEST)
Message-ID: <4FB2CA26.2030206@trigofacile.com>
Date: Tue, 15 May 2012 23:27:02 +0200
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.7; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
References: <2958FE1C9A0446E39943C89CE0C53924@Iulius> <20120515110742.GA25534@davros.org>
In-Reply-To: <20120515110742.GA25534@davros.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [NNTP] Interoperability with 502 answer to GROUP command
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Hi Clive,

> If you want to hide the presence of group.auth2 entirely from people who
> don't have access to it, you could use a 411. But then why did you return
> 480 to group.auth1?
>
> You need to decide one of:
> (1) People can know about groups they don't have access to. They appear
> in LIST ACTIVE. You return 480 to any attempt to get at the group with
> authority.
> (2) People can't know about groups they don't have access to. They don't
> appear in LIST ACTIVE and you return 411 to attempts to get them. The user
> has to know that she needs to authenticate and they will magically appear.
> (3) Any mix of the above.

Understood, and agreed.  Many thanks for your answer.
It is up to the implementation to decide how it wants to handle the case.

-- 
Julien ÉLIE

« Mieux vaut allumer une bougie que maudire les ténèbres. » (Lao
   Zi)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Tue May 15 14:35:35 2012
Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com
Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5977F11E8074 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 14:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2qRB6IGl93p for <ietfarch-nntpext-archive@ietfa.amsl.com>; Tue, 15 May 2012 14:35:34 -0700 (PDT)
Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) by ietfa.amsl.com (Postfix) with ESMTP id A795211E8093 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 14:35:34 -0700 (PDT)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 5FE5667E70 for <nntpext-archive@ietf.org>; Tue, 15 May 2012 14:35:34 -0700 (PDT)
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 129BB67E64 for <ietf-nntp@lists.eyrie.org>; Tue, 15 May 2012 14:35:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 782328177; Tue, 15 May 2012 23:35:32 +0200 (CEST)
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 OxLEK4I1mvY1; Tue, 15 May 2012 23:35:32 +0200 (CEST)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-100-201.w83-114.abo.wanadoo.fr [83.114.195.201]) by denver.dinauz.org (Postfix) with ESMTPSA id 3A808805C; Tue, 15 May 2012 23:35:32 +0200 (CEST)
Message-ID: <4FB2CC23.5030007@trigofacile.com>
Date: Tue, 15 May 2012 23:35:31 +0200
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.7; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <4FB17C0F.7030602@trigofacile.com> <CALaySJKutjT-J+8nU+FAGqvC+DiCQOM-gXHqOm5nEWBN=FFJ6A@mail.gmail.com>
In-Reply-To: <CALaySJKutjT-J+8nU+FAGqvC+DiCQOM-gXHqOm5nEWBN=FFJ6A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf-nntp@lists.eyrie.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [NNTP] Errata 1707 and 1527 for RFC 3977
X-BeenThere: ietf-nntp@lists.eyrie.org
X-Mailman-Version: 2.1.13
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

Hi Barry,

>> As I see that you are currently pretty active on errata for RFC 3977, I
>> believe it could be time to properly close the two remaining subjects that
>> weren't updated two years ago.
>
> Well, I've been trying to address "reported" errata that haven't been
> classified, not trying to spin up more work.  :-)  But still...

Many thanks to you!
And sorry for pushing a bit to hard...


>> * Could the following rationale be added to erratum 1707 for RFC 3977 so as
>> to explain the reason of the reject?
>
> I have asked the RFC Editor to help me with this, off list.  We'll get
> it sorted out.

Thanks !


>> * Could erratum 1527 for RFC 3977 be updated and its status changed to
>> "VERIFIED" so that it could be properly reviewed when the NNTP protocol
>> moves from proposed standard to draft standard?
>
> This one appears to be exactly what "held for document update" is for:
> It's flagged for review if/when the document is ever updated or
> advanced on the standards track.  That seems to be just what you want
> anyway, so there's no reason to change the status.

OK, I understand that the status should remain the same.
My concern was that we found out the wording to use for Section 3.4.2 
and two examples for Section 5.3.3 so as to fix the issue, and I do not 
know how not to lose the work done.  (No need to do the work twice, 
especially when the exact update is already known.)

-- 
Julien ÉLIE

« Mieux vaut allumer une bougie que maudire les ténèbres. » (Lao
   Zi)
