...
FIRST DRAFT SUBMITTED
--- start of Statement initial text section ---
A split resulting in IANA Functions being undertaken by more than one IANA Functions Operator would be likely to introduce instability. The ALAC therefore recommends that although no measures were introduced by the IANA Coordination Group to increase direct operational coordination between the Operational Communities, this should be promoted at Implementation Phase, with the aim to reduce the likelihood of a split in IANA Functions Operators. This direct operational coordination should take place as enhanced communication and continuous dialogue.
In the event of an Operational Community reaching the decision to replace the IANA Functions Operator, they should discuss their decision with other Operational Communities prior to proceeding forward, seeking all ways to keep all of the IANA functions undertaken by a single IANA Functions Operator.
--- end of Statement initial text section ---
This text section now forms a sub-part of the ALAC's Statement which will take the form of a set of responses to a Public Input Template.
Please look at the Public Input Template Provided by the ICG and which we have filled with the above text (plus other points) including feedback from the IANA Issues WG call calls on 26 & 27 Aug 2015:
Working Document in Word Format Version 3
Below: document in PDF format Version 3
| View file | ||||
|---|---|---|---|---|
|
It is expected that the ALAC input in the consultation will take the full form using the Template Provided. Please comment below on the template's contents or use the working group mailing list (if you are a member of the ALAC IANA Issues & ICANN Accountability Working group) using "track changes")