Home Networking Control Protocol
draft-ietf-homenet-hncp-00

The information below is for an old version of the document
Document Type Active Internet-Draft (homenet WG)
Last updated 2014-04-23 (latest revision 2014-04-22)
Replaces draft-stenberg-homenet-hncp
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Homenet Working Group                                        M. Stenberg
Internet-Draft
Intended status: Standards Track                                S. Barth
Expires: October 17, 2014
                                                          April 15, 2014

                    Home Networking Control Protocol
                       draft-ietf-homenet-hncp-00

Abstract

   This document describes the HomeNet Control Protocol (HNCP), a
   minimalist state synchronization protocol for Homenet routers.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 17, 2014.

Copyright Notice

   Copyright (c) 2014 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.

Stenberg & Barth        Expires October 17, 2014                [Page 1]
Internet-Draft      Home Networking Control Protocol          April 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements language . . . . . . . . . . . . . . . . . . . .   3
   3.  Data model  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Trickle-Driven Status Updates . . . . . . . . . . . . . .   4
     4.2.  Protocol Messages . . . . . . . . . . . . . . . . . . . .   5
       4.2.1.  Network State Update (NetState) . . . . . . . . . . .   5
       4.2.2.  Network State Request, (NetState-Req) . . . . . . . .   5
       4.2.3.  Node Data Request (Node-Req)  . . . . . . . . . . . .   6
       4.2.4.  Network and Node State Reply (NetNode-Reply)  . . . .   6
     4.3.  HNCP Protocol Message Processing  . . . . . . . . . . . .   6
     4.4.  Adding and Removing Neighbors . . . . . . . . . . . . . .   8
     4.5.  Purging Unreachable Nodes . . . . . . . . . . . . . . . .   8
   5.  Type-Length-Value objects . . . . . . . . . . . . . . . . . .   8
     5.1.  Request TLVs (for use within unicast requests)  . . . . .   9
       5.1.1.  Request Network State TLV . . . . . . . . . . . . . .   9
       5.1.2.  Request Node Data TLV . . . . . . . . . . . . . . . .   9
     5.2.  Data TLVs (for use in both multi- and unicast data) . . .  10
       5.2.1.  Node Link TLV . . . . . . . . . . . . . . . . . . . .  10
       5.2.2.  Network State TLV . . . . . . . . . . . . . . . . . .  10
       5.2.3.  Node State TLV  . . . . . . . . . . . . . . . . . . .  10
       5.2.4.  Node Data TLV . . . . . . . . . . . . . . . . . . . .  11
       5.2.5.  Node Public Key TLV (within
               Node Data TLV)  . . . . . . . . . . . . . . . . . . .  11
       5.2.6.  Neighbor TLV (within Node Data TLV) . . . . . . . . .  12
     5.3.  Custom TLV (within/without Node Data TLV) . . . . . . . .  12
     5.4.  Version TLV (within Node Data TLV)  . . . . . . . . . . .  13
     5.5.  Authentication TLVs . . . . . . . . . . . . . . . . . . .  13
       5.5.1.  Certificate-related TLVs  . . . . . . . . . . . . . .  13
       5.5.2.  Signature TLV . . . . . . . . . . . . . . . . . . . .  13
   6.  Border Discovery and Prefix Assignment  . . . . . . . . . . .  14
   7.  DNS-based Service Discovery . . . . . . . . . . . . . . . . .  18
     7.1.  DNS Delegated Zone TLV  . . . . . . . . . . . . . . . . .  18
     7.2.  Domain Name TLV . . . . . . . . . . . . . . . . . . . . .  18
     7.3.  Router Name TLV . . . . . . . . . . . . . . . . . . . . .  18
   8.  Routing support . . . . . . . . . . . . . . . . . . . . . . .  19
     8.1.  Protocol Requirements . . . . . . . . . . . . . . . . . .  19
     8.2.  Announcement  . . . . . . . . . . . . . . . . . . . . . .  19
     8.3.  Protocol Selection  . . . . . . . . . . . . . . . . . . .  20
     8.4.  Fallback Mechanism  . . . . . . . . . . . . . . . . . . .  20
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
Show full document text