> No arguments from me re: making status info visible via RRP. This type of
change would best be requested through our customer service channels,
though. I'll pass this on, but any registrar who has suggestions for
changes or improvements should send them directly to our customer service
department at info@NSIRegistry.net, who will route it appropriately.
Scott,
I *did* request this through the NSI customer service department back in
April. It resulted in a con-call with several very polite NSI people who
said that they weren't going to implement anything that goes against the RRP
spec. They suggested that I bring up the issue in the NSI-Registrars
mailing list to first change the spec.
Now that Eric and I have brought it up, I'll resubmit my request to NSI
Customer Service. I suggest everyone else (pro or con) speak up too!
Attached, FYI, is my initial e-mail, NSI's response, and my response.
Cheers,
_Mike
-- Mike Lampson Info Avenue Internet Services (803) 802-6584 ----- Original Message ----- From: "NSI Registry Support" <info@nsiregistry.com> To: "Mike Lampson" <lampson@InfoAve.Net> Sent: Friday, April 14, 2000 3:57 PM Subject: Re: RRPStatusDomain usage> > Dear Mike, > > Thank you for contacting NSI Registry Customer Service. > > Only the Registrar of Record has the ability to view the status of domain > name. This is documented in the RRP Protocol Specifications > (www.ietf.org/internet-drafts/draft-hollenbeck-rrp-01.txt). Domain Status > is considered privileged information. The capability to view the status of > any domain name could result in misuse of the system through data mining and > speculation based on current status. Data mining could result in > performance issues for the Shared Registration System (SRS). > > In reviewing the ICANN-NSI Registry Agreement, the Registrar License & > Agreement, and Registrar Accreditation Agreement, we cannot find any > requirement that the StatusDomain function must be made available. Could > you provide further clarification to your reference so that we can research > it further? > > > Best Regards, > > Inez Toppin > NSI Registry Customer Service > http://www.nsiregistry.net > info@nsiregistry.net > > > -----Original Message----- > From: Mike Lampson <lampson@InfoAve.Net> > To: NSI Registry Support by way of The Registry at Info > Avenuetheregistryinfoavenet <info@nsiregistry.com> > Date: Friday, April 14, 2000 11:23 AM > Subject: Q: RRPStatusDomain usage > > > Hi, > > I am in the process of implementing code to allow our customer service > department to help customers transfer their domains to us. One of the > things I was planning was to execute an RRPStatusDomain to verify the > current registrar and to check that there are no locks or holds on the > domain. > > However, when I try to check a domain in the OT&E server that we > (IARegistry) did not create, I get an RRP status of 531 Authorization > Failed. > > Am I supposed to be able to get the status of a domain owned by another > registrar? > > Where is this behavior documented? It is not in the NSI Registry C API > v1.1.0. (At least I can't find it.) > > If I'm not allowed to do this, why not? All the information available from > the StatusDomain function is supposed to be available via a combination of > your master WhoIs server and the Registrar's according to the ICANN > agreement, so it is not secret. > > It would be a great benefit to be able to validate a domain's current status > against the "live" data vs. looking at the "snapshot" stored in WhoIs prior > to initiating a Transfer request via the RRP. > > Regards, > > _Mike > -- > Mike Lampson > Info Avenue Internet Services > (803) 802-6584 >
From: "Mike Lampson" <lampson@infoave.net> To: "NSI Registry Support" <info@nsiregistry.com> Sent: Monday, April 17, 2000 8:53 AM Subject: Re: RRPStatusDomain usage
> I would agree with your assertion about data mining if there was a way to > scan domain name ranges. However, my interest is to look at the state of > a specific domain where I send a single domain name via the RRP. > > From ICANN, look at the Registrar Accreditation Agreement, dated 11/04/1999, > section II.F (Public Access to Data on SLD Registrations). > > Below is a mapping of the data available via StatusDomain vs. what is > available via WhoIs: > > DomainName - input value, included in response. > > RegistrationExpirationDate - available via Registrar WhoIs per ICANN RAA. > > Registrar - available via whois.crsnic.net. > > RegistrarTransferDate - not available via WhoIs. > > Status - available via whois.crsnic.net. > > CreatedDate - available via Registrar WhoIs per ICANN RAA. > > CreatedBy - not available via WhoIs, usually the same as > Registrar. > > UpdatedDate - available via whois.crsnic.net. > > UpdatedBy - not available via WhoIs (But must be either > the Registrar or the Registry, right?) > > NameServers - available via whois.crsnic.net or Registrar > WhoIs. > > The fact that virtually all the information available via the CheckDomain > function is also available via public WhoIs makes the restriction of the > function irrelevant. In fact, I believe it is counterproductive to both > you, the Registry, and us, (collectively) the Registrars, to restrict us > from determining, up front, the true status of a domain as accurately as > possible. Considering the limited number of organizations with access to > the RRP I would think this would be a non-issue. > > This is just my opinion. Please help me understand why such a restriction > exists on the RRP when it does not exist on WhoIs. And if you agree with > me, when do you think this restriction could be removed from the RRP? > > Regards, > > _Mike > -- > Mike Lampson > Info Avenue Internet Services > (803) 802-6584
--------- See http://www.nsiregistry.com/maillist/rrp/ for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Mon Sep 11 2000 - 15:43:55 EDT