Re: [dispatch] [NNTP] Internet Draft for NNTP additions submitted

Ken Murchison <murch@fastmail.com> Sat, 18 April 2020 12:20 UTC

Return-Path: <murch@fastmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461163A046A for <dispatch@ietfa.amsl.com>; Sat, 18 Apr 2020 05:20: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=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=O7ToKD5g; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=3IvHtK/k
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUgMwudYduj6 for <dispatch@ietfa.amsl.com>; Sat, 18 Apr 2020 05:20:06 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC373A045E for <dispatch@ietf.org>; Sat, 18 Apr 2020 05:20:06 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id A9810613; Sat, 18 Apr 2020 08:20:05 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 18 Apr 2020 08:20:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=C jQSlYJCIVrYysdOHu9tmP4qi+eMiyX+49ltZgGuEpM=; b=O7ToKD5g7gg/4LLCR 3/jKoJxtq/gG215DhFnlbb7/t3iWk8T1mHEy+oaaljniFtXJ2MA/LUGDSHNtO5Lf JrXSmJs0si35nfouk9ePhNPnuM1WdNmFyOI3E+xvu5JnT8wNnCkK6EU7xj7o4y/a 41rLUPFDBHSPcLS+vwdttuFSsrN9/V4PCSWzRoEv0kq6HFamC6StqdH6hnT5tlvF dfnqXABqxX54Eds7i85GFQXbNpSuFLU8KnkanElZ9zkUdfug7kGlF/SPyDCqDoZJ pF8n8I9TxHDp1TM2W/1Hw/CnoFc4TJfVfVvvn93FcjJvqvbQntq25I1bIbyYM07m HgjxQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=CjQSlYJCIVrYysdOHu9tmP4qi+eMiyX+49ltZgGuE pM=; b=3IvHtK/kJkLcDkAk1ry+y/h4TUvHpr4+8M6lMLRdmGRqO3FGkM3NeD+9r w8MUmRblioyYUscReUNc0lYf/Yz9qbNS1aA9eVCHRsOZu6ZqzeC1Lwb9swJyM0sn ML9Ej4sOzQWX5bpU8d+O/dkk1hyq1iYNswpL80/+ZiFq9dCiQFr3Escsg9cajHgG tz7EoqGDK9nVXvJ0wMc/ER+V6iPqGICGQLk+N9v27NsBT27PyhFZj2DI/qJj952v ljV4FlI6dbefmfDB37UjQXsMCyvYkCoYxNI9BfxBatCz1AGPhP0MugzF1szNcefe maoArk6FVQQc8B7XnTh9B8GgfKy2w==
X-ME-Sender: <xms:dPCaXmg1WQJSLfKjiwn0SlsObutiFX8OtcvtynFBuF-4nN1lZoaMIg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeelgdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhfhokffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvnhcu ofhurhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuffhomh grihhnpehivghtfhdrohhrghdpvgihrhhivgdrohhrghenucfkphepjeegrdejjedrkeeh rddvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:dPCaXhWqsYGZbf6l_c08D9qgwhqpNfGknl1uOLnPH3nyMmPvEbbW6w> <xmx:dPCaXoUzMJZffv6ajb_nVySuar51l_Zi2lLDo3-lPhI_BKdlcA56Iw> <xmx:dPCaXlhiHft5he8qgIzV4-T2ZWlJMvXTQ2ZtujtcZJ5NcLD2iksbZg> <xmx:dfCaXnBbbYqIlIxeZsFkB2ygree-sjFfUzi3qq3AqyuKUKwWGkPf5g>
Received: from localhost.localdomain (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 8AEFF328005E; Sat, 18 Apr 2020 08:20:04 -0400 (EDT)
To: Julien ÉLIE <julien@trigofacile.com>, dispatch@ietf.org, ietf-nntp@lists.eyrie.org
References: <CAKFo7wmMsX-FcijRRoYLapnSatqwA8GPYgvOeaCMEvts=ArULA@mail.gmail.com> <54da6d7a-23da-aa43-92e1-64903c1ad053@trigofacile.com>
From: Ken Murchison <murch@fastmail.com>
Organization: FastMail US LLC
Message-ID: <87cf665d-97c1-fd95-9f05-793d722d5195@fastmail.com>
Date: Sat, 18 Apr 2020 08:20:03 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <54da6d7a-23da-aa43-92e1-64903c1ad053@trigofacile.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/OkH1mtl0-3FenMOqcUTfE91voP0>
Subject: Re: [dispatch] [NNTP] Internet Draft for NNTP additions submitted
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Apr 2020 12:20:08 -0000

On 4/5/20 7:38 AM, Julien ÉLIE wrote:
> Hi all,
>
>> I have made the first I-D for the NNTP additions. It has been 
>> submitted to the IETF datatracker. The file name is 
>> draft-sam-nntpupdates-00.txt
>
> https://www.ietf.org/id/draft-sam-nntpupdates-00.txt
>
>
> Here are a few comments:
>
>>    Article numbers MUST lie between 1 and 9,223,372,036,854,775,807, 
>>    inclusive.  The client and server MAY use leading zeroes in    
>> specifying article numbers but MUST NOT use more than 19 digits.
> We'll need to define a capability to advertise that new feature.
>
> Note that Ken Murchison once suggested (in 2005) a LARGEGROUP 
> extension, which seems to be a reasonable implementation according to 
> a few discussions since that time:
> https://lists.eyrie.org/pipermail/ietf-nntp/2005-July/005720.html
>
> *************************************************
> - Servers which support 64-bit (large) article counters advertise a
> capability such as 'LARGEGROUP' (or some better named capability).
>
> - Servers always hide (411 response for [LIST]GROUP, ommission from LIST
> ACTIVE response) groups which have exceeded the 32-bit article count
> from clients until the client tells the server that it can support such
> groups.
>
> - A client tells the server that it supports large groups by using the
> new keyword 'LARGEGROUP' as an argument to the CAPABILITY command.
>
> - The server can then use the existing response codes for the
> [LIST]GROUP and LIST ACTIVE commands.
> *************************************************
>
>
> Also note Clive Feather's BIGNUM proposal:
> https://lists.eyrie.org/pipermail/ietf-nntp/2005-July/005802.html


At this point, why not just define a NNTP VERSION 3 capability which 
indicates that all commands that accept/return article numbers can be 63 
bit?  This requires no changes to existing commands, and clients will 
know right away from the capabilities whether they should proceed or not.


-- 
Kenenth Murchison
Senior Software Developer
Fastmail US LLC