Re: Changes we'd make to EPP, was Re: Domain check in draft-obispo-epp-idn-00.txt
Eric Brunner-Williams <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Organization | wampumpeag |
| Message-ID | <[email protected]> |
On 1/17/12 1:54 PM, Theo Kramer wrote: >> > Registry operators have got to get out of their vacuum mentality > Registry operator responsibilities include maintaining the db - can't see how this is 'vacuum mentality'. Michele has this correct. A registry contract holder exists in isolation. If the contract holder operates its own facilities based registry platform, and has no other tenants, and its registrar "arm" (prospective) only provides access to its own registry, then this dyad of registry operator and registrar operator exist in isolation, relative to the rest of the bells-and-whistles-EEP-verse. A registry platform operator with two or more tenants (or expectations along those lines) exists differently, and has a longer, or broader, view of the bells-and-whistles-EEP-verse and the associated policy space. The degenerate platform operator case is the tenant-only bells-and-policy aware, and otherwise indifferent, operator. A registrar meeting the access requirements of two or more policy distinct (some non-shared bells-and-whistles) registries has to take a very different view of features, changes, and predicable events. Those implementing multi-namespace services, whether server-side or client-side, necessarily take a different view from implementors and operators of mono-namespaces. The "vacuum mentality" is natural, and hard to fault, for each isolated island of misfit toys. Eric _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg