[NNTP] Tr: [Errata Held for Document Update] RFC3977 (1707) -- archive of rationale

Julien ÉLIE <julien@trigofacile.com> Sat, 23 January 2010 12:58 UTC

Return-Path: <ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org>
X-Original-To: ietfarch-nntpext-archive@core3.amsl.com
Delivered-To: ietfarch-nntpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF7043A6809 for <ietfarch-nntpext-archive@core3.amsl.com>; Sat, 23 Jan 2010 04:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.809
X-Spam-Level:
X-Spam-Status: No, score=-0.809 tagged_above=-999 required=5 tests=[AWL=-1.245, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3, STOX_REPLY_TYPE=0.001, TVD_FINGER_02=2.134]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4emf7fhOh9eI for <ietfarch-nntpext-archive@core3.amsl.com>; Sat, 23 Jan 2010 04:58:59 -0800 (PST)
Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) by core3.amsl.com (Postfix) with ESMTP id CDA173A67D9 for <nntpext-archive@ietf.org>; Sat, 23 Jan 2010 04:58:58 -0800 (PST)
Received: from hope.eyrie.org (localhost [127.0.0.1]) by hope.eyrie.org (Postfix) with ESMTP id A3A3067E0A for <nntpext-archive@ietf.org>; Sat, 23 Jan 2010 04:58:54 -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: Julien ÉLIE <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+nntpext-archive=ietf.org@lists.eyrie.org
Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org

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
>