July 2013 - ALAC - lists.icann.org

Fwd: Creating a New ICANN 5-Year Strategic Plan - Durban Monday 10:30 - 12:00 Hall 6
by Olivier MJ Crepin-Leblond July 7, 2013

July 7, 2013

Dear all, please be so kind to find the announcement of the session below in Durban. The community is being solicited to take part in this new process, which is a brand new start, in contrast to previous processes. This is of course brought about by the new Team so I hope that we will be able to take part fully in this, although I am aware that this clashes partly with the At-Large Regulatory Issues Group (Registrant Rights and WHOIS Groups). So we'll have to split into (at least) two groups at the time. Kind regards, Olivier -------- Original Message -------- Subject: Creating a New ICANN 5-Year Strategic Plan - Durban Monday 10:30 - 12:00 Hall 6 Date: Fri, 5 Jul 2013 18:36:59 -0700 From: Denise Michel <denise.michel(a)icann.org> Reply-To: denise.michel(a)icann.org To: ocl(a)gih.com CC: Sebastien Bachollet <sebastien.bachollet(a)icann.org>, Heidi Ullrich <Heidi.Ullrich(a)icann.org>, David Olive <david.olive(a)icann.org> Dear Olivier & At-Large Community Members: Attached is information on the Durban session on *"Creating a New ICANN 5-Year Strategic Plan," scheduled for Monday, 15 July from 10:30 - 12:00* *in Hall 6*. We look forward to seeing you there and would appreciate you sharing this note broadly. This special community event will follow the ICANN President's Opening Session to help build ICANN's new, overarching vision and five-year strategic plan. Xplane, professional facilitators who have worked with the ICANN Board, staff and some community groups, will help us run a cross-constituency brainstorming and discussion session to yield focused input for ICANN's new strategic plan. This session also is intended to help prompt more strategic conversations throughout the community during our week in Durban and beyond. Building on previous discussions about how to help prepare ICANN for an increasingly complex world, this session will solicit input on eight key areas of consideration for the new strategic plan: * Role clarity for ICANN * ICANN Community * Users * Internationalization & Regional Development * Internet Governance * Security and stability * Operational Excellence * Domain Name Industry Engagement. We look forward to seeing you there. Regards, Denise Denise Michel VP Strategic Initiatives & Advisor to the President ICANN

3 6

Fwd: NGPC Progress on Addressing GAC Beijing Advice on New gTLDs
by Carlton Samuels July 4, 2013

July 4, 2013

Grist for our Q&A mill.... -Carlton ============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment & Turnaround* ============================= ** [image: ICANN] <http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-03jul13-en.htm ------------------------------ NGPC Progress on Addressing GAC Beijing Advice on New gTLDs 3 July 2013 On 2 July 2013, the the ICANN Board New gTLD Program Committee (NGPC) had its seventh meeting to discuss the GAC Beijing advice on New gTLDs. The Committee took the following actions: 1. *Initial Protections for IGO Protections* In the Beijing Communiqué, the GAC reiterated previous advice that "appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch." In response to a number of issues raised by the Board, the GAC noted in the Beijing Communiqué that it is "mindful of outstanding implementation issues" and that it is committed to "actively working with IGOs, the Board, and ICANN Staff to find a workable and timely way forward. In a 6 June 2013 response letter to the GAC on the IGO GAC Advice, the ICANN Board Chairman proposed that a small number of NGPC members and ICANN staff begin a dialogue with the GAC on these issues At its 2 July 2013 meeting, the NGPC passed a resolution confirming that the New gTLD Registry Agreement will require operators to provide appropriate preventative initial protection for the IGO identifiers. These protections will remain in place while the GAC, NGPC, ICANN Staff and community continue to actively work through outstanding implementation issues. More specifically, registry operators will implement temporary protections for the IGO names and acronyms on the "IGO List dated 22/03/2013" until the first meeting of the NGPC following the ICANN 47 Meeting in Durban. The Resolution provides temporary protections for IGOs while respecting the ongoing work on implementation issues. The IGO List is attached to the Resolution as Annex 1. If the NGPC and GAC do not reach an agreement on outstanding implementation issues for protecting IGO names and acronyms by the first meeting of the NGPC following the ICANN 47 meeting in Durban, and subject to any matters that arise during the discussions, registry operators will be required to protect only the IGO names (and not the acronyms) identified on the GAC's IGO List. 2. *Category 1 Advice* In the Beijing Communiqué, the GAC proposed Category 1 safeguard advice, which includes recommended restrictions and consumer protections for sensitive strings and regulated markets. The Category 1 Safeguard Advice is divided into three main sections. The first section provides five (5) items of advice that apply to "strings that are linked to regulated or professional sectors." The Beijing Communiqué identified a list of strings to which this advice applies. The second section provides three (3) additional pieces of advice that should apply to a limited subset of the strings noted in the GAC's list that are "associated with market sectors which have clear and/or or regulated entry requirements (such as: financial, gambling, professional services, environmental, health and fitness, corporate identifiers, and charity) in multiple jurisdictions…." The third section includes an additional requirement for applicants for the following strings: .fail, .gripe, .sucks and .wtf. On 23 April 2013, ICANN initiated a public comment forum to solicit input on how the NGPC should address GAC advice regarding safeguards applicable to broad categories of new gTLD strings http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en…. The public comment forum closed on 4 June 2013. While many commenters voiced support for the Category 1 safeguard advice, many others submitting opposing comments. One overarching theme from the public comments was the need for additional clarity on the scope and intent of the Category 1 Safeguard Advice. After considering the community comments, the NGPC decided to begin a dialogue with the GAC during the ICANN Meeting in Durban to clarify the scope of the requirements provided in the Category 1 Safeguard Advice. The dialogue with the GAC on Category 1 will also include discussion of GAC's Category 2.1 Safeguard Advice regarding "Restricted Access" since that advice applies to the strings listed under Category 1. Pending the dialogue with the GAC, staff will defer moving forward with the contracting process for applicants who have applied for TLD strings listed in the GAC's Category 1 Safeguard Advice. 3. *New gTLD Registry Agreement* Finally, the NGPC considered the revised New gTLD Registry Agreement that will be entered into between ICANN and successful new gTLD applicants. The revised agreement is the result of several months of negotiations, formal community feedback (most recently during public comment forums initiated on 5 February 2013 on 29 April 2013), and meetings with various stakeholders and communities. The revisions include feedback from the ICANN community at the ICANN 46 Meeting on 7-11 April 2013 in Beijing as well as GAC advice issued in its Beijing Communiqué. After considering the comments received from the community, the NGPC determined that the revised New gTLD Registry Agreement included significant improvements in response to the concerns raised by the community. The Committee also noted that in response to the GAC's Beijing Communiqué, revisions were made to Specification 11 to implement the non-Category 1 safeguard advice (i.e., safeguards applicable to all strings and Category 2 safeguards). The revisions to Specification 11 incorporate standardized language to address the safeguard advice. Applicant-specific PICs will be included on a case-by-case basis to the extent not superseded by or inconsistent with the standard PICs included to address the GAC's Beijing Communiqué. The NGPC approved the form of the New gTLD Registry Agreement and authorized ICANN staff to take all necessary steps to implement it and to move forward with implementation of the New gTLD Program. The Agreement is attached to the Resolution as Annex 1; the complete Summary of Changes to the New gTLD Registry Agreement is attached to the Resolution as Annex 2; a redline of the current agreement as compared to the previous version dated 29 April 2013 is attached to the Resolution as Annex 3; and the Summary and Analysis of Public Comments is available at http://www.icann.org/en/news/public-comment/report-comments-base-agreement-…, 338 KB]. All of the resolutions adopted at the 2 July 2013 NGPC meeting are posted at http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-02jul13…. A table summarizing NGPC Consideration of the GAC's Beijing Advice appears below: http://www.icann.org/en/news/announcements/announcement-2-03jul13-en.htm#su…

