ICANN variant project update

[John C Klensin]

(top posting)

One important addition to Andrew's comments/pointer:

Unless this report is handled differently from the way many
reports within ICANN have been handled, an absence of comments
is likely to be construed as broad community approval and
support for whatever the report says.   If your reason for not
commenting is that you don't have the time and resources to deal
carefully with a 100+ page report with no executive summary (or
equivalent), I think it is probably reasonable and appropriate
to say that rather than being counted among those who have
reviewed it and approve.  Any such comments (as well as more
targeted reviews) should be submitted as Andrew suggests below;
comments along those lines to this list are likely to be
particularly useless.

    john

Disclaimer: ICANN has asked me to review this document and
several others associated with the project and is partially
supporting that work.  The comments above do not necessarily
reflect the views of ICANN, its staff, or anyone but myself.


--On Wednesday, January 04, 2012 17:41 -0500 Andrew Sullivan
<ajs at anvilwalrusden.com> wrote:

> Dear colleagues,
> 
> Apologies in advance for duplicate postings.  I didn't
> cross-post because of the difficulty that sometimes causes if
> people follow up on list to discuss issues.
> 
> Many of you will be aware that ICANN undertook the IDN Variant
> Issues Project last year.  (Full disclosure: I was involved in
> the project.) On 23 December 2011 the report was posted for
> public comment, and I realise that I have been remiss in
> drawing people's attention to it. This message is to fix that.
> 
> You can see the public announcement at
> http://www.icann.org/en/announcements/announcement-2-23dec11-e
> n.htm. That's also a good place to start in order to submit
> comments if you have them.  The pubic comment period closes at
> the end of January 2012.
> 
> ICANN is eagerly soliciting comments, and I hope that those of
> you interested in this topic will take the time to read the
> report and send your observations.  Having been a participant
> in this particular sausage-making exercise, I will say that I
> am sure there are things that need improvement, expansion, or
> more careful statement.  I'm aware that the report as it
> stands is rather long, and I appreciate the difficulty in
> finding the time to read, digest, and comment on all of it.
> Given the importance of the topic, however, I think it's worth
> it.
> 
> It might be tempting to discuss the document on this list, but
> I think it would be better to take such discussion either to
> the project list (which is still, as far as I know, open --
> vip at icann.org, list info at
> https://mm.icann.org/mailman/listinfo/vip) or to use the
> public-comment links in the announcement to send such
> comments.  That way, ICANN staff are sure to see the comments.
> 
> Thanks and best regards,
> 
> Andrew