ICANN/GNSO
DNSO and GNSO Mailling lists archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ga] Legitimate Hi-Jacking


John and all assembly members,

John Berryhill Ph.D. J.D. wrote:

> Since ICANN now seems to be moving seriously to enforce the 15-day
> confirmation period for suspect whois data, it might be a good idea to let
> the cat out of the bag, so that every one will have a fair chance.

  Good point here John, and one that I tried to make in part
yesterday regarding one of ICANN's own staff members,
Kent Crispit with the At-large.org registration. See:
 http://www.fitug.de/atlarge-discuss/0209/msg00086.html
Seems that Even and ICANN staff member cannot or will not
keep the Domain name he has in his name Accurate.

>
>
> Consider - the Wait-List Service has been approved, and you will soon be able
> to obtain a deleted name with certainty.  The trick, of course, is knowing
> which domain names are going to be deleted, since you have to pay your money
> up front.  The Redemption Grace Period adds further uncertainty to the
> process.  However....
>
> Now, we have the way to shake the tree and make the domain names fall out.
> Look for domain names which have contact email address of defunct ISP, such
> as home.com, and others which caused mass-strandings of domain name
> registrants with no way to fix their whois data if email confirmation is
> required.  Alternatively, try to find out or guess when the domain name
> registrant of the name you want is away from their phone, email, or address
> for two weeks.   Don't worry, if you guess wrong, you can try again.
>
> The whois confirmation policy provides a 15 day "bed check" for the registrar
> to confirm these details are correct, and this is MUCH shorter than the
> proposed redemption grace period.  So...
>
> STEP 1 - Take out a WLS or Snapback on the name you want.
> STEP 2- Complain loud and hard that the whois data for the domain name is
> bad.
> STEP 3 - Wait 15 days.
> STEP 4 - Enjoy your new domain name.
>
> What's nice about this method, as opposed to other hi-jacking methods, is
> that if you score the name and your target wakes up and figures out what
> happened, then he/she has virtually no recourse.
>
> If you are concerned about the security of any of your domain names, keep in
> mind that every domain name has a 15 day fuse to deletion (and you will not
> likely be informed at day 1, so it is less than that), and act accordingly.
> Email server down this week?  Kiss your domain names goodbye.

  Exactly right!  ANd this is in part what several complained and
discussed on the two TR TF Phone Conferences..

  Therefore as a result of this horrible WLS consideration, I am
finding it very difficult if not impossible how the ICANN BOD and
staff can state with a straight face and expect any participant,
informed registrant, or any other Stakeholder how they are
improving or even providing at all for "Stability" as is in their
Mandate of the White Paper and MoU... ????

  It also therefore seems to me with your nice brief outline
above John that if even one of ICANN's staff people,
one Kent Crispin, can do so with his own domain, how
now they can than make a policy decision and expect
equitable enforcement or even oversight of Whois data
accuracy and WLS...

>
>
> --
> This message was passed to you via the ga@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga" in the body of the message).
> Archives at http://www.dnso.org/archives.html

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html




<<< Chronological Index >>>    <<< Thread Index >>>