
From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Sun Dec  9 05:59:17 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 D584521F8C12 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun,  9 Dec 2012 05:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.44
X-Spam-Level: 
X-Spam-Status: No, score=-0.44 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqN5RClmP6xF for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun,  9 Dec 2012 05:59:17 -0800 (PST)
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 02DDD21F8C08 for <nntpext-archive@ietf.org>; Sun,  9 Dec 2012 05:59:13 -0800 (PST)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id E7BE567E05 for <nntpext-archive@ietf.org>; Sun,  9 Dec 2012 05:59:11 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id 8037667DB2 for <ietf-nntp@lists.eyrie.org>; Sun,  9 Dec 2012 05:59:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 930F3818D; Sun,  9 Dec 2012 14:59:09 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YKBnhCkcnqR; Sun,  9 Dec 2012 14:59:09 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-137-73.w83-114.abo.wanadoo.fr [83.114.112.73]) by denver.dinauz.org (Postfix) with ESMTPSA id 48FB3817B; Sun,  9 Dec 2012 14:59:09 +0100 (CET)
Message-ID: <50C4992C.7000700@trigofacile.com>
Date: Sun, 09 Dec 2012 14:59:08 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
References: <20120107185610.GA8389@tamara.rt.uk.eu.org>
In-Reply-To: <20120107185610.GA8389@tamara.rt.uk.eu.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: River Tarnell <river@RT.UK.EU.ORG>
Subject: Re: [NNTP] Command to list wanted groups for transit peers
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 River,

I do not know whether you have advanced a bit on that topic since last year.
Anyway, here are a few links...


> So, most (at least non-binary) peering arrangements include a list of
> groups the server wants to accept.  Usually this is configured by hand,
> but there are automated out-of-band methods to do it automatically (e.g.
> GUP, the Group Update Protocol).

Though not the same, but could be used in a similar way, a draft
for Dynamic Feed Adjustment was published a decade ago:
    http://www.eyrie.org/~eagle/nntp/drafts/draft-court-dynfeed-01.txt


> I think a better way to do it would be a new command, which would list
> the groups the server wants to accept as a wildmat.  For instance:
> 
> S: 200 Server ready.
> C: CAPABILITIES
> S: 101 Capabilities list follows.
> S: WANTGROUPS
> S: ...
> S: .
> C: WANTGROUPS
> S: 2xx List of groups follows.
> S: *
> S: @alt.sex.*
> S: @*.bina*
> S: de.bina*
> S: !uk.test
> S: .

It would also need adding the maximum article size or things like that,
possibly related to each line returned by the command.


> This would be an "extended" wildmat like INN uses; I don't think @ is
> available in the RFC 3977 wildmats.
>
> Thoughts?

It could also be a new keyword to the LIST command.

In case it could help, here is a thread we had in December 2009
in news.software.nntp:

    https://groups.google.com/forum/?hl=fr&fromgroups=#!topic/news.software.nntp/fgX4tUk0tGM

"Proposal for a standardized LIST MOTD command"
Message-ID: <he74ps$58i$1@news.trigofacile.com>
Message-ID: <hh4vs5$o2$1@speranza.aioe.org>
...



[Paolo Amori]
LIST MOTD (without argument)

should/must include several data about the server (ie. Tech Contact, Legal 
Contact (the was requested me by the italian police: how can i find the one 
who maintains an NNTP site using *only* the server itself?), Max Article 
Size (and other newsfeeds flags), Web site). They should be shown in a 
standardized way in order to allow people to easily understand them. 
It could also be used as a standardized way show peering data (but a 
standard doesn't exist at the moment)

i'm thinking about somewhat like this


------
Path:                aioe.org
Primary-Host:        nntp.aioe.org
Backup-Host:        news.aioe.org
Accept-From:        news-out.aioe.org
Send-To:                news-in.aioe.org
Tech-Contact:        use...@aioe.org
Abuse-Contact:        ab...@aioe.org
Support-Group:          news://aioe.news.helpdesk
Legal-Contact:        **************** (in order to avoid spam here)
Location:                Holland, EU
Documentation:        http://www.aioe.org/
Max-Article-Size:        32768
Groups:                All except binaries (or an uwildmat string)
------

LIST MOTD <GROUP>

should include the manifesto of each group (they'are collected so it should 
be easy to find them, i suppose)




imho, it's a need.
I've about 40 peers, each one with different peering data. Sometimes, data 
are subjected to changes. There's no common places where peering data can be 
found and many news server don't show these data in their web sites. 
A way to know which parameters are requested by each peer is useful and has 
the advantage to avoid 'third party' configuration errors.

btw, i *strongly* need a standardized way to show which is my legal contact 
(the email address that police *must* use for court orders and legal 
requests). It can be shown inside 'HELP' or 'LIST' output but it's needed an 
official paper that says to use *that* address for such requests.




> Is an RFC considered as an official paper for police?
yes. I've made the same answer to them in an interview room, after three 
hours wait.

> Should ask the question to a policeman :-)
it should be a great idea. Interpol said me that an official statement is 
needed, policeman were convince themselves that newsgroups are 'google 
groups' and so they wanted from me 'apache logs'.

