[NA-Discuss] Reporting on Durban meeting

Evan Leibovitch evan at telly.org
Mon Jul 22 20:08:05 UTC 2013


I did give an impromptu update on the week Friday during an ISOC conference
call (help every week for North American chapters). I was still in Durban
at the time, and the call quality is spotty. But, thanks to Joly, the
report was recorded and is available at http://isoc-ny.org/p2/5802

My take is that the meeting was fairly positive, from the end-user PoV, for
a couple of reasons:


   - Fadi Chehade is breaking off the gTLD operations -- including the new
   expansion program -- into a semi-independent division that will let the
   rest of ICANN be less distracted by the expansion in dealing with issues
   such as directory services, registrant privacy versus accountability, IPV6,
   DNSSEC, and similar matters. Quite telling is the fact that contractual
   compliance was not split off into the new division and will repoprt
   directly to Fadi. This should make for less future obfuscation but I will
   remain skeptical until proven otherwise.

   - On dotless domains and internally-conflicted domains (ie, .corp, .bar,
   .example), we scored what I would call a win. ALAC has been telling ICANN
   to heed its own SSAC advice (which is against deletaing such domains) but
   ICANN says the community is "split" and has ordered new business studies.
   During the ALAC meeting with the GAC, we asked the GAC to consider these
   issues seriously (it had not to that time been seen on the GAC's "radar",
   so to speak. The GAC communique issued at the end of the Durban meeting
   week was clear in supporting the community position backing the SSAC
   recommendations.
   -




On 22 July 2013 13:50, Dharma Dailey <dharma.dailey at gmail.com> wrote:

> Hi Kieren,
>
> I haven't forgotten your suggestion before the meeting for communicating
> back to the NARALO about the meeting.  I heartily agree that for those of
> us who can't regularly attend meetings, it's super helpful to get a birds
> eye view analysis from our reps on the ground. IMO, that's low hanging
> fruit on the engagement continuum. Before attending, I imagined that I
> might send communications on the fly, but the way the schedule is
> constructed doesn't lend itself to reflection and synthesis. For example,
> on Sunday we were in meetings for 13 + hours straight.  So, I quickly
> abandoned the idea of trying to report on the fly.  However, I did leave
> with 31 pages of typed notes which I will wheedle down to one woman's guess
> at what will be of most interest to you and the rest of NARALO.  One
> consequence of the travel and conference schedule was that I came back with
> a wicked cold. So, it may take me a few days to report back.
>
> Best Regards,
> Dharma Dailey
>
>
>
> On Jul 22, 2013, at 12:15 PM, "Garth Bruen" <gbruen at knujon.com> wrote:
>
> > Kieren,
> >
> > Thanks for the comment. Our elections are critical and getting them
> right is
> > even more important.
> >
> > As far as reporting goes I would like to draw your attention to this
> > document: http://www.knujon.com/icann_compliance_2012.pdf which shows
> that
> > ICANN's internal compliance function is essentially non-functional
> > regardless of recently published data by ICANN. This was a follow up to a
> > report sent directly to the CEO
> > (
> http://www.icann.org/en/news/correspondence/bruen-to-chehade-22apr13-en.pdf
> > ) which has not been responded to.
> >
> > ICANN is failing the public At-Large and won't discuss these core
> concerns,
> > has been completely silent on them. I think you can help by raising your
> > voice to ask about them as well from within our community.
> >
> > There is a very long report log here:
> >
> https://community.icann.org/display/atlarge/At-Large+Durban+Meeting+Reports+
> > Workspace which is being constantly updated by At-Large representatives,
> > even remote ones. Working groups regularly give reports on our monthly
> > calls. We'd love to have you come on and give your perspective, let me
> know.
> >
> > So, it's not really a question of reporting from At-Large, it's more of a
> > question of why we have to leave our families and travel thousands of
> miles
> > just to be ignored by ICANN. It's really not that much fun. If the
> problems
> > could be solved and questions answered, we wouldn't have to go at all.
> >
> > -Garth
> >
> >
> >
> > -----Original Message-----
> > From: na-discuss-bounces at atlarge-lists.icann.org
> > [mailto:na-discuss-bounces at atlarge-lists.icann.org] On Behalf Of Kieren
> > McCarthy
> > Sent: Sunday, July 21, 2013 11:09 PM
> > To: na-discuss at atlarge-lists.icann.org
> > Subject: Re: [NA-Discuss] VOTE RESULTS: 2013 NARALO Secretary Selection
> >
> > I wish as much time, energy and effort had gone into informing us about
> the
> > meeting you were paid as our representatives to attend last week in
> Durban
> > as has been out into bickering about voting procedures.
> >
> >
> > Kieren
> >
> >
> > [from mobile device]
> >
> > On Jul 21, 2013, at 7:19 PM, Alan Greenberg <alan.greenberg at mcgill.ca>
> > wrote:
> >
> >> Tom,
> >>
> >> I presume that by "incumbent" you mean people in office such as the ALAC
> > members or ALAC Chair (usually it is used referring to the person who is
> in
> > office but is in a contested election).
> >>
> >> I guess our experiences are different. Certainly someone who is part of
> a
> > current organization is familiar with the others who may be in a
> contested
> > election. But KNOW is definitely not the same as TRUST and not
> infrequently
> > KNOW is synonymous with wanting someone new. (And I am not implying
> anything
> > about the people in the current election).
> >>
> >> Alan
> >>
> >> At 21/07/2013 02:34 PM, toml at communisphere.com wrote:
> >>> Alan,
> >>>
> >>> What I am trying to say is that incumbents will better know and trust a
> > known player. Amopholy (sp?), might describe the human response that
> Option
> > 4 draws upon. There are both good and bad associated with this. Random is
> > life.
> >>>
> >>> Best,
> >>>
> >>> T9m Lowenhaupt
> >>
> >> ------
> >> NA-Discuss mailing list
> >> NA-Discuss at atlarge-lists.icann.org
> >> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
> >>
> >> Visit the NARALO online at http://www.naralo.org
> >> ------
> > ------
> > NA-Discuss mailing list
> > NA-Discuss at atlarge-lists.icann.org
> > https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
> >
> > Visit the NARALO online at http://www.naralo.org
> > ------
> >
> > ------
> > NA-Discuss mailing list
> > NA-Discuss at atlarge-lists.icann.org
> > https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
> >
> > Visit the NARALO online at http://www.naralo.org
> > ------
>
> ------
> NA-Discuss mailing list
> NA-Discuss at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
>
> Visit the NARALO online at http://www.naralo.org
> ------
>



-- 
Evan Leibovitch
Toronto Canada

Em: evan at telly dot org
Sk: evanleibovitch
Tw: el56


More information about the NA-Discuss mailing list