Hi all, The architecture text has been updated to -05.
See: http://tools.ietf.org/html/draft-ietf-homenet-arch-05 We can take comments towards a -06 over the weekend. The most substantial changes are in the Naming and Service Discovery section (3.7), so if you have limited time please focus your reading there. One item where there seemed to be a lack of a firm conclusion (despite some firm statements each way) was the question of using a single global name space or separate internal and external name spaces. The current text essentially says: * The default is to use an ISP-provided domain in the homenet, but with the user able to use an independent domain name instead if preferred. * If no global domain is available, the homenet uses either a ULQDN (preferred) or ALQDN, and these are scoped to the local homenet (i.e. the homenet can only be reached remotely if using a global domain). The open issue is whether the LQDN should be used alongside a global FQDN if one is available (with appropriate mappings/CNAMEs and reverse entries to the global FQDN as proposed I think by Curtis), or if the global domain is available then no local domain should be used. Tim On 19 Oct 2012, at 17:00, [email protected] wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Home Networking Working Group of the IETF. > > Title : Home Networking Architecture for IPv6 > Author(s) : Tim Chown > Jari Arkko > Anders Brandt > Ole Troan > Jason Weil > Filename : draft-ietf-homenet-arch-05.txt > Pages : 43 > Date : 2012-10-19 > > Abstract: > This text describes evolving networking technology within > increasingly large residential home networks. The goal of this > document is to define an architecture for IPv6-based home networking, > while describing the associated principles, considerations and > requirements. The text briefly highlights the specific implications > of the introduction of IPv6 for home networking, discusses the > elements of the architecture, and suggests how standard IPv6 > mechanisms and addressing can be employed in home networking. The > architecture describes the need for specific protocol extensions for > certain additional functionality. It is assumed that the IPv6 home > network is not actively managed, and runs as an IPv6-only or dual- > stack network. There are no recommendations in this text for the > IPv4 part of the network. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-homenet-arch > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-homenet-arch-05 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-arch-05
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
