[102064] in North American Network Operators' Group
Re: EU Official: IP Is Personal
daemon@ATHENA.MIT.EDU (Jeff McAdams)
Thu Jan 24 09:25:12 2008
Date: Thu, 24 Jan 2008 08:59:09 -0500
From: Jeff McAdams <jeffm@iglou.com>
To: nanog@merit.edu
In-Reply-To: <20080124131504.GA524@roxanne.org>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig05FD6FE7B6C9969E9971B040
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Eric Gauthier wrote:
> Heya,
>=20
>>> In the US, folks are fighting the RIAA claiming that an IP address is=
n't
>>> enough to identify a person.
>>>
>>> In Europe, folks are fighting the Google claiming that an IP address =
is
>>> enough to identify a person.
>>>
>>> I guess it depends on which side of the pond you are on.
>>>
>> They are both right. If you have a dynamic IP such as most college stu=
dents
>> have, it is here-today-gone-tomorrow.
> Our University uses dynamic addressing but we are able to identify like=
ly users
> in response to the RIAA stuff. There is a hidden step in here, at leas=
t for our=20
> University, in the IP-to-Person mapping. Our network essentially track=
s the=20
> IP-to-MAC relationship and the MAC-to-Owner relationship. For us, its =
not the=20
> IP that identifies a person, but the combination of IP plus Timestamp, =
which can=20
> be used to walk our database and produce a system owner.
There are a couple of ways that can break down. "Hey, dude, lemme
borrow your laptop for a minute." Or
"ifconfig eth0 ether aa:bb:cc:dd:ee:ff"
> I'm guessing that Google et. al. have a similar multi-factor token set =
(IP, time,
> cookie, etc) which allows them to map back to a "person".
Which, for similar reasons, does not, in any absolutely reliable way,
identify a *person* at the keyboard.
--=20
Jeff McAdams
"They that can give up essential liberty to obtain a
little temporary safety deserve neither liberty nor safety."
-- Benjamin Franklin
--------------enig05FD6FE7B6C9969E9971B040
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHmJmxXkUmzpmSrfwRAoWlAKDUe29h/GkwY/LGtns1uVegQ4iMmACgtBSQ
otecXQpEti55vb1bG2Nk0ok=
=xG8z
-----END PGP SIGNATURE-----
--------------enig05FD6FE7B6C9969E9971B040--
