
From nobody Mon Mar  3 03:48:24 2014
Return-Path: <mglt.ietf@gmail.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 B39921A001D; Mon,  3 Mar 2014 03:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 Jl1k9DvXfGBe; Mon,  3 Mar 2014 03:48:18 -0800 (PST)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3161A0032; Mon,  3 Mar 2014 03:48:18 -0800 (PST)
Received: by mail-wg0-f45.google.com with SMTP id m15so3025628wgh.28 for <multiple recipients>; Mon, 03 Mar 2014 03:48:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EX/d1Txs1ysE5asJCj1sP6TBvXynMUaY6DvP5UHawmA=; b=Qj+jCwIqk4UWhsmGnY75FNr4Wu4FQ04U5TfWamtPKqUPFMCGuszrfrlsNfINsEG5Co YvqXDD3lzcWEmEDVv+YSEuRJzUYMqDkbmTg3pRc7FZk+4vm/DDUt0Jr4eQlaXUJVLFPW EL5O5SV2CO7wmo1k0DVwwWeUPbh+2BeOiPjOivOh4JZKG323AZgsitJ9qYD1qrHuBJ9y 8FDKSBu8C146Nglg+wkyS75QqmUkaiGXglsI6SBAoht78MRMLmEr8QcgxudOvKnin3w1 1NHXbAOhjqLL4hmT+apyw/rQPF5YUpJkFmMhJJefafzxBwODfzV46MQ4wNhqv45H8wR2 DSdw==
MIME-Version: 1.0
X-Received: by 10.194.24.35 with SMTP id r3mr5021889wjf.68.1393847294900; Mon, 03 Mar 2014 03:48:14 -0800 (PST)
Received: by 10.194.171.225 with HTTP; Mon, 3 Mar 2014 03:48:14 -0800 (PST)
In-Reply-To: <CADZyTkmKZnerSMJhZk3zv1MD1QG-AByL1aLcdGwT6Su1C-rpCQ@mail.gmail.com>
References: <CADZyTkmKZnerSMJhZk3zv1MD1QG-AByL1aLcdGwT6Su1C-rpCQ@mail.gmail.com>
Date: Mon, 3 Mar 2014 12:48:14 +0100
Message-ID: <CADZyTknuMa=kX99_jXzO0W8RO14iNwWzksw_XaJQcAfyO9BbhA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: "homenet@ietf.org" <homenet@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/FlDX8NkashpsK7OOgnsPO2MumRc
Subject: [homenet] Fwd: draft-mglt-homenet-naming-architecture-dhc-options-01
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, 03 Mar 2014 11:48:21 -0000

Hi,

Summarizing feed backs from the DHCP WG here is what we had:
    - 1) Do not use FQDN AND IP6 address in the Payload. Use one of the other.
    - 2) Do not use TSIG payloads,

non DHCP-related comments:
    - 3) Do not limit to server / slave synchronization, enable nsupdates
    - 4) This option may address other type of networks and should not
be limited to homenet.
    - 5) Maybe another one, I have to check with Lorenzo.

For 1) I suggest we keep the FQDN. This makes the mechanism work for
IPv6 and IPv4. The reason we added the IP6 address is to avoid a DNS
resolution. It does not seems an issue.
For 2) I agree, we will remove TSIG payload in the next version.
For 3) I agree most probably we need to extend the "Security" to
consider nsupdate_sig(0), master-slave-synchronization....
For 4) Agree, we need to document these cases to make sure options are
designed to address these cases. [Text on that is welcome]

BR
Daniel

---------- Forwarded message ----------
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Thu, Feb 13, 2014 at 5:37 PM
Subject: draft-mglt-homenet-naming-architecture-dhc-options-01
To: "homenet@ietf.org" <homenet@ietf.org>


Hi,

Please find the new version of the draft
draft-mglt-homenet-naming-architecture-dhc-options-01. It defines DHCP
Options to configure the Homenet naming architecture.

Feel free to comment!

BR,
Daniel

A new version of I-D, draft-mglt-homenet-naming-architecture-dhc-options-01.txt
has been successfully submitted by Daniel Migault and posted to the
IETF repository.

Name: draft-mglt-homenet-naming-architecture-dhc-options
Revision: 01
Title: DHCP Options for Homenet Naming Architecture
Document date: 2014-02-13
Group: Individual Submission
Pages: 18
URL:
http://www.ietf.org/internet-drafts/draft-mglt-homenet-naming-architecture-dhc-options-01.txt
Status:
https://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options/
Htmlized:
http://tools.ietf.org/html/draft-mglt-homenet-naming-architecture-dhc-options-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-mglt-homenet-naming-architecture-dhc-options-01

Abstract:
   The home network naming architecture requires a complex naming
   configuration on the CPE.  This configuration MAY not be handled
   easily by the average end user.  Furthermore, such misconfiguration
   MAY result in making home network unreachable.

   This document proposes a DHCP options that provide the CPE all
   necessary parameters to set up the home network naming architecture.

   First, this DHCP options provide automatic configuration and avoid
   most end users' misconfiguration.  Most average end users may not
   require specific configuration, and their ISP default configuration
   MAY fully address their needs.  In that case, the naming homenet
   architecture configuration will be completely transparent to the end
   users.  Then, saving naming configuration outside the CPE, makes it
   resilient to change of CPE or CPE upgrades.  Such configuration may
   also be configured by the end user, via the customer area of their
   ISP.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



--
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58


-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58


From nobody Tue Mar  4 02:00:42 2014
Return-Path: <marka@isc.org>
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 E59FB1A04A6 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 7SAfo6mdaVfm for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:00:38 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 715BA1A046A for <homenet@ietf.org>; Tue,  4 Mar 2014 02:00:38 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 981A2238426 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:00:23 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EA963160058 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:01:18 +0000 (UTC)
Received: from rock.dv.isc.org (dhcp-b59a.meeting.ietf.org [31.133.181.154]) by zmx1.isc.org (Postfix) with ESMTPSA id C52A516004E for <homenet@ietf.org>; Tue,  4 Mar 2014 10:01:18 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2718110AD645 for <homenet@ietf.org>; Tue,  4 Mar 2014 21:00:21 +1100 (EST)
To: homenet@ietf.org
From: Mark Andrews <marka@isc.org>
Date: Tue, 04 Mar 2014 21:00:21 +1100
Message-Id: <20140304100021.2718110AD645@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/GB9Q5HkpfxVkE7vwMvSOH1C4KRE
Subject: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:00:40 -0000

	The optimal place to sign DNS zones is where they are
	generated.  For homenet this is in the home.

	For zeroconf the CPE generates DNSKEY records and pushes
	DS records for them to the parent zone.  We know how to do
	this securely.

	If you replace a CPE it just pushed new DS records for the
	new DNSKEY records it generates.  This is equivalent to a
	emergency key rollover and only impacts client that have
	cached records for the zone or its DS records.

	For split horizon zones you use the same DNSKEYS in all
	versions of the zone.  This prevents issues with cached
	DS/DNSKEY records as machines move from being locally
	connected to externally connected.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org


From nobody Tue Mar  4 02:06:29 2014
Return-Path: <marka@isc.org>
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 440A81A0546 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, 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 12RCcB1jF_9l for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:06:24 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8371A053B for <homenet@ietf.org>; Tue,  4 Mar 2014 02:06:23 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 64194238424 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:06:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id B48BF160058 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:07:03 +0000 (UTC)
Received: from rock.dv.isc.org (dhcp-b59a.meeting.ietf.org [31.133.181.154]) by zmx1.isc.org (Postfix) with ESMTPSA id 8F2BE16004E for <homenet@ietf.org>; Tue,  4 Mar 2014 10:07:03 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id DD2FF10AD6A9 for <homenet@ietf.org>; Tue,  4 Mar 2014 21:06:06 +1100 (EST)
To: homenet@ietf.org
From: Mark Andrews <marka@isc.org>
Date: Tue, 04 Mar 2014 21:06:06 +1100
Message-Id: <20140304100606.DD2FF10AD6A9@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/oSzM0MgUDrmjyEqM4rJRwNK-n2U
Subject: [homenet] DHCP DNSSEC Time Option
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: Tue, 04 Mar 2014 10:06:26 -0000

	This should be a 32 bit value calculated exactly the same
	way that the inception and expire fields of a RRSIG are
	generated.  Seconds since 00:00:00 Jan 1 1970 UTC, excluing
	leap seconds, modulo 2^32.

	This prevents common issues like mis-handling of leap years
	in converting from text to binary.

	This allow clients to use the value directly to initialise
	a clock with a 1 hz freqency for use for DNSSEC validation.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org


From nobody Tue Mar  4 02:09:12 2014
Return-Path: <dns@fl1ger.de>
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 837E61A04E9 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 DgFzir1dMwmV for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:09:08 -0800 (PST)
Received: from nox.guxx.net (nox.guxx.net [78.46.109.173]) by ietfa.amsl.com (Postfix) with ESMTP id AED971A049E for <homenet@ietf.org>; Tue,  4 Mar 2014 02:08:58 -0800 (PST)
Received: by nox.guxx.net (Postfix, from userid 65534) id 8957ADB8268; Tue,  4 Mar 2014 11:08:54 +0100 (CET)
Received: from dhcp-a6e3.meeting.ietf.org (dhcp-a6e3.meeting.ietf.org [31.133.166.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nox.guxx.net (Postfix) with ESMTPSA id DEB47DB817F; Tue,  4 Mar 2014 11:08:53 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ralf Weber <dns@fl1ger.de>
In-Reply-To: <20140304100021.2718110AD645@rock.dv.isc.org>
Date: Tue, 4 Mar 2014 10:08:53 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
References: <20140304100021.2718110AD645@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/kxEytYGqRxN7P2IWY8ivx9aRRFY
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:09:10 -0000

Moin!

On 04 Mar 2014, at 10:00, Mark Andrews <marka@isc.org> wrote:

> 	If you replace a CPE it just pushed new DS records for the
> 	new DNSKEY records it generates.  This is equivalent to a
> 	emergency key rollover and only impacts client that have
> 	cached records for the zone or its DS records.
What if the new device doesn't support DNSSEC signing? I still think =
there are reasons to support both archictectures (signing on the CPE or =
on the ISP auth name server). I have no problem with signing on the CPE. =
I just don't want to make it mandatory, as I have seen more problems =
with CPEs than with ISP operations (ok I may be biased here working in =
ISP operations for 15 years ;-).

So long
-Ralf


From nobody Tue Mar  4 02:15:56 2014
Return-Path: <marka@isc.org>
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 BCFBD1A0527 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:15:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 D2AH8nyAWS2X for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:15:53 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 236AC1A03FC for <homenet@ietf.org>; Tue,  4 Mar 2014 02:15:53 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id AB6ACC9481; Tue,  4 Mar 2014 10:15:37 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393928150; bh=PsAhG0iQyu+hsMMr60JZXPeSH1rNKkjW+Q5o2GZpXYk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=nT2KwvnDkiuRIZh2M2QPxFeflOd3zvvADiRGZtcV+0EfjXae/MfQNAj077A7cwPWZ 5cE5l12ZFAJpbvo+g6e8+G1V05FfUWKxJwz2MNIYdfHod0H3YxS32fmpXkE3xJqG0e Gs+iLTYYM/aH6ivPvGQbN6EXo10mNx+qq5ug6j48=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue,  4 Mar 2014 10:15:37 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8A044160058; Tue,  4 Mar 2014 10:16:33 +0000 (UTC)
Received: from rock.dv.isc.org (dhcp-b59a.meeting.ietf.org [31.133.181.154]) by zmx1.isc.org (Postfix) with ESMTPSA id 655AB16004E; Tue,  4 Mar 2014 10:16:33 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id CAECD10AD88C; Tue,  4 Mar 2014 21:15:36 +1100 (EST)
To: Ralf Weber <dns@fl1ger.de>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
In-reply-to: Your message of "Tue, 04 Mar 2014 10:08:53 -0000." <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
Date: Tue, 04 Mar 2014 21:15:36 +1100
Message-Id: <20140304101536.CAECD10AD88C@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/tDV2eOSRh52r5QINs8huMYIBqPQ
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:15:55 -0000

In message <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>, Ralf Weber writes:
> Moin!
>
> On 04 Mar 2014, at 10:00, Mark Andrews <marka@isc.org> wrote:
>
> > 	If you replace a CPE it just pushed new DS records for the
> > 	new DNSKEY records it generates.  This is equivalent to a
> > 	emergency key rollover and only impacts client that have
> > 	cached records for the zone or its DS records.
> What if the new device doesn't support DNSSEC signing? I still think
> there are reasons to support both archictectures (signing on the CPE or
> on the ISP auth name server). I have no problem with signing on the CPE.
> I just don't want to make it mandatory, as I have seen more problems with
> CPEs than with ISP operations (ok I may be biased here working in ISP
> operations for 15 years ;-).
>
> So long
> -Ralf

The CPE that doesn't sign clears the DS records rather than adding /
replacing the DS records.  The zones still need to be delegated.
If the CPE doesn't request deletations.  The ISP DHCP server clears
the delegation from its zones and that includes DS records.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Mar  4 02:39:29 2014
Return-Path: <mcr@sandelman.ca>
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 3DB501A049D for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.981
X-Spam-Level: 
X-Spam-Status: No, score=-0.981 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 576wPuAUboGp for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:39:26 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 212431A0535 for <homenet@ietf.org>; Tue,  4 Mar 2014 02:39:26 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0A4D120050 for <homenet@ietf.org>; Tue,  4 Mar 2014 06:57:53 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 98348647C9; Tue,  4 Mar 2014 05:39:22 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 83026647C8 for <homenet@ietf.org>; Tue,  4 Mar 2014 05:39:22 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <20140304100021.2718110AD645@rock.dv.isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 05:39:22 -0500
Message-ID: <334.1393929562@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Yu6j4FjsRswv0pg4D03IjWNH_Qc
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:39:27 -0000

--=-=-=


My three points that I made:

1) if the key resides in the CPE, then the ISP-owned CPE deployment
   is functionally identical to the Mark-Andrews/Michael-Richardson owned CPE
   deployment.
   => perhaps the underlying worry is that unless CPE-borne DNSSEC isn't
      the default/only-choice, that ISPs won't support it, and those of us that care
      will, again, be left in the cold.
      There is significant precedent that given a choice, ISP have made
      poor choices, and some of those choices have become architectural
      catatrophies.

   I agree with Mark: there is no issue with replacement of CPEs, etc.
   I don't think that I would move the private key from one CPE to another.
   For the reverse zone, just a new private key and populate that.
   For a forward zone that I owned, I would push a new DS record upwards.
   The likely reason for a new CPE is that the blue smoke got out of the old
   one.  If the models were compatible, and I had a backup of the config,
   then perhaps the private key would move, but that seems doubtful for most
   users.

2) what Andrew Sullivan said: if the keys are different for inside the home
   vs for outside the home, then any mobile node will get confused and/or
   will have to flush it's DNS cache way too often.

3) the perpass/National-Security-Letter situation.
   If the key by default resides at the ISP, then it is the ISP that gets
   served when some agency thinks it wants to divert traffic by changing DNS,
   and once served, the net may may be much larger than desired.
   By putting the key in the CPE, the legal papers will have to specify that
   device.  It may still be the ISP legal department that responds, but the
   chance of screwing up is larger.

   While it seems like the ISP might be better able to protect a single
   private key against various vulnerability; having more technical people
   than the average home user, etc... the impact of a compromise is so much
   larger.   Yes, home routers have vulnerabilities:  if we assume that they
   are breachable, then the breach can just change the unsigned data, having
   the private key at the ISP doesn't help us at all.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxWtWoqHRg3pndX9AQIONAQAkD0AMdTme6620abfMLfPc8hOa3XeLDYe
CnsaVN0KT0GjZ7FMVHWG3mTxtcNe0mdGrejRbk4dcfjxgr1vGYudTXVeuThBP5sb
CJevxOp024BZWv1k+QqbE6n4zOlJ8LDazneIqZfNtGb9qL2gBMyHYNckKPPXWESz
XiM8rRko2n8=
=MfFL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 02:45:54 2014
Return-Path: <mcr@sandelman.ca>
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 051481A023D for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:45:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 mi0SUds2Cjgj for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:45:51 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 0444A1A0191 for <homenet@ietf.org>; Tue,  4 Mar 2014 02:45:51 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2098520050 for <homenet@ietf.org>; Tue,  4 Mar 2014 07:04:18 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id BF23B647C9; Tue,  4 Mar 2014 05:45:47 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A732B647C8 for <homenet@ietf.org>; Tue,  4 Mar 2014 05:45:47 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 05:45:47 -0500
Message-ID: <1681.1393929947@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/jYjQUwbMLXb4A0xdIY4N0z-qiwM
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:45:52 -0000

--=-=-=


