From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id A8F8021F1C4 for ; Fri, 7 Feb 2014 10:51:43 -0800 (PST) Received: by mail-qc0-f171.google.com with SMTP id n7so6668229qcx.16 for ; Fri, 07 Feb 2014 10:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=JSfiXGM15jreuvx8vgTlAby+bVKCi+mSofufXR1tFWQ=; b=HDLUqWyCwYaViJP8kY+XGfMTBUnKiKwM1tFX/hkef/XGcvWp/VlXQLiGxOcpYWsUQJ vuR3RJ6o4PpUL8gyYIn/wJ8cROVkHlWcNJiFClyb9PnQHihEdb547FiR0N/tTfhJNdWV ZdCvl61EDNChdezjlnZBCY4hXfuT2jtdIuAVB8SmF09XWZwknnE8N3FyT3Ba79hC+DJR /11K8fAANSxmcVbq3WdylXBCdrNfpLvsHU40asgpIYEcmNIopzgs0PpYbXkBQnxelQhT Eca/WzRfXKEN2DdNO+jFRWOAN3/KPZ4WGJlxo7C74ZRrjoshvH+R5AjXZdmwn3Hd63UJ zWmQ== MIME-Version: 1.0 X-Received: by 10.140.49.9 with SMTP id p9mr23229608qga.75.1391799102628; Fri, 07 Feb 2014 10:51:42 -0800 (PST) Received: by 10.224.27.133 with HTTP; Fri, 7 Feb 2014 10:51:42 -0800 (PST) Date: Fri, 7 Feb 2014 13:51:42 -0500 Message-ID: From: Dave Taht To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] HNCP protocol design RFC and code X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 18:51:43 -0000 HNCP is going to solve a lot of problems with border discovery, propagating ipv6 prefixes and other problems like that. It looks like it will break the logjam we've had for 2+ years in homenet with the incendiary "embed config info in routing protocol" vs "embed config in a separate protocol" debate. Some code already exists for openwrt. I haven't had time to read the draft or code fully, but with the latent integration into opewrt's ubus system it seems probable we can replace AHCP in the long run. I love that HNCP uses the trickle protocol underlying. My only glancing comments were that the crypto architecture needs work, and it wasn't clear if /128s could be distributed and there is probably more configuration information that needs to be propagated across a homenet. Also I'd still like to see some ipv4 concerns (like local nat discovery) also addressed. Please make your comments on the homenet mailing list, not here. This is not slated for the upcoming cero stable release. See below for links. ---------- Forwarded message ---------- From: Markus Stenberg Date: Wed, Feb 5, 2014 at 9:52 AM Subject: [homenet] Two new drafts (and third one 'soon') To: "homenet@ietf.org Group" Cc: Markus Stenberg Drafts: http://tools.ietf.org/html/draft-stenberg-homenet-hncp-00 http://tools.ietf.org/html/draft-stenberg-homenet-dnssd-hybrid-proxy-zer= oconf-00 (Generic PA one in the works, but submitted also 'soon') Experimental partial implementation: https://github.com/sbyx/hnetd/ Discuss. Cheers, -Markus _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html