ICANN/DNSO
DNSO Mailling lists archives

[ga-roots]


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

Re: [ga-roots] Capture and Diversion (was Smart Browsers)


Patrick and all,

Patrick Corliss wrote:

> On Wednesday, May 02, 2001 7:19 AM (AEST), Bret Fausett wrote:
> > I agree with all of that, but I'm not eager for ICANN or any ICANN
> committee
> > (including this one) to take a position on what third-party software
> > developers, not bound by ICANN consensus policies, should do with their
> > products. It's well beyond the scope of ICANN's technical coordination
> > function.
>
> Hi Bret
>
> I'm happy to draw a boundary around what we should determine is, or ought to
> be, ICANN policy.  However, I'm not convinced of your argument.  Let me
> explain why.
>
> A user can type in a guess, a partial or incomplete address, click on a link
> or a fully-resolvable URL in accordance with RFCs or other standards.  That
> input string can then be transmitted, fudged or manipulated to resolve in a
> way that the user did not expect.

  Certainly this is possible, but unlikely on a very regular basis.  However
Patrick, it CAN happen, yes.  But if such a situation exists there are ways
in which to prevent such an occurrence.  These have been outlined on several
occasions on the DNSO GA and DOmain Policy lists several times and are
well known.  So I won't go into them in detail here.

>
>
> As well, the data can be routed anywhere through the DNS to all sort of
> name/root servers.  The string can be tampered with, or captured, anywhere
> along that chain from the browser's input line onwards.  In some cases it
> may have the user's implied consent.  But there may be plug-ins, MultiBinds,
> anything, along the way which simply take control

  Again as has been pointed out time and time again, sure this is possible
but unlikely on any regular basis, and methods for protecting from this
potential occurrence have already been discussed and dealt with accordingly.
Hence as a concern, this one is so minor as to be insignificant.

>
>
> Even after the URL resolves, you are not safe.  Some websites, especially
> those promoting sexual pleasures, will again take control and capture your
> computer's attention (if not yours).  Sudddenly, control is switched again
> and again to anywhere at all.  Your computer can even be reconfigured
> without your consent.  It happens and its happened to me.

  Well mine cant be reconfigured, although many attempts have been made
to do so.  Again Patrick, methods that are well documented and already
discussed on the DNSO GA and Domain Policy lists have been in some detail
provided.

>
>
> Should that sort of capture become commonplace, the whole internet will have
> lost integrity.  You can type any stribg you like and have very little hope
> that you will resolve, or stay resolved, to the website of your choice.

  Not really true.  And yet again Patrick, this has been discussed in great
detail with many different methods of technically preventing such an
occurrence (Rare as it is)...

>
>
> It seems to me that ICANN can't help but consider the issues of "capture"
> and/or "diversion" as matters of policy.  Otherwise they will have lost
> control of the whole internet.

  ICANN doesn't control the internet Patrick!

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

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members 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:  972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


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



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