<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><title>Re: [tech-whois] A follow up session in San Francisco?</title><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>Hello all,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>I'd like to thank Jim, Jay and Michael for their thoughtful points and respond to their concerns related to the process or next steps for this work. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>This technical WHOIS work originated in part from a report prepared by staff in July 2009 at the request of the GNSO to detail the technical WHOIS service requirements that might be required to support current WHOIS requirements and proposed future WHOIS policy proposals, including the problem of internationalized domain names. (See: <a href="http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-29jul10-en.pdf"><span style='color:#0000BF;mso-style-textfill-fill-color:#0000BF;mso-style-textfill-fill-alpha:100.0%'>http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-29jul10-en.pdf</span></a> ). In the course of preparing this report, and analyzing how the WHOIS protocol can accommodate IDNs in particular, the question arose -- is the existing protocol robust enough to continue as-is, or should the protocol be updated to address its shortcomings before introducing the complexities associated with IDNs? IRIS is an existing protocol with extensive capabilities, but it has not been widely adopted. As new gTLDs are introduced, it will be important to better understand why this is the case. And in the course of research, staff also learned that a web-based alternative to the current protocol was being used by some RIRs, and explored further to see whether this type of implementation might provide capabilities worth considering.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>Staff kicked off this dialogue with the ICANN community to evaluate the WHOIS protocol from a purely technical perspective -- assuming the current WHOIS policies stay largely in place. If this dialogue leads to an understanding that the technical protocol needs to be changed for all gTLDs, staff fully appreciates -- and would expect the community to follow -- the appropriate procedures for adoption of that new protocol, including the initiation of the GNSO Council's policy development processes as set forth in the ICANN bylaws. There may also be a need to reach out to the IETF as appropriate and to conduct an evaluation of existing contracts to determine if they should be updated or amended to incorporate any new technical protocols. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>However, it may be premature to raise the issue within the GNSO Council at this time without more information and data. The session in Cartagena was an initial data gathering effort, and an event in SV would be a continuation of this effort. Because there may be others that share your concerns regarding the policy implications, I agree that it would be important to clarify in the agenda for the SV meeting the purpose/expected next steps of this dialogue. It may be useful to note that there is a Board mandated process underway to revise the current GNSO PDP. One of the key elements under consideration is the importance of greater fact-finding and research, prior to launching policy development work, especially on complex matters. In this new PDP “model”, the community is encouraged to meet, collect factual data, hold workshops, and even consider hiring experts when appropriate to provide useful information about the nature of policy concerns and possible options to address them before proceeding on a formal PDP track. Creating a technical WHOIS discussion list is in keeping with that model, and is not intended to circumvent the policy development process. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>If the community prefers to continue this discussion in another forum, such as under the auspices of an SO or AC, or through a “cross” SO-AC email list, staff will be happy to accommodate and support that.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>Best Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17375E;mso-style-textfill-fill-color:#17375E;mso-style-textfill-fill-alpha:100.0%'>Liz<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tech-whois-bounces@icann.org [mailto:tech-whois-bounces@icann.org] <b>On Behalf Of </b>Steve Sheng<br><b>Sent:</b> Thursday, February 17, 2011 2:49 PM<br><b>To:</b> James M Galvin; Jay Daley<br><b>Cc:</b> tech-whois@icann.org<br><b>Subject:</b> Re: [tech-whois] A follow up session in San Francisco?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif"'>Thank you Jim and Jay for your suggestion. <br><br>Warm regards, <br>Steve<br><br><br>On 2/16/11 4:37 PM, "James M Galvin" <<a href="jgalvin@afilias.info">jgalvin@afilias.info</a>> wrote:</span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif"'>I agree with Jay's suggestion.<br><br>Jim<br><br><br><br>-- On February 17, 2011 11:49:40 AM +1300 Jay Daley <<a href="jay@nzrs.net.nz">jay@nzrs.net.nz</a>><br>wrote regarding Re: [tech-whois] A follow up session in San Francisco?<br>--<br><br>> Hi Steve<br>><br>> On 2/02/2011, at 2:04 PM, Steve Sheng wrote:<br>><br>> > What do others on the mailing list think? Since Whois is used not<br>> > only by GNSO constituencies, but by ccTLDs, RIRs as well. Should<br>> > this be a joint working group with other SOs and ACs, for example<br>> > with SSAC? Another question is should the discussion happen inside<br>> > IETF instead of ICANN?<br>><br>> I would recommend that we have a joint WG across all constituencies<br>> that discusses "A new directory service" and that does what Michael<br>> suggested, which is consider the various requirements and get<br>> agreement on those. The registrar and user communities may have just<br>> as much input as the registries.<br>><br>> Once that is done then we can take two further steps:<br>><br>> 1. Have a joint WG on whether to scrap the current WHOIS service.<br>> 2. Ask the IETF to look at the protocol needed to support this new<br>> service including revisiting CRISP.<br>><br>> cheers<br>> Jay<br>><br>> ><br>> > Warm regards,<br>> > Steve<br>> ><br>> ><br>> > On 1/31/11 10:35 AM, "Michael Young" <<a href="myoung@ca.afilias.info">myoung@ca.afilias.info</a>> wrote:<br>> ><br>> > I tend to agree with James on this one, if we are going to do<br>> > something meaningful here, let's put a plan together on how to do<br>> > so.<br>> ><br>> > I think the last meeting found that we all agree that the current<br>> > Whois is at least lacking a solution for IDNs (I think we all<br>> > agreed on other shortcomings as well, but that was the most urgent<br>> > one I noted).<br>> ><br>> > There are many other controversial potential Whois requirements<br>> > that are related to the Whois policy(and related studies) work<br>> > going on. I suggest we try and focus on building a requirements<br>> > list of items that we believe a) don't constrain or affect current<br>> > or anticipated policy issues and have the GNSO/IRD review and agree<br>> > on that list b) if they do have policy implications but are<br>> > urgent (such as IDN enablement), let's work with the IRD and GNSO<br>> > to create some prioritized attention to the issues.<br>> ><br>> > Once you have an agreed upon set of requirements, with the relevant<br>> > stakeholders bought in, the rest becomes an examination of<br>> > inventory and then execution. We can then examine the most<br>> > efficient proposals to solve the requirements - including looking<br>> > at past work to see if there's anything worth reusing.<br>> ><br>> > Michael Young<br>> ><br>> > M:+1-647-289-1220<br>> ><br>> > -----Original Message-----<br>> > From: James M Galvin [<a href="mailto:jgalvin@afilias.info">mailto:jgalvin@afilias.info</a>]<br>> > Sent: January-31-11 1:23 PM<br>> > To: Steve Sheng; <a href="tech-whois@icann.org">tech-whois@icann.org</a><br>> > Subject: Re: [tech-whois] A follow up session in San Francisco?<br>> ><br>> > I'm not opposed to a follow up session in San Francisco but I'd<br>> > like to have a more actionable goal for the meeting than "engage a<br>> > discussion on the technical evolution of WHOIS".<br>> ><br>> > One thing that was clear from our last meeting is somebody needs to<br>> > "own" this work. A generic meeting with a generic agenda is not<br>> > making progress. If this work is going to progress then from whom<br>> > is there a formal mandate and what is it?<br>> ><br>> > Without an actionable goal we're just using up meeting slots.<br>> ><br>> > For one thing, let's be clear about whether we're talking about the<br>> > Whois protocol, the Whois data model, or the Whois data<br>> > representation.<br>> ><br>> > Depending on the actionable goal, if we are going to have<br>> > presentations by RWS and IRIS, perhaps a presentation by the IRD<br>> > would be helpful since it will have something to say about future<br>> > requirements for a replacement Whois data model.<br>> ><br>> > Jim<br>> ><br>> ><br>> ><br>> ><br>> > -- On January 26, 2011 9:52:17 AM -0800 Steve Sheng<br>> > <<a href="steve.sheng@icann.org">steve.sheng@icann.org</a>> wrote regarding [tech-whois] A follow up<br>> > session in San Francisco? --<br>> ><br>> > > Dear all,<br>> > ><br>> > > We had a successful workshop in Cartagena last year. Thinking<br>> > > ahead for the San Francisco meeting, we would like to ask if<br>> > > there would be any interest in scheduling a follow up session in<br>> > > San Francisco. Particularly we thought about inviting IRIS and<br>> > > RWS authors and implementers to come and give presentations about<br>> > > their experience, and then engage a discussion on the technical<br>> > > evolution of WHOIS.<br>> > ><br>> > > If there is sufficient interest, we can request a slot in the<br>> > > San Francisco meeting and invite speakers to come.<br>> > ><br>> > > Warm regards,<br>> ><br>> ><br>> > _______________________________________________<br>> > tech-whois mailing list<br>> > <a href="tech-whois@icann.org">tech-whois@icann.org</a><br>> > <a href="https://mm.icann.org/mailman/listinfo/tech-whois">https://mm.icann.org/mailman/listinfo/tech-whois</a><br>> ><br>> ><br>> > _______________________________________________<br>> > tech-whois mailing list<br>> > <a href="tech-whois@icann.org">tech-whois@icann.org</a><br>> > <a href="https://mm.icann.org/mailman/listinfo/tech-whois">https://mm.icann.org/mailman/listinfo/tech-whois</a><br><br><br></span><o:p></o:p></p></div></body></html>