Substitute enterprise boundary with ecosystem boundary

[adammontville]

Wherever the draft talks about the enterprise boundary, we should update the term to be the ecosystem boundary.

[adammontville]

I received an off-list suggestion to use term responsibility domain instead of ecosystem boundary. The argument put forth is essentially that the term ecosystem isn’t really used to describe architectural boundaries.

I think what we were going after in making this change is to explicitly recognize that the computing resources used by an enterprise today may include endpoints (in the traditional sense), and other computing resources such as non-enterprise devices (BYOD), and resources that are part of a shared responsibility model.

1. Is the reasoning described above correct?
2. Does the term responsibility domain capture this notion?

[sacm]

Hi Adam, My two cents. The noun/adjective "Responsibility" does nothing for me to disambiguate "Domain". And the phrase certainly does not leave any impression of "Boundary" (which seems to be the important point here). Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Co-Chair - TCG Metadata Access Protocol SG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434

…

On Tue, Oct 8, 2019 at 6:01 PM adammontville ***@***.***> wrote: I received an off-list suggestion to use term *responsibility domain* instead of *ecosystem boundary*. The argument put forth is essentially that the term ecosystem isn’t really used to describe architectural boundaries. I think what we were going after in making this change is to explicitly recognize that the computing resources used by an enterprise today may include endpoints (in the traditional sense), and other computing resources such as non-enterprise devices (BYOD), and resources that are part of a shared responsibility model. 1. Is the reasoning described above correct? 2. Does the term *responsibility domain* capture this notion? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=ACTMJUI72K6JV7Q747EFQLLQNT7MXA5CNFSM4I6JZ3WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVYGDI#issuecomment-539722509>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACTMJULNJHHBCC72I52QUOLQNT7MXANCNFSM4I6JZ3WA> . _______________________________________________ sacm mailing list ***@***.*** https://www.ietf.org/mailman/listinfo/sacm

[adammontville]

Thanks, Ira. How about "Boundary of Responsibility" or something similar to that? Or, we can simply leave it at "enterprise boundary".

[sacm]

Hi Adam, Yes, I like "Boundary of Responsibility". Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Co-Chair - TCG Metadata Access Protocol SG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434

…

On Thu, Oct 10, 2019 at 11:30 AM adammontville ***@***.***> wrote: Thanks, Ira. How about "Boundary of Responsibility" or something similar to that? Or, we can simply leave it at "enterprise boundary". — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=ACTMJUPDM2F6IYS4CTTFEXLQN5DA7A5CNFSM4I6JZ3WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA4YWKQ#issuecomment-540642090>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTMJUIXCQ5XDJLY5ZS2JJTQN5DA7ANCNFSM4I6JZ3WA> . _______________________________________________ sacm mailing list ***@***.*** https://www.ietf.org/mailman/listinfo/sacm

[adammontville]

Any other comments on "boundary of responsibility"? If there are no objections, we'll move forward with this term.

[wmunyan]

Well, no other responses. "Boundary of Responsibility" it is - changed for -04