1 0

Fwd: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY
by Holly Raiche July 4, 2013

July 4, 2013

Hi Everyone On Tuesday/Wednesday's ALAC call, there were questions abut the need for non-US citizens to have filled in the form - so I asked. This is the answer for those (like me) who thought it was very clear, but needed confirmation after the call. Holly Begin forwarded message: > From: ICANN Constituency Travel <constituency-travel(a)icann.org> > Date: 3 July 2013 4:54:39 PM AEST > To: Holly Raiche <H.RAICHE(a)internode.on.net> > Cc: ICANN Constituency Travel <constituency-travel(a)icann.org> > Subject: Re: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY > > Hi Holly, > > Since you are not a US citizen, you will need to provide/complete a W-8BEN Form. > > Thank you! > > Best wishes, > > Joseph de Jesus > Travel Support Coordinator > > Diane Schroeder, Joseph de Jesus, and Karen Lettner > Constituency Travel Team > > ICANN > 12025 Waterfront Drive, Suite 300 > Los Angeles, CA 90094-2536 > > email: constituency-travel(a)icann.org > > From: Holly Raiche <H.RAICHE(a)internode.on.net> > Date: Tuesday, July 2, 2013 9:44 PM > To: Joseph de Jesus <constituency-travel(a)icann.org> > Subject: Re: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY > > Hi Joseph > A final question: Everyone was sent a US tax form, but it turned out it is only for US citizens. I have not filled it out, since I am an Australian citizen. I am assuming that means that my per diem will go into the bank soon, and that all is okay. > > Thanks (amidst what must be a VERY busy time for you) > > Holly > On 28/06/2013, at 6:26 AM, ICANN Constituency Travel wrote: > >> Thank you. Duly noted. >> >> Best wishes, >> >> Joseph de Jesus >> Travel Support Coordinator >> >> Diane Schroeder, Joseph de Jesus, and Karen Lettner >> Constituency Travel Team >> >> ICANN >> 12025 Waterfront Drive, Suite 300 >> Los Angeles, CA 90094-2536 >> >> email: constituency-travel(a)icann.org >> >> From: Holly Raiche <H.RAICHE(a)internode.on.net> >> Date: Thursday, June 27, 2013 1:19 PM >> To: Joseph de Jesus <constituency-travel(a)icann.org> >> Subject: Re: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY >> >> Hi Joseph >> >> I hope that isn't a 'change' - just reflecting the flight plans already made (arrival late in the evening of the 12th and departure mid afternoon of the 19th) >> >> >> Also, when my accommodation is booked, could someone please note that my plane doesn't arrive in Durban until 7.05 pm so I"ll be a late arrival >> >> Thanks >> >> >> On 28/06/2013, at 2:51 AM, ICANN Constituency Travel wrote: >> >>> Hi Holly, >>> >>> I'll make the change. >>> >>> Best wishes, >>> >>> Joseph de Jesus >>> Travel Support Coordinator >>> >>> Diane Schroeder, Joseph de Jesus, and Karen Lettner >>> Constituency Travel Team >>> >>> ICANN >>> 12025 Waterfront Drive, Suite 300 >>> Los Angeles, CA 90094-2536 >>> >>> email: constituency-travel(a)icann.org >>> >>> From: Holly Raiche <H.RAICHE(a)internode.on.net> >>> Date: Wednesday, June 26, 2013 7:05 PM >>> To: Joseph de Jesus <constituency-travel(a)icann.org> >>> Subject: Re: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY >>> >>> Hi Joseph >>> >>> I had planned to check out the morning of the 19th - so my last night will be the 18th. >>> >>> Holly >>> On 27/06/2013, at 9:51 AM, ICANN Constituency Travel wrote: >>> >>>> Hello Holly, >>>> >>>> Before I approve, I note that you are departing on the 19th. Will you be checking out and leaving the conference where you have meetings on the 18th? >>>> >>>> Best wishes, >>>> >>>> Joseph de Jesus >>>> Travel Support Coordinator >>>> >>>> Diane Schroeder, Joseph de Jesus, and Karen Lettner >>>> Constituency Travel Team >>>> >>>> ICANN >>>> 12025 Waterfront Drive, Suite 300 >>>> Los Angeles, CA 90094-2536 >>>> >>>> email: constituency-travel(a)icann.org >>>> >>>> From: Holly Raiche <H.RAICHE(a)internode.on.net> >>>> Date: Tuesday, June 25, 2013 9:16 PM >>>> To: Joseph de Jesus <constituency-travel(a)icann.org> >>>> Subject: Re: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY >>>> >>>> Hi Joseph >>>> >>>> This email suggests that ICANN will only cover accommodation for the nights of 13 - 19 July. The nights' accommodation I will need are from 12 - 18 July - the same number of nights, but just a day earlier. As I have already explained, the best flight for me from Australia arrives at 2200 on the 12th. Other flights, costing much the same, would have taken considerably longer time and I would have arrived Saturday morning - when the meetings I will be attending - will have started. >>>> >>>> So please confirm that ICANN will be covering my accommodation costs on the nights from 12 - 18 July. >>>> >>>> Thank you >>>> >>>> Harriet (Holly) Raiche >>>> >>>> >>>> On 24/06/2013, at 4:51 PM, ICANN Constituency Travel wrote: >>>> >>>>> Dear Harriet, >>>>> >>>>> Your itinerary below has been ticketed and this itinerary has been approved to be paid by ICANN with the following provisions: >>>>> >>>>> 1)ICANN will pay hotel nights for only Saturday, July 13, 13 - Friday, July 19, 13. It is your own financial responsibility to pay for any other hotel nights outside of your approved travel days. >>>>> >>>>> 2)It is your responsibility to make your own hotel arrangement for your outside approved travel days. If you would like to stay at the same hotel for any unapproved travel days, please submit your request to us and we will attempt to accommodate. Kindly note that you will be financially responsible in paying for during the outside travel days. >>>>> >>>>> 3)You are only eligible for per diem/stipend/actual expenses (as it pertains to your group) payments as based on your approved travel dates. >>>>> >>>>> 4)If you subsequently make any changes to your itinerary, you are financially responsible in paying for all additional fare costs. >>>>> >>>>> Best wishes, >>>>> >>>>> Joseph de Jesus >>>>> Travel Support Coordinator >>>>> >>>>> Diane Schroeder, Joseph de Jesus, and Karen Lettner >>>>> Constituency Travel Team >>>>> >>>>> ICANN >>>>> 12025 Waterfront Drive, Suite 300 >>>>> Los Angeles, CA 90094-2536 >>>>> >>>>> email: constituency-travel(a)icann.org >>>>> >>>>> From: "burbankgba(a)bcdtravel.com" <burbankgba(a)bcdtravel.com> >>>>> Date: Friday, June 21, 2013 6:43 PM >>>>> To: Joseph de Jesus <constituency-travel(a)icann.org>, "H.RAICHE(a)INTERNODE.ON.NET" <H.RAICHE(a)INTERNODE.ON.NET> >>>>> Subject: TRAVEL INVOICE FOR RAICHE/HARRIET LOCKE TRAVEL DATE 12Jul FOR LOCATOR KMOCMY >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Please do not respond to this message via email. This is an auto-generated message and can not process your reply. >>>>> >>>>> Printer Friendly >>>>> >>>>> Invoice / Ticket Receipt >>>>> Total Invoice Amount: 2976.00 USD >>>>> ElectronicTicket Number: 0837287965289 >>>>> Invoice Number: 0038289 >>>>> Ticket Amount: 2976.00 USD >>>>> Form of Payment: AX***********1006 >>>>> >>>>> This ticket information applies to the following trip(s): >>>>> >>>>> South African Airways Flight 7701 from Sydney to Johannesburg on July 12 >>>>> South African Airways Flight 575 from Johannesburg to Durban on July 12 >>>>> South African Airways Flight 566 from Durban to Johannesburg on July 19 >>>>> South African Airways Flight 7700 from Johannesburg to Sydney on July 19 >>>>> >>>>> >>>>> >>>>> Travel Summary – Agency Record Locator KMOCMY >>>>> Traveler >>>>> RAICHE / HARRIET LOCKE >>>>> Reference number by traveler: Not Applicable >>>>> >>>>> Date From/To Flight/Vendor Status Depart/Arrive Class/Type >>>>> 07/12/2013 SYD-JNB SA 7701 Confirmed 09:55 AM/04:15 PM Economy / S >>>>> 07/12/2013 JNB-DUR SA 575 Confirmed 05:55 PM/07:05 PM Economy / H >>>>> 07/19/2013 DUR-JNB SA 566 Confirmed 03:30 PM/04:40 PM Economy / B >>>>> 07/19/2013 JNB-SYD SA 7700 Confirmed 06:15 PM/02:15 PM +1 Economy / S >>>>> >>>>> AIR - Friday, July 12 2013 - Agency Record Locator KMOCMY Add to Calendar Need Help? >>>>> South African Airways Flight SA7701 Economy Class >>>>> Depart: Kingsford Smith, TERMINAL 1 INTERNATIONAL >>>>> Sydney, New South Wales, Australia Weather >>>>> 09:55 AM Friday, July 12 2013 >>>>> Arrive: O.R. Tambo Int'l, TERMINAL A >>>>> Johannesburg, South Africa Weather >>>>> 04:15 PM Friday, July 12 2013 >>>>> Duration: 14 hour(s) and 20 minute(s) Non-stop >>>>> Status: Confirmed - South African Airways Record Locator: 5ZLS88 >>>>> Equipment: Boeing 747-400 Passenger >>>>> Operated By: Qantas Airways >>>>> Seat: Assigned at Check-in >>>>> FF Number: QFXXXX814 - RAICHE/HARRIET LOCKE >>>>> Distance: 6845 miles >>>>> CO2 Emissions: 2,560.03lbs/1,163.65kgs >>>>> >>>>> AIR - Friday, July 12 2013 - Agency Record Locator KMOCMY >>>>> South African Airways Flight SA575 Economy Class >>>>> Depart: O.R. Tambo Int'l, TERMINAL B >>>>> Johannesburg, South Africa Weather >>>>> 05:55 PM Friday, July 12 2013 >>>>> Arrive: King Shaka International Airport >>>>> Durban, South Africa Weather >>>>> 07:05 PM Friday, July 12 2013 >>>>> Duration: 1 hour(s) and 10 minute(s) Non-stop >>>>> Status: Confirmed - South African Airways Record Locator: 5ZLS88 >>>>> Meal: Snack or Brunch >>>>> Equipment: Airbus Industrie A319 >>>>> Seat: Assigned at Check-in >>>>> FF Number: QFXXXX814 - RAICHE/HARRIET LOCKE >>>>> Distance: 312 miles >>>>> CO2 Emissions: 137.28lbs/62.4kgs >>>>> >>>>> AIR - Friday, July 19 2013 - Agency Record Locator KMOCMY Add to Calendar Need Help? >>>>> South African Airways Flight SA566 Economy Class >>>>> Depart: King Shaka International Airport >>>>> Durban, South Africa Weather >>>>> 03:30 PM Friday, July 19 2013 >>>>> Arrive: O.R. Tambo Int'l, TERMINAL B >>>>> Johannesburg, South Africa Weather >>>>> 04:40 PM Friday, July 19 2013 >>>>> Duration: 1 hour(s) and 10 minute(s) Non-stop >>>>> Status: Confirmed - South African Airways Record Locator: 5ZLS88 >>>>> Meal: Snack or Brunch >>>>> Equipment: Boeing 737-800 Passenger >>>>> Seat: Assigned at Check-in >>>>> FF Number: QFXXXX814 - RAICHE/HARRIET LOCKE >>>>> Distance: 312 miles >>>>> CO2 Emissions: 137.28lbs/62.4kgs >>>>> Remarks: A DEPARTURE TAX MAY EXIST. >>>>> DEPARTURE TAXES ARE PAYABLE IN LOCAL CURRENCY. >>>>> >>>>> AIR - Friday, July 19 2013 - Agency Record Locator KMOCMY >>>>> South African Airways Flight SA7700 Economy Class >>>>> Depart: O.R. Tambo Int'l, TERMINAL A >>>>> Johannesburg, South Africa Weather >>>>> 06:15 PM Friday, July 19 2013 >>>>> Arrive: Kingsford Smith, TERMINAL 1 INTERNATIONAL >>>>> Sydney, New South Wales, Australia Weather >>>>> 02:15 PM Saturday, July 20 2013 >>>>> Duration: 12 hour(s) and 0 minute(s) Non-stop >>>>> Status: Confirmed - South African Airways Record Locator: 5ZLS88 >>>>> Equipment: Boeing 747-400 Passenger >>>>> Operated By: Qantas Airways >>>>> Seat: Assigned at Check-in >>>>> FF Number: QFXXXX814 - RAICHE/HARRIET LOCKE >>>>> Distance: 6845 miles >>>>> CO2 Emissions: 2,560.03lbs/1,163.65kgs >>>>> >>>>> Remarks >>>>> ----------------AFTER HOURS EMERGENCY CONTACTS-------- >>>>> PLEASE CALL THE TRAVEL DEPT DURING OPERATING HOURS >>>>> MON-FRI 900AM PST - 600PM PST >>>>> FOR TRAVEL EMERGENCIES AFTERHOURS AND ON >>>>> WEEKENDS PLEASE CALL 1-877-910-9738 AND USE MEMBERSHIP >>>>> CODE SMS8C >>>>> IF TRAVELING OUTSIDE THE US OR CANADA PLEASE HAVE >>>>> INTERNATIONAL OPERATOR PLACE A COLLECT CALL TO >>>>> 847-759-5437 FOR TRAVEL ASSISTANCE >>>>> ----------------SECURITY INFORMATION------------------ >>>>> FOR SECURITY INFORMATION PLEASE REFER TO THE US STATE >>>>> DEPARTMENT WEBSITE WWW.TRAVEL.STATE.GOV‡ >>>>> FOR INTERNATIONAL HEALTH/IMMUNIZATION REQUIREMENTS >>>>> REFER TO THE CDC WEBSITE WWW.CDC.GOV/TRAVEL >>>>> FOR ADDITIONAL HEALTH INFORMATION PLEASE REFER TO >>>>> THE WHO WEBSITE WWW.WHO.INT >>>>> ----------------MISC AIRLINE ADVISORIES--------------- >>>>> PLEASE BE ADVISED THAT SOME AIRLINES CHARGE SERVICE >>>>> FEES FOR CHANGES MADE DIRECTLY WITH THE AIRLINE >>>>> ----------------------------------------------------- >>>>> FOR INFORMATION ON TRAVEL REQUIREMENTS/U.S. EMBASSIES >>>>> AND/OR HEALTH IMMUNIZATIONS VISIT WWW.TRAVEL.STATE.GOV >>>>> OR CALL 202-647-5225 >>>>> *ATTN U.S. CITIZENS TRAVELLING INTERNATIONALLY* >>>>> A VALID PASSPORT IS REQUIRED FOR TRAVEL OUTSIDE >>>>> THE U.S. AND ITS TERRITORIES. MOST COUNTRIES REQUIRE >>>>> THAT YOUR PASSPORT BE VALID AT LEAST SIX <6> MONTHS BEYOND >>>>> THE DATES OF YOUR TRIP AND CONTAIN AT LEAST ONE BLANK VISA PAGE. >>>>> FOR DOMESTIC TRAVEL CHECK IN 2 HOURS PRIOR TO DEPARTURE. >>>>> INTERNATIONAL CHECK IN 3 HOURS PRIOR. >>>>> GOVERNMENT ISSUED PHOTO ID IS REQUIRED. >>>>> OBTAIN YOUR BOARDING PASS PRIOR TO REACHING THE MAIN >>>>> SECURITY CHECK POINT VIA AN ETKT KIOSK >>>>> AIRLINE COUNTER OR WEBSITE 24 HRS PRIOR TO DEPARTURE. >>>>> RECONFIRM CONTINUING INTL FLIGHTS AT LEAST >>>>> 72 HOURS IN ADVANCE. >>>>> TICKET IS NON REFUNDABLE/NON TRANSFERABLE. >>>>> CHANGES SUBJECT TO PENALTIES PLUS FARE INCREASE. >>>>> SOME CARRIERS REQUIRE CANCELLATION PRIOR TO DEPARTURE >>>>> OR YOUR TICKET MAY HAVE NO VALUE. CALL THE TRAVEL OFFICE >>>>> FOR CHANGES OR CANCELLATION OF THIS TRIP >>>>> CHECKED BAGGAGE POLICIES VARY BASED ON CARRIER AND >>>>> DESTINATION. FOR THE LATEST INFORMATION PLEASE CHECK >>>>> WITH YOUR TRAVEL CONSULTANT OR THE AIRLINES WEBSITE. >>>>> YOUR TRAVEL ITINERARY CAN BE VIEWED ONLINE AT >>>>> WWW.VIRTUALLYTHERE.COM. YOUR RESERVATION CODE >>>>> IS KMOCMY. >>>>> PROOF OF CITIZENSHIP IS REQUIRED FOR THIS ITINERARY >>>>> >>>>> Thank you for using BCD Travel for your travel needs. >>>>> >>>>> Email generated on Saturday, June 22, 2013/1:43 AM UTC >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> BCD Travel acts only as an agent for the airlines, hotels, bus companies, railroads, tour operators, cruise lines, car rental companies, and other similar third parties providing accommodations, transportation, or other meeting and travel related services (“Suppliers”). Suppliers are independent and do not act for or on behalf of BCD Travel, are not employees of BCD Travel, and do not have a joint venture or partnership with BCD Travel. Suppliers have their own terms and conditions for the services they provide, and you agree to abide by the terms and conditions set forth in any and all documents for any such Supplier services, including, without limitation, all cancellation fees. By utilizing the services represented by this itinerary, you agree to the foregoing and also agree that neither BCD Travel or its parent, affiliates, subsidiaries, partners, agents, and their respective officers, directors, employees, and representatives shall be or become liable for any loss, cost, expense, injury, accident, or damage to person or property resulting directly or indirectly from (i) the acts or omissions of Suppliers, including, but not limited to, delays or cancellation of services, cessation of operations, breakdown in machinery or equipment, or changes in fares, itineraries, or schedules; and/or (ii) acts of God, dangers incident to the sea, fires, acts of government or other authorities, wars, acts of terrorism, civil unrest, strikes, riots, thefts, pilferage, epidemics, quarantines, other diseases, climatic aberrations, or from any other cause beyond BCD Travel’s control. Please see additional terms and conditions related to this itinerary at Terms and Conditions. >>>> >>> >> >

