Stephane Bortzmeyer wrote: [..]
There are solutions for some protocols (SSH keys of RFC 4251 or Host Identifiers of HIP in RFC 4423 are two good examples) but no general "identity layer" in the Internet architecture.
IMHO HIP (RFC4423) is that exact identity layer and additionally solves a number of other issues that it was made for.
The big problem though is that actually getting programs to use this is cumbersome, simply because a lot of programmers don't know about it.
Same goes for the use of SRV records, IMHO, instead of point to AAAA/A records for a service, one should *always* use SRV records.
SRV records solve loadbalancing, failover and a lot of other issues mostly already in DNS.
Webbrowsers for instance don't do SRV yet. One of their arguments is 'lookup time', the same reason that some 'webdevelopers' used IP addresses in their websites as that would skip the resolving step...
This is more about educating programmers than anything else... Greets, Jeroen
Attachment:
signature.asc
Description: OpenPGP digital signature