[homenet] RFC 7368 on IPv6 Home Networking Architecture Principles

rfc-editor@rfc-editor.org Fri, 24 October 2014 23:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4A2BF1A1AE1; Fri, 24 Oct 2014 16:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id OqaGQoTAlzjP; Fri, 24 Oct 2014 16:18:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 1B60D1A1C06; Fri, 24 Oct 2014 16:18:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 69A48181C99; Fri, 24 Oct 2014 16:17:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141024231743.69A48181C99@rfc-editor.org>
Date: Fri, 24 Oct 2014 16:17:43 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/eA15Yuj0M9vY5twWE9fz4XG9M1U
Cc: drafts-update-ref@iana.org, homenet@ietf.org, rfc-editor@rfc-editor.org
Subject: [homenet] RFC 7368 on IPv6 Home Networking Architecture Principles
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Oct 2014 23:18:17 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7368

        Title:      IPv6 Home Networking Architecture Principles 
        Author:     T. Chown, Ed.,
                    J. Arkko, A. Brandt,
                    O. Troan, J. Weil
        Status:     Informational
        Stream:     IETF
        Date:       October 2014
        Mailbox:    tjc@ecs.soton.ac.uk, 
        Pages:      49
        Characters: 125402
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-homenet-arch-17.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7368.txt

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.

This document is a product of the Home Networking Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC