As was alluded to in my email of 9th June, we have been asked to replace RFC 7788 (HNCP) with an RFC 7788-bis as soon as possible to incorporate the errata raised by the DNSOP chair regarding the unintended apparent reservation of ".home" as the default domain TLV within HNCP.
We should also take that opportunity to fix the error in the diagrams for the DHCPv4_DATA and DHCPv6_DATA TLVs where the numbers shown conflict with the IANA registrations for those TLVs. Those two changes will be the only ones made, unless any further errata are made in the meantime. Slightly longer term, and notwithstanding our previously stated desire to wait until Ted Lemon's Naming Architecture was further progressed, we would like to obtain WG consensus on whether ".home" is indeed a suitable default domain for HNCP. In the meantime, implementors are hereby advised that ".home" is potentially subject to change. It should be noted (as pointed out to us by the Chair of the IAB) that the default domain need not be a single-label "pseudo-TLD" - it could be a sub-domain of an existing name in the DNS such as ".arpa". Whichever domain is chosen, we will then instigate a new WG document (or perhaps resurrect draft-cheshire-homenet-dot-home if ".home" is preferred) to follow due process and formally reserve a default domain as a "special use domain name". Ray and Mark _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