1 0

ccNSO comments on GNSO Cross-WG principles
by Alan Greenberg July 3, 2013

July 3, 2013

>From: Jonathan Robinson <jrobinson(a)afilias.info> >To: <council(a)gnso.icann.org> >Subject: [council] FW: Letter to ccNSO re. CWG principles >Date: Wed, 3 Jul 2013 11:12:51 +0100 > >All, > >Please note ccNSO follow-up to the the GNSO >draft Principles Cross Community WG's. > >This may be one of the discussion points with >the ccNSO or indeed within the Council itself in Durban. > >Jonathan > >From: Bart Boswinkel [mailto:bart.boswinkel@icann.org] >Sent: 28 June 2013 09:43 >To: Jonathan Robinson >Cc: Gabriella Schittek; Glen de Saint Géry; Marika Konings; Lesley Cowley >Subject: Re: Letter to ccNSO re. CWG principles > >Dear Jonathan, >Please find included the comments and >suggestions on the GNSO draft Principles Cross >Community WG's in response to the GNSO Council >request to provide feed-back. The paper was >adopted at the ccNSO Council meeting on 11 June >2013. The ccNSO Council looks forward to further dialogue on this topic, >On behalf of the ccNSO Council >Bart Boswinkel > >From: Jonathan Robinson ><<mailto:jonathan.robinson@ipracon.com>jonathan.robinson(a)ipracon.com> >Date: Thursday, April 25, 2013 3:46 PM >To: Lesley Cowley <<mailto:lesley@nominet.org.uk>lesley(a)nominet.org.uk> >Cc: Bart Boswinkel ><<mailto:bart.boswinkel@icann.org>bart.boswinkel(a)icann.org>, >Gabriella Schittek ><<mailto:gabriella.schittek@icann.org>gabriella.schittek(a)icann.org>, >Glen de Saint Géry <<mailto:Glen@icann.org>Glen(a)icann.org> >Subject: Letter to ccNSO re. CWG principles > >Dear Lesley, > >Please see the attached letter intended as a >follow up to our meeting in Beijing and previous >discussions on the topic of CWGs. > >Best wishes, > > >Jonathan

