Homenet vs. the Market: Gap Analysis
draft-lemon-homenet-review-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           T. Lemon
Internet-Draft                                       Nibbhaya Consulting
Intended status: Informational                            March 11, 2019
Expires: September 12, 2019

                  Homenet vs. the Market: Gap Analysis
                     draft-lemon-homenet-review-00

Abstract

   This document discusses the homenet problem space and tries to
   compare what we have both with what the market is now providing, and
   also with what we need.

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 https://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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Lemon                  Expires September 12, 2019               [Page 1]
Internet-Draft               Homenet Review                   March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Finding the Gaps  . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Connectivity between hosts on the homenet . . . . . . . .   4
     2.2.  Connectivity from hosts on the homenet to hosts on the
           internet (single egress)  . . . . . . . . . . . . . . . .   5
     2.3.  Connectivity from hosts on the internet to hosts on the
           homenet . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Support for multi-homing (more than one egress) . . . . .   5
     2.5.  Service discovery . . . . . . . . . . . . . . . . . . . .   6
     2.6.  Roaming between APs . . . . . . . . . . . . . . . . . . .   6
     2.7.  IPv4 Connectivity within the home . . . . . . . . . . . .   6
     2.8.  Connectivity from hosts on IoT leaf networks to hosts on
           the internet  . . . . . . . . . . . . . . . . . . . . . .   6
     2.9.  Connectivity from hosts on the Internet to hosts on IoT
           leaf networks . . . . . . . . . . . . . . . . . . . . . .   7
     2.10. Connectivity between hosts on the same IoT leaf network .   7
     2.11. Connectivity between hosts on different IoT leaf networks
           within the same home  . . . . . . . . . . . . . . . . . .   7
     2.12. Connectivity from hosts on the homenet to hosts on the
           IoT network . . . . . . . . . . . . . . . . . . . . . . .   7
       2.12.1.  Connectivity from hosts on the IoT network to hosts
                on the homenet . . . . . . . . . . . . . . . . . . .   7
     2.13. Isolation between hosts that shouldn't be communicating
           on the homenet  . . . . . . . . . . . . . . . . . . . . .   8
   3.  Themes  . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The Homenet working group has been developing a set of specifications
   for some years with the goal of providing a self-configuring home
   network with potentially multiple routers.  Since Homenet began, the
   market has changed significantly, and it is worth spending some time
   looking at how it has changed and how that changes what, if anything,
   the Homenet working group should be doing.

   Homenet originally set out to provide for a multi-homed network with
   a layer 3 routing topology that would isolate individual subnets in
   the hope of better performance, while preserving end-to-end service
   and allowing for service discovery throughout the home.

   At the time, a typical home network either had a single router, or
   several routers connected together with one or more layers of network
   address translation.  Each router provided an isolated "LAN" link,
   connected to a "WAN" upstream.  Service discovery was restricted to

Lemon                  Expires September 12, 2019               [Page 2]
Show full document text