<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] RE: [registrars] PIR’s EPP DOMAIN INFO command change announcement
- To: Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
- Subject: RE: [registrars] RE: [registrars] PIR’s EPP DOMAIN INFO command change announcement
- From: Tim Ruiz <tim@xxxxxxxxxxx>
- Date: Thu, 5 Aug 2004 19:38:35 -0700
- Cc: halloran@xxxxxxxxx, registrars@xxxxxxxx, Jay Westerdal <jwesterdal@xxxxxxxxxxxxx>, bbeckwith@xxxxxxx, twomey@xxxxxxxxx
- Reply-to: Tim Ruiz <tim@xxxxxxxxxxx>
- Sender: owner-registrars@xxxxxxxxxxxxxx
<div>Bruce,</div>
<div> </div>
<div>There are probably any number of legitimate reasons why a third-party
registrar uses some of the dates or the status
information currently returned without providing the auth-info
code.</div>
<div> </div>
<div>For example, we check the status of requested transfers prior to ever
asking for an auth-info code. If the status does not allow transfer we
can then save the customer a lot of unnecessary time and reduce the
aggrevation. I am certain there other registrars with equally
legitimate processes using this information.</div>
<div> </div>
<div>True, we can work around with Whois, unless of course that changes
too. But the other problem is what Jay points out, PIR restricts its
whois severly. We understand their concerns regarding Whois since it is
a public utility and potentially subject to mining. However, only
accredited registrars have access to the INFO command and the results.
It seems extreme to punish everyone for what PIR may view as abuse by a
few, and that abuse may actually be legitimate use that just isn't fully
understood by PIR. It would seem to me to make more sense to attach some
micro-fee to the command then to just basically ban it
altogether.<BR><BR>The other problem we have with this is the timing.
Sometimes it seems that the registries think that they are the only
supplier we deal with and can make changes to our systems at the drop
of a hat. This change in the INFO command comes on the heels of changes
that need to be made to be compliant with the new Transfer policy and
for us, at least two other modifications that we are working on with
other registries. These days, a three month notice ain't much.</div>
<div> </div>
<div>Tim</div>
<div> </div>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT:
blue 2px solid"><BR>-------- Original Message --------<BR>Subject:
[registrars]<BR>=?utf-8?B?UkU6IFtyZWdpc3RyYXJzXSBQSVLigJlzIEVQUCBET01BSQ==?=
=?utf-8?B?TiBJTkZPIGNvbW1hbmQgY2hhbmdlIGFubm91bmNlbWU=?=
=?utf-8?B?bnQ=?=<BR>From: "Bruce Tonkin"
<Bruce.Tonkin@xxxxxxxxxxxxxxxxxx><BR>Date: Thu, August 05, 2004
7:08 pm<BR>To: "Jay Westerdal" <jwesterdal@xxxxxxxxxxxxx>,
bbeckwith@xxxxxxx,<BR>twomey@xxxxxxxxx<BR>Cc: halloran@xxxxxxxxx,
registrars@xxxxxxxx<BR><BR>Hello Jay,<BR><BR>Actually I support the
general changes being considered by PIR.<BR><BR>What is done with the
Australian .com.au registry (which uses EPP), is that the <info>
command returns full details if:<BR>(a) the request is from the
registrar of record for that particular domain name record<BR>Or<BR>(b)
the auth-info password is provided<BR><BR>Thus for a transfer-in, a
gaining registrar can request the full record provided the registrant
has provided the correct auth-info.<BR><BR>I see no reason why the
general public needs to know the expiry date of a registrant's domain
name licence, any more than you need to know the expiry date of my
drivers licence or passport.<BR><BR>With respect to the EPP protocol, a
field may be returned empty and still be compliant with the protocol.
It is a policy decision for what content needs to be provided in
which field for certain queries.<BR><BR>I don't believe that the
proposed change would be non-compliant with EPP, any more than a thin
registry model would be non-compliant with EPP.<BR><BR>Right now from a
contractual point of view, the information must be supplied in the WHOIS
(not necessarily via EPP).<BR>Personally I hope this decision can be
reviewed as part of the WHOIS policy
development.<BR><BR>Regards,<BR>Bruce<BR><BR><BR><BR><BR>>
-----Original Message-----<BR>> From:
owner-registrars@xxxxxxxxxxxxxx <BR>>
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Jay
Westerdal<BR>> Sent: Friday, 6 August 2004 11:44 AM<BR>> To:
bbeckwith@xxxxxxx; twomey@xxxxxxxxx<BR>> Cc: halloran@xxxxxxxxx;
registrars@xxxxxxxx<BR>> Subject: [registrars] PIRâ??s EPP DOMAIN
INFO command change <BR>> announcement<BR>> <BR>> Name
Intelligence, Inc.<BR>> 12806 SE 22nd PL Î? Bellevue, WA
98005<BR>> <BR>> August 5, 2004<BR>> <BR>> VIA
EMAIL<BR>> <BR>> Attention: Paul Twomey and Bruce Beckwith Public
Interest Registry<BR>> 1775 Wiehle Ave, Suite 102A<BR>> Reston,
Virginia 20190<BR>> Phone: +1-703-464-7005<BR>> Facsimile:
+1-703-464-7006<BR>> <BR>> RE: PIRâ??s EPP DOMAIN INFO command
change announcement<BR>> <BR>> Dear Paul Twomey and Bruce
Beckwith,<BR>> <BR>> Name Intelligence, Inc. has just been made
aware that PIR <BR>> will be modifying its Dot ORG Registry Software
to be <BR>> non-compliant with EPP1.0. They are moving away from full
<BR>> complacence with EPP 1.0â??s DOMAIN INFO command. Their
<BR>> announcement is that they will stop providing complete
<BR>> information according to RFC 3732. Their intention is stop
<BR>> showing all information except for Registrar of record. The
<BR>> reason is to make the command thinner and prevent data
<BR>> mining. However NO registrant information is even being
<BR>> returned with this command right now. The â??INFOâ?? command
is <BR>> already a thin command that shows very little information.
<BR>> The information that it does show is fields like: Domain
<BR>> Name, Registrar of Record, Domain Status (On-hold, <BR>>
Transfer-prohibited, Registrar-lock), Domain Creation Date, <BR>>
Modification Date, Expiration Date. We need these fields for <BR>>
our domain suggestion software that appears on <BR>>
NetworkSolutions.com, GoDaddy.com, Enom.com, Yahoo, and lots <BR>>
of other registration companyâ??s websites. This software helps
<BR>> millions of people a year to register domain names. PIRâ??s
<BR>> impact on our business and that of our customers would be
<BR>> overwhelming if their stated changes takes place.<BR>>
<BR>> Even VeriSign which operates a thin Registry would be showing
<BR>> more information then PIR after PIRâ??s EPP change. PIR limits
<BR>> their whois access more severally then VeriSign does. <BR>>
Therefore gathering Domain Status and expiration date is very <BR>>
complex with PIR. With VeriSign we just query for this using <BR>>
their whois and we get the answer back. We tried this <BR>> approach
with PIR but they banned our IP addresses because <BR>> they said we
requested too many records. I am not sure if <BR>> that was fair and
equal for them to do since we sevice <BR>> millions of customers a
day, but that is the primary reason <BR>> our company sought
accreditation as an ICANN Registrar. <BR>> Querying via the
EPP command instead of whois allows us <BR>> access to the same
information which is critical to the <BR>> operations of our
company. Actually, the info command returns <BR>> less information
then whois. But having got accredited just <BR>> for EPP domain info
command and now using EPP to gather this <BR>> information we later
hear that PIR is going to begin hiding <BR>> domainâ??s status and
expiration date from the DOMAIN INFO <BR>> command. Our
business relies on this EPP command to <BR>> determine the
domainâ??s status and expiration date and we use <BR>> these values
in our suggestion software.<BR>> <BR>> We formally request that
PIR repeal their decision on hiding <BR>> expiration date and status
from the DOMAIN INFO command. And <BR>> we also formally request that
ICANN enforce their contract <BR>> with PIR and make them stay
complaint with EPP 1.0 (RFC3732) <BR>> for the DOMAIN INFO
command.<BR>> <BR>> PIR has stated several times that they wish
to be the model <BR>> registry, yet this move by them would make
them even worse <BR>> then VeriSign as far as usability. It would
degrade the <BR>> registration process of millions of users
annually. <BR>> Suggestions for available domain names is a service
that <BR>> users rely on and expect in a good registrar. PIR would
force <BR>> our software to be less accurate and possible suggest a
.ORG <BR>> domain that is already registered. And in my option that
is a <BR>> move in the wrong direction for this registry. Helping us
<BR>> help the registrars with registration is where I want to see
<BR>> PIR headed.<BR>> <BR>>
http://www.icann.org/tlds/agreements/org/<BR>>
http://www.faqs.org/rfcs/rfc3732.html<BR>> <BR>> <BR>>
Sincerely,<BR>> <BR>> <BR>> <BR>> Jay Westerdal<BR>>
President and CEO Name Intelligence, Inc.<BR>> CC: Dan Holloran,
Registrars<BR>> <BR>> </BLOCKQUOTE>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|