[IOT] IRP IOT comments review - discussion aids for one we will review this week

[Kavouss Arasteh]

Dear All, Is it right to count the replies in favour or against a given
raised issue.
Are these respondents representing the entire communities?.
Are their agreement or disagreement taking into account all pros and cones
in favour or against any period?.
Are we coming back to issues which were discussed for hours and hours.?
Are we obliged to follow the insistance of one or two individuals in the
group?
I suggest that we wind up the discussions at today's meeting and refer the
matter to CCWG Plenary in which the formal representatives of all
chartering organisations attend together with other participants
Regards
Kavouss .

2017-03-01 18:17 GMT+01:00 Malcolm Hutty <malcolm at linx.net>:

> On 27/02/2017 17:46, McAuley, David wrote:
> > Malcolm has kindly volunteered to lead us on the timing of claims issues
> > that several comments touched on, including his own.
>
> Dear all,
>
> I have read carefully through all the comments submitted on the timing
> issue, and attempted a more detailed analysis of the points raised than
> the staff excerpt.
>
> This pulls out both positions/recommendations and the major arguments
> raised to support those positions.
>
> In preparation for our call tomorrow, please find this review attached.
>
> Malcolm.
>
> --
>             Malcolm Hutty | tel: +44 20 7645 3523
>    Head of Public Affairs | Read the LINX Public Affairs blog
>  London Internet Exchange | http://publicaffairs.linx.net/
>
>                  London Internet Exchange Ltd
>            Monument Place, 24 Monument Street London EC3R 8AJ
>
>          Company Registered in England No. 3137929
>        Trinity Court, Trinity Street, Peterborough PE1 1DA
>
> _______________________________________________
> IOT mailing list
> IOT at icann.org
> https://mm.icann.org/mailman/listinfo/iot
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/iot/attachments/20170302/e5be193a/attachment.html>