Changes

Line 127: Line 127:  
* leverage existing and proven ICANN design patterns already available for use by the [[ICANN Community]] (such as the naming services portal, operating on salesforce), existing technology stacks (ICANN Account operating on okta identity platform), and  
 
* leverage existing and proven ICANN design patterns already available for use by the [[ICANN Community]] (such as the naming services portal, operating on salesforce), existing technology stacks (ICANN Account operating on okta identity platform), and  
 
* rely on in-house expertise and users.
 
* rely on in-house expertise and users.
The Whois disclosure system needs to be written but will be a traffic cop in the middle. The latest version of this proof of concept or minimal viable product proposal involves the removal of authentication. What's left are accreditation and access.<ref>[https://74.schedule.icann.org/meetings/ GNSO:EPDP Phase 2 Session, ICANN 74]
+
The Whois disclosure system needs to be written but will be a traffic cop in the middle. The latest version of this proof of concept or minimal viable product proposal involves the removal of authentication. What's left are accreditation and access.<ref>[https://74.schedule.icann.org/meetings/ GNSO:EPDP Phase 2 Session, ICANN 74]</ref>
 +
[[Milton Mueller]] expressed concerns over a temporary solution becoming a permanent default, from which any further improvements are
 +
made, and the absence of a billing function. There may be a very different level of demand if ICANN has to impose some costs on the people making the request. The org could bundle request subscriptions and say give us some fee, like $100, and you get 100 requests or 500 requests for the next two months or something.<ref>[https://74.schedule.icann.org/meetings/ GNSO:EPDP Phase 2 Session, ICANN 74]</ref>
    
==References==
 
==References==
Bureaucrats, Check users, lookupuser, Administrators, translator
14,952

edits