Proposed GNSO Council Agenda 13 August 2009
Proposed GNSO Council Agenda 13 August 2009 https://st.icann.org/gnso-council/index.cgi?agenda_13_aug_2009 http://gnso.icann.org/meetings/agenda-13aug09.shtml This agenda was established according to the Rules of Procedure for the GNSO Council Coordinated Universal Time 13:00 UTC - see below for local times (06:00 Los Angeles, 09:00 Washington DC, 14:00 London, 15:00 Brussels, 23:00 Melbourne) Avri Doria will be chairing the GNSO Council meeting Scheduled time for meeting 120 mins. Dial-in numbers sent individually to Council members. Item 0: Roll call of Council members Item 1: Update any statements of interest Avri Doria's updated statement of interest Item 2: Review/amend agenda Item 3: Approve GNSO Council minutes (Items 1-3 15 mins) GNSO Council minutes 23 July 2009 Item 4: Fast Flux Hosting Final Report (30 mins) Presentation by WG chair- James Bladel Item 5: Joint ccNSO-GNSO IDN Working Group (JIG) call for participants (15 mins) Draft Charter http://gnso.icann.org/drafts/jig-charter-21jul09.pdf Item 6: Discussion of Remaining GNSO Council Transition Matters Necessary To Seat New Council In Seoul (15 mins) --- Review timetables, note outstanding items to be resolved, --- agree to assignments and deliverables Item 7: Schedule for Seoul (15 mins) Item 8: Status Updates (30 mins) 8. 1. Board Update - Denise Michel Preliminary report 8. 2. ccNSO Liaison update - Olga Cavalli 8. 3. Geographical Region WG update - Olga Cavalli/Zahid Jamil Public Comment: Geographic Regions Initial Report 8. 4. Joint AC/SO Efforts 8. 4. 1. Prospective GNSO-SSAC work 8. 4. 2. RAA with ALAC 8. 5 Policy Items 8. 5. 1. Working Groups 8. 5. 1. 1. Registration Abuse Policies Working Group (RAPWG) - Mike Rodenbaugh 8. 5. 1. 2. Post-Expiry Domain Name Recovery Working Group - Tim Ruiz 8. 5. 1. 3. Inter-Registrar Transfer Policy Part B Working Group - Secretariat 8. 6. Drafting Teams 8. 6. 1. Travel Policy Drafting Team - Olga Cavalli 8. 6. 2. IDNG Working Group update - IDNG Draft Charter- Edmon Chung 8. 7. GNSO Improvement Work Teams 8. 7. 1. Policy Process Steering Committee (PPSC) Policy Development Process (PDP) work team (WT) - Marika Konings 8. 7. 2. PPSC Working Group work team WGWT - Marika Konings 8. 7. 3. Operations Steering Committee (OSC) Communications coordination work team - Julie Hedlund 8. 7. 4. OSC Constituency operations work team - Julie Hedlund 8. 7. 5. OSC GNSO Council operations work team - Julie Hedlund 8. 8. Restructuring effort - Rob Hoggarth 8. 8. 1. Status of By-Law amendments - Margie Milam ICANN Bylaws Amendments Related to GNSO Restructuring: Complete Side-By-Side Comparison [Version: 31 July 2009] http://www.icann.org/en/general/proposed-gnso-council-bylaw-amendments-compa... 8. 8. 2. Stakeholder Group Charters - Rob Hoggarth 8. 8. 3. Constituency Charters - Rob Hoggarth Item 9: AOB - Action Items (06:00 Los Angeles, 09:00 Washington DC, 14:00 London, 15:00 Brussels, 23:00 Melbourne) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 13:00 ---------------------------------------------------------------------------- California, USA (PDT) UTC-7+1DST 06:00 New York/Washington DC, USA (EDT) UTC-4+1DST 09:00 Buenos Aires, Argentina UTC-3+0DST 10:00 Rio de Janeiro, Brazil UTC-3+0DST 10:00 London, United Kingdom (BST) UTC+1DST 14:00 Brussels, Belgium (CEST) UTC+1+1DST 15:00 Paris, France (CEST) UTC+1+1DST 15:00 Barcelona, Spain (CEST) UTC+1+1DST 15:00 Karachi, Pakistan UTC+5+0DST 19:00 Hong Kong, China UTC+8+0DST 21:00 Singapore, Singapore UTC+8+0DST 21:00 Melbourne, Australia (EST) UTC+10+0DST 23:00 ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2009, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Please let me know if you have any questions. Thank you. Glen de Saint Géry GNSO Secretariat gnso.secretariat@gnso.icann.org http://gnso.icann.org
In the interest of time could we pursue the suggestion of Chuck (not for the first time) that basic status reports are provided in advance of the meeting in writing and subject to a Q and A at the meeting if any one has a question? This would give time for the more pertinent updates on structure and charters which will need to be discussed. Philip
Hi, While I appreciate the value of written status updates and agree that it would be good to have them I wonder whether they actually will save time. For people who read them, it will give them a chance to think through the status and have better questions - and this is a good effect. Yet there will always be people who did not have a chance to read them, so I believe we will still need to ask for a verbal report in most cases. a. On 10 Aug 2009, at 07:57, Philip Sheppard wrote:
In the interest of time could we pursue the suggestion of Chuck (not for the first time) that basic status reports are provided in advance of the meeting in writing and subject to a Q and A at the meeting if any one has a question?
This would give time for the more pertinent updates on structure and charters which will need to be discussed.
Philip
I like Philip (or is it Chuck's) suggestion. I would much prefer to have these status updates in advance and plan for shorter Council meetings as a consequence. It is always my feeling, when listening through these status updates during our meetings, that the people giving them are Reading from a written text anyway. If that impression is correct, then surely it would be no extra trouble to send to text to the Council list ahead of the meeting. I for one would find it easier to assimilate these status reports if they were sent as text rather than read aloud. And if that can mean a 1:30 hour long meeting instead of a 2 hour meeting, all those involved would probably gain. Thanks, Stéphane Envoyé de mon iPhone Le 10 août 2009 à 14:11, Avri Doria <avri@psg.com> a écrit :
Hi,
While I appreciate the value of written status updates and agree that it would be good to have them I wonder whether they actually will save time. For people who read them, it will give them a chance to think through the status and have better questions - and this is a good effect. Yet there will always be people who did not have a chance to read them, so I believe we will still need to ask for a verbal report in most cases.
a.
On 10 Aug 2009, at 07:57, Philip Sheppard wrote:
In the interest of time could we pursue the suggestion of Chuck (not for the first time) that basic status reports are provided in advance of the meeting in writing and subject to a Q and A at the meeting if any one has a question?
This would give time for the more pertinent updates on structure and charters which will need to be discussed.
Philip
Agree 100% with Stéphane, Philip and Chuck. K -----Original Message----- From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Stephvg2 Sent: Monday, August 10, 2009 9:46 AM To: Avri Doria Cc: Council GNSO Subject: Re: [council] Proposed GNSO Council Agenda 13 August 2009 I like Philip (or is it Chuck's) suggestion. I would much prefer to have these status updates in advance and plan for shorter Council meetings as a consequence. It is always my feeling, when listening through these status updates during our meetings, that the people giving them are Reading from a written text anyway. If that impression is correct, then surely it would be no extra trouble to send to text to the Council list ahead of the meeting. I for one would find it easier to assimilate these status reports if they were sent as text rather than read aloud. And if that can mean a 1:30 hour long meeting instead of a 2 hour meeting, all those involved would probably gain. Thanks, Stéphane Envoyé de mon iPhone Le 10 août 2009 à 14:11, Avri Doria <avri@psg.com> a écrit :
Hi,
While I appreciate the value of written status updates and agree that it would be good to have them I wonder whether they actually will save time. For people who read them, it will give them a chance to think through the status and have better questions - and this is a good effect. Yet there will always be people who did not have a chance to read them, so I believe we will still need to ask for a verbal report in most cases.
a.
On 10 Aug 2009, at 07:57, Philip Sheppard wrote:
In the interest of time could we pursue the suggestion of Chuck (not for the first time) that basic status reports are provided in advance of the meeting in writing and subject to a Q and A at the meeting if any one has a question?
This would give time for the more pertinent updates on structure and charters which will need to be discussed.
Philip
Hi, Let's assume we have consensus on instituting a rule of requiring those doing a status report to submit it in advance. How long before the meeting should they be required to do so? And does the same rule apply to Council members making report as liaisons and Staff members making reports? Also what do we do if someone does not submit a report - allow them to give it orally or just skip the report? As I said I favor getting the written reports as well (though some of the responses made it appear as if I was not clear about that). I just don't believe that shortening meetings wiil be the result. but time will tell. BTW, Not sure what the following meant.
On 10 Aug 2009, at 09:32, Philip Sheppard wrote:
In which case lets take status reform first.
Is this an additional agenda item (an agenda item about how we do status) or a request to switch something around in the agenda - i.e. status of the GNSO reform. a. On 10 Aug 2009, at 09:49, Rosette, Kristina wrote:
Agree 100% with Stéphane, Philip and Chuck.
K
Avri, BTW, Not sure what the following meant.
On 10 Aug 2009, at 09:32, Philip Sheppard wrote:
In which case lets take status reform first.
Is this an additional agenda item (an agenda item about how we do status) or a request to switch something around in the agenda - i.e. status of the GNSO reform. It is the latter.
Lets keep it simple. Q: How long before the meeting should they be required to do so? A: Target 7 days, latest 24 hours. Q: And does the same rule apply to Council members making report as liaisons and Staff members making reports? A: Yes Q: Also what do we do if someone does not submit a report - allow them to give it orally or just skip the report? A: If staff, a hanging. If volunteers, a round of drinks for the entire Council. Ok ...a sensible answer .... A: Skip the report if not essential that day and allow it to be submitted in the next 7 days. Philip
Philip's answers sound reasonable to me. Chuck
-----Original Message----- From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Philip Sheppard Sent: Monday, August 10, 2009 10:18 AM To: 'Council GNSO' Subject: RE: [council] Proposed GNSO Council Agenda 13 August 2009
Lets keep it simple.
Q: How long before the meeting should they be required to do so? A: Target 7 days, latest 24 hours.
Q: And does the same rule apply to Council members making report as liaisons and Staff members making reports? A: Yes
Q: Also what do we do if someone does not submit a report - allow them to give it orally or just skip the report? A: If staff, a hanging. If volunteers, a round of drinks for the entire Council.
Ok ...a sensible answer .... A: Skip the report if not essential that day and allow it to be submitted in the next 7 days.
Philip
Just for clarification Chuck, the hanging or the round of drinks? RobH On 8/10/09 10:28 AM, "Chuck Gomes" <cgomes@verisign.com> wrote: Philip's answers sound reasonable to me. Chuck
-----Original Message----- From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Philip Sheppard Sent: Monday, August 10, 2009 10:18 AM To: 'Council GNSO' Subject: RE: [council] Proposed GNSO Council Agenda 13 August 2009
Lets keep it simple.
Q: How long before the meeting should they be required to do so? A: Target 7 days, latest 24 hours.
Q: And does the same rule apply to Council members making report as liaisons and Staff members making reports? A: Yes
Q: Also what do we do if someone does not submit a report - allow them to give it orally or just skip the report? A: If staff, a hanging. If volunteers, a round of drinks for the entire Council.
Ok ...a sensible answer .... A: Skip the report if not essential that day and allow it to be submitted in the next 7 days.
Philip
I'll leave that one alone Rob. :) I took that in gest. Chuck ________________________________ From: Robert Hoggarth [mailto:robert.hoggarth@icann.org] Sent: Monday, August 10, 2009 11:03 AM To: Gomes, Chuck; Philip Sheppard; Council GNSO Subject: Re: [council] Proposed GNSO Council Agenda 13 August 2009 Just for clarification Chuck, the hanging or the round of drinks? RobH On 8/10/09 10:28 AM, "Chuck Gomes" <cgomes@verisign.com> wrote: Philip's answers sound reasonable to me. Chuck > -----Original Message----- > From: owner-council@gnso.icann.org > [mailto:owner-council@gnso.icann.org] On Behalf Of Philip Sheppard > Sent: Monday, August 10, 2009 10:18 AM > To: 'Council GNSO' > Subject: RE: [council] Proposed GNSO Council Agenda 13 August 2009 > > > > Lets keep it simple. > > Q: How long before the meeting should they be required to do so? > A: Target 7 days, latest 24 hours. > > Q: And does the same rule apply to Council members making > report as liaisons and Staff members making reports? > A: Yes > > Q: Also what do we do if someone does not submit a report - > allow them to give it orally or just skip the report? > A: If staff, a hanging. If volunteers, a round of drinks for > the entire Council. > > Ok ...a sensible answer .... > A: Skip the report if not essential that day and allow it to > be submitted in the next 7 days. > > Philip > >
... as it was intended, Chuck ... RobH On 8/10/09 11:34 AM, "Chuck Gomes" <cgomes@verisign.com> wrote: I'll leave that one alone Rob. :) I took that in gest. Chuck ________________________________ From: Robert Hoggarth [mailto:robert.hoggarth@icann.org] Sent: Monday, August 10, 2009 11:03 AM To: Gomes, Chuck; Philip Sheppard; Council GNSO Subject: Re: [council] Proposed GNSO Council Agenda 13 August 2009 Just for clarification Chuck, the hanging or the round of drinks? RobH On 8/10/09 10:28 AM, "Chuck Gomes" <cgomes@verisign.com> wrote: Philip's answers sound reasonable to me. Chuck
-----Original Message----- From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Philip Sheppard Sent: Monday, August 10, 2009 10:18 AM To: 'Council GNSO' Subject: RE: [council] Proposed GNSO Council Agenda 13 August 2009
Lets keep it simple.
Q: How long before the meeting should they be required to do so? A: Target 7 days, latest 24 hours.
Q: And does the same rule apply to Council members making report as liaisons and Staff members making reports? A: Yes
Q: Also what do we do if someone does not submit a report - allow them to give it orally or just skip the report? A: If staff, a hanging. If volunteers, a round of drinks for the entire Council.
Ok ...a sensible answer .... A: Skip the report if not essential that day and allow it to be submitted in the next 7 days.
Philip
All After many years of supporting the ISPCP Constituency and representing their interest on the GNSO Council and numerous working groups, Greg Ruth is moving on from Verizon. His place on the GNSO Council will be filled by Maggie Mansoukia who worked with Greg in Verizon and has also been active in the ISPCP Constituency, again representing them on various task force and working groups. Maggie will be filling this seat until the new Council members are seated in Seoul. I'm sure those of you who worked with Greg across the years will join me in thanking him for the effort he put in across the years. Tony
Hi, Greg: It has been a privileged working with you these past few years. Both when we agreed and we didn't, you always were a pleasure to talk to. Good luck in new ventures. Maggie: Welcome - please let me know what I can do to help you with getting involved with the council work. I am sure Glen will add you to the mailing soon, if she has not done so already. a. On 27 Aug 2009, at 14:21, Tony Holmes wrote:
All
After many years of supporting the ISPCP Constituency and representing their interest on the GNSO Council and numerous working groups, Greg Ruth is moving on from Verizon.
His place on the GNSO Council will be filled by Maggie Mansoukia who worked with Greg in Verizon and has also been active in the ISPCP Constituency, again representing them on various task force and working groups. Maggie will be filling this seat until the new Council members are seated in Seoul.
I'm sure those of you who worked with Greg across the years will join me in thanking him for the effort he put in across the years.
Tony
Greg, It was a pleasure working witht you, I wish you good luck and all the best in your new work. Maggie, welcome! Looking forward to working with you in the council. Regards Olga 2009/8/27 Tony Holmes <tonyarholmes@btinternet.com>
All
After many years of supporting the ISPCP Constituency and representing their interest on the GNSO Council and numerous working groups, Greg Ruth is moving on from Verizon.
His place on the GNSO Council will be filled by Maggie Mansoukia who worked with Greg in Verizon and has also been active in the ISPCP Constituency, again representing them on various task force and working groups. Maggie will be filling this seat until the new Council members are seated in Seoul.
I'm sure those of you who worked with Greg across the years will join me in thanking him for the effort he put in across the years.
Tony
-- Olga Cavalli, Dr. Ing. www.south-ssig.com.ar
participants (10)
-
Avri Doria -
Avri Doria -
Glen de Saint Géry -
Gomes, Chuck -
Olga Cavalli -
Philip Sheppard -
Robert Hoggarth -
Rosette, Kristina -
Stephvg2 -
Tony Holmes