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 ------------------------------------------------------------------------------------------------------------------
My preference is for (2) Requestor agent, Service Agent. I would be ok with (3) Requestor Agent, Granter Agent. I am strongly against using (1) Provider Agent, for reasons I outlined in other emails and we talked about this morning. John On Dec 16, 2009, at 12:31 PM, 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 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
Hi Guy, I believe they should be either "requester and provider" or "client and server", as they are well established names, and we do not have any reason to re-define them. So, among the chocies, I choose [1]. Tomohiro On Wed, 16 Dec 2009 17:31:58 +0000 Guy Roberts <Guy.Roberts@dante.net> 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 ------------------------------------------------------------------------------------------------------------------
I agree with Tomohiro. The term "provider" has long grown out of the context of ISPs. The term "service provider" now has a much broader scope, and I do not think it is confusing. Jeroen. On 17/12/2009 12:12, Tomohiro Kudoh wrote:
Hi Guy,
I believe they should be either "requester and provider" or "client and server", as they are well established names, and we do not have any reason to re-define them.
So, among the chocies, I choose [1].
Tomohiro
On Wed, 16 Dec 2009 17:31:58 +0000 Guy Roberts <Guy.Roberts@dante.net> 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
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
Dear *, My preference here would be: 2 What the client is requesting is a service. A granter Agent would grant (= evaluate policy and say yes or no) but the term does not necessarily tell that it also enables/enforces delivers the service. Implementer would not include handling the policy. So the most symmetric choice would be: Client - Agent <-> Service - Agent or Client - Agent <-> Server - Agent So, my preference is 2 and one can consider to change Requestor to CLient. Best regards, Cees. On Dec 16, 2009, at 6:31 PM, 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 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
All, I also would like to vote for # 2, but would not mind a change in name to "Client" rather than "requestor". Although we are focused ONLY on network services in this group, the terms would expand nicely to other services such as compute, storage, and instrumentation services, if successful. Wishing everyone a wonderful holiday season! Kind regards, Gigi Cees de Laat wrote:
Dear *,
My preference here would be: 2
What the client is requesting is a service. A granter Agent would grant (= evaluate policy and say yes or no) but the term does not necessarily tell that it also enables/enforces delivers the service. Implementer would not include handling the policy.
So the most symmetric choice would be:
Client - Agent <-> Service - Agent or Client - Agent <-> Server - Agent
So, my preference is 2 and one can consider to change Requestor to CLient.
Best regards, Cees.
On Dec 16, 2009, at 6:31 PM, 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 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
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg
Dear Guy, My choice is 1: {requester, provider} agents. On a second instance, I would choose 3, but in general I agree with Tomohiro. By the way, I will be on holidays from tomorrow to the 10th of Jan, with occasionally Internet access. Please, excuse my slow reaction to email. Regards, -- Joan A. García-Espín CTX, Fundació i2CAT El 16/12/2009 18:31, Guy Roberts escribió:
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
I vote for 1. Even though it may sound "traditional" I think it captures accurately the concept we are trying to present in the NSI. - Chin --On December 16, 2009 5:31:58 PM +0000 Guy Roberts <Guy.Roberts@dante.net> 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
Tel: +44 (0)1223 371 316
City House, 126-130 Hills Road
Cambridge, CB2 1PQ, UK
------------------------------------------------------------------------- -----------------------------------------
participants (9)
-
"Joan A. García-Espín" -
Cees de Laat -
Chin Guok -
Gigi Karmous-Edwards -
Guy Roberts -
Jeroen van der Ham -
Jerry Sobieski -
John Vollbrecht -
Tomohiro Kudoh