- ispcp - lists.icann.org

FW: Conference Details ISP NOV 04, 2008--15:15 -Conf# 1360303)
by mark.h.mcfadden＠bt.com Nov. 3, 2008

Nov. 3, 2008

Subject: Conference Details ISP NOV 04, 2008--15:15 -Conf# 1360303) Dear All, The dial-in details for the ISP constituency call. CONFIRMATION #: 1360303 Meeting Room: ABDEEN 2 (Confirming that this room will be large enough for 30 participants) CALL DATE: NOV-04-2008 - Tuesday CALL TIME: 13:15 UTC, 05:15 PST, 08:15 EST, 14:15 CET , 15:15 CAIRO DURATION: 1 hr 45 min 5 LINES (if you need more let me know) DIAL-IN NUMBERS: PARTICIPANT PASSCODE: ISP For security reasons, the passcode will be required to join the call. Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0494 AUSTRALIA ADELAIDE: 61-8-8121-4862 1-800-880-485 AUSTRALIA BRISBANE: 61-7-3102-0964 1-800-880-485 AUSTRALIA CANBERRA: 61-2-6100-1964 1-800-880-485 AUSTRALIA MELBOURNE: 61-3-9010-7733 1-800-880-485 AUSTRALIA PERTH: 61-8-9467-5243 1-800-880-485 AUSTRALIA SYDNEY: 61-2-8211-1386 1-800-880-485 AUSTRIA 43-1-92-89-654 0800-999-636 BELGIUM 32-2-402-2432 0800-4-8360 BRAZIL 0800-8912038 CHILE 1230-020-0281 CHINA* 86-400-810-4760 10800-712-1193 10800-120-1193 COLOMBIA 01800-9-156463 CZECH REPUBLIC 420-2-25-98-56-15 800-700-167 DENMARK 45-7014-0238 8088-6075 FINLAND Land Line: 106-33-164 0-800-1-12056 FINLAND Mobile: 09-106-33-164 0-800-1-12056 FRANCE LYON: 33-4-26-69-12-75 080-511-1431 FRANCE MARSEILLE: 33-4-86-06-00-75 080-511-1431 FRANCE PARIS: 33-1-70-75-00-04 080-511-1431 GERMANY 49-69-2222-52104 0800-216-1601 GREECE 30-80-1-100-0639 00800-12-5999 HONG KONG 852-2286-5632 800-964-136 HUNGARY 06-800-15227 INDIA 000-800-852-1216 INDONESIA 001-803-011-3500 IRELAND 353-1-246-0036 1800-931-782 ISRAEL 1-80-9303048 ITALY 39-02-3600-0326 800-906-585 JAPAN OSAKA: 81-6-7739-4763 00531-12-1149 JAPAN TOKYO: 81-3-5539-5154 00531-12-1149 LUXEMBOURG 352-27-000-1314 MALAYSIA 1-800-80-8121 MEXICO 001-866-627-0541 NETHERLANDS 31-20-710-9321 0800-023-4655 NEW ZEALAND 64-9-970-4641 0800-443-793 NORWAY 47-21-59-00-14 800-11982 PANAMA 011-001-800-5072119 POLAND 00-800-1210067 PORTUGAL 8008-12179 RUSSIA 8-10-8002-9613011 SINGAPORE 65-6883-9197 800-120-4057 SLOVAK REPUBLIC 421-2-322-422-15 SOUTH AFRICA 080-09-93390 SOUTH KOREA 82-2-6744-1052 00798-14800-6323 SPAIN 34-91-414-15-44 800-099-279 SWEDEN 46-8-566-10-782 0200-887-612 SWITZERLAND 41-44-580-7718 0800-000-038 TAIWAN 886-2-2795-7346 00801-137-565 THAILAND 001-800-1206-65091 UNITED KINGDOM BIRMINGHAM: 44-121-210-9015 0800-018-0795 UNITED KINGDOM GLASGOW: 44-141-202-3215 0800-018-0795 UNITED KINGDOM LEEDS: 44-113-301-2115 0800-018-0795 UNITED KINGDOM LONDON: 44-20-7019-0812 0800-018-0795 UNITED KINGDOM MANCHESTER: 44-161-601-1415 0800-018-0795 URUGUAY 000-413-598-3439 USA 1-210-795-0472 877-818-6787 VENEZUELA 0800-1-00-3205 *Access to your conference call will be either of the numbers listed, dependent on the participants' local telecom provider. Let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

by Tony Holmes Nov. 1, 2008

Nov. 1, 2008

