Re: [council] Council Way Forward on Accountability Proposal

["James M. Bladel" <jbladel@xxxxxxxxxxx>]

Thanks Phil.  And my response certainly didn’t seem “timely,” as any work we do 
on this topic is already too late. :)

I agree that at least one intercessional meeting is necessary to get this done. 
 I’ll work towards drafting the Pre-Christmas letter.  The Subteam (and many 
thanks to you, Keith & Ed for volunteering so far) should meet early in the 
week of 3 JAN, with a Council-level discussion later that week (7 JAN as you 
suggested), with a drop-dead formal vote on the issue scheduled for 14 JAN.  I 
believe this last date is already on our calendars, but I will ask Glen to 
confirm.

Thanks again—

J.


From: Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Date: Sunday, December 20, 2015 at 11:21
To: "egmorris1@xxxxxxxxx<mailto:egmorris1@xxxxxxxxx>" 
<egmorris1@xxxxxxxxx<mailto:egmorris1@xxxxxxxxx>>, James Bladel 
<jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>, Keith Drazek 
<kdrazek@xxxxxxxxxxxx<mailto:kdrazek@xxxxxxxxxxxx>>
Cc: GNSO Council List <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: RE: [council] Council Way Forward on Accountability Proposal

James:

Thank you for your timely response to my inquiry.

I to would like to volunteer for the subteam. I’d also urge that we set times 
and dates for Council calls to consider the draft Resolution – perhaps January 
7th for preliminary discussion and, if necessary, January 14th for completing 
our work.

I look forward to working with other Council members on this important task.

Best to all,
Philip

Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

From: Edward Morris [mailto:egmorris1@xxxxxxxxx]
Sent: Sunday, December 20, 2015 11:43 AM
To: James M. Bladel; Drazek, Keith
Cc: Phil Corwin; council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>
Subject: Re: [council] Council Way Forward on Accountability Proposal

Hi James,

A good plan forward.

I would also like to volunteer to help.

Ed



________________________________
From: "Drazek, Keith" <kdrazek@xxxxxxxxxxxx<mailto:kdrazek@xxxxxxxxxxxx>>
Sent: Sunday, December 20, 2015 4:24 PM
To: "James M. Bladel" <jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>
Cc: "Phil Corwin" <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>, 
"council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>" 
<council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: Re: [council] Council Way Forward on Accountability Proposal

I think this make sense.

I volunteer to help.

Keith



On Dec 20, 2015, at 10:31 AM, James M. Bladel 
<jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>> wrote:

Thanks, Phil.  And generally, I believe your message below captures the 
challenges we (and other SO/ACs) face when asked to provide feedback in a 
compressed time frame, that also happens to collide with year-end holidays.  My 
availability is similar to yours, NamesCon included,  and from talking with 
Marika I think we should expect reduced support from Staff as well.

Given that our call on 17 DEC ran fairly long and you & several others had to 
drop, I wanted to share the way we left things with Thomas Rickert regarding 
GNSO feedback on the CCWG’s latest draft:

  — The SGs and Cs in the GNSO Community were working to analyze the report and 
prepare their comments by the close of the comment period.
  — The GNSO, as a Chartering Organization of the CCWG, was unlikely to submit 
any formal comments by 21 DEC.
  — Several SGs and Cs within the GNSO Community would, however, submit their 
comments by Monday.
  — The GNSO would provide feedback/approval to the final report upon 
completion in January.

I propose that we draft a letter to the CCWG next week, reiterating that we 
would not weigh in as an SO, but instead link to comments submitted by SGs and 
Cs (target: 24 DEC).  And next, that we form a subteam (me and any other 
volunteers) to review submitted comments and draft a formal GNSO position for 
review by the Council (target: 7 JAN).

Thoughts/comments/volunteers?

Thanks—

J.



From: <owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>> on 
behalf of Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Date: Friday, December 18, 2015 at 9:49
To: GNSO Council List <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: [council] Council Way Forward on Accountability Proposal

Fellow Councilors – and especially James, Heather, and Donna:

As I had to leave yesterday’s extended Council call a few minutes before it 
concluded, I am wondering whether any structure/schedule was agreed to for our 
consideration of the 3rd CCWG-ACCT Proposal in our role as a Chartering 
Organization?

Will we be scheduling additional calls to consider key aspects of the Proposal, 
especially those that elicit comments expressing concern or suggesting 
modifications? How will we handle drafting of a Resolution expressing Council’s 
view on behalf of the GNSO? And what is our target date for reaching a final 
decision?

For the record, I am available and willing to participate in calls next week 
(suggesting that any such call be after 12/21 to allow time for review of 
submitted comments) and during the first week of January.

>From December 26-January 3rd I shall be on vacation and intend to unplug from 
>the grid to the maximum extent possible.

>From January 9-13 I and 900-plus other members of the domain community will be 
>attending NamesCon and I will have limited availability to join any call. I am 
>departing the conference in the middle of its last day so that I can 
>participate in the tentatively scheduled January 14th Council call.

Thanks and best regards,
Philip


Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7227 / Virus Database: 4489/11213 - Release Date: 12/19/15