1 0

Decertification of ALS: ISOC Pakistan
by Alan Greenberg July 2, 2013

July 2, 2013

I make the following motion and request a seconder. Once seconded, I request that the Chair initiate an online vote. Alan ================== Whereas the At-Large Structure: Internet Society Pakistan Chapter no longer seems to exist, its domain name (isocpk.org) has expired, and all communication with identified leaders of the ALS has failed; Whereas the Internet Society has informed the Chair of the ALAC that this Internet Society Chapter has been closed; Whereas other At-Large participants from Pakistan have verified that the Internet Society Pakistan Chapter no longer exists; Whereas the ALAC has documented the due diligence investigating this decertification as per https://community.icann.org/display/atlarge/Internet+Society+Pakistan+%28AP…; Whereas the ALAC allows for such decertification as per Section II.7 of the At-Large Framework Formation (http://www.atlarge.icann.org/framework.htm#CertificationProcess) It is resolved that the ALAC decertifies the Internet Society Pakistan Chapter as an ICANN At-Large Structure. Such decertification is subject ICANN Board Reconsideration as per Article IV, Section 2 of the ICANN Bylaws and is done without prejudice to any future re-application of this organization for certification as an ALS, or the application for ALS certification of any new group bearing the same name.

3 2

Re: [ALAC] [APAC-Discuss] At-Large Community Views Requested on Draft Final Report on Universal Acceptance of IDN TLDs
by Edmon July 2, 2013

