January 2014 - Gnso-contactinfo-pdp-wg

Re: [gnso-contactinfo-pdp-wg] Re: GNSO Council Confirmation of Co-Chairs
by Julie Hedlund Jan. 23, 2014

Jan. 23, 2014

Dear Ching, The Confirmation is on a revised version of the agenda that Glen has just sent. I have copied it below. It is item 3.3 on the Consent Agenda. Best regards, Julie Proposed Agenda for the GNSO Council Teleconference 23 January 2013 This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf%20> > For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 18:00 UTC http://tinyurl.com/otro8aq Coordinated Universal Time 18:00 UTC 10:00 Los Angeles; 13:00 Washington; 18:00 London; 19:00 Brussels; 02:00 Perth Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u <http://stream.icann.org:8000/gnso.m3u> Item 1: Administrative matters (10 mins) 1.1 Roll Call 1.2 Statement of interest updates Bret Fausett https://community.icann.org/display/gnsosoi/Bret+Fausett+SOI 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meetings 20 November 2013 <http://gnso.icann.org/mailing-lists/archives/council/msg15531.html> part 1 and part 2 <http://gnso.icann.org/mailing-lists/archives/council/msg15532.html> will be posted as approved on 23 January 2014. Minutes of the Council meeting 12 December 2013 <http://gnso.icann.org/mailing-lists/archives/council/msg15533.html> will be posted as approved on 23 January 2014. Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List <http://gnso.icann.org/meetings/projects-list.pdf> and Action List <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> . Comments or questions arising. Item 3: Consent agenda (5 mins) 3.1 Approve Council Recommendations Report on protection of IGO-INGO names and acronyms to the ICANN Board <http://gnso.icann.org/en/drafts/council-board-igo-ingo-21jan14-en.pdf> . 3.2 Confirm Don Blumenthal RySG as Chair and Steve Metalitz - IPC and Graeme Bunton - RrSG as Vice-Chairs for the Privacy & Proxy Services Accreditation Issues PDP working group. 3.3 Confirm Chris Dillon NCSG and Rudi Vansnick NPOC as co-chairs of the Translation and Transliteration of Contact Information PDP Working Group. Item 4: MOTION Metrics and Reporting Working Group Charter (15 mins) The 2010 Registration Abuse Policies Working Group (RAPWG) identified the an issue relating to Uniformity of Reporting which it described as ³need for more uniformity in the mechanisms to initiate, track, and analyze policy-violation reports.² The RAPWG recommended in its Final Report that ³the GNSO and the larger ICANN community in general, create and support uniform [problem-] reporting [and report-tracking] processes.² The GNSO Council recommended the creation of an Issue Report <http://gnso.icann.org/en/issues/uofr-final-31mar13-en.pdf> to further research metrics and reporting needs with the aim of improving the policy development process. The report created by ICANN Staff outlined accomplishments regarding reporting and metrics by the Contractual Compliance function and it also reviewed other reporting sources that may be of relevance. The GNSO Council subsequently adopted a recommendation to form a non-PDP Working Group tasked with exploring opportunities for developing reporting and metrics processes and/or appropriate standardized methodologies that could better inform fact-based policy development and decision making. Here the Council vote on whether to approve the Charter of the Metrics and Reporting Working Group. 4.1 - Review the Motion 4.2 - Discussion 4.3 - Vote (voting threshold simple majority vote of each house) Item 5: INPUT & DISCUSSION Prospective improvements to the Policy Development Process (15 mins) The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community. The Council has previously discussed a paper prepared by ICANN staff <http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf> on potential improvements to the PDP process. The discussion is now encapsulated in a table form which has been revised through various discussions at council meetings and on email lists. The document now also includes reference to the related recommendations of the ATRT2. Here the Council will aim to agree concrete next steps including the requirement to form a group to continue this work, particularly with a focus on items 3 & 5 in the table. 5.1 Review of table of prospective PDP Improvements <http://gnso.icann.org/en/drafts/pdp-improvements-table-16jan14-en.pdf> (Marika Konings) 5.2 Discussion 5.3 Next steps Item 6: UPDATE GAC Engagement the work of the Joint GAC / GNSO Consultation Group (15 mins) Here the Council will receive an update and discuss any action going forward. 6.1 Status update (Jonathan Robinson) 6.2 Discussion 6.3 Next steps Item 7: Update Forthcoming review of the GNSO (15 mins) As part of a periodic review process that is built into the ICANN model, ICANN board initiated reviews of the GNSO (and the GNSO Council and related functions) are expected. In order to be informed and effectively prepared for this work, we have begun to engage with the body that commissions such reviews (the structural improvements committee) through its chair, Ray Plazk. The Council will track the planning work of the SIC and, where appropriate; provide relevant input to the process. We will also prepare to undertake a form of self-review in a similar format to that which we expect to arise out of the work of the SIC. A self-review will ensure that we are not only prepared for the board initiated work but also able to flag areas for potential improvement in as timely as possible a manner. 7.1 Update (Jennifer Wolfe) 7.2 Discussion 7.3 Next steps Item 8: DISCUSSION International Internet Governance Issues (15 mins) Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. Item 9: UPDATE & DISCUSSION Planning for Singapore (15 mins) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, David Cake will lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council¹s proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board. 9.1 Update (David Cake) 9.2 Discussion 9.3 Next steps Item 10: Any Other Business (10 mins) * Proposal to review SSAC reports and determine whether or not any recommendations impact on GNSO Consensus Policy Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A <http://www.icann.org/en/about/governance/bylaws#AnnexA> ): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4 <http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf> ) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting¹s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 15:00 ---------------------------------------------------------------------------- California, USA (PDT <http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html> ) UTC-7+1DST 10:00 Iowa City, USA (CST <http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00> ) UTC-6+1DST 12:00 New York/Washington DC, USA (EST) UTC-4+1DST 13:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 16:00 Montevideo, Uruguay (UYST <http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html> ) UTC-2+1DST 16:00 Buenos Aires, Argentina (ART <http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html> ) UTC-3+0DST 15:00 London, United Kingdom (BST) UTC+0DST 18:00 Bonn, Germany (CET) UTC+1+0DST 19:00 Stockholm, Sweden (CET) UTC+1+0DST 19:00 Cairo, Egypt, (EET) UTC+2+0DST 20:00 Istanbul, Turkey (EEST) UTC+2+0DST 20:00 Ramat Hasharon, Israel(IST <http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel. html> ) UTC+2+0DST 20:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 02:00 next day Perth, Australia (WST <http://timeanddate.com/library/abbreviations/timezones/au/wst.html> ) UTC+8+0DST 02:00 next day ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com <http://www.timeanddate.com/> http://tinyurl.com/otro8aq Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org <http://gnso.icann.org/> From: Ching Chiao <ching.chiao(a)gmail.com> Date: Thursday, January 23, 2014 2:47 AM To: Rudi Vansnick <rudi.vansnick(a)isoc.be> Cc: Julie Hedlund <julie.hedlund(a)icann.org>, "Dillon, Chris" <c.dillon(a)ucl.ac.uk> Subject: Re: [gnso-contactinfo-pdp-wg] Re: GNSO Council Confirmation of Co-Chairs I did not see contact-info on the Council meeting agenda http://gnso.icann.org/en/meetings/agenda-council-23jan14-en.htm Will speak to Jonathan and see if we can get Council to approve the appointment of Co-Chairs. Thanks! Ching On Thu, Jan 23, 2014 at 3:38 PM, Rudi Vansnick <rudi.vansnick(a)isoc.be> wrote: > Dear Julie, Chris, > > I do not see any problem with regards a report to be delivered the 27th > February. Based on our workplace we could certainly give status and the > progress made in the WG. Also, we will be able to present the schedule for the > outreach at the Singapore ICANN meeting. > > Till this afternoon. > > Rudi Vansnick > NPOC chair Policy Committee > NPOC treasurer > rudi.vansnick(a)npoc.org > Tel : +32 (0)9 329 39 16 <tel:%2B32%20%280%299%20329%2039%2016> > Mobile : +32 (0)475 28 16 32 <tel:%2B32%20%280%29475%2028%2016%2032> > www.npoc.org <http://www.npoc.org> > > Op 22-jan.-2014, om 22:10 heeft Julie Hedlund <julie.hedlund(a)icann.org> het > volgende geschreven: > >> Dear Chris, >> >> I apologize if I wasn't clear below, but the update is provided by a member >> of the GNSO Council in this case the PDP WG's liaison to the Council, who >> is Ching Chao. That is one of the purposes of having a liaison. Of course, >> generally what this means is that the Co-Chairs provide the update to the >> Liaison for the Liaison to then provide to the Council. So, in this case you >> and Rudi could work together (with staff support) to develop a report/update >> for Ching to provide. This could be in the form of a brief statement, >> slides, or whatever you think is most helpful. It may also be possible for >> you and Rudi to be available on the Council call to answer questions that >> Ching might not be able to field, if the Council agrees. >> >> I hope this is more clear, but please let me know if you have questions. >> >> Best regards, >> Julie >> >> From: <Dillon>, Chris <c.dillon(a)ucl.ac.uk> >> Date: Wednesday, January 22, 2014 4:01 PM >> To: Julie Hedlund <julie.hedlund(a)icann.org>, Rudi Vansnick >> <rudi.vansnick(a)isoc.be> >> Cc: "Dillon, Chris" <c.dillon(a)ucl.ac.uk>, "gnso-contactinfo-pdp-wg(a)icann.org" >> <gnso-contactinfo-pdp-wg(a)icann.org> >> Subject: Re: GNSO Council Confirmation of Co-Chairs >> >> Dear Julie, >> >> Thank you for the update. >> >> My instinct is to ask Rudi to give an update on 27 Feb. - are you happy with >> that, Rudi? >> >> Regards, >> >> Chris. >> == >> Research Associate in Linguistic Computing, Centre for Digital Humanities, >> UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 >> <tel:%2B44%2020%207679%201599> (int 31599) ucl.ac.uk/dis/people/chrisdillon >> <http://ucl.ac.uk/dis/people/chrisdillon> >> >> On 22 Jan 2014, at 18:45, Julie Hedlund <julie.hedlund(a)icann.org> wrote: >> >>> Dear Chris, Rudi, and PDP WG Members, >>> >>> Per the Working Group Guidelines the Chairs of Working Groups must be >>> confirmed by their Chartering Organization in this case the GNSO Council. >>> Specifically, the Guidelines say, "Once selected, a Working Group Chair will >>> need to be confirmed by the Chartering Organization (CO). The newly elected >>> Chair will act on a provisional basis until the Chartering Organization has >>> confirmed the appointment. If there are any objections to the selected >>> Chair, the CO will conduct a vote to establish whether there is sufficient >>> support for the selected Chair according to the voting procedures of the CO. >>> If not, the Working Group will be requested to reconsider their choice for >>> Chair and return to the CO with a new proposal." >>> >>> The usual procedure is to include the confirmation of chairs as an item on >>> the consent agenda of a GNSO Council meeting, which means that it is not >>> subject to a vote unless there is an objection. Accordingly, the >>> confirmation of Chris and Rudi as Co-Chairs has been added to the consent >>> agenda for the Council meeting to be held tomorrow, 23 January. >>> >>> Please note that if the Co-Chairs would like updates on the work of the PDP >>> WG to be provided to the Council, per the Working Group Guidelines the PDP >>> WG Liaison to the Council (in this case Ching Chao) will provide them if >>> requested, either via email or during a Council meeting. Although it is too >>> late to get an update on the agenda for tomorrow's Council meeting, the PDP >>> WG may consider whether to ask Ching to provide an update during the Council >>> meeting on 27 February, or if preferable, via email to the Council list. >>> >>> Please let me know if you have any questions and I look forward to talking >>> to you tomorrow. >>> >>> Best regards, >>> >>> Julie >>> >>> Julie Hedlund, Policy Director >> > -- Ching Chiao Founder and CEO www.Brandma.co +886.918.211372 +86.135.20187032

1 0

Attendance and recording: Translation and Transliteration of Contact Information PDP - Thursday 16 January 2014
by Julia Charvolen Jan. 16, 2014

Jan. 16, 2014

Dear All, The next Translation and Transliteration of Contact Information PDP Charter Drafting Team is scheduled for Thursday 23 January 2014 at 1400 UTC Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Charter Drafting Team call held on Thursday 16 January 2014 at 1400 UTC: http://audio.icann.org/gnso/gnso-transliteration-contact-20140116-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar#<http://gnso.icann.org/en/group-activities/calendar#may>jan The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Wanawit Ahkuputra – Individual Peter Dernbach - IPC Chris Dillon - NCSG Amr Elsadr – NCUC Jim Galvin – SSAC Sarmad Hussain – No SOI Yoav Keren – RrSG Pitinan Koarmornpatna – Individual Patrick Lenihan - NCUC Petter Rindforth - IPC Rudi Vansnick – NPOC Mae Suchayapim Siriwat – No SOI Jennifer Chung - No SOI Peter Green - No SOI Apologies: Ephraim Kenyanito - NCUC ICANN staff: Lars Hoffman Steve Sheng Julia Charvolen ** Please let me know if your name has been left off the list ** Wiki page: http://tinyurl.com/mpwxstx Thank you. Kind regards, Julia Charvolen For GNSO Secretariat Adobe Chat Transcript for Thursday 16th January 2013: Lars Hoffmann:Welcome to the T&T PDP Working Group onThursday 16 January 2014 Amr Elsadr:Hi. Dialling in now. Pitinan Kooarmornpatana:Hi working group Peter Dernbach:Hi everyone. Jennifer Chung:Hello all Peter Green-CONAC:Hi all Amr Elsadr:Hi. I should be on the call now, but can't hear anything. Chris Dillon:Hello, all Pitinan Kooarmornpatana:yes i can hear you Amr Elsadr:Thnx Julia. :) Julia Charvolen:Sure :) Rudi Vansnick:hello all Rudi Vansnick:sorry for being a bit late ;-) Lars Hoffmann:Morning all. Julie will not be joining as you might recall. Should we start the call? Amr Elsadr:Hi Rudi. It doesn't look like we've started yet. Chris Dillon:Let's start Rudi Vansnick:go ahead Chris Julia Charvolen:Steve Sheng joined the phone bridge Peter Dernbach:I updated my SOI Peter Dernbach:I mean I successfully uploaded my SOI Rudi Vansnick:there have been updates doen in the past week I thought Petter Rindforth:can you show page 1 of this again? Rudi Vansnick:sorry i was silent as I was still in another meeting Julia Charvolen:Yoav Keren joined the Adobe Connect Petter Rindforth:yes Yoav Keren:hi all Julia Charvolen:Sarmad Hussain joined the phone bridge Amr Elsadr:@Jim: +1 Amr Elsadr:Hey Yoav. Hope you're well. Rudi Vansnick:will be very helpful Rudi Vansnick:we need to decide anyway next week Amr Elsadr:+1 Rudi Vansnick:let's put it on the wiki perhaps Rudi Vansnick:i copied the text into a local notepâd, so eventually i can send it to the list just after the call Rudi Vansnick:@Amr: + 1 Lars Hoffmann 2:Sorry. got dropped off th line. I wanted to add that we can always send out additional letters in case additional questions come up and/or we would like further details from other SG/C or AC/SO Rudi Vansnick:Lars can you put on the list of questions of last week call Amr Elsadr:Thanks Lars, but I would recommend we give the WG at least a week after getting an initial draft of the letter to suggest edits. Getting feedback once is sometimes challenging. Asking for a second round of feedback might be quite ambitious. :) Rudi Vansnick:What is contact information (review and expand on the taxonomies noted above)?Why are we doing this?; is this particular feature necessary?Who gets access to what?Who are the stakeholders?; who is affected? and what do they want (linking back to What)?How much would a particular feature cost?When would policy come into effect?What should be mandatory? Lars Hoffmann 2:Thank you Rudi - my internet is rather slow here. Amr Elsadr:Where are these questions on the Wiki? The page for questions and taxonomies appears blank. Rudi Vansnick:Who are the stakeholders?; who is affected? and what do they want (linking back to What)? Lars Hoffmann 2:Finally, staff have created wiki pages for each of the proposed questions. These will be filled in as information is added:1. What is contact information & What Taxonomies are Available?2. Why are we doing this? Is this particular feature necessary?3. Who gets access to what information?4. Who are the stakeholders? Who is affected and what do they want?5. How much would a particular feature cost and how to weigh the costs versus the benefits?6. When would policy come into effect?7. What should be mandatory? Lars Hoffmann 2:Here are the URLs from the questions Rudi Vansnick:https://community.icann.org/display/tatcipdp/09+January+2014 Lars Hoffmann 2:https://community.icann.org/pages/viewpage.action?pageId=44958769 Lars Hoffmann 2:https://community.icann.org/pages/viewpage.action?pageId=44960108 Lars Hoffmann 2:https://community.icann.org/pages/viewpage.action?pageId=44960114 Peter Dernbach:https://community.icann.org/pages/viewpage.action?pageId=44958769 Amr Elsadr:Ah..., thanks Rudi. Peter Dernbach:+1 Sarmad Hussain: cost of T&T depends on accuracy requirements Rudi Vansnick:Jim do you have any information to add to the stakeholders definition ? Sarmad Hussain:so as a precursor we need to determine what level of accuracy is needed Amr Elsadr:@Sarmad: accuracy requirements depend on some RAA specs like validation. Sarmad Hussain:do RAAs have any specs on T&T validation? Amr Elsadr:Not specific to T&T, but validation of contact info in the whois. Sarmad Hussain:their requirements are mostly on original lang data validation Jim Galvin:@rudi not at this time Lars Hoffmann 2:FYI - i just updated the question page:https://community.icann.org/pages/viewpage.action?pageId=44960091 Amr Elsadr:Thanks Lars. Amr Elsadr:Yes Chris..., very true. The WG could recommend that it is not desirable to have a policy requiring T&T. Amr Elsadr:I agree Chris. :) Amr Elsadr:I wouldn't mind discussions that would lead to me changing my mind though. :) WANAWIT Ahkuputra:Fully agree on the GAC role regaridng that issue Peter Dernbach:I agree on trying to solicit opinions from GAC. Rudi Vansnick:exactly Lars, we need to have a small slot to discuss this with GAC Rudi Vansnick:in Singapore Sarmad Hussain:+1 on GAC role Pitinan Kooarmornpatana:+1 on GAC role Amr Elsadr:Thanks Lars. Perhaps a customized letter to the GAC asking for individual responses from GAC members. Sarmad Hussain:+1 on discussion with GAC in sg Amr Elsadr:And wouldn't the NSO be covered in the regular AC/SO letter? Peter Dernbach:@ Amr +1 re: requesting individual responses WANAWIT Ahkuputra:I could help in laise and explain to GAC members. Amr Elsadr:Thanks Wanawit. Rudi Vansnick:what about other stakeholders ? Peter Dernbach:Thanks Wanawit. Lars Hoffmann 2:@Amr - i think that is great idea. and the NSP would be covered too. But again they do not always provide coordinated feedback, so reaching out to individual NSO members might be very useful too. Pitinan Kooarmornpatana:additional to that , for the Thai GAC team, we actually in the process to make paper regarding to this will share with the WG soon, probably before the next meeting for the Thai Addressing System Lars Hoffmann 2:GNSO Staff could also reach out to both NSO and GAC staff, if you think tha tmight be useful Amr Elsadr:Thanks Lars. That sounds great. Amr Elsadr:There are ongoing attempts between the gnso council and GAC to increase early participation in the GNSO's PDP. This WG might make for an interesting case study. Lars Hoffmann 2:@Amr - i think the Policy and Implementation Working Group has also already tried to do some more targetted outreach to the GAC so we could compare notes with that Group on their approach/success too. Petter Rindforth:I can reach out to FICPI - intl IP-attorney organization, just to get their inputs Amr Elsadr:@Lars: right you are. There are some GAC members who are on that WG who are also trying to help. Rudi Vansnick:there is a GNSO call next week, we could launch the question in that meeting WANAWIT Ahkuputra:UPU - Universal Postal Union and UNGEGN - United Nations Group of Experts on Geographical Names are impotant stake holder that relate to the address system Amr Elsadr:@Rudi: Probably not the forum for this, although the WG liaison to the council could bring up that atteptes are being made to get GAC feedback. Lars Hoffmann 2:I think you are right, Amr Rudi Vansnick:@Amr: we can ask our NCSG councillors to add this question to the meeting Amr Elsadr:Lars posted the questions on number "4". :) Amr Elsadr:Names also affect addresses in Arabic, because most street names (at least in Egypt) are named after people. Peter Green-CONAC:In Chinese, we also have names of streets named after a person's name Rudi Vansnick:i'm just wondering how some registrars are handling these problems when they register a domain name in the actual whois Rudi Vansnick:they have to translate anyway Peter Dernbach:Thank you Chris and all! Lars Hoffmann 2:due to my travels i might send actions items and other information late on friday or early on monday. i hope that is ok. Amr Elsadr:thanks Chris and Rudi. Thanks everyone. Peter Green-CONAC:Thanks Chris, and thanks all Lars Hoffmann 2:thanks everybody! Jim Galvin:thx and bye Peter Green-CONAC:bye Pitinan Kooarmornpatana:Thanks Christ and all , bye Jennifer Chung:Thank you all! WANAWIT Ahkuputra:Thanks Chris and All Sawasdee Julia Charvolen:Recordings are stopped Chris Dillon:Goodbye, all Rudi Vansnick:see you all next week ! Rudi Vansnick:enjoy the rest of the week