All The attached document is the result of work done by representatives of the IP, ISP and BC constituencies (Tony Holmes for the ISPCP) to find common ground between our three constituencies so that a basis to go forward with GNSO reform can be established. The logic, particularly recognizing the short time frame between the Cairo and Mexico City meetings (and certain milestones that need to be met), is to ask our constituencies to weigh in on which of the three models they would like to pursue: Constituency, Collapsed, or Transitional. Ideally each constituency might rank them in the order of most to least desirable to assist further work. Discussions within the ISPCP to date lean heavily towards the Constituency model, so if you have another view its important to respond promptly to the list. The objective is try to have feedback on this - and a decision - by the end of the Cairo meeting. Thank you in advance for your consideration. Regards from Cairo Tony

1 0

[ SECRETARIAT ] Draft Agenda for ICANN ISPCP Constiteuncy Meetings in Cairo, Egypt
by Mark McFadden Oct. 23, 2008

Oct. 23, 2008

======================================================================== Internet Service Provider and Connectivity Provider Constituency Generic Names Supporting Organization ======================================================================== 23 October 2008 DRAFT AGENDA - ISPCP CONSTITUENCY MEETING - ICANN CAIRO MEETING As agreed on today's ISPCP conference call, the following draft agenda Will be used at the ICANN meetings in Cairo, Egypt: ISPCP Constituency Agenda 4 Nov 2008 - Starting at 15:15 Ending at 17:00 Room: Abdeen 2 Agenda 1. Introductions and agenda bashing 2. ISPCP discussions on the way forward for gNSO reform 3. Brief update on the state of discussions surrounding whois 4. Signing the root - implications and timeline 5. Discussion of ISPCP response to developments related to new gTLDs 6. Fast-flux and the ISPCP community 7. Presentation on the .tel TLD 8. Presentation on the .mobi TLD 9. Any other business 10. Adjournment For questions about the agenda, the ICANN meetings in general or the ISPCP constituency please drop a note to secretariat(a)ispcp.info

1 0

SECRETARIAT: [ reminder ] ISPCP Constituency Conference Call on Thursday 23 October
by Mark McFadden Oct. 22, 2008

Oct. 22, 2008

All: This is just a reminder for a ISPCP Constituency call on Thursday: There will be a short ISPCP Conference Call for all constituency members on Thursday 23 October 2008 1700 - Germany, France 1600 - UK (BST) 1500 - GMT 1300 - Buenos Aires 1100 - Boston, Washington DC 1000 - Madison Other times can be found here: http://www.timeanddate.com/worldclock/fixedtime.html?year=2008 <http://www.timeanddate.com/worldclock/fixedtime.html?year=2008&month=10&day =23&hour=15&min=0&sec=0> &month=10&day=23&hour=15&min=0&sec=0 The principle topic of the Conference Call will be preparations for the upcoming ICANN meeting in Cairo Egypt. If you would like to participate, please drop me a note at: ispcp-activity(a)mcfaddencentral.com and I will be happy to forward the conference details to you. Mark McFadden Secretariat, ISPCP Constituency

1 0

SECRETARIAT: New ISPCP Member
by Mark McFadden Oct. 22, 2008

Oct. 22, 2008

======================================================================== Internet Service Provider and Connectivity Provider Constituency Generic Names Supporting Organization ======================================================================== 22 October 2008 Please join with me in officially welcoming the newest member of the ISPCP Constituency: the Arab Regional ISP's Association (ARISPA). ARISPA is represented by its chairman: Mr. Mohamad Feras Bakour and is now a participant on the ISPCP mailing list. More information about ARISPA can be found at its website: http://www.arispa.org On behalf of all of the ISPs working in ICANN, please join me in Welcoming ARISPA to the ISPCP Constituency! Mark McFadden Secretariat, ISPCP Constituency

1 0

FW: Policy staff at constituency day meetings
by mark.h.mcfadden＠bt.com Oct. 21, 2008

Oct. 21, 2008

To be considered on our Thursday conference call. mark ________________________________ From: Glen de Saint Géry [mailto:Glen@icann.org] Sent: Mon 10/20/2008 16:14 To: McFadden,MH,Mark,DMF R; tonyarholmes(a)btinternet.com; Anthony Harris; 'Greg Ruth' Cc: GNSO Secretariat Subject: Policy staff at constituency day meetings Dear All, Could you please let me know if you would like any member in particular, or all the policy staff, Denise Michel, Liz Gasster, Marika Konings, Rob Hoggarth and Ken Bour, the new policy team consultant, to address your constituency, and the topics in particular you would like them to address. Please also indicate an appropriate time so that we can coordinate the different requests. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org <http://gnso.icann.org/>

