[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSE
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Tony" == Tony Li <Tony.Li@procket.com> writes:
>> From an _engineering_ viewpoint, the hostname is not easy
Tony> to manipulate as an identifier. It is variable length and
Tony> we've decided on a fixed length field in our headers. If it
Tony> is of any length at all, it's likely to be longer than a
Tony> numeric identifier would be and in that sense is inefficient.
Tony> However, a numeric identifier of sufficient and fixed length
Tony> that had a 1:1 mapping with hostnames would work perfectly.
How about a 128-bit number, derived from some convenient nearby landmark,
or cross street?
Like a domain name, it may have no real meaning as a locator, only as a
end-point identifier. But, like a domain name, (such as mine), it provide
some geographic notion of where I am, even if that doesn't tell you which
AS# will get you here. Or like "procket.com", it might be assigned by an
organization on a first-come, first-served basis, and tell me nothing really,
about where you are.
It also fits nicely into both AAAA and A6 RR records, and has a well
defined reverse mapping to a hostname.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBPcqvf4qHRg3pndX9AQFWoQQArzv7WfHV8Y0iafpcJXtMOfy+kgP8Wcra
p36WlqWK2VqlYMaggT3HENiIYeHy8R176aPDGqQwyOBOOURRytjRJwDYwfjmy4cZ
b0vfiwGslChHrWG/M6ZT7si24Qsfz4N1J2sllff/PPWcfLFX5/hzJzJvPktHyScK
D5AkGqenhOo=
=z5kj
-----END PGP SIGNATURE-----
- References:
- RE: GSE
- From: "Tony Li" <Tony.Li@procket.com>