1 0

Examples of addresses
by Dillon, Chris Jan. 16, 2014

Jan. 16, 2014

Dear colleagues, I would like to start a collection of international addresses on this list. Many will be in non-Latin scripts, but some may be using the Latin alphabet perhaps with lots of diacritics (accents) or in some other way. I hope the following Japanese example, taken at random, makes this suggestion clear: The address is how it appears at the bottom of the organization’s website, www.nii.ac.jp<http://www.nii.ac.jp> : 国立情報学研究所　テ101-8430　東京都千代田区一ツ橋2－1－2 On English pages of the same site, for example, www.nii.ac.jp/en<http://www.nii.ac.jp/en> , it appears as: National Institute for Informatics 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430 Notes The name of this organization has a well established English translation and acronym (NII). It is not always clear whether an organization prefers its long name or its acronym. Many/All of the divisions and other parts of the organization also have established English translations. What should the policy be when an organization name has no established English translation? The rest of the address is transliterated using some form of Hepburn Romanization. Strictly speaking Tokyo should be Tōkyō. See here for further information: http://en.wikipedia.org/wiki/Hepburn_romanization Japanese addresses are not normally translated. I shall translate this address to illustrate the point and for your amusement: 2-1-2 One Bridge, Thousand Generations Field Ward, East Capital Metropolis, 101-8430 Each speaker of Japanese would probably produce a different rendering. It is interesting that the ku in Chiyoda-ku is not usually translated as “ward”. Note also the hyphen. The order of the address is more or less reversed. Literally in Hepburn it would be: Kokuritsu Jōhō Kagaku Kenkyūjo 101-8430 Tōkyōto Chiyodaku Hitotsubashi 2-1-2 I have added spaces and capital letters. テcomes before the Japanese postcode. 研究所 may be romanized as kenkyūjo or kenkyūsho. NII prefers the former, but machine transliteration would produce two possibilities if it did not know this specific organization. There are some other Romanizations in fairly common use in Japan e.g. Kunrei-siki and these cause confusion. One may see, for example, Hitotubasi instead of Hitotsubashi and frequently an address in Hepburn may have a couple of spellings borrowed from another system. I am not aware of a Romanization that officially spells out long ō vowels as in e.g. jōhō as ou, but one sees this frequently e.g. jouhou. The officially Hepburn way of doing it, if one has no access to macrons is joohoo. One also sees jôhô (borrowed from Kunrei-siki). I hope this will be a good way of discovering current practice and issues. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) ucl.ac.uk/dis/people/chrisdillon

6 10

Interesting upcoming study
by Rudi Vansnick Jan. 14, 2014

Jan. 14, 2014

Dear colleague’s, Just got the information link below. Study to Evaluate Available Solutions for the Submission and Display of Internationalized Contact Data As part of the process to implement the internationalized registration data recommendations of the ICANN WHOIS review team, ICANN commissioned a study to document and evaluate the potential solutions submitting or displaying contact data in non-ASCII (American Standard Code for Information Interchange) character sets. In this wiki we provide some background and outline the requirements for the study. Kind regards, Rudi Vansnick NPOC chair Policy Committee NPOC treasurer rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32 www.npoc.org

3 2

Attendance and Recording Translation and Transliteration of Contact Information PDP Working Group meeting - 9 January 2014
by Glen de Saint Géry Jan. 9, 2014

Jan. 9, 2014

Dear All, The next meeting of this group is scheduled for Thursday, 16 January 2014 at 14:00 UTC. Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Charter Drafting Team call held on Thursday 9 January 2014 at 14:00 UTC at: http://audio.icann.org/gnso/gnso-transliteration-contact-20140109-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar#jan The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Chris Dillon - NCSG - co-chair Rudi Vansnick - NPOC -co-chair Amr Elsadr - NCUC Yoav Keren - RrSG Petter Rindforth - IPC Jim Galvin - SSAC Peter Dernbach - IPC Pitinan Koarmornpatna - GAC Sarmad Hussain - SSAC Jennifer Chung - RySG Peter Green - NCSG Ahkuputra Wanawit - GAC Vinay Kumar Singh - Individual Anthony Oni - NCUC Apologies: none ICANN staff: Julie Hedlund Lars Hoffman Mary Wong Glen de Saint Gery ** Please let me know if your name has been left off the list ** Wiki page: http://tinyurl.com/mpwxstx Thank you. Kind regards, Glen Adobe Chat Transcript for Thursday 9 January 2014: Glen de Saint Gery:Welcome to the Translation and Transliteration of Contact Information PDP Working Group call Julie Hedlund:Hello everyone and welcome! Peter Dernbach:Hello everyone. Happy New Year! Rudi Vansnick:hello everone, also a happy new year Amr Elsadr:Hi all. Dialling in now. Julie Hedlund:Yes, Happy New Year everyone! Chris Dillon:Happy New Year! Amr Elsadr:On the call. Hello again. Lars Hoffmann:See gaps for missing SOIs: https://community.icann.org/x/WDd-Ag Pitinan Kooarmornpatana:I support Sarmad Hussain:yes Rudi Vansnick:78 on 13 agreed Sarmad Hussain:I support Rudi Vansnick:sorry 7 on 13 Wanawit Ahkuputra:I support Rudi Vansnick:makes it 8 Rudi Vansnick:makes it 9 on 13 Jim Galvin:Thanks Lars for the pointer to the SOIs. I'll submit one today. Jim Galvin:For the record, I am representing RySG, not the SSAC. This is incorrectly stated on thecommunity members page. Rudi Vansnick:OK Jim we take note and will ask for the modification Peter Dernbach:Lars: I just resent my SOI that I had sent on 23 December. Sarmad Hussain:what is the conference ID for calling in? Chris Dillon:Contact Glen de Saint Gery:Sarmad if you send me your number we can call you otherwise pass word is CONTACT Sarmad Hussain:thx Rudi Vansnick:do we need to indicate who's the liaison to the GNSO within this WG ? Amr Elsadr:Also important to note that the WG should request input from the different SOs/SGs/Constituencies/ACs as well. Peter Dernbach:I thought Ching Chiao was the GNSO liaison for this WG. Amr Elsadr:If I'm not mistaken, Ching has volunteered to be the Council liaison to this WG. Amr Elsadr:Peter types faster than I do. :) Peter Dernbach:;-) Rudi Vansnick:thanks Peter, just ot be sure we did not forgot to officialize this Rudi Vansnick:for the first question we point to the SSAC 054 document where the contact info is well described Julie Hedlund:@Amr -- You are correct that Ching is the liaison. Glen has kindly reviewed the minutes from the 12 December meeting and found the following: From the Council minutes 12 December which are still being reviewed by the chairs please see: · Petter Rindforth mentioned that he volunteered as Council liaison for the Translation and Transliteration of Contact Information Policy Development Process working group, but it was noted that Ching Chiao was the Council liaison. Amr Elsadr:Thanks Julie and Glen. Julie Hedlund:On Contact Information the Final Issue Report states: ""In the context of these issues, "contact information" is a subset of Domain Name Registration Data. It is the information that enables someone using a Domain Name Registration Data Directory Service (such as WHOIS) to contact the domain name registration holder. It includes the name, organization, and postal address of the registered name holder, technical contact, as well as administrative contact. Domain Name Registration Data is accessible to the public via a Directory Service (also known as the WHOIS service). The Registrar Accreditation Agreement (RAA 3.3.1) specifies the data elements that must be provided by registrars (via Port 43 and via web-based services) in response to a query, but it does not require that data elements, such as contact information, must be translated or transliterated." Amr Elsadr:I don't know if Jim mentioned it, but the RAA also specifies what data elements are included in "contact information". Julie Hedlund:@Amr: That is the information above that also was included in the Final Issue Report. Rudi Vansnick:@Jim : also EPP ? Amr Elsadr:@Julie: That's right. Thanks. As Julie mentioned, these elements are also listed in the charter. Jim Galvin:yes Rudi. Sarmad Hussain:Perhaps we should look at the users of WHOIS Amr Elsadr:Answering this question will be one of the main tasks of this WG along with associated costs. Rudi Vansnick:@Yoav : for customer trust purposes maybe Sarmad Hussain:consumer trust is one of the points in AOC Petter Rindforth:clear information is important from both legal and marketing point of view Yoav Keren:@Petter - do you mean that from a legal point of view whois in local script will be clearer? Petter Rindforth:yes, if both versions are available - how to do it in a clear way is another question... Julie Hedlund:All: Just a reminder that this call is scheduled for 1 hour. Petter Rindforth:I'll spare our time and take down my hand ;-) Julie Hedlund:@Petter: This was not directed at you ;-) Amr Elsadr:That's ok. Petter Rindforth:Yoav in fact said more or less what I planned! Rudi Vansnick:thanks Petter ad Amr VINAY KUMAR SINGH:Rudi & Chris, I would like to work on the legal aspect Rudi Vansnick:@Vinay : that's noted, thanks a lot Petter Rindforth:add me to that! Rudi Vansnick:@Petter : noted VINAY KUMAR SINGH:@Petter, welcome to the team :-) Peter Dernbach:Thanks Rudi & Chris for agreeing to Co-Chair this WG. Amr Elsadr:This day and time are good for me. Sarmad Hussain:good for me Peter Dernbach:This day and time are good for me. Jennifer Chung:This timeslot works for me as well. Pitinan Kooarmornpatana:good for me Anthony:time ok Pitinan Kooarmornpatana:Thanks everyone Julie Hedlund:Thank you everyone! I will need to drop off now to join another call. Jim Galvin:bye for now Peter Dernbach:bye all. Amr Elsadr:Thnx. Bye. VINAY KUMAR SINGH:bye bye Chris Dillon:Goodbye Wanawit Ahkuputra:Thank you everyone, Bye Anthony:bye all Pitinan Kooarmornpatana:bye Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0