1 0

[SECRETARIAT] ISPCP Conference Call - Thursday 23 October 2008
by mark.h.mcfadden＠bt.com Oct. 21, 2008

Oct. 21, 2008

All: There will be a short ISPCP Conference Call for all constituency members on Thursday 23 October 2008 1700 - Germany, France 1600 - UK (BST) 1500 - GMT 1300 - Buenos Aires 1100 - Boston, Washington DC 1000 - Madison Other times can be found here: http://www.timeanddate.com/worldclock/fixedtime.html?year=2008&month=10&day… The principle topic of the Conference Call will be preparations for the upcoming ICANN meeting in Cairo Egypt. If you would like to participate, please drop me a note at: ispcp-activity(a)mcfaddencentral.com and I will be happy to forward the conference details to you. Mark McFadden Secretariat, ISPCP Constituency

1 0

Re: [ispcp] Draft statement on gNSO reform implementation issues
by Greg Ruth Sept. 16, 2008

Sept. 16, 2008

Looks fine to me. There seems to be a typo in the first paragraph of section 2 "for an interim period one NCA appointee would made to each house" Greg ----- Original Message ---- From: Mark McFadden <mcfadden(a)ispcp.info> To: ispcp(a)icann.org Sent: Tuesday, September 16, 2008 10:48:55 AM Subject: [ispcp] Draft statement on gNSO reform implementation issues Based on the last ISPCP teleconference, a draft ISPCP statement on gNSO reform implementation issues has been produced. It is attached to this mail message. We need to have comments pretty quickly because the deadline for submitting these comments is almost upon us. Please “reply-all” any comments you might have on this short draft. Thanks for your prompt attention! Mark Mark McFadden Secretariat, ISPCP

1 0

Draft statement on gNSO reform implementation issues
by Mark McFadden Sept. 16, 2008

Sept. 16, 2008

Based on the last ISPCP teleconference, a draft ISPCP statement on gNSO reform implementation issues has been produced. It is attached to this mail message. We need to have comments pretty quickly because the deadline for submitting these comments is almost upon us. Please "reply-all" any comments you might have on this short draft. Thanks for your prompt attention! Mark Mark McFadden Secretariat, ISPCP

1 0

Comments of the ISPCP Constituency on the ALAC Review
by mark.h.mcfadden＠bt.com Sept. 12, 2008

Sept. 12, 2008