July 2, 2013

Hi Satish, That is a great question. The scope of the issues are well documented in the UX report: http://www.icann.org/en/resources/idn/variant-tlds/active-ux-21mar13-en.pdf As more languages consider their IDN Variant policies, we may see other challenges as well, so I am not sure whether it will ever be "complete"... but I think the operational experience already out there and the framework of the UX report should provide us enough to go out to the technical community to alert them about it and then perhaps there might be feedback to prompt more work too... Edmon > -----Original Message----- > From: apac-discuss-bounces(a)atlarge-lists.icann.org [mailto:apac-discuss- > bounces(a)atlarge-lists.icann.org] On Behalf Of Satish Babu > Sent: Tuesday, July 2, 2013 4:02 PM > To: Rinalia Abdul Rahim > Cc: apralo; No name; ALAC Working List; ec(a)isoc.my > Subject: Re: [APAC-Discuss] At-Large Community Views Requested on Draft > Final Report on Universal Acceptance of IDN TLDs > > Hi Rinalia > Thanks for the document. > > Coming from a linguistically diverse country, I fully endorse the > recommendations made by the JIG, and also support the position that you > have proposed for ALAC. > > As a programmer, I see several challenges ahead for DNS/website/database > administrators in retrofitting IDNs into their Internet applications. I am > curious to know if there any remaining technical issues that will need > resolution before the Universal Acceptance policy can be reliably rolled > out...in particular, are the issues around IDN variants (esp. security related) > fully resolved ? > > > > satish > > > On Tue, Jul 2, 2013 at 12:02 PM, Rinalia Abdul Rahim > <rinalia.abdulrahim(a)gmail.com> wrote: > > Hello, everyone. > > > > I have not received feedback regarding the 9-page draft final report > > from the JIG. My personal opinion is that recommendations of the > > report do require At-Large support, particularly if IDN TLD adoption > > is considered to be important for Internet users. I propose the > > following simple response - your comments are most welcome: > > > > *ALAC Statement on the Draft Final Report on Universal Acceptance of > > IDN > > TLDs* > > > > The ALAC is of the view that the implementation of policies that > > support the Universal Acceptance of IDNs is crucial for the success > > and uptake of IDN gTLDs and IDN ccTLDs. We therefore support the > > recommendations of the JIG in its Final Report on Universal Acceptance > > of IDN TLDs. We urge ICANN to leverage its influence and resources to > > promote and support the universal acceptance of IDN TLDs broadly as > > described in the report towards ensuring user access and utilization > > of IDN TLDs as well as a consistent, predictable and secure user experience. > > ---- end > > > > Comments welcome on the wiki here: > > https://community.icann.org/display/alacpolicydev/At-Large+Draft+Final > > > +Report+on+Universal+Acceptance+of+IDN+TLDs+Workspace?focusedCom > mentId > > =41893594#comment-41893594 > > > > Thanks. > > > > Rinalia > > > > On Fri, Jun 28, 2013 at 9:11 AM, Rinalia Abdul Rahim < > > rinalia.abdulrahim(a)gmail.com> wrote: > > > >> Dear Members of the At-Large Community and IDN Working Group, > >> > >> Your views are kindly requested on the JIG Draft Final Report on > >> Universal Acceptance of IDN TLDs. Specifically, > >> > >> 1. Should the general recommendations of the report be supported? > >> 2. Are there specific issues of concern within the report that should > >> be raised? > >> > >> If you have views, please share them via the At-Large Policy > >> Development workspace by 7 July 2013. > >> > >> At-Large Policy Development workspace link: > >> > >> https://community.icann.org/display/alacpolicydev/At-Large+Draft+Fina > >> l+Report+on+Universal+Acceptance+of+IDN+TLDs+Workspace > >> * > >> Informational Resurces* > >> > >> Full Report Link: > >> http://ccnso.icann.org/workinggroups/idn-tld-acceptance-final-25jun13 > >> -en.pdf[PDF, 135 KB] > >> > >> [Extract on General Recommendations] > >> > >> 1. IDN TLD operators (including IDN ccTLD, IDN gTLD and IDN > gTLDAccredited Registrars) are recommended to support Universal > Acceptance of > >> IDN TLDs in their own systems. Part of this recommendation is that > >> ICANN's IDN Guidelines be updated to include provisions for IDN > TLDregistries and registrars to support the Universal Acceptance of IDN TLDs > >> within their own systems (i.e. for registration systems and services to > >> accept name server records, child hosts, contact information with IDN > TLDs) > >> 2. ICANN should allocate specific resources for the advocacy of > >> Universal Acceptance beyond the development of informational > materials and > >> toolkits. > >> 3. ICANN should develop of informative reference materials for new > IDN > >> TLDs (including gTLD and ccTLD) to handle issues of Universal > >> Acceptance > >> 4. ICANN initiates efforts, lead by staff, with participation from the > >> community, for further studies to investigate the scope of the issue and > >> what other services or actions could be taken by ICANN to support the > >> Universal Acceptance of IDN TLDs beyond outreach and awareness > >> campaigns > >> > >> > >> Best regards, > >> > >> Rinalia > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: ICANN At-Large Staff <staff(a)atlarge.icann.org> > >> Date: Wed, Jun 26, 2013 at 6:32 AM > >> Subject: [ALAC-Announce] FW: ICANN News Alert -- Draft Final Report > >> on Universal Acceptance of IDN TLDs > >> To: "alac-announce(a)atlarge-lists.icann.org" < > >> alac-announce(a)atlarge-lists.icann.org> > >> > >> > >> > >> > [http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> > >> News Alert > >> > >> http://www.icann.org/en/news/announcements/announcement-2- > 25jun13-en. > >> htm > >> > >> ________________________________ > >> Draft Final Report on Universal Acceptance of IDN TLDs > >> > >> 25 June 2013 > >> > >> > >> > >> Forum Announcement: Comment Period Opens on Date: 25 June 2013 > >> Categories/Tags: > >> > >> * Top-Level Domains > >> * Policy Processes > >> * Transparency/Accountability > >> > >> > >> Purpose (Brief): The joint ccNSO-GNSO IDN working Group (JIG) seeks > >> input from the community on its draft Final Report on Universal > >> Acceptance of IDN TLDs. The draft includes recommendations to the > >> ccNSO and GNSO Councils for further action to resolve policy and > >> other relating to the universal acceptance of IDN TLDs The Working > >> expects to finalize and publish its Final Report, and submit their > >> report, after taking into account the comments received. > >> Public Comment Box Link: > >> http://www.icann.org/en/news/public-comment/idn-tld-acceptance- > final- > >> 25jun13-en.htm > >> > >> > >> > >> This message was sent to matt.ashtiani(a)icann.org<mailto: > >> matt.ashtiani(a)icann.org> from: > >> > >> ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 > >> > >> > >> Email Marketing by > >> [http://app.icontact.com/images/icontact_tryFree.gif] < > >> http://www.icontact.com/a.pl/144186> > >> > >> > >> Manage Your Subscription < > >> http://app.icontact.com/icp/mmail- > mprofile.pl?r=24564788&l=6333&s=BCA > >> 3&m=915394&c=165637 > >> > > >> > >> _______________________________________________ > >> ALAC-Announce mailing list > >> ALAC-Announce(a)atlarge-lists.icann.org > >> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce > >> > >> At-Large Official Site: http://www.atlarge.icann.org > >> > >> > > _______________________________________________ > > APAC-Discuss mailing list > > APAC-Discuss(a)atlarge-lists.icann.org > > https://atlarge-lists.icann.org/mailman/listinfo/apac-discuss > > > > Homepage for the region: http://www.apralo.org > _______________________________________________ > APAC-Discuss mailing list > APAC-Discuss(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/apac-discuss > > Homepage for the region: http://www.apralo.org > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.2904 / Virus Database: 3204/6448 - Release Date: 06/28/13

