[discuss] structural separation example (was Re: Host country)
drc at virtualized.org
Wed Mar 19 00:03:22 UTC 2014
On Mar 18, 2014, at 9:44 AM, John Curran <jcurran at istaff.org> wrote:
> On Mar 18, 2014, at 5:04 PM, David Conrad <drc at virtualized.org> wrote:
>> I'm curious: given ARIN performs a registration function along with a policy definition function, do you believe there should be structural separation of those functions in ARIN/the RIRs?
> When we talk about the RIRs, Registry Policy Development is generally done by a
> community working group or body, and implementation/admin/operations handled by
> RIR staff.
Right. Do you see a significant difference between this and ICANN's coordination of names via gNSO/ccNSO Policy Development Processes with implementation/admin/operation done by ICANN as the IANA Functions Operator?
> Combine this with an accountable membership structure to help insure
> faithful implementation and administration, and it's not a bad system.
So, in your view, the existence of a "clear membership structure" is sufficient to remove the need for structural separation?
> I will note, however, that even accountability to membership doesn't help provide
> any protection against implementation that is favorable to "industry" (those who
> are direct member of the registry);
This would appear to suggest that structural separation is still necessary despite the RIRs having a clear membership structure.
> i.e. in a case where civil society were to
> successfully relate their (industry-adverse) needs during policy development such
> that they were indeed adequately incorporated into policy, there is still no clear
> recourse available against a less-than-diligent implementation, if the member-
> elected leadership fails to intervene.
Given the membership is drawn overwhelmingly (or even exclusively in practice) from the industry, wouldn't there be a natural tendency for the elected leadership to favor industry-preferred implementation?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the discuss