ISPCP Comments to the ALAC Review In the main, the ISPCP constituency believes that the At-Large Advisory Committee (ALAC) can serve a useful and important role in ICANN to "consider and provide advice on the activities of ICANN, insofar as they relate to the interests of individual Internet users." [from the Bylaws] We believe that, although the ALAC initially had an ineffectual beginning, it has seen significant improvement in the past year. Nevertheless, it has a long way to go before it can truly be said to represent the interests of the general Internet user community. Therefore, the ISPCP constituency welcomes the ALAC Review as a valuable starting point for strengthening the ALAC and improving its efficacy. Toward that end we offer the following comments to the main recommendations of the BCG report. 1.1 Recommendations Recommendation 1 That the number of NomCom appointees to the ALAC should be increased from five to seven, and that this structure should specifically be revisited at the next triennial review taking account of the then existing Geographic Regional Structure of ICANN. We see no reason to change the number of appointees to the ALAC. This would run counter to the concept of ALAC representing the 5 ICANN regions. Each region has its own particular interests and concerns; population is not an overriding factor. Recommendation 2 That all members of the ALAC (and, ideally, of the RALOs) should be given clear position descriptions. We fully support this recommendation. Recommendation 3 That the current distribution of the RALOs be left unaltered until at least the next ALAC review. This a reasonable approach. The implementation of the RALO concept is still in its early days. It should be more mature before considering an alteration of its structure. Recommendation 4 That ICANN should implement an activity-based costing system in order to improve resource management. We fully endorse this recommendation. This is indispensable to improving ALAC's effectiveness. Recommendation 5 That ICANN should provide further resourcing to support the ALAC, to the extent of (up to) one new employee per region. We agree that ICANN should provide further resourcing if, as and when necessary to support the ALAC. The amount and type of support should be based on the Annual Statement of Intent and ALAC Strategic Plan (see Rec. 10). Until a clear and persuasive case is made, though, it is premature to suggest increased support. Recommendation 6 That the ALAC Chair negotiate an annual support agreement with ICANN staff, setting out agreed expectations and performance indicators. Agreed. Recommendation 7 The ALAC position on the Board should remain that of a Liaison, with rights to full participation and information, but no voting rights. Agreed. This is an effective and appropriate way for ALAC to contribute to the deliberations of the ICANN Board. Recommendation 8 That the term of appointment of the Board and other Liaisons be extended to two years, subject to the ALAC retaining the 'right of recall' under the Rules of Procedure, Rule 11 - Recall Votes. Acceptable. This is a reasonable modification of the current arrangement. Recommendation 9 That ICANN staff should create a brief and multi-lingual guide to ICANN and the ALAC, aimed at individual Internet users and ALSs. We fully support this. Recommendation 10 That the ALAC should develop: * A simple annual Statement of Intent which specifies the current issues and priorities, objectives and activities for the next 12 months, and defines measures of success for each of the activities and objectives. This document should be strongly aligned to ICANN's Strategic and Operational Plans and be published on the ALAC website; * Before the next ICANN annual planning cycle, the ALAC should develop a Strategic Plan of its own (complementing the broader ICANN Strategic Plan). * Following the development of this Strategic Plan, the ALAC should then generate an annual Operating Plan which cites the activities and resources required to support the Strategic Plan during that year (also complementing the corresponding broader ICANN Strategic and Operating Plans and fitting the same planning cycle). We believe these documents are necessary to improve the focus and effectiveness of the ALAC. Considerable emphasis should be place on outreach activities; today ALAC engages an unacceptably miniscule fraction of the billion+ Internet users. If regional focus is expanded, additional staff support should be implemented step by step as warranted (see comments on Rec. 5). Recommendation 11 That the term of appointment of the ALAC Chair should be extended to two years. This is an acceptable modification of the current arrangement. As with Rec. 8, we believe the 'right of recall' under the Rules of Procedure, Rule 11 - Recall Votes should be retained. Recommendation 12 That the ALAC should explore ways to differentiate between organizations that genuinely represent individual Internet users, and are therefore ALS candidates, as opposed to those which may be a better fit with the NCUC. We fully support this. Additionally we recommend that both ALAC and NCUC should be urged to clarify the status of representation. Recommendation 13 That the ALAC should publish on its website trends in the average time taken from receipt of an ALS application to decision. Supported. Recommendation 14 That regular ALS compliance reviews be conducted and the non-compliance provisions be applied as appropriate. Supported. Recommendation 15 That ICANN should develop clear sanctions for non-compliance. These might include: ineligibility for ICANN travel funding; loss of voting rights; or being suspended until the matter is remedied. Supported. Recommendation 16 That any outstanding issues relating to Ombudsman reports 05-1090 and 06-317, should be dealt with as soon as possible by the ICANN Board or the ALAC (as appropriate). Supported. Recommendation 17 That the ALAC should develop a clearly defined process for the engagement of the At-Large community in developing policy positions. We fully support this. A uniform process and increased outreach are called for. Recommendation 18 That the ALAC should use multi-lingual wikis rather than the current email lists to allow the At-Large community to more easily observe and participate in the development of policy positions. Agreed. Recommendation 19 That ICANN should increase the public comment period to 45 calendar days in order to allow a greater time period for At-Large community consultation in all regions. This should not be necessary if ALAC succeeds in improving its effectiveness in reaching its target community. 45 days is unacceptably long. Recommendation 20 That the ICANN Board should amend the Travel Policy to pay for accommodation expenses (including breakfast and internet access fees) and where practicable accommodate At-large members at or very near the main conference venue. The per diem amount (to cover other appropriate daily expenses) should also be available as a cash advance for those that require it. No special provisions should be formulated for ALAC participation in ICANN. Any ALAC travel policy should be discussed and developed in the context of the general ICANN travel policy and subject to the same financial reviews. Recommendation 21 That private email lists should be used only for appropriate non-public discussion. Agreed. Recommendation 22 That ICANN should continue to work on its language policy, including translation and other services. Generally supported, but ICANN should determine the impact on its financial budget implications and transparently make their findings known to the public. Recommendation 23 That ICANN staff should manage and maintain content of the various ALAC wikis. As with Rec. 22 we generally support this concept, but with the proviso that the specific budget implications are calculated and made transparent. Recommendation 24 That the ALAC should replace email lists with wikis for policy discussions in particular and continue the evaluation of Web-based tools to facilitate discussion and collaborative working. Agreed. This should help improve ALAC's effectiveness.

1 0