[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] Re: [RAM] Different approaches for different protocols



On 20 dec 2007, at 17:41, Templin, Fred L wrote:

LISP & family do the id->loc mapping in a middlebox, when the DNS name used
to come up with the id that's in the packet header is a distant
memory.

When the ITR is co-located with the DNS resolver, this
isn't so much of a problem (i.e., the RLOC and EID
lookups could occur when the FQDN is still available).

This would solve the problem most of the time, but you really don't want stuff to work "most of the time":

Even when doing this in the host itself the FQDN may not be
available when the time comes to do the mapping.

I.e., if the packets are sent to an IP address that was not recently derived from a DNS lookup, but rather, learned from the user, a config file, something that was stored on disk for some time, a referral in a protocol that does IP address referrals, etc.

Also, this kind of DNS magic is a large part of why NAT-PT was deprecated.

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg