On 07.06.2017 23:14, Ted Lemon wrote:
Okay, I think I've procrastinated on responding to this long enough, and Ray and Mark seem to feel even more strongly about that than I do. Sorry for taking so long, and thanks very much for the careful review!NAK because, this says exactly that I can't use '.home.arpa' for anything different than HNCP ...On Apr 30, 2017, at 8:06 PM, Suzanne Woolf <[email protected] <mailto:[email protected]>> wrote:Sec. 1, Introduction1. Existing text: "The '.home.arpa' domain replaces '.home' as the default domain used by the Home Networking Control Protocol (HNCP)"There's an accepted erratum on this, since the "reservation" of .home occurred without reference to the relevant registry, so it would be helpful for anyone trying to understand why this document exists to point that out.Suggested new text: "The '.home.arpa' domain corrects an error in RFC7788, replacing '.home' as the default domain used by the Home Networking Control Protocol (HNCP)."OK
my use case is just primitive DNS for an intranet in a LAN ...
In addition, this text doesn't touch at all on the fact a delegation in the global DNS is considered necessary for the default zone in order to properly support DNSSEC, or the rationale for it, or the potential difficulty of obtaining it in the root zone.Finally, it's unclear why a separate document is needed to support redaction of ".home" from RFC 7788, when this document replaces it with ".home.arpa." anyway. This document is standards track and already updates RFC 7788.
because ".home" should be used in the intention of the draft I've found ... https://datatracker.ietf.org/doc/draft-cheshire-homenet-dot-home/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
