ICANN/GNSO GNSO Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] Re: 2 questions about our Council agenda

  • To: stephane.vangelder@xxxxxxxxx, john@xxxxxxxxxxxxxxxxxxx
  • Subject: Re: [council] Re: 2 questions about our Council agenda
  • From: John Berard <johnberard@xxxxxxx>
  • Date: Tue, 10 Apr 2012 13:45:15 -0400 (EDT)
  • Cc: Jeff.Neuman@xxxxxxxxxx, KnobenW@xxxxxxxxxx, council@xxxxxxxxxxxxxx
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1334079915; bh=KzW8OgXagTGV1lZLt/fngNxIxslFu+OFqWUniWTDnls=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=sTsGEjPySMruuFgWaQD9geP39oW5eyef8gxaq33kyjG7qYURlwxH7a+w25ucdRUL0 I+biyFPEG7iewHcnIHyn8FwmvQSdxN1UAKgUFlhmg7FCfSUWDByCvlINJuoJlOqRwk cSc4giXrd6Xmwb/a9GQafqcJCyX9styEgXLSJI3c=
  • In-reply-to: <257F49F5-04AE-47F1-87F5-0C6415026F21@indom.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <20120410101430.a9a203d782c20324abd21efa41e2a5a6.46aa4b4c59.wbe@email14.secureserver.net> <257F49F5-04AE-47F1-87F5-0C6415026F21@indom.com>
  • Sender: owner-council@xxxxxxxxxxxxxx

 Of course.  I am in a fog



-----Original Message-----
From: Stéphane Van Gelder <stephane.vangelder@xxxxxxxxx>
To: john <john@xxxxxxxxxxxxxxxxxxx>
Cc: Neuman Jeff <Jeff.Neuman@xxxxxxxxxx>; Wolf-Ulrich Knoben 
<KnobenW@xxxxxxxxxx>; council@xxxxxxxxxxxxxx GNSO <council@xxxxxxxxxxxxxx>
Sent: Tue, Apr 10, 2012 10:24 am
Subject: Re: [council] Re: 2 questions about our Council agenda

Vice Chair


Le 10 avr. 2012 à 19:14, <john@xxxxxxxxxxxxxxxxxxx> a écrit :


In this context, what is a VC?

John Berard
Credible Context
58 West Portal Avenue, #291
San Francisco, CA 94127
m: 415.845.4388

-------- Original Message --------
Subject: [council] Re: 2 questions about our Council agenda
From: Stéphane_Van_Gelder <stephane.vangelder@xxxxxxxxx>
Date: Tue, April 10, 2012 8:51 am
To: <john@xxxxxxxxxxxxxxxxxxx>
Cc: Neuman Jeff <Jeff.Neuman@xxxxxxxxxx>,        Wolf-Ulrich Knoben
<KnobenW@xxxxxxxxxx>,        "<council@xxxxxxxxxxxxxx> GNSO"


Thanks for your questions. I am copying the Council list.

On item 3, that is a discussion for the meeting itself. This agenda item stems 
from the Council's decision, taken in CR, to delay on this PDP. We are acting 
on that decision.

On item 5, this was proposed by one of the VCs. It is a question being asked. 
Once again, I would suggest that we not preempt the very discussion we are 
trying to have by starting it now, but instead have it during the call. If 
there is no topic here, then that is what our minutes for the meeting will say 
and we can all move on. But the Council may welcome the chance to discuss this.



Le 10 avr. 2012 à 17:40, <john@xxxxxxxxxxxxxxxxxxx> a écrit :


With regard to:

Item 3: Thick Whois Policy Development Process (PDP)10 minutes)
 The GNSO Council initiated a PDP at its meeting on 14 March. However, 
considering other circumstances, the GNSO Council is of the view that the next 
steps in this PDP (formation of a drafting team to develop a charter) is not 
timely and that it may be preferable to delay until the .COM negotiations have 
been completed. This motion provides for that delay. 

The BC argued that the motion would muddy the waters with regard to the RAA 
negotiations, but we were unconvincing.  How does this conflate with the .com 
contract now?  When did that happen?

With regard to:

Item 5: GNSO Council comment on .COM contract renewal (10 minutes) 

In its announcement on the .COM contract renewal dated 27 March 2012 
(http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm) ICANN 
states that the question of transitioning a large existing registry to thick 
WHOIS has been recognised by the GNSO as raising operational and other issues 
that require further discussion and consideration 

 So Council discussions are being cited as the rationale for the fact that the 
2012 .COM contract contains no obligations on the registry operator to switch 
to a thick WHOIS format. Considering the debate that went on at Council level 
on this issue, the Council may deem this to be a misrepresentation of the 
truth. If so, the Council may then wish to draft a statement outlining this and 
direct the Chair to send it to the Board. 

How did this get on the agenda?  Are we responding in a fit of pique?  It seems 
we are leapfrogging the public comment period.


John Berard
Credible Context
58 West Portal Avenue, #291
San Francisco, CA 94127
m: 415.845.4388


<<< Chronological Index >>>    <<< Thread Index >>>