Ralf Weber <dns@fl1ger.de> wrote:
    > On 04 Mar 2014, at 10:00, Mark Andrews <marka@isc.org> wrote:

    >> If you replace a CPE it just pushed new DS records for the
    >> new DNSKEY records it generates.  This is equivalent to a
    >> emergency key rollover and only impacts client that have
    >> cached records for the zone or its DS records.

    > What if the new device doesn't support DNSSEC signing? I still think
    > there are reasons to support both archictectures (signing on the CPE or

Then I think that it doesn't support DNS delegation anyway.

Ralf Weber <dns@fl1ger.de> wrote:
    > CPE. I just don't want to make it mandatory, as I have seen more
    > problems with CPEs than with ISP operations (ok I may be biased here
    > working in ISP operations for 15 years ;-).

I also have many years of experience in ISP operations as a consultant and owner.
ISPs make a lot of short-term decisions that bite them later on.
I observe a pendulum of picking the cheapest CPE device, followed by picking
an overkill CPE device (for their "managed" service). Lather, rinse, repeat.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxWu24qHRg3pndX9AQJOcQQAxbrOmSkwVBK7uNsi/QU8Ad3B1Fionhjr
kB7mhJjh3UkHGwPnGP7bgATL9jsDXJVYFaZLNJ7LIItOu9YpQ9EudfRyQBcQa8tc
dJpPINAjpPQrq+kpGDM6xvwMi6HMxVB5sP1vg7KN99wMsvErbJKxC2TacZtz7dLw
FycRbMO46MM=
=nyGR
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 02:52:37 2014
Return-Path: <ajs@anvilwalrusden.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 EBCCA1A03AC for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 xoy3jyV1ylnI for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 02:52:33 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 71D721A02CE for <homenet@ietf.org>; Tue,  4 Mar 2014 02:52:33 -0800 (PST)
Received: from mx1.yitter.info (dhcp-bca3.meeting.ietf.org [31.133.188.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9B9608A031 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:52:20 +0000 (UTC)
Date: Tue, 4 Mar 2014 05:52:18 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20140304105217.GD8224@mx1.yitter.info>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/gKOMSwczXjV34wCqD31tb1kbHbQ
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 10:52:35 -0000

On Tue, Mar 04, 2014 at 10:08:53AM +0000, Ralf Weber wrote:

> or on the ISP auth name server). I have no problem with signing on
> the CPE. I just don't want to make it mandatory

For the purposes of this discussion, I'm going to assume that one has
an inward-facing zone and and outward-facing one (i.e. this is a
split-brain DNS situation).

Now, if the inward-facing DNS (wherever it's run -- CPE or elsewhere
in the homenet) signs anything, then you must have common keys for the
outward-facing DNS.  (I suppose as an alternative, you could use
extremely low TTLs on your zones -- say, a few minutes).  This is
because one of the use cases we originally had in mind was that you
carry your laptop off to some out-of-homenet network and want access
to services inside the homenet.

Since we're all wandering around with a DNS cache on our laptops any
more, you could easily get an answer back from (say) the homenet DNS
with the DNSKEY record.  You will cache it.

If you then go to some other network, you will try to validate with
that DNSKEY that you have cached (until it expires).  If you then
query for some resource inside the homenet for a record you don't
already have cached, you'll need to be able to validate it; so it
needs to be validatable using that same cached key record.  If it's
not, then the data will validate bogus and you'll fail to connect.

The same issue is true in the other direction. 

So if we're going to say that the signing may happen in the ISP's
infrastructure, then either (1) we need a mechanism to share private
keys (which sounds like a bozo move to me or (2) we need to state that
it is incompatible with using DNSSEC in the inward-facing zone or (3)
we need to state that any access to any DNSSEC-signed name in the
outward zone should be expected to route through the ISP link;
inside-homenet-only names may use in-homenet interfaces.  (I'm sure
there's a more elegant way to say that, but I've written in haste.)

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Mar  4 03:42:00 2014
Return-Path: <mcr@sandelman.ca>
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 509521A0034 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 03:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no
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 L6b1S0_3nZI0 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 03:41:56 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 50B8C1A002A for <homenet@ietf.org>; Tue,  4 Mar 2014 03:41:56 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 055F12006D; Tue,  4 Mar 2014 08:00:22 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 8B371647C9; Tue,  4 Mar 2014 06:41:51 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 78370647C8; Tue,  4 Mar 2014 06:41:51 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20140304105217.GD8224@mx1.yitter.info>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 06:41:51 -0500
Message-ID: <13623.1393933311@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/4P0khhOFllA1Jxhk0flbDqqsQ7o
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 11:41:57 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
    > Now, if the inward-facing DNS (wherever it's run -- CPE or elsewhere
    > in the homenet) signs anything, then you must have common keys for the
    > outward-facing DNS.  (I suppose as an alternative, you could use
    > extremely low TTLs on your zones -- say, a few minutes).  This is
    > because one of the use cases we originally had in mind was that you
    > carry your laptop off to some out-of-homenet network and want access
    > to services inside the homenet.

While it's a good use case example, a better one is that your smartphone
wanders on your person, inside your home, and then uses 3G for a few seconds
when you wander onto the porch, and the wifi signal goes to zero.

The important thing is that you didn't do anything to actually "leave" your
home, while the laptop situation is perhaps more intentional, and contains
many possible signals that a cache should be flushed.

    > Since we're all wandering around with a DNS cache on our laptops any
    > more, you could easily get an answer back from (say) the homenet DNS
    > with the DNSKEY record.  You will cache it.

The MIF people have some statements about flushing caches, and about caching
on a per-interface basis. (I think that this is all wrong, btw)

    > So if we're going to say that the signing may happen in the ISP's
    > infrastructure, then either (1) we need a mechanism to share private
    > keys (which sounds like a bozo move to me or (2) we need to state that
    > it is incompatible with using DNSSEC in the inward-facing zone or (3)
    > we need to state that any access to any DNSSEC-signed name in the
    > outward zone should be expected to route through the ISP link;
    > inside-homenet-only names may use in-homenet interfaces.  (I'm sure
    > there's a more elegant way to say that, but I've written in haste.)

A fourth option is that the name from the outside is different than the name
From=20the inside.  I think that this is the least interesting version.


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting for hire =3D-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxW7/4qHRg3pndX9AQK5KQP/QLUw2mPccpu72ZLJo6Af5haxRhTy+ty9
wA5qiKF1oVTWwllBTEtt8tdPwuoVIKv0q717vi7mV6rOvXjAevGGpnLZKnVzlER/
nygmhrVb5XZBsNzSUOpHhaKpc/MqtNnHjvOCGKgr4U9EukNtHCPF+oIQz8f1EtDC
C9TkMVhneBY=
=sOgy
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 04:28:26 2014
Return-Path: <v6ops@globis.net>
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 C09C81A0085 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 04:28:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 dw0dIzjk1Tg8 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 04:28:22 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7B31A0099 for <homenet@ietf.org>; Tue,  4 Mar 2014 04:28:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 269378714A4; Tue,  4 Mar 2014 13:28:17 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zizDcUrd8gE0; Tue,  4 Mar 2014 13:28:16 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id C9BA48714A2; Tue,  4 Mar 2014 13:28:16 +0100 (CET)
Message-ID: <5315C6DF.4030608@globis.net>
Date: Tue, 04 Mar 2014 13:28:15 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info>
In-Reply-To: <20140304105217.GD8224@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Q3cNLA05ZzNHeRAFbxN_-LDGYKw
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 12:28:24 -0000

inline.

Andrew Sullivan wrote:
> On Tue, Mar 04, 2014 at 10:08:53AM +0000, Ralf Weber wrote:
>
>> or on the ISP auth name server). I have no problem with signing on
>> the CPE. I just don't want to make it mandatory
>
> For the purposes of this discussion, I'm going to assume that one has
> an inward-facing zone and and outward-facing one (i.e. this is a
> split-brain DNS situation).

I think even large corporations are slowly learning that split-brain DNS 
is a bad idea that seemed like a good idea at the time, especially in 
the presence of highly-mobile devices, and forwarders.

I'm becoming a convert myself to that way of thinking. That doesn't mean 
to say that we can't use 'views' or some other mechanism to hide some 
records from being resolvable from the outside.
>
> Now, if the inward-facing DNS (wherever it's run -- CPE or elsewhere
> in the homenet) signs anything, then you must have common keys for the
> outward-facing DNS.  (I suppose as an alternative, you could use
> extremely low TTLs on your zones -- say, a few minutes).  This is
> because one of the use cases we originally had in mind was that you
> carry your laptop off to some out-of-homenet network and want access
> to services inside the homenet.
>
> Since we're all wandering around with a DNS cache on our laptops any
> more, you could easily get an answer back from (say) the homenet DNS
> with the DNSKEY record.  You will cache it.
>
> If you then go to some other network, you will try to validate with
> that DNSKEY that you have cached (until it expires).  If you then
> query for some resource inside the homenet for a record you don't
> already have cached, you'll need to be able to validate it; so it
> needs to be validatable using that same cached key record.  If it's
> not, then the data will validate bogus and you'll fail to connect.
>
> The same issue is true in the other direction.
>
> So if we're going to say that the signing may happen in the ISP's
> infrastructure, then either (1) we need a mechanism to share private
> keys (which sounds like a bozo move to me or (2) we need to state that
> it is incompatible with using DNSSEC in the inward-facing zone or (3)
> we need to state that any access to any DNSSEC-signed name in the
> outward zone should be expected to route through the ISP link;
> inside-homenet-only names may use in-homenet interfaces.  (I'm sure
> there's a more elegant way to say that, but I've written in haste.)
>
> Best regards,
>
> A
>

-- 
Regards,
RayH


From nobody Tue Mar  4 04:51:53 2014
Return-Path: <sm@resistor.net>
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 1DA4E1A00AE for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 04:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
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 1m2xE3W_HqW1 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 04:51:50 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A53C1A00BE for <homenet@ietf.org>; Tue,  4 Mar 2014 04:51:49 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s24Cpa1Y025244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Mar 2014 04:51:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393937503; bh=S3plPsN1RfM8YhhdlduT6JTH9u/SuqsWLsDypGq2ngw=; h=Date:To:From:Subject:In-Reply-To:References; b=P7bGYy4mlab6WdFHOMjyiRbyBH1LaolYSZcXJ348bZCjSr/b4sJaVyqyFb0ab6viU erdlbQIKNsdjJ08NcOXVNCV3R3paBW9RRDdml4QYeolTH/FSQS9uzT/3Db5QNQe7EC cjs7XAypwNglzg8GHDMAaJFSvuGFA830sDffpmtk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1393937503; i=@resistor.net; bh=S3plPsN1RfM8YhhdlduT6JTH9u/SuqsWLsDypGq2ngw=; h=Date:To:From:Subject:In-Reply-To:References; b=ENej9dlxOcDDiinXcadOxj7kEqFqLkUdPJyhlQpLHYrobHNoPuq12ySXqUbhHy+gt O5ENwZphM8jCuYxXx+oBBd1WFjcyeDl4ND91UEr08LPEea6q/t15wpthgDVpHQOtGv d86zKpqkUUN9gIDDnAJWFocQFxLImwqLDhnnvF8M=
Message-Id: <6.2.5.6.2.20140304043321.0c893400@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 04 Mar 2014 04:50:33 -0800
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <20140304105217.GD8224@mx1.yitter.info>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/GdIYICrRYCapjQ-Hb2XiorWpWrk
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 12:51:51 -0000

Hi Andrew,
At 02:52 04-03-2014, Andrew Sullivan wrote:
>Since we're all wandering around with a DNS cache on our laptops any
>more, you could easily get an answer back from (say) the homenet DNS
>with the DNSKEY record.  You will cache it.
>
>If you then go to some other network, you will try to validate with
>that DNSKEY that you have cached (until it expires).  If you then
>query for some resource inside the homenet for a record you don't
>already have cached, you'll need to be able to validate it; so it
>needs to be validatable using that same cached key record.  If it's
>not, then the data will validate bogus and you'll fail to connect.

That's an interesting case.  I did not think of it.  If I understood 
correctly the answer in the DNS cache would be for a non-global 
resource.  There is no longer an assumption of uniqueness.  As a 
local decision I would use low TTLs [1].

Regards,
-sm

1. I gave some thought to the state of connectivity in future.  I 
suspect that there would be edge cases.  I don't know whether it is 
worth discussing about those cases. 


From nobody Tue Mar  4 05:30:44 2014
Return-Path: <mcr@sandelman.ca>
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 B897F1A0187 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 05:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 yp-9nXkKA5FP for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 05:30:39 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 374191A0183 for <homenet@ietf.org>; Tue,  4 Mar 2014 05:30:39 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2FF7920050; Tue,  4 Mar 2014 09:49:06 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 75566647C9; Tue,  4 Mar 2014 08:30:35 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5B12D647C8; Tue,  4 Mar 2014 08:30:35 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <5315C6DF.4030608@globis.net>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <5315C6DF.4030608@globis.net>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 08:30:35 -0500
Message-ID: <4153.1393939835@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/vbbAaDdoaL7Yb1WQeAnQg_NDXGU
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 13:30:41 -0000

--=-=-=


Ray Hunter <v6ops@globis.net> wrote:
    >> On Tue, Mar 04, 2014 at 10:08:53AM +0000, Ralf Weber wrote:
    >>
    >>> or on the ISP auth name server). I have no problem with signing on
    >>> the CPE. I just don't want to make it mandatory
    >>
    >> For the purposes of this discussion, I'm going to assume that one has
    >> an inward-facing zone and and outward-facing one (i.e. this is a
    >> split-brain DNS situation).

    > I think even large corporations are slowly learning that split-brain
    > DNS is a bad idea that seemed like a good idea at the time, especially
    > in the presence of highly-mobile devices, and forwarders.

    > I'm becoming a convert myself to that way of thinking. That doesn't
    > mean to say that we can't use 'views' or some other mechanism to hide
    > some records from being resolvable from the outside.

The issue is that actually, you want some nodes to be able to resolve many
records even when they are "outside".

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxXVe4qHRg3pndX9AQKTCAP+PuYcOSEPkfHHb+daouSEUX2bdWCQ2XhU
8/zx19layd3Z1Zm9EcA/LvArHVkZROSWgIooSD56mQ88C5uMLhi1rhJT8N7hbmYZ
tMTK5Hug/Ep0/MtYnmPUSYysPSRrMeSmEuYba08gM1qvWNbEXAQqXFexEPNZX4EA
Ez9hoEEkcvQ=
=qljK
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 05:52:04 2014
Return-Path: <mellon@fugue.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 3DF051A0176 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 05:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.448
X-Spam-Level: 
X-Spam-Status: No, score=-4.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.547, 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 BtBDpCDd2dGg for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 05:51:58 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 351741A0161 for <homenet@ietf.org>; Tue,  4 Mar 2014 05:51:58 -0800 (PST)
Received: from [IPv6:2001:67c:370:176:9b:2e31:3f43:d3e8] (unknown [IPv6:2001:67c:370:176:9b:2e31:3f43:d3e8]) by toccata.fugue.com (Postfix) with ESMTPSA id 3633923808C7; Tue,  4 Mar 2014 08:51:53 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <334.1393929562@sandelman.ca>
Date: Tue, 4 Mar 2014 13:51:51 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/OzOEzZFBoM2zA2cF-gEn8d3e6cc
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 13:52:01 -0000

On Mar 4, 2014, at 10:39 AM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>   For a forward zone that I owned, I would push a new DS record =
upwards.
>   The likely reason for a new CPE is that the blue smoke got out of =
the old
>   one.  If the models were compatible, and I had a backup of the =
config,
>   then perhaps the private key would move, but that seems doubtful for =
most
>   users.

How are you going to push DS records upwards if you have lost your key?

> 3) the perpass/National-Security-Letter situation.
>   If the key by default resides at the ISP, then it is the ISP that =
gets
>   served when some agency thinks it wants to divert traffic by =
changing DNS,
>   and once served, the net may may be much larger than desired.
>   By putting the key in the CPE, the legal papers will have to specify =
that
>   device.  It may still be the ISP legal department that responds, but =
the
>   chance of screwing up is larger.

This is probably the best argument I've heard against putting the keys =
on the ISP's server.   However, you still have to make it work.


From nobody Tue Mar  4 06:02:37 2014
Return-Path: <marka@isc.org>
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 DA0311A019A for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.448
X-Spam-Level: 
X-Spam-Status: No, score=-4.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.547, 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 OMqGwvU6LTGq for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:02:32 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id C55F41A014F for <homenet@ietf.org>; Tue,  4 Mar 2014 06:02:32 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 7985A2383C1; Tue,  4 Mar 2014 14:02:15 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E137B160058; Tue,  4 Mar 2014 14:03:10 +0000 (UTC)
Received: from rock.dv.isc.org (dhcp-b59a.meeting.ietf.org [31.133.181.154]) by zmx1.isc.org (Postfix) with ESMTPSA id BBA1916004E; Tue,  4 Mar 2014 14:03:10 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id B96F010AF870; Wed,  5 Mar 2014 01:02:13 +1100 (EST)
To: Ted Lemon <mellon@fugue.com>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>
In-reply-to: Your message of "Tue, 04 Mar 2014 13:51:51 -0000." <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>
Date: Wed, 05 Mar 2014 01:02:13 +1100
Message-Id: <20140304140213.B96F010AF870@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/r7_H08N6DfqauzZhRLbtJiCHkX0
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 14:02:35 -0000

In message <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>, Ted Lemon writes:
> On Mar 4, 2014, at 10:39 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote
> :
> >   For a forward zone that I owned, I would push a new DS record upwards.
> >   The likely reason for a new CPE is that the blue smoke got out of the old
> >   one.  If the models were compatible, and I had a backup of the config,
> >   then perhaps the private key would move, but that seems doubtful for most
> >   users.
> 
> How are you going to push DS records upwards if you have lost your key?

If you have example.com then you are not zero conf and you add you tsig
key to the cpe.

If you are using a ISP assigned name then you re-establish credentials
as part of the DHCP exchange with the ISP.

Updating DS does not and should not require working DNSSEC to do however
this is a arguement for Friday and DNSOP.

> > 3) the perpass/National-Security-Letter situation.
> >   If the key by default resides at the ISP, then it is the ISP that gets
> >   served when some agency thinks it wants to divert traffic by changing DNS
> ,
> >   and once served, the net may may be much larger than desired.
> >   By putting the key in the CPE, the legal papers will have to specify that
> >   device.  It may still be the ISP legal department that responds, but the
> >   chance of screwing up is larger.
> 
> This is probably the best argument I've heard against putting the keys on the
>  ISP's server.   However, you still have to make it work.
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Mar  4 06:22:15 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 4469E1A019E for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=no
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 RuMwqJwC1jXU for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:22:07 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id BF3E11A00C3 for <homenet@ietf.org>; Tue,  4 Mar 2014 06:22:06 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id s24EM2SJ020151 for <homenet@ietf.org>; Tue, 4 Mar 2014 15:22:02 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id BB56D709F3 for <homenet@ietf.org>; Tue,  4 Mar 2014 15:22:02 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id HCVn-y575jgA for <homenet@ietf.org>; Tue,  4 Mar 2014 15:22:01 +0100 (CET)
Received: from ijon.pps.jussieu.fr (dhcp-a24c.meeting.ietf.org [31.133.162.76]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 3950E709F0 for <homenet@ietf.org>; Tue,  4 Mar 2014 15:22:01 +0100 (CET)
Date: Tue, 04 Mar 2014 14:22:00 +0000
Message-ID: <87fvmyujqv.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: homenet@ietf.org
References: <3FAA507C-0A6B-4D1E-AFF1-E084A9B698F1@pps.univ-paris-diderot.fr>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: message/rfc822
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 04 Mar 2014 15:22:02 +0100 (CET)
X-Miltered: at korolev with ID 5315E18A.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5315E18A.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5315E18A.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/SEH6mLbYj9HRtJG2avSwNzLRBhM
Subject: [homenet] Fwd: [Babel-users] Source-sensitive routing paper
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: Tue, 04 Mar 2014 14:22:09 -0000

Delivered-To: <jch@pps.univ-paris-diderot.fr>
From: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
Date: Tue, 4 Mar 2014 15:08:12 +0100
Message-Id: <3FAA507C-0A6B-4D1E-AFF1-E084A9B698F1@pps.univ-paris-diderot.fr>
To: "babel-users@lists.alioth.debian.org Users"
 <babel-users@lists.alioth.debian.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-policyd-weight: using cached result; rate: -6.1
Subject: [Babel-users] Source-sensitive routing paper
X-BeenThere: babel-users@lists.alioth.debian.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion related to the Babel Routing Daemon
 <babel-users.lists.alioth.debian.org>
List-Unsubscribe: <http://lists.alioth.debian.org/cgi-bin/mailman/options/babel-users>, 
 <mailto:babel-users-request@lists.alioth.debian.org?subject=unsubscribe>
List-Archive: <http://lists.alioth.debian.org/pipermail/babel-users/>
List-Post: <mailto:babel-users@lists.alioth.debian.org>
List-Help: <mailto:babel-users-request@lists.alioth.debian.org?subject=help>
List-Subscribe: <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users>, 
 <mailto:babel-users-request@lists.alioth.debian.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: babel-users-bounces+jch=pps.univ-paris-diderot.fr@lists.alioth.debian.org
Sender: "Babel-users"
 <babel-users-bounces+jch=pps.univ-paris-diderot.fr@lists.alioth.debian.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: babel-users-bounces+jch=pps.univ-paris-diderot.fr@lists.alioth.debian.org
X-SA-Exim-Scanned: No (on moszumanska.debian.org); SAEximRunCond expanded to false

Hi,

We wrote a conference paper on source-sensitive routing, which you will found there:

  http://hal-univ-diderot.archives-ouvertes.fr/hal-00947234
  http://fr.arxiv.org/abs/1403.0445

Matthieu


_______________________________________________
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


From nobody Tue Mar  4 06:56:53 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 E5CAE1A00B9 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 ORkAl5S9NSg4 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 06:56:47 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id 90F4C1A0179 for <homenet@ietf.org>; Tue,  4 Mar 2014 06:56:47 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id s24Eug9x009264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <homenet@ietf.org>; Tue, 4 Mar 2014 15:56:43 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id s24EugjM010371 for <homenet@ietf.org>; Tue, 4 Mar 2014 15:56:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id ACBFD709FD for <homenet@ietf.org>; Tue,  4 Mar 2014 15:56:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id iZnS9iC0ArU7 for <homenet@ietf.org>; Tue,  4 Mar 2014 15:56:41 +0100 (CET)
Received: from ijon.pps.jussieu.fr (dhcp-a24c.meeting.ietf.org [31.133.162.76]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8A12D709FB for <homenet@ietf.org>; Tue,  4 Mar 2014 15:56:41 +0100 (CET)
Date: Tue, 04 Mar 2014 14:56:40 +0000
Message-ID: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: homenet@ietf.org
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 04 Mar 2014 15:56:43 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 04 Mar 2014 15:56:42 +0100 (CET)
X-Miltered: at korolev with ID 5315E9AA.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5315E9AA.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5315E9AA.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5315E9AA.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5315E9AA.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5315E9AA.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/jljQikAfzz2lujC8HTTdAUoHmMs
Subject: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 14:56:49 -0000

Hi,

During this morning's session, I mentioned how much I like the HCNP
protocol, and that I'm looking into abandoning AHCP for a hacked-up
HCNP.  I made the following points this morning:

0. As far as I'm concerned, this is not "The Homenet Configuration
Protocol", this is a configuration protocol for unmanaged routers that
happens to have been designed by the Homenet group.  Please keep this
in mind when you read the following.

1. The draft seems overspecified at times.  Do we really mandate
Trickle, or do we want just an abstract description of flooding
requirements?  (Knowledgeable people commented that Trickle is fine.)

2. Related to the previous point, is everything MUST, or should some
parts be made optional?  I'd personally like the DNS proxy stuff to be
made optional.

3. There would appear to be no way to specify "please carve this
prefix into /64 or shorter" as opposed to "please feel free to grab
a /128 in this prefix".

4. Do we want the ability to mark an option as mandatory, as in
"Please don't configure unless you understand the following TLV, and
intend to act upon it".  One the one hand, this makes is easier to
design compatible extensions to the protocol (by sending two
configuration blocks, one with a mandatory incompatible option, one
without the option, and having old routers ignore the block with the
incompatible option).  On the other hand, it adds another failure mode.

5. I don't think the routing protocol should be negotiated by the
config protocol, since that implies that the routing daemon is started
by the config daemon.  The routing daemon(s) should be started at
boot, and notice when the config daemon adds IP addresses to
interfaces.  Knowledgeable people appeared to disagree.

(It seems to me that the config protocol should be routing-protocol
agnostic, and merely say "this protocol assumes that a routing
protocol satisfying the following conditions is available".  Homenet
should specify what the protocol is, and mandate implementation of The
One Homenet Routing Protocol (OHRP).)

I'd like RIP to be the OHRP, but I don't have strong opinions on the
subject.

I also don't care whether Homenet says that routers MUST implement
OHRP, or whether they MUST implement OHRP and MAY implement other
routing protocols.  In either case,

  - commercial Homenet router vendors will implement the OHRP and
    ignore the MAY protocols;
  - the OpenWRT routing overlay will probably install the OHRP by
    default, but provide its usual set of optional routing daemons.

In short, there will be no difference in practice whether Homenet
allows non-Homenet routing protocols or not.

-- Juliusz


From nobody Tue Mar  4 07:35:55 2014
Return-Path: <markus.stenberg@iki.fi>
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 673641A0085 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 0mdGPkLkBkdV for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:35:43 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out.inet.fi [195.156.147.13]) by ietfa.amsl.com (Postfix) with ESMTP id 52E7D1A0117 for <homenet@ietf.org>; Tue,  4 Mar 2014 07:35:43 -0800 (PST)
Received: from [192.168.43.129] (80.220.67.193) by kirsi1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 529734CF0804BE2A; Tue, 4 Mar 2014 17:35:36 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr>
Date: Tue, 4 Mar 2014 15:35:34 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/hNNJdXZuKUNpGz36zaxdCnMaFxY
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 15:35:50 -0000

On 4.3.2014, at 14.56, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> During this morning's session, I mentioned how much I like the HCNP
> protocol, and that I'm looking into abandoning AHCP for a hacked-up
> HCNP.  I made the following points this morning:
>=20
> 0. As far as I'm concerned, this is not "The Homenet Configuration
> Protocol", this is a configuration protocol for unmanaged routers that
> happens to have been designed by the Homenet group.  Please keep this
> in mind when you read the following.
>=20
> 1. The draft seems overspecified at times.  Do we really mandate
> Trickle, or do we want just an abstract description of flooding
> requirements?  (Knowledgeable people commented that Trickle is fine.)

Problem with abstract requirements is that it=92s easy to get them =
wrong. For example, =91up to once per minute =3D~ once a minute?=92 in =
hands of a creative reader. =91Use Trickle with these constants=92 is a =
short form for describing exponential backoff system which suppresses =
duplicate multicast messages from my point of view.

I=92m soliciting input on how this could be better, though (in a way =
which is unlikely to be broken by lowest common denominator =
implementor). As always, pull requests welcome ;)

> 2. Related to the previous point, is everything MUST, or should some
> parts be made optional?  I'd personally like the DNS proxy stuff to be
> made optional.

Agreed. It started as a separate draft and MUST in separate draft was =
sensible but now, well.. I=92m wondering even about PA stuff, because if =
you want to use different algorithm, it should be ok as long as you =
publish your delegated/assigned things in a compatible way.

> 3. There would appear to be no way to specify "please carve this
> prefix into /64 or shorter" as opposed to "please feel free to grab
> a /128 in this prefix=94.

Hmmh. Do you think it=92s issue in the hncp-00 or prefix-assignment one? =
I=92m not exactly sure I want =91purpose=92 bits for delegated prefixes. =
(see above also on mandatoriness of prefix-assignment _draft_)

> 4. Do we want the ability to mark an option as mandatory, as in
> "Please don't configure unless you understand the following TLV, and
> intend to act upon it".  One the one hand, this makes is easier to
> design compatible extensions to the protocol (by sending two
> configuration blocks, one with a mandatory incompatible option, one
> without the option, and having old routers ignore the block with the
> incompatible option).  On the other hand, it adds another failure =
mode.

I=92m slightly concerned about that - from my point of view, ideal way =
to extend is to ignore unknown TLVs, and then embed all information that =
requires understanding the TLV _within_ that TLV in some way.=20

> 5. I don't think the routing protocol should be negotiated by the
> config protocol, since that implies that the routing daemon is started
> by the config daemon.  The routing daemon(s) should be started at
> boot, and notice when the config daemon adds IP addresses to
> interfaces.  Knowledgeable people appeared to disagree.

There seems to be various assumptions around. I think I have heard =
fairly good arguments towards different solutions (turning routing =
protocol on or off based on configuration, =91always routing if possible =
using real protocol=92 (possibly one of many)). I am not yet convinced =
the either way.

> (It seems to me that the config protocol should be routing-protocol
> agnostic, and merely say "this protocol assumes that a routing
> protocol satisfying the following conditions is available".  Homenet
> should specify what the protocol is, and mandate implementation of The
> One Homenet Routing Protocol (OHRP).)

=46rom specification and dependency point of view, HNCP which assumes =
OHRP would work, _given_ we can assume everyone implements OHRP. If not, =
we wind up in the rathole of 0-1 routing protocols and the effects which =
trigger even that single OHRP on and off.. sigh.

> I'd like RIP to be the OHRP, but I don't have strong opinions on the
> subject.

On general level, I=92m =91RIP.. really?=92 (does someone have an =
open-source RIP implementation which _does_ fullfill the requirements? =
And no, it doesn=92t count if you patch existing one ;->). And yes, I =
know it happens in routers a lot, and I also know the implementation =
changes aren=92t probably significant but still.

> I also don't care whether Homenet says that routers MUST implement
> OHRP, or whether they MUST implement OHRP and MAY implement other
> routing protocols.  In either case,
>=20
>  - commercial Homenet router vendors will implement the OHRP and
>    ignore the MAY protocols;
>  - the OpenWRT routing overlay will probably install the OHRP by
>    default, but provide its usual set of optional routing daemons.
>=20
> In short, there will be no difference in practice whether Homenet
> allows non-Homenet routing protocols or not.

I have thought about this for a while now (and the discussions in IETF =
have been helpful too). I really wonder how needs of everyone can be =
taken care of (notably, the crowd that wants 0 routing protocols).

My preliminary thought is as follows, repurposing the fallback routing - =
let me know if this sounds bad:

Add a no-routing-TLV (zero content) which means that routes towards this =
node have to be done without routing protocol (by other HNCP nodes that =
support real routing protocol). The no-routing node can also do routes =
towards other nodes similarly. (This has underlying assumption that HNCP =
TLV space covers all prefixes we care about, which is probably =
sufficient for packets to flow although possibly suboptimally.)

In this approach, there would be _no_ indication about routing protocol =
being used, and just an assumption that administrative domain has chosen =
one; for homenet case, it would be OHRP except for nodes which opt out =
of OHRP altogether and raise the no-routing flag.=20

Admin or someone else who sets up a set of routers with different =
purpose on the other hand could configure (one or more) non-OHRP routing =
protocols and HNCP itself would be usable in that case too (and no =
magic, and no strong binding between configuration and routing).

(General zero routing protocols case is even simpler, but I am not very =
happy with OHRP =3D current hncp-routing idea.)

Now that I think more of this, giving an opt-out of routing would (by =
Juliusz=92s logic) most likely lead to most simple implementations not =
doing OHRP at all in any case. Hmm. So fundamentally the choices boil =
down to (as far as I see them):

[1] 0/1-N routing protocols (OHRP in case of homenet, or something else =
elsewhere) per router (as long as the administrative =
distances/priorities work out ok)
[2] 1 routing protocol, period (OHRP in case of homenet) per =
administrative domain, on _every router_
[3] 0 real routing protocols (fallback-only)

Personally, [3] would make me a sad panda. [2] sounds nice, but I wonder =
if the crowd that is speciffying future SPERs etc are happy about =
adopting OHRP all over the place (and if not, there is a failure mode =
there right away). [1] is described above and is probably =91political =
layer proof=92 but not pretty due to the extra TLV shenaginans I =
describe above.

Cheers,

-Markus=


From nobody Tue Mar  4 07:39:46 2014
Return-Path: <mcr@sandelman.ca>
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 EE4001A0085 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 m51beD2xKNfu for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:39:42 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 8C3A91A005E for <homenet@ietf.org>; Tue,  4 Mar 2014 07:39:42 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id C382B20050; Tue,  4 Mar 2014 11:58:09 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 351EA647C9; Tue,  4 Mar 2014 10:39:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1EC98647C8; Tue,  4 Mar 2014 10:39:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 10:39:38 -0500
Message-ID: <31285.1393947578@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/TXC0J4wdj_iRTy-hW0QTagX9kY4
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 15:39:44 -0000

--=-=-=


Ted Lemon <mellon@fugue.com> wrote:
    >> For a forward zone that I owned, I would push a new DS record upwards.
    >> The likely reason for a new CPE is that the blue smoke got out of the
    >> old one.  If the models were compatible, and I had a backup of the
    >> config, then perhaps the private key would move, but that seems
    >> doubtful for most users.

    > How are you going to push DS records upwards if you have lost your key?

Same way that I got my zone bootstrapped when I first bought it.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxXzuYqHRg3pndX9AQKB0QP9HKC2neVnNgqrTkkVKMKecmnT2qwMBvML
onIeMLttcc/H+jBe2mLeKLuyuc2fy+ZYBQ232a6tI03lmeKoeXgCVSLgLgeO2cOx
lyvd46EiBVsX0gsYwCLbFuIxJNEM+iuHN2kEcZqIhQ/XxXe8H+JIVat8NeXMHoys
VCo8hCQjITA=
=U5kW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 07:44:59 2014
Return-Path: <mellon@fugue.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 5B1451A00F5 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 tPs_6DV4lkum for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:44:47 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id EACAC1A01C6 for <homenet@ietf.org>; Tue,  4 Mar 2014 07:44:35 -0800 (PST)
Received: from nat64.meeting.ietf.org (unknown [IPv6:2001:67c:1231:998:290e:83f9:d755:ccec]) by toccata.fugue.com (Postfix) with ESMTPSA id DF2F223808C7; Tue,  4 Mar 2014 10:44:31 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <31285.1393947578@sandelman.ca>
Date: Tue, 4 Mar 2014 15:44:29 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/8tVudS_qFvOoTD6SCALjiZLZiZE
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 15:44:49 -0000

On Mar 4, 2014, at 3:39 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> Same way that I got my zone bootstrapped when I first bought it.

When you bootstrapped it, you didn't already have a key established.   =
Now you do.   Is the ISP supposed to just trust you when you re-key your =
zone?  This seems like a nice attack surface.


From nobody Tue Mar  4 07:53:10 2014
Return-Path: <v6ops@globis.net>
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 847CB1A0179 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 Uq8lIuWnoPee for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 07:53:05 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 17FD51A022B for <homenet@ietf.org>; Tue,  4 Mar 2014 07:53:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id CB8DB870F8A; Tue,  4 Mar 2014 16:52:54 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G4P8eBDdiaaC; Tue,  4 Mar 2014 16:52:54 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id A2CEF870F89; Tue,  4 Mar 2014 16:52:54 +0100 (CET)
Message-ID: <5315F6D6.60508@globis.net>
Date: Tue, 04 Mar 2014 16:52:54 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <5315C6DF.4030608@globis.net> <4153.1393939835@sandelman.ca>
In-Reply-To: <4153.1393939835@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/xNY0q6WBuRj78C6zJwuN9wsXO_4
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 15:53:06 -0000

> Michael Richardson <mailto:mcr+ietf@sandelman.ca>
> 4 March 2014 14:30
> Ray Hunter <v6ops@globis.net> wrote:
> >> On Tue, Mar 04, 2014 at 10:08:53AM +0000, Ralf Weber wrote:
> >>
> >>> or on the ISP auth name server). I have no problem with signing on
> >>> the CPE. I just don't want to make it mandatory
> >>
> >> For the purposes of this discussion, I'm going to assume that one has
> >> an inward-facing zone and and outward-facing one (i.e. this is a
> >> split-brain DNS situation).
>
> > I think even large corporations are slowly learning that split-brain
> > DNS is a bad idea that seemed like a good idea at the time, especially
> > in the presence of highly-mobile devices, and forwarders.
>
> > I'm becoming a convert myself to that way of thinking. That doesn't
> > mean to say that we can't use 'views' or some other mechanism to hide
> > some records from being resolvable from the outside.
>
> The issue is that actually, you want some nodes to be able to resolve many
> records even when they are "outside".
>
Agreed. Cloud computing being a prime disruptor to the split brain model.
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting for hire =-
>
>


