On 2012-06-29 19:19, Olafur Gudmundsson wrote:
...
>>> b) Homenet name-service MUST NOT be in Internet name space.
>>
>> How are things in the home identified from outside the homenet?
>
> They will have to have two names one internal and one externally visible.
Exactly. This has been standard practice in enterprise networks
using standard DNS software for years, and is exactly analogous to
ULAs and globally-routeable GUAs. The internal name should IMHO
be syntactically identical to an FQDN but will not resolve off-site.
This does not need to break the hierarchical purity of the DNS
name space, just as ULAs do not break the IPv6 address hierarchy.
(By contrast, RFC 1918 and .local do break their respective
hierarchies.)
On 2012-06-29 20:18, Michael Thomas wrote:
> On 06/29/2012 11:53 AM, Don Sturek wrote:
>> Hi Michael,
>>
>> The difficulty with your proposal is that the homenet address space is now
>> connected to the wider internet.
>
> It wasn't a proposal of a solution, so much as plea to not make my
> life more difficult trying to keep track of the difference between
> "in" and "out" naming systems. We've done a pretty good job of
> teaching the world about fqdn's to the point that seeing unqualified
> names makes me wonder what they are and whether they even refer
> to anything Internet-like. And of course, I want to have a flip of
> the switch if I decide to make them Internet-wide visible.
+1
Brian
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
