RFC 7368: IPv6 Home Networking Architecture Principles
In plain English — editorial summary, not part of the RFC
This text describes evolving networking technology within residential home networks with increasing numbers of devices and a trend towards increased internal routing. The goal of this document is to define a general architecture for IPv6-based home networking, describing the associated principles, considerations, and requirements. The text briefly highlights 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.
Document record
- Document ID
- RFC7368
- Published
- October 2014
- Authors
- T. Chown; J. Arkko; A. Brandt; O. Troan; J. Weil
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 49
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 7219SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)Current
May 2014
- RFC 7600IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)Current
July 2015
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7668IPv6 over BLUETOOTH(R) Low EnergyCurrent
October 2015
- RFC 7676IPv6 Support for Generic Routing Encapsulation (GRE)Current
October 2015
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?