Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Be more specific with common terms or leave them out (#59)

From: adammontville <[email-masked]>
Date: Mon, 31 Jul 2017 13:46:23 -0700

In some cases we are using common terms for SACM-specific purposes. `Proxy` is one example, `Provider` is another. There are certainly others we might consider (this is somewhat related to #58 ). 

When we do need to be SACM-specific, I would encourage the terms to be named in a SACM-specific manner. Take `Proxy` for example, which has the following definition: `A proxy is a specific controller type that provides data plane and control plane functions, information, or services on behalf of another component, which is not directly participating in the SACM architecture.`. 

Because I don't think we mean "proxy" as in "the authority to represent someone else", I think we mean something like this: `a server (a computer system or an application) that acts as an intermediary for requests from clients seeking resources from other servers` (see https://en.wikipedia.org/wiki/Proxy_server). 

If we want this to be SACM-specific, then I would suggest:

`SACM Proxy Controller: A SACM Controller that provides [SACM] data plane and [SACM] control plane functions, information, or services on behalf of another component not directly participating in the SACM architecture.`

Or something like that. In this particular example, I'm not sure it's necessary to define SACM Proxy Controller. It may be enough just to state in the appropriate documents that a SACM Controller may function as a proxy server for some other component in the enterprise.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/59