Re: Host Name address handling

From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
Date: Fri Jan 28 2005 - 14:44:35 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Looking forward, it might become a very good place for passing host identifier if HIP gets
their way.

-Q

Randall Stewart wrote:

> Randall Stewart wrote:
>
>> Hirotsugu.Chiba@windriver.com wrote:
>>
>>> Hello Randall-san et al,
>>>
>>> Are there any sample implementation of handling "Host Name address"
>
> in
>
>>> INIT/INIT_ACK messages?
>>> xxxBSD or Linux??
>
>
> The problem with the host-name-address parameter IMO is:
>
> a) It servers little purpose since you can get through a
> NAT like the nat draft says by just NOT placing any
> addresses in your INIT.. yes you are singly homed.. but
> the HNA param would not help.. you have to have nat's
> cooperating to get M-homed..
>
> b) It is very very difficult to implement in the kernel since
> when it is time to resolve the host name one must
> 1) upcall to an app to do the DNS lookup
> 2) sleep the kernel thread waiting for an app
> to write back
> 3) when the app gets the DNS response have it
> write it down the "socket" or other special
> IPC mechanism
> 4) Then proceed.
>
> This is very ugly and so far, we have not been able to
> test this feature at any interop since no one is implementing
> it.. and for good reason... I really think it should be something
> we drop from the protocol :-D
>
> R
>
>>>
>>> Thank you in advance,
>>>
>>> chiba
>>>
>>>
>>
>> Forwarding to my cisco account so I can answer
>>
>> R
>>
>>
>
>
Received on Fri Jan 28 14:55:13 2005