-- 
Regards,
RayH


From nobody Tue Mar  4 08:59:17 2014
Return-Path: <mcr@sandelman.ca>
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 704391A01A8 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 08:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 iWRSns7mT9uw for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 08:59:13 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 699721A00F5 for <homenet@ietf.org>; Tue,  4 Mar 2014 08:59:13 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5B91320094; Tue,  4 Mar 2014 13:17:41 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 21596647C9; Tue,  4 Mar 2014 11:59:10 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0E3C763B88; Tue,  4 Mar 2014 11:59:10 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 11:59:10 -0500
Message-ID: <15768.1393952350@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/DbFiHbR7iXwXriuFjAWZyox3qy4
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 16:59:15 -0000

--=-=-=


Ted Lemon <mellon@fugue.com> wrote:
    >> Same way that I got my zone bootstrapped when I first bought it.

    > When you bootstrapped it, you didn't already have a key established.
    > Now you do.  Is the ISP supposed to just trust you when you re-key your
    > zone?  This seems like a nice attack surface.

As Mark said, if it's an ISP provided zone, then pushing the new DS is done
under the TSIG key that the DHCP established. (So, ted-lemon-house.isp.example.net,
and the reverse map).

If it's fugue.com, then you have to go to your registrar and change DS.
This is largely akin to what you'd do if your key was compromised.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxYGXYqHRg3pndX9AQIzXQP/WgErNLaNuByE5F5Snmj6t8naFVvt2Jzv
a8Sm4jinthS+asqzC9f7e4b+Gk/KF0+abz5cehyTRZ/zp9sQK1c9wch05YIrtdt1
y1Rv6uOy9Zqbr8yjFGHnKu9hFrecdYCtY1byPw1OTRUq5YzA+ALH0Fy7aD6zLssi
Rk4P3ZuQYBE=
=G6uW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 09:06:12 2014
Return-Path: <mellon@fugue.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 90C271A024A for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 09:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 c7wcF7UBsguH for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 09:06:07 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1732A1A01F1 for <homenet@ietf.org>; Tue,  4 Mar 2014 09:06:07 -0800 (PST)
Received: from dhcp-a664.meeting.ietf.org (dhcp-a664.meeting.ietf.org [31.133.166.100]) by toccata.fugue.com (Postfix) with ESMTPSA id 0268023808C7; Tue,  4 Mar 2014 12:06:02 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <15768.1393952350@sandelman.ca>
Date: Tue, 4 Mar 2014 17:05:59 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com> <15768.1393952350@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/yNQd3SO5Pxv1tZLS6NBnnnCzRUM
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 17:06:09 -0000

On Mar 4, 2014, at 4:59 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> As Mark said, if it's an ISP provided zone, then pushing the new DS is =
done
> under the TSIG key that the DHCP established. (So, =
ted-lemon-house.isp.example.net,
> and the reverse map).

Oh, so the TSIG key sent in the clear over DHCP is the attack surface.   =
Got it.   Actually during the DHC working group presentation, we asked =
Daniel to take the TSIG key out because it's not secure.   The right way =
to do it is with SIG(0).   But that doesn't provide a way to repudiate a =
lost key, because it relies on a leap of faith to begin trusting the =
initial key.

If the connection between the DHCP server and DHCP client is secure, =
then a nonce sent over DHCP could be used along with SIG(0) to assist, =
but this is not the only potential configuration.   Trusting the wire =
works pretty well in these scenarios in practice, but only if there _is_ =
a wire.


From nobody Tue Mar  4 09:59:00 2014
Return-Path: <marka@isc.org>
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 6F3A41A0262 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 09:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 M5uPnbI9AIA5 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 09:58:39 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id A4BC81A02A2 for <homenet@ietf.org>; Tue,  4 Mar 2014 09:58:35 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id EF18D23840F; Tue,  4 Mar 2014 17:58:18 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7920F160058; Tue,  4 Mar 2014 17:59:14 +0000 (UTC)
Received: from rock.dv.isc.org (unknown [149.20.66.86]) by zmx1.isc.org (Postfix) with ESMTPSA id D389B16004E; Tue,  4 Mar 2014 17:59:13 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 52F4010AFDCE; Wed,  5 Mar 2014 04:58:12 +1100 (EST)
To: Ted Lemon <mellon@fugue.com>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com> <15768.1393952350@sandelman.ca> <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>
In-reply-to: Your message of "Tue, 04 Mar 2014 17:05:59 -0000." <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>
Date: Wed, 05 Mar 2014 04:58:12 +1100
Message-Id: <20140304175812.52F4010AFDCE@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/6_jShGRyjWw0pYNALYyUk6LfUak
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 17:58:41 -0000

In message <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>, Ted Lemon writes:
> On Mar 4, 2014, at 4:59 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> > As Mark said, if it's an ISP provided zone, then pushing the new DS is done
> > under the TSIG key that the DHCP established. (So, ted-lemon-house.isp.exam
> ple.net,
> > and the reverse map).
> 
> Oh, so the TSIG key sent in the clear over DHCP is the attack surface.   Got 
> it.   Actually during the DHC working group presentation, we asked Daniel to 
> take the TSIG key out because it's not secure.   The right way to do it is wi
> th SIG(0).   But that doesn't provide a way to repudiate a lost key, because 
> it relies on a leap of faith to begin trusting the initial key.
> 
> If the connection between the DHCP server and DHCP client is secure, then a n
> once sent over DHCP could be used along with SIG(0) to assist, but this is no
> t the only potential configuration.   Trusting the wire works pretty well in 
> these scenarios in practice, but only if there _is_ a wire.

Please go read draft-andrews-dnsop-pd-reverse.  This technique will
work with any zone to be delegated by the ISP.  For most cases the
wire is the authenticator by for things like WiMax you will be
putting credentials into the box to authenticticate your DHCP request
to the ISP as the medium is not secure anyway.

> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Mar  4 10:07:13 2014
Return-Path: <cyrus@openwrt.org>
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 8D11B1A02BA for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311] autolearn=no
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 zMKvYLhNQAds for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:07:04 -0800 (PST)
Received: from chi.subsignal.org (cxd-2-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:ed::2]) by ietfa.amsl.com (Postfix) with ESMTP id 26D7E1A02E8 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:06:35 -0800 (PST)
Received: from [172.16.0.36] (host217-45-232-169.in-addr.btopenworld.com [217.45.232.169]) by chi.subsignal.org (Postfix) with ESMTPSA id 151B0126102; Tue,  4 Mar 2014 19:08:24 +0100 (CET)
Message-ID: <53161623.6080700@openwrt.org>
Date: Tue, 04 Mar 2014 19:06:27 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Markus Stenberg <markus.stenberg@iki.fi>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi>
In-Reply-To: <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Ve8-Dp1CtV69nqBnPaWY0AX73t4
Cc: homenet@ietf.org
Subject: Re: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 18:07:08 -0000

> On 4.3.2014, at 14.56, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>> During this morning's session, I mentioned how much I like the HCNP
>> protocol, and that I'm looking into abandoning AHCP for a hacked-up
>> HCNP.  I made the following points this morning:
>>
>> 0. As far as I'm concerned, this is not "The Homenet Configuration
>> Protocol", this is a configuration protocol for unmanaged routers that
>> happens to have been designed by the Homenet group.  Please keep this
>> in mind when you read the following.
The thing is how much do we want to speculate to make it suitable for
other unknown usecases. I don't really want to overengineer it based
upon unknown requirements.


>
>> 2. Related to the previous point, is everything MUST, or should some
>> parts be made optional?  I'd personally like the DNS proxy stuff to be
>> made optional.
> Agreed. It started as a separate draft and MUST in separate draft was sensible but now, well.. I’m wondering even about PA stuff, because if you want to use different algorithm, it should be ok as long as you publish your delegated/assigned things in a compatible way.
I suppose we want to differentiate between transport and payload here.
I'm not sure if splitting it up into individual drafts might make sense
but definitely - as I also pointed out in the presentation - it wasn't
meant to be interpreted in a way that any of the non-protocol related
TLVs are mandatory. Though in practice there are some inter-dependencies
between payloads atm, e.g. both the fallback-routing and the DNS/SD
stuff somewhat reuses prefixes and / or address-information announced by
the PA-mechanism.

>
>> 3. There would appear to be no way to specify "please carve this
>> prefix into /64 or shorter" as opposed to "please feel free to grab
>> a /128 in this prefix”.
> Hmmh. Do you think it’s issue in the hncp-00 or prefix-assignment one? I’m not exactly sure I want ‘purpose’ bits for delegated prefixes. (see above also on mandatoriness of prefix-assignment _draft_)
I don't know if we really consider a /128-assignment to be a prefix in
that sense. I would see this as a special case to aid in meshing and
similar so I think maybe adding a special kind of _assigned_ prefix type
of some sort might make sense for this from which every (supporting)
router should be able to pick a /128 regardless of the link.


>
>> 4. Do we want the ability to mark an option as mandatory, as in
>> "Please don't configure unless you understand the following TLV, and
>> intend to act upon it".  One the one hand, this makes is easier to
>> design compatible extensions to the protocol (by sending two
>> configuration blocks, one with a mandatory incompatible option, one
>> without the option, and having old routers ignore the block with the
>> incompatible option).  On the other hand, it adds another failure mode.
> I’m slightly concerned about that - from my point of view, ideal way to extend is to ignore unknown TLVs, and then embed all information that requires understanding the TLV _within_ that TLV in some way.
I'm not sure if that makes sense either. HNCP is a pretty agnostic
protocol and -please prove me wrong- I can only really see a point for
this for extensions to the actual transport or security logic. This also
refers to the discussion if we want mandatory payloads.

>
>> 5. I don't think the routing protocol should be negotiated by the
>> config protocol, since that implies that the routing daemon is started
>> by the config daemon.  The routing daemon(s) should be started at
>> boot, and notice when the config daemon adds IP addresses to
>> interfaces.  Knowledgeable people appeared to disagree.
I would disagree here. I don't see the point in starting the daemons for
homenet-interfaces here if they have to wait for HNCP to assign prefixes
/ addresses anyway.
> My preliminary thought is as follows, repurposing the fallback routing - let me know if this sounds bad:
>
> Add a no-routing-TLV (zero content) which means that routes towards this node have to be done without routing protocol (by other HNCP nodes that support real routing protocol). The no-routing node can also do routes towards other nodes similarly. (This has underlying assumption that HNCP TLV space covers all prefixes we care about, which is probably sufficient for packets to flow although possibly suboptimally.)
I wouldn't really do it like that. Even though I agree with the 0-1 or 1
routing protocol agenda I wouldn't really do negative capability
announcements. If for some reason you want to make changes or use HNCP
for other purposes later this will get ugly.


From nobody Tue Mar  4 10:08:40 2014
Return-Path: <mellon@fugue.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 EDCF41A02DB for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 MOLwuu4B3_Pc for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:08:30 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 95F3C1A02CB for <homenet@ietf.org>; Tue,  4 Mar 2014 10:08:30 -0800 (PST)
Received: from nat64.meeting.ietf.org (unknown [IPv6:2001:67c:1231:998:6c5b:6f71:2778:aa89]) by toccata.fugue.com (Postfix) with ESMTPSA id 62F9F23808C7; Tue,  4 Mar 2014 13:08:26 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <20140304175812.52F4010AFDCE@rock.dv.isc.org>
Date: Tue, 4 Mar 2014 18:08:22 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CCAECEA-0D86-49A3-A314-3A0E0528159C@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com> <15768.1393952350@sandelman.ca> <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com> <20140304175812.52F4010AFDCE@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/tCxafOds4qRPY7WFi3FcxSF1SjM
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 18:08:33 -0000

On Mar 4, 2014, at 5:58 PM, Mark Andrews <marka@isc.org> wrote:
> Please go read draft-andrews-dnsop-pd-reverse.  This technique will
> work with any zone to be delegated by the ISP.  For most cases the
> wire is the authenticator by for things like WiMax you will be
> putting credentials into the box to authenticticate your DHCP request
> to the ISP as the medium is not secure anyway.

Your draft is certainly a valid solution to the problem it sets out to =
solve, but it doesn't actually change the security model I was talking =
about.   Given that my point was that you have to trust the wire to make =
this work, I think are in violent agreement at least on this point, =
except that I would like us to describe a solution that at least =
addresses the use case where you can't trust the wire.


From nobody Tue Mar  4 10:18:09 2014
Return-Path: <marka@isc.org>
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 AECC41A025F for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:18:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 T6ysQRgVJrol for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:18:04 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 00E6C1A01FD for <homenet@ietf.org>; Tue,  4 Mar 2014 10:18:03 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 8F1AB23840F; Tue,  4 Mar 2014 18:17:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1D2DD160058; Tue,  4 Mar 2014 18:18:44 +0000 (UTC)
Received: from rock.dv.isc.org (unknown [149.20.66.86]) by zmx1.isc.org (Postfix) with ESMTPSA id 8B55D16004E; Tue,  4 Mar 2014 18:18:43 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E325010B06C2; Wed,  5 Mar 2014 05:17:42 +1100 (EST)
To: Ted Lemon <mellon@fugue.com>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com> <15768.1393952350@sandelman.ca> <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com> <20140304175812.52F4010AFDCE@rock.dv.isc.org> <4CCAECEA-0D86-49A3-A314-3A0E0528159C@fugue.com>
In-reply-to: Your message of "Tue, 04 Mar 2014 18:08:22 -0000." <4CCAECEA-0D86-49A3-A314-3A0E0528159C@fugue.com>
Date: Wed, 05 Mar 2014 05:17:42 +1100
Message-Id: <20140304181742.E325010B06C2@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/XmJbpLZpGseGYmYSirA1He2yghs
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 18:18:06 -0000

In message <4CCAECEA-0D86-49A3-A314-3A0E0528159C@fugue.com>, Ted Lemon writes:
> On Mar 4, 2014, at 5:58 PM, Mark Andrews <marka@isc.org> wrote:
> > Please go read draft-andrews-dnsop-pd-reverse.  This technique will
> > work with any zone to be delegated by the ISP.  For most cases the
> > wire is the authenticator by for things like WiMax you will be
> > putting credentials into the box to authenticticate your DHCP request
> > to the ISP as the medium is not secure anyway.
> 
> Your draft is certainly a valid solution to the problem it sets out to =
> solve, but it doesn't actually change the security model I was talking =
> about.   Given that my point was that you have to trust the wire to make =
> this work, I think are in violent agreement at least on this point, =
> except that I would like us to describe a solution that at least =
> addresses the use case where you can't trust the wire.
 
A HMAC-* option for DHCP (c.f. TSIG) would work if we have to
authenticate a DHCP request without relying on any other layers.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Mar  4 10:31:31 2014
Return-Path: <markus.stenberg@iki.fi>
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 806B41A02A0 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 HJA7-yNBds_2 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:31:24 -0800 (PST)
Received: from jenni1.inet.fi (mta-out.inet.fi [195.156.147.13]) by ietfa.amsl.com (Postfix) with ESMTP id E04CA1A01F1 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:31:23 -0800 (PST)
Received: from [192.168.43.129] (80.220.67.193) by jenni1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 527750DA0A232222; Tue, 4 Mar 2014 20:31:12 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <53161623.6080700@openwrt.org>
Date: Tue, 4 Mar 2014 18:31:03 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6E7C06B-0741-4B9E-9F16-E1F009191BB1@iki.fi>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi> <53161623.6080700@openwrt.org>
To: Steven Barth <cyrus@openwrt.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/yUkUQATdFhHQGM3-_MuyY--JKP8
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 18:31:27 -0000

On 4.3.2014, at 18.06, Steven Barth <cyrus@openwrt.org> wrote:
>>> 2. Related to the previous point, is everything MUST, or should some
>>> parts be made optional?  I'd personally like the DNS proxy stuff to =
be
>>> made optional.
>> Agreed. It started as a separate draft and MUST in separate draft was =
sensible but now, well.. I=92m wondering even about PA stuff, because if =
you want to use different algorithm, it should be ok as long as you =
publish your delegated/assigned things in a compatible way.
> I suppose we want to differentiate between transport and payload here.
> I'm not sure if splitting it up into individual drafts might make =
sense
> but definitely - as I also pointed out in the presentation - it wasn't
> meant to be interpreted in a way that any of the non-protocol related
> TLVs are mandatory. Though in practice there are some =
inter-dependencies
> between payloads atm, e.g. both the fallback-routing and the DNS/SD
> stuff somewhat reuses prefixes and / or address-information announced =
by
> the PA-mechanism.

Splitting TLV-only content to separate drafts (especially now that they =
have little extra content) probably wouldn=92t help much. (Mostly =
because it would create bunch of very minimal drafts with at least =
strong dependencies on the generic drafts, and the core draft). I =
suppose the right way forward on that front is just to specify that =
extra feature sets are SHOULD/MAY-ish, and if implementing that feature =
set, relevant MUST/SHOULDs there.

>>> 3. There would appear to be no way to specify "please carve this
>>> prefix into /64 or shorter" as opposed to "please feel free to grab
>>> a /128 in this prefix=94.
>> Hmmh. Do you think it=92s issue in the hncp-00 or prefix-assignment =
one? I=92m not exactly sure I want =91purpose=92 bits for delegated =
prefixes. (see above also on mandatoriness of prefix-assignment _draft_)
> I don't know if we really consider a /128-assignment to be a prefix in
> that sense. I would see this as a special case to aid in meshing and
> similar so I think maybe adding a special kind of _assigned_ prefix =
type
> of some sort might make sense for this from which every (supporting)
> router should be able to pick a /128 regardless of the link.

We already have that assigned address TLV anyway, so given extra =
assigned prefix bit (we have 3 reserved ones), it could be probably =
fairly straightforward to do /128 allocations using this.

Logic along the lines of:=20

- if /128 allocations are desirable, allocate one assigned prefix with =
<whatever size> and bit X=3D1 (possibly even allow multiple ones in race =
cases?)
- and then just allocate stuff from there.

>>> 5. I don't think the routing protocol should be negotiated by the
>>> config protocol, since that implies that the routing daemon is =
started
>>> by the config daemon.  The routing daemon(s) should be started at
>>> boot, and notice when the config daemon adds IP addresses to
>>> interfaces.  Knowledgeable people appeared to disagree.
> I would disagree here. I don't see the point in starting the daemons =
for
> homenet-interfaces here if they have to wait for HNCP to assign =
prefixes
> / addresses anyway.

I suppose that if you were ambitious and wanted to run this non-root on =
non-suid binary system (e.g. Android) it would make sort of sense, =
because you=92d want to do things as root early in the boot time and =
then just configure existing services (with sufficient privileges to do =
what is needed).=20

> I wouldn't really do it like that. Even though I agree with the 0-1 or =
1
> routing protocol agenda I wouldn't really do negative capability
> announcements. If for some reason you want to make changes or use HNCP
> for other purposes later this will get ugly.

Hmmh, with 1 routing protocol agenda negative capability is not really =
needed in any case (in that one, you just assume routing happens and =
everyone lives happily ever after). So how do you think the 0-1 should =
be done?

- option a: negative capability indication, mixed network (what I wrote)

- option b: =91support protocol X/Y/Z=92 =3D> mixed network (with =
explicit support for fallback too(?), somehow know/avoid bad =
combinations?)

- option c: =91support protocol X/Y/Z=92 =3D>  0/1 routing protocol in =
whole home

If I were <random ISP customer>, and they sent me braindead router, I=92d =
be unhappy with option c as it would force 0 routing protocols in whole =
home. But that=92s where you=92d get with e.g. current hncp-00 text. =
Same thing with transitions between 0 and 1 routing protocols in a whole =
network, which I would rather avoid.

Cheers,

-Markus=


