Re: [NIC-990226.52da] Suggestion: Add contact entry to whois

[owen () DeLong SJ CA US (Owen DeLong)]

I don't know quite what to say to this, so I simply forward it to the
list without further comment...

Owen

----- Begin Included Message -----

> From creg () internic net Thu Mar 25 20:59:15 1999
From: Contact Registration Account <creg () internic net>
Subject: Re: [NIC-990226.52da] Suggestion:  Add contact entry to whois
To: owen () dixon DeLong SJ CA US (Owen DeLong)
Date: Thu, 25 Mar 1999 23:59:16 -0500 (EST)
In-Reply-To: <199903151618.IAA09244 () irkutsk delong sj ca us> from "Owen DeLong" at Mar 15, 99 08:18:01 am
X-MTS-Ticket: 990226.52da
X-MTS-Type: POC
X-MTS-Priority: Normal
X-MTS-Mode: Unknown
X-MTS-Status: Open
X-MTS-Timestamp: 990315111628
X-Mailer: ELM [version 2.4 PL24 PGP2]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Lines: 124

>
Thank you for contacting Network Solutions.

We are unable to fulfill your request without the following information, as 
indicated below:

Domain Name Registration Agreement 

___ 1. Your request was not submitted on the appropriate form. Please
       submit your request on the Domain Name Registration Agreement.
        
___ 2. The NIC-tracking number (example: 990203.1a2d) associated with
       your request was either not provided or is invalid.

___ 2b The NIC-tracking number you referenced is not associated with your
       current request. If you are unable to locate the NIC-tracking number
       for your current request, please re-submit your Domain Name Registration
       Agreement to receive a new tracking number.

___ 2c The NIC-tracking number you have referenced, (), does not  
       have a Domain Name Registration Agreement associated with it. Please 
       check the number and resubmit your request.

___ 3. To ensure that we have the proper authorization to process your
       request, we require a faxed authorization letter. To create
       an authorization letter to modify a domain name record, please
       visit our web site at www.networksolutions.com.

___ 4. We did not receive your facsimile in its entirety or it
       was illegible.

___ 5. Your request is considered a transfer of a domain name 
       registration, and must be submitted on a Registrant Name Change
       Agreement - Transfer form. The form is available at
       www.networksolutions.com. Select Make Changes, then choose 
       Registrant Name Change Agreement. Answers to Frequently Asked 
       Questions about the Registrant Name Change Agreement are available
       on our Web site.  From our home page, choose Help, Make Changes,
       Registrant Name Change Agreement FAQ.


Contact Form 

___ 1. To ensure that we have the proper authorization to process your
       request, we require a faxed authorization letter. To create
       an authorization letter to modify an individual contact record,
       please visit our web site at www.networksolutions.com.

___ 2. To ensure that we have the proper authorization to process your
       request, we require a faxed authorization letter. To create
       a letter of authorization to modify an role contact record,
       please visit our web site at www.networksolutions.com.

___ 3. Your Contact Form is incomplete.  Please complete Section 1 in its
       entirety and re-submit the Form to HOSTMASTER () INTERNIC NET 
        

Best Regards,

Network Solutions Registration Services 

World Wide Web: http://www.networksolutions.com
E-mail:         hostmaster () internic net
Tax ID #:       52-1146119                       cc 03/06/99

nsi_rp80
=========================================================================

> Well, I, and many other people on NANOG where this has been discussed
> over the last several weeks would tend to disagree with you.  While
> your answer certainly reflects the current state of the database, it
> appears that you may not have understood the intent of the message.
>
> I am suggesting that it may be time to consider the addition of those
> fields as a change.  I wanted to solicit input from InterNIC and ARIN,
> as well as NANOG.  At this point, I will probably attempt to put it
> through the RFC process.  The idea seemed to have substantial support
> from the community.  There were some voices of dissent, but most of
> them revolved around the fact that it didn't solve all the problems
> or didn't solve certain problems it wasn't intended to solve.
>
> There was one voice opposed on the basis that all contact information
> for domains should be private, but this opinion doesn't appear to be
> widely represented among the community.
>
> Owen
>
> > >
> > Dear Customer,
> >
> > Thank you for contacting Network Solutions, Inc., InterNIC
> > Registration Services.
> >
> > Please be advised, unfortunately three contacts are all that needed.
> >
> >
> > Best Regards,
> > Ed r
> > Network Solutions, Inc. 
> >
> > World Wide Web: http://rs.internic.net
> > E-mail:         hostmaster () internic net
> > Phone:          703-742-4777(Monday-Friday 7:00am to 9:00pm Eastern Time)
> > Billing Fax:    703-318-9125
> > Regular Fax:    703-742-9552(For Modification & Delete Authorization)
> > Postal:         Network Solutions, Inc.
> >                 ATTN: InterNIC
> >                  505 Huntmar Park Drive
> >                  Herndon, VA 20170
> > Tax ID #:       52-1146119                       crg  11/02/98 
> > nsi_rp112
> > ========================================================================== 
> >
> > > We already have Admin, Tech, and Billing.  Would it be possible to consider
> > > the addition of an Abuse contact in whois?
> > >
> > > Owen



----- End Included Message -----