My vote is as follows:

First preference:  Requester agent, service agent

Second preference:  Requestor agent, provider agent

While I concur with the opinion to try to break out of conventional thinking, I don't think the agent naming issue will be the defining issue for NSI's outside the box thinking.  That will come from the architecture itself.  I hope we can adopt one and move on to describing its functionality in the document adequately to override any potential historical conotation in the reader's mind. 

But here's my vote.

Regards
Jerry

Guy Roberts wrote: 
Hi All,

On the latest NSI conference call we have been pondering a suitable name for the two instances of an Agent that resides on either end of a Network Service Interface.  Up to now the term 'Requestor Agent' has been used to identify the agent that originates the connection request, and 'Provider Agent' for the agent that processes (reserves, provisions etc) the request.  Objections have been raised to this terminology based on the desire to break away from the old use of 'provider' as used in ISP.

We would like to hold a ballot in the NSI group for preferred name.  The following names have been suggested, please respond with an email to me with the number of your preferred choice.


1.       Requestor Agent, Provider Agent

2.       Requestor Agent, Service Agent

3.       Requestor Agent, Granter Agent

4.       Requestor Agent, Implementer Agent

Regards,
Guy

------------------------------------------------------------------------------------------------------------------
Guy  Roberts,  Ph.D

Network Engineering & Planning
DANTE - www.dante.net<http://www.dante.net/>
Tel: +44 (0)1223 371 316
City House, 126-130 Hills Road
Cambridge, CB2 1PQ, UK
------------------------------------------------------------------------------------------------------------------




  

_______________________________________________
nsi-wg mailing list
nsi-wg@ogf.org
http://www.ogf.org/mailman/listinfo/nsi-wg