> Well, maybe you need another address than the one for abuse requests...
yes, of course.
Abuse desk is a common email mailbox. Legal contact goes to my mobile phone 
or laptop.





[Jeffrey M. Vinocur]
=> This would require support for nnrpd virtualhosts, FYI.




-- 
Julien ÉLIE

« The hardest thing is to go to sleep at night, when there are so many
  urgent things needing to be done.  A huge gap exists between what we
  know is possible with today's machines and what we have so far been
  able to finish. »  (Donald Knuth)

From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org  Sun Dec  9 06:06:39 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 09D2D21F844E for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun,  9 Dec 2012 06:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.37
X-Spam-Level: 
X-Spam-Status: No, score=-1.37 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPRGihVH9gN4 for <ietfarch-nntpext-archive@ietfa.amsl.com>; Sun,  9 Dec 2012 06:06:38 -0800 (PST)
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 8915321F841C for <nntpext-archive@ietf.org>; Sun,  9 Dec 2012 06:06:38 -0800 (PST)
Received: from hope.eyrie.org (unknown [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id A051E67E05 for <nntpext-archive@ietf.org>; Sun,  9 Dec 2012 06:06:37 -0800 (PST)
X-Original-To: ietf-nntp@lists.eyrie.org
Delivered-To: ietf-nntp@lists.eyrie.org
Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hope.eyrie.org (Postfix) with ESMTP id DB4E267DB2 for <ietf-nntp@lists.eyrie.org>; Sun,  9 Dec 2012 06:06:36 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 8A876818F; Sun,  9 Dec 2012 15:06:36 +0100 (CET)
Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUEygLCdawfm; Sun,  9 Dec 2012 15:06:36 +0100 (CET)
Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-652-1-137-73.w83-114.abo.wanadoo.fr [83.114.112.73]) by denver.dinauz.org (Postfix) with ESMTPSA id 51E6F818E; Sun,  9 Dec 2012 15:06:36 +0100 (CET)
Message-ID: <50C49AEB.50004@trigofacile.com>
Date: Sun, 09 Dec 2012 15:06:35 +0100
From: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf-nntp@lists.eyrie.org
References: <20120107171417.GA7831@tamara.rt.uk.eu.org>
In-Reply-To: <20120107171417.GA7831@tamara.rt.uk.eu.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: River Tarnell <river@RT.UK.EU.ORG>
Subject: Re: [NNTP] Advertise maximum article size in CAPABILITIES
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 River,

> I propose an extension to the NNTP protocol: a server should advertise
> the maximum article size it is willing to accept in CAPABILITIES, via a
> new "SIZE <nbytes>" capability.  A client should not offer any article
> (via POST, IHAVE, CHECK or TAKETHIS) which is larger than that size.
>
> Rationale: no need to configure maximum article size to send to every
> peer; allows peers to change the maximum article size they want to
> accept without having to contact all their peers to change the config;
> allows clients posting multi-part messages (i.e., binaries) to split
> messages based on the server-suggested size.
>
> Real-world use: I can allow articles up to 1MB from a text-only peer,
> while restricting articles from a peer that carries unfiltered binaries
> to 32KB.
>
> I haven't implemented this or done any interoperability checking yet;
> I'm happy to do that and write an I-D/RFC for it myself if it seems like
> a good idea.

I also believe it is a good idea.
Other kinds of parameters related to a feed should be taken care of
at the same time (for instance contents of Distribution: headers, 
minimal article size, maximum number of newsgroups in crosspost...). 
Maybe the feed-related parameters known by innfeed.conf, newsfeeds and 
cleanfeed could be a good start.

-- 
Julien ÉLIE

« The hardest thing is to go to sleep at night, when there are so many
   urgent things needing to be done.  A huge gap exists between what we
   know is possible with today's machines and what we have so far been
   able to finish. »  (Donald Knuth)
