Re: [homenet] Next Steps for Routing Protocol
James Woodyatt <jhw@nestlabs.com> Mon, 17 November 2014 20:23 UTC
Return-Path: <jhw@nestlabs.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57AFD1A9039 for <homenet@ietfa.amsl.com>; Mon, 17 Nov 2014 12:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNdMxPzEuUlm for <homenet@ietfa.amsl.com>; Mon, 17 Nov 2014 12:23:33 -0800 (PST)
Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888701A9007 for <homenet@ietf.org>; Mon, 17 Nov 2014 12:23:32 -0800 (PST)
Received: by mail-vc0-f173.google.com with SMTP id id10so7373878vcb.18 for <homenet@ietf.org>; Mon, 17 Nov 2014 12:23:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1J74S5khOZ+UOUtUtMJ5VOsN09f1husgvHgxFEkWzMQ=; b=EMkAx7W6+jRvtagSCVoNKgUbNysOYbxaWnmMo7gYZk2E9qlxgnLs2fZt+Th/rJI3Qr ou+jd3V1wc476i5mNlb21icvo9hE7sPI5flXnDDj/2xsUrD5zaC8SMnNIN+SL/nZfExC P4zVArikPWE/sgb6dLWoF09SLh0MA3N/z+pr0S4z9Ih+d/lN3gx9oMRY4zOQrYcNyBpa TKMus1e/bQt8o91DEc83h0x8OR96ULQGrmQDT+EL4u+hJendp20WtXmyn4S8X8n9LdtX Rd2SKgXxjeUT7nxiEGoOnBAnZQ6JdQyKm71zFvQ6ZrnpveAypTm0qbJmNELM+GQtCu8H JM4w==
X-Gm-Message-State: ALoCoQlQl6rEiI2XliIFvCLR5HK0NYCU099RUhxNiEj07iY6p/i5puarVU3ATpGb/qfC5hNvM+MV
MIME-Version: 1.0
X-Received: by 10.52.165.164 with SMTP id yz4mr3074922vdb.73.1416255809910; Mon, 17 Nov 2014 12:23:29 -0800 (PST)
Received: by 10.31.10.65 with HTTP; Mon, 17 Nov 2014 12:23:29 -0800 (PST)
In-Reply-To: <CAA93jw4uJ+dWKXwsvM35ZCYWD-epJmnSj=5L9cJj6XtRWV3vwg@mail.gmail.com>
References: <CAESTAVvW5YrL03xhsE11LZT5P2Sxz0=itJQ9nNoji9mXDPGgsw@mail.gmail.com> <87wq6w5ugq.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4uJ+dWKXwsvM35ZCYWD-epJmnSj=5L9cJj6XtRWV3vwg@mail.gmail.com>
Date: Mon, 17 Nov 2014 12:23:29 -0800
Message-ID: <CADhXe515pLCkuxKuDP+vQiYU+gEn9ge8j2zzw8Prg=S_rE26ZA@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: Dave Taht <dave.taht@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c2083a760f8f050813c0f6"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/oBFVSOgn08I56ROSmGlBDBu0oIo
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Next Steps for Routing Protocol
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: Mon, 17 Nov 2014 20:23:46 -0000
Dave, At Nest, we have different OS platforms we use depending on the constraints of the hardware. For things like the Nest Learning Thermostat, where there is a graphics subsystem and such, we use a $POSIX variant commonly found in larger embedded systems. It has not much flash and even less memory. We cut a lot of things out to make everything we need to fit, and we feel significant volatile and non-volatile memory pressure on this platform. For things like the Nest Protect, which are much smaller, we use a library-oriented $RTOS variant. The current Nest Protect device, for example, executes code from 512 kB of flash, using 64 kB of RAM. It has a very lightweight IPv6 stack, over which we have implemented all our communications protocols and our application logic. We are under truly extraordinary memory pressures on this platform, of the sort that I believe only somebody with experience working in the C64 demoware scene can fully appreciate. (Seriously, you can't even. Don't try.) I'm hoping future evolutions both in these product lines might have incrementally more resources, in which it may be possible to demand space for Comms Engineering to insert HNCP, when it's finally deployable. Assuming HNCP can be made to work. Lot of ifs. However, whatever happens, we eventually will need something that does what HNCP does, and I like HNCP itself better than I like the idea of rolling something proprietary. Does that help explain matters? On Sat, Nov 15, 2014 at 8:46 AM, Dave Taht <dave.taht@gmail.com> wrote: > On Sat, Nov 15, 2014 at 7:55 AM, Juliusz Chroboczek > <jch@pps.univ-paris-diderot.fr> wrote: > >> This included technical discussion around a partially unanticipated > > I have always felt that we needed to have something that could route > packets as best as possible based on conditions (and in particular > transport configuration information) across many disparate link layers > - homeplug, MoCa, 802.11, 802.11ad, 802.14, 6lowpan, VPNs, and sharks > with lasers. ( > https://twitter.com/RalfMuehlen/status/533414954167070720/photo/1 > ). > > While full compliance with rfc2549 is not required, wires as we knew > them are going the way of the dodo, and already have, in most homes > and small businesses. > > >> requirement for HNCP to support a stub network with a gateway that > >> doesn't have sufficient resources to run a routing protocol. > > Could someone describe what sort of resources these gateways (nest, I > assume) actually have? - What OS they run, how much ram and flash is > on them, is there virtual memory, etc? > > Are there devices in this category that can be hacked on? I am > reminded of the dnssec debate put to rest by merely producing a proof > of concept on an ancient cpe... I mean, babel, for example, is like, > 61k, on mips with the sole dependency on libc. Other daemons, like > pimd are in the same size category. > > > > > Mark, > > > > Could you please spell out the requirements for a stub-only > > implementation? Do you expect the stub router to hold the full routing > > table, or just two routes (connected network and default route)? > > > > Is there interest in a stub-only implementation of Babel? Should it be > > a standalone daemon, or should it be integrated in the HNCP daemon? > > > > -- Juliusz > > > > _______________________________________________ > > homenet mailing list > > homenet@ietf.org > > https://www.ietf.org/mailman/listinfo/homenet > > > > -- > Dave Täht > > thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet > -- james woodyatt <jhw@nestlabs.com> Nest Labs, Communications Engineering
- [homenet] Next Steps for Routing Protocol Mark Townsley
- Re: [homenet] Next Steps for Routing Protocol Markus Stenberg
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Margaret Wasserman
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Acee Lindem (acee)
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Acee Lindem (acee)
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Mikael Abrahamsson
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Ole Troan
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Acee Lindem (acee)
- Re: [homenet] Next Steps for Routing Protocol Teco Boot
- Re: [homenet] Next Steps for Routing Protocol Mikael Abrahamsson
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- [homenet] Stub-only Babel [was: Next Steps for Ro… Juliusz Chroboczek
- Re: [homenet] Stub-only Babel [was: Next Steps fo… Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Pierre Pfister
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Pierre Pfister
- Re: [homenet] Next Steps for Routing Protocol Pierre Pfister
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Lorenzo Colitti
- Re: [homenet] Next Steps for Routing Protocol Teco Boot
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Markus Stenberg
- Re: [homenet] Next Steps for HNCP Pierre Pfister
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Mikael Abrahamsson
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Henning Rogge
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Margaret Wasserman
- Re: [homenet] Next Steps for Routing Protocol Margaret Wasserman
- Re: [homenet] Next Steps for Routing Protocol Margaret Wasserman
- Re: [homenet] Next Steps for Routing Protocol Henning Rogge
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol James Woodyatt
- Re: [homenet] Next Steps for Routing Protocol Ole Troan
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Ole Troan
- Re: [homenet] Next Steps for Routing Protocol Steven Barth
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Stub-only Babel [was: Next Steps fo… Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Michael Richardson
- Re: [homenet] Next Steps for Routing Protocol Teco Boot
- Re: [homenet] Next Steps for Routing Protocol Acee Lindem (acee)
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Acee Lindem (acee)
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Juliusz Chroboczek
- Re: [homenet] Next Steps for Routing Protocol Dave Taht
- Re: [homenet] Next Steps for Routing Protocol Steven Barth