From nobody Tue Mar  4 10:33:30 2014
Return-Path: <mcr@sandelman.ca>
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 D6AB81A02CE for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 p4IqeeqFvFcd for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:33:27 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id F116F1A02EB for <homenet@ietf.org>; Tue,  4 Mar 2014 10:33:26 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 578B92006C; Tue,  4 Mar 2014 14:51:53 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C8E7D647C9; Tue,  4 Mar 2014 13:33:21 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B3ED063B88; Tue,  4 Mar 2014 13:33:21 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <334.1393929562@sandelman.ca> <8C733A95-E0D1-4863-BB9C-A25488AA5006@fugue.com> <31285.1393947578@sandelman.ca> <B0BCD812-ADA6-4674-B088-542AE82C34CC@fugue.com> <15768.1393952350@sandelman.ca> <F5BC424E-133E-41CC-B456-943F15462F82@fugue.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 04 Mar 2014 13:33:21 -0500
Message-ID: <3198.1393958001@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/eIIpgSSeJNEJSxoFGdl7vQD6kWU
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 18:33:29 -0000

--=-=-=


Ted Lemon <mellon@fugue.com> wrote:
    >> As Mark said, if it's an ISP provided zone, then pushing the new DS is
    >> done under the TSIG key that the DHCP established. (So,
    >> ted-lemon-house.isp.example.net, and the reverse map).

    > Oh, so the TSIG key sent in the clear over DHCP is the attack surface.

Yes, I agree, that is the attack surface!

Using SIG(0) with leap of faith is certainly a better thing, and I agree with
you that this then makes the "blue-smoke-got-out-of-CPE" problem more
difficult.   I think that I now forget what other situations we have that
caused us to replace the CPE.

1) The leap-of-faith could be reset by the ISP when they also send out the new
   router.

2) The new CPE might send a different DUID in DHCPv6, and this might cause the ISP
   to allocate a new prefix to you.  This clears the leap-of-faith for the
   reverse zone.
   (please forgive me if DUID was the wrong term. I think I'm right here)

3) if this was really PPPoE, then the "link", while still in the clear,
   was authenticated at "layer-2" from your PPPoE username/password, and
   maybe something could be leveraged there to reset "ted-lemon-house.isp.example.net".
   For the WiMax with authenticated ESSID, there may be a similar layer-2
   signal.  I agree that this likely doesn't work ("trusts wire") for the
   generic ethernet-like [cable/GPON/FTTH] cases.

    > Got it.  Actually during the DHC working group presentation, we asked
    > Daniel to take the TSIG key out because it's not secure.  The right way
    > to do it is with SIG(0).  But that doesn't provide a way to repudiate a
    > lost key, because it relies on a leap of faith to begin trusting the
    > initial key.

    > If the connection between the DHCP server and DHCP client is secure,
    > then a nonce sent over DHCP could be used along with SIG(0) to assist,
    > but this is not the only potential configuration.  Trusting the wire
    > works pretty well in these scenarios in practice, but only if there
    > _is_ a wire.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxYccYqHRg3pndX9AQJayQQAt5KSZ4rlDMt8/KfyShzuD2FNLwh4ZyJG
Gm5gKJeLNXFkO3B98y3/DKMbuJ7+/Vm6jQ+2vbEsPCAnfeaLINAxx7WfARm9m81m
xnijqJxA1VKZAyAEBme+3hH6fNxynQ/sHcfQ9Ih2+EyFO0iVJjCyJYgTQzC2gLQp
I3ADwOjHkZQ=
=8sGL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  4 10:50:25 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 4C4721A02D2 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 1M8QQMCb_isf for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 10:50:20 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id 189301A02B9 for <homenet@ietf.org>; Tue,  4 Mar 2014 10:50:19 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id s24IoGuL027570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Mar 2014 19:50:16 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id s24IoGiZ029273; Tue, 4 Mar 2014 19:50:16 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 22A5670A20; Tue,  4 Mar 2014 19:50:16 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id t3KNFDPmhMzc; Tue,  4 Mar 2014 19:50:14 +0100 (CET)
Received: from ijon.pps.jussieu.fr (unknown [82.33.220.194]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B486E70A16; Tue,  4 Mar 2014 19:50:14 +0100 (CET)
Date: Tue, 04 Mar 2014 18:50:14 +0000
Message-ID: <87ha7dlrx5.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <53161623.6080700@openwrt.org>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi> <53161623.6080700@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-2022-JP
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 04 Mar 2014 19:50:16 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 04 Mar 2014 19:50:16 +0100 (CET)
X-Miltered: at korolev with ID 53162068.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 53162068.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 53162068.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 53162068.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 53162068.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 53162068.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/7RLgcbPU2Uszo9EelGA4dzsupXc
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 18:50:23 -0000

>>> 0. As far as I'm concerned, this is not "The Homenet Configuration
>>> Protocol", this is a configuration protocol for unmanaged routers that
>>> happens to have been designed by the Homenet group.  Please keep this
>>> in mind when you read the following.

> The thing is how much do we want to speculate to make it suitable for
> other unknown usecases. I don't really want to overengineer it based
> upon unknown requirements.

Agreed.  I'm looking at it from the point of view of "when can I dump
AHCP", which might not be relevant for this working group.  On the
other hand, we've done a lot of experimenting with AHCP, so I would
claim that learning from the (few) relevant bits of AHCP wisdom might
be beneficial.

>>> 2. Related to the previous point, is everything MUST, or should some
>>> parts be made optional?  I'd personally like the DNS proxy stuff to be
>>> made optional.

> I suppose we want to differentiate between transport and payload here.

Yes.

> I'm not sure if splitting it up into individual drafts might make sense

My personal preference would be to keep it a single draft, and only split
it if we find out that one part is holding up the others (i.e. if we find
that the transport part is ready to go RFC, but payload still needs work).

>>> 3. There would appear to be no way to specify "please carve this
>>> prefix into /64 or shorter" as opposed to "please feel free to grab
>>> a /128 in this prefix$B!I(B.

> I would see this as a special case to aid in meshing

That's of course the intended application, but there are others.
VPNs, point-to-point links, management interfaces.

>>> 4. Do we want the ability to mark an option as mandatory,

>> I$B!G(Bm slightly concerned about that

> I'm not sure if that makes sense either.

Ok, point taken.

>>> 5. I don't think the routing protocol should be negotiated by the
>>> config protocol, since that implies that the routing daemon is started
>>> by the config daemon.

> I would disagree here. I don't see the point in starting the daemons for
> homenet-interfaces here if they have to wait for HNCP to assign prefixes
> / addresses anyway.

Let me try to explain where I'm coming from.  There are two arguments.

(1) IPv6 based routing protocols (including at least RIPng, OSPFv3 and
Babel) are able to route over unnumbered interfaces using link-local
addresses.  OSPFv3 and Babel start sending hellos as soon as there is
a link-local address on the interface, and establish adjacencies
straight away.  If the local addresses change, the adjacencies are not
torn down as long as the link-local address remains the same.

AHCP versions 0 and 0.5 (protocol version, not the version of the
software) used to negociate the routing protocol over AHCP.  The
result was that whenever the AHCP configuration changed, the routing
daemon was stopped, lost all adjacencies, including the Hello history.
In AHCP version 1 (protocol version), the routing protocol runs in
parallel to AHCP.  When AHCP changes configuration, the routing
protocol keeps running -- retains all adjacencies and link-quality
data.  Loss of connectivity is on the order of milliseconds.

Now AHCP is used in mesh networks, with often have poor connectivity.
Spurious AHCP expirations happen regularly (not often, just regularly).
Users like the fact that connectivity resumes as soon as they get back
into range -- and that's due to retaining the Hello history.

(2) With AHCP version 0/0.5, the OpenWRT and Debian init scripts used
to check if AHCP is installed before deciding to start Babel -- the
assumption was that AHCP would start Babel when it got configuration
information.  With AHCP version 1, Babel is started unconditionally.
The packagers like that -- it feels much less brittle.  And I like
happy packagers.

>> Add a no-routing-TLV (zero content) which means that routes towards
>> this node have to be done without routing protocol (by other HNCP
>> nodes that support real routing protocol).

Could you please spell out what problem you're trying to solve?  If
the problem is nodes with limited resources, then let's choose
a protocol that allows minimal implementations.  Snooping on RIPng or
Babel and installing a default route (using a hackish system("ip route add"))
can be done in two hundred lines of code or so.  (Yes, I'm volunteering.)

-- Juliusz


From nobody Tue Mar  4 12:37:08 2014
Return-Path: <internet-drafts@ietf.org>
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 564691A02AA; Tue,  4 Mar 2014 12:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 lOJnCj9G8MW9; Tue,  4 Mar 2014 12:37:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9071A0305; Tue,  4 Mar 2014 12:37:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140304203700.2291.17459.idtracker@ietfa.amsl.com>
Date: Tue, 04 Mar 2014 12:37:00 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/s4LnmKIA5QfijFOZk7OE9PLk0_E
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-arch-13.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 04 Mar 2014 20:37:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : IPv6 Home Networking Architecture Principles
        Authors         : Tim Chown
                          Jari Arkko
                          Anders Brandt
                          Ole Troan
                          Jason Weil
	Filename        : draft-ietf-homenet-arch-13.txt
	Pages           : 52
	Date            : 2014-03-04

Abstract:
   This text describes evolving networking technology within residential
   home networks with increasing numbers of devices and a trend towards
   increased internal routing.  The goal of this document is to define a
   general architecture for IPv6-based home networking, describing the
   associated principles, considerations and requirements.  The text
   briefly highlights specific implications of the introduction of IPv6
   for home networking, discusses the elements of the architecture, and
   suggests how standard IPv6 mechanisms and addressing can be employed
   in home networking.  The architecture describes the need for specific
   protocol extensions for certain additional functionality.  It is
   assumed that the IPv6 home network is not actively managed, and runs
   as an IPv6-only or dual-stack network.  There are no recommendations
   in this text for the IPv4 part of the network.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-arch/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-arch-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-arch-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Mar  4 15:01:48 2014
Return-Path: <markus.stenberg@iki.fi>
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 CC2751A002F for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 15:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 EJ3HsPc4QN4n for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 15:01:42 -0800 (PST)
Received: from jenni2.inet.fi (mta-out.inet.fi [195.156.147.13]) by ietfa.amsl.com (Postfix) with ESMTP id 09E681A001A for <homenet@ietf.org>; Tue,  4 Mar 2014 15:01:41 -0800 (PST)
Received: from [192.168.43.129] (80.220.67.193) by jenni2.inet.fi (8.5.140.03) (authenticated as stenma-47) id 52775C990A1A5515; Wed, 5 Mar 2014 01:01:29 +0200
Content-Type: text/plain; charset=iso-2022-jp
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87ha7dlrx5.wl%jch@pps.univ-paris-diderot.fr>
Date: Tue, 4 Mar 2014 23:01:09 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <07E94521-F378-46DD-A10D-2A35EB3CFF54@iki.fi>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <A57940C0-B602-4849-93A7-0930FE2D8C88@iki.fi> <53161623.6080700@openwrt.org> <87ha7dlrx5.wl%jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/5M-aZTxC5rNsWFdDILAqRsFFTzE
Cc: Steven Barth <cyrus@openwrt.org>, Markus Stenberg <markus.stenberg@iki.fi>, homenet@ietf.org
Subject: Re: [homenet] HCNP: my points this morning
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: Tue, 04 Mar 2014 23:01:45 -0000

On 4.3.2014, at 18.50, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>>> Add a no-routing-TLV (zero content) which means that routes towards
>>> this node have to be done without routing protocol (by other HNCP
>>> nodes that support real routing protocol).
> Could you please spell out what problem you're trying to solve?  If
> the problem is nodes with limited resources, then let's choose
> a protocol that allows minimal implementations.  Snooping on RIPng or
> Babel and installing a default route (using a hackish system("ip route =
add"))
> can be done in two hundred lines of code or so.  (Yes, I=1B$B!G=1B(Bm =
volunteering.)

It=1B$B!G=1B(Bs mostly the 0 real routing protocols case on some routers =
that it addresses. However, I=1B$B!G=1B(Bm perfectly happy to live with =
the =1B$B!F=1B(B1 routing protocol, always=1B$B!G=1B(B mode of operation =
too ;)

Just snooping wouldn=1B$B!G=1B(Bt work very well, as for assuming =
no-real-routing arbitrary node in topology, both it and it=1B$B!G=1B(Bs =
neighbors have to do manual route maintenance to keep packets flowing. =
The fallback option (documented in hncp-00) would work, though, if the =
affected node and it=1B$B!G=1B(Bs on-link neighbors would do it.

Cheers,

-Markus


From nobody Tue Mar  4 15:42:16 2014
Return-Path: <ajs@anvilwalrusden.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 65FE51A0063 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 15:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 zOX3wnhS3Mof for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 15:42:12 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB251A0074 for <homenet@ietf.org>; Tue,  4 Mar 2014 15:42:12 -0800 (PST)
Received: from mx1.yitter.info (unknown [130.129.158.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B896A8A031 for <homenet@ietf.org>; Tue,  4 Mar 2014 23:42:08 +0000 (UTC)
Date: Tue, 4 Mar 2014 18:42:06 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20140304234206.GC9166@mx1.yitter.info>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20140304043321.0c893400@resistor.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/XIXe_I4ow9Nq1j73lnRGSXGVL2s
Subject: Re: [homenet] DNSSEC and homenet
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: Tue, 04 Mar 2014 23:42:13 -0000

On Tue, Mar 04, 2014 at 04:50:33AM -0800, SM wrote:
> correctly the answer in the DNS cache would be for a non-global
> resource.  There is no longer an assumption of uniqueness.  As a
> local decision I would use low TTLs [1].

But as Michael pointed out upthread, the more realistic and compelling
(if harder to understand) examples involve a dual-homed node like a
phone flipping from one interface to another.  You'd need sub-second
TTLs for that not to be a problem, and we don't have those.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Mar  4 21:12:50 2014
Return-Path: <marka@isc.org>
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 B262E1A0231 for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 21:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 CiuEP_uOMLJq for <homenet@ietfa.amsl.com>; Tue,  4 Mar 2014 21:12:42 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id C0DAA1A022C for <homenet@ietf.org>; Tue,  4 Mar 2014 21:12:42 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 820BFC949B; Wed,  5 Mar 2014 05:12:26 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393996359; bh=mYnGpFnIVaiRWBrSanJerBot3RRvkC78UC4g4B3ic3k=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=T5mn6o+bChLCmskZSBfHAbtMu+wD+Nypqbp2HXlSc3z6YEof21QJBlSjJp7upELqR XGzH9KBBX6adsZWCGqj6RM7TGuByvEaBEbwEWK5KRCt9hM4e6HorfND1BaD5yMjyrd U1fkzS91Szub9lNwggUvSQVKuRd+0NHd2Pfyp/JM=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed,  5 Mar 2014 05:12:26 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D6C8416004E; Wed,  5 Mar 2014 05:13:22 +0000 (UTC)
Received: from rock.dv.isc.org (unknown [149.20.66.86]) by zmx1.isc.org (Postfix) with ESMTPSA id 3E97D160041; Wed,  5 Mar 2014 05:13:22 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 49EF410B2648; Wed,  5 Mar 2014 16:12:21 +1100 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info>
In-reply-to: Your message of "Tue, 04 Mar 2014 18:42:06 -0500." <20140304234206.GC9166@mx1.yitter.info>
Date: Wed, 05 Mar 2014 16:12:21 +1100
Message-Id: <20140305051221.49EF410B2648@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Cl5SSW3D9SgUPwUBiTWzaHUCUCk
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 05:12:46 -0000

In message <20140304234206.GC9166@mx1.yitter.info>, Andrew Sullivan writes:
> On Tue, Mar 04, 2014 at 04:50:33AM -0800, SM wrote:
> > correctly the answer in the DNS cache would be for a non-global
> > resource.  There is no longer an assumption of uniqueness.  As a
> > local decision I would use low TTLs [1].
> 
> But as Michael pointed out upthread, the more realistic and compelling
> (if harder to understand) examples involve a dual-homed node like a
> phone flipping from one interface to another.  You'd need sub-second
> TTLs for that not to be a problem, and we don't have those.

I don't see current phones flip from WiFi to 3/4G multiple times a
second.  They have longer duty cycles than that.  Additionally if
you are in such a zone you tend to 1) move or 2) force WiFi or 3/4G
to get stability.

Additionally the impact of getting the wrong version is that you end
up with a unusable address when you get a ULA/RFC 1918 address packets
to which should be dropped by the telco or you get NXDOMAIN or the
global address of the resourse and hair pinnig in the NAT helps with
the later.

Mark

> Best,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Mar  5 00:36:13 2014
Return-Path: <v6ops@globis.net>
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 5CF271A00EC for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 00:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.521
X-Spam-Level: 
X-Spam-Status: No, score=-0.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_64=0.6, SPF_NEUTRAL=0.779] autolearn=no
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 rzQRDYQ-voxA for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 00:36:04 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id DE07E1A023B for <homenet@ietf.org>; Wed,  5 Mar 2014 00:36:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 834E58714A1; Wed,  5 Mar 2014 09:35:59 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABfCb3vpxmVL; Wed,  5 Mar 2014 09:35:59 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 6337A870F92; Wed,  5 Mar 2014 09:35:59 +0100 (CET)
Message-ID: <5316E1EE.7040200@globis.net>
Date: Wed, 05 Mar 2014 09:35:58 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Steven Barth <cyrus@openwrt.org>
References: <58809B4D-CCE4-4DAC-9A1A-DD475584E65B@iki.fi> <6BF5B681-446C-4BCA-9B53-A05A9D4A9E38@townsley.net> <52FE480F.3030801@globis.net> <52FE6E9B.3060107@openwrt.org>
In-Reply-To: <52FE6E9B.3060107@openwrt.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/8bXOIiY3v5jGvMdqiR1AtK0fS3w
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, markus.stenberg@iki.fi, Mark Townsley <mark@townsley.net>
Subject: Re: [homenet] HNCP
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: Wed, 05 Mar 2014 08:36:09 -0000

> Steven Barth <mailto:cyrus@openwrt.org>
> 14 February 2014 20:29
>
> I think your arguments about the downsides are valid and we have 
> thought about them as well. However the current approach seems to be 
> practical given the current situation that there is no common 
> consensus about an IGP or about there even being an IGP that fits all 
> use cases. Some people even argue that in some or many common cases an 
> IGP might be overkill.
>
> On top of that I even think if there would be a consensus in the near 
> future then we still need autoconfiguration and source+dest routing 
> standardized and adopted for that given IGP which will probably take 
> quite some time as well.
>
> So yes, there are limitations and hopefully this is not the final 
> stance on this topic and at some point there is some kind of 
> industry-consensus on an IGP. But honestly I don't see this happening 
> any time soon.
>
>
> ------------------------------------------------------------------------
Thinking further about what should or should not be in HNCP.

Is HNCP a useful place to standardise negotiation and maintenance of 
trust anchors?

I know many pieces of kit support a 'peer now' button (Bluetooth audio, 
DECT phones, Powerline Ethernet), which triggers a leap of faith that 
direct neighbours in the same mode are trustworthy, but I'm not aware of 
any IETF standardised way that Homenet devices could negotiate e.g. a 
common encryption key or private root certificate.

As a rough sketch:

an external trigger [physical button, GUI command, first power on, 
factory specific action] places one or more devices into "leap of faith" 
mode
each device generates a candidate encryption key or private key on the fly
device detects direct neighbours in similar leap of faith negotiation mode
two neighbouring devices establish a secure channel between the pair
neighbouring devices exchange certificates or keys and optionally enter 
them into a store, so that the direct neighbors can authenticate each 
other in the future without entering leap of faith mode.

Devices periodically flood a public key throughout the homenet, with the 
flooding being authenticated across each pair of neighbours using the 
trust established above, or a HNCP key or certificate that has been 
previously established.
During the flooding, if A trusts B and B trusts C then A trusts C.
All devices end up with a copy of every other device's public key. Each 
device has its own private key.

For maintenance, a timer triggers key or certificate roll over of 
existing established neighbour trust relationships

This HNCP established key or certificate can be used to authenticate 
future HNCP messages (e.g. between two devices that were not direct 
neighbours, but become neighbours, because one device has been 
replugged), or other messages in other protocols.

-- 
Regards,
RayH


From nobody Wed Mar  5 01:04:07 2014
Return-Path: <pierre.pfister@darou.fr>
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 A8DCC1A0255 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level: 
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RP_MATCHES_RCVD=-0.547] 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 7XdnSxAvDgQi for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:04:03 -0800 (PST)
Received: from ks395963.kimsufi.com (darou.fr [176.31.121.140]) by ietfa.amsl.com (Postfix) with ESMTP id 378D91A0177 for <homenet@ietf.org>; Wed,  5 Mar 2014 01:04:03 -0800 (PST)
Received: from dhcp-a063.meeting.ietf.org (dhcp-a063.meeting.ietf.org [31.133.160.99]) (Authenticated sender: pierre@darou.fr) by ks395963.kimsufi.com (Postfix) with ESMTPSA id 075AA6049D; Wed,  5 Mar 2014 10:03:58 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr>
Date: Wed, 5 Mar 2014 09:03:58 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Ul8Z1YAC00tqJZjnCJrgP4Oj4dw
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HCNP: my points this morning
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: Wed, 05 Mar 2014 09:04:06 -0000

I agree with Markus and Steven on most points, but let me clarify a few =
aspects.

- First, I think this is really cool if another area wants to use hncp. =
So I don=92t see any reason we couldn=92t adapt the documents to allow =
it. We should be careful *not* to make homenet specifications too =
complex thought. Having too many abstraction layers may not be =
desirable.

- As Markus said, I think removing some TLV=92s from hncp transport =
layer specifications is not a problem. We can have a specification for =
hncp-transport, and another for hncp-homenet. I=92m a bit more concerned =
about removing trickle algorithm behavior. We can abstract the TLV =
layer, but abstracting upper AND lower layer seems too ambitious. Having =
the network to correctly converge, and efficiently enough, is not an =
easy requirement. Trickle is lightweight, efficient, proven for this =
purpose. I think hncp should precisely specify the packets transmission =
behavior.

- The prefix assignment algorithm supports /128. I=92m not sure we want =
Homenet to have such =91carve it into /128=92 option. Homenet doesn=92t =
want to do that.

- Homenet-hncp intends to be incremental in terms of TLVs. Other TLVs =
will come, and, if hncp is widely used in homes, vendor-specific options =
will come as well. So I think =91ignore TLVs you don=92t know=92 is the =
correct behavior.
Nevertheless, I understand hncp could be used for other purposes, in =
different contexts. But such use should run in different instances. =
Using a different UDP port, *or* creating a =91context=92 TLV or header =
value (With defined =91homenet=92 context, =91ahcp=92 context, etc=85). =
Of course, in terms of performances, using a different UDP port is =
desirable.

- Concerning the routing protocol, finally. Although I like the 0,1 =
option and that negotiating a routing protocol doesn=92t disturbs me so =
much, I think most vendors will only implement the 0 if they can=85 So, =
for Homenet, I think we are going to end up with a single RP. I may be =
dreaming, but I would like to see the hncp-routing (0 RP), because it =
would avoid a lot of redundancy in propagated information. But for that =
purpose, we=92ll have to prove its design is correct.
Then, if we make a hncp-transport document, it will be completely =
agnostic to this routing stuff. Only hncp-homenet will. Using a =
different =91context=92 or UDP port, you could just define your own =
behavior for hncp-ahcp regarding routing.

- Thanks for you comments. It=92s a very interesting discussion.

Le 4 mars 2014 =E0 14:56, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> a =E9crit :

> Hi,
>=20
> During this morning's session, I mentioned how much I like the HCNP
> protocol, and that I'm looking into abandoning AHCP for a hacked-up
> HCNP.  I made the following points this morning:
>=20
> 0. As far as I'm concerned, this is not "The Homenet Configuration
> Protocol", this is a configuration protocol for unmanaged routers that
> happens to have been designed by the Homenet group.  Please keep this
> in mind when you read the following.
>=20
> 1. The draft seems overspecified at times.  Do we really mandate
> Trickle, or do we want just an abstract description of flooding
> requirements?  (Knowledgeable people commented that Trickle is fine.)
>=20
> 2. Related to the previous point, is everything MUST, or should some
> parts be made optional?  I'd personally like the DNS proxy stuff to be
> made optional.
>=20
> 3. There would appear to be no way to specify "please carve this
> prefix into /64 or shorter" as opposed to "please feel free to grab
> a /128 in this prefix".
>=20
> 4. Do we want the ability to mark an option as mandatory, as in
> "Please don't configure unless you understand the following TLV, and
> intend to act upon it".  One the one hand, this makes is easier to
> design compatible extensions to the protocol (by sending two
> configuration blocks, one with a mandatory incompatible option, one
> without the option, and having old routers ignore the block with the
> incompatible option).  On the other hand, it adds another failure =
mode.
>=20
> 5. I don't think the routing protocol should be negotiated by the
> config protocol, since that implies that the routing daemon is started
> by the config daemon.  The routing daemon(s) should be started at
> boot, and notice when the config daemon adds IP addresses to
> interfaces.  Knowledgeable people appeared to disagree.
>=20
> (It seems to me that the config protocol should be routing-protocol
> agnostic, and merely say "this protocol assumes that a routing
> protocol satisfying the following conditions is available".  Homenet
> should specify what the protocol is, and mandate implementation of The
> One Homenet Routing Protocol (OHRP).)
>=20
> I'd like RIP to be the OHRP, but I don't have strong opinions on the
> subject.
>=20
> I also don't care whether Homenet says that routers MUST implement
> OHRP, or whether they MUST implement OHRP and MAY implement other
> routing protocols.  In either case,
>=20
>  - commercial Homenet router vendors will implement the OHRP and
>    ignore the MAY protocols;
>  - the OpenWRT routing overlay will probably install the OHRP by
>    default, but provide its usual set of optional routing daemons.
>=20
> In short, there will be no difference in practice whether Homenet
> allows non-Homenet routing protocols or not.
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Mar  5 01:09:53 2014
Return-Path: <markus.stenberg@iki.fi>
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 888C11A01C7 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:09:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 Wxd5vAAkzAJF for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:09:49 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out.inet.fi [195.156.147.13]) by ietfa.amsl.com (Postfix) with ESMTP id B02661A0200 for <homenet@ietf.org>; Wed,  5 Mar 2014 01:09:48 -0800 (PST)
Received: from [192.168.43.129] (80.220.67.193) by kirsi1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 529734CF081447C9; Wed, 5 Mar 2014 11:09:32 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <5316E1EE.7040200@globis.net>
Date: Wed, 5 Mar 2014 09:09:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <06EF824C-9D02-4EEA-A257-6AE5304CDAE4@iki.fi>
References: <58809B4D-CCE4-4DAC-9A1A-DD475584E65B@iki.fi> <6BF5B681-446C-4BCA-9B53-A05A9D4A9E38@townsley.net> <52FE480F.3030801@globis.net> <52FE6E9B.3060107@openwrt.org> <5316E1EE.7040200@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/MydGWfLdYi4paWEV4LesfRanjlU
Cc: Steven Barth <cyrus@openwrt.org>, Markus Stenberg <markus.stenberg@iki.fi>, Mark Townsley <mark@townsley.net>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HNCP
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: Wed, 05 Mar 2014 09:09:51 -0000

On 5.3.2014, at 8.35, Ray Hunter <v6ops@globis.net> wrote:
> Thinking further about what should or should not be in HNCP.
>=20
> Is HNCP a useful place to standardise negotiation and maintenance of =
trust anchors?

I=92m not sure. It is definitely feasible place for it, though..

> I know many pieces of kit support a 'peer now' button (Bluetooth =
audio, DECT phones, Powerline Ethernet), which triggers a leap of faith =
that direct neighbours in the same mode are trustworthy, but I'm not =
aware of any IETF standardised way that Homenet devices could negotiate =
e.g. a common encryption key or private root certificate.
>=20
> As a rough sketch:
>=20
> an external trigger [physical button, GUI command, first power on, =
factory specific action] places one or more devices into "leap of faith" =
mode
> each device generates a candidate encryption key or private key on the =
fly
> device detects direct neighbours in similar leap of faith negotiation =
mode
> two neighbouring devices establish a secure channel between the pair
> neighbouring devices exchange certificates or keys and optionally =
enter them into a store, so that the direct neighbors can authenticate =
each other in the future without entering leap of faith mode.

Given multiple scopes of HNCP (e.g. PA draft assumes that there is both =
linklocal and network-wide set of TLVs; currently only the later is done =
so we use network-wide TLVs even when we don=92t need to in the =
implementation), this would be fairly straightforward to do; announce =
the faith negotiation mode using linklocal(ish) TLV, and then define an =
exchange that basically is just =91hey, you want to trust me, right?=92 =
and vice versa.=20

We have a student look at this starting in April, but obviously input is =
solicited here too; is this a good idea? Should we instead assume =
public/private keys and associated trust data just show up magically and =
use that?

Cheers,

-Markus=


From nobody Wed Mar  5 01:15:47 2014
Return-Path: <mcr@sandelman.ca>
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 262A11A02D3 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 vTOffpI6tuCS for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:15:43 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 8522F1A02AD for <homenet@ietf.org>; Wed,  5 Mar 2014 01:15:43 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E091120095; Wed,  5 Mar 2014 05:34:11 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 3E82F647C9; Wed,  5 Mar 2014 04:15:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 17AA7647C8; Wed,  5 Mar 2014 04:15:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Andrews <marka@isc.org>
In-Reply-To: <20140305051221.49EF410B2648@rock.dv.isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 05 Mar 2014 04:15:38 -0500
Message-ID: <24056.1394010938@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/GXUTVT4QtvMdkfG0Y7PNnOPAlqk
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 09:15:45 -0000

--=-=-=


Mark Andrews <marka@isc.org> wrote:
    > In message <20140304234206.GC9166@mx1.yitter.info>, Andrew Sullivan
    > writes:
    >> On Tue, Mar 04, 2014 at 04:50:33AM -0800, SM wrote: > correctly the
    >> answer in the DNS cache would be for a non-global > resource.  There
    >> is no longer an assumption of uniqueness.  As a > local decision I
    >> would use low TTLs [1].
    >>
    >> But as Michael pointed out upthread, the more realistic and compelling
    >> (if harder to understand) examples involve a dual-homed node like a
    >> phone flipping from one interface to another.  You'd need sub-second
    >> TTLs for that not to be a problem, and we don't have those.

    > I don't see current phones flip from WiFi to 3/4G multiple times a
    > second.  They have longer duty cycles than that.  Additionally if you
    > are in such a zone you tend to 1) move or 2) force WiFi or 3/4G to get
    > stability.

Current Android phones have to turn one or to turn the other on. (I can't
speak for other brands).  They also don't do MIF at all.
That why it takes so long, and it pissed people off, and it's gonna get fixed.

At that point, it won't be that they "flip", so much as they always have the
3G alive, but the wifi could get too weak and it might flip things over.

People don't want to be "forcing" things --- they want to just have a device
in their pocket that does stuff for them.

So I agree that this isn't a problem we see today, but maybe next year;
certainly before homenet w/DNSSEC is seen by early adopters.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxbrOYqHRg3pndX9AQKlxgP+LCknfzxYHrCaqI+MrC8Y8BEEsT7U2/2j
VL2iVIw6udK9VKoe+50EPMIFs8R9o5le+Nsy2DVuY4uDj6u5Ys0GDZ6Lbys5WMAC
m0YX/CVxYodH5fqN3DD+tKqPoGIPe1xtAimjs03r/plly8YiLjh/bDs7PRkL9Aqk
0QbA2WuKKzI=
=U60b
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar  5 01:29:15 2014
Return-Path: <brian.e.carpenter@gmail.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 5BCCC1A000D for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 75N3sJOOZrLT for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:29:09 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 063AC1A0199 for <homenet@ietf.org>; Wed,  5 Mar 2014 01:29:08 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id z12so864925wgg.17 for <homenet@ietf.org>; Wed, 05 Mar 2014 01:29:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0PmpOUtWGdF28GPbjjqdhsavuU7+JKTe1zZEuI1ksa8=; b=Gk4ab3+kNqjlPo3uYCGwx2sbsL3rRuRka/iTYxFUSNLd2kZWvVNT8tUlOV9uAsXar8 tpm3CiNJKoJm0gMpgEPuzh9nax0aLjIpTEc10oPPVtg8IDv3pMSc7ZAxHaymCxp5wDd6 vQRU/d9jiqVlXUElKjJxGkhgmFYfPVrtK+tWC9O5mMICsO+E5TsNHzXhrO3fwToSQCr+ ibHKwXbSbGST389IbhJcgWoqwT0bElzdcqPEvHesiCnzya19PGpzl4Vl55mI1Pz0t4VH YiSInbOowqmvevfcDX4fUTcrtnZ/Ns54B7cdBzg/Vp0tTCPjikfHxwnqImm3Vzx8r1tJ dYng==
X-Received: by 10.194.92.164 with SMTP id cn4mr6933858wjb.74.1394011745126; Wed, 05 Mar 2014 01:29:05 -0800 (PST)
Received: from [31.133.165.224] (dhcp-a5e0.meeting.ietf.org. [31.133.165.224]) by mx.google.com with ESMTPSA id dd3sm8858082wjb.9.2014.03.05.01.29.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 01:29:04 -0800 (PST)
Message-ID: <5316EE5E.7050801@gmail.com>
Date: Wed, 05 Mar 2014 22:29:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr>
In-Reply-To: <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Y8FSBJevDEihCBQJ6mEbQIIzKEM
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] HCNP: my points this morning
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: Wed, 05 Mar 2014 09:29:11 -0000

> - The prefix assignment algorithm supports /128. I=E2=80=99m not sure w=
e want Homenet to have such =E2=80=98carve it into /128=E2=80=99 option. =
Homenet doesn=E2=80=99t want to do that.

It was pretty clear in 6man yesterday that there is little support
for longer subnet prefixes than 64, and they are forbidden by the
homenet architecture. All the same, it seems to me that routing
should be strictly VLSN (and that is the IPv6 routing architecture).
So I think that basic protocols should be agnostic on the prefix
length, which means allow anything out to /128.

An implementation should follow the homenet architecture, of course.

    Brian


From nobody Wed Mar  5 01:58:47 2014
Return-Path: <marka@isc.org>
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 C1C381A02B8 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 wvNf6HshA8y9 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 01:58:43 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 884B01A01C2 for <homenet@ietf.org>; Wed,  5 Mar 2014 01:58:43 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 6ED80C9484; Wed,  5 Mar 2014 09:58:27 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1394013520; bh=bdmsNWvE7CXvrV59kU/ru8Cm/VIma4r92uIBsmU6ofA=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=cVtScTsYiu1XQS8Ly38L8KvTFO5j6aBoFudkF7/NCKPkETzGqT5Dyuh/q4ksZkyt5 F5phdcrmZE++oDu1tyXb8FYx3wcAEAE/bm+u5eQSfv/8zuTcMTw+B4dJyUTRrkbnRM /5/iTQCiKTZ0qY3jZCaUyFjcRtt0KzM27g/86PLs=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed,  5 Mar 2014 09:58:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DD60A16005C; Wed,  5 Mar 2014 09:59:23 +0000 (UTC)
Received: from rock.dv.isc.org (unknown [149.20.66.86]) by zmx1.isc.org (Postfix) with ESMTPSA id 2823E16005B; Wed,  5 Mar 2014 09:59:23 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [127.0.0.1]) by rock.dv.isc.org (Postfix) with ESMTP id 06E1610BC47D; Wed,  5 Mar 2014 20:58:23 +1100 (EST)
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca>
In-reply-to: Your message of "Wed, 05 Mar 2014 04:15:38 -0500." <24056.1394010938@sandelman.ca>
Date: Wed, 05 Mar 2014 20:58:23 +1100
Message-Id: <20140305095823.06E1610BC47D@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/784VvoK-RmQ8u9hwrEnO3D0S0Zw
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 09:58:46 -0000

In message <24056.1394010938@sandelman.ca>, Michael Richardson writes:
> --=-=-=
> 
> 
> Mark Andrews <marka@isc.org> wrote:
>     > In message <20140304234206.GC9166@mx1.yitter.info>, Andrew Sullivan
>     > writes:
>     >> On Tue, Mar 04, 2014 at 04:50:33AM -0800, SM wrote: > correctly the
>     >> answer in the DNS cache would be for a non-global > resource.  There
>     >> is no longer an assumption of uniqueness.  As a > local decision I
>     >> would use low TTLs [1].
>     >>
>     >> But as Michael pointed out upthread, the more realistic and compelling
>     >> (if harder to understand) examples involve a dual-homed node like a
>     >> phone flipping from one interface to another.  You'd need sub-second
>     >> TTLs for that not to be a problem, and we don't have those.
> 
>     > I don't see current phones flip from WiFi to 3/4G multiple times a
>     > second.  They have longer duty cycles than that.  Additionally if you
>     > are in such a zone you tend to 1) move or 2) force WiFi or 3/4G to get
>     > stability.
> 
> Current Android phones have to turn one or to turn the other on. (I can't
> speak for other brands).  They also don't do MIF at all.
> That why it takes so long, and it pissed people off, and it's gonna get fixed
> .
> 
> At that point, it won't be that they "flip", so much as they always have the
> 3G alive, but the wifi could get too weak and it might flip things over.

iPhones flip based on WiFi signal strength and being to associate with the
AP but certainly not multiple times a second.

> People don't want to be "forcing" things --- they want to just have a device
> in their pocket that does stuff for them.

Which they do today.  If you are sitting on the edge of WiFi range you get
a bit of flip flop but most of the time one is just "On WiFi" at home or
on 3G (or whatever) when away from home.

For me the WiFi border is sitting at the bus stop around the corner.
 
> So I agree that this isn't a problem we see today, but maybe next year;
> certainly before homenet w/DNSSEC is seen by early adopters.

I really don't see this as being a issue in practice.  Just sign
the zone (all verisons) in the house with the same keys.  Stop with
this nonsence idea that you shouldn't sign the internal version
when you are signing the external version.

The CPE is a recursive server on the inside interfaces that is also
authoritative for these zones with acls limiting recursion to
internal addresses.  The external interface is only authoritative
for the external version of the zones.

For the record I have split horizon signed zones with the same
DNSKEY records for both versions running on my border router which
is a 1998 vintage PC and have done for about a decade now.  Same
sort of compute power and storage as you can get in modern CPE
devices.  I eat my own dog food.  The nameserver accepts dynamic
updates from both the DHCP server and internal clients.  The home
has GUA, ULA IPv6 addresses + RFC 1918 addresses for IPv4.  This all
just works.

Mark

> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting for hire =-
> 
> 
> 
> 
> --=-=-=
> Content-Type: application/pgp-signature
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQCVAwUBUxbrOYqHRg3pndX9AQKlxgP+LCknfzxYHrCaqI+MrC8Y8BEEsT7U2/2j
> VL2iVIw6udK9VKoe+50EPMIFs8R9o5le+Nsy2DVuY4uDj6u5Ys0GDZ6Lbys5WMAC
> m0YX/CVxYodH5fqN3DD+tKqPoGIPe1xtAimjs03r/plly8YiLjh/bDs7PRkL9Aqk
> 0QbA2WuKKzI=
> =U60b
> -----END PGP SIGNATURE-----
> --=-=-=--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Mar  5 02:19:28 2014
Return-Path: <teco@inf-net.nl>
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 171521A039E for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 02:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 GSgZBcpDNRuz for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 02:19:24 -0800 (PST)
Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by ietfa.amsl.com (Postfix) with ESMTP id 85FB51A039D for <homenet@ietf.org>; Wed,  5 Mar 2014 02:19:23 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id t60so917526wes.5 for <homenet@ietf.org>; Wed, 05 Mar 2014 02:19:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=wNCe/bVbWVXJQRKHcFYm+1GLfbDUgOko9eEBhI4I3cE=; b=JnaT4WH+62sLz032vGLh+D4abJVUTFB4oQhTjBw5mkZ2RE/BD/UmTJm/KQryhlJEZz b8wupqqkHwDaxBxdYqDtS2VFqHm755Gri/ZsecCONeBN/0mRmC0sWDsBf8VYD3JSM/dz iUdgbz13iXy9+LxBiIFIae+ZVNrUUUMcdWAjfrr9yyPEZOcgS7g2mvbxbFp2hT88zHOC iG+zGvWoYXwUw0PgYW4yIyxmQwemW8XHe8pqJWFW9s2DqIFb0az8i55oPwq8dWXmm/PU ki0N+D68akyRIybNEEEWmPCZUwC8yMX9FK3GgH49v42FwlfvRJm8UonL8UcnqPpppZGi mz1g==
X-Gm-Message-State: ALoCoQnInd4x6AqhCTxWXKjjtzSPzE8vr//RIhjxm9nfqehvNbK0tM264IR0TW3MGQ7M3kUXHKiN
X-Received: by 10.195.13.103 with SMTP id ex7mr7120591wjd.3.1394014760024; Wed, 05 Mar 2014 02:19:20 -0800 (PST)
Received: from dhcp-a727.meeting.ietf.org (dhcp-a727.meeting.ietf.org. [31.133.167.39]) by mx.google.com with ESMTPSA id uq2sm9508685wjc.5.2014.03.05.02.19.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 02:19:19 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <5316E1EE.7040200@globis.net>
Date: Wed, 5 Mar 2014 11:19:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <25A6B6D6-DFBE-4BE8-AAF8-479FD3E15494@inf-net.nl>
References: <58809B4D-CCE4-4DAC-9A1A-DD475584E65B@iki.fi> <6BF5B681-446C-4BCA-9B53-A05A9D4A9E38@townsley.net> <52FE480F.3030801@globis.net> <52FE6E9B.3060107@openwrt.org> <5316E1EE.7040200@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/WjR5UhOs7KMHLFbrhETXJ3_9kSk
Cc: Steven Barth <cyrus@openwrt.org>, Markus Stenberg <markus.stenberg@iki.fi>, Mark Townsley <mark@townsley.net>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HNCP
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: Wed, 05 Mar 2014 10:19:27 -0000

Op 5 mrt. 2014, om 09:35 heeft Ray Hunter <v6ops@globis.net> het =
volgende geschreven:

>> Steven Barth <mailto:cyrus@openwrt.org>
>> 14 February 2014 20:29
>>=20
>> I think your arguments about the downsides are valid and we have =
thought about them as well. However the current approach seems to be =
practical given the current situation that there is no common consensus =
about an IGP or about there even being an IGP that fits all use cases. =
Some people even argue that in some or many common cases an IGP might be =
overkill.
>>=20
>> On top of that I even think if there would be a consensus in the near =
future then we still need autoconfiguration and source+dest routing =
standardized and adopted for that given IGP which will probably take =
quite some time as well.
>>=20
>> So yes, there are limitations and hopefully this is not the final =
stance on this topic and at some point there is some kind of =
industry-consensus on an IGP. But honestly I don't see this happening =
any time soon.
>>=20
>>=20
>> =
------------------------------------------------------------------------
> Thinking further about what should or should not be in HNCP.
>=20
> Is HNCP a useful place to standardise negotiation and maintenance of =
trust anchors?
>=20
> I know many pieces of kit support a 'peer now' button (Bluetooth =
audio, DECT phones, Powerline Ethernet), which triggers a leap of faith =
that direct neighbours in the same mode are trustworthy, but I'm not =
aware of any IETF standardised way that Homenet devices could negotiate =
e.g. a common encryption key or private root certificate.
>=20
> As a rough sketch:
>=20
> an external trigger [physical button, GUI command, first power on, =
factory specific action] places one or more devices into "leap of faith" =
mode
> each device generates a candidate encryption key or private key on the =
fly
> device detects direct neighbours in similar leap of faith negotiation =
mode
> two neighbouring devices establish a secure channel between the pair
> neighbouring devices exchange certificates or keys and optionally =
enter them into a store, so that the direct neighbors can authenticate =
each other in the future without entering leap of faith mode.
>=20
> Devices periodically flood a public key throughout the homenet, with =
the flooding being authenticated across each pair of neighbours using =
the trust established above, or a HNCP key or certificate that has been =
previously established.
> During the flooding, if A trusts B and B trusts C then A trusts C.
> All devices end up with a copy of every other device's public key. =
Each device has its own private key.
>=20
> For maintenance, a timer triggers key or certificate roll over of =
existing established neighbour trust relationships
>=20
> This HNCP established key or certificate can be used to authenticate =
future HNCP messages (e.g. between two devices that were not direct =
neighbours, but become neighbours, because one device has been =
replugged), or other messages in other protocols.

On user friendly trust maintenance, I would use by mobile to let my new =
devices join my homenet. Also, I would use the app for excluding devices =
I don=92t own anymore. I=92m not sure the mechanism needs to be build on =
a distributed database or has a more centralized approach. Perhaps use =
the zero dependency rule and avoid SPOF.

Having my portable gear be part of HNCP would introduce additional =
requirements on merge of the distributed database, on for example =
conflict resolving.

Teco


>=20
> --=20
> Regards,
> RayH
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Mar  5 02:25:49 2014
Return-Path: <ajs@anvilwalrusden.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 E1DA11A03C3 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 02:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 X7WG08nzaVhC for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 02:25:43 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 4593A1A03C1 for <homenet@ietf.org>; Wed,  5 Mar 2014 02:25:43 -0800 (PST)
Received: from mx1.yitter.info (dhcp-bcfb.meeting.ietf.org [31.133.188.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 066808A031 for <homenet@ietf.org>; Wed,  5 Mar 2014 10:25:38 +0000 (UTC)
Date: Wed, 5 Mar 2014 05:25:37 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20140305102536.GD9266@mx1.yitter.info>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca> <20140305095823.06E1610BC47D@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140305095823.06E1610BC47D@rock.dv.isc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/h24rcBC7Xj1cht2CwyrT4S8ia4E
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 10:25:48 -0000

Mark,

On Wed, Mar 05, 2014 at 08:58:23PM +1100, Mark Andrews wrote:
> a bit of flip flop but most of the time one is just "On WiFi" at home or

The point is that we're designing a protocol, and "most of the time"
won't be good enough to avoid support calls to the ISP help desk.  ISP
margins are thin enough that it would be a bad thing to build a
specification that encourages that even rarely.

> I really don't see this as being a issue in practice.  Just sign
> the zone (all verisons) in the house with the same keys.  Stop with
> this nonsence idea that you shouldn't sign the internal version
> when you are signing the external version.

Mark, you're at least jumping ahead to implementation and at worst
begging the question.  We started with a proposal that did signing in
the ISP's server.  I was pointing out the consequences of that for
DNSSEC.  One of the possible solutions is that the "internal version"
is unsigned.  It would be careless not to list that as one of the
possibilities, even if I think that's a foolish outcome.  We have to
list the possibilities we don't like, too, or else we won't have a
clear picture of what we're talking about.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Mar  5 03:02:25 2014
Return-Path: <marka@isc.org>
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 471DD1A0434 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 mPQiEchekKFU for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:02:20 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 50FF31A0431 for <homenet@ietf.org>; Wed,  5 Mar 2014 03:02:20 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id DD118C941E; Wed,  5 Mar 2014 11:02:03 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1394017337; bh=Wkhnti0CccYTlPIxD1U8wfHJLE12opDRjULyMS02+nk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=UfNIihnwSG8rDStQ6bhNT2Wwg2V++gT/BWSPqcFgb/ykBczY58voUgqpN+pB8YrOq LwlEGA6VNQaO0AlQJ7LkeZ7+7eDv/SafZSgYTW7cCs4quNKT3Cj06XwTdGE68M4zN8 n+N7D6LnFb/r3JA/oU7M83SD3Ye9OKGJ+dpkP330=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed,  5 Mar 2014 11:02:03 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5C99116005C; Wed,  5 Mar 2014 11:03:00 +0000 (UTC)
Received: from rock.dv.isc.org (unknown [149.20.66.86]) by zmx1.isc.org (Postfix) with ESMTPSA id C508116005B; Wed,  5 Mar 2014 11:02:59 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [127.0.0.1]) by rock.dv.isc.org (Postfix) with ESMTP id 4A4D410BCBF1; Wed,  5 Mar 2014 22:01:59 +1100 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca> <20140305095823.06E1610BC47D@rock.dv.isc.org> <20140305102536.GD9266@mx1.yitter.info>
In-reply-to: Your message of "Wed, 05 Mar 2014 05:25:37 -0500." <20140305102536.GD9266@mx1.yitter.info>
Date: Wed, 05 Mar 2014 22:01:59 +1100
Message-Id: <20140305110159.4A4D410BCBF1@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/2o3NWURzxCLCxPegEfqRDsQXiFE
Cc: homenet@ietf.org
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 11:02:23 -0000

In message <20140305102536.GD9266@mx1.yitter.info>, Andrew Sullivan writes:
> Mark,
> 
> On Wed, Mar 05, 2014 at 08:58:23PM +1100, Mark Andrews wrote:
> > a bit of flip flop but most of the time one is just "On WiFi" at home or
> 
> The point is that we're designing a protocol, and "most of the time"
> won't be good enough to avoid support calls to the ISP help desk.  ISP
> margins are thin enough that it would be a bad thing to build a
> specification that encourages that even rarely.

This is a problem that is INDEPENDENT of DNSSEC when you are siging both
zones.   This is about there being two versions of the zone.

> > I really don't see this as being a issue in practice.  Just sign
> > the zone (all verisons) in the house with the same keys.  Stop with
> > this nonsence idea that you shouldn't sign the internal version
> > when you are signing the external version.
> 
> Mark, you're at least jumping ahead to implementation and at worst
> begging the question.  We started with a proposal that did signing in
> the ISP's server.  I was pointing out the consequences of that for
> DNSSEC.  One of the possible solutions is that the "internal version"
> is unsigned.  It would be careless not to list that as one of the
> possibilities, even if I think that's a foolish outcome.  We have to
> list the possibilities we don't like, too, or else we won't have a
> clear picture of what we're talking about.

Signed and unsigned versions of the same zones are a REALLY REALLY
REALLY REALLY bad idea.  This is a "Doctor it hurts if I do this.
Then don't do this." example. It could be made to work with negative
trust anchors which are installed when the WiFi SSID matches the
home's SSID but we really don't want to go there.  There be dragons.

It is dead simple for nameserver in the CPE to do the signing.  Why
people thing it is beyond the capabilities of the a device like
this is beyond me.  The CPE generated the keys.  It signs the
records.  It updates the parent zone to add DS records for the keys
it has generated.

The owner of the CPE has to do nothing to make this happen.

Either sign all version or don't sign any.

I will appeal any version that even hints that mixed signing is the
way to go.  It is just bad design, bad engineer and will cause pain
for everyone.

> Best regards,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Mar  5 03:09:30 2014
Return-Path: <mcr@sandelman.ca>
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 E2D171A0458 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no
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 2RiGESwQ8PY7 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:09:28 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 97AF01A0404 for <homenet@ietf.org>; Wed,  5 Mar 2014 03:09:28 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A1E5B2002A for <homenet@ietf.org>; Wed,  5 Mar 2014 07:27:58 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 92803647C9; Wed,  5 Mar 2014 06:09:24 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7CBFD647C8 for <homenet@ietf.org>; Wed,  5 Mar 2014 06:09:24 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 05 Mar 2014 06:09:24 -0500
Message-ID: <15409.1394017764@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/sC51cga_r1bw6FYEUg21uCCBPno
Subject: Re: [homenet] HCNP: my points this morning
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: Wed, 05 Mar 2014 11:09:30 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Pierre Pfister <pierre.pfister@darou.fr> wrote:
    > I agree with Markus and Steven on most points, but let me clarify a f=
ew
    > aspects.

    > - First, I think this is really cool if another area wants to use
    > hncp. So I don=E2=80=99t see any reason we couldn=E2=80=99t adapt the=
 documents to
    > allow it. We should be careful *not* to make homenet specifications t=
oo
    > complex thought. Having too many abstraction layers may not be
    > desirable.

Copy and paste is an acceptable way to develop specifications.
The IETF owns the text, if someone wants to use it, let them write a
document.  If the documents can be converged later on, great.

    > hncp-transport, and another for hncp-homenet. I=E2=80=99m a bit more =
concerned
    > about removing trickle algorithm behavior. We can abstract the TLV

If you remove trickle, then you might as go back to OSPFv3.

    > - Homenet-hncp intends to be incremental in terms of TLVs. Other TLVs
    > will come, and, if hncp is widely used in homes, vendor-specific
    > options will come as well. So I think =E2=80=98ignore TLVs you don=E2=
=80=99t know=E2=80=99 is
    > the correct behavior.  Nevertheless, I understand hncp could be used

We actually need a "critical" bit on the Type value then.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting for hire =3D-

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxcF5IqHRg3pndX9AQJy8AQA7I4BZ6Ws88VjDYUTAhkswCPpNP45VefH
e9Nmx1vqRX7eeelkjes3LFYn05CeSkhJTyBNYbpiJMcAr/aLe6dCxdYkALS/KIeh
/jkqfNSu9IqO0mPufzLjYEIp8uaY3PSwJiel27x2NLZDSeKPlx/Itwou7Dkoj4O6
lw0rbFpZVQ0=
=j94x
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar  5 03:15:37 2014
Return-Path: <mcr@sandelman.ca>
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 B6A9B1A049F for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 FMo0gnesF7nX for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:15:35 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 585DD1A04B6 for <homenet@ietf.org>; Wed,  5 Mar 2014 03:15:35 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AA7FD2002A; Wed,  5 Mar 2014 07:34:05 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id BD92B647C9; Wed,  5 Mar 2014 06:15:31 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A942D647C8; Wed,  5 Mar 2014 06:15:31 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Andrews <marka@isc.org>
In-Reply-To: <20140305095823.06E1610BC47D@rock.dv.isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca> <20140305095823.06E1610BC47D@rock.dv.isc.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 05 Mar 2014 06:15:31 -0500
Message-ID: <16701.1394018131@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/hCK5xzWjEHlce0pF_qXSXTTYpeA
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 11:15:36 -0000

--=-=-=


Mark Andrews <marka@isc.org> wrote:
    >> People don't want to be "forcing" things --- they want to just have a
    >> device in their pocket that does stuff for them.

    > Which they do today.  If you are sitting on the edge of WiFi range you
    > get a bit of flip flop but most of the time one is just "On WiFi" at
    > home or on 3G (or whatever) when away from home.

Well, it takes so long that it's really annoying, and I know that being on
both networks at the same time ("make before break") is where things are going.

    > For me the WiFi border is sitting at the bus stop around the corner.

The wifi in my front yard depends upon whether the front door is open or
closed.

    >> So I agree that this isn't a problem we see today, but maybe next
    >> year; certainly before homenet w/DNSSEC is seen by early adopters.

    > I really don't see this as being a issue in practice.  Just sign the
    > zone (all verisons) in the house with the same keys.  Stop with this
    > nonsence idea that you shouldn't sign the internal version when you are
    > signing the external version.

We are in violent agreement here: it seems like you are arguing with my use case.
I agree with you: signing with the house key solves the problem of devices
wandering.

    > For the record I have split horizon signed zones with the same DNSKEY
    > records for both versions running on my border router which is a 1998
    > vintage PC and have done for about a decade now.  Same sort of compute
    > power and storage as you can get in modern CPE devices.  I eat my own
    > dog food.  The nameserver accepts dynamic updates from both the DHCP
    > server and internal clients.  The home has GUA, ULA IPv6 addresses +
    > RFC 1918 addresses for IPv4.  This all just works.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUxcHU4qHRg3pndX9AQIbDwP9EhrNNMDIU73Phdywa5737XE1CpV/k1sb
dirESmZRYgUBgB4ucod9QFUBenlJqe/sWeplRvgHJgyBwjvsodo3QUPi6McctUkJ
S6+52AceaqSbjc/qas5E8YuaKNdUHkkWpmSPhwFIiEiSED5j2n7jkDbiJQhiuCq6
9i2dckxTl9w=
=0mKm
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar  5 03:22:34 2014
Return-Path: <ogud@ogud.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 48AF61A0538 for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 CcEoOwTFMqLl for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:22:31 -0800 (PST)
Received: from smtp129.ord.emailsrvr.com (smtp129.ord.emailsrvr.com [173.203.6.129]) by ietfa.amsl.com (Postfix) with ESMTP id 06CEA1A04E9 for <homenet@ietf.org>; Wed,  5 Mar 2014 03:22:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp29.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 8D3F6108697; Wed,  5 Mar 2014 06:22:27 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp29.relay.ord1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BB5041086B1;  Wed,  5 Mar 2014 06:22:25 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20140305110159.4A4D410BCBF1@rock.dv.isc.org>
Date: Wed, 5 Mar 2014 11:22:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A82EB36-6BA8-4070-B44A-D231200F11E6@ogud.com>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca> <20140305095823.06E1610BC47D@rock.dv.isc.org> <20140305102536.GD9266@mx1.yitter.info> <20140305110159.4A4D410BCBF1@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/aAbKdtmZyKZySJWGvs0kJmGULZ8
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 11:22:33 -0000

On Mar 5, 2014, at 11:01 AM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <20140305102536.GD9266@mx1.yitter.info>, Andrew Sullivan =
writes:
>> Mark,
>>=20
>> On Wed, Mar 05, 2014 at 08:58:23PM +1100, Mark Andrews wrote:
>>> a bit of flip flop but most of the time one is just "On WiFi" at =
home or
>>=20
>> The point is that we're designing a protocol, and "most of the time"
>> won't be good enough to avoid support calls to the ISP help desk.  =
ISP
>> margins are thin enough that it would be a bad thing to build a
>> specification that encourages that even rarely.
>=20
> This is a problem that is INDEPENDENT of DNSSEC when you are siging =
both
> zones.   This is about there being two versions of the zone.
>=20
>>> I really don't see this as being a issue in practice.  Just sign
>>> the zone (all verisons) in the house with the same keys.  Stop with
>>> this nonsence idea that you shouldn't sign the internal version
>>> when you are signing the external version.
>>=20
>> Mark, you're at least jumping ahead to implementation and at worst
>> begging the question.  We started with a proposal that did signing in
>> the ISP's server.  I was pointing out the consequences of that for
>> DNSSEC.  One of the possible solutions is that the "internal version"
>> is unsigned.  It would be careless not to list that as one of the
>> possibilities, even if I think that's a foolish outcome.  We have to
>> list the possibilities we don't like, too, or else we won't have a
>> clear picture of what we're talking about.
>=20
> Signed and unsigned versions of the same zones are a REALLY REALLY
> REALLY REALLY bad idea.  This is a "Doctor it hurts if I do this.
> Then don't do this." example. It could be made to work with negative
> trust anchors which are installed when the WiFi SSID matches the
> home's SSID but we really don't want to go there.  There be dragons.
>=20

I think the fundamental question is=20
"Do we expect that INTERNAL zones on a home-net are signed ?

If the answer is yes then we have to assume that some device are DNS =
servers have the=20
ability to sign the zones. If they can sign the internal zones they can =
sign the
external zones.=20

The key management when devices are "rolled" is an issue but that can be =
addressed=20
by smart use of storage devices.=20
Rolled here means both Re-flashed and replaced by new one

> It is dead simple for nameserver in the CPE to do the signing.  Why
> people thing it is beyond the capabilities of the a device like
> this is beyond me.  The CPE generated the keys.  It signs the
> records.  It updates the parent zone to add DS records for the keys
> it has generated.
>=20

The device can sign if it has accurate time,=20
it can generate keys if it has good source of randomness.=20
It can be relied upon if the zone survives reboots.=20

> The owner of the CPE has to do nothing to make this happen.

There is no harm in signing when there is no DS=20
it is real bad to sign with a new key when there is a DS in place,=20
the same goes for not signing when there is a DS but the errors will be =
different,=20

If the ISP/third party is signing the zones then they can handle the DS =
management and it is easier to=20
roll the devices.=20

> Either sign all version or don't sign any.
>=20
> I will appeal any version that even hints that mixed signing is the
> way to go.  It is just bad design, bad engineer and will cause pain
> for everyone.
>=20

The question is what is the "least bad design the can be deployed" along =
with the question
"is there one fits all solution?"=20

	Olafur=20


>> Best regards,
>>=20
>> A
>>=20
>> --=20
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Mar  5 03:58:06 2014
Return-Path: <v6ops@globis.net>
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 164111A042F for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 ebGR0d7nCjDl for <homenet@ietfa.amsl.com>; Wed,  5 Mar 2014 03:58:04 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCD31A0424 for <homenet@ietf.org>; Wed,  5 Mar 2014 03:58:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 73383871499; Wed,  5 Mar 2014 12:57:59 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gw49NTOliyzl; Wed,  5 Mar 2014 12:57:59 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 53F1387007E; Wed,  5 Mar 2014 12:57:59 +0100 (CET)
Message-ID: <53171146.8000806@globis.net>
Date: Wed, 05 Mar 2014 12:57:58 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <20140304100021.2718110AD645@rock.dv.isc.org> <48F0CF63-2595-43CD-884D-0C764CD5913E@fl1ger.de> <20140304105217.GD8224@mx1.yitter.info> <6.2.5.6.2.20140304043321.0c893400@resistor.net> <20140304234206.GC9166@mx1.yitter.info> <20140305051221.49EF410B2648@rock.dv.isc.org> <24056.1394010938@sandelman.ca> <20140305095823.06E1610BC47D@rock.dv.isc.org> <20140305102536.GD9266@mx1.yitter.info> <20140305110159.4A4D410BCBF1@rock.dv.isc.org>
In-Reply-To: <20140305110159.4A4D410BCBF1@rock.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/M9kWb45mRry-tyoLpPQtgcrsLAU
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] DNSSEC and homenet
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: Wed, 05 Mar 2014 11:58:05 -0000

Mark Andrews wrote:
> In message<20140305102536.GD9266@mx1.yitter.info>, Andrew Sullivan writes:
>> Mark,
>>
>> On Wed, Mar 05, 2014 at 08:58:23PM +1100, Mark Andrews wrote:
>>> a bit of flip flop but most of the time one is just "On WiFi" at home or
>> The point is that we're designing a protocol, and "most of the time"
>> won't be good enough to avoid support calls to the ISP help desk.  ISP
>> margins are thin enough that it would be a bad thing to build a
>> specification that encourages that even rarely.
>
> This is a problem that is INDEPENDENT of DNSSEC when you are siging both
> zones.   This is about there being two versions of the zone.
>
>>> I really don't see this as being a issue in practice.  Just sign
>>> the zone (all verisons) in the house with the same keys.  Stop with
>>> this nonsence idea that you shouldn't sign the internal version
>>> when you are signing the external version.
>> Mark, you're at least jumping ahead to implementation and at worst
>> begging the question.  We started with a proposal that did signing in
>> the ISP's server.  I was pointing out the consequences of that for
>> DNSSEC.  One of the possible solutions is that the "internal version"
>> is unsigned.  It would be careless not to list that as one of the
>> possibilities, even if I think that's a foolish outcome.  We have to
>> list the possibilities we don't like, too, or else we won't have a
>> clear picture of what we're talking about.
>
> Signed and unsigned versions of the same zones are a REALLY REALLY
> REALLY REALLY bad idea.
+1
>   This is a "Doctor it hurts if I do this.
> Then don't do this." example. It could be made to work with negative
> trust anchors which are installed when the WiFi SSID matches the
> home's SSID but we really don't want to go there.  There be dragons.
>
> It is dead simple for nameserver in the CPE to do the signing.  Why
> people thing it is beyond the capabilities of the a device like
> this is beyond me.  The CPE generated the keys.  It signs the
> records.  It updates the parent zone to add DS records for the keys
> it has generated.
>
> The owner of the CPE has to do nothing to make this happen.
>
> Either sign all version or don't sign any.
+1
> I will appeal any version that even hints that mixed signing is the
> way to go.  It is just bad design, bad engineer and will cause pain
> for everyone.
>
>> Best regards,
>>
>> A
>>
>> -- 
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet

-- 
Regards,
RayH


From nobody Mon Mar 24 04:33:15 2014
Return-Path: <Ray.Bellis@nominet.org.uk>
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 2D6BA1A01CF for <homenet@ietfa.amsl.com>; Mon, 24 Mar 2014 04:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.909
X-Spam-Level: 
X-Spam-Status: No, score=-2.909 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 01WuB4dgXGQ7 for <homenet@ietfa.amsl.com>; Mon, 24 Mar 2014 04:33:12 -0700 (PDT)
Received: from mx1.nominet.org.uk (mail.nominet.org.uk [213.248.242.48]) by ietfa.amsl.com (Postfix) with ESMTP id A2DC91A01CD for <homenet@ietf.org>; Mon, 24 Mar 2014 04:33:11 -0700 (PDT)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To: Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: MIME-Version; b=oJsG4xlcgtWQPD3vrtRBbEzPoh5hS0nxEJafmj3dcRG4ReHzLPuVOWlf mHX2WwIljDl0bi8vVP+5YipPtJLERWLQqbjwl/nzSp1gC0wqVT6A3bQRr JvdFrTXw5QRX8ck5ZD4quYFNTO1O/elTjecMe0FO5GDI80yh2X3YqrlzR 0F/Nkt04Qkbr+4xpM+0qCrRgmBt4EDd5dVa1yZcXqr/G2OCYGmY4Wr4Qm L1881xWCR1cTk+tCuClU6IN7xSQlp;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1395660791; x=1427196791; h=from:to:subject:date:message-id:mime-version; bh=WtTWVPassQGzAZoBtd7i0bbmoU5T81/Z3MuAh06JRbM=; b=fYuerUDgxN68nAMk6WpG+cYfHcFSg1VE/elSfl5JQifq7RC681hW7Djz sIgR0pZhPfK5+vbMs6uIH+gSNuDxb/WBe5vgmLV3byQ8oMb1+Njtm18we Mv//9MBePnyjU/Wmu7Ph7w8Lt31FtWZtjtmakdCziGmK60YS7FMVkKi0Q Xt5lkSQ6qAz/nY/wF9jEnDXEMdcm2arkYocpyNpvX5S1oGEtGHDzfhMCr tYBNXu/NQMG4/YsTs8y1lyIOac/cd;
X-IronPort-AV: E=Sophos;i="4.97,720,1389744000"; d="scan'208,217";a="8630332"
X-IPAS-Result: AuoMANMWMFPV+MWR/2dsb2JhbABZgmUhATo0CxiFaLQhgRYVBIhPFnSCHBBTOAELAXQnBByHcQMJnEmxLBeOJoMJD2eBFASqe4FAgW2CKw
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx1.nominet.org.uk with ESMTP; 24 Mar 2014 11:33:09 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.03.0123.003; Mon, 24 Mar 2014 11:33:09 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: IETF89 session notes
Thread-Index: AQHPR1TUHetBd5v3WkWAlH8ZCUKI+A==
Date: Mon, 24 Mar 2014 11:33:08 +0000
Message-ID: <4700D4CE-FA82-4F21-A0FB-33D5A1A5AC0D@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: multipart/alternative; boundary="_000_4700D4CEFA824F21A0FB33D5A1A5AC0Dnominetorguk_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/l6tRuTpfzRzrM9sYcip5Wqg2vtc
Subject: [homenet] IETF89 session notes
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, 24 Mar 2014 11:33:14 -0000

--_000_4700D4CEFA824F21A0FB33D5A1A5AC0Dnominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

With thanks as usual to Thomas Heide Clausen, the notes and transcript of t=
he Homenet session at IETF89 in London are now online at <http://www.ietf.o=
rg/proceedings/89/minutes/minutes-89-homenet>

If you are able to fill in any of the blanks, or have any other corrections=
, please let me know by Monday 31st March.

thanks,

Ray


--_000_4700D4CEFA824F21A0FB33D5A1A5AC0Dnominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <867C3CB7C18D0A45BB422E7E1F92F868@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
With thanks as usual to Thomas Heide Clausen, the notes and transcript of t=
he Homenet session at IETF89 in London are now online at &lt;<a href=3D"htt=
p://www.ietf.org/proceedings/89/minutes/minutes-89-homenet">http://www.ietf=
.org/proceedings/89/minutes/minutes-89-homenet</a>&gt;
<div><br>
</div>
<div>If you are able to fill in any of the blanks, or have any other correc=
tions, please let me know by Monday 31st March.</div>
<div><br>
</div>
<div>thanks,</div>
<div><br>
</div>
<div>Ray</div>
<div><br>
</div>
</body>
</html>

--_000_4700D4CEFA824F21A0FB33D5A1A5AC0Dnominetorguk_--


From nobody Mon Mar 24 15:30:32 2014
Return-Path: <dave.taht@gmail.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 DBEDB1A02AE for <homenet@ietfa.amsl.com>; Mon, 24 Mar 2014 15:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 A2xIAtadyijr for <homenet@ietfa.amsl.com>; Mon, 24 Mar 2014 15:30:29 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 264311A02A2 for <homenet@ietf.org>; Mon, 24 Mar 2014 15:30:28 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so3968891wgh.16 for <homenet@ietf.org>; Mon, 24 Mar 2014 15:30:27 -0700 (PDT)
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=crIXz4jwxKno/Qlsc8bZUa56HUeo0/bCDL9Vg2gfLHQ=; b=TzmhTI4v1dKzSO2JEHwhl6RHj4z7hBgmatKiJAoRpsh2R4qneWkCCs7C0LhKrYexxE 9L4TdDHITtnmhDxskUZMz92fou5XkoddwuKJtd5qaDmns51GqspzQsuU+qum8KbL5Sp4 9qSJlJ5mEyBhNZLXALMFqffN3Kx50AzjsrFhWu3QyseTDMPs08qbo/onZOgNvlA3HxXk fBtIaAoQxm/DI0XdBoarDSRMdT6wB8BdHaHjVNSzBSayuV7ceBhFl3iMnJd2pppnw5Xb IGKrqRd6wlA2f2dsqrnf8pQ3Z5VCAFaiST3qnqg4wRO6GD5UQpJ2j8ezEUeYa42jFTYZ rXvA==
MIME-Version: 1.0
X-Received: by 10.180.36.226 with SMTP id t2mr3273974wij.37.1395700227469; Mon, 24 Mar 2014 15:30:27 -0700 (PDT)
Received: by 10.216.8.1 with HTTP; Mon, 24 Mar 2014 15:30:27 -0700 (PDT)
Date: Mon, 24 Mar 2014 15:30:27 -0700
Message-ID: <CAA93jw7DVi7CNNsjB6DkCm4jM4OAHQrP89iXeU9wnq90KgQ+nw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>, HOMENET <homenet@ietf.org>,  bloat <bloat@lists.bufferbloat.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/VciATWEzciNAwP7bGcGv404s9Dw
Subject: [homenet] mesh networking @ google
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, 24 Mar 2014 22:30:31 -0000

This is a very speculative article

http://www.eweek.com/cloud/why-google-is-working-on-home-mesh-networking.ht=
ml

and I can quite honestly say I have no clue what's up. 802.11s?
6lopan? ad-hoc with some sort of networking protocol? RPL? what? Guess
I'll have to wait with everyone else...


--=20
Dave T=E4ht


From nobody Tue Mar 25 03:07:43 2014
Return-Path: <Ray.Bellis@nominet.org.uk>
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 4B5CC1A039A for <homenet@ietfa.amsl.com>; Tue, 25 Mar 2014 03:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 x79AgtUVEG5B for <homenet@ietfa.amsl.com>; Tue, 25 Mar 2014 03:07:05 -0700 (PDT)
Received: from mx1.nominet.org.uk (mx1.nominet.org.uk [213.248.242.48]) by ietfa.amsl.com (Postfix) with ESMTP id E05ED1A036B for <homenet@ietf.org>; Tue, 25 Mar 2014 03:07:03 -0700 (PDT)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To: Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=ioxim9lK52EY5S6/DTZsJ09aEsUwYe3dX6lhIiBq8T98EPDyPRyxGSxo BB+S8hVXJnU3wWXe4m7Cjn9aA4Ij4TF/zOwYKZMiW/jOQztF+7pJSQgkA g1dRVN705c/PhLohuK0dM46WqLYZAObewzW+e3ftpdJ3xZz6FD65rmG7e guFjaoQGibwsbmnqOhPpVyCOKvsNq4ewmxErRlutgo2LM6Ahl7PNb8qft fXAfRvSfw+x1jL14ErESN1MHt0hDJ;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1395742024; x=1427278024; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=pzSocdeNrj3qyf8CZO0AbLCBkHjhD11aiLU5ETcUu3g=; b=lHxht4EnprxAYEmdanqm44aqt/VdQg+tLXOMMllEbXDXCgBXo6HujwkD To/lJ1GCzkcg/LBF/kOb4SeeWgIvcXXxt9Ipgzly9cRy02h2KHSb5FNxY qvW3Etb2kZg8X+glFrjB+9WHTrFEs5lSjfRTphnYLBkPDoxm2AJ+JN8ge dhAv6JcyvHA+BclRS5SPCtHg0uOx72h0ZtGIxbHV5rH47WViHf7Uay52W RR3QO1QEqpkGbtTUiTbPsRg07s3CY;
X-IronPort-AV: E=Sophos;i="4.97,728,1389744000";  d="scan'208";a="8643930"
X-IPAS-Result: AiMFAGtUMVPV+MWR/2dsb2JhbABZgmUhAXkYuy+IWhZ0giwdHRk4AT5CJwSIDQOdILFgF44Vg3+BFASqf4Mtgis
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx1.nominet.org.uk with ESMTP; 25 Mar 2014 10:07:01 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.03.0123.003; Tue, 25 Mar 2014 10:07:01 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: WG adoption of draft-stenberg-homenet-hncp-00
Thread-Index: AQHPSBH2sAibSti7AUO5/uF/+E9TuQ==
Date: Tue, 25 Mar 2014 10:07:00 +0000
Message-ID: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <210665E7FB9ACB47B8CDC27CD399EFE4@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/HisjtylEIsxISxyBY9lignKj-ss
Subject: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Tue, 25 Mar 2014 10:07:07 -0000

At IETF 89 in London we took three hums:

1. On use of OSPF vs HNCP for configuration - strong consensus for HNCP

2. On how many routing protocols we should support in Homenet -
  strong consensus that it should be zero or one, but no consensus yet
  on which.

3. On adoption of HNCP as a WG item - good consensus for, a few undecided,
  none against.

On this basis the Chairs wish to proceed with the formal call for adoption =
of draft-stenberg-homenet-hncp-00, with a two week response window.

Please therefore send your comments on adoption of this draft to the list b=
efore 23:59 UTC on Tuesday 1st April.

thanks,

Ray and Mark=


From nobody Wed Mar 26 13:58:00 2014
Return-Path: <v6ops@globis.net>
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 79C9A1A03CB for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 13:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 7bblYPRFujvc for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 13:57:57 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8821A03C6 for <homenet@ietf.org>; Wed, 26 Mar 2014 13:57:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 577CB870073; Wed, 26 Mar 2014 21:57:55 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLAN6J5UQWHt; Wed, 26 Mar 2014 21:57:55 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 2FD6C87005E; Wed, 26 Mar 2014 21:57:55 +0100 (CET)
Message-ID: <53333F51.5030106@globis.net>
Date: Wed, 26 Mar 2014 21:57:53 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
In-Reply-To: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/ZU7MFPrVl5hfmnoIE9TZ8DWpWwc
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Wed, 26 Mar 2014 20:57:58 -0000

Support adoption of HNCP as a WG item.

I am interested to read more information on how Homenet would/could work 
with zero routing protocol.

I presumed exactly one common Homenet interworking routing protocol.

Ray Bellis wrote:
> At IETF 89 in London we took three hums:
>
> 1. On use of OSPF vs HNCP for configuration - strong consensus for HNCP
>
> 2. On how many routing protocols we should support in Homenet -
>    strong consensus that it should be zero or one, but no consensus yet
>    on which.
>
> 3. On adoption of HNCP as a WG item - good consensus for, a few undecided,
>    none against.
>
> On this basis the Chairs wish to proceed with the formal call for adoption of draft-stenberg-homenet-hncp-00, with a two week response window.
>
> Please therefore send your comments on adoption of this draft to the list before 23:59 UTC on Tuesday 1st April.
>
> thanks,
>
> Ray and Mark
>

-- 
Regards,
RayH


From nobody Wed Mar 26 14:30:35 2014
Return-Path: <mcr@sandelman.ca>
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 D6F201A03C0 for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 14:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] 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 eH65OXp0PsvK for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 14:30:32 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 0969F1A0253 for <homenet@ietf.org>; Wed, 26 Mar 2014 14:30:31 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7D3F320091 for <homenet@ietf.org>; Wed, 26 Mar 2014 18:50:18 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 7D77163ABA; Wed, 26 Mar 2014 17:30:29 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 678EF63AA2 for <homenet@ietf.org>; Wed, 26 Mar 2014 17:30:29 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <53333F51.5030106@globis.net>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 26 Mar 2014 17:30:29 -0400
Message-ID: <25769.1395869429@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/ZubRcCOAitxYf9pcPGSnb_OkdgQ
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Wed, 26 Mar 2014 21:30:34 -0000

--=-=-=


I have read the HNCP draft, and while it is very rough, and lacks greatly in
the area of "how", being focused on the "what", I am happy with the WG
adopting it, and then improving it.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUzNG9YqHRg3pndX9AQJYZQQAl/8QIl4RzqbxYevH+VFkaaSk/kB/1GYM
hUUG4DXCTVooxECbfsQMPkduIdO2fWcYlNOD+uqowswLrYX00OzBT8K9HGJqz5G9
DiatOh9bc+8Q90d9XWNoSJdQaLNVvBO/lPocRl71sJYi0F/AYJfplzcqNMWwlsqr
hNhjAlGUxKI=
=5sBL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Mar 26 23:03:21 2014
Return-Path: <swmike@swm.pp.se>
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 51E271A0468 for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 23:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 t1PgMFuTDta0 for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 23:03:16 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id A1D031A0462 for <homenet@ietf.org>; Wed, 26 Mar 2014 23:03:16 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9AA6AA9; Thu, 27 Mar 2014 07:03:13 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9788DA8 for <homenet@ietf.org>; Thu, 27 Mar 2014 07:03:13 +0100 (CET)
Date: Thu, 27 Mar 2014 07:03:13 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <25769.1395869429@sandelman.ca>
Message-ID: <alpine.DEB.2.02.1403270700450.747@uplift.swm.pp.se>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <25769.1395869429@sandelman.ca>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/UoOIwnAG8cRF9gNpU_AZA-ygiO4
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 06:03:18 -0000

On Wed, 26 Mar 2014, Michael Richardson wrote:

>
> I have read the HNCP draft, and while it is very rough, and lacks greatly in
> the area of "how", being focused on the "what", I am happy with the WG
> adopting it, and then improving it.

I agree. The mechanisms described in the HNCP documents seem good to me, 
I am not at all sure that the HNCP protocol as it stands right now is the 
best way to communicate the information the mechanisms need in order to do 
their job, but this is the kind of work the WG needs to do.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed Mar 26 23:04:23 2014
Return-Path: <swmike@swm.pp.se>
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 CD64C1A0464 for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 23:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.861
X-Spam-Level: 
X-Spam-Status: No, score=-3.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 YGgQU5s0X-q3 for <homenet@ietfa.amsl.com>; Wed, 26 Mar 2014 23:04:17 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 73BED1A0462 for <homenet@ietf.org>; Wed, 26 Mar 2014 23:04:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7D78AA5; Thu, 27 Mar 2014 07:04:15 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 75281A3; Thu, 27 Mar 2014 07:04:15 +0100 (CET)
Date: Thu, 27 Mar 2014 07:04:15 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <53333F51.5030106@globis.net>
Message-ID: <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/WVLE9N2BvqfkDDqtYgn_30wwtmg
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 06:04:20 -0000

On Wed, 26 Mar 2014, Ray Hunter wrote:

> Support adoption of HNCP as a WG item.
>
> I am interested to read more information on how Homenet would/could work with 
> zero routing protocol.
>
> I presumed exactly one common Homenet interworking routing protocol.

HNCP as it stands right now has a "routing protocol" of it's own that is 
extremely rudimentary, but it gets the job done. I think this is what is 
referred to as "zero routing protcol" because people don't really want to 
call it a routing protocol (my interpretation).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Mar 27 00:08:09 2014
Return-Path: <swmike@swm.pp.se>
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 21B801A0471 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.861
X-Spam-Level: 
X-Spam-Status: No, score=-3.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 eA6q0vQjoWl7 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:08:00 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 9722E1A047A for <homenet@ietf.org>; Thu, 27 Mar 2014 00:08:00 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 47753A5; Thu, 27 Mar 2014 08:07:58 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 40090A3; Thu, 27 Mar 2014 08:07:58 +0100 (CET)
Date: Thu, 27 Mar 2014 08:07:58 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <15409.1394017764@sandelman.ca>
Message-ID: <alpine.DEB.2.02.1403270804520.747@uplift.swm.pp.se>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr> <15409.1394017764@sandelman.ca>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1417572279-1395904078=:747"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/jU7TJjjExviWgz_72XiKAQjQvcs
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HCNP: my points this morning
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: Thu, 27 Mar 2014 07:08:04 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-1417572279-1395904078=:747
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 5 Mar 2014, Michael Richardson wrote:

>    > - Homenet-hncp intends to be incremental in terms of TLVs. Other TLVs
>    > will come, and, if hncp is widely used in homes, vendor-specific
>    > options will come as well. So I think â€˜ignore TLVs you donâ€™t knowâ€™ is
>    > the correct behavior.  Nevertheless, I understand hncp could be used
>
> We actually need a "critical" bit on the Type value then.

Or some kind of "feature election" within the home? Just the way HNCP now 
has a kind of voting system for which IGP to choose (which might go away 
since we only want a single IGP), perhaps we need a mechanism to choose if 
a feature is used within the home or not. This would only apply to some 
features that actually need the entire home to support the feature for it 
to work correctly.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-1417572279-1395904078=:747--


From nobody Thu Mar 27 00:19:59 2014
Return-Path: <v6ops@globis.net>
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 DEFBE1A047B for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 PxVywCiJx8iT for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:19:55 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0E01A0464 for <homenet@ietf.org>; Thu, 27 Mar 2014 00:19:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 46435870073; Thu, 27 Mar 2014 08:19:53 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aB7kSsonorcm; Thu, 27 Mar 2014 08:19:53 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 2863B870061; Thu, 27 Mar 2014 08:19:53 +0100 (CET)
Message-ID: <5333D118.60404@globis.net>
Date: Thu, 27 Mar 2014 08:19:52 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/w7GDpd_rgQhLmZtan6MwfPFrlSI
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 07:19:57 -0000

> Mikael Abrahamsson <mailto:swmike@swm.pp.se>
> 27 March 2014 07:04
> On Wed, 26 Mar 2014, Ray Hunter wrote:
>
>
> HNCP as it stands right now has a "routing protocol" of it's own that 
> is extremely rudimentary, but it gets the job done. I think this is 
> what is referred to as "zero routing protcol" because people don't 
> really want to call it a routing protocol (my interpretation).
>
>
Right, but the way I see it:

If you have an arbitrary topology then you probably need to carry 
metrics to prefer one link type over another.
If you want to be able to determine which prefixes to delete from the 
FIB and RA when a particular upstream provider link goes down, you 
probably need some sort of tagging.
If you want fast convergence around failures you probably need a decent 
path discovery algorithm.
If you want to differentiate between a temporary change (due to an 
incident or link failure) and a longer term permanent change (due to 
replugging or device insertion or removal) then you probably need two 
different sets of timers and problem diagnostics.

In other words; we definitely need a routing protocol, and probably a 
configuration protocol too.

So isn't the danger than HNCP starts off being very simple, and ends up 
duplicating a lot of previous work and experience?

I'm interested to hear the contrarian view.

-- 
Regards,
RayH


From SRS0=iWy7=Y4=darou.fr=pierre.pfister@bounces.m4x.org  Thu Mar 27 00:50:14 2014
Return-Path: <SRS0=iWy7=Y4=darou.fr=pierre.pfister@bounces.m4x.org>
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 C736C1A02A3 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, 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 XRwLkDdqj74V for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 00:50:11 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) by ietfa.amsl.com (Postfix) with ESMTP id A21DA1A0383 for <homenet@ietf.org>; Thu, 27 Mar 2014 00:50:10 -0700 (PDT)
Received: from [10.148.10.24] (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 437C11408EEE1; Thu, 27 Mar 2014 08:50:06 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <5333D118.60404@globis.net>
Date: Thu, 27 Mar 2014 08:50:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0DA30F4-4954-4CED-AEC1-D5751981F815@darou.fr>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1874)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Mar 27 08:50:06 2014 +0100 (CET))
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/yzHqo79LB27EtWukXsszgvAzImc
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 07:52:03 -0000

Le 27 mars 2014 =E0 08:19, Ray Hunter <v6ops@globis.net> a =E9crit :

>> Mikael Abrahamsson <mailto:swmike@swm.pp.se>
>> 27 March 2014 07:04
>> On Wed, 26 Mar 2014, Ray Hunter wrote:
>>=20
>>=20
>> HNCP as it stands right now has a "routing protocol" of it's own that =
is extremely rudimentary, but it gets the job done. I think this is what =
is referred to as "zero routing protcol" because people don't really =
want to call it a routing protocol (my interpretation).
>>=20
>>=20

That is my understanding of the "zero routing protocol =BB too.

> Right, but the way I see it:
>=20
> If you have an arbitrary topology then you probably need to carry =
metrics to prefer one link type over another.
> If you want to be able to determine which prefixes to delete from the =
FIB and RA when a particular upstream provider link goes down, you =
probably need some sort of tagging.
> If you want fast convergence around failures you probably need a =
decent path discovery algorithm.
> If you want to differentiate between a temporary change (due to an =
incident or link failure) and a longer term permanent change (due to =
replugging or device insertion or removal) then you probably need two =
different sets of timers and problem diagnostics.
>=20
> In other words; we definitely need a routing protocol, and probably a =
configuration protocol too.
>=20
> So isn't the danger than HNCP starts off being very simple, and ends =
up duplicating a lot of previous work and experience?
>=20
> I'm interested to hear the contrarian view.

Except the second point (determine which prefix to delete=85), which is =
done by the prefix assignment algorithm on top of HNCP, all other points =
will have to be answered to decide which routing protocol to use. The =
current draft doesn=92t intend to answer the routing protocol issue. It =
was not left blank for the simple reason we  needed to implement it and =
make it run.

I dont think we want to run a complex routing protocol in HNCP. It=92s =
more like either we want to make something very simple, and we use HNCP =
for this, or we want all what you said, and we use another existing =
protocol. The point of the draft is just to let you know that it is =
*possible* to route packets, in a very simple way, by using just HNCP as =
it is, with no extra information.

Regards,
Pierre

>=20
> --=20
> Regards,
> RayH
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Mar 27 01:30:08 2014
Return-Path: <otroan@employees.org>
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 4D0611A04A6 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 01:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 37lEtrc-3HE2 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 01:30:03 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2FA1A049F for <homenet@ietf.org>; Thu, 27 Mar 2014 01:30:03 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id BCB6A609D; Thu, 27 Mar 2014 01:30:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=selector1; bh=oFPERYWHiM3vNbylQhSsA PY1a9M=; b=TGoCeIcL/ohh3qzmAXobilS3dinPPlEulv0dEoob2jxQ4qprchfw7 JGqO9YPJ18ZXDNt1opCRKjJfR6v0Z3w3dAr2lpMoxQw9gJhoFkYR5qwaAHe64Q/S z/5MeGhT4y8QimXrcG8rkqc/DyNjUrcmU79iiuoX/LWuuuereD7KRc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; q=dns; s=selector1; b=CjSMzm4Ygh77Vhn XV1n5e5fZf0tsbrQGryCYnhdAXOJod0Czo5H5HUTPgcId+HFmRrjjPki5zJ0Gnj6 XsbkugleibIRVKtv9s6Zv5Sloo5TfDY6NNnaQ79crDI7GYNmXbfbtscCArirCT1M XoDx6UEJ4JgMrQa2yfKe5unkhIno=
Received: from dhcp-lys01-vla250-10-147-112-211.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5D6E46065; Thu, 27 Mar 2014 01:29:58 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_66C7515D-C9B3-46B7-A5F2-5D5C1733AF43"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Date: Thu, 27 Mar 2014 09:29:56 +0100
Message-Id: <5D4502F4-267A-4ED2-99A8-479FDCB03293@employees.org>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/_3ZFje3K8paPj5X-mXnlFyKKP6A
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 08:30:06 -0000

--Apple-Mail=_66C7515D-C9B3-46B7-A5F2-5D5C1733AF43
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> At IETF 89 in London we took three hums:
>=20
> 1. On use of OSPF vs HNCP for configuration - strong consensus for =
HNCP
>=20
> 2. On how many routing protocols we should support in Homenet -
>  strong consensus that it should be zero or one, but no consensus yet
>  on which.
>=20
> 3. On adoption of HNCP as a WG item - good consensus for, a few =
undecided,
>  none against.
>=20
> On this basis the Chairs wish to proceed with the formal call for =
adoption of draft-stenberg-homenet-hncp-00, with a two week response =
window.
>=20

I'm in favour of adopting this document, with the premise that HNCP is =
not going to be yet another routing protocol.
that is restricted to bootstrapping / configuring the home network.

cheers,
Ole

--Apple-Mail=_66C7515D-C9B3-46B7-A5F2-5D5C1733AF43
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTM+GEAAoJEFuJXizso86gG+MH/1Lje2HhTWmHwbnmEjtF6f9L
WjVM9BbdBckGukizkCxuGKVtGq4BjSrIa30nT1qKE6Od1ipyXtW8WCrBNi5nUSxZ
OEMlheV6Z0tWAwej8FvtB2RUG7qca57t7a5icHM8v1qFP+Am4vvWQD6mr9CAlr4e
M8WGTqKvYARAZiuCjI0ie4eiIvawkXTttrmmfQl2CSox3fEHBaGnJYoRK3iorTuN
Hz21j6E9YIrsG8BRyNFGqPB4PLF15UPoI0WZc7Z4xPBFYZgscrntgkut2dj7ZNOa
40wmcDh+EsZJdj1ZuHDIIccGveSf3s0BZOB+s7McgDXLUR65ogdqQMiGiu9dtnY=
=4/iF
-----END PGP SIGNATURE-----

--Apple-Mail=_66C7515D-C9B3-46B7-A5F2-5D5C1733AF43--


From nobody Thu Mar 27 05:34:32 2014
Return-Path: <mellon@fugue.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 AAD371A066D for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 05:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 2TyQaasUSJXq for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 05:34:29 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BBD831A066A for <homenet@ietf.org>; Thu, 27 Mar 2014 05:34:29 -0700 (PDT)
Received: from [172.16.0.56] (rrcs-67-78-65-202.sw.biz.rr.com [67.78.65.202]) by toccata.fugue.com (Postfix) with ESMTPSA id DAF512381509; Thu, 27 Mar 2014 08:34:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <5333D118.60404@globis.net>
Date: Thu, 27 Mar 2014 07:34:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C82BDDF-4E09-4536-9EF8-99EC4258E497@fugue.com>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/BN6hkTIx6BnXG4dROWSqPo4eGps
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 12:34:30 -0000

On Mar 27, 2014, at 2:19 AM, Ray Hunter <v6ops@globis.net> wrote:
> So isn't the danger than HNCP starts off being very simple, and ends =
up duplicating a lot of previous work and experience?

If the working group submits HNCP for publication and it's morphed into =
a full-blown routing protocol, I will send it back (assuming I'm still =
AD at that point, and also in the unlikely event that I didn't intervene =
when someone proposed adding the ful-blown routing stuff).   I don't =
think anybody intends for this to happen, and if it does happen it will =
prevent the spec getting published, so I think we're pretty safe... :)


From nobody Thu Mar 27 06:03:16 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 838961A06D8 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.45
X-Spam-Level: 
X-Spam-Status: No, score=0.45 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35, J_CHICKENPOX_47=0.6] autolearn=no
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 nF0VbZylHWtz for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:03:12 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id C6B2E1A06D1 for <homenet@ietf.org>; Thu, 27 Mar 2014 06:03:11 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id s2RD38Pl017323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 27 Mar 2014 14:03:08 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id s2RD38gX023615; Thu, 27 Mar 2014 14:03:08 +0100
Received: from mailhub.admin.local (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1540E2B72C8; Thu, 27 Mar 2014 14:03:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.admin.local (mailhub.admin.local [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id aHnTSykBz-Sy; Thu, 27 Mar 2014 14:03:07 +0100 (CET)
Received: from ijon.pps.jussieu.fr (dra38-1-82-225-44-56.fbx.proxad.net [82.225.44.56]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id D6F8A2B72C6; Thu, 27 Mar 2014 14:03:06 +0100 (CET)
Date: Thu, 27 Mar 2014 14:03:05 +0100
Message-ID: <87y4zvg5fa.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <5333D118.60404@globis.net>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 27 Mar 2014 14:03:08 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 27 Mar 2014 14:03:08 +0100 (CET)
X-Miltered: at korolev with ID 5334218C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5334218C.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5334218C.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5334218C.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5334218C.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5334218C.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/9JRXJuqmFYmRsfiljZ_o7EwE3Fc
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 13:03:13 -0000

> So isn't the danger than HNCP starts off being very simple, and ends
> up duplicating a lot of previous work and experience?

I agree, and I'd like to put that in stronger terms.

Homenet has just avoided committing suicide by not requiring an
unimplementable, undebuggable monster of an OSPF+configuration
protocol.

Are we now going to require an unimplementable, undebuggable monster
of an HCNP+routing protocol?

-- Juliusz




From nobody Thu Mar 27 06:11:15 2014
Return-Path: <Ray.Bellis@nominet.org.uk>
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 C58061A06E5 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.71
X-Spam-Level: 
X-Spam-Status: No, score=-3.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_47=0.6, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 xNfzJA_ZJWDK for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:11:11 -0700 (PDT)
Received: from mx2.nominet.org.uk (mx2.nominet.org.uk [213.248.242.49]) by ietfa.amsl.com (Postfix) with ESMTP id D7E461A06CB for <homenet@ietf.org>; Thu, 27 Mar 2014 06:11:10 -0700 (PDT)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To:CC: Subject:Thread-Topic:Thread-Index:Date:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=ZvqgoGXVKFhT9p5UDk1IwyX1ZTeDcWItoEbmIqbt+aLHWTuXPoJ04nk3 xnkAcKXOr1tuzFfwt/AQZe6q8M2vxT+OPHrQPJdFffa2t9Ri/w5Uo8kOj XbgisjbhSTXdi589UQPD7gbqrBRYoCdu7aAhBzcjoGnAgozrLPGdGattK NxUy9jZxGCov26kNe1OoOP+vNpROQavGJggDD1tpL0wmb//EF+pIgcFvB rC3wlHLmYohVbZI1gId5XM19/rvJO;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1395925869; x=1427461869; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5NgH0RNZIVZT9rhlw5rmVbde6HLC08wWU45GorxVFzU=; b=E5CkT+VX7o/6owBhm2v0FjK+EELBiVLcFc3H8+LnqKt0BmtbLOKtPx1y WtDmCiGAoqLhS2N34G0qfClQ1Lxlvodg0mjOGd6toG2EGpVb9ZptJU9zQ FOcNTWgKjg2g4LMB+oO+4b1eMP5og3VOeRdYJHKgAf8cUbFKX0rlo1neA fXB5xcOJVEkNj9HrywPg64l0HI1BfMwZdV/DIKOGj4HwjHOAlbv6yTIcJ bDZprtQzDKVVnKT8iJRklyGkqNfGH;
X-IronPort-AV: E=Sophos;i="4.97,742,1389744000";  d="scan'208";a="8054483"
X-IPAS-Result: AkEEAOsiNFPV+MWRdGdsb2JhbABZgmWBM8JfgRoWDgEMWYIlAQEBAQIBOhkmBQsCAQgOKBAyJQIEDgWHcQkD0HwXjkAzB4MkgRQEri+CKw
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx2.nominet.org.uk with ESMTP; 27 Mar 2014 13:10:46 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.03.0123.003; Thu, 27 Mar 2014 13:10:46 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
Thread-Index: AQHPSBH2sAibSti7AUO5/uF/+E9TuZrz2/iAgACYp4CAABUgAIAAX+WAgAACIwA=
Date: Thu, 27 Mar 2014 13:10:44 +0000
Message-ID: <3E3F8BD8-0A18-48CD-A9CC-E4FD2E61E98E@nominet.org.uk>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net> <87y4zvg5fa.wl%jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87y4zvg5fa.wl%jch@pps.univ-paris-diderot.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A703517A62769A4FAB27FE6B74CA2407@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/xrOSpRoVCaJEaJzkTCxfZ7UFtgQ
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 13:11:14 -0000

On 27 Mar 2014, at 13:03, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr=
> wrote:

> Homenet has just avoided committing suicide by not requiring an
> unimplementable, undebuggable monster of an OSPF+configuration
> protocol.
>=20
> Are we now going to require an unimplementable, undebuggable monster
> of an HCNP+routing protocol?

That is clearly not the plan.

Could we please reserve this thread for discussion around the _adoption_ of=
 this draft.  If you have thoughts about HNCP's specification and future im=
plementation, please start a new thread.

Ray


From nobody Thu Mar 27 06:15:23 2014
Return-Path: <tjw.ietf@gmail.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 D7F1F1A06D1 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 ExTv6PAqmoL1 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:15:20 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 726EA1A0055 for <homenet@ietf.org>; Thu, 27 Mar 2014 06:15:20 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id r5so4252008qcx.32 for <homenet@ietf.org>; Thu, 27 Mar 2014 06:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vIuCu0HIaYPbK4wuGhoF2S+boC1HdwqDkqAwUyheDao=; b=lXHANVEDDkBWrJlqn/gQd5INvbFvPOeAW7qVkUKGAR/aAPYneh31KMku/IuJdTDuEf 7wE8NKAUB5zvLZZAU7Pl2U4ucNN7nDKX9mp/oa1cXQLs9a7eUBy36H37re1ssp46VOK9 7aGD0nqNffcYgdLNqw5DpOainWnCPBHrmgyP+c8WUhD0VU/EOpzJY9PExFG6hCGFpVcm pj0DnVO06ZosePPVDF4NxK/orT6ikQRMkcTPyjrN3CzIOLxSPI1TLnPmAmrGRKlSDstF Gwb77DvgbSGCWwpL40hqDBnjFlsLSRxmMWCrK1F179QDnhH4OJQSJ366H8w0pqcIKts0 JGGg==
X-Received: by 10.140.85.230 with SMTP id n93mr1886068qgd.26.1395926118493; Thu, 27 Mar 2014 06:15:18 -0700 (PDT)
Received: from feather.local (184-19-89-148.drr03.clbg.wv.frontiernet.net. [184.19.89.148]) by mx.google.com with ESMTPSA id g92sm2641094qge.7.2014.03.27.06.15.13 for <homenet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Mar 2014 06:15:13 -0700 (PDT)
Message-ID: <53342461.80409@gmail.com>
Date: Thu, 27 Mar 2014 09:15:13 -0400
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Thunderbird/30.0a2
MIME-Version: 1.0
To: "homenet@ietf.org Group" <homenet@ietf.org>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <25769.1395869429@sandelman.ca>
In-Reply-To: <25769.1395869429@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/c2ol8WmZzMfYLtoHJUEouOOjnkc
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 13:15:22 -0000

On 3/26/14, 5:30 PM, Michael Richardson wrote:
> I have read the HNCP draft, and while it is very rough, and lacks greatly in
> the area of "how", being focused on the "what", I am happy with the WG
> adopting it, and then improving it.
>
>
After reading the draft again, I agree the WG should adopt this, with 
the knowledge the draft is rough and needs some iterations to make whole.



tim


From nobody Thu Mar 27 06:29:57 2014
Return-Path: <mcr@sandelman.ca>
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 591A01A00FD for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yYcCUhImBthB for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 06:29:53 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 612F81A00F8 for <homenet@ietf.org>; Thu, 27 Mar 2014 06:29:53 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id EC8F82002D; Thu, 27 Mar 2014 10:49:41 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 8895663ABA; Thu, 27 Mar 2014 09:29:50 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6DD1263AA2; Thu, 27 Mar 2014 09:29:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1403270804520.747@uplift.swm.pp.se>
References: <87eh2iui53.wl%jch@pps.univ-paris-diderot.fr> <E4F88E97-5659-4BE9-B083-6A3524D84847@darou.fr> <15409.1394017764@sandelman.ca> <alpine.DEB.2.02.1403270804520.747@uplift.swm.pp.se>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 27 Mar 2014 09:29:50 -0400
Message-ID: <28343.1395926990@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/PXf22Qdp4ieL8Ofe5wy9xDX_Cok
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HCNP: my points this morning
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: Thu, 27 Mar 2014 13:29:55 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Mikael Abrahamsson <swmike@swm.pp.se> wrote:
    >> > - Homenet-hncp intends to be incremental in terms of TLVs. Other
    >> TLVs > will come, and, if hncp is widely used in homes,
    >> vendor-specific > options will come as well. So I think =E2=80=98ign=
ore TLVs
    >> you don=E2=80=99t know=E2=80=99 is > the correct behavior.  Neverthe=
less, I understand
    >> hncp could be used
    >>
    >> We actually need a "critical" bit on the Type value then.

    > Or some kind of "feature election" within the home? Just the way HNCP
    > now has a kind of voting system for which IGP to choose (which might =
go

That's a higher level concept than understanding whether a particular tlv
can be decoded or not.

Or: I am not disagreeing with you, but saying it is an orthogonal issue.


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUzQny4qHRg3pndX9AQLWAQQAnby3m0PpLZEoniuTa24Yxgl8uXgDaELe
cbboBKZ0cad4fUyPPUkWMeizGRvzD18VomZKFpiuVULTUAv6lCAfzqYuw7z4oGOf
Z9tgWPUgdlC98mOERBqC6K7SF+yvOwHALEYUboYgnCbto4IHqaQBWyDOBU3E7Qhp
CXamtDaIyII=
=vTwW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar 27 11:37:04 2014
Return-Path: <v6ops@globis.net>
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 728531A0728 for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 JauxAlHJvGel for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:56 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id A53251A02AE for <homenet@ietf.org>; Thu, 27 Mar 2014 11:36:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 4E3F7870074; Thu, 27 Mar 2014 19:36:53 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIjbmT71oZdQ; Thu, 27 Mar 2014 19:36:53 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 2B9CB870070; Thu, 27 Mar 2014 19:36:53 +0100 (CET)
Message-ID: <53346FC4.7000705@globis.net>
Date: Thu, 27 Mar 2014 19:36:52 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net> <A0DA30F4-4954-4CED-AEC1-D5751981F815@darou.fr>
In-Reply-To: <A0DA30F4-4954-4CED-AEC1-D5751981F815@darou.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/2A-Bauy0o7ZIz6r-QWdAz3Kr3V0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 18:36:57 -0000

> Pierre Pfister <mailto:pierre.pfister@darou.fr>
> 27 March 2014 08:50
> Le 27 mars 2014 à 08:19, Ray Hunter<v6ops@globis.net>  a écrit :
>
>>> Mikael Abrahamsson<mailto:swmike@swm.pp.se>
>>> 27 March 2014 07:04
>>> On Wed, 26 Mar 2014, Ray Hunter wrote:
>>>
>>>
>>> HNCP as it stands right now has a "routing protocol" of it's own that is extremely rudimentary, but it gets the job done. I think this is what is referred to as "zero routing protcol" because people don't really want to call it a routing protocol (my interpretation).
>>>
>>>
>
> That is my understanding of the "zero routing protocol » too.
>
>> Right, but the way I see it:
>>
>> If you have an arbitrary topology then you probably need to carry metrics to prefer one link type over another.
>> If you want to be able to determine which prefixes to delete from the FIB and RA when a particular upstream provider link goes down, you probably need some sort of tagging.
>> If you want fast convergence around failures you probably need a decent path discovery algorithm.
>> If you want to differentiate between a temporary change (due to an incident or link failure) and a longer term permanent change (due to replugging or device insertion or removal) then you probably need two different sets of timers and problem diagnostics.
>>
>> In other words; we definitely need a routing protocol, and probably a configuration protocol too.
>>
>> So isn't the danger than HNCP starts off being very simple, and ends up duplicating a lot of previous work and experience?
>>
>> I'm interested to hear the contrarian view.
>
> Except the second point (determine which prefix to delete…), which is done by the prefix assignment algorithm on top of HNCP, all other points will have to be answered to decide which routing protocol to use. The current draft doesn’t intend to answer the routing protocol issue. It was not left blank for the simple reason we  needed to implement it and make it run.

I think that's still an open question "(determine which prefix to 
delete…)", and an interesting side effect of a decision to split routing 
and prefix assignment.

e.g. looking at 
http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-06 
section 5.2

and especially considering any end hosts that do not understand 
http://tools.ietf.org/html/draft-troan-homenet-sadr-00,

do you want RA to start or stop advertising a prefix (hat has been 
derived from an upstream neighbor) on a local interface as a candidate 
default routeto locally connected end systems because the path to that 
ISP is down (routing), or because of a configuration timeout (DHCPv6 PD 
+ HNCP), or both, or neither?

> I dont think we want to run a complex routing protocol in HNCP. It’s more like either we want to make something very simple, and we use HNCP for this, or we want all what you said, and we use another existing protocol. The point of the draft is just to let you know that it is *possible* to route packets, in a very simple way, by using just HNCP as it is, with no extra information.
>
> Regards,
> Pierre
>
>> -- 
>> Regards,
>> RayH
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
> ------------------------------------------------------------------------


-- 
Regards,
RayH


From nobody Thu Mar 27 11:49:10 2014
Return-Path: <dave.taht@gmail.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 95C4D1A06EE for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 11:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 ouudBg3Mp7Gb for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 11:49:04 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7C21A06F8 for <homenet@ietf.org>; Thu, 27 Mar 2014 11:49:01 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id bs8so3484264wib.17 for <homenet@ietf.org>; Thu, 27 Mar 2014 11:48:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=y/cbrAT+Rmx+hsZ9TDfim6bl9fq01xIQHeG5p74GCw0=; b=lU0NxoZ9kmY9pfBgz4aIrxAObi6JxBoil6ryKsE/2PKcEngqnpM2UZsU2YpkqC08Ef JISk+lw9ac+rF1GSFwEiak9IF42kpoCguRLrnoIK7Xv3KbvXi+XkCWv+eDfVcxmrHIrR dCBUAi/vJQCJY6Mm+1j65oR2eHF14sLtdTi4CAvTYQ6XTs55oyC5RDwaTq4F+VQbOOAq od5OUB9weQ6M01+moZgA4dX0If/n2mi8GXr9wWfMZ8EdHHkuEXFLd93A2YnspS/BiBT+ L7APkE3s1hIGb0GJosrg+qGXyeZAHGWdB4oQsir+JYMyo7gf0VfvxQWRX1CspaDZlvo6 tm9Q==
MIME-Version: 1.0
X-Received: by 10.180.77.200 with SMTP id u8mr7256334wiw.48.1395946139546; Thu, 27 Mar 2014 11:48:59 -0700 (PDT)
Received: by 10.216.8.1 with HTTP; Thu, 27 Mar 2014 11:48:59 -0700 (PDT)
In-Reply-To: <53342461.80409@gmail.com>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <25769.1395869429@sandelman.ca> <53342461.80409@gmail.com>
Date: Thu, 27 Mar 2014 11:48:59 -0700
Message-ID: <CAA93jw6kaQivFzQ-MZstb+Z_9nH+xMoQbOwW9rbJi5m0UTPm=w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/nSoB9fuUbH2JSnpGznJeoAcdXn4
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Thu, 27 Mar 2014 18:49:08 -0000

On Thu, Mar 27, 2014 at 6:15 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
> On 3/26/14, 5:30 PM, Michael Richardson wrote:
>>
>> I have read the HNCP draft, and while it is very rough, and lacks greatl=
y
>> in
>> the area of "how", being focused on the "what", I am happy with the WG
>> adopting it, and then improving it.
>>
>>
> After reading the draft again, I agree the WG should adopt this, with the
> knowledge the draft is rough and needs some iterations to make whole.

I agree the WG should adopt this, with the knowledge that the code is rough=
,
and needs some more people working on it so that the ideas can be fully exp=
lored
and  tested and then the draft made whole.

Code in progress is at:

https://github.com/sbyx/hnetd/

for anyone that cares to look/contribute.

>
>
>
> tim
>
>
> _______________________________________________
> 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


From nobody Fri Mar 28 00:56:04 2014
Return-Path: <swmike@swm.pp.se>
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 A2F041A0285 for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 00:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 VT_Mt2D-fVdn for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 00:56:01 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id D16071A012C for <homenet@ietf.org>; Fri, 28 Mar 2014 00:56:00 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D314EA6; Fri, 28 Mar 2014 08:55:57 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CB8A6A5; Fri, 28 Mar 2014 08:55:57 +0100 (CET)
Date: Fri, 28 Mar 2014 08:55:57 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw6kaQivFzQ-MZstb+Z_9nH+xMoQbOwW9rbJi5m0UTPm=w@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1403280820460.747@uplift.swm.pp.se>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <25769.1395869429@sandelman.ca> <53342461.80409@gmail.com> <CAA93jw6kaQivFzQ-MZstb+Z_9nH+xMoQbOwW9rbJi5m0UTPm=w@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/W0g2H1ah01ugUilj11rvGhitqFg
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Fri, 28 Mar 2014 07:56:02 -0000

On Thu, 27 Mar 2014, Dave Taht wrote:

> Code in progress is at:
>
> https://github.com/sbyx/hnetd/
>
> for anyone that cares to look/contribute.

I have been testing the code the guys have made available in OpenWRT 
trunk. Yes, the code is very rough, but there are quite a lot of things 
that work (and some that don't).

Very nice to see running code!

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Mar 28 01:02:33 2014
Return-Path: <swmike@swm.pp.se>
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 754061A0488 for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 01:02:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.861
X-Spam-Level: 
X-Spam-Status: No, score=-3.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 2FtK70uqElwU for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 01:02:31 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEE41A02C7 for <homenet@ietf.org>; Fri, 28 Mar 2014 01:02:31 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 693FEA5; Fri, 28 Mar 2014 09:02:28 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 629FBA3 for <homenet@ietf.org>; Fri, 28 Mar 2014 09:02:28 +0100 (CET)
Date: Fri, 28 Mar 2014 09:02:28 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <alpine.DEB.2.02.1403280820460.747@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1403280858430.747@uplift.swm.pp.se>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <25769.1395869429@sandelman.ca> <53342461.80409@gmail.com> <CAA93jw6kaQivFzQ-MZstb+Z_9nH+xMoQbOwW9rbJi5m0UTPm=w@mail.gmail.com> <alpine.DEB.2.02.1403280820460.747@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/oNADuiWyXY1P53K6yHIWJikmYdI
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Fri, 28 Mar 2014 08:02:32 -0000

On Fri, 28 Mar 2014, Mikael Abrahamsson wrote:

> I have been testing the code the guys have made available in OpenWRT 
> trunk. Yes, the code is very rough, but there are quite a lot of things 
> that work (and some that don't).

Btw, the package is called "hnet-full" which installs everything one 
needs. Then there is interface configuration needed. The authors pointed 
me to an interface configuration script at:

<https://raw.github.com/fingon/hnet-openwrt-feed/master/hnet/files/setup-network/ar71xx.sh>

Depending on platform you might have to change interface identifiers and 
vlan setup options.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Mar 28 05:13:34 2014
Return-Path: <hansliu@gmail.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 27C051A0552 for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 05:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 akd695l90r5o for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 05:13:30 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7991A050E for <homenet@ietf.org>; Fri, 28 Mar 2014 05:13:30 -0700 (PDT)
Received: by mail-ig0-f172.google.com with SMTP id hn18so721382igb.17 for <homenet@ietf.org>; Fri, 28 Mar 2014 05:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=W7V4G0Xg8vEj1JSTj/rELR3CoNrNRR7/Zl7xFTYaEYk=; b=sVovxN8lX9iKFpTk1hnrVH0OeuRnHKiDTkY01D2XFCgo+01Y0n47wPieMqXePwZQyK qkLsw6aU7JEykf8IzeQkjTzqXpNX+mV27/0MRZg1rbaD9N9l5YnDzNlS2Sz+6G/phr/6 Af0Ct3lkVNS6rO08agGIrOJfhhIsa0ZeJablwMRkHxOXdzLwqdzmGLlihJNzdrkoepbo UwYQI7ziHsIdU7hHWPvGL0zEQdvMi9z74RgmuC6iSxez2NfiayA5StlEPbMujEkxkdBJ 4vsyFlqEm6GdPR/wCXS99ESOktPqXgbBrxPDt3sp2L6Uim5tNago1688xXnqe8YFlVTG TxYQ==
MIME-Version: 1.0
X-Received: by 10.43.138.8 with SMTP id iq8mr7071572icc.37.1396008807904; Fri, 28 Mar 2014 05:13:27 -0700 (PDT)
Received: by 10.64.231.97 with HTTP; Fri, 28 Mar 2014 05:13:27 -0700 (PDT)
In-Reply-To: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Date: Fri, 28 Mar 2014 20:13:27 +0800
Message-ID: <CAHEOdgupViPBed5zQOhDD1+L0qNuxC6d2zMj9WrvB=-7FPc8ng@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c20364193aea04f5a9a11b
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/xqtzGdEpCypbEGg_hGyo1V7-vbs
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Fri, 28 Mar 2014 12:13:32 -0000

--001a11c20364193aea04f5a9a11b
Content-Type: text/plain; charset=UTF-8

Just read the draft and would like to support the adoption of HNCP as a WG
item.

Thanks,
Hans


On Tue, Mar 25, 2014 at 6:07 PM, Ray Bellis <Ray.Bellis@nominet.org.uk>wrote:

> At IETF 89 in London we took three hums:
>
> 1. On use of OSPF vs HNCP for configuration - strong consensus for HNCP
>
> 2. On how many routing protocols we should support in Homenet -
>   strong consensus that it should be zero or one, but no consensus yet
>   on which.
>
> 3. On adoption of HNCP as a WG item - good consensus for, a few undecided,
>   none against.
>
> On this basis the Chairs wish to proceed with the formal call for adoption
> of draft-stenberg-homenet-hncp-00, with a two week response window.
>
> Please therefore send your comments on adoption of this draft to the list
> before 23:59 UTC on Tuesday 1st April.
>
> thanks,
>
> Ray and Mark
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>



-- 
Instead of following the fashion, we lead it through.

--001a11c20364193aea04f5a9a11b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just read the draft and would like to support the adoption=
 of HNCP as a WG item.=C2=A0<div><br></div><div>Thanks,</div><div>Hans</div=
></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue=
, Mar 25, 2014 at 6:07 PM, Ray Bellis <span dir=3D"ltr">&lt;<a href=3D"mail=
to:Ray.Bellis@nominet.org.uk" target=3D"_blank">Ray.Bellis@nominet.org.uk</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">At IETF 89 in London we took three hums:<br>
<br>
1. On use of OSPF vs HNCP for configuration - strong consensus for HNCP<br>
<br>
2. On how many routing protocols we should support in Homenet -<br>
=C2=A0 strong consensus that it should be zero or one, but no consensus yet=
<br>
=C2=A0 on which.<br>
<br>
3. On adoption of HNCP as a WG item - good consensus for, a few undecided,<=
br>
=C2=A0 none against.<br>
<br>
On this basis the Chairs wish to proceed with the formal call for adoption =
of draft-stenberg-homenet-hncp-00, with a two week response window.<br>
<br>
Please therefore send your comments on adoption of this draft to the list b=
efore 23:59 UTC on Tuesday 1st April.<br>
<br>
thanks,<br>
<br>
Ray and Mark<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Instead of f=
ollowing the fashion, we lead it through.
</div>

--001a11c20364193aea04f5a9a11b--


From nobody Fri Mar 28 05:27:14 2014
Return-Path: <Ray.Bellis@nominet.org.uk>
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 339E41A05D1 for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 05:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 PBNH1ivGd_V0 for <homenet@ietfa.amsl.com>; Fri, 28 Mar 2014 05:27:08 -0700 (PDT)
Received: from mx1.nominet.org.uk (mx1.nominet.org.uk [213.248.242.48]) by ietfa.amsl.com (Postfix) with ESMTP id 864E21A0573 for <homenet@ietf.org>; Fri, 28 Mar 2014 05:27:07 -0700 (PDT)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To: Subject:Thread-Topic:Thread-Index:Date:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=r+zEIz8RYBn+wHNYfLy0AGTIgWRdpnn0SQO3/9+VTydraOIFnRWC+bAk MszZonL6yT9FVC9ZY1D1AbRCB7e4gfF6cDUnrWvTvMqkep4EvwwqGfXDZ HX9PSp4/TBzgFRcgjBjB6rnAw+yt5WmgTgPYV209hb5C1HgQ3AYPudjdK hCj3Zaj1XVGmloa1D0blNiXGd5RFRIQPqAf3bcL/RyvY56yHNI25HkpqG idhZWipn2VgPU6/9+Pm47XhbmGdVM;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1396009626; x=1427545626; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=AZDZym0K+a4imTKY8MlJ+R8cLsSjuukRdb5H8xcZheI=; b=Eoi5qfKJTbqPL+SGQGyuCUt8je+Akw4KgR1MgQLiz/ScdfwAp9KRRAKS anfQK1kjOeqAkM7mFawsIzGc6ysymaGvXNxgoMYjjeqZKpVVdk14oOXPe Uim3DzhRZ2QDvJw6gTGpYwaNd9am/j6AStRqFEef/e/UEEcQZUUMQk4z2 piZV4Iv+8O4agj8GbyIw1Ja0moFNnNi7FrJSIOeddYIhjjxABGsbqkliX zYzwmueJVbrLucOp8G/9xeB6FBJmc;
X-IronPort-AV: E=Sophos;i="4.97,750,1389744000";  d="scan'208";a="8740503"
X-IPAS-Result: AkcEAOtpNVPV+MWRdGdsb2JhbABZgmWBM8JtgRsWDgEMWYIlAQEBAQIBOhkrCwIBCDYQMiUCBBOHcQkD0WwXjkg6gySBFASsc4E/gis
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx1.nominet.org.uk with ESMTP; 28 Mar 2014 12:27:04 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.03.0123.003; Fri, 28 Mar 2014 12:27:04 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: [homenet] WG adoption of draft-stenberg-homenet-hncp-00 {Sender Address Possibly Forged}
Thread-Index: AQHPSoEG2hHYEW/buUGHIhXl7aorgA==
Date: Fri, 28 Mar 2014 12:27:03 +0000
Message-ID: <CE0876A4-3E6A-43A4-93AF-B8959C12C31A@nominet.org.uk>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
In-Reply-To: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FA014F23CA2FD74993F3E8D43D93B44D@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Hg61S97FcGVhp6citMmM7zpdWqc
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00 {Sender Address Possibly Forged}
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: Fri, 28 Mar 2014 12:27:11 -0000

On 25 Mar 2014, at 10:07, Ray Bellis <Ray.Bellis@nominet.org.uk> wrote:

> Please therefore send your comments on adoption of this draft to the list=
 before 23:59 UTC on Tuesday 1st April.

Oops, where did March go?!

That should, of course, have read Tuesday *8th* April.

Ray


From nobody Mon Mar 31 19:31:50 2014
Return-Path: <shwethab@cisco.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 D36861A6FCC for <homenet@ietfa.amsl.com>; Mon, 31 Mar 2014 19:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 OR9J4PKOqstY for <homenet@ietfa.amsl.com>; Mon, 31 Mar 2014 19:31:47 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id F12701A6FC0 for <homenet@ietf.org>; Mon, 31 Mar 2014 19:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=959; q=dns/txt; s=iport; t=1396319503; x=1397529103; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=zVQ8C629NBjuwED5Gly6sf/JhgVkpD9idROsAjpxxjo=; b=aUVbyVtR5hjFYpxQbtVtUkzj9TnSyfHwMF3VoVKKiUd2i0H83D/pyXGf eDAtyKmF2Lg4nQ8D5C5aNkNzIz2dz/EEvgFFVcPPcNAEdfjhR7TNrLHRT s7nBzrRYAQgn5NywGE3hzP+3EyqrKLAjFD+DevGpsDyZgbMUzZDhIH1ed I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFALcjOlOtJV2c/2dsb2JhbABZgwY7V7tohmRRgR4WdIInAQQBAQEaHTQdAQg2NwslAgQBEod5DdEoEwSOHFuEOASYTpI2gzCCKw
X-IronPort-AV: E=Sophos;i="4.97,769,1389744000"; d="scan'208";a="31861480"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP; 01 Apr 2014 02:31:42 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s312Vgv5009714 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 1 Apr 2014 02:31:42 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.5]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Mon, 31 Mar 2014 21:31:41 -0500
From: "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
Thread-Index: AQHPSBH2sAibSti7AUO5/uF/+E9TuZr81agA
Date: Tue, 1 Apr 2014 02:31:40 +0000
Message-ID: <CF6022C4.16B941%shwethab@cisco.com>
In-Reply-To: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.65.38.145]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B7F5229393D9524AA5E15F043E218403@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/zgkAwbnmP5L4Ga4vp8ScAd5GuDg
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
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: Tue, 01 Apr 2014 02:31:49 -0000

I have read and support adoption of this draft.

Thanks,
Shwetha

On 3/25/14 3:37 PM, "Ray Bellis" <Ray.Bellis@nominet.org.uk> wrote:

>At IETF 89 in London we took three hums:
>
>1. On use of OSPF vs HNCP for configuration - strong consensus for HNCP
>
>2. On how many routing protocols we should support in Homenet -
>  strong consensus that it should be zero or one, but no consensus yet
>  on which.
>
>3. On adoption of HNCP as a WG item - good consensus for, a few undecided,
>  none against.
>
>On this basis the Chairs wish to proceed with the formal call for
>adoption of draft-stenberg-homenet-hncp-00, with a two week response
>window.
>
>Please therefore send your comments on adoption of this draft to the list
>before 23:59 UTC on Tuesday 1st April.
>
>thanks,
>
>Ray and Mark
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet

