Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Home Networking Control Protocol (RFC7788)

IP.com Disclosure Number: IPCOM000246699D
Original Publication Date: 2016-Apr-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 80 page(s) / 94K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Stenberg: AUTHOR [+3]

Abstract

The Home Networking Control Protocol (HNCP) is designed to facilitate the sharing of state among home routers to fulfill the needs of the IPv6 homenet architecture [RFC7368], which assumes zero-configuration operation, multiple subnets, multiple home routers, and (potentially) multiple upstream service providers providing (potentially) multiple prefixes to the home network. While RFC 7368 sets no requirements for IPv4 support, HNCP aims to support the dual-stack mode of operation, and therefore the functionality is designed with that in mind. The state is shared as TLVs transported in the DNCP node state among the routers (and potentially advanced hosts) to enable:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                       M. Stenberg Request for Comments: 7788                                      S. Barth Category: Standards Track                                    Independent ISSN: 2070-1721                                               P. Pfister                                                            Cisco Systems                                                               April 2016

                     Home Networking Control Protocol

Abstract

   This document describes the Home Networking Control Protocol (HNCP),    an extensible configuration protocol, and a set of requirements for    home network devices.  HNCP is described as a profile of and    extension to the Distributed Node Consensus Protocol (DNCP).  HNCP    enables discovery of network borders, automated configuration of    addresses, name resolution, service discovery, and the use of any    routing protocol that supports routing based on both the source and    destination address.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7788.

Stenberg, et al.             Standards Track                    [Page 1]
 RFC 7788            Home Networking Control Protocol          April 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3

     1.1.  Applicability . . . . . . . . . ....