<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 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoPlainText>Dear All,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>A new IETF working group has been proposed in the
Applications Area, with the following draft charter (see <a
href="http://www.ietf.org/iesg/evaluation/weirds-charter.txt">http://www.ietf.org/iesg/evaluation/weirds-charter.txt</a>),
and is provided for informational purposes only. Kindly note that current draft
proposes way forward using RESTful framework for both names and numbers and
also the timelines are Aug. 2013 for the completion of drafts.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Regards,<br>
Sarmad<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Web Extensible Internet Registration Data Service
(weirds)<o:p></o:p></p>
<p class=MsoPlainText>----------------------------------------------------------<o:p></o:p></p>
<p class=MsoPlainText>Status: Proposed Working Group<o:p></o:p></p>
<p class=MsoPlainText>Last updated: 2012-04-24<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Chairs:<o:p></o:p></p>
<p class=MsoPlainText> TBD<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Applications Area Directors:<o:p></o:p></p>
<p class=MsoPlainText> Barry Leiba<<a
href="mailto:barryleiba@computer.org">barryleiba@computer.org</a>><o:p></o:p></p>
<p class=MsoPlainText> Pete Resnick<<a
href="mailto:presnick@qualcomm.com">presnick@qualcomm.com</a>><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Mailing List: <o:p></o:p></p>
<p class=MsoPlainText> Address: <a
href="mailto:weirds@ietf.org">weirds@ietf.org</a><o:p></o:p></p>
<p class=MsoPlainText> To Subscribe: <a
href="https://www.ietf.org/mailman/listinfo/weirds">https://www.ietf.org/mailman/listinfo/weirds</a><o:p></o:p></p>
<p class=MsoPlainText> Archive: <a
href="http://www.ietf.org/mail-archive/web/weirds/">http://www.ietf.org/mail-archive/web/weirds/</a><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Description of Working Group:<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Internet registries for both number resources and names
have historically maintained a lookup service to permit public access to some
portion of the registry database. Most registries offer the service via
WHOIS (RFC 3912), with additional services being offered via world wide web
pages, bulk downloads, and other services, such as RPSL (RFC 2622).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>WHOIS has never been internationalized. In the
absence of formal specification, ad hoc solutions to signal internationalized
registration data have been adopted and deployed. Providing a
standards-based solution that scales well could minimize further proliferation
of ad hoc solutions.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>WHOIS also has no data model: replies are basically just
free-form text. This means that processing of WHOIS output amounts to
"screen scraping", with specialized handlers for every service.<o:p></o:p></p>
<p class=MsoPlainText>While many of the domain name registries share a basic
common output format, the addition of data elements changes the output and
causes problems for parsers of the data.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The WHOIS protocol does not offer any differential
service; it cannot differentiate among clients to offer different subsets of
information or to allow different access rates to it.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Various attempts to solve the limitations of WHOIS have
met with mixed success. The most recent of these was IRIS (RFC 3891).<o:p></o:p></p>
<p class=MsoPlainText>IRIS has not been a successful replacement for
WHOIS. The primary technical reason for this appears to be the complexity
of IRIS, the fact that it builds upon many available technologies that in the
aggregate form a complex system. There may also exist non-technical reasons,
but they lie in areas upon which the IETF does not pass judgement.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>In recent years, ARIN and RIPE NCC have fielded
production RESTful web services to serve WHOIS data, and each has met with
success.<o:p></o:p></p>
<p class=MsoPlainText>It is widely believed that this simpler re-use of Web
technologies familiar to modern web developers has enabled this success. The
purpose of this working group is to broaden the use of RESTful web services by
achieving simple and common URI patterns and responses amenable to all number
resource and domain name registries.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>This Working Group shall determine the general needs of
such a service, and standardize a single data framework. That framework
shall be used to encapsulate objects that could form part of an answer.
The framework shall be for data to be delivered via a RESTful data service
using HTTP (optionally using TLS), and may use standard features of HTTP to support
differential service levels to different classes of user. The data shall have
one mandatory format, though the working group may consider other optional
formats.<o:p></o:p></p>
<p class=MsoPlainText>The overall effort will be broadly aligned with a subset
of the Cross Registry Internet Service Protocol (CRISP) Requirements (RFC
3707), but with the explicit additional goals of producing a simple,
easy-to-implement protocol, supporting internationalized registration data and,
specifically for name registries, capturing the needs of internationalized
domain names in the data model.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>As the number registries have more experience with these
services and have found common ground, with their dissimilarities resulting in
more complete working group input documents, the goals of the working group are
to produce standards-track specifications for both number and name registries
using the fashion and pattern of the number registry input documents,
draft-newton-et-al-weirds-rir-query and
draft-newton-et-al-weirds-rir-json-response, as an initial basis.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Work to specify the query for domain name registration
data will be based on draft-sheng-weirds-icann-rws-dnrd.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The Working Group shall determine the general
requirements of such a service, using draft-kucherawy-weirds-requirements as an
input document, and standardize a single data framework. The working
group will likely not seek publication of this draft.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Should the Working Group reach a point where it
determines that the problem of producing a grand unified specification for both
numbers and names appears to be intractable, it will be permitted to divide the
problem into separate tasks and amend its milestones accordingly.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Milestones:<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Nov 2012 Draft specifying the common infrastructure
document to the<o:p></o:p></p>
<p class=MsoPlainText>
IESG for approval as a Proposed Standard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Feb 2013 Draft specifying the RESTful URL query
format for RIRs to the<o:p></o:p></p>
<p class=MsoPlainText>
IESG for approval as a Proposed Standard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Mar 2013 Draft specifying the format for responses
to RIR queries<o:p></o:p></p>
<p class=MsoPlainText> to
the IESG for approval as a Proposed Standard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Jul 2013 Draft specifying the RESTful URL query
format for domain name<o:p></o:p></p>
<p class=MsoPlainText>
registration data to the IESG for approval as a Proposed<o:p></o:p></p>
<p class=MsoPlainText>
Standard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Aug 2013 Draft(s) specifying the format(s) for
responses to domain name<o:p></o:p></p>
<p class=MsoPlainText>
registration data queries to the IESG for approval as a<o:p></o:p></p>
<p class=MsoPlainText>
Proposed Standard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>