Hi Michael,
You know homenet details much better. The only point I was trying to
make is that it is possible to have sub-domains under a special use
domain. "home.arpa" is one example. "e164.arpa" from RFC 6116
(https://www.rfc-editor.org/rfc/rfc6116.html) seems to be another example.
Whether sub domains are resolvable and how they are registered/managed
can be (and will be) different. As you wrote in another email, if we
have a good justification, IAB will likely bless with appropriate guidance.
Hope you + others in the working group had an enjoyable and productive
week in Brisbane. Safe travels!
--Mohit
On 3/22/24 11:24, Michael Richardson wrote:
Mohit Sethi <mo...@iki.fi> wrote:
> As far as I can tell, we will not be the first ones using such a
> scheme. ".home.arpa." defined in RFC 8375
> (https://www.rfc-editor.org/rfc/rfc8375.html) allows sub domains. It
says:
> "For an administrative domain that uses subdomains of 'home.arpa.', such
as a
> homenet, the recursive resolvers provided by that domain will be able to
> answer queries for subdomains of 'home.arpa.'"
It's not at all the same thing :-)
home.arpa is a real anchor which home routers can serve names into using DNS.
(Replacing ".local" [which implies mDNS], and .lan, which some home routers use)
> We are taking a more conservative approach where subdomains need expert
> review and registration before they are allocated and can be used in
> deployments.
I would not characterize it this way at all.
I suspect we can have what we want, we just need to explain it to the IAB
well enough. Unfortunately too late in the week for a hallway conversation.
I found some IESG to talk to at the last break, but no IAB.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
