Re: Xref and relaying agents (was: Protocol changes in draft-allbery-usefor-usepro-00)

"Charles Lindsey" <chl@clerew.man.ac.uk> Wed, 03 January 2007 05:14 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1ySX-00057n-A6 for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:14:41 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1ySU-00013t-9b for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:14:41 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l035CX7g063923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jan 2007 22:12:33 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l035CXXM063910; Tue, 2 Jan 2007 22:12:33 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l035CUgF063860 for <ietf-usefor@imc.org>; Tue, 2 Jan 2007 22:12:31 -0700 (MST) (envelope-from news@clerew.man.ac.uk)
Received: from [80.175.135.89] ([80.175.135.89] helo=clerew.man.ac.uk country=GB ident=postmaster&pop3*clerew#man&ac^uk) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.237) id 459b3b3a.6483.907 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:26 +0000 (envelope-sender <news@clerew.man.ac.uk>)
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id l035CQgf018056 for <ietf-usefor@imc.org>; Wed, 3 Jan 2007 05:12:26 GMT
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id l035CQDe018053 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:26 GMT
To: ietf-usefor@imc.org
Xref: clerew local.usefor:23999
Path: clerew!chl
From: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: Xref and relaying agents (was: Protocol changes in draft-allbery-usefor-usepro-00)
Message-ID: <JB96C7.M1y@clerew.man.ac.uk>
X-Newsreader: NN version 6.5.2 (NOV)
References: <JA8C4p.Anu@clerew.man.ac.uk> <873b7i9b2m.fsf@windlord.stanford.edu> <JAHJs5.FHC@clerew.man.ac.uk> <87fyaygz0d.fsf_-_@windlord.stanford.edu>
Date: Tue, 02 Jan 2007 18:07:19 +0000
Lines: 65
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

In <87fyaygz0d.fsf_-_@windlord.stanford.edu> Russ Allbery <rra@stanford.edu> writes:

>Charles Lindsey <chl@clerew.man.ac.uk> writes:
>> Russ Allbery <rra@stanford.edu> writes:
>>> Charles Lindsey <chl@clerew.man.ac.uk> writes:

>>>> 20. [00] (3.5) Relaying agent MAY add a new Xref header.

>>> Because the same piece of software also implements a serving agent,
>>> which has to add the Xref header, and the same code path is used for
>>> all articles received by the server whether they are for further
>>> relaying or local serving.

>> Well if that is the case it was nominally the serving function that
>> added the Xref (section 3.6).

>No, because changes made by serving agents would only be seen by posting
>agents.  Serving agents do not sent messages to any other news server.
>Only relaying agents do that.

Ah! I see! We carefully said that the order of the steps in the various
"Duties" sections could be varied so long as the final effect was the
same, but we omitted to say the same for the order in which serving and
relaying were done.

You could cover it in the definitions section 1.4 by saying:

'A "relaying agent" accepts articles from injecting agents, serving
agents, or other relaying agents and distributes them ...".'

possibly with corresponding tweaks in the varius "Duties" sections.

My problem was with your wording under Duties of a Relaying Agent where
you said:

9. It MAY delete any Xref header field present and MAY add a new Xref
header field with any valid content. ...

That will be confusing to a reader who has not spotted the subtlety of the
particular order of happenings that we have described, and he will ask
himself "of what possible use is an Xref header added by a _relaying_
agent?". And of course the answer is "none" because it was not really the
relaying agent that you had in mind, but just an artefact of the way
things were described.

I think the simplest thing is to admit that relaying agents may obtain
their input from serving agents, as I have suggested above, and then that
Step 9 for relaying agents can be reduced to a simple "MAY delete XREFs".

>> Now whether such an agent first stores the article and then relays what
>> it has stored, or whether it relays first and then stores after is none
>> of our business.

And so our document should reflect that.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5