|
Potential Registration Processes
Processes Steps to implement the four initial registration
processes are detailed below.
These processes serve as initial examples that consider a minimal and judicious
deployment of scarce resources to create a self-sustaining and scaleable At-Large
membership that meets the three minimal criteria of:
- Demonstrated Interest
- Authenticated Identity
- Financial Contribution
In the future, registration processes that also meet these three criteria may
be considered as local processes and communities develop and mature over time
(e.g. financial transaction mechanisms provided by local Internet communities.)
Initial Resources Required:
- ALSO Organizing Committee
- "ALSO founders group" of interested organizations and individuals willing
to pledge resources to establish the ALSO (e.g. starting with the 46 organizations
and the 2147 individuals that responded to the ALSC's surveys)
- At-Large Membership Registration Website with financial transaction capability
- Bank account for At-Large Membership
- Outreach Channels
- ICANN website
- TLD registries and registrars (voluntary)
- Local organizations interested in ICANN activities
- Local/regional Internet community events (RIPE, APRICOT, RIR meetings,
IETF, AFRINIC, INET etc.)
- Organizations that promote local language discussions
Implementation Steps:
Step 1: Establish ALSO Organizing Committee
Step 2: Establish Membership Registration Website with financial transaction
capability and discussion lists
Step 3: Establish Account for receiving At-Large Membership dues
Step 4: Work with "founders group" to develop, execute outreach plan
Step 5: Establish hyperlink from outreach channels to website
Step 6: Determine initial set of ICANN related mailing lists, specified organizations
and walk-in events for registration process.
Step 7: [see implementation table below]
Future Considerations:
Innovative Public Key Infrastructure and non-hardware based biometric authentication
mechanisms should continue to be tracked and investigated for suitability.
| Registration Infrastructure |
Demonstrated Interest |
Authentication |
Payment |
| TLD Registration Infrastructure |
- Holding Domain Name
- Filling in membership details via website or
- Automated capture of data through domain name registration process
(in long-term on voluntary basis)
|
- Initially administrative contact data matched with payment name data
- In long-term registrant data could be used and exchanged via EPP
and matched with 'whois' and payment data. [cctld's that don't currently
offer registrations for individuals may consider offering registrations
using DNS-based technologies for aggregating and exchanging registrant
data -- e.g. use in a non-resolvable domain like "at-large.invalid"
]
|
- Credit card or electronic funds transfer
|
| Website/ICANN-related mailing lists |
- Subscribing to ICANN-related mailing list
- Initially centrally hosted lists but can be distributed over time
as local language discussions groups evolve.
- Filling in Membership form via website.
|
- Mailing list data matched with data from payment mechanism.
|
- Initially through credit card or funds transfer until local organizational
support is developed.
- Once local organizational support is available sliding scale and
batched processing can be introduced.
|
|
ICANN-related events
- ICANN meetings and related events (RIPE, APRICOT, RIR meeting, IETF,
AFRINIC etc.)
|
- Attending ICANN event
- Filling in membership data from website
- Showing up to the event
|
- Providing proof of identity with accepted local proof of identity)
|
- Direct payment to staff (cash, credit card etc.)
- Easy to implement sliding scale payment and lower unit cost of clearing.
|
| Local Membership Organizations |
- Membership in select organizations that support ICANN's mission
- Filling in membership data via website or
- (long-term) automated exchange of membership data (e.g. XML)
|
- Membership data matched with payment name or
- Local organization authentication process (to be published)
|
- Payment through credit card or funds transfer until local organizational
support is developed/ integrated.
|
|