1 0

At-Large Community Views Requested on Draft Final Report on Universal Acceptance of IDN TLDs
by Rinalia Abdul Rahim July 2, 2013

July 2, 2013

Dear Members of the At-Large Community and IDN Working Group, Your views are kindly requested on the JIG Draft Final Report on Universal Acceptance of IDN TLDs. Specifically, 1. Should the general recommendations of the report be supported? 2. Are there specific issues of concern within the report that should be raised? If you have views, please share them via the At-Large Policy Development workspace by 7 July 2013. At-Large Policy Development workspace link: https://community.icann.org/display/alacpolicydev/At-Large+Draft+Final+Repo… * Informational Resurces* Full Report Link: http://ccnso.icann.org/workinggroups/idn-tld-acceptance-final-25jun13-en.pd…, 135 KB] [Extract on General Recommendations] 1. IDN TLD operators (including IDN ccTLD, IDN gTLD and IDN gTLDAccredited Registrars) are recommended to support Universal Acceptance of IDN TLDs in their own systems. Part of this recommendation is that ICANN's IDN Guidelines be updated to include provisions for IDN TLD registries and registrars to support the Universal Acceptance of IDN TLDs within their own systems (i.e. for registration systems and services to accept name server records, child hosts, contact information with IDN TLDs) 2. ICANN should allocate specific resources for the advocacy of Universal Acceptance beyond the development of informational materials and toolkits. 3. ICANN should develop of informative reference materials for new IDN TLDs (including gTLD and ccTLD) to handle issues of Universal Acceptance 4. ICANN initiates efforts, lead by staff, with participation from the community, for further studies to investigate the scope of the issue and what other services or actions could be taken by ICANN to support the Universal Acceptance of IDN TLDs beyond outreach and awareness campaigns Best regards, Rinalia ---------- Forwarded message ---------- From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wed, Jun 26, 2013 at 6:32 AM Subject: [ALAC-Announce] FW: ICANN News Alert -- Draft Final Report on Universal Acceptance of IDN TLDs To: "alac-announce(a)atlarge-lists.icann.org" < alac-announce(a)atlarge-lists.icann.org> [http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-25jun13-en.htm ________________________________ Draft Final Report on Universal Acceptance of IDN TLDs 25 June 2013 Forum Announcement: Comment Period Opens on Date: 25 June 2013 Categories/Tags: * Top-Level Domains * Policy Processes * Transparency/Accountability Purpose (Brief): The joint ccNSO-GNSO IDN working Group (JIG) seeks input from the community on its draft Final Report on Universal Acceptance of IDN TLDs. The draft includes recommendations to the ccNSO and GNSO Councils for further action to resolve policy and other relating to the universal acceptance of IDN TLDs The Working expects to finalize and publish its Final Report, and submit their report, after taking into account the comments received. Public Comment Box Link: http://www.icann.org/en/news/public-comment/idn-tld-acceptance-final-25jun1… This message was sent to matt.ashtiani(a)icann.org<mailto: matt.ashtiani(a)icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] < http://www.icontact.com/a.pl/144186> Manage Your Subscription < http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91… > _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce At-Large Official Site: http://www.atlarge.icann.org

