Re: [mif] DNS selection with HE-MIF

[GangChen <[e-mail]>]

2013/2/4, Ted Lemon <[e-mail]>:
> On Feb 4, 2013, at 5:44 AM, GangChen <[e-mail]> wrote:
>> Backing to the target of this thread, we intent to describe
>> issues within HE-MIF context. For issues in general and concrete
>> recommendations, would it make sense to draft new I-D?
>
> No.   The point of HE-MIF is to solve the problem.   So not talking about
> the full problem in the HE-MIF solution means that we're producing something
> that's probably harmful.


Allow me to explore *the problem* a bit. Following the discussion, I
realize there are actually two seperated problems.
1) Using HE-MIF (no domain information provisioned) to select DNS
2) Once domain name is resolved, using answer only within the
provisioning domain

For 1),

If there is no domain information provisioned (e.g. RFC6731),HE-MIF
selects DNS server using *connection speed* other than provisioning
domain information. I guess it desirable to do DNS query within a
matched provisioning domain. So pre-provisioned domain
information(e.g. RFC6731) would prioritize the interface sending DNS
query.

# For 2),#

I can't comment on benefits of "doing DNS queries within one
provisioning domain, and then using the results in the other
provisioning domain." But HE-MIF has to do in some cases, because that
maybe a normal node behavior, like stated in RFC6418 "A node usually
has a node-scoped routing table". This issue may retrospect to basic
Internet host design in RFC1122. Changing the model would go beyond
HE-MIF scope.

We would surely document full problem in HE-MIF solution at next update.

>
> It sounds like you think there's some value to doing DNS queries within one
> provisioning domain, and then using the results in the other provisioning
> domain.   Can you explain why?

See above # For 2),#

Best Regards

Gang

>