[ALAC] Fwd: Invitation to an ICANN Advice kick-off workshop, Sunday, November 17 in Buenos Aires

Tue Nov 12 18:59:54 UTC 2013

I agree absolutely with Rinaldo on this...

CLO from my Mobile phone
On 12/11/2013 12:06 PM, "Rinalia Abdul Rahim" <rinalia.abdulrahim at gmail.com>
wrote:

> Olivier,
>
> Having dealt with the issues surrounding the adequacy of technical
> expertise involved in getting the Root Zone LGR procedure for IDNs off the
> ground, my position on this issue is as follows:
>
> 1. The ALAC should support the Bylaws changes that have been proposed to
> increase the availability of technical advice to the Board as well as the
> effectiveness of the Technical Liaison Group.  It is clear that the current
> modus operandi is not working and has not brought any benefit to ICANN in
> terms of advice.
>
> 2. The areas that are in perpetual need of advice centers on the DNS, both
> operationally and strategically.
> - Operationally, advice is continuously required on issues related to DNS
> security, stability and resiliency as they are affected by developments in
> ICANN's area of work such as TLD expansion, IDN TLD and upcoming Variant
> TLD delegation.
> - Strategically, advice/information is needed on how competition and
> complements to the DNS may be evolving as a continuous viability assessment
> for ICANN and its future.
>
> 3. Designated technical experts/groups should serve both the watchdog
> (proactive provision of advice) function as well as provide advice upon
> request and the request should be allowed to come not only from the Board,
> but also from the community.
>
> 4. The ALAC, as a community of Internet Users, is not positioned to offer
> technical advice, but our community would certainly be affected by
> technical issues and we certainly are a consumer of technical advice.  We
> therefore would want that advice to be available "on tap" as and when
> needed, in an easily understandable way, but also forthcoming proactively
> when there are issues of concern such as in the case of name and variant
> collisions.
>
> Best regards,
>
> Rinalia
>
>
> On Sun, Nov 10, 2013 at 5:30 PM, Olivier MJ Crepin-Leblond <ocl at gih.com
> >wrote:
>
> > Dear All,
> >
> > Please be so kind to find a message from Steve Crocker, Chair of the
> > ICANN Board, regarding a workshop to take place at the beginning of the
> > ICANN meeting in Buenos Aires. I am aware that the ALAC is already
> > meeting on Sunday morning. We may need to nominate someone to sit on
> > that workshop on behalf of the ALAC.
> > Kind regards,
> >
> > Olivier MJ Crépin-Leblond
> > ALAC Chair
> >
> >
> > -------- Original Message --------
> > Subject:        Invitation to an ICANN Advice kick-off workshop, Sunday,
> > November 17 in Buenos Aires
> > Date:   Sun, 10 Nov 2013 00:51:06 -0500
> > From:   Steve Crocker <steve at shinkuro.com>
> > CC:     Steve Crocker <steve at shinkuro.com>, Karine Perset
> > <karine.perset at icann.org>
> >
> >
> >
> > SO and AC chairs, TLG members, ISOC, senior ICANN staff, and ICANN Board,
> >
> > As many -- perhaps all -- of you have heard, we are revamping our
> > process of asking for, receiving, acknowledging and processing technical
> > advice.  Toward that end, we are having an informal workshop session
> > Sunday morning, Nov 17, from 10:30 to noon in the Martin Fierro room at
> > the ICANN meeting in Buenos Aires to kick-off this revised advice
> > process.  You are invited to send technical people from each of your
> > organizations.  (Many of you have already been alerted to this meeting
> > and have already made plans to come.  This message is intended to share
> > the same information with everyone.)
> >
> > Here's a bit of background.  Our bylaws specify the existence of two
> > technical Advisory Committees, RSSAC and SSAC, and the existence of a
> > Technical Liaison Group (TLG), whose members, ETSI, ITU-T, W3C and IETF,
> > each provide advice when asked.  There is also considerable expertise
> > within the other Advisory Committees and within the Supporting
> > Organizations.
> >
> > Until now, our process for asking for and receiving technical advice has
> > been a patchwork.  For example, SSAC regularly sends the Board
> > reports with advice.  ALAC has begun doing the same.  Three of the TLG
> > members have shared one seat on the Board but have not otherwise
> > provided specific advice.
> >
> > Our next step is to develop a regular dialog for technical advice,
> > starting with the workshop on Nov 17.  The workshop will focus on two
> > primary questions:
> >
> >   * What are the areas you think need technical advice?  This applies to
> >     both those who need advice and those who have the expertise to give
> >     us advice.
> >
> >   * Do you prefer to be asked for specific advice, prefer to offer
> >     advice on topics of your choice, or both?
> >
> > Please RSVP to Karine Perset, Director of Board Support,
> > karine.perset at icann.org <mailto:karine.perset at icann.org>, and please
> > come with suggestions for both specific technical issues and how to make
> > the process work best from your point of view.
> >
> > Thanks!
> >
> > Steve Crocker
> > Chair, ICANN Board of Directors
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > ALAC mailing list
> > ALAC at atlarge-lists.icann.org
> > https://atlarge-lists.icann.org/mailman/listinfo/alac
> >
> > At-Large Online: http://www.atlarge.icann.org
> > ALAC Working Wiki:
> >
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
> >
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki:
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>