2 3

Motions to approve RoP Adjunct Documents 01 and 04.
by Alan Greenberg July 1, 2013

July 1, 2013

I submit the following two motions as previously discussed. Once seconded, I request that the Chair initiate online votes on the two motions. Alan ===================== Whereas the ALAC approved a revised Rules of Procedure on 03 April 2013 and to become effective several associated documents also need to be approved by the ALAC It is resolved that the ALAC approves the ALAC Rules of Procedure Adjunct Document 01 - Position Description for ALAC Members, Liaisons and Appointees dated 2013-06-19. The document is linked at https://community.icann.org/display/atlarge/Rules+of+Procedure. ------------ Whereas the ALAC approved a revised Rules of Procedure on 03 April 2013 and to become effective several associated documents also need to be approved by the ALAC It is resolved that the ALAC approves the ALAC Rules of Procedure Adjunct Document 04 - At-Large Structure Framework dated 2013-06-19. He document is linked at https://community.icann.org/display/atlarge/Rules+of+Procedure.

2 1

Re: [ALAC] Decertification of ALS: Internet Users Network (Tokyo)
by Alan Greenberg July 1, 2013

July 1, 2013

I note that as per our practice to make ALS certification votes confidential and not reveal how each ALAC member votes, I presume that the same will be true for decertification votes. Alan At 01/07/2013 02:45 PM, Alan Greenberg wrote: >I make the following motion and request a seconder. Once seconded, I >request that the Chair initiate an online vote. > >Alan >================== >Whereas the official representative of the At-Large Structure: >Internet Users Network (Tokyo) has requested that the At-Large >Structure (ALS) be decertified as a preparatory step to the Internet >Users Network (Tokyo) being dissolved; > >Whereas the ALAC has documented the due diligence investigating this >decertification as per >https://community.icann.org/display/atlarge/Internet+Users+Network+-+Tokyo+…; > >Whereas the ALAC allows for such decertification as per Section II.7 >of the At-Large Framework Formation >(http://www.atlarge.icann.org/framework.htm#CertificationProcess) > >It is resolved that the ALAC decertifies the Internet Users Network >(Tokyo) as an ICANN At-Large Structure. Such decertification is >subject ICANN Board Reconsideration as per Article IV, Section 2 of >the ICANN Bylaws and is done without prejudice to any future >re-application of this organization for certification as an ALS, or >the application for ALS certification of any new group bearing the same name. > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

1 0

Decertification of ALS: Internet Users Network (Tokyo)
by Alan Greenberg July 1, 2013

July 1, 2013

I make the following motion and request a seconder. Once seconded, I request that the Chair initiate an online vote. Alan ================== Whereas the official representative of the At-Large Structure: Internet Users Network (Tokyo) has requested that the At-Large Structure (ALS) be decertified as a preparatory step to the Internet Users Network (Tokyo) being dissolved; Whereas the ALAC has documented the due diligence investigating this decertification as per https://community.icann.org/display/atlarge/Internet+Users+Network+-+Tokyo+…; Whereas the ALAC allows for such decertification as per Section II.7 of the At-Large Framework Formation (http://www.atlarge.icann.org/framework.htm#CertificationProcess) It is resolved that the ALAC decertifies the Internet Users Network (Tokyo) as an ICANN At-Large Structure. Such decertification is subject ICANN Board Reconsideration as per Article IV, Section 2 of the ICANN Bylaws and is done without prejudice to any future re-application of this organization for certification as an ALS, or the application for ALS certification of any new group bearing the same name.

3 2