headers
River Tarnell | 7 Jan 2012 19:56

[NNTP] Command to list wanted groups for transit peers

Hi,

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).

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:  <at> alt.sex.*
S:  <at> *.bina*
S: de.bina*
S: !uk.test
S: .
C: CHECK <...

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

Thoughts?
(Continue reading)

Permalink | Reply |
headers
Julien ÉLIE | 9 Dec 2012 14:59
Favicon

Re: [NNTP] Command to list wanted groups for transit peers

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:  <at> alt.sex.*
> S:  <at> *.bina*
> S: de.bina*
> S: !uk.test
(Continue reading)

Permalink | Reply |

Gmane