[Internal-cg] Community Comments Handling Process ..
kavouss.arasteh at gmail.com
Mon Feb 2 15:17:44 UTC 2015
Tks for confirmation.
One possible way would be that we send the following to the concerned
ICG has received information from a member of community that " insert the
You are kindly request to carefully examine the matter and provide
clarifications/ comments/counter argument to the submitting entity and
forward a copy to ICG for any required action, as appropriate
There may be different language instead
2015-02-02 16:00 GMT+01:00 Daniel Karrenberg <daniel.karrenberg at ripe.net>:
> i fully agree with that. and i have explicitly said that at least two
> times. again: i absolutely agree that we can decide to ask an explicit
> question to an oc using our normal process. it requires an icg member to
> suggest it and the icg to decide to do it using our normal process.
> Sent from a hand held device.
> On 02.02.2015, at 13:30, Kavouss Arasteh <kavouss.arasteh at gmail.com>
> Dear Daniel,
> Dear All,
> Yes we are not appeal body, but we represent the 13 ICANN community and
> our Charter allow us to request the Operational Community to duly and
> carefully examine the " concerns " or " Comments " received and provide
> answers7 clarification or justification for action was taken and make
> remedial action ,if and where required.
> Kavouss t
> 2015-02-02 8:59 GMT+01:00 Daniel Karrenberg <daniel.karrenberg at ripe.net>:
>> On 1.02.15 19:30 , Milton L Mueller wrote:
>> you understood my points completely. I am confident that the OCs, having
>> spent considerable effort and process to create their proposals, will
>> publicly respond to substantial comments.
>> Yes we are dealing with people. And just because we are dealing with
>> people we have to be careful not to create the impression that the ICG is
>> an appeals body with an obligation for due process and an obligation to
>> respond to each and every comment.
>> Internal-cg mailing list
>> Internal-cg at icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Internal-cg