Re: [homenet] Homenets and MPVD

[Ole Troan <[e-mail]>]

Markus,

>> All routers gather this information through HNCP and use it to configure hosts. DHCP options that are associated with a given delegated prefix are given to hosts associated with the link prefix provided by the prefix assignment algorithm. DHCP options that are not associated with a delegated prefix are aggregated and given to the host (Excepted for the DNS server option, as the router is used as DNS relay).
> 
> DNS server option is mostly changed so we can do in-home service discovery. In MIF world, we would probably pass along DNS servers within PVDs as is, provide (e.g.) ‘.home’ PVD for in-home services only, and provide only to legacy clients the ‘relay’ DNS server address. So oddly enough, current scheme would work, most likely as-is ;) The unknown new PVD option would be passed along as is, and the clients would treat the provided legacy DNS server (+search path) as an extra implicit PVD with hopefully lower priority than the explicit PVDs.
> 
> Not changing PVDs may be crucial if the PVD authentication ever takes hold, as changing it’s content then may make it altogether invalid from the client’s point of view. 

is it actually obvious that you'd pass the PVDs to the hosts in homenets?
PVDs contain policy. and allowing them to pass the administrative boundary into a home is also up to policy.
given that we already have options to control DNS server selection policy. why can't the home border amalgamate that information (according to local policy)?

sorry, I'm struggling to understand the PVD use case I suppose.

cheers,
Ole