[35528] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: new.net: yet another dns namespace overlay play

daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Mon Mar 12 10:39:08 2001

Message-Id: <200103121528.f2CFSak24734@foo-bar-baz.cc.vt.edu>
To: Arnold Nipper <arnold@nipper.de>
Cc: Charles Sprickman <spork@inch.com>, Steve Rubin <ser@tch.org>,
	Paul A Vixie <vixie@mfnx.net>, nanog@merit.edu
In-Reply-To: Your message of "Wed, 07 Mar 2001 00:05:51 +0100."
             <020901c0a692$2e6d3980$0190a8c0@nipper.de> 
From: Valdis.Kletnieks@vt.edu
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_537143236P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 12 Mar 2001 10:28:36 -0500
Errors-To: owner-nanog-outgoing@merit.edu


--==_Exmh_537143236P
Content-Type: text/plain; charset=us-ascii

On Wed, 07 Mar 2001 00:05:51 +0100, Arnold Nipper said:
> The resolver shouldn't care where the queries come from. That means a query
> from a web application will be resolved the same way as an ftp.

That's if you're using a replacement resolver.  The problem is that as
I originally read it, it was a *web browser plugin* - as such, if it's
interfering in other lookups (like FTP or an SMTP process) it's overstepping
its bounds.

Some of us run operating systems where the distinction is still made
between the OS kernel, the system libraries, and the application's
libraries and plugins...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


--==_Exmh_537143236P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOqzrJHAt5Vm009ewEQLDtACg9YkWrvIPDWUPEyNNIzwg/FaI2EoAn37h
+P0ns+Rip7ZczKif9ncR1Znj
=ZiTU
-----END PGP SIGNATURE-----

--==_Exmh_537143236P--


home help back first fref pref prev next nref lref last post