[NNTP] Advertise maximum article size in CAPABILITIES

River Tarnell river at RT.UK.EU.ORG
Sat Jan 7 09:14:17 PST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(Re-sending this because it didn't appear again; I know I'm subscribed 
this time, so I think the S/MIME signature must be the problem.)

Hi,

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.

Regards,
- -- 
        -- river.                      | Free Usenet: http://news.rt.uk.eu.org/
Non-Reciprocal Laws of Expectations:   | PGP: 2B9CE6F2
    Negative expectations yield negative results.
    Positive expectations yield negative results.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)

iEYEARECAAYFAk8IfWkACgkQIXd7fCuc5vLyzQCgi77nSFZxsQMfGiXwKVWwPLUD
BIYAnA4ih68eP+PSPvE7sqT0alDFNXeC
=35Lw
-----END PGP SIGNATURE-----


More information about the ietf-nntp mailing list