<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] FW: Letter from the GAC regarding IOC/RC Protections
- To: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Subject: Re: [council] FW: Letter from the GAC regarding IOC/RC Protections
- From: Maria Farrell <maria.farrell@xxxxxxxxx>
- Date: Thu, 29 Nov 2012 15:46:57 +0000
- Cc: John Berard <john@xxxxxxxxxxxxxxxxxxx>, Jonathan Robinson <jonathan.robinson@xxxxxxxxxxx>, "<council@xxxxxxxxxxxxxx>" <council@xxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8abbqKqAlziCGArsET0+qI5GfqegBJLCdEaKqZ4lHv8=; b=rNdNdy/rwSn/FID7j+sGg1oPvxuOav/O0W/ZnC1OsNJd+QjF1W7MPoPhTy2ljHkCF6 YPjg63TthkgXEfDJsBqsagQOxeONdDWZTKqRZI4ZVEZqHFJQI10VmAfY7nn3l6kSOD+L HUmVxaZm9w0OPqQ7lLH2FGEoM+Y+qfZiBMzJ8VRk+EDMRi8WeWkipzWum47++HI5AJfx cJIlWDjBL60Fk23gFB/Hhrd2Jf/xXnBRaM1jYs5fgURYJhloJHB4syoAEpQyJmqaQicc +9GM04bPcuwEUl86Bs0ztYuFTnFbGUZhHU/E5gXD7FBNiW4CxA9iuWACDLDpr6G5JdgX W2+Q==
- In-reply-to: <50B77C72.8090107@key-systems.net>
- List-id: council@xxxxxxxxxxxxxx
- References: <CCDBC434.2D4FC%gacsec@gac.icann.org> <003d01cdce18$4855ec60$d901c520$@ipracon.com> <C43F33D9-01D3-4F14-AB62-FE37414B8956@crediblecontext.com> <50B77C72.8090107@key-systems.net>
- Sender: owner-council@xxxxxxxxxxxxxx
John raises some important points in relation to the GAC's role vis a vis
the Council. I agree that this letter highlights the need for the GAC to
appoint a liaison.
The GAC, which of course advises the Board, has asked us for the
'rationale' for a Council decision. I would like to be helpful, but aside
from directing them to the relevant motion and its attached 'whereas'
sequence, what else is there?
As to the GAC's opinion that this relates to merely an implementation
issue, we have all seen in the last few weeks that 'implementation issues'
can be policy issues, depending on the strength of one's point of view and
wish to see that prevail.
As a practical matter regarding the rationale of the group of two dozen
people who voted, I don't see what we can provide, other than a link to the
motion(s) in question. Am I missing something?
Maria
On 29 November 2012 15:17, Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>wrote:
> I also agree with Jeff that defining the two terms aside from the issues
> would be necessary. I would however like to add that "implementation" of
> existing policy may by the way of the interpretation have such a
> significant impact on stakeholders that community consensus of the form of
> implementation may become necessary.
>
> Best,
>
> Volker
>
>
> Jonathan,
>
> First, this letter makes me more certain we should be emphatic about
> getting a GAC observer on the Council.
>
> Second, I have heard Jeff Neuman's comment on clarifying what is policy
> and what is implementation and I agree.
>
> Third, until the GNSO structure changes, the GAC advises the Board and
> if there are policy questions, the Board engages the Council. Where is the
> Board on this direct advice to the Council?
>
> Four, look forward to the next Council meeting!
>
> Cheers,
>
> Berard
>
> Sent from my iPhone
>
> On Nov 29, 2012, at 4:59 AM, "Jonathan Robinson" <
> jonathan.robinson@xxxxxxxxxxx> wrote:
>
> All,****
>
> ** **
>
> FYI. Please see the attached letter received from the GAC last night my
> time.****
>
> ** **
>
> Jonathan****
>
> ** **
>
> *From:* GAC Secretariat [mailto:gacsec@xxxxxxxxxxxxx<gacsec@xxxxxxxxxxxxx>]
>
> *Sent:* 28 November 2012 21:38
> *To:* jonathan.robinson@xxxxxxxxxxx
> *Cc:* Steve Crocker; Fadi Chehade; Heather Dryden; Maria Häll;
> alice@xxxxxxx; Choon Sai LIM (IDA)
> *Subject:* Letter from the GAC regarding IOC/RC Protections****
>
> ** **
>
> Sent on behalf of Heather Dryden, GAC Chair ****
>
> ** **
>
> Dear Jonathan, ****
>
> ** **
>
> Attached please find a letter from the GAC regarding IOC and Red Cross/Red
> Crescent protections. ****
>
> ** **
>
> Best regards, ****
>
> ** **
>
> Jeannie Ellers ****
>
> ** **
>
> Jeannie Ellers
> Manager, GAC Coordination
> Internet Corporation for Assigned Names and Numbers
> 1101 New York Avenue NW, Suite 930****
>
> Washington, DC 20005
> Ph. +1 202 570 7135
> M. +1 310 302 7552****
>
> <GAC_GNSOCouncil_20121128.pdf>
>
>
>
> --
> Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
>
> Mit freundlichen Grüßen,
>
> Volker A. Greimann
> - Rechtsabteilung -
>
> Key-Systems GmbH
> Im Oberen Werk 1
> 66386 St. Ingbert
> Tel.: +49 (0) 6894 - 9396 901
> Fax.: +49 (0) 6894 - 9396 851
> Email: vgreimann@xxxxxxxxxxxxxxx
>
> Web: www.key-systems.net / www.RRPproxy.netwww.domaindiscount24.com /
> www.BrandShelter.com
>
> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei
> Facebook:www.facebook.com/KeySystemswww.twitter.com/key_systems
>
> Geschäftsführer: Alexander Siffrin
> Handelsregister Nr.: HR B 18835 - Saarbruecken
> Umsatzsteuer ID.: DE211006534
>
> Member of the KEYDRIVE GROUPwww.keydrive.lu
>
> Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
> Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
> Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese
> Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per
> E-Mail oder telefonisch in Verbindung zu setzen.
>
> --------------------------------------------
>
> Should you have any further questions, please do not hesitate to contact us.
>
> Best regards,
>
> Volker A. Greimann
> - legal department -
>
> Key-Systems GmbH
> Im Oberen Werk 1
> 66386 St. Ingbert
> Tel.: +49 (0) 6894 - 9396 901
> Fax.: +49 (0) 6894 - 9396 851
> Email: vgreimann@xxxxxxxxxxxxxxx
>
> Web: www.key-systems.net / www.RRPproxy.netwww.domaindiscount24.com /
> www.BrandShelter.com
>
> Follow us on Twitter or join our fan community on Facebook and stay
> updated:www.facebook.com/KeySystemswww.twitter.com/key_systems
>
> CEO: Alexander Siffrin
> Registration No.: HR B 18835 - Saarbruecken
> V.A.T. ID.: DE211006534
>
> Member of the KEYDRIVE GROUPwww.keydrive.lu
>
> This e-mail and its attachments is intended only for the person to whom it is
> addressed. Furthermore it is not permitted to publish any content of this
> email. You must not use, disclose, copy, print or rely on this e-mail. If an
> addressing or transmission error has misdirected this e-mail, kindly notify
> the author by replying to this e-mail or contacting us by telephone.
>
>
>
>
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|