
From nobody Fri Jul  8 06:00:16 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietf.org
Delivered-To: homenet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 439B012D62F; Fri,  8 Jul 2016 06:00:11 -0700 (PDT)
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: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708130011.32095.81479.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 06:00:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ADhChJHbSUuD9t_KVoVIkBwz7Tc>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-babel-profile-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 13:00:11 -0000

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

        Title           : Homenet profile of the Babel routing protocol
        Author          : Juliusz Chroboczek
	Filename        : draft-ietf-homenet-babel-profile-00.txt
	Pages           : 7
	Date            : 2016-07-08

Abstract:
   This document defines the subset of the Babel routing protocol
   [RFC6126] and its extensions that a Homenet router must implement.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-babel-profile-00


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 Fri Jul  8 07:20:07 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietf.org
Delivered-To: homenet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD3E12D1A5; Fri,  8 Jul 2016 07:20:02 -0700 (PDT)
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: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708142002.32180.68068.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 07:20:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pi3GfZSblh_Kq6ZdVFRmotB2C80>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 14:20:02 -0000

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

        Title           : Home Networking Control Protocol
        Authors         : Markus Stenberg
                          Steven Barth
                          Pierre Pfister
	Filename        : draft-ietf-homenet-hncp-bis-00.txt
	Pages           : 38
	Date            : 2016-07-08

Abstract:
   This document describes the Home Networking Control Protocol (HNCP),
   an extensible configuration protocol, and a set of requirements for
   home network devices.  HNCP is described as a profile of and
   extension to the Distributed Node Consensus Protocol (DNCP).  HNCP
   enables discovery of network borders, automated configuration of
   addresses, name resolution, service discovery, and the use of any
   routing protocol that supports routing based on both the source and
   destination address.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-hncp-bis-00


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 Fri Jul  8 09:25:38 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5718112D8DC; Fri,  8 Jul 2016 09:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 iORQovvTcM3U; Fri,  8 Jul 2016 09:25:27 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87E1812D7FA; Fri,  8 Jul 2016 09:25:23 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id f89so23530544qtd.2; Fri, 08 Jul 2016 09:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=jsfnLXDBEyVQq8z2vghpu65vdd1zwGQiEUTBEXAOIvU=; b=LYFAZvnUKRlp9+wcODPelTVlDWnXLgWoS8iBrZ9gB+y81eDQQzhgc07I1VIObmqSlT sCBppKM1knUj0AHqFL7dSmTVN9URJp1l+uYSH/3kfVYZ9G/7btT9fixv0Oqwgujt6meA X96pWY7ZEdA46IVDVRQBWc4kkkKw3jciKbwuLFrNN9XoLLm2J4qdBC4qOTnICpBxEINz 2Tubqu2kWBVdFKm2OPv2CjlyLIeO0oPlef7KrqMxmjQ7jzwCYusSdNaaPbtXFFECXPGy +sxXKuNn/eJlMeS7tjJ/C+VQ0MG8pG8A+gWudUEZCh4+kbYqZvwXvHpkDMilXly0TmEV OH+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=jsfnLXDBEyVQq8z2vghpu65vdd1zwGQiEUTBEXAOIvU=; b=IX6rBdJyg4hTQR510g9Rxvt+FVS5wQw9kb8PbCQaGifOnLJFuMHzNseDTMe9URXAYW aDC0Z7+3SWLWBDEUKOZXUEBTkOcEbXxLFzcu86mRHV1YH8l/PcZRgSHK4bK0qFAbKVxU vJG2GPY/j7wWc7QGgGlNzvv6tYPDz5z7eVWg1JqNiiTiMlLm6Q948WwOcAq7lRl5kqmE poXLZFBgYyVMSLanOnW9yjzMl4NO/Njxoo7tUDogJeE2CSiMrCA5t9y+63H1hF5H8J9Z K/h95cLTiw4JJiwshrT8KTGRp6o0faUaBSArg64FvJMI7WdE/+vZU1gR5c8DKgV19OqE 50RQ==
X-Gm-Message-State: ALyK8tK9BXGZfrnkfWfMTUseLdyFkrCqQ0+Uait8BgGJmre4tdEM/Z9OWVYR66bjisKrbQ==
X-Received: by 10.200.50.237 with SMTP id a42mr10054026qtb.80.1467995122462; Fri, 08 Jul 2016 09:25:22 -0700 (PDT)
Received: from ?IPv6:2001:420:2c8b:1300:1c79:cd32:17ff:a74a? ([2001:420:2c8b:1300:1c79:cd32:17ff:a74a]) by smtp.gmail.com with ESMTPSA id r81sm719916qka.33.2016.07.08.09.25.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Jul 2016 09:25:21 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_29E4C8A0-6F94-476A-BE32-7FDE1E68BD97"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail 2.6b2
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <20160708142002.32180.68068.idtracker@ietfa.amsl.com>
Date: Fri, 8 Jul 2016 12:25:20 -0400
Message-Id: <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com>
To: draft-ietf-homenet-hncp-bis.all@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Xh1W5ynhpi_4KA2nLuhB_kUV_MQ>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 16:25:34 -0000

--Apple-Mail=_29E4C8A0-6F94-476A-BE32-7FDE1E68BD97
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I took a quick look at draft-ietf-homenet-hncp-bis-00, including a diff; =
seems the only change is to solve the .home problem.  I don't think I =
quite understand the new text and here's a suggested clarification:

OLD:

  A default value for this TLV MUST be set, although
  the default value of the Domain-Name TLV (Section 10.6) is out of
  scope of this document, and an administrator MAY configure the
  announcement of a Domain-Name TLV for the network.

NEW:

  The administrator MUST configure the announcement of a network-wide
  zone suffix through the Domain-Name TLV.

As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address =
errata 4718.  While this errata has not yet been verified, in my opinion =
*something* has to be done to correct the text around "Multicast DNS =
Proxy".  If "Multicast DNS Proxy" is intended to refer to "Hybrid Proxy" =
in draft-ietf-dnssd-hybrid-03, the appropriate normative reference will =
constitute a downref in draft-ietf-homenet-hncp-bis-00.

- Ralph

> On Jul 8, 2016, at 10:20 AM 7/8/16, Internet-Drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Home Networking of the IETF.
>=20
>        Title           : Home Networking Control Protocol
>        Authors         : Markus Stenberg
>                          Steven Barth
>                          Pierre Pfister
> 	Filename        : draft-ietf-homenet-hncp-bis-00.txt
> 	Pages           : 38
> 	Date            : 2016-07-08
>=20
> Abstract:
>   This document describes the Home Networking Control Protocol (HNCP),
>   an extensible configuration protocol, and a set of requirements for
>   home network devices.  HNCP is described as a profile of and
>   extension to the Distributed Node Consensus Protocol (DNCP).  HNCP
>   enables discovery of network borders, automated configuration of
>   addresses, name resolution, service discovery, and the use of any
>   routing protocol that supports routing based on both the source and
>   destination address.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp-bis/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-homenet-hncp-bis-00
>=20
>=20
> 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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_29E4C8A0-6F94-476A-BE32-7FDE1E68BD97
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXf9PxAAoJEINeeBNmFjV5BM0QALeatP7KLCN9fPkmCsSHBXOZ
wh8AC938hULF+apGaPcNjstruFwz5W1GViwjiaFfqtB9XRITeJUO/wXP4QTRRmBz
c0L8LsDmN7o+HjFmF0MpFaTsEgJA3oix5iKllD1pBZ0twP3HDo9xlSwoA2+rEQKl
FqtAvGNv3utyOw2MLbshtaI1Pczfg2nUktOsCq96KhKJdH/OaXtLz1vT1oNJGVM9
LvWwCIX38HXAFhflrRv2NvHE8utN8UdGWafVs1ltRqQ5hby09TJtJHNdwvLQAxcF
RqP1dY3drgc6fiHe+qVva6Pfmaq9XZLUfuMfE1niNBnZLLo7ZycEwXC+cVwBBWK9
CV1SNraD/pUV2UOuGxNTE6alEgxkOsB78+Bao/x/9mqeuz1dCvfxvnrqXibQrLmz
ElIz6O8W2ESDJWx65xFQaV/fsybb1JHUCP6m5TP+JpQIN1PSGg4VsPkxLg5F9qHd
h9alvkpSYggmRS6gwS3w1XMB65Ig3cKtwkPM95AtYB19g+ok8Xu9U3+TEgzo5Uos
T5gCu1Gml6JcYmD1AOyv5OeCp6c93Tx2Z3bZnngvWobRn7X7w7EiQLhtyWsSrYRc
khGBW8D4asf5YOvcKE1tU/914Ka898KM4YUZByVsxEerBYA7R6ae6V/uQZgKTbEF
lN2cK+tB1Qv9bqZNPtlX
=7ToI
-----END PGP SIGNATURE-----

--Apple-Mail=_29E4C8A0-6F94-476A-BE32-7FDE1E68BD97--


From nobody Fri Jul  8 09:30:44 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C907612D7C4; Fri,  8 Jul 2016 09:30:41 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 ewcpNAPLbYWN; Fri,  8 Jul 2016 09:30:35 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23D1612D783; Fri,  8 Jul 2016 09:30:17 -0700 (PDT)
Received: from [46.227.151.81] (port=53253 helo=rays-mbp-3.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bLYfN-0006cL-7d (Exim 4.72) (return-path <ray@bellis.me.uk>); Fri, 08 Jul 2016 17:30:13 +0100
To: Ralph Droms <rdroms.ietf@gmail.com>, draft-ietf-homenet-hncp-bis.all@ietf.org
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
Date: Fri, 8 Jul 2016 17:30:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/7prJ5G24cbTHboCKMoGoSDjpl6w>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 16:30:42 -0000

On 08/07/2016 17:25, Ralph Droms wrote:
> I took a quick look at draft-ietf-homenet-hncp-bis-00, including a
> diff; seems the only change is to solve the .home problem.  I don't
> think I quite understand the new text and here's a suggested
> clarification:
> 
> OLD:
> 
> A default value for this TLV MUST be set, although the default value
> of the Domain-Name TLV (Section 10.6) is out of scope of this
> document, and an administrator MAY configure the announcement of a
> Domain-Name TLV for the network.
> 
> NEW:
> 
> The administrator MUST configure the announcement of a network-wide 
> zone suffix through the Domain-Name TLV.
> 
> As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address
> errata 4718.  While this errata has not yet been verified, in my
> opinion *something* has to be done to correct the text around
> "Multicast DNS Proxy".  If "Multicast DNS Proxy" is intended to refer
> to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, the appropriate
> normative reference will constitute a downref in
> draft-ietf-homenet-hncp-bis-00.

The instruction to the authors were to incorporate the original .home
errata verbatim, and also to fix the error with options 37/38 being the
wrong way around in two diagrams.

If there is to be further wordsmithing on that we'd need to take that up
with our AD.

As for errata 4718, I fully expect that it will be incorporated in a
further revision just as soon as it has been verified (and subject to a
resolution of any resulting downref issue).

kind regards,

Ray


From nobody Fri Jul  8 15:45:49 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043E012D76C; Fri,  8 Jul 2016 15:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tAnvSLLTrC1x; Fri,  8 Jul 2016 15:45:45 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B971712D580; Fri,  8 Jul 2016 15:45:45 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id f89so28509584qtd.2; Fri, 08 Jul 2016 15:45:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=jdQV0AT7MhcEkpm9LnpObdy663vMxVhGV9cHV0zrscU=; b=naPIuWdPQEKoXPmLrLIz4gBRHLlNABsQPYdl78eBjJksrBJ7DZqqWGc6Bgn0/JVbNy /2046uimGOnq8ZVH71fRDJ8qjwqyGQJtzfln5M2av+8xkRvTwhKgq+d/5+Nr1vWMbG5A 9sy8GUwVWEx8hGldapry733XNYmw7uIt6GwRuAGUtmK8LtiI0vBE39lmshSdHas21O5y y7XBsvChXE5cw4ZIYQMbq7oKiprpQkh/S7LDNSNL2iol4AZUvgp49pQpi7/VUBU8REJf VTSirkHTxl0TOAxUXst91lYviOWqRN9g7MN8Ad0PInZCSCp9dzYPtZy9wscp/temZwcN u6UA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=jdQV0AT7MhcEkpm9LnpObdy663vMxVhGV9cHV0zrscU=; b=MrgtP+aqIa28D0BfgKnB8u/Xbs3CjRtd2RoKYdolLMYvJHsjTfgkCpUtI4S6348ZR3 ACHTa8M0qaNUjOo+DVYrbRm6hNq9sbv91Gudllkb441wLVtzW8KH2s9yWIbLo0ongIkk SF+nepsjfCCpfR1sOhOe0uz8U/rl4dRd2/BOaWw6CCG69/jAI6VdEX3HS/7jFWIuASiA HvZ8H6egw+a5lq51kqjz5kS+UC986/L8xIYCLB1t/FZI7rBSz4ifiIdwrJO421UJZswG pPR1S619zjfsj0I7iNXkAKJq2qEHEIx/e6yd9E2w4Fw+ORoj+vtGhJKEnKQdCxpGe3iV FrGw==
X-Gm-Message-State: ALyK8tL1AKceXH4RrQAD5lyCI+XtjLEibEYtaJ8cf2bfSDyDytqx1vzR20XaSXUCjpdCIg==
X-Received: by 10.237.39.167 with SMTP id a36mr12457066qtd.103.1468017944827;  Fri, 08 Jul 2016 15:45:44 -0700 (PDT)
Received: from rtp-rdroms-nitro3.cisco.com ([173.38.117.77]) by smtp.gmail.com with ESMTPSA id n198sm1556032qkn.15.2016.07.08.15.45.43 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Jul 2016 15:45:44 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_169FA3D0-C620-47D8-92DE-BEE3FEE3B502"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail 2.6b2
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
Date: Fri, 8 Jul 2016 18:45:42 -0400
Message-Id: <B22E7F4B-149E-4FE5-9E19-47AA3CA3ED67@gmail.com>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/cGeHcKFuBllhEE4v8UnFxD9f6gg>
Cc: HOMENET <homenet@ietf.org>, draft-ietf-homenet-hncp-bis.all@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 22:45:48 -0000

--Apple-Mail=_169FA3D0-C620-47D8-92DE-BEE3FEE3B502
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 8, 2016, at 12:30 PM 7/8/16, Ray Bellis <ray@bellis.me.uk> =
wrote:
>=20
>=20
>=20
> On 08/07/2016 17:25, Ralph Droms wrote:
>> I took a quick look at draft-ietf-homenet-hncp-bis-00, including a
>> diff; seems the only change is to solve the .home problem.  I don't
>> think I quite understand the new text and here's a suggested
>> clarification:
>>=20
>> OLD:
>>=20
>> A default value for this TLV MUST be set, although the default value
>> of the Domain-Name TLV (Section 10.6) is out of scope of this
>> document, and an administrator MAY configure the announcement of a
>> Domain-Name TLV for the network.
>>=20
>> NEW:
>>=20
>> The administrator MUST configure the announcement of a network-wide
>> zone suffix through the Domain-Name TLV.
>>=20
>> As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address
>> errata 4718.  While this errata has not yet been verified, in my
>> opinion *something* has to be done to correct the text around
>> "Multicast DNS Proxy".  If "Multicast DNS Proxy" is intended to refer
>> to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, the appropriate
>> normative reference will constitute a downref in
>> draft-ietf-homenet-hncp-bis-00.
>=20
> The instruction to the authors were to incorporate the original .home
> errata verbatim, and also to fix the error with options 37/38 being =
the
> wrong way around in two diagrams.

I honestly can't understand the new text.  Why a friendly suggestion for =
a simplification need AD intervention?

>=20
> If there is to be further wordsmithing on that we'd need to take that =
up
> with our AD.
>=20
> As for errata 4718, I fully expect that it will be incorporated in a
> further revision just as soon as it has been verified (and subject to =
a
> resolution of any resulting downref issue).

OK. As an aside, *something* will have to be done with the text =
regarding "Multicast DNS Proxy" regardless of whether or not the errata =
is verified.  I see a couple of ways to read the existing text and the =
citations of RFC 6762.

One way to read RFC 7788 is to assume "Multicast DNS Proxy" refers to =
the "Multicast DNS Proxy Servers" defined in RFC 6762, in which case RFC =
7788 is specifying that an HNCP device should participate in whatever =
election protocol "Multicast DNS Proxy Servers" use to elect the proxy =
server for a link.  That election protocol would need a normative =
reference.

Another way to read RFC 7788 is that there is no citation for a =
definition of "Multicast DNS Proxy" at all (assuming the citations of =
RFC 6762 apply just to mDNS and not "proxy"), in which case RFC 7788 =
needs to be amended to include that definition of "Multicast DNS Proxy".

Seems like the WG might want to go ahead and figure out which way it =
wants to fix this issue as doing nothing isn't an option.

- Ralph

>=20
> kind regards,
>=20
> Ray
>=20


--Apple-Mail=_169FA3D0-C620-47D8-92DE-BEE3FEE3B502
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXgC0XAAoJEINeeBNmFjV57HkP/3WjhsC2jla6I2KHAQS9oLyt
8VD1qCXGtDadeySwXEwwki05padGT4NTxP4gem54blw1AWkW+V1h/1QB4wQS/wt3
QMKunlqhcmA7JwGHw+/z5B/glHLGsTTohOtNGIiffrDA5KcfOuVtHYrBwXfLaqgz
uyQF3rdBA2VlmoQUbqCIM4uQNGs/ivqjyFKEXzIlYBDNsqFYooMrBJwBVV5h4yqx
I3y6iGLlacboRF1RF41hVpqRExCxQWHroTGj9DavP24oxTfYvKY6wtHI5nIwsuMs
e8Fx5pRsEw4RuHvkGy1myjU0S1tA+ZMKGnh83A4di4ORwXMpKfIv1KCliw6Wo114
elF9Rnou/oEtutP/ru6UwFeJ7z+pip/aRwIf+lCj0/2lS2aDttBsAlvF3sTai/M+
vqVZx2xDj7tNzCl/XffITGeVIrwVlM5eRP5uN3Sj9ct/OD9td0hQlo8q2Hef6Lq3
qlROnhyLbkpVhY/oH3WpbjUbqwgzqprCUzK3Dtel5JMcnAI1Q4bmftZtnaHDjTYR
9mXH3aF7Sk+R7FA02y04TpbTeJKg3FvblIM1IEAlpwGwv5n1Paw3XZ7OD5fRNWa/
xYhCw7pv50bUnXUeOdVXeMaO6yCkvv/6z98atGJpQNIWTsj5ZHirXRej+7WxzqRH
LHy290mYzYqCTyuL1BE6
=MsEw
-----END PGP SIGNATURE-----

--Apple-Mail=_169FA3D0-C620-47D8-92DE-BEE3FEE3B502--


From nobody Fri Jul  8 15:47:40 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA5912D8C4; Fri,  8 Jul 2016 15:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4IAFDlLsQQY0; Fri,  8 Jul 2016 15:47:28 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ECA812D779; Fri,  8 Jul 2016 15:47:28 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id c34so28536177qte.0; Fri, 08 Jul 2016 15:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=a+qL3p4Q1E/akjZbLDFBF6ZrxMHKTsBOz9aPrlTtGz8=; b=NT+T+v4eqlEvpzCewH8Ltt8gWcp//152affj3xVoHiHBDBFpbyQOTdGLQpv0ARXTLo RDeYtG2/zlyDCcZsMa1nl22IFBrG6Tc22mHVUAofZIYhEyadH80mgkNozFwGYg5PxVbx sQM0BVif0pSTfbljPEizqX+4tO7v+U5oy7DRJ3sdRwEyRhtwwO9LRQxWPl6Kl5J7yg1u Bgz/jFIQrl956WtP5jpT41NvSnulpCemwDAEz15PLh0WEUUa3v+9T3g6za1A5hBTyJ67 GMGx/xT3KXzkfvPScLQZbt/MV/VoQ2L7ALvdt4LgeMaDb7Oz9KHlE+S4fuU1L7gqC+s7 EYWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=a+qL3p4Q1E/akjZbLDFBF6ZrxMHKTsBOz9aPrlTtGz8=; b=nDkFi4kUxjgvY1PlZyA4/c1xgohyF2B/j0atiHNSNYkpcBxYIcdSBP28XNE41ri8ol yej/ESy2BnfEGSX9dFuQAli/pIfgEixAlbEQtIVpunr+ujVLjpSsN9QMKmvPLxLAkb9T UFGKBjhTIZMYfylztuHxibNKD00My9i7i8vNsjBjoHnykui0wZArE2gRLiRHuYDRPchl 8RndyH+D4pQ94+q4n+UIMsHtepUdKCGx/B0EiKBCPrLA1dCJRgv+Ax8RpDtGnQqIa/xw hWkdHyqAZDg/nMjvGruakMu/DuWUwdU3DUot80aKAlfO73POWKvOVpnhidWVVnY3txqa wDKQ==
X-Gm-Message-State: ALyK8tIvgrmQAJytckE0Ovq/iCHsgXbsuuMVDSJL9Ns8aostELxGDHJxP6DqIfyepb9IQw==
X-Received: by 10.237.33.69 with SMTP id 63mr12363769qtc.45.1468018047127; Fri, 08 Jul 2016 15:47:27 -0700 (PDT)
Received: from rtp-rdroms-nitro3.cisco.com ([173.38.117.77]) by smtp.gmail.com with ESMTPSA id n198sm1559331qkn.15.2016.07.08.15.47.26 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Jul 2016 15:47:26 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_92DD95D9-223D-428C-8EE3-B50B33C2CB86"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail 2.6b2
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
Date: Fri, 8 Jul 2016 18:47:25 -0400
Message-Id: <F2B69F41-BD45-4664-B024-C9933A3A5F38@gmail.com>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/gkXQ6vcTm7f5Db-Qdfcaeek6JFM>
Cc: HOMENET <homenet@ietf.org>, draft-ietf-homenet-hncp-bis.all@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 22:47:39 -0000

--Apple-Mail=_92DD95D9-223D-428C-8EE3-B50B33C2CB86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 8, 2016, at 12:30 PM 7/8/16, Ray Bellis <ray@bellis.me.uk> =
wrote:
>=20
>=20
>=20
> On 08/07/2016 17:25, Ralph Droms wrote:
>> I took a quick look at draft-ietf-homenet-hncp-bis-00, including a
>> diff; seems the only change is to solve the .home problem.  I don't
>> think I quite understand the new text and here's a suggested
>> clarification:
>>=20
>> OLD:
>>=20
>> A default value for this TLV MUST be set, although the default value
>> of the Domain-Name TLV (Section 10.6) is out of scope of this
>> document, and an administrator MAY configure the announcement of a
>> Domain-Name TLV for the network.
>>=20
>> NEW:
>>=20
>> The administrator MUST configure the announcement of a network-wide
>> zone suffix through the Domain-Name TLV.
>>=20
>> As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address
>> errata 4718.  While this errata has not yet been verified, in my
>> opinion *something* has to be done to correct the text around
>> "Multicast DNS Proxy".  If "Multicast DNS Proxy" is intended to refer
>> to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, the appropriate
>> normative reference will constitute a downref in
>> draft-ietf-homenet-hncp-bis-00.
>=20
> The instruction to the authors were to incorporate the original .home
> errata verbatim, and also to fix the error with options 37/38 being =
the
> wrong way around in two diagrams.

I honestly can't understand the new text.  Why a friendly suggestion for =
a simplification need AD intervention?

>=20
> If there is to be further wordsmithing on that we'd need to take that =
up
> with our AD.
>=20
> As for errata 4718, I fully expect that it will be incorporated in a
> further revision just as soon as it has been verified (and subject to =
a
> resolution of any resulting downref issue).

OK. As an aside, *something* will have to be done with the text =
regarding "Multicast DNS Proxy" regardless of whether or not the errata =
is verified.  I see a couple of ways to read the existing text and the =
citations of RFC 6762.

One way to read RFC 7788 is to assume "Multicast DNS Proxy" refers to =
the "Multicast DNS Proxy Servers" defined in RFC 6762, in which case RFC =
7788 is specifying that an HNCP device should participate in whatever =
election protocol "Multicast DNS Proxy Servers" use to elect the proxy =
server for a link.  That election protocol needs a reference

Another way to read RFC 7788 is that there is no citation for a =
definition of "Multicast DNS Proxy" at all (assuming the citations of =
RFC 6762 apply just to mDNS and not "proxy"), in which case RFC 7788 =
needs to be amended to include that definition of "Multicast DNS Proxy".

Seems like the WG might want to go ahead and figure out which way it =
wants to fix this issue as doing nothing isn't an option.

- Ralph

>=20
> kind regards,
>=20
> Ray
>=20


--Apple-Mail=_92DD95D9-223D-428C-8EE3-B50B33C2CB86
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXgC19AAoJEINeeBNmFjV5mc0P/1ae2R6Xex9PWtpdcELgBaO+
DAfRj9KixSlGisSFmAcva4fHYQNZLB7sy2XyhQAOSr4q9NwqJwXBKaPefqmH4mHi
9NjvCCzfQDU8xKsYKSJRTTGgtTTZNfLueQL2cazlGZBFEFGjMskEg3/0UnjLCIG6
38/Fz5J2iE4avGw0amtluhZ7z50a9DyZejiEdlU1CWue7+5GittDrk+ideHPTACY
s70T1YdluTJbDoibI+KByJ1EcA6hpfQ8Ua0DlW+l9PfLDlOkezwP/qGrj4CByzJu
/+DiVO/YvhNqRtOPJFA8VddmRMIj+h79KHoMz+zkWapixR1lNVe0bxCW8/VHfHDg
N4EuhK6s+KUBA7ebs3SPWRf4Nbo8/Xd5sNVJp83wyPKZycBmh0Btd/nxUfOLmZ48
7ARS2ih3qbqEiFsoyOb+P/0N4cDdx7k5X2wRJHkEndiSmZEi1mq55d3OBn6wIhOJ
n4AveuoUxHM+loh3d4IHHqaHA1pjhZBOsJ3T04BDzjSVcCZgvkiR9d72PP/9tZxy
2tqSZ55Tr0TiQa7gpptMWdP7W7LfNtKLhCs0PZs57WM0vizw0Ha2emNTD+wyL/mV
xKrOPLSXOA5/7z7lqCXa0YGqHz/TOD8OxZ0EU8aILfhxwIOhuIwRRAD9uaS3SEIw
IvUMK3JlYDjZnUmuvg6K
=NUzd
-----END PGP SIGNATURE-----

--Apple-Mail=_92DD95D9-223D-428C-8EE3-B50B33C2CB86--


From nobody Fri Jul  8 15:52:26 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1F512D8CE; Fri,  8 Jul 2016 15:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 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, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rsN3yjGndGJK; Fri,  8 Jul 2016 15:52:23 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C85B12D1D5; Fri,  8 Jul 2016 15:52:23 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id s63so14207748qkb.2; Fri, 08 Jul 2016 15:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VXZnsFaweQnZoCAXsJhFC1ghp7nO4eTzrBlHyWJwn3g=; b=cOZbB+worQdWtzjtrqKUuhh1qFOwCyB7yOhK8JlwqA0REl1jNwCWeYjirM5cC8P4a2 ONH9i08vvr/drE+1XjiYSM5qYa7Pbjp8e0FB+A6JhwRmKLbftyyXQs7wKBd2qZQXlkVG WNqXt55Paoc3yJVt+eNcx1WIffouONaQry4i42n9uP9TcfkLKHB6s3s2tfWhWx7aruyF 74bEIi7tAWlFcUrnb00+E0apyCzzm5jgF31luLX5hcabhTF+qzEkHc9mv+cxg4kp+whi A0/4vcbkcdX9fqXP1UP1E+m73DQ8lTHz9HvnQf6FQNYrrqPz5MlkX6l1BCSG+0zAeen9 DgQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VXZnsFaweQnZoCAXsJhFC1ghp7nO4eTzrBlHyWJwn3g=; b=h5J+sNei1HsjP5w7nAPAOjboUN4hYDR8OVYZPeq3PZZxFb/386heo+X2KymhS+KFjg jL5w0ONlxasG+LwkL11wXjA33yBjy/QiZ56isP3kZwYn5AIH4ddYepu2fU9dQcYPVChv HHcT+U9y7o7KNSmPgNhbkQaU5W+HbVlW4mzKItpT8UD6BRyj3rf8Ww91miybrENPMybZ FN/mx3JxnIP356FpttDI9AOfIrCI6UL6ijJ17VkIHu+xMfY89WhpUS4mI9uzPNg3cbgF kraQI43dNPnF5icv85GHfcDZp6Ig5b59HdsqjJz3tc70NXUYU50WQB78ioqrcGbehtIF Bw0w==
X-Gm-Message-State: ALyK8tJM3sAYR/LApsj8K5NqZKNJkoqhqd7Ut2BnXpmpsWsIwwX/YZJ1NioKz/NC5wNh3g==
X-Received: by 10.55.116.195 with SMTP id p186mr10293392qkc.52.1468018342410;  Fri, 08 Jul 2016 15:52:22 -0700 (PDT)
Received: from rtp-rdroms-nitro3.cisco.com ([173.38.117.77]) by smtp.gmail.com with ESMTPSA id a22sm59989qtb.6.2016.07.08.15.52.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Jul 2016 15:52:22 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/html; charset=us-ascii
X-Apple-Base-Url: x-msg://123/
X-Apple-Mail-Remote-Attachments: YES
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
X-Apple-Windows-Friendly: 1
Date: Fri, 8 Jul 2016 18:45:15 -0400
X-Apple-Mail-Signature: 
Content-Transfer-Encoding: quoted-printable
Message-Id: <C407F615-99A5-44F2-B719-9C26FC04094C@gmail.com>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/wSgKHPRJlQxMxmgI2U_Hqe-RPo4>
Cc: HOMENET <homenet@ietf.org>, draft-ietf-homenet-hncp-bis.all@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 22:52:25 -0000

<html><head></head><body dir=3D"auto" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><blockquote type=3D"cite">On Jul 8, 2016, at =
12:30 PM 7/8/16, Ray Bellis &lt;ray@bellis.me.uk&gt; =
wrote:<br><br><br><br>On 08/07/2016 17:25, Ralph Droms =
wrote:<br><blockquote type=3D"cite">I took a quick look at =
draft-ietf-homenet-hncp-bis-00, including a<br>diff; seems the only =
change is to solve the .home problem. &nbsp;I don't<br>think I quite =
understand the new text and here's a =
suggested<br>clarification:<br><br>OLD:<br><br>A default value for this =
TLV MUST be set, although the default value<br>of the Domain-Name TLV =
(Section 10.6) is out of scope of this<br>document, and an administrator =
MAY configure the announcement of a<br>Domain-Name TLV for the =
network.<br><br>NEW:<br><br>The administrator MUST configure the =
announcement of a network-wide<br>zone suffix through the Domain-Name =
TLV.<br><br>As far as I can tell, draft-ietf-homenet-hncp-bis-00 does =
not address<br>errata 4718. &nbsp;While this errata has not yet been =
verified, in my<br>opinion *something* has to be done to correct the =
text around<br>"Multicast DNS Proxy". &nbsp;If "Multicast DNS Proxy" is =
intended to refer<br>to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, =
the appropriate<br>normative reference will constitute a downref =
in<br>draft-ietf-homenet-hncp-bis-00.<br></blockquote><br>The =
instruction to the authors were to incorporate the original =
.home<br>errata verbatim, and also to fix the error with options 37/38 =
being the<br>wrong way around in two diagrams.<br></blockquote><br>I =
honestly can't understand the new text. &nbsp;Why a friendly suggestion =
for a simplification need AD intervention?<br><br><blockquote =
type=3D"cite"><br>If there is to be further wordsmithing on that we'd =
need to take that up<br>with our AD.<br><br>As for errata 4718, I fully =
expect that it will be incorporated in a<br>further revision just as =
soon as it has been verified (and subject to a<br>resolution of any =
resulting downref issue).<br></blockquote><br>OK. As an aside, =
*something* will have to be done with the text regarding "Multicast DNS =
Proxy" regardless of whether or not the errata is verified. &nbsp;I see =
a couple of ways to read the existing text and the citations of RFC =
6762.<div><br></div><div>One way to read RFC 7788 is to assume =
"Multicast DNS Proxy" refers to the "Multicast DNS Proxy Servers" =
defined in RFC 6762, in which case RFC 7788 is specifying that an HNCP =
device should participate in whatever election protocol "Multicast DNS =
Proxy Servers" use to elect the proxy server for a link. &nbsp;That =
election protocol needs a =
reference&nbsp;</div><div><br></div><div>Another way to read RFC 7788 is =
that there is no citation for a definition of "Multicast DNS Proxy" at =
all (assuming the citations of RFC 6762 apply just to mDNS and not =
"proxy"), in which case RFC 7788 needs to be amended to include that =
definition of "Multicast DNS Proxy".<br><br>Seems like the WG might want =
to go ahead and figure out which way it wants to fix this issue as doing =
nothing isn't an option.<br><br>- Ralph<br><br><blockquote =
type=3D"cite"><br>kind =
regards,<br><br>Ray<br><br></blockquote><br></div></body></html>=


From nobody Fri Jul  8 16:05:13 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED42A12D945 for <homenet@ietfa.amsl.com>; Fri,  8 Jul 2016 16:05:11 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 SXp9nmcCECTR for <homenet@ietfa.amsl.com>; Fri,  8 Jul 2016 16:05:07 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6854212D8D9 for <homenet@ietf.org>; Fri,  8 Jul 2016 16:05:06 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id q132so36546704lfe.3 for <homenet@ietf.org>; Fri, 08 Jul 2016 16:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8sERR0oEdVQh4L+IgCvY04YUcqyXf0yXjG7YwH4Q0gM=; b=Ok+2EoWokzrooW5utayzhW3jke7mpG6Xxe1ShdgrVbLvs2CnGRnA+4dAJlqojofUE3 ZapjhvLKD+/yhvVRT4iiub5q/oQt0+7cI1j5Imjx5gqg7TdP0LiNQWhAcpip7gvLoo/m hYvv2hss4cf0je8qeRq1CFa9Q2UFyE4VPfAPRBWHSqB6v0qdzahvVwmfA/cPhcEbVHfO LMQOZpDqRHaH2Q0stqjOy3wWQN2/Z0klJtKN6ZaV5RPYa9wJpLU+kn6TTCU7LbNoIaJE BXRoq2cfaQDiMPqxzGFqqTD4etHVKs3Aew0j5r0o6+PPpdxXaQ7iH+bxANyuqWHS8oUd ZxYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8sERR0oEdVQh4L+IgCvY04YUcqyXf0yXjG7YwH4Q0gM=; b=bOcf595qcSR9M+ycNcwdu3nxEjxMZQAHWSSP06XAD7hzd8l2Gt/Y6JLOOoYxrHbZJ0 xybWtYMOtEUt8IJIo3Yfl2dLqBaTj14u4wbr4+UNkFcxccSPtmtXJxxdOajz+sVoBlPb x1WI2DSZCqomA/vFwCWCQaO7zY/6TVbPr1WW9+YYwtDtDwgFf0QPovlhDhIdn/JFHQ82 zT/WZsHCAZtYTsjoJzTF4hl+Rw0WgTAVoej6+h+hOlCJL+ZMLBS56Zuf0/JlCSKSN/Zv 2WhqnJ6YXt9NtcraQv3PL54NyU7/2k3ebx7lQQBIhVjYmp7AoT7SyKAYYLKK14Agv9pB H79Q==
X-Gm-Message-State: ALyK8tLdXpaI4OTW8qSjg4nRGy4k1b6dRDqanV+wmfiwPUBS/LNbEfLCQdp+AtW30rzJNujZS0ZsyMxsSEgRGw==
X-Received: by 10.25.216.106 with SMTP id p103mr1768384lfg.226.1468019104618;  Fri, 08 Jul 2016 16:05:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Fri, 8 Jul 2016 16:04:18 -0700 (PDT)
In-Reply-To: <C407F615-99A5-44F2-B719-9C26FC04094C@gmail.com>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk> <C407F615-99A5-44F2-B719-9C26FC04094C@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 8 Jul 2016 16:04:18 -0700
Message-ID: <CAPt1N1n9rL_Ybr=PSJaMTm-zD1atM6V15g3gi83BOzr2ivm5eA@mail.gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140d0ca413372053727d50a
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MiaiLK1RzfFj1d38sIyWYAJ4b3k>
Cc: HOMENET <homenet@ietf.org>, draft-ietf-homenet-hncp-bis.all@ietf.org, Ray Bellis <ray@bellis.me.uk>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Jul 2016 23:05:12 -0000

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

A small reminder: while there was clearly a mistake made in including
".home" in this document, from a process perspective an updated document
being worked on by the working group is a working group document, and the
working group can make changes to it.   The document doesn't get published
as a working group document if there isn't consensus to publish it.

So the chairs do not need to "check with the AD" about other changes that
are proposed.   The AD may have specified an accelerated timeline for the
work, so the chairs may say "look, we don't have time for that," but if we
do have time for that, and there is consensus to do it, why on earth would
we not?   If there is a time limit, just say that the change doesn't go in
if there's no consensus to make it before the time limit.

ADs do not get to say what is in documents.   They can refuse to publish,
and they can publish individual submissions if they get IETF consensus, and
they can threaten to close working groups, but any other changes are the
purview of the working group.


On Fri, Jul 8, 2016 at 3:45 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

>
> On Jul 8, 2016, at 12:30 PM 7/8/16, Ray Bellis <ray@bellis.me.uk> wrote:
>
>
>
> On 08/07/2016 17:25, Ralph Droms wrote:
>
> I took a quick look at draft-ietf-homenet-hncp-bis-00, including a
> diff; seems the only change is to solve the .home problem.  I don't
> think I quite understand the new text and here's a suggested
> clarification:
>
> OLD:
>
> A default value for this TLV MUST be set, although the default value
> of the Domain-Name TLV (Section 10.6) is out of scope of this
> document, and an administrator MAY configure the announcement of a
> Domain-Name TLV for the network.
>
> NEW:
>
> The administrator MUST configure the announcement of a network-wide
> zone suffix through the Domain-Name TLV.
>
> As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address
> errata 4718.  While this errata has not yet been verified, in my
> opinion *something* has to be done to correct the text around
> "Multicast DNS Proxy".  If "Multicast DNS Proxy" is intended to refer
> to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, the appropriate
> normative reference will constitute a downref in
> draft-ietf-homenet-hncp-bis-00.
>
>
> The instruction to the authors were to incorporate the original .home
> errata verbatim, and also to fix the error with options 37/38 being the
> wrong way around in two diagrams.
>
>
> I honestly can't understand the new text.  Why a friendly suggestion for a
> simplification need AD intervention?
>
>
> If there is to be further wordsmithing on that we'd need to take that up
> with our AD.
>
> As for errata 4718, I fully expect that it will be incorporated in a
> further revision just as soon as it has been verified (and subject to a
> resolution of any resulting downref issue).
>
>
> OK. As an aside, *something* will have to be done with the text regarding
> "Multicast DNS Proxy" regardless of whether or not the errata is verified.
> I see a couple of ways to read the existing text and the citations of RFC
> 6762.
>
> One way to read RFC 7788 is to assume "Multicast DNS Proxy" refers to the
> "Multicast DNS Proxy Servers" defined in RFC 6762, in which case RFC 7788
> is specifying that an HNCP device should participate in whatever election
> protocol "Multicast DNS Proxy Servers" use to elect the proxy server for a
> link.  That election protocol needs a reference
>
> Another way to read RFC 7788 is that there is no citation for a definition
> of "Multicast DNS Proxy" at all (assuming the citations of RFC 6762 apply
> just to mDNS and not "proxy"), in which case RFC 7788 needs to be amended
> to include that definition of "Multicast DNS Proxy".
>
> Seems like the WG might want to go ahead and figure out which way it wants
> to fix this issue as doing nothing isn't an option.
>
> - Ralph
>
>
> kind regards,
>
> Ray
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<div dir=3D"ltr">A small reminder: while there was clearly a mistake made i=
n including &quot;.home&quot; in this document, from a process perspective =
an updated document being worked on by the working group is a working group=
 document, and the working group can make changes to it. =C2=A0 The documen=
t doesn&#39;t get published as a working group document if there isn&#39;t =
consensus to publish it.<div><br></div><div>So the chairs do not need to &q=
uot;check with the AD&quot; about other changes that are proposed. =C2=A0 T=
he AD may have specified an accelerated timeline for the work, so the chair=
s may say &quot;look, we don&#39;t have time for that,&quot; but if we do h=
ave time for that, and there is consensus to do it, why on earth would we n=
ot? =C2=A0 If there is a time limit, just say that the change doesn&#39;t g=
o in if there&#39;s no consensus to make it before the time limit.</div><di=
v><br></div><div>ADs do not get to say what is in documents. =C2=A0 They ca=
n refuse to publish, and they can publish individual submissions if they ge=
t IETF consensus, and they can threaten to close working groups, but any ot=
her changes are the purview of the working group.=C2=A0</div><div><br></div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Ju=
l 8, 2016 at 3:45 PM, Ralph Droms <span dir=3D"ltr">&lt;<a href=3D"mailto:r=
droms.ietf@gmail.com" target=3D"_blank">rdroms.ietf@gmail.com</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto" style=3D"word-=
wrap:break-word"><br><blockquote type=3D"cite"><span class=3D"">On Jul 8, 2=
016, at 12:30 PM 7/8/16, Ray Bellis &lt;<a href=3D"mailto:ray@bellis.me.uk"=
 target=3D"_blank">ray@bellis.me.uk</a>&gt; wrote:<br><br><br><br></span><s=
pan class=3D"">On 08/07/2016 17:25, Ralph Droms wrote:<br><blockquote type=
=3D"cite">I took a quick look at draft-ietf-homenet-hncp-bis-00, including =
a<br>diff; seems the only change is to solve the .home problem.=C2=A0 I don=
&#39;t<br>think I quite understand the new text and here&#39;s a suggested<=
br>clarification:<br><br>OLD:<br><br>A default value for this TLV MUST be s=
et, although the default value<br>of the Domain-Name TLV (Section 10.6) is =
out of scope of this<br>document, and an administrator MAY configure the an=
nouncement of a<br>Domain-Name TLV for the network.<br><br>NEW:<br><br>The =
administrator MUST configure the announcement of a network-wide<br>zone suf=
fix through the Domain-Name TLV.<br><br>As far as I can tell, draft-ietf-ho=
menet-hncp-bis-00 does not address<br>errata 4718.=C2=A0 While this errata =
has not yet been verified, in my<br>opinion *something* has to be done to c=
orrect the text around<br>&quot;Multicast DNS Proxy&quot;.=C2=A0 If &quot;M=
ulticast DNS Proxy&quot; is intended to refer<br>to &quot;Hybrid Proxy&quot=
; in draft-ietf-dnssd-hybrid-03, the appropriate<br>normative reference wil=
l constitute a downref in<br>draft-ietf-homenet-hncp-bis-00.<br></blockquot=
e><br>The instruction to the authors were to incorporate the original .home=
<br>errata verbatim, and also to fix the error with options 37/38 being the=
<br>wrong way around in two diagrams.<br></span></blockquote><br><span clas=
s=3D"">I honestly can&#39;t understand the new text.=C2=A0 Why a friendly s=
uggestion for a simplification need AD intervention?<br><br></span><blockqu=
ote type=3D"cite"><br><span class=3D"">If there is to be further wordsmithi=
ng on that we&#39;d need to take that up<br>with our AD.<br><br>As for erra=
ta 4718, I fully expect that it will be incorporated in a<br>further revisi=
on just as soon as it has been verified (and subject to a<br>resolution of =
any resulting downref issue).<br></span></blockquote><br><span class=3D"">O=
K. As an aside, *something* will have to be done with the text regarding &q=
uot;Multicast DNS Proxy&quot; regardless of whether or not the errata is ve=
rified.=C2=A0 I see a couple of ways to read the existing text and the cita=
tions of RFC 6762.<div><br></div><div>One way to read RFC 7788 is to assume=
 &quot;Multicast DNS Proxy&quot; refers to the &quot;Multicast DNS Proxy Se=
rvers&quot; defined in RFC 6762, in which case RFC 7788 is specifying that =
an HNCP device should participate in whatever election protocol &quot;Multi=
cast DNS Proxy Servers&quot; use to elect the proxy server for a link.=C2=
=A0 That election protocol needs a reference=C2=A0</div><div><br></div><div=
>Another way to read RFC 7788 is that there is no citation for a definition=
 of &quot;Multicast DNS Proxy&quot; at all (assuming the citations of RFC 6=
762 apply just to mDNS and not &quot;proxy&quot;), in which case RFC 7788 n=
eeds to be amended to include that definition of &quot;Multicast DNS Proxy&=
quot;.<br><br>Seems like the WG might want to go ahead and figure out which=
 way it wants to fix this issue as doing nothing isn&#39;t an option.<br><b=
r>- Ralph<br><br><blockquote type=3D"cite"><br>kind regards,<br><br>Ray<br>=
<br></blockquote><br></div></span></div>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
<br></blockquote></div><br></div>

--001a1140d0ca413372053727d50a--


From nobody Sun Jul 10 11:58:15 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A07312D0C5 for <homenet@ietfa.amsl.com>; Sun, 10 Jul 2016 11:58:14 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 naIBPsLVjQ2P for <homenet@ietfa.amsl.com>; Sun, 10 Jul 2016 11:58:12 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 393CA12D0BF for <homenet@ietf.org>; Sun, 10 Jul 2016 11:58:12 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id q132so56827435lfe.3 for <homenet@ietf.org>; Sun, 10 Jul 2016 11:58:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=CqoRl3iP0/DSWIC+8zVyqJHtqS28TRVeTzbNl9c8tKY=; b=UyxedlxpA6zBBFouCHxLhsXV/AdmmJjEWj91P+Vl5SzfC1z2xbauZHxgILRsFaoNEz Ti+TWGD2n6RUUfE0ltvvvENvwnYh7GeUqPEvvco+6y7rfRnm8BQ8eYe+z9j+bR6TuXGt l9cgQWoAYSY5Zs4nMNjtFdqaMYqVw1NyiZD3ipfyErLDGFzNyUSpekFZB4ZknCHX3+h/ VbLvJ6inDAzITV5E08eTziZXsVwRVCR0+XWUYpdNjoQyPPXMC3xlyv1mXFMH3OmfZeU4 sKpq4QvCG2iQX+Envnwa2Jo33mJbeE/abr2Q01jGo6EkbDFRWWk5AIr0u0qRkmhnxkC3 lNyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CqoRl3iP0/DSWIC+8zVyqJHtqS28TRVeTzbNl9c8tKY=; b=FAOO/QsTD2Lq4Cj9nnmny+RN5MFB2gynwRH+ZhfQdHiOncXp7DmVRuyBMASn6VC3pW sD7epQfShh3GBKPoOSNDrKz6zhvzrJpCX6F/V2OoFt6imx/BeoWpUsB51WPqF3sP1N1S 4xY3yYhbO+ktHq8X+FTVcoqpN2yqhat1RigmiLJYSJXwa6ijqRtDYBihh6ngQBH5ZPGn 0/r3+DZLDyHuX5BwxheU861Gk8PCAAiytCLzQBGF2PAkUh3J4OBbyP4PGCrpp57E0v7w GsCf3Wxzxo4eG1Bxj4xQdGNQaoxp4HR/aproETRYBkswMpvAlktlZ2RCUOOfazd1Jgjp lxlA==
X-Gm-Message-State: ALyK8tKLTgfeUK530G/fmaxyVjLIn6cPHr9mvSD0W4FiKFFtrX4Wd93OXS1zCivJ5r7UEAkZeJJbEX9eMWPBNg==
X-Received: by 10.25.85.200 with SMTP id j191mr3341555lfb.39.1468177090136; Sun, 10 Jul 2016 11:58:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Sun, 10 Jul 2016 11:57:28 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Date: Sun, 10 Jul 2016 11:57:28 -0700
Message-ID: <CAPt1N1m+uS2dpQeD5minLo+U16z4FgxHnHt7_3O=z1YXrEFemw@mail.gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11424d0ceceb7c05374c9d95
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Qwy8huyOQ0-jZDqZl0G_63fqSN0>
Subject: [homenet] New version of homenet naming architecture...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 10 Jul 2016 18:58:14 -0000

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

I published a new version of my proposed homenet naming architecture
document on Friday.   I updated it based on extensive comments from Stuart
and various other folks, but I haven't yet gone through and systematically
figured out if I got everyone's comments.

The draft is in the datatracker here:
https://datatracker.ietf.org/doc/draft-lemon-homenet-naming-architecture/
Diffs from -00 here:
https://tools.ietf.org/rfcdiff?url2=draft-lemon-homenet-naming-architecture-01.txt
github:
https://github.com/Abhayakara/draft-lemon-homenet-naming-architecture

I made the document quite a bit more definite, since I didn't hear any
strenuous objections when I presented it last time.   I'd like to propose
adopting the document as a working group work item.   Thoughts?   Do people
think this is a good direction, or did the lack of objection last time
indicate shocked horror rather than acquiescence?

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

<div dir=3D"ltr">I published a new version of my proposed homenet naming ar=
chitecture document on Friday. =C2=A0 I updated it based on extensive comme=
nts from Stuart and various other folks, but I haven&#39;t yet gone through=
 and systematically figured out if I got everyone&#39;s comments.<div><br><=
/div><div>The draft is in the datatracker here:=C2=A0<a href=3D"https://dat=
atracker.ietf.org/doc/draft-lemon-homenet-naming-architecture/">https://dat=
atracker.ietf.org/doc/draft-lemon-homenet-naming-architecture/</a></div><di=
v>Diffs from -00 here:=C2=A0<a href=3D"https://tools.ietf.org/rfcdiff?url2=
=3Ddraft-lemon-homenet-naming-architecture-01.txt">https://tools.ietf.org/r=
fcdiff?url2=3Ddraft-lemon-homenet-naming-architecture-01.txt</a></div><div>=
github:=C2=A0<a href=3D"https://github.com/Abhayakara/draft-lemon-homenet-n=
aming-architecture">https://github.com/Abhayakara/draft-lemon-homenet-namin=
g-architecture</a></div><div><br></div><div>I made the document quite a bit=
 more definite, since I didn&#39;t hear any strenuous objections when I pre=
sented it last time. =C2=A0 I&#39;d like to propose adopting the document a=
s a working group work item. =C2=A0 Thoughts? =C2=A0 Do people think this i=
s a good direction, or did the lack of objection last time indicate shocked=
 horror rather than acquiescence?</div></div>

--001a11424d0ceceb7c05374c9d95--


From nobody Sat Jul 16 00:42:43 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF7312D667 for <homenet@ietfa.amsl.com>; Sat, 16 Jul 2016 00:42:42 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 NSo34E_d5Xxv for <homenet@ietfa.amsl.com>; Sat, 16 Jul 2016 00:42:40 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5776212D643 for <homenet@ietf.org>; Sat, 16 Jul 2016 00:42:39 -0700 (PDT)
Received: from [46.227.151.81] (port=49154 helo=rays-mbp-3.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bOKFB-0005Ol-It (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Sat, 16 Jul 2016 08:42:37 +0100
To: HOMENET <homenet@ietf.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk>
Date: Sat, 16 Jul 2016 08:42:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/JYIfmj1i2Kc6fvgi1gu2ie3pum4>
Subject: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 16 Jul 2016 07:42:42 -0000

The Chairs have been asked to forward this to the WG on behalf of the IAB:

--8<--8<--

The IAB discussed RFC 7788 and the appearance of the domain ".home" in
the RFC. The IAB was happy to see that an appropriate erratum has been
filed and approved, observing the problem with RFC 7788 and publishing a
fix for the error. The original text in the RFC is problematic, because
the use of .home in this case would constitute use of .home as a Special
Use Name, but there is no text in RFC 7788 following the process in
section 5 of RFC 6761 and no IANA Considerations updating the Special
Use Names registry.

The IAB requests that the homenet WG and the IESG follow up on the
publication of the erratum for RFC 7788 with the re-approval of the RFC
with a fix as quickly as possible. The IAB feels strongly that a
correct, formal RFC is required immediately to avoid any further
problems. Also, sending a timely note to the implementors known to be
interested in HOMENET may be useful.

The IAB considers the existence of RFC 7788 in its current state to be
problematic for two reasons: the specification of home in an IETF
document without following the appropriate RFC 6761 process may result
in other organizations pointing out that the IETF can't even follow its
own processes with regard to Special Use Names; and encoding .home as
the default in implementations may result in embedding this
inappropriate use of .home in deployed products.]

--8<--8<--

There is some time set aside on our agenda on Monday for Jari to speak
about this.

In the meantime, please note that the RFC 7788 authors have filed a -bis
draft (draft-ietf-homenet-hncp-bis-00).

thanks,

Ray and Mark


From nobody Sat Jul 16 01:50:12 2016
Return-Path: <terry.manderson@icann.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5990A12D67F for <homenet@ietfa.amsl.com>; Sat, 16 Jul 2016 01:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level: 
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 B-zhZpSBFGU1 for <homenet@ietfa.amsl.com>; Sat, 16 Jul 2016 01:50:09 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2231112B057 for <homenet@ietf.org>; Sat, 16 Jul 2016 01:50:09 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 16 Jul 2016 01:50:06 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Sat, 16 Jul 2016 01:50:06 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Ray Bellis <ray@bellis.me.uk>, HOMENET <homenet@ietf.org>
Thread-Topic: [homenet] RFC 7788 and ".home"
Thread-Index: AQHR3zWyxpSNp4RjaE2KKFwnC71EkaAb3KUA
Date: Sat, 16 Jul 2016 08:50:06 +0000
Message-ID: <D3B0315C.95E19%terry.manderson@icann.org>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk>
In-Reply-To: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3551539802_1119405"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/FKBsbqQal_m8jth-yNN_1iswS7A>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 16 Jul 2016 08:50:10 -0000

--B_3551539802_1119405
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Thanks Ray,

I would also like the WG to read this draft before entering the discussion
on this topic.

https://datatracker.ietf.org/doc/draft-stw-whatsinaname

While currently a -00 individual submission there is some very good
guidance in this document that might help frame everyone's thoughts.

Thanks
Terry

On 16/07/2016, 5:42 PM, "homenet on behalf of Ray Bellis"
<homenet-bounces@ietf.org on behalf of ray@bellis.me.uk> wrote:

>The Chairs have been asked to forward this to the WG on behalf of the IAB:
>
>--8<--8<--
>
>The IAB discussed RFC 7788 and the appearance of the domain ".home" in
>the RFC. The IAB was happy to see that an appropriate erratum has been
>filed and approved, observing the problem with RFC 7788 and publishing a
>fix for the error. The original text in the RFC is problematic, because
>the use of .home in this case would constitute use of .home as a Special
>Use Name, but there is no text in RFC 7788 following the process in
>section 5 of RFC 6761 and no IANA Considerations updating the Special
>Use Names registry.
>
>The IAB requests that the homenet WG and the IESG follow up on the
>publication of the erratum for RFC 7788 with the re-approval of the RFC
>with a fix as quickly as possible. The IAB feels strongly that a
>correct, formal RFC is required immediately to avoid any further
>problems. Also, sending a timely note to the implementors known to be
>interested in HOMENET may be useful.
>
>The IAB considers the existence of RFC 7788 in its current state to be
>problematic for two reasons: the specification of home in an IETF
>document without following the appropriate RFC 6761 process may result
>in other organizations pointing out that the IETF can't even follow its
>own processes with regard to Special Use Names; and encoding .home as
>the default in implementations may result in embedding this
>inappropriate use of .home in deployed products.]
>
>--8<--8<--
>
>There is some time set aside on our agenda on Monday for Jari to speak
>about this.
>
>In the meantime, please note that the RFC 7788 authors have filed a -bis
>draft (draft-ietf-homenet-hncp-bis-00).
>
>thanks,
>
>Ray and Mark
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet

--B_3551539802_1119405
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFLtG
k+xzOgniv6eoWUbUnG9DM3OEMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE2MDcxNjA4NTAwMlowDQYJKoZIhvcNAQEBBQAEggEAvbU2JYjIwYNl4zsufwin
zXxggeupxfhMzVrlZHUOG8EMvuwdH1JPdalt5KKGa2Cki8Vnsv+IfdyTaL3qAlyoYUe2+Ll/
Mhu0hGtwYdtuTIlOaXn5aODnIiXFPVr+iE/lwjwxCSRHHOn7kLr2frKGxkkl3yiCSZA/jsXU
EJNLtb1Gh9wewBaIwUqMjmwFuEh0ZRzk/2TQ0BuIN4fEwZv5dl1lUy+qC+3F8JmHx9rRupRI
Nxbj+TZx7y7m6RO3wX5mcev4VSBZCpjG1BT4u6Dk6TkTHcgkmP9PJcSH3QzSuSCChD5m7TDA
aqVCF5DUw8ubC8GOqPzi+hpSw7BpcZtzCQ==

--B_3551539802_1119405--


From nobody Sat Jul 16 01:56:08 2016
Return-Path: <terry.manderson@icann.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD44812D7B0; Sat, 16 Jul 2016 01:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level: 
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Jgu6_MEeWeU3; Sat, 16 Jul 2016 01:56:04 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 484F112D789; Sat, 16 Jul 2016 01:56:04 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 16 Jul 2016 01:56:01 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Sat, 16 Jul 2016 01:56:01 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Ray Bellis <ray@bellis.me.uk>, Ralph Droms <rdroms.ietf@gmail.com>, "draft-ietf-homenet-hncp-bis.all@ietf.org" <draft-ietf-homenet-hncp-bis.all@ietf.org>
Thread-Topic: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
Thread-Index: AQHR2SPgDQuDVBZ0PUW5EmIhWgIqd6APLbQAgAABYICADLtdAA==
Date: Sat, 16 Jul 2016 08:56:00 +0000
Message-ID: <D3B0327A.95E1E%terry.manderson@icann.org>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
In-Reply-To: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3551540158_1101239"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/LPtgwDuXcn_KsW-1qmH_UoDjhsw>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 16 Jul 2016 08:56:06 -0000

--B_3551540158_1101239
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit



On 9/07/2016, 2:30 AM, "Ray Bellis" <ray@bellis.me.uk> wrote:
>
>The instruction to the authors were to incorporate the original .home
>errata verbatim, and also to fix the error with options 37/38 being the
>wrong way around in two diagrams.
>
>If there is to be further wordsmithing on that we'd need to take that up
>with our AD.

So let me clarify a point, the direction from me was to use the errata
wording verbatim in the initial BIS as that forms the start point of the
discussion.

Beyond that, if the WG comes to a consensus to either use that text or
other text after fuller discussion, that will be a WG decision and not
explicitly my decision. The solution must be a WG solution yet respect
IETF processes.

Cheers
Terry

--B_3551540158_1101239
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFNFO
6PQru+fz85YV9MrdgEBzi6vJMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE2MDcxNjA4NTU1OFowDQYJKoZIhvcNAQEBBQAEggEAlEniQV6yrKvcf/IYioTU
rA0lccsVYscFMd/HZUOCXCvoAyCx1APVHH0/kPyVgT+G1fx8WUQ0PIdL3nvKcVOEBNDoyHos
mOVy7U682LDNUmyV+Dv0wz9M2YRfeMtkUuSGoSCeqRClTlDP1u7iSZUN5+RsKctaGgQHjoYm
Y/Q/9qdicOmehZVwhAa6K8bxcwsmmNDUJJxGbzU+QSmDr2Y6/GpqxoDNw77z02ehMHIRTUEJ
c7z39EYOmakB6jjtl+OaBhL2/R5p4YTrGA/+uCl4rNbyjLVyZHnBGLNct6PPFfh54zqgF7Hu
5uq62kI9Z9HfJ+bftVVh1hxMII3eIq91Qg==

--B_3551540158_1101239--


From nobody Sat Jul 16 01:57:36 2016
Return-Path: <terry.manderson@icann.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1595512D7D2; Sat, 16 Jul 2016 01:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level: 
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 5-JiitEYZk5y; Sat, 16 Jul 2016 01:57:33 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4FDA12D7B0; Sat, 16 Jul 2016 01:57:33 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 16 Jul 2016 01:57:30 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Sat, 16 Jul 2016 01:57:31 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Ted Lemon <mellon@fugue.com>, Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
Thread-Index: AQHR2SPgDQuDVBZ0PUW5EmIhWgIqd6APLbQAgAABYICAAGjGgIAABVIAgAxNsAA=
Date: Sat, 16 Jul 2016 08:57:30 +0000
Message-ID: <D3B033EE.95E22%terry.manderson@icann.org>
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com> <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk> <C407F615-99A5-44F2-B719-9C26FC04094C@gmail.com> <CAPt1N1n9rL_Ybr=PSJaMTm-zD1atM6V15g3gi83BOzr2ivm5eA@mail.gmail.com>
In-Reply-To: <CAPt1N1n9rL_Ybr=PSJaMTm-zD1atM6V15g3gi83BOzr2ivm5eA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3551540248_1125089"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/KgDnr0zxZdQthBC0cTUm0GD0Yq0>
Cc: HOMENET <homenet@ietf.org>, "draft-ietf-homenet-hncp-bis.all@ietf.org" <draft-ietf-homenet-hncp-bis.all@ietf.org>, Ray Bellis <ray@bellis.me.uk>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 16 Jul 2016 08:57:35 -0000

--B_3551540248_1125089
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit



On 9/07/2016, 9:04 AM, "homenet on behalf of Ted Lemon"
<homenet-bounces@ietf.org on behalf of mellon@fugue.com> wrote:
>
>
>ADs do not get to say what is in documents.   They can refuse to publish,
>and they can publish individual submissions if they get IETF consensus,
>and they can threaten to close working groups, but any other changes are
>the purview of the working group.
>

Correct.

:)

Terry

--B_3551540248_1125089
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFKVW
VkrZSlrqc9d62/kryeavdIgtMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE2MDcxNjA4NTcyOFowDQYJKoZIhvcNAQEBBQAEggEAvZWnaTeti8wr8RyXL5L9
RFI9pwdiFaHFzM4dD3FdG9iT/A0z4Zi1dhBqviJvyr+bs0UIs4jV/Ki1mQ4FrYRhHd0mKMrE
HWEj4LR/OogcUg1TSKCnbYO58jPK3LwMjymiVLegoZKoJTLrMDwuHBXztZo3COO33m5f7Tey
TmkpstToggzW+ZU0EVP7kYrFlC12eyIaMTCTnDw1Z/NtFjZeVPGcWbKE8tnyKLs+M3VehByb
W6zi/0n1DyGtNIkC4y3x1Uo+oX/RoVnQHltErjHNeLbYzCRPowarQ6837jApIyX4IRuEulxI
DnY7ybasDGIuKTngnrTmujn8CxEFyAzGsA==

--B_3551540248_1125089--


From nobody Sun Jul 17 15:34:24 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666DB12B02C for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:34:23 -0700 (PDT)
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 autolearn_force=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 KZ_sg3poYgOe for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:34:21 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 7905012B00D for <homenet@ietf.org>; Sun, 17 Jul 2016 15:34:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 504D510D27 for <homenet@ietf.org>; Sun, 17 Jul 2016 22:34:20 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcJGrZiqgIIR for <homenet@ietf.org>; Sun, 17 Jul 2016 22:34:19 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-8e13.meeting.ietf.org [31.133.142.19]) by mx2.yitter.info (Postfix) with ESMTPSA id 27A96105A5 for <homenet@ietf.org>; Sun, 17 Jul 2016 22:34:19 +0000 (UTC)
Date: Sun, 17 Jul 2016 18:34:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160717223416.GB40669@mx2.yitter.info>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <20160617010044.GA22195@mx2.yitter.info> <4e794ce6-2605-a0d2-c0e7-fe44bb149794@bellis.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4e794ce6-2605-a0d2-c0e7-fe44bb149794@bellis.me.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YjvJb5YbgwihPWOLHFJ-hSHBDeg>
Subject: Re: [homenet] RFC 7788-bis (and also draft-cheshire-homenet-dot-home-03)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 17 Jul 2016 22:34:23 -0000

Dear colleagues,

On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:

> Whilst there may be "undermined" ways it's being used, it's clear that
> most of the ways it's used are just because some vendors and sites
> decided to use that for their default *site local* domain which makes it
> completely consistent with what we need.
> 
> I therefore completely disagree on point #1 - officially allocating
> .home for this purpose and having it "sunk" by default on internet
> facing recursive resolvers would IMHO actually *help* with the traffic
> hitting the root and reduce leakage of it.

The argument above, which is rehearsed to some extent in
draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),
is interesting to me, in that it appears to start with the exact same
premises I do and reach the exact opposite conclusion.  I believe this
is because of some unstated premises, and so I'm going to attempt to
lay out the premises as I understand them as completely as I can.

To do this, I'm going to draw some inferences about what Ray was
arguing and about what is in draft-cheshire-homenet-dot-home-03.  I
hope the authors indulge me, and I hope you, Gentle Reader, do not
mistake my inferences as speaking correctly either for Ray or for
Stuart.  Since they're both here, they can correct what I get wrong;
but I think trying to lay out this different story might help us.

I think we all agree that the label home, in the top-most position of
a domain name (but maybe not a name in the DNS), is in use by some
people.  I think we all agree that at least some uses of that name are
somehow related to "stuff in my house behind my home-router-like
thing".  And I think we all agree that, whatever basis for that use
is, it either is not or ought not to be related to any actual
delegation of the name in the DNS.

With the above premises, I conclude that home is by definition not
suitable for our purposes.  I conclude that from these additional
premises:

    â€˘ that, given the detectable pollution of the namespace at and
      beneath home, there is a significant population already using
      the name for some purposes, we know not what;

    â€˘ that if we want an identifier to be some sort of protocol switch
      by which we tell software to do something novel, we need an
      identifier that has at least a modest chance of not running into
      widely-deployed use for some purpose not defined to be
      consistent with the protocol switch;

    â€˘ that it is at least fantastically difficult to suss out all the
      strange things people are already doing with "in the wild"
      undelegated names in the DNS, even if we make the dubious
      assumption that there is something like a rigorous design behind
      those doings;

    â€˘ that strings that could be used as protocol switches are
      fundamentally machine-directed rather than human-directed, and
      therefore have a certain arbitrariness about them.

With the same premises, I think the opposite argument is that home is
entirely good for our purposes, because of the following additional
premises:

    â€˘ that we have (or we can get, which is what
      draft-cheshire-homenet-dot-home-03 is asking for) a pretty clear
      idea that all the uses of home are already more or less what
      we're trying to do;

    â€˘ that picking the same string is very unlikely to break any of
      the existing behaviour;

    â€˘ that a meaningful string to a human user is of high importance
      here;

    â€˘ that a primary (or even important secondary) motivation for the
      allocation would be to capture traffic that should never have
      been destined for the root in the first place;

    â€˘ that with adequate documentation, a possibly-conflicting use of
      home would not have negative effects.




I think the effort to document what people are actually doing with
home is laudable, and I hope it succeeds in producing a more-or-less
complete account of the use of that name.  But I do not see how we can
get from "documenting these uses is good" to "having documented it,
you can then use the name that way."  The kind of exhaustive survey
that would be needed to show the real uses of home would cost far more
in time, effort, and money than the convenience of the string
presents.  Moreover, it's not even clear that this would be the
"right" string.  For lots of people on Earth don't use Latin writing,
never mind English words.

I hope this explains why I think proceeding with home is problematic.

Andrew (speaking only for myself).

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Sun Jul 17 15:39:09 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED45612B018 for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:39:08 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jfNRuNEu_jxO for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:39:06 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1410512B00E for <homenet@ietf.org>; Sun, 17 Jul 2016 15:39:06 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id g62so10057962lfe.3 for <homenet@ietf.org>; Sun, 17 Jul 2016 15:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4tmDonKpqWPtcfuDSjuLxlT2js3tvx4vkZ4RQeDkD+0=; b=hPJcTYAQ2eWBU6thrJqdX4HkjWYsKekC5VXGfo9vr036UII1XJPQujRCToWdStcKow b/IeuyGLgdg/0f+W9zles3txyWnM3X6QNvvoTfBEBVdvn4yxTTkQjqkI+ww+HIThrMH0 lZN0T8M4cN1frz+M7aWCbrGmenLXON3VDOtWnfwSu1NTFAk1vekUJRMzr/BcS923ArPW ILaBKhZf4pdV6dgoZUNLTfp/Jdw7ddxa3rbfX9xwLM+h73N35RDyswfAJKgTtzTO2Zey usRkksG1TrxjXJagQ7UXqeJWm8nppKv0HprkCmdPzHhA3HzZy4SevTVl+kLf5wFeKI5t R39g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4tmDonKpqWPtcfuDSjuLxlT2js3tvx4vkZ4RQeDkD+0=; b=FJT1Tc6752ReV9O2Yp9gXEjbE9KKnb/nSV01hQSMOynesTr9s2F1/Ngs7IJZP8iswY xONknTDIP2Lbl0t8cNIVMu7icmRg8jwtRCTFuuhkEUZrfod4TiNgqgDxI4ywwpSntEQP hnZwIX5nE1AF3/WAJiQ6oMJzXd/RQlo5KJtCTyt5OvU+DHiB3cRhP8XRdQrMOJAgNEYT GKB9V8YLda+PRqBFoISaWQm3OqbuqZgWCs26hWoWzPZT9y7WV+88ASpw/QiycgjzbT5R My+0SIBVDrh3VBb3f5asXh/8aWbkSSXFNquk1YlZeqbDLF+Ns0hXbRHFYa9oIZb3vNqn qLXw==
X-Gm-Message-State: ALyK8tKfrSnYpnHj+LAJyzJl8wd2mAB7yX8uNGRcn/2N9L1FzIB6LVl3mTgWyQIFEEWuND74cmVTYD6t2W2MOQ==
X-Received: by 10.25.159.10 with SMTP id i10mr3043063lfe.131.1468795144181; Sun, 17 Jul 2016 15:39:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Sun, 17 Jul 2016 15:38:24 -0700 (PDT)
In-Reply-To: <20160717223416.GB40669@mx2.yitter.info>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <20160617010044.GA22195@mx2.yitter.info> <4e794ce6-2605-a0d2-c0e7-fe44bb149794@bellis.me.uk> <20160717223416.GB40669@mx2.yitter.info>
From: Ted Lemon <mellon@fugue.com>
Date: Sun, 17 Jul 2016 18:38:24 -0400
Message-ID: <CAPt1N1ngRGChXV_b6z9C_drWNMKccEPt7nKs1DE5_L055GMHHg@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a11411c42d128860537dc843b
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ZyCN9-ix4R5-C_r808oPQ2Me7qc>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788-bis (and also draft-cheshire-homenet-dot-home-03)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 17 Jul 2016 22:39:09 -0000

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

Violent agreement here.   Hence, ".homenet".   :)

On Sun, Jul 17, 2016 at 6:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Dear colleagues,
>
> On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:
>
> > Whilst there may be "undermined" ways it's being used, it's clear that
> > most of the ways it's used are just because some vendors and sites
> > decided to use that for their default *site local* domain which makes i=
t
> > completely consistent with what we need.
> >
> > I therefore completely disagree on point #1 - officially allocating
> > .home for this purpose and having it "sunk" by default on internet
> > facing recursive resolvers would IMHO actually *help* with the traffic
> > hitting the root and reduce leakage of it.
>
> The argument above, which is rehearsed to some extent in
> draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),
> is interesting to me, in that it appears to start with the exact same
> premises I do and reach the exact opposite conclusion.  I believe this
> is because of some unstated premises, and so I'm going to attempt to
> lay out the premises as I understand them as completely as I can.
>
> To do this, I'm going to draw some inferences about what Ray was
> arguing and about what is in draft-cheshire-homenet-dot-home-03.  I
> hope the authors indulge me, and I hope you, Gentle Reader, do not
> mistake my inferences as speaking correctly either for Ray or for
> Stuart.  Since they're both here, they can correct what I get wrong;
> but I think trying to lay out this different story might help us.
>
> I think we all agree that the label home, in the top-most position of
> a domain name (but maybe not a name in the DNS), is in use by some
> people.  I think we all agree that at least some uses of that name are
> somehow related to "stuff in my house behind my home-router-like
> thing".  And I think we all agree that, whatever basis for that use
> is, it either is not or ought not to be related to any actual
> delegation of the name in the DNS.
>
> With the above premises, I conclude that home is by definition not
> suitable for our purposes.  I conclude that from these additional
> premises:
>
>     =E2=80=A2 that, given the detectable pollution of the namespace at an=
d
>       beneath home, there is a significant population already using
>       the name for some purposes, we know not what;
>
>     =E2=80=A2 that if we want an identifier to be some sort of protocol s=
witch
>       by which we tell software to do something novel, we need an
>       identifier that has at least a modest chance of not running into
>       widely-deployed use for some purpose not defined to be
>       consistent with the protocol switch;
>
>     =E2=80=A2 that it is at least fantastically difficult to suss out all=
 the
>       strange things people are already doing with "in the wild"
>       undelegated names in the DNS, even if we make the dubious
>       assumption that there is something like a rigorous design behind
>       those doings;
>
>     =E2=80=A2 that strings that could be used as protocol switches are
>       fundamentally machine-directed rather than human-directed, and
>       therefore have a certain arbitrariness about them.
>
> With the same premises, I think the opposite argument is that home is
> entirely good for our purposes, because of the following additional
> premises:
>
>     =E2=80=A2 that we have (or we can get, which is what
>       draft-cheshire-homenet-dot-home-03 is asking for) a pretty clear
>       idea that all the uses of home are already more or less what
>       we're trying to do;
>
>     =E2=80=A2 that picking the same string is very unlikely to break any =
of
>       the existing behaviour;
>
>     =E2=80=A2 that a meaningful string to a human user is of high importa=
nce
>       here;
>
>     =E2=80=A2 that a primary (or even important secondary) motivation for=
 the
>       allocation would be to capture traffic that should never have
>       been destined for the root in the first place;
>
>     =E2=80=A2 that with adequate documentation, a possibly-conflicting us=
e of
>       home would not have negative effects.
>
>
>
>
> I think the effort to document what people are actually doing with
> home is laudable, and I hope it succeeds in producing a more-or-less
> complete account of the use of that name.  But I do not see how we can
> get from "documenting these uses is good" to "having documented it,
> you can then use the name that way."  The kind of exhaustive survey
> that would be needed to show the real uses of home would cost far more
> in time, effort, and money than the convenience of the string
> presents.  Moreover, it's not even clear that this would be the
> "right" string.  For lots of people on Earth don't use Latin writing,
> never mind English words.
>
> I hope this explains why I think proceeding with home is problematic.
>
> Andrew (speaking only for myself).
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">Violent agreement here. =C2=A0 Hence, &quot;.homenet&quot;=
. =C2=A0 :)</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sun, Jul 17, 2016 at 6:34 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear colleagues=
,<br>
<br>
On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:<br>
<br>
&gt; Whilst there may be &quot;undermined&quot; ways it&#39;s being used, i=
t&#39;s clear that<br>
&gt; most of the ways it&#39;s used are just because some vendors and sites=
<br>
&gt; decided to use that for their default *site local* domain which makes =
it<br>
&gt; completely consistent with what we need.<br>
&gt;<br>
&gt; I therefore completely disagree on point #1 - officially allocating<br=
>
&gt; .home for this purpose and having it &quot;sunk&quot; by default on in=
ternet<br>
&gt; facing recursive resolvers would IMHO actually *help* with the traffic=
<br>
&gt; hitting the root and reduce leakage of it.<br>
<br>
The argument above, which is rehearsed to some extent in<br>
draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),<br>
is interesting to me, in that it appears to start with the exact same<br>
premises I do and reach the exact opposite conclusion.=C2=A0 I believe this=
<br>
is because of some unstated premises, and so I&#39;m going to attempt to<br=
>
lay out the premises as I understand them as completely as I can.<br>
<br>
To do this, I&#39;m going to draw some inferences about what Ray was<br>
arguing and about what is in draft-cheshire-homenet-dot-home-03.=C2=A0 I<br=
>
hope the authors indulge me, and I hope you, Gentle Reader, do not<br>
mistake my inferences as speaking correctly either for Ray or for<br>
Stuart.=C2=A0 Since they&#39;re both here, they can correct what I get wron=
g;<br>
but I think trying to lay out this different story might help us.<br>
<br>
I think we all agree that the label home, in the top-most position of<br>
a domain name (but maybe not a name in the DNS), is in use by some<br>
people.=C2=A0 I think we all agree that at least some uses of that name are=
<br>
somehow related to &quot;stuff in my house behind my home-router-like<br>
thing&quot;.=C2=A0 And I think we all agree that, whatever basis for that u=
se<br>
is, it either is not or ought not to be related to any actual<br>
delegation of the name in the DNS.<br>
<br>
With the above premises, I conclude that home is by definition not<br>
suitable for our purposes.=C2=A0 I conclude that from these additional<br>
premises:<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that, given the detectable pollution of the namespa=
ce at and<br>
=C2=A0 =C2=A0 =C2=A0 beneath home, there is a significant population alread=
y using<br>
=C2=A0 =C2=A0 =C2=A0 the name for some purposes, we know not what;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that if we want an identifier to be some sort of pr=
otocol switch<br>
=C2=A0 =C2=A0 =C2=A0 by which we tell software to do something novel, we ne=
ed an<br>
=C2=A0 =C2=A0 =C2=A0 identifier that has at least a modest chance of not ru=
nning into<br>
=C2=A0 =C2=A0 =C2=A0 widely-deployed use for some purpose not defined to be=
<br>
=C2=A0 =C2=A0 =C2=A0 consistent with the protocol switch;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that it is at least fantastically difficult to suss=
 out all the<br>
=C2=A0 =C2=A0 =C2=A0 strange things people are already doing with &quot;in =
the wild&quot;<br>
=C2=A0 =C2=A0 =C2=A0 undelegated names in the DNS, even if we make the dubi=
ous<br>
=C2=A0 =C2=A0 =C2=A0 assumption that there is something like a rigorous des=
ign behind<br>
=C2=A0 =C2=A0 =C2=A0 those doings;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that strings that could be used as protocol switche=
s are<br>
=C2=A0 =C2=A0 =C2=A0 fundamentally machine-directed rather than human-direc=
ted, and<br>
=C2=A0 =C2=A0 =C2=A0 therefore have a certain arbitrariness about them.<br>
<br>
With the same premises, I think the opposite argument is that home is<br>
entirely good for our purposes, because of the following additional<br>
premises:<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that we have (or we can get, which is what<br>
=C2=A0 =C2=A0 =C2=A0 draft-cheshire-homenet-dot-home-03 is asking for) a pr=
etty clear<br>
=C2=A0 =C2=A0 =C2=A0 idea that all the uses of home are already more or les=
s what<br>
=C2=A0 =C2=A0 =C2=A0 we&#39;re trying to do;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that picking the same string is very unlikely to br=
eak any of<br>
=C2=A0 =C2=A0 =C2=A0 the existing behaviour;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that a meaningful string to a human user is of high=
 importance<br>
=C2=A0 =C2=A0 =C2=A0 here;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that a primary (or even important secondary) motiva=
tion for the<br>
=C2=A0 =C2=A0 =C2=A0 allocation would be to capture traffic that should nev=
er have<br>
=C2=A0 =C2=A0 =C2=A0 been destined for the root in the first place;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that with adequate documentation, a possibly-confli=
cting use of<br>
=C2=A0 =C2=A0 =C2=A0 home would not have negative effects.<br>
<br>
<br>
<br>
<br>
I think the effort to document what people are actually doing with<br>
home is laudable, and I hope it succeeds in producing a more-or-less<br>
complete account of the use of that name.=C2=A0 But I do not see how we can=
<br>
get from &quot;documenting these uses is good&quot; to &quot;having documen=
ted it,<br>
you can then use the name that way.&quot;=C2=A0 The kind of exhaustive surv=
ey<br>
that would be needed to show the real uses of home would cost far more<br>
in time, effort, and money than the convenience of the string<br>
presents.=C2=A0 Moreover, it&#39;s not even clear that this would be the<br=
>
&quot;right&quot; string.=C2=A0 For lots of people on Earth don&#39;t use L=
atin writing,<br>
never mind English words.<br>
<br>
I hope this explains why I think proceeding with home is problematic.<br>
<br>
Andrew (speaking only for myself).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</font></span></blockquote></div><br></div>

--001a11411c42d128860537dc843b--


From nobody Sun Jul 17 15:47:48 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C750D12B018 for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:47:46 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 vvmcSiQGmuUQ for <homenet@ietfa.amsl.com>; Sun, 17 Jul 2016 15:47:44 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556B812B00D for <homenet@ietf.org>; Sun, 17 Jul 2016 15:47:44 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id l69so63231247lfg.1 for <homenet@ietf.org>; Sun, 17 Jul 2016 15:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=whuuV9d+/hyECeFn2wYTwLhPOBJ+3Umr2tMyE0L90jY=; b=d+05cGgsJFnHXAjgdLkZknHzjJD1smRfFf+BvyHPs4o7kLEzra8AzUvNohsakKxRZL UIXcqFk9wRjRLk7Um5+qovDErRf5zJZW0RK4DWXla//2C2+Oec7aboSAJKp9AOvcStto 6BXW7N1fQ9zorzqSXp0FQIghmBpSm7xnDY9uVbHcvXlOJrwP0lSWqR0DQXB1nZLSuhzQ AePeZLj6MU5Enf5atpxcgMlqWHFPSWgyTylo5pm4RZ2lD/F7jHcauc81LuCVLi9ir1t+ /zyXXpRtQlKfYYy5PMcQyP5upJu99Yrbe4xviwqd5yUMECjj9VqnOMPjKcShKDfNQ+nX MjaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=whuuV9d+/hyECeFn2wYTwLhPOBJ+3Umr2tMyE0L90jY=; b=ffLyGijWceRQDk46Q0Kc7FuwIIB9WzYVJqK5Wt0zJsZVJb1VAJfoMqZT6pQRBAeCm2 fHqiRa+DinwIFsEcF+lRdFm7x7K4YdE/ns1R0RrSxdomnscfDU+h/oEStFA0bW+vl64p uqGtJnm3yRzIn2lPBph0JJeTY5xWOAniF7ihLmp62jr3Fm939lumUVr/V+xOzSCDFRrN 9NGCtqJO50tmW4kxYGZtByaJYE0o1k+CXykV8sI7fCpvPkN3fVhf8zllap8/NvZVuK42 zXqlMAj+hXLmKbyYyx0HyKUGrCLvNS02akTrldivGXDq0bX4iyhXKPkPjA5Nrb7irVVQ QiYw==
X-Gm-Message-State: ALyK8tJTBIFf3aUxNrO+zm8rF5s+wY8YFP/ycBSr+Qcivqms9+QcOpdrkgMJTXvaZhMZZJeH6p7HzcOe9v7/yg==
X-Received: by 10.25.152.135 with SMTP id a129mr12365916lfe.226.1468795263820;  Sun, 17 Jul 2016 15:41:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Sun, 17 Jul 2016 15:40:24 -0700 (PDT)
In-Reply-To: <CAPt1N1ngRGChXV_b6z9C_drWNMKccEPt7nKs1DE5_L055GMHHg@mail.gmail.com>
References: <76ed7404-35ff-9cc8-262b-d5785595465c@isc.org> <20160617010044.GA22195@mx2.yitter.info> <4e794ce6-2605-a0d2-c0e7-fe44bb149794@bellis.me.uk> <20160717223416.GB40669@mx2.yitter.info> <CAPt1N1ngRGChXV_b6z9C_drWNMKccEPt7nKs1DE5_L055GMHHg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Sun, 17 Jul 2016 18:40:24 -0400
Message-ID: <CAPt1N1mn9j2rQUoC+C9J5WFxaOtu04xpk4aRAYtb9FU9qEq=+g@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a114035e2f2bb360537dc8b83
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/KsLsQyot0FOBb_Dg4BhW9sgD760>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788-bis (and also draft-cheshire-homenet-dot-home-03)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 17 Jul 2016 22:47:47 -0000

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

BTW, to do your excellent disquisition on this topic a tiny bit more
justice, I think the point where you and Stuart probably disagree is that
you want to take into account networks that will use homenet router
technology that are already using .home for something else, whereas Stuart
doesn't think this is a real use case.

I agree with you that it is a real use case we need to account for.

On Sun, Jul 17, 2016 at 6:38 PM, Ted Lemon <mellon@fugue.com> wrote:

> Violent agreement here.   Hence, ".homenet".   :)
>
> On Sun, Jul 17, 2016 at 6:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
>
>> Dear colleagues,
>>
>> On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:
>>
>> > Whilst there may be "undermined" ways it's being used, it's clear that
>> > most of the ways it's used are just because some vendors and sites
>> > decided to use that for their default *site local* domain which makes =
it
>> > completely consistent with what we need.
>> >
>> > I therefore completely disagree on point #1 - officially allocating
>> > .home for this purpose and having it "sunk" by default on internet
>> > facing recursive resolvers would IMHO actually *help* with the traffic
>> > hitting the root and reduce leakage of it.
>>
>> The argument above, which is rehearsed to some extent in
>> draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),
>> is interesting to me, in that it appears to start with the exact same
>> premises I do and reach the exact opposite conclusion.  I believe this
>> is because of some unstated premises, and so I'm going to attempt to
>> lay out the premises as I understand them as completely as I can.
>>
>> To do this, I'm going to draw some inferences about what Ray was
>> arguing and about what is in draft-cheshire-homenet-dot-home-03.  I
>> hope the authors indulge me, and I hope you, Gentle Reader, do not
>> mistake my inferences as speaking correctly either for Ray or for
>> Stuart.  Since they're both here, they can correct what I get wrong;
>> but I think trying to lay out this different story might help us.
>>
>> I think we all agree that the label home, in the top-most position of
>> a domain name (but maybe not a name in the DNS), is in use by some
>> people.  I think we all agree that at least some uses of that name are
>> somehow related to "stuff in my house behind my home-router-like
>> thing".  And I think we all agree that, whatever basis for that use
>> is, it either is not or ought not to be related to any actual
>> delegation of the name in the DNS.
>>
>> With the above premises, I conclude that home is by definition not
>> suitable for our purposes.  I conclude that from these additional
>> premises:
>>
>>     =E2=80=A2 that, given the detectable pollution of the namespace at a=
nd
>>       beneath home, there is a significant population already using
>>       the name for some purposes, we know not what;
>>
>>     =E2=80=A2 that if we want an identifier to be some sort of protocol =
switch
>>       by which we tell software to do something novel, we need an
>>       identifier that has at least a modest chance of not running into
>>       widely-deployed use for some purpose not defined to be
>>       consistent with the protocol switch;
>>
>>     =E2=80=A2 that it is at least fantastically difficult to suss out al=
l the
>>       strange things people are already doing with "in the wild"
>>       undelegated names in the DNS, even if we make the dubious
>>       assumption that there is something like a rigorous design behind
>>       those doings;
>>
>>     =E2=80=A2 that strings that could be used as protocol switches are
>>       fundamentally machine-directed rather than human-directed, and
>>       therefore have a certain arbitrariness about them.
>>
>> With the same premises, I think the opposite argument is that home is
>> entirely good for our purposes, because of the following additional
>> premises:
>>
>>     =E2=80=A2 that we have (or we can get, which is what
>>       draft-cheshire-homenet-dot-home-03 is asking for) a pretty clear
>>       idea that all the uses of home are already more or less what
>>       we're trying to do;
>>
>>     =E2=80=A2 that picking the same string is very unlikely to break any=
 of
>>       the existing behaviour;
>>
>>     =E2=80=A2 that a meaningful string to a human user is of high import=
ance
>>       here;
>>
>>     =E2=80=A2 that a primary (or even important secondary) motivation fo=
r the
>>       allocation would be to capture traffic that should never have
>>       been destined for the root in the first place;
>>
>>     =E2=80=A2 that with adequate documentation, a possibly-conflicting u=
se of
>>       home would not have negative effects.
>>
>>
>>
>>
>> I think the effort to document what people are actually doing with
>> home is laudable, and I hope it succeeds in producing a more-or-less
>> complete account of the use of that name.  But I do not see how we can
>> get from "documenting these uses is good" to "having documented it,
>> you can then use the name that way."  The kind of exhaustive survey
>> that would be needed to show the real uses of home would cost far more
>> in time, effort, and money than the convenience of the string
>> presents.  Moreover, it's not even clear that this would be the
>> "right" string.  For lots of people on Earth don't use Latin writing,
>> never mind English words.
>>
>> I hope this explains why I think proceeding with home is problematic.
>>
>> Andrew (speaking only for myself).
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>
>

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

<div dir=3D"ltr">BTW, to do your excellent disquisition on this topic a tin=
y bit more justice, I think the point where you and Stuart probably disagre=
e is that you want to take into account networks that will use homenet rout=
er technology that are already using .home for something else, whereas Stua=
rt doesn&#39;t think this is a real use case.<div><br></div><div>I agree wi=
th you that it is a real use case we need to account for.</div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Jul 17, 2016 at=
 6:38 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.co=
m" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><div dir=3D"ltr">Violent agreement here. =C2=A0 Hence, &=
quot;.homenet&quot;. =C2=A0 :)</div><div class=3D"HOEnZb"><div class=3D"h5"=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Jul 17, =
2016 at 6:34 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:aj=
s@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Dear colleagues,<br>
<br>
On Fri, Jun 17, 2016 at 09:37:06AM +0100, Ray Bellis wrote:<br>
<br>
&gt; Whilst there may be &quot;undermined&quot; ways it&#39;s being used, i=
t&#39;s clear that<br>
&gt; most of the ways it&#39;s used are just because some vendors and sites=
<br>
&gt; decided to use that for their default *site local* domain which makes =
it<br>
&gt; completely consistent with what we need.<br>
&gt;<br>
&gt; I therefore completely disagree on point #1 - officially allocating<br=
>
&gt; .home for this purpose and having it &quot;sunk&quot; by default on in=
ternet<br>
&gt; facing recursive resolvers would IMHO actually *help* with the traffic=
<br>
&gt; hitting the root and reduce leakage of it.<br>
<br>
The argument above, which is rehearsed to some extent in<br>
draft-cheshire-homenet-dot-home-03 (although there IMO more subtly),<br>
is interesting to me, in that it appears to start with the exact same<br>
premises I do and reach the exact opposite conclusion.=C2=A0 I believe this=
<br>
is because of some unstated premises, and so I&#39;m going to attempt to<br=
>
lay out the premises as I understand them as completely as I can.<br>
<br>
To do this, I&#39;m going to draw some inferences about what Ray was<br>
arguing and about what is in draft-cheshire-homenet-dot-home-03.=C2=A0 I<br=
>
hope the authors indulge me, and I hope you, Gentle Reader, do not<br>
mistake my inferences as speaking correctly either for Ray or for<br>
Stuart.=C2=A0 Since they&#39;re both here, they can correct what I get wron=
g;<br>
but I think trying to lay out this different story might help us.<br>
<br>
I think we all agree that the label home, in the top-most position of<br>
a domain name (but maybe not a name in the DNS), is in use by some<br>
people.=C2=A0 I think we all agree that at least some uses of that name are=
<br>
somehow related to &quot;stuff in my house behind my home-router-like<br>
thing&quot;.=C2=A0 And I think we all agree that, whatever basis for that u=
se<br>
is, it either is not or ought not to be related to any actual<br>
delegation of the name in the DNS.<br>
<br>
With the above premises, I conclude that home is by definition not<br>
suitable for our purposes.=C2=A0 I conclude that from these additional<br>
premises:<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that, given the detectable pollution of the namespa=
ce at and<br>
=C2=A0 =C2=A0 =C2=A0 beneath home, there is a significant population alread=
y using<br>
=C2=A0 =C2=A0 =C2=A0 the name for some purposes, we know not what;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that if we want an identifier to be some sort of pr=
otocol switch<br>
=C2=A0 =C2=A0 =C2=A0 by which we tell software to do something novel, we ne=
ed an<br>
=C2=A0 =C2=A0 =C2=A0 identifier that has at least a modest chance of not ru=
nning into<br>
=C2=A0 =C2=A0 =C2=A0 widely-deployed use for some purpose not defined to be=
<br>
=C2=A0 =C2=A0 =C2=A0 consistent with the protocol switch;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that it is at least fantastically difficult to suss=
 out all the<br>
=C2=A0 =C2=A0 =C2=A0 strange things people are already doing with &quot;in =
the wild&quot;<br>
=C2=A0 =C2=A0 =C2=A0 undelegated names in the DNS, even if we make the dubi=
ous<br>
=C2=A0 =C2=A0 =C2=A0 assumption that there is something like a rigorous des=
ign behind<br>
=C2=A0 =C2=A0 =C2=A0 those doings;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that strings that could be used as protocol switche=
s are<br>
=C2=A0 =C2=A0 =C2=A0 fundamentally machine-directed rather than human-direc=
ted, and<br>
=C2=A0 =C2=A0 =C2=A0 therefore have a certain arbitrariness about them.<br>
<br>
With the same premises, I think the opposite argument is that home is<br>
entirely good for our purposes, because of the following additional<br>
premises:<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that we have (or we can get, which is what<br>
=C2=A0 =C2=A0 =C2=A0 draft-cheshire-homenet-dot-home-03 is asking for) a pr=
etty clear<br>
=C2=A0 =C2=A0 =C2=A0 idea that all the uses of home are already more or les=
s what<br>
=C2=A0 =C2=A0 =C2=A0 we&#39;re trying to do;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that picking the same string is very unlikely to br=
eak any of<br>
=C2=A0 =C2=A0 =C2=A0 the existing behaviour;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that a meaningful string to a human user is of high=
 importance<br>
=C2=A0 =C2=A0 =C2=A0 here;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that a primary (or even important secondary) motiva=
tion for the<br>
=C2=A0 =C2=A0 =C2=A0 allocation would be to capture traffic that should nev=
er have<br>
=C2=A0 =C2=A0 =C2=A0 been destined for the root in the first place;<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 that with adequate documentation, a possibly-confli=
cting use of<br>
=C2=A0 =C2=A0 =C2=A0 home would not have negative effects.<br>
<br>
<br>
<br>
<br>
I think the effort to document what people are actually doing with<br>
home is laudable, and I hope it succeeds in producing a more-or-less<br>
complete account of the use of that name.=C2=A0 But I do not see how we can=
<br>
get from &quot;documenting these uses is good&quot; to &quot;having documen=
ted it,<br>
you can then use the name that way.&quot;=C2=A0 The kind of exhaustive surv=
ey<br>
that would be needed to show the real uses of home would cost far more<br>
in time, effort, and money than the convenience of the string<br>
presents.=C2=A0 Moreover, it&#39;s not even clear that this would be the<br=
>
&quot;right&quot; string.=C2=A0 For lots of people on Earth don&#39;t use L=
atin writing,<br>
never mind English words.<br>
<br>
I hope this explains why I think proceeding with home is problematic.<br>
<br>
Andrew (speaking only for myself).<br>
<span><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrus=
den.com</a><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a114035e2f2bb360537dc8b83--


From nobody Mon Jul 18 00:12:05 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAA512D13E for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 00:12:03 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 ehpBchTINak1 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 00:12:01 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60DE512D0F9 for <homenet@ietf.org>; Mon, 18 Jul 2016 00:12:01 -0700 (PDT)
Received: from dhcp-b14e.meeting.ietf.org ([31.133.177.78]:62321) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bP2id-0007zx-JJ (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Mon, 18 Jul 2016 08:11:59 +0100
To: HOMENET <homenet@ietf.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <48bcea51-c4a4-b1ae-7a90-08bd71277687@bellis.me.uk>
Date: Mon, 18 Jul 2016 09:11:59 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/XSGQUr80093k3MmmhYRCewIciRE>
Subject: [homenet] Volunteers requested for Jabber scribe and note taker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 07:12:04 -0000

If we could please have advanced volunteers for jabber scribe(s) and
note taker for this afternoon's that would be much appreciated.

thanks,

Ray & Mark


From nobody Mon Jul 18 02:32:45 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8986B12D607 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 02:32:44 -0700 (PDT)
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 autolearn_force=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 HBfQnnALMux6 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 02:32:42 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 28EF012D66A for <homenet@ietf.org>; Mon, 18 Jul 2016 02:31:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 7E0BE10D28 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:31:16 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKpdMOwbXrkQ for <homenet@ietf.org>; Mon, 18 Jul 2016 09:31:15 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-b2a2.meeting.ietf.org [31.133.178.162]) by mx2.yitter.info (Postfix) with ESMTPSA id 8CA6D10BCD for <homenet@ietf.org>; Mon, 18 Jul 2016 09:31:15 +0000 (UTC)
Date: Mon, 18 Jul 2016 05:31:11 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160718093111.GF42471@mx2.yitter.info>
References: <CAPt1N1m+uS2dpQeD5minLo+U16z4FgxHnHt7_3O=z1YXrEFemw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPt1N1m+uS2dpQeD5minLo+U16z4FgxHnHt7_3O=z1YXrEFemw@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/6lnXcJW_Zp5k0t1Ot8Mjz6cRLP4>
Subject: Re: [homenet] New version of homenet naming architecture...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 09:32:44 -0000

Dear colleagues,

On Sun, Jul 10, 2016 at 11:57:28AM -0700, Ted Lemon wrote:
> I made the document quite a bit more definite, since I didn't hear any
> strenuous objections when I presented it last time.   I'd like to propose
> adopting the document as a working group work item.   Thoughts?   Do people
> think this is a good direction, or did the lack of objection last time
> indicate shocked horror rather than acquiescence?

I've read this draft.  I've got some various reservations and comments
that I'll want to make in more detail, but on the basic question of
whether this is a good foundation for the WG's efforts, I think it
obviously is.

One very large architectural issue in here is the flat&local namespace
and its correspondence to a hierarchical&global namespace.  This seems
to me to be a potentially very tricky mechanism with potential for
inconsistency, and it makes me deeply nervous, particularly since
we're talking about basically using the same names only sometimes in a
local and sometimes in a global context, with different authorities.
My inner database weenie is cringing.  So I want to be clear that
support for adopting the document does not mean that I think even very
fundamental notions in the document can't be thrown over later.  But I
think the WG ought to have change control over such decisions.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 18 03:32:45 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7C112D840 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 03:32:42 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 ULMJkmDQihMd for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 03:32:39 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3451712D82F for <homenet@ietf.org>; Mon, 18 Jul 2016 03:32:35 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id b199so128852608lfe.0 for <homenet@ietf.org>; Mon, 18 Jul 2016 03:32:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Lb+vqPu521IW4G7R9OUTTjp22h448wADexo59HEyk1c=; b=Dgjma5omA9Urv+J+0AWBI6V/nVNJ/gyMFHd5likMsnkVEiYzUCRRTKp6QOHYYF4enM jOVqdPVzIFy+0XVd+c3oRXf02RQDNBeLMDH19HVYDBbKmVW8XIbNZZfH4G72wD2ckX+W 6W31NRxX9Wb/crHEXUaqdKKxfj3m1wr0VegSjbhF85wpY8yrT39AK3PiSzy+ntrRjyr2 3It3Egqnjw5CewnXHWYvNxE/S+PlbmtW+Djov+lgHvItrhZsovZvrzFdIfRNBx5gC6ZZ Wtu/oTSlUlx2sIlvR1JMeysqiMHv32jA4BJt4h5zKlMfENKmtYP/akHJ4uBIt7qofc7l vBpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Lb+vqPu521IW4G7R9OUTTjp22h448wADexo59HEyk1c=; b=VVLmNjtqK9+zGupinnhELLwCQx3tbdLAXbauVIjF4h2opWPMoPeiJZ7GIUQSpclqW6 fUoD2k29szSOQylHX/SlGf4w+qoZrY+dJonBSPkQMdbHmmS65DfPsNw1X2znoETLcgqQ nhRtdHJU482D2UwCf7N3/15srUIrKgM+M43dIdK+gR7tDSKhmik/jATBHq0unLti0lDj ptX5FUuk0QWCPuBaPxnZX6gcDp+oWJT9E69suZRsDPOFQ0lRcasJqA9RIiECLtf5W4Be 8udNIQRPpDZXxddvLqqgiFCZWnEPKPl7KyELOBcPsMgij7hM/BP0KBXOzbIxRriwVPR+ gwwg==
X-Gm-Message-State: ALyK8tKdsaxzHwcqoi+F25n/cV1/mX2NTOOfpEa0pMsthiFEpmODV7T+5/LBJ/EjS7j/vqYMzg9kGbub8Fy7nQ==
X-Received: by 10.25.152.135 with SMTP id a129mr13317355lfe.226.1468837953419;  Mon, 18 Jul 2016 03:32:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 03:31:53 -0700 (PDT)
In-Reply-To: <20160718093111.GF42471@mx2.yitter.info>
References: <CAPt1N1m+uS2dpQeD5minLo+U16z4FgxHnHt7_3O=z1YXrEFemw@mail.gmail.com> <20160718093111.GF42471@mx2.yitter.info>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 12:31:53 +0200
Message-ID: <CAPt1N1kJMB=YHp_02Bq197BN1V+g9FT4J8Fyayv=Sh6hwKquhg@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a114035e272502d0537e67c75
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/dViBcaomK83Ky7neKr5MH-9hKQ0>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] New version of homenet naming architecture...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 10:32:43 -0000

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

Thanks for the review!

I agree that we need to make sure we get the global/local bit right.   Bear
in mind that the "flatness" is intended to be the only thing that is ever
seen by a resolver.   The per-link hierarchy is simply a hack to make
hybrid mDNS work without requiring the user to see multiple link names.
>From a database perspective, think of the presented host namespace as being
a view that represents the join of the link-specific mDNS tables and the
internal host namespace.   Of course it's not quite that simple, but that's
the basic idea.

There are definitely some tricks to that that aren't documented in the
architecture document, and indeed I didn't even make clear the idea that
the presented namespace is a view; unfortunately I didn't fully realize
that I'd failed to do that until just now.   :)


On Mon, Jul 18, 2016 at 11:31 AM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Dear colleagues,
>
> On Sun, Jul 10, 2016 at 11:57:28AM -0700, Ted Lemon wrote:
> > I made the document quite a bit more definite, since I didn't hear any
> > strenuous objections when I presented it last time.   I'd like to propose
> > adopting the document as a working group work item.   Thoughts?   Do
> people
> > think this is a good direction, or did the lack of objection last time
> > indicate shocked horror rather than acquiescence?
>
> I've read this draft.  I've got some various reservations and comments
> that I'll want to make in more detail, but on the basic question of
> whether this is a good foundation for the WG's efforts, I think it
> obviously is.
>
> One very large architectural issue in here is the flat&local namespace
> and its correspondence to a hierarchical&global namespace.  This seems
> to me to be a potentially very tricky mechanism with potential for
> inconsistency, and it makes me deeply nervous, particularly since
> we're talking about basically using the same names only sometimes in a
> local and sometimes in a global context, with different authorities.
> My inner database weenie is cringing.  So I want to be clear that
> support for adopting the document does not mean that I think even very
> fundamental notions in the document can't be thrown over later.  But I
> think the WG ought to have change control over such decisions.
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">Thanks for the review!<div><br></div><div>I agree that we =
need to make sure we get the global/local bit right. =C2=A0 Bear in mind th=
at the &quot;flatness&quot; is intended to be the only thing that is ever s=
een by a resolver. =C2=A0 The per-link hierarchy is simply a hack to make h=
ybrid mDNS work without requiring the user to see multiple link names. =C2=
=A0 From a database perspective, think of the presented host namespace as b=
eing a view that represents the join of the link-specific mDNS tables and t=
he internal host namespace. =C2=A0 Of course it&#39;s not quite that simple=
, but that&#39;s the basic idea.<div><br></div><div>There are definitely so=
me tricks to that that aren&#39;t documented in the architecture document, =
and indeed I didn&#39;t even make clear the idea that the presented namespa=
ce is a view; unfortunately I didn&#39;t fully realize that I&#39;d failed =
to do that until just now. =C2=A0 :)</div><div><br></div></div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 18, 2016 at=
 11:31 AM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvi=
lwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">Dear colleagues,<br>
<span class=3D""><br>
On Sun, Jul 10, 2016 at 11:57:28AM -0700, Ted Lemon wrote:<br>
&gt; I made the document quite a bit more definite, since I didn&#39;t hear=
 any<br>
&gt; strenuous objections when I presented it last time.=C2=A0 =C2=A0I&#39;=
d like to propose<br>
&gt; adopting the document as a working group work item.=C2=A0 =C2=A0Though=
ts?=C2=A0 =C2=A0Do people<br>
&gt; think this is a good direction, or did the lack of objection last time=
<br>
&gt; indicate shocked horror rather than acquiescence?<br>
<br>
</span>I&#39;ve read this draft.=C2=A0 I&#39;ve got some various reservatio=
ns and comments<br>
that I&#39;ll want to make in more detail, but on the basic question of<br>
whether this is a good foundation for the WG&#39;s efforts, I think it<br>
obviously is.<br>
<br>
One very large architectural issue in here is the flat&amp;local namespace<=
br>
and its correspondence to a hierarchical&amp;global namespace.=C2=A0 This s=
eems<br>
to me to be a potentially very tricky mechanism with potential for<br>
inconsistency, and it makes me deeply nervous, particularly since<br>
we&#39;re talking about basically using the same names only sometimes in a<=
br>
local and sometimes in a global context, with different authorities.<br>
My inner database weenie is cringing.=C2=A0 So I want to be clear that<br>
support for adopting the document does not mean that I think even very<br>
fundamental notions in the document can&#39;t be thrown over later.=C2=A0 B=
ut I<br>
think the WG ought to have change control over such decisions.<br>
<br>
Best regards,<br>
<br>
A<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</font></span></blockquote></div><br></div>

--001a114035e272502d0537e67c75--


From nobody Mon Jul 18 06:59:34 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AF112DBC3 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 06:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 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, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 7BM67EKHK1r9 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 06:59:28 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F1812DAFE for <homenet@ietf.org>; Mon, 18 Jul 2016 06:33:31 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0ADBEA3; Mon, 18 Jul 2016 15:33:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1468848809; bh=PnRyihzCBYVY2fImYDhlUUGKnvgEOChEe17X+nYfP/I=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=BAy923Bbz97jm0g58RgiJ0E/F0bv8qWqsVA2Orsp8+REBpcyojV8UnXQpUfCEieX2 1GrTjRnaE9vvqmTZb2Du7ufMkeg9FI+aqFKc93+F6r9saTQU48grq29B3LL8IOU3+o K/XKkgPzpLon7uafn9KzohWz67Es5qLH4HR+/+uE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 06AC5A2; Mon, 18 Jul 2016 15:33:29 +0200 (CEST)
Date: Mon, 18 Jul 2016 15:33:28 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Terry Manderson <terry.manderson@icann.org>
In-Reply-To: <D3B0315C.95E19%terry.manderson@icann.org>
Message-ID: <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org>
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: <https://mailarchive.ietf.org/arch/msg/homenet/ftPYwwYUgbAC3QoBVHDgNUy1Q4Y>
Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 13:59:33 -0000

The option 4 mentioned updating RFC7788. It's not clear to me what this 
update would be.

.HOME has not been handed out by ICANN yet, what's the odds that RFC6761 
process reserving .HOME for special use would succeed?

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


From nobody Mon Jul 18 07:16:42 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7973B12E142 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:16:40 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 piQRsZCnMtMk for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:16:27 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3476012DCBF for <homenet@ietf.org>; Mon, 18 Jul 2016 06:45:33 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id l69so75359445lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 06:45:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=k6oMLazo26LTuea1UL1Ax6hKzrbss1vfaGpmU63Xooo=; b=ger24xF9H6q7vPiyM4YRsFq19DBhXdw4nsc+gIZZqqbc0hzBrgUrG4+gr1vLgk/BOu +jXxEsdm+7bx5LBnPxdazRy0rCk496XhzB/YpgyMQXG8a8MuRr8lSy5yPrWAxTZGXHik KEhjzJSMawt11/HTGWBw0UtJ9lT25IE2neYI+726VefwDGzotHxrElufptXfRn4ZyGsw D9M3c+/3THM77GbQqqwZBYkGdYO2G6LQe8lsM9nJfNndqsSpfEEnkuGEjlaRv8TkzBrU oYCSKbB1WTuUbj2fb3eMTT6MqkLpUVL/CwjqthNR2OhjVmVuVYooZ0NFNlDB+AGi3Rk3 3Bjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=k6oMLazo26LTuea1UL1Ax6hKzrbss1vfaGpmU63Xooo=; b=ZXm4CVc4kZSKCfW1Hr53DQ4e4TlYXeKcGbBp3XZHL+RJ14t/zVXqXc+Yj6rmJTJXaQ f6NPMJOznA1Qtfrn6ZpBA1UFwJ0GSjsLhvKj2KMteMBAXDBRNyY0EmT1nbcGPAQMTNfc oNYIN0bnsdCqgxwGzSGC1q/EY9ZARCD2fz1GvT064qEr95ivJixdOGGaHt+qBUrR2Ih4 2tenu7fhXPMxiuPh1WJR5SRRDTXIaqAwM49jCvSl5H850IINKWJDFTj7QwTEAwF2bY+K I8VMuleIGCvoPpU60ZN+DQOvH5uuyaMY1S3dmglm8VpcH5y7cT12Y1SGB7eSACErcvf5 BSig==
X-Gm-Message-State: ALyK8tIPqj57TtFL2air+tbjCowidlkvsVWz/MITIEvXJEJuVZNjgjprXeOTKwmNPrr8Ki9lHPTp4AMVvGbuXA==
X-Received: by 10.25.42.207 with SMTP id q198mr13700150lfq.181.1468849531011;  Mon, 18 Jul 2016 06:45:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 06:44:51 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 15:44:51 +0200
Message-ID: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
To: HOMENET <homenet@ietf.org>, Terry Manderson <terry.manderson@icann.org>
Content-Type: multipart/alternative; boundary=001a11411dba8656570537e92e5f
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/_AOw5X67N-YZmG12XrqbJ3wyOvE>
Subject: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:16:41 -0000

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

The document as written causes some harm, but less harm than updating it.
The text in the document as written as to how domain names are resolved is
not very good, and really really needs to be clarified with a detailed
document that explains how name resolution works on the homenet.

But I think we all accept that there's going to have to be a special-use
top-level name allocated.   That name is either going to be '.home' or
'.homenet' as far as I can tell.

Andrew made a very good case for why it shouldn't be .home.   I agree with
him, but not strongly enough that I would kick up a fuss of the consensus
was to allocate .home anyway.    I also don't mind the two-stage process if
IETF leadership is willing to do what I asked at the mic and actively keep
the debate on track.

But it's really a three-stage process: do the erratum as an update, then do
the 6761 allocation of either .home or .homenet, then do the document that
explains how it all works.   We need step two to happen _soon_ or we are in
trouble.   Step 1 may be necessary and highly motivating because of the
layer 9 problems that this mistake caused, but if we only do step 1 and
then trail off on step 2, the effect in the market is either going to be
that everybody uses .home anyway, or else that everybody uses something
different.   Neither of these outcomes are good outcomes.

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

<div dir=3D"ltr">The document as written causes some harm, but less harm th=
an updating it. =C2=A0 The text in the document as written as to how domain=
 names are resolved is not very good, and really really needs to be clarifi=
ed with a detailed document that explains how name resolution works on the =
homenet.<div><br></div><div>But I think we all accept that there&#39;s goin=
g to have to be a special-use top-level name allocated. =C2=A0 That name is=
 either going to be &#39;.home&#39; or &#39;.homenet&#39; as far as I can t=
ell.</div><div><br></div><div>Andrew made a very good case for why it shoul=
dn&#39;t be .home. =C2=A0 I agree with him, but not strongly enough that I =
would kick up a fuss of the consensus was to allocate .home anyway. =C2=A0 =
=C2=A0I also don&#39;t mind the two-stage process if IETF leadership is wil=
ling to do what I asked at the mic and actively keep the debate on track.</=
div><div><br></div><div>But it&#39;s really a three-stage process: do the e=
rratum as an update, then do the 6761 allocation of either .home or .homene=
t, then do the document that explains how it all works. =C2=A0 We need step=
 two to happen _soon_ or we are in trouble. =C2=A0 Step 1 may be necessary =
and highly motivating because of the layer 9 problems that this mistake cau=
sed, but if we only do step 1 and then trail off on step 2, the effect in t=
he market is either going to be that everybody uses .home anyway, or else t=
hat everybody uses something different. =C2=A0 Neither of these outcomes ar=
e good outcomes.</div></div>

--001a11411dba8656570537e92e5f--


From nobody Mon Jul 18 07:17:02 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49BBB12E14D for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 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, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 f3FcSQYEgLuC for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:16:53 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66F6512DE7A for <homenet@ietf.org>; Mon, 18 Jul 2016 06:45:47 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BEE15A3; Mon, 18 Jul 2016 15:45:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1468849545; bh=QM5p4fgstQLBWLK1+ci/1RubZhOnqEajiys6YKu3qcA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=oOwShreSI7/q4kbRiJlfGNHDXF1zFqk0cikv+ylqoP/20SCraGt/PGc2H3z5l5jFv V/Zpp+cMzWejasV24SGT6e5Z3k101DJkWXSV4HkPyGng8Mvxm0ogoxxEMSiZWiKth4 BAZbomw4jOP/NrEzZf0GJ//pLntk4Hns0JtbIRrQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 762CBA2; Mon, 18 Jul 2016 15:45:45 +0200 (CEST)
Date: Mon, 18 Jul 2016 15:45:45 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Terry Manderson <terry.manderson@icann.org>
In-Reply-To: <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1607181543540.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@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: <https://mailarchive.ietf.org/arch/msg/homenet/uOSEnSGanLbgLUdG3T_6wAj4ax0>
Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:16:59 -0000

On Mon, 18 Jul 2016, Mikael Abrahamsson wrote:

>
> The option 4 mentioned updating RFC7788. It's not clear to me what this 
> update would be.
>
> .HOME has not been handed out by ICANN yet, what's the odds that RFC6761 
> process reserving .HOME for special use would succeed?

Let me just clarify. Updating RFC7788 to remove ".home", then do RFC6761 
process to reserve .home for special use, succeeding in that, then 
updating RFC7788 again. This seems silly.

I propose fast-tracking RFC6761 process for ".home" reservation for 
special-use, and not touch RFC7788 unless this process fails.

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


From nobody Mon Jul 18 07:25:00 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B597126579 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 L4nALgoNrTTm for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:24:56 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27DD412DF3F for <homenet@ietf.org>; Mon, 18 Jul 2016 06:50:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=uMMw3MnjQ0/FQwX4/XLD+2jO1dcjQNj2jd7MvmHGPg8=; b=GoJW4EpUi+1yZb5Q6/n6cZD+EJXGyEz7Fv0gj9MJIIyno8Z9AuDpFqyZb2D2o4h2+z8IEGA3yd7kXxxGDZzoz9CndNCAjpHXHzYqV1wfiCipCY1gCmol28MWQNDNBsC6N35qLvEd7Gd9fzbXNzHr4KPpU5RaScJsAEurnAI01u0=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0245.outbound.protection.outlook.com [213.199.154.245]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-64-s4YRZ5boMHeDdMPFolE08Q-1; Mon, 18 Jul 2016 14:50:27 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) with Microsoft SMTP Server (TLS) id 15.1.539.14; Mon, 18 Jul 2016 13:50:25 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.019; Mon, 18 Jul 2016 13:50:25 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: HOMENET <homenet@ietf.org>
Thread-Topic: use of .home
Thread-Index: AQHR4PtVI3pD+SP5BESMWDiJBkTBRA==
Date: Mon, 18 Jul 2016 13:50:25 +0000
Message-ID: <3A7CABDD-4D6D-4DF6-8EF5-4B7BF89EFAAD@jisc.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:152:f139:b19d:466a:5b18]
x-ms-office365-filtering-correlation-id: 14c3502f-e6e4-4f22-644f-08d3af127880
x-microsoft-exchange-diagnostics: 1; AMSPR07MB455; 20:p8ZrzdEq2jfy1XCHoH2+ehuL891PF6+VP4q/7Z+KK0uxX3Oho7sfJv8ERL31Pi2R4YetKGK/S+NWOQBtmgnHHlOYkKCiORCtIv/t0HQjp2RYEgNXIN9rERfZlMNnABRmXyREZ3b48KAZMQ0ofSHcN3Y24JQVXStNOCKP9PomsV0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB455;
x-microsoft-antispam-prvs: <AMSPR07MB455D0CECB69630871482802D6360@AMSPR07MB455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(209352067349851);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB455; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB455; 
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(189002)(199003)(50986999)(15395725005)(16236675004)(101416001)(50226002)(8936002)(7906003)(10400500002)(74482002)(33656002)(2906002)(19617315012)(3280700002)(11100500001)(106116001)(5002640100001)(19580395003)(105586002)(68736007)(81166006)(81156014)(7736002)(7846002)(92566002)(229853001)(106356001)(8676002)(83716003)(2900100001)(77096005)(97736004)(450100001)(87936001)(57306001)(82746002)(36756003)(122556002)(15975445007)(6116002)(102836003)(586003)(86362001)(107886002)(110136002)(3660700001)(189998001)(142923001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB455; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2016 13:50:25.2772 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB455
X-MC-Unique: s4YRZ5boMHeDdMPFolE08Q-1
Content-Type: multipart/alternative; boundary="_000_3A7CABDD4D6D4DF68EF54B7BF89EFAADjiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/b_eRNWCD5Qc_ro667CsprBaslE8>
Subject: [homenet] use of .home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:24:59 -0000

--_000_3A7CABDD4D6D4DF68EF54B7BF89EFAADjiscacuk_
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

SGksDQoNCkkgd2FzIGdvaW5nIHRvIHNheSB0d28gdGhpbmdzIGF0IHRoZSBtaWMgYmVmb3JlIHdl
IHJhbiBvdXQgb2YgdGltZS4NCg0KRmlyc3QsIHRoYXQgSSBhZ3JlZSB3aXRoIFJhbHBoIG9uIGhp
cyBjb21tZW50cyBhYm91dCByZXF1aXJlbWVudHMuDQoNClNlY29uZCwgYXMgU3R1YXJ0IHBvaW50
ZWQgb3V0LCB1c2UgaXMgYWxyZWFkeSBiZWluZyBtYWRlIG9mIC5ob21lLCBlLmcuIGl04oCZcyB1
c2VkIGJ5IEJUIGluIHRoZSBVSy4gVGhlcmUgYXJlIGFydGljbGVzIG9ubGluZSB0aGF0IHN1Z2dl
c3QgNTAwTSBoaXRzL2RheSB0byB0aGUgcm9vdHMgZm9yIC5ob21lLCBhbmQgdGhhdCAuaG9tZSBp
cyB0aGUgaGVhdmllc3QgdXNlZCB1bmFsbG9jYXRlZCBUTEQuIFdoaWNoIEkgYXNzdW1lIGlzIGlu
IG5vIHNtYWxsIHBhcnQgd2h5IElDQU5OIGNob3NlIHRvIG5vdCBhbGxvY2F0ZSB0aGUgVExELCBp
bnN0ZWFkIG1hcmtpbmcgaXQgKGFuZCAuY29ycCkgYXMgYSDigJxoaWdoIHJpc2vigJ0gVExELCBk
dWUgdG8gZXhpc3RpbmcgdXNlLiBGb3IgYW4gZXhhbXBsZSwgc2VlIGh0dHA6Ly9kb21haW5pbmNp
dGUuY29tLzEzNzczLWhvbWUtZ2V0cy1oYWxmLWEtYmlsbGlvbi1oaXRzLWEtZGF5LWNvdWxkLXRo
aXMtcHV0LW5ldy1ndGxkcy1hdC1yaXNrLiAgT2YgY291cnNlICpob3cqIC5ob21lIGlzIGJlaW5n
IHVzZWQgaXMgYW5vdGhlciBxdWVzdGlvbiwgYnV0IGl04oCZcyBlZmZlY3RpdmVseSBub3QgYWxs
b2NhdGFibGUgZWxzZXdoZXJlLg0KDQpUaW0NCg0KDQoNCg==
--_000_3A7CABDD4D6D4DF68EF54B7BF89EFAADjiscacuk_
Content-Type: text/html; charset=UTF-8
Content-ID: <D8EA8501F577604B86C8863130F341C5@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGksDQo8ZGl2IGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5JIHdhcyBnb2luZyB0byBzYXkgdHdv
IHRoaW5ncyBhdCB0aGUgbWljIGJlZm9yZSB3ZSByYW4gb3V0IG9mIHRpbWUuPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5GaXJzdCwgdGhh
dCBJIGFncmVlIHdpdGggUmFscGggb24gaGlzIGNvbW1lbnRzIGFib3V0IHJlcXVpcmVtZW50cy48
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PlNlY29uZCwgYXMgU3R1YXJ0IHBvaW50ZWQgb3V0LCB1c2UgaXMgYWxyZWFkeSBiZWluZyBtYWRl
IG9mIC5ob21lLCBlLmcuIGl04oCZcyB1c2VkIGJ5IEJUIGluIHRoZSBVSy4gVGhlcmUgYXJlIGFy
dGljbGVzIG9ubGluZSB0aGF0IHN1Z2dlc3QgNTAwTSBoaXRzL2RheSB0byB0aGUgcm9vdHMgZm9y
IC5ob21lLCBhbmQgdGhhdCAuaG9tZSBpcyB0aGUgaGVhdmllc3QgdXNlZCB1bmFsbG9jYXRlZCBU
TEQuIFdoaWNoIEkgYXNzdW1lDQogaXMgaW4gbm8gc21hbGwgcGFydCB3aHkgSUNBTk4gY2hvc2Ug
dG8gbm90IGFsbG9jYXRlIHRoZSBUTEQsIGluc3RlYWQgbWFya2luZyBpdCAoYW5kIC5jb3JwKSBh
cyBhIOKAnGhpZ2ggcmlza+KAnSBUTEQsIGR1ZSB0byBleGlzdGluZyB1c2UuIEZvciBhbiBleGFt
cGxlLCBzZWUmbmJzcDs8YSBocmVmPSJodHRwOi8vZG9tYWluaW5jaXRlLmNvbS8xMzc3My1ob21l
LWdldHMtaGFsZi1hLWJpbGxpb24taGl0cy1hLWRheS1jb3VsZC10aGlzLXB1dC1uZXctZ3RsZHMt
YXQtcmlzayIgY2xhc3M9IiI+aHR0cDovL2RvbWFpbmluY2l0ZS5jb20vMTM3NzMtaG9tZS1nZXRz
LWhhbGYtYS1iaWxsaW9uLWhpdHMtYS1kYXktY291bGQtdGhpcy1wdXQtbmV3LWd0bGRzLWF0LXJp
c2s8L2E+Lg0KICZuYnNwO09mIGNvdXJzZSAqaG93KiAuaG9tZSBpcyBiZWluZyB1c2VkIGlzIGFu
b3RoZXIgcXVlc3Rpb24sIGJ1dCBpdOKAmXMgZWZmZWN0aXZlbHkgbm90IGFsbG9jYXRhYmxlIGVs
c2V3aGVyZS48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0i
Ij4NCjxkaXYgY2xhc3M9IiI+VGltJm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1pbnRlcmNoYW5nZS1uZXdsaW5lIj4NCjwv
ZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=
--_000_3A7CABDD4D6D4DF68EF54B7BF89EFAADjiscacuk_--


From nobody Mon Jul 18 07:36:11 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC55112DC02 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:36:09 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 0qgmO6N2pJZi for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:36:08 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E6C312E0A4 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:04:05 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id l69so75767991lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:04:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4u+JsSZVlv/5gH8LWU2CrEYFQscfw02hrsy6D1OqbBQ=; b=sS3x306+6eeMy4aSek5p7QQ9z++572OT/7o+BJVRQLATtTXzQPz4lrJNhCkcrq5NcI 0YoqkXG5cC8mujZy5uALHqBNfsI+OReRawGTKLM2jsQXtAJIrEHn+BhPPicYd4CL2ltF AxrebQSmX9nGzjVA3+75Xl8Cv5jncZ/3/QEDwIJS6tlsHU5vG+yKOaj8M49BFHlS81a1 3F04Yvz6DKgx3QDZ9JeHfZxM7o/uObIhq2UEKNC+nxXwLZqZfKQFrccjEbzM5xU1f5RW 1sWzKQflYq+LqPdPGeaC2L524+jjkCtW3ZYHH6RbUoSHJDBuxlCYOJbb6o8T8NgOWymv EdQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4u+JsSZVlv/5gH8LWU2CrEYFQscfw02hrsy6D1OqbBQ=; b=QRu+uQIrexp9tbr0483ExleOgvN9RjL8pHNes6W7TjhtxmIOy5yGgslUu/nPJZMwqm 7uoHR87EcSMlPRDF0ulwjI31JGSoA9VRXXhTW1e/nIy+CQgjDnRG6ceGyhb/OW61gGHS DckBOR4o6WoLx62/7QjCV0UTLwRCA53S64QGy1GfMJZdRB+mp38FnvNl9OIUrEDpjAX2 13oWZQyoikqKS2ntGNj+GqS3E+toaZYcoYAMQVUOpYYvsfMUO7fE9ElXuOiYejriefhM ndgu2EOctThRWG/tNFSuq1em5LhbYmrvPad2NAu2GWt9LPZ7aO4CbOBBZ+efKFcCr/iQ vtVQ==
X-Gm-Message-State: ALyK8tJ/G32QbxKKREGeDFZfquk3Hr3mL2P5t11W2M/oEgDgqJpwhHVxXL9KXxeyxFImOs7mCUBDqlMmJld4QA==
X-Received: by 10.25.131.150 with SMTP id f144mr12695339lfd.53.1468850643712;  Mon, 18 Jul 2016 07:04:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 07:03:24 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 16:03:24 +0200
Message-ID: <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=001a113f20b8d8d28b0537e9708a
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nlSzBBGVXM0GposUcO8VDf5bbgE>
Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:36:10 -0000

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

Zero.   See the discussion in draft-tldr-sutld-02 on this topic (search for
.home).

On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:

>
> The option 4 mentioned updating RFC7788. It's not clear to me what this
> update would be.
>
> .HOME has not been handed out by ICANN yet, what's the odds that RFC6761
> process reserving .HOME for special use would succeed?
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">Zero. =C2=A0 See the discussion in draft-tldr-sutld-02 on =
this topic (search for .home).</div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahamsson <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swm=
ike@swm.pp.se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
The option 4 mentioned updating RFC7788. It&#39;s not clear to me what this=
 update would be.<br>
<br>
.HOME has not been handed out by ICANN yet, what&#39;s the odds that RFC676=
1 process reserving .HOME for special use would succeed?<span class=3D"HOEn=
Zb"><font color=3D"#888888"><br>
<br>
-- <br>
Mikael Abrahamsson=C2=A0 =C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank">swmike@swm.pp.se</a></font></span><div class=3D"HOEnZb"><=
div class=3D"h5"><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div></div></blockquote></div><br></div>

--001a113f20b8d8d28b0537e9708a--


From nobody Mon Jul 18 07:43:02 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 936B312DE5C for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:42:59 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 gI9_P3ANjVH1 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:42:57 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01AB912DE5B for <homenet@ietf.org>; Mon, 18 Jul 2016 07:14:27 -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/56228) with ESMTP id u6IEEQLD012659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <homenet@ietf.org>; Mon, 18 Jul 2016 16:14:26 +0200
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/56228) with ESMTP id u6IEEQ1w007277 for <homenet@ietf.org>; Mon, 18 Jul 2016 16:14:26 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1105361FA3 for <homenet@ietf.org>; Mon, 18 Jul 2016 16:14:26 +0200 (CEST)
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 LCcZBeI_kH2F for <homenet@ietf.org>; Mon, 18 Jul 2016 16:14:24 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 9F99761FA1 for <homenet@ietf.org>; Mon, 18 Jul 2016 16:14:24 +0200 (CEST)
Date: Mon, 18 Jul 2016 16:14:26 +0200
Message-ID: <87d1mb11a5.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]); Mon, 18 Jul 2016 16:14:26 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 18 Jul 2016 16:14:26 +0200 (CEST)
X-Miltered: at korolev with ID 578CE442.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578CE442.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578CE442.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: 578CE442.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 : 578CE442.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578CE442.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: <https://mailarchive.ietf.org/arch/msg/homenet/FN8MQyyY8EDUEqfMLkxC3Znh_K8>
Subject: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:42:59 -0000

This is to repeat the comment that I made at the mike about
draft-lemon-homenet-naming-architecture-01.

Among other things, this draft suggests:

   1. having a new ND option (Section 3.5);
   2. defining a RESTful management API (Section 3.6);
   3. the use of a local resolver (Section 4.5);
   4. the use of a ULA (Section 5.5).

These are some fairly ambitious requirements, and I believe that they
deserve discussion separately from the naming issue.  More precisely:

(1) Are wo to go to the effort of specifying and deploying a new ND option?

(2) Defining a management API goes against the Homenet tradition, which
    is to negotiate things over HNCP rather than defining new APIs.

(3) HNCP does not currently mandate using a local resolver, and neither
    does it define a means to advertise the address of a local resolver to
    HNCP routers.  Are we requiring a full DNS server with DNSsec support
    on each HNCP node, including an HNCP speaker that is not a router?
    (Note that I'd be strongly opposed to requiring that every HNCP
    speaker must be a router, and I think my opinion on putting a DNS
    forwarder on every HNCP node is similar.)

(4) Is there WG consensus on requiring a ULA?

I don't have a definite opinion yet, but these requirements certainly make
me nervous.

-- Juliusz


From nobody Mon Jul 18 07:44:49 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 691D712DBF4 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:44:48 -0700 (PDT)
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 autolearn_force=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 gYoP9ciO3rQk for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:44:46 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 68BE912D955 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:16:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id DBB5510D27 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:16:44 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jd-tceZG-ed for <homenet@ietf.org>; Mon, 18 Jul 2016 14:16:44 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2001:67c:370:176:ec3c:e7e8:d91a:f625]) by mx2.yitter.info (Postfix) with ESMTPSA id E8C731067D for <homenet@ietf.org>; Mon, 18 Jul 2016 14:16:43 +0000 (UTC)
Date: Mon, 18 Jul 2016 10:16:41 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160718141641.GI43287@mx2.yitter.info>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/FaztdyAPNbH33V0ghdciToWkMiA>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:44:48 -0000

On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
> 
> .HOME has not been handed out by ICANN yet

There are several applications for home in the root zone.  To my mind,
that means that home has been claimed as being inside the global DNS
context, and therefore is not available under RFC 6761.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 18 07:45:15 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8FE12DC3C for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 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, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 VJiB-Qaw9nVi for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:45:11 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888CF12DE95 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:17:15 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 1FEFAA3; Mon, 18 Jul 2016 16:17:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1468851433; bh=hFFf5alBE232d3H55QOekoUqdt4/WsNy3YeHtxq5K1o=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=RXd0gAmSz+Aw+RHcHvrsRlWlJvk7bdu49ukhoojzDxfIuc1DPNxKVZQnE1QyfvrYM +ivFrtc6CZ0b1y7Mg8sXbipDLhSTAw/zeTTNn7th1r2gICmtst1zas9O8AIzNoEbGW DlzY7Mxy9QlBahEJkRc4FuEFaKcunKxKpif5vwag=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 19609A2; Mon, 18 Jul 2016 16:17:13 +0200 (CEST)
Date: Mon, 18 Jul 2016 16:17:13 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1607181616440.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@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: <https://mailarchive.ietf.org/arch/msg/homenet/JphAx4nhuV4LcdwZSjs9bhdzahE>
Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:45:13 -0000

On Mon, 18 Jul 2016, Ted Lemon wrote:

> Zero.  See the discussion in draft-tldr-sutld-02 on this topic (search 
> for .home).

I guess you mean https://tools.ietf.org/html/draft-tldr-sutld-ps-02 ?

I can't find any mention of .home in it.

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


From nobody Mon Jul 18 07:52:47 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A02812DA89 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:52:45 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 maEt34RpnOIj for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:52:43 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A261C12DD0A for <homenet@ietf.org>; Mon, 18 Jul 2016 07:24:45 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id l69so76225689lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:24:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pDNRfzDSrirSRWcgb4t79euOrl6KRNSYzOsLbyTFmEU=; b=GBVvF8pbgUX7l82SoK9s5o3uQQKRiJASVbDCe5mUVgHBhZ+ufdUl7PJkLZaxVC8LJ4 2nYO1KiowbqE0WvmPq/044zriVFUBPfPMSzDD3Pe/lApjZp0qbi2e1v1DyARuxx5zHWV v0T7MCuDLKyZ99dMUQFph19e73jyjx0Pm7cztKcWTy1kzcW7jWry6sdycte5os18E980 xxXvArhmaX8tkiqyUP2iIxP1//AtFj6x/Ael2Mbl2W3yFHbuBukqzZS4PfcWQArgsBMw tsuzh2xlvPKs1XLjMVmbt9Zjr+kC/fvUAsRwvJBglmJZYGezIOX3c/GT+cyJCJsY11z6 pLaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pDNRfzDSrirSRWcgb4t79euOrl6KRNSYzOsLbyTFmEU=; b=em9tVRS3bUXUCFtHc9h45IuvWFzSZ0u4f+LrK9lZPPALO/DPA1ME7fG7zyvaEW3RHY 3TpjRZgcvleq6FbxgjIGIZC/h7AiHb7mxJsIjyxrNXUGbI0+/vFaBY0qWQG7tmLVhGpf DudBotIn4viOQ1u48GMWr0kxjWRwlZOHGwLe5cHzZDyUCeQMyrfI81jcoZVQQffdxtvA iuQTseAABuRnrTP5q8w7E/B75MNDOXpC8XR5uSCqtXEzrw/B2zSx6Ved0Etah78Gj1Sx grlJ6GIH4q40EINNUFeWlHvlLtkNyjHigC8cCZ02lKcRjZhDj6Z2FiQ8EokokmOnqRKK NzLQ==
X-Gm-Message-State: ALyK8tKYRpVdpB2dXA52k2O3BOsokWTpYG4lWnMgIRIy8X/OcPmUezRntyULrY+PL3oV0D5qkVdp1u1HmUfSBQ==
X-Received: by 10.25.42.207 with SMTP id q198mr13770653lfq.181.1468851883832;  Mon, 18 Jul 2016 07:24:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 07:24:04 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1607181616440.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com> <alpine.DEB.2.02.1607181616440.2309@uplift.swm.pp.se>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 16:24:04 +0200
Message-ID: <CAPt1N1=Lh3Scqc1gbFSiFoEPmZgaTvqsgq8i=cxfMccSAACqRw@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=001a11411dbac388b40537e9ba37
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/dWGNS7QuQqmJGZh3sm9RCS0mF2o>
Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 14:52:45 -0000

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

Wow.   Apparently my freudian slip at the microphone today is a trend: the
place where I should have said ".home" in sutldr-ps, I said ".local"
instead.   Thanks for indirectly pointing this out to me!   :}

On Mon, Jul 18, 2016 at 4:17 PM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:

> On Mon, 18 Jul 2016, Ted Lemon wrote:
>
> Zero.  See the discussion in draft-tldr-sutld-02 on this topic (search for
>> .home).
>>
>
> I guess you mean https://tools.ietf.org/html/draft-tldr-sutld-ps-02 ?
>
> I can't find any mention of .home in it.
>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>

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

<div dir=3D"ltr">Wow. =C2=A0 Apparently my freudian slip at the microphone =
today is a trend: the place where I should have said &quot;.home&quot; in s=
utldr-ps, I said &quot;.local&quot; instead. =C2=A0 Thanks for indirectly p=
ointing this out to me! =C2=A0 :}</div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:17 PM, Mikael Abrahamsson <=
span dir=3D"ltr">&lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">=
swmike@swm.pp.se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><s=
pan class=3D"">On Mon, 18 Jul 2016, Ted Lemon wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Zero.=C2=A0 See the discussion in draft-tldr-sutld-02 on this topic (search=
 for .home).<br>
</blockquote>
<br></span>
I guess you mean <a href=3D"https://tools.ietf.org/html/draft-tldr-sutld-ps=
-02" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft=
-tldr-sutld-ps-02</a> ?<br>
<br>
I can&#39;t find any mention of .home in it.<div class=3D"HOEnZb"><div clas=
s=3D"h5"><br>
<br>
-- <br>
Mikael Abrahamsson=C2=A0 =C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank">swmike@swm.pp.se</a><br>
</div></div></blockquote></div><br></div>

--001a11411dbac388b40537e9ba37--


From nobody Mon Jul 18 08:01:58 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 619EE12DA9E for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.187
X-Spam-Level: 
X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 rSCLLst2Yuex for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:01:55 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50E3A12DBEF for <homenet@ietf.org>; Mon, 18 Jul 2016 07:34:19 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 5061A280628; Mon, 18 Jul 2016 16:34:17 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 4B6C5280497; Mon, 18 Jul 2016 16:34:17 +0200 (CEST)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id 3F4DFB38038; Mon, 18 Jul 2016 16:33:47 +0200 (CEST)
Date: Mon, 18 Jul 2016 16:33:47 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
Message-ID: <20160718143347.GA26878@nic.fr>
References: <3A7CABDD-4D6D-4DF6-8EF5-4B7BF89EFAAD@jisc.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3A7CABDD-4D6D-4DF6-8EF5-4B7BF89EFAAD@jisc.ac.uk>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.3.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/jzAVJfOnOP-_23Vq77tQZbW3lxY>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] use of .home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:01:57 -0000

On Mon, Jul 18, 2016 at 01:50:25PM +0000,
 Tim Chown <Tim.Chown@jisc.ac.uk> wrote 
 a message of 69 lines which said:

> There are articles online that suggest 500M hits/day to the roots
> for .home,

L-root alone receives 180 Mhits/day so it is possible. (Source:
http://stats.dns.icann.org/hedgehog/ )

> and that .home is the heaviest used unallocated TLD.

No, it is .local. (Source: the same)


From nobody Mon Jul 18 08:13:56 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4ED12DBDE for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:13:55 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 kTgzavRHBTCe for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:13:52 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3DD012DCF2 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:49:55 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id f93so133721906lfi.2 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:49:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qvvLGi38TO86GvyKMTt7I+9jTB1IgMq6aoytNsjRWWk=; b=Ko4tL8RXvWKumujSVsg00URzwx4SccmazIde2ZEZMeJw4KLu8ZqiboLjFX3DhcejqR B7ciZiQsg+WhX1fNeaKDff4008CJjoE/95LK/5LBcy8ghnourU1v6TtpOBJbk24fIOlW Nhpx/pqxP+4/EJNydHh63CoPCjFtvoOsqSnjNFoaDh74Ktu7XRyc5ZVQhTZFILe4tAqy nsIm4luVpWjY47bxemy1HTzyOUaxoCpf4hYqrS91OUUY4K83ZJlOh++F2dW1EhNuIhVZ IGQ3ga/Gwifh5wW0g+ZJyaGgele3N8Hy9z1AFat1bg/g4Sv66HLX5Rx5iZnhc1XQ7Pn4 yNnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qvvLGi38TO86GvyKMTt7I+9jTB1IgMq6aoytNsjRWWk=; b=Ey6w19k7/tZlxVaOAFZK3sUXHox47rD5jwcPOBCS7hD57DOK0kpBgyYM68dLPf5aZj eMtmddHM7sk5PU3rbSIeSToVAvb2T4/FOG5X76zUW6rdL+TFdkRXFeD0bpzjYmu79sQ+ uyQBRPqy4ZZHyYFSZedoqHt4HFS0WNrqolBy8TA3A1uOhSfjQMl8u5FxQEDyBvN4yzdE 0OaXBUjB6FPyQ7rKrUGpclb7mTHdeoFN4cW14fGI1RyUqK9U2wpZ5zvDDb/tiwOZfAOk 1WtpWiPoTL0NUrtNYzRKbf+D5vFWxhAVTMA0pYsnRwaNyVbqS7sPEe6MAlgZyjdmTO8t H1pw==
X-Gm-Message-State: ALyK8tIj3AgECPZaJnlPyfrDK202zFwfswxVFXGefZ8jzBxX/Vj5m0M4OLczTVO0JwETl42UinufRoBD/BGIYw==
X-Received: by 10.25.26.194 with SMTP id a185mr16534140lfa.167.1468853394085;  Mon, 18 Jul 2016 07:49:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 07:49:14 -0700 (PDT)
In-Reply-To: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 16:49:14 +0200
Message-ID: <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11403bd8c82d450537ea140e
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/T5cG4O8HnhaMZruemrfiV7tffbQ>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:13:55 -0000

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

I wrote the ULA text because I thought there was already consensus, but
obviously whether or not there is consensus will come out if the document
is adopted by the WG, since if people object to the ULA, we can take it
out.   Personally I think that would be a mistake, and probably ideally the
ULA shouldn't be in the naming architecture since it's got little to do
with naming.

I would like to caution people against the idea that being less ambitious
will be a shortcut to success.   Andrew made this point at the mic, and it
is a really important point: a partial solution will become an obstacle to
a complete solution.   There are ways of diving this problem into chunks
that make sense, but we should have in mind the complete solution, even if
we approach it in a stepwise manner.   Otherwise we may wind up creating
problems that will be difficult to clean up later.

Of course, if we really don't care about all the things that the
architecture describes, that's another question entirely.   From my
perspective, though, there is nothing technically hard about what we're
talking about here; the main issue is that it's a substantial amount of
work.

On Mon, Jul 18, 2016 at 4:14 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> This is to repeat the comment that I made at the mike about
> draft-lemon-homenet-naming-architecture-01.
>
> Among other things, this draft suggests:
>
>    1. having a new ND option (Section 3.5);
>    2. defining a RESTful management API (Section 3.6);
>    3. the use of a local resolver (Section 4.5);
>    4. the use of a ULA (Section 5.5).
>
> These are some fairly ambitious requirements, and I believe that they
> deserve discussion separately from the naming issue.  More precisely:
>
> (1) Are wo to go to the effort of specifying and deploying a new ND option?
>
> (2) Defining a management API goes against the Homenet tradition, which
>     is to negotiate things over HNCP rather than defining new APIs.
>
> (3) HNCP does not currently mandate using a local resolver, and neither
>     does it define a means to advertise the address of a local resolver to
>     HNCP routers.  Are we requiring a full DNS server with DNSsec support
>     on each HNCP node, including an HNCP speaker that is not a router?
>     (Note that I'd be strongly opposed to requiring that every HNCP
>     speaker must be a router, and I think my opinion on putting a DNS
>     forwarder on every HNCP node is similar.)
>
> (4) Is there WG consensus on requiring a ULA?
>
> I don't have a definite opinion yet, but these requirements certainly make
> me nervous.
>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">I wrote the ULA text because I thought there was already c=
onsensus, but obviously whether or not there is consensus will come out if =
the document is adopted by the WG, since if people object to the ULA, we ca=
n take it out. =C2=A0 Personally I think that would be a mistake, and proba=
bly ideally the ULA shouldn&#39;t be in the naming architecture since it&#3=
9;s got little to do with naming.<div><br></div><div>I would like to cautio=
n people against the idea that being less ambitious will be a shortcut to s=
uccess. =C2=A0 Andrew made this point at the mic, and it is a really import=
ant point: a partial solution will become an obstacle to a complete solutio=
n. =C2=A0 There are ways of diving this problem into chunks that make sense=
, but we should have in mind the complete solution, even if we approach it =
in a stepwise manner. =C2=A0 Otherwise we may wind up creating problems tha=
t will be difficult to clean up later.</div><div><br></div><div>Of course, =
if we really don&#39;t care about all the things that the architecture desc=
ribes, that&#39;s another question entirely. =C2=A0 From my perspective, th=
ough, there is nothing technically hard about what we&#39;re talking about =
here; the main issue is that it&#39;s a substantial amount of work.</div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 1=
8, 2016 at 4:14 PM, Juliusz Chroboczek <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:jch@pps.univ-paris-diderot.fr" target=3D"_blank">jch@pps.univ-paris-did=
erot.fr</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is to =
repeat the comment that I made at the mike about<br>
draft-lemon-homenet-naming-architecture-01.<br>
<br>
Among other things, this draft suggests:<br>
<br>
=C2=A0 =C2=A01. having a new ND option (Section 3.5);<br>
=C2=A0 =C2=A02. defining a RESTful management API (Section 3.6);<br>
=C2=A0 =C2=A03. the use of a local resolver (Section 4.5);<br>
=C2=A0 =C2=A04. the use of a ULA (Section 5.5).<br>
<br>
These are some fairly ambitious requirements, and I believe that they<br>
deserve discussion separately from the naming issue.=C2=A0 More precisely:<=
br>
<br>
(1) Are wo to go to the effort of specifying and deploying a new ND option?=
<br>
<br>
(2) Defining a management API goes against the Homenet tradition, which<br>
=C2=A0 =C2=A0 is to negotiate things over HNCP rather than defining new API=
s.<br>
<br>
(3) HNCP does not currently mandate using a local resolver, and neither<br>
=C2=A0 =C2=A0 does it define a means to advertise the address of a local re=
solver to<br>
=C2=A0 =C2=A0 HNCP routers.=C2=A0 Are we requiring a full DNS server with D=
NSsec support<br>
=C2=A0 =C2=A0 on each HNCP node, including an HNCP speaker that is not a ro=
uter?<br>
=C2=A0 =C2=A0 (Note that I&#39;d be strongly opposed to requiring that ever=
y HNCP<br>
=C2=A0 =C2=A0 speaker must be a router, and I think my opinion on putting a=
 DNS<br>
=C2=A0 =C2=A0 forwarder on every HNCP node is similar.)<br>
<br>
(4) Is there WG consensus on requiring a ULA?<br>
<br>
I don&#39;t have a definite opinion yet, but these requirements certainly m=
ake<br>
me nervous.<br>
<br>
-- Juliusz<br>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote></div><br></div>

--001a11403bd8c82d450537ea140e--


From nobody Mon Jul 18 08:15:00 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DB712DEC8 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:14:59 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 10lS9u6FCJvC for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:14:57 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92D3A12DF05 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:51:42 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id g62so23692436lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:51:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LPLkjvpaSCzrGO1l7U2+CVsqHC+riWmevlekLWHnyS4=; b=TC3hGbI1G5tMB4sPrxkE25exWOSDbTZzaWC8LHio9xTu3jga4FuG0YKS9G7bS6KY+V McJBuoOqMvltCWKVEB9/WJ2ISQrhUlATq8doh+l8IJji0ezvehbck9nBWqF2SJiA5HvN FKfnitgvBnf3PX75Ty/EfS5Sacf31nIm6HXLeZHaZbU9FmfBz9Qf7A6ONia4PvImbOId zX7gEa55NKod6rxDxwrTO/u4pgePgTK7vxwh3bKeEdHjUCH+8JNrXYMmzpgeBfF8COI2 KeRkv86CfoD9UTvW3leElmY8w2yd5IPabJ4LVheyY6Pr5uOAIFrA/quDhn73Sh/kIttz vjWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LPLkjvpaSCzrGO1l7U2+CVsqHC+riWmevlekLWHnyS4=; b=P7PRzqidhJyuWsBXUxDbicsQKIKcY4j5RpATYsbdLrhrR0Pmn+aaK83qiVla9reCSX B/Ql10HUB3uR03Y0lgnTD843DXAlJ4CL8Pe6os37i/Jz0Yg/qRQgOdd5kSdHYxiVwf6H KiL2tepFgWzqPHuoFVYAy0st0OnOn0puH8reIWREc0IR5l2M51t4yFGHVHZ11OqjrotR I5rCsm4ITNQcGMlcnaIhtJFCWTUf9uyYDEiOTkCRnzuLB9KhHD1ghPIS99xNs5K8i5Ki HCUPXp3G9VwQ9qjozrtdzrTRCEJZtBWQIu+rNuVQFyGmbH7lP6wyBnje9rM/2dPJ4pEW GymQ==
X-Gm-Message-State: ALyK8tIKQYZ9qNHFRQpBjaLZMiGbdNEhEGaPfDYoUwTc22vLYXF6uD9dxHhQ0RPjS+lGs8EIsDk3PRfTUUMkBg==
X-Received: by 10.25.42.207 with SMTP id q198mr13815689lfq.181.1468853500866;  Mon, 18 Jul 2016 07:51:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 07:51:01 -0700 (PDT)
In-Reply-To: <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 16:51:01 +0200
Message-ID: <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11411dba2581c50537ea1b68
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/b4yxRP_odtsB_aVK6bMytbzm8vg>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:14:59 -0000

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

On Mon, Jul 18, 2016 at 4:49 PM, Ted Lemon <mellon@fugue.com> wrote:

> From my perspective, though, there is nothing technically hard about what
> we're talking about here; the main issue is that it's a substantial amount
> of work.
>

And, furthermore, we've built a lot of fairly complex and wonderful
technology at the IETF, and figuring out ways to automate deploying it is a
really useful exploration.   And something that your grad students might be
able to get some valuable experience with!   :)

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jul 18, 2016 at 4:49 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>From my perspec=
tive, though, there is nothing technically hard about what we&#39;re talkin=
g about here; the main issue is that it&#39;s a substantial amount of work.=
</div></div></blockquote><div><br></div><div>And, furthermore, we&#39;ve bu=
ilt a lot of fairly complex and wonderful technology at the IETF, and figur=
ing out ways to automate deploying it is a really useful exploration. =C2=
=A0 And something that your grad students might be able to get some valuabl=
e experience with! =C2=A0 :)=C2=A0</div></div></div></div>

--001a11411dba2581c50537ea1b68--


From nobody Mon Jul 18 08:16:24 2016
Return-Path: <terry.manderson@icann.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7ED712DEB9 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level: 
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 LZQSXyc914_W for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:16:22 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EA2712DF2A for <homenet@ietf.org>; Mon, 18 Jul 2016 07:53:14 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 18 Jul 2016 07:53:12 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Mon, 18 Jul 2016 07:53:11 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Ted Lemon <mellon@fugue.com>, HOMENET <homenet@ietf.org>
Thread-Topic: What I really meant by option 5
Thread-Index: AQHR4Pq0p3u6S/6prkGVEEz74ep2UaAfYzSA
Date: Mon, 18 Jul 2016 14:53:11 +0000
Message-ID: <D3B32A41.9629B%terry.manderson@icann.org>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
In-Reply-To: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3551734386_5524875"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/_DZpVIPQifjwRtYvrAYizderKyc>
Subject: Re: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:16:24 -0000

--B_3551734386_5524875
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Thank you for clarifying what you meant Ted.

Cheers
Terry



On 18/07/2016, 11:44 PM, "Ted Lemon" <mellon@fugue.com> wrote:

>The document as written causes some harm, but less harm than updating it.
>  The text in the document as written as to how domain names are resolved
>is not very good, and really really needs to be clarified with a detailed
>document that explains
> how name resolution works on the homenet.
>
>
>But I think we all accept that there's going to have to be a special-use
>top-level name allocated.   That name is either going to be '.home' or
>'.homenet' as far as I can tell.
>
>
>Andrew made a very good case for why it shouldn't be .home.   I agree
>with him, but not strongly enough that I would kick up a fuss of the
>consensus was to allocate .home anyway.    I also don't mind the
>two-stage process if IETF leadership is willing
> to do what I asked at the mic and actively keep the debate on track.
>
>
>But it's really a three-stage process: do the erratum as an update, then
>do the 6761 allocation of either .home or .homenet, then do the document
>that explains how it all works.   We need step two to happen _soon_ or we
>are in trouble.   Step 1 may be
> necessary and highly motivating because of the layer 9 problems that
>this mistake caused, but if we only do step 1 and then trail off on step
>2, the effect in the market is either going to be that everybody uses
>.home anyway, or else that everybody uses something
> different.   Neither of these outcomes are good outcomes.
>

--B_3551734386_5524875
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFFnX
9hjsrSZiaV0vgycZGZSvTw54MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE2MDcxODE0NTMwNlowDQYJKoZIhvcNAQEBBQAEggEApTuyguW7gUrTPy6UCyGs
gBqXfbBPYVjyGUFVvDB/PZ/f5FDL9RF7LeNL4q8uUZz81S8Pq7mT5DSubVZWxDz8O0w34OqG
4v4r+wViHeYz7iev0oknx2QGSkJezgJYmFR7wxnjARofpjLqw/ygp4QvyI+v/IVtm54p7m6y
cxLJ9ti1qz1qSzQ9OHbXQHf/mNyr2gknxS4gZmSoWOTZpgwhM9Q4zKZBJZ1G1HnEAhJDvYBt
ApVDsTLeIboojzSPUMvbM6B79jeZqTCEGnJH+mJlmtuMmE/c2xBqXhqODu/F2KgCkPqd/aiH
aB06bX5XN7gTgQD/7Pu7s/qkyUFXj34AvQ==

--B_3551734386_5524875--


From nobody Mon Jul 18 08:19:26 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A552A12DACC for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:19:23 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 VV_tKQpL5tjD for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:19:17 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9712412DF74 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:57:15 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id b199so133966938lfe.0 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:57:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rlsRM3zI+XZJVJV6nfZHF6wGFSXvtkr6fmRW+emGN2k=; b=FAL38rQ7AXY924cwbwUSLt3D6f6sgo8XVIwFGwLD9nSwYfxFbSbIQmIrD6WCiiQ19i VykTYhsXxSIFU8iUz5Dkp5xg8zA81z3PJSGLvW6M5qH/KrmOGajg/wfn/C8FTHsmY+wV oirWX/xU/L17YjcZ8tdbfuivqZcyZDX4CdWlhP3IJAVCujv0j3oOEQ41l2VBdR5m+dD9 xrdf4WALGXRriHlkojIj+vqP7bEwSyDJRUq3aavJivh5UbxM34lqHKMtN3wpEKxqi1jc F19vB3SUPd1GKAkaQXEbInVm60KADhJzXGPowAp2t7Ghhpx2FE5fr3FRl88tydZY33Q7 Z//g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rlsRM3zI+XZJVJV6nfZHF6wGFSXvtkr6fmRW+emGN2k=; b=CHS2cmt69g83LgRdl9AmjYoG3QGmAJvLsRU+7OePjT+fGFfMZTwXZIxNnqfnVn0Z3v pFkgFA/dm5QV5nFoYQVxdWkrXyRDoQN6pI2PrLjQzytxWFSyUZGaFhdlI7XN+vGmClEe Wi6yHsBEFie1r7s77DRuJRsFnpIUlaqivYvD/+w5vfwgouoQi24BSrHPJrwSqs9i01Fw eDem/Z4fmfi6FGwDJpi4I50/sZCI+PT/Ws2UDvgZ84BTLn4mn8+Yd4CSRwoTlXn9URZS HaH6WVN4cdCll9/g+yH8ZlOexzyYOCHRsed8sCmdPAPNPa2xrTzqmGplAqdO+h6UYARQ tJ1w==
X-Gm-Message-State: ALyK8tI65mW3n5VPpzNBuuG0rp3kHM3oAe9yq8FvbpElv3jR1RZV00zcHR/WJdpDv5Xr/05XMuFn0QcA9g3Nxw==
X-Received: by 10.25.42.207 with SMTP id q198mr13823980lfq.181.1468853833855;  Mon, 18 Jul 2016 07:57:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 07:56:34 -0700 (PDT)
In-Reply-To: <D3B32A41.9629B%terry.manderson@icann.org>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com> <D3B32A41.9629B%terry.manderson@icann.org>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 16:56:34 +0200
Message-ID: <CAPt1N1mRW9PL86qA0RqaNWiEE=CLRYFr=nanmqQqHNwqKRphRg@mail.gmail.com>
To: Terry Manderson <terry.manderson@icann.org>
Content-Type: multipart/alternative; boundary=001a11411dbafe87e20537ea2e82
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Cnv9r0VwC3JgjTLqrftDWLt065A>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:19:24 -0000

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

Sure.   Sorry if that was a bit of a shocking comment--I just feel like
we're at risk of backing off a cliff because we're looking in the wrong
direction.   Obviously we need to do something, but we have to be careful
that we don't create collateral damage in the process.

On Mon, Jul 18, 2016 at 4:53 PM, Terry Manderson <terry.manderson@icann.org>
wrote:

> Thank you for clarifying what you meant Ted.
>
> Cheers
> Terry
>
>
>
> On 18/07/2016, 11:44 PM, "Ted Lemon" <mellon@fugue.com> wrote:
>
> >The document as written causes some harm, but less harm than updating it.
> >  The text in the document as written as to how domain names are resolved
> >is not very good, and really really needs to be clarified with a detailed
> >document that explains
> > how name resolution works on the homenet.
> >
> >
> >But I think we all accept that there's going to have to be a special-use
> >top-level name allocated.   That name is either going to be '.home' or
> >'.homenet' as far as I can tell.
> >
> >
> >Andrew made a very good case for why it shouldn't be .home.   I agree
> >with him, but not strongly enough that I would kick up a fuss of the
> >consensus was to allocate .home anyway.    I also don't mind the
> >two-stage process if IETF leadership is willing
> > to do what I asked at the mic and actively keep the debate on track.
> >
> >
> >But it's really a three-stage process: do the erratum as an update, then
> >do the 6761 allocation of either .home or .homenet, then do the document
> >that explains how it all works.   We need step two to happen _soon_ or we
> >are in trouble.   Step 1 may be
> > necessary and highly motivating because of the layer 9 problems that
> >this mistake caused, but if we only do step 1 and then trail off on step
> >2, the effect in the market is either going to be that everybody uses
> >.home anyway, or else that everybody uses something
> > different.   Neither of these outcomes are good outcomes.
> >
>

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

<div dir=3D"ltr">Sure. =C2=A0 Sorry if that was a bit of a shocking comment=
--I just feel like we&#39;re at risk of backing off a cliff because we&#39;=
re looking in the wrong direction. =C2=A0 Obviously we need to do something=
, but we have to be careful that we don&#39;t create collateral damage in t=
he process.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jul 18, 2016 at 4:53 PM, Terry Manderson <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:terry.manderson@icann.org" target=3D"_blank">terry.manderson@=
icann.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank yo=
u for clarifying what you meant Ted.<br>
<br>
Cheers<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Terry<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On 18/07/2016, 11:44 PM, &quot;Ted Lemon&quot; &lt;<a href=3D"mailto:mellon=
@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
<br>
&gt;The document as written causes some harm, but less harm than updating i=
t.<br>
&gt;=C2=A0 The text in the document as written as to how domain names are r=
esolved<br>
&gt;is not very good, and really really needs to be clarified with a detail=
ed<br>
&gt;document that explains<br>
&gt; how name resolution works on the homenet.<br>
&gt;<br>
&gt;<br>
&gt;But I think we all accept that there&#39;s going to have to be a specia=
l-use<br>
&gt;top-level name allocated.=C2=A0 =C2=A0That name is either going to be &=
#39;.home&#39; or<br>
&gt;&#39;.homenet&#39; as far as I can tell.<br>
&gt;<br>
&gt;<br>
&gt;Andrew made a very good case for why it shouldn&#39;t be .home.=C2=A0 =
=C2=A0I agree<br>
&gt;with him, but not strongly enough that I would kick up a fuss of the<br=
>
&gt;consensus was to allocate .home anyway.=C2=A0 =C2=A0 I also don&#39;t m=
ind the<br>
&gt;two-stage process if IETF leadership is willing<br>
&gt; to do what I asked at the mic and actively keep the debate on track.<b=
r>
&gt;<br>
&gt;<br>
&gt;But it&#39;s really a three-stage process: do the erratum as an update,=
 then<br>
&gt;do the 6761 allocation of either .home or .homenet, then do the documen=
t<br>
&gt;that explains how it all works.=C2=A0 =C2=A0We need step two to happen =
_soon_ or we<br>
&gt;are in trouble.=C2=A0 =C2=A0Step 1 may be<br>
&gt; necessary and highly motivating because of the layer 9 problems that<b=
r>
&gt;this mistake caused, but if we only do step 1 and then trail off on ste=
p<br>
&gt;2, the effect in the market is either going to be that everybody uses<b=
r>
&gt;.home anyway, or else that everybody uses something<br>
&gt; different.=C2=A0 =C2=A0Neither of these outcomes are good outcomes.<br=
>
&gt;<br>
</div></div></blockquote></div><br></div>

--001a11411dbafe87e20537ea2e82--


From nobody Mon Jul 18 08:21:13 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3544F12DB98 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:21:11 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 bmOlHk9LqevZ for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:21:10 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFBCF12DBAD for <homenet@ietf.org>; Mon, 18 Jul 2016 08:01:11 -0700 (PDT)
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/56228) with ESMTP id u6IF19oC012114; Mon, 18 Jul 2016 17:01:09 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E72F061FA8; Mon, 18 Jul 2016 17:01:09 +0200 (CEST)
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 QKqfBcJfS9EK; Mon, 18 Jul 2016 17:01:08 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8F31661FA2; Mon, 18 Jul 2016 17:01:08 +0200 (CEST)
Date: Mon, 18 Jul 2016 17:01:10 +0200
Message-ID: <8760s30z49.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com>
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 [194.254.61.138]); Mon, 18 Jul 2016 17:01:09 +0200 (CEST)
X-Miltered: at korolev with ID 578CEF35.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578CEF35.002 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 : 578CEF35.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/lP329sheHDWHInKlgkEuAeukoZo>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:21:12 -0000

>> From my perspective, though, there is nothing technically hard about
>> what we're talking about here; the main issue is that it's a
>> substantial amount of work.

You're possibly right, I don't know, but I'm worried about implementability.
I'm very worried that you're apparently proscribing speaking HNCP without
speaking DNS.

> And something that your grad students might be able to get some valuable
> experience with! :)

All of the students working on HNCP are undergrads.  Some of them first years.
So ease of implementation is essential ;-)

-- Juliusz


From nobody Mon Jul 18 08:22:02 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB2E12D8AD for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:22:00 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 NzenFJSXKwRi for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:21:59 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79DD512DBF9 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:02:27 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id g62so23929930lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:02:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DIqJFUjeYbrgctFYOZNFF9vtHIdL7X8IZ5qNIKIS9PE=; b=HsYBpbObPk9SVZKnC3o1A+gUqSb87FoZy7Cp9ne++M1KByxBnRll16oP7zroWj8vP8 Ahyl+yuQOndWBRWSiLm5qI9pq1GBvr0dbPjWiB8NFikw3ag4SE+5CwLQxPS6Yv0Hb8Hv Xwmf9ZR/FHRpgElZO+E74uxGhLNrIGA45dn+we4Id3Qe+yqgl/v9HO5x/t7LT0S4ilSr G4qoXUZF39rUzGevTQgHM/efyeXq28H3LVee1j1bRbLAa1/9OaOJ9yfVa0wgd03wxtsF oPL8mVz1MEtKBAJXBbHur3x8/WK08YKj8ZV4p74ZeVMy86+IbhVIMZs3aXXIxKU50OE+ +opg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DIqJFUjeYbrgctFYOZNFF9vtHIdL7X8IZ5qNIKIS9PE=; b=jJzUORxlmM7sCAR4NgUuS7h1/AYlfCKwwvPNR2616FlNwn8QJGbnHsMFkeKwiUn7WY LHMkQQbNQgxTw7YphPWM0lO7IhQDO9s4QSbp5Bbca0zyHwfgl3lfLLZyrmAM+Ua59Wpg +9sz4M0xeWBTQxzve3wJ7waWZ3dcytUz1Ao34og9t44xlBNb6xifedXL9y+Lt83qz7if d9pCyMvPsleP5eG7hlI6SLmY/qKBUmTetwVa9sOVRLdcuLo0wwOZ/K6I8xy3xIhgHrAi LiPmkJNxxylqZWyg/H9IJmO77ne0Jo5Y3KPGyrcdrVIAZ5d8KiTlZgz6YCKarFYGrIRH J1sQ==
X-Gm-Message-State: ALyK8tKnQYP7f/5FDe8WpTRG9DiZRc6qPwfaJq2hinLn5b3aJOemhEujl2jzjy3u8xVKUNRy4PoiFeDhd+nljQ==
X-Received: by 10.25.159.10 with SMTP id i10mr4453971lfe.131.1468854145700; Mon, 18 Jul 2016 08:02:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 08:01:46 -0700 (PDT)
In-Reply-To: <20160718141641.GI43287@mx2.yitter.info>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 17:01:46 +0200
Message-ID: <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a11411c4294df640537ea4155
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/S545tUtZVOLqE6iP8_SmDh9BKxk>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:22:01 -0000

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

Yup.   In terms of minimizing risk to the IETF, switching to .homenet is
expedient--that's why I put it in the Homenet Naming/Service Discovery
Architecture doc.   Perhaps some homenet participants aren't aware of the
issues surrounding this.
The reason we are getting so much top-down push from IETF leadership on
this is not that IETF leadership are being political--it's that there's a
real cost to the IETF if one of the GTLD people decides that we have taken
a name for which they paid an application fee.   I apologize for glossing
over this in my earlier response.

If people are interested in better understanding this problem, I encourage
you to read this:
https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3

You can get more background by reading section 4 as well.   Bear in mind,
s/.local/.home/ in section 4.2.4.

On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
> >
> > .HOME has not been handed out by ICANN yet
>
> There are several applications for home in the root zone.  To my mind,
> that means that home has been claimed as being inside the global DNS
> context, and therefore is not available under RFC 6761.
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">Yup. =C2=A0 In terms of minimizing risk to the IETF, switc=
hing to .homenet is expedient--that&#39;s why I put it in the Homenet Namin=
g/Service Discovery Architecture doc. =C2=A0 Perhaps some homenet participa=
nts aren&#39;t aware of the issues surrounding this. =C2=A0=C2=A0<div>The r=
eason we are getting so much top-down push from IETF leadership on this is =
not that IETF leadership are being political--it&#39;s that there&#39;s a r=
eal cost to the IETF if one of the GTLD people decides that we have taken a=
 name for which they paid an application fee. =C2=A0 I apologize for glossi=
ng over this in my earlier response.<br></div><div><div><br></div><div>If p=
eople are interested in better understanding this problem, I encourage you =
to read this:=C2=A0<a href=3D"https://tools.ietf.org/html/draft-tldr-sutld-=
ps-02#section-3">https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section=
-3</a></div></div><div><br></div><div>You can get more background by readin=
g section 4 as well. =C2=A0 Bear in mind, s/.local/.home/ in section 4.2.4.=
</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mo=
n, Jul 18, 2016 at 4:16 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">O=
n Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:<br>
&gt;<br>
&gt; .HOME has not been handed out by ICANN yet<br>
<br>
</span>There are several applications for home in the root zone.=C2=A0 To m=
y mind,<br>
that means that home has been claimed as being inside the global DNS<br>
context, and therefore is not available under RFC 6761.<br>
<br>
Best regards,<br>
<br>
A<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div></div></blockquote></div><br></div>

--001a11411c4294df640537ea4155--


From nobody Mon Jul 18 08:23:39 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0198F12DA52 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1hNm1Nnm3Hai for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:23:36 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A26112DC35 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:04:57 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id u25so93119089qtb.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=HdRDlkHHLeMzhjf33oUg2tB9cppfKZWEgg/bSUNlIvo=; b=bVL6322gGFpdYLZJuY63VWY08ujWmrPZGmk2EZAQmoTIN15OOIICROQB64dRoAMsS4 1RA5SnJG/NE8x7fViFS6zHjJ84yUcYC1Y1y2TfC/nVq9r9bYEOZisNyXXIymmWTCtXBw Lv6YbbV7u8LQpKZiHiHA+yvTq64rWTywPsw0DPJqIFJV1HBYSLQxEik2XisNhYCBPcUE K01l8QAAr+R+E7w/nU8BADKyE2oDxFvZue7zwNE5XhM6qXkCE8MRYEohFAaSUABzPCug 6ldTaR+X/HUHotL9h0HmOu9M61RaF1orAE4kjPNHFrPL7T3eJX5wQ9/xOETTWTvFJVMJ 1ElA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=HdRDlkHHLeMzhjf33oUg2tB9cppfKZWEgg/bSUNlIvo=; b=MXhZueEgS56REkzyn+hMXr+17zeV56/SJmdsKtmswIGwv4+06RE+dmks6bOTRmfPnU dgZQ6/DfBC+M92XR6v0+xQLoMEGyIzMF1qcOKGDxRLHY2iPk7ciArDHgr4N57hqitd0U mbxgu3rlCMo+0qqdH1bsflz9IOMOpZu95Xdhi/nBaA63jt/3jpB9dYfdj57IpVPZP4Jy 5UiW3n4eUAp9gspGCrEFTjgD2NT/G0bffIhs0kvv3WYFFD6YUr0cbybyjcO4m2WLdiyt T1TmdN9TpZrkCtSURYzrnnp91QjF882m4zN+cs4c4jkLtvBsyK8XAiMELhkPQ+K0WKKh O5Ow==
X-Gm-Message-State: ALyK8tIhzNjCVtohRb7CLoheWmqIKije+NDHUufp0b4pK5624Rl2NIsGrhhwh/r6+4e2+w==
X-Received: by 10.200.51.173 with SMTP id c42mr51883094qtb.14.1468854296501; Mon, 18 Jul 2016 08:04:56 -0700 (PDT)
Received: from ?IPv6:2001:420:c0c4:1008::129? ([2001:420:c0c4:1008::129]) by smtp.gmail.com with ESMTPSA id m11sm1691140qke.36.2016.07.18.08.04.55 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 18 Jul 2016 08:04:55 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C7284EC6-6291-4D4C-9F54-95EF1A7E0B76"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
Date: Mon, 18 Jul 2016 17:04:51 +0200
Message-Id: <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/wHMKl3LgXTqYZdX_OUlEmDzuz-M>
Cc: HOMENET <homenet@ietf.org>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:23:38 -0000

--Apple-Mail=_C7284EC6-6291-4D4C-9F54-95EF1A7E0B76
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 18, 2016, at 3:44 PM 7/18/16, Ted Lemon <mellon@fugue.com> =
wrote:
>=20
> The document as written causes some harm, but less harm than updating =
it.   The text in the document as written as to how domain names are =
resolved is not very good, and really really needs to be clarified with =
a detailed document that explains how name resolution works on the =
homenet.

I agree with Ted 100% about the text in the document regarding name =
resolution.  In my opinion, the proper organization for the =
specifications here would be to ensure that the details of name =
resolution in homenet are correctly specified in Ted's document or =
another separate document, with text in the HNCP document the specifies =
how the requisite configuration information is carried in HNCP.

> But I think we all accept that there's going to have to be a =
special-use top-level name allocated.   That name is either going to be =
'.home' or '.homenet' as far as I can tell.
>=20
> Andrew made a very good case for why it shouldn't be .home.   I agree =
with him, but not strongly enough that I would kick up a fuss of the =
consensus was to allocate .home anyway.    I also don't mind the =
two-stage process if IETF leadership is willing to do what I asked at =
the mic and actively keep the debate on track.
>=20
> But it's really a three-stage process: do the erratum as an update, =
then do the 6761 allocation of either .home or .homenet, then do the =
document that explains how it all works.   We need step two to happen =
_soon_ or we are in trouble.   Step 1 may be necessary and highly =
motivating because of the layer 9 problems that this mistake caused, but =
if we only do step 1 and then trail off on step 2, the effect in the =
market is either going to be that everybody uses .home anyway, or else =
that everybody uses something different.   Neither of these outcomes are =
good outcomes.

I agree with Ted 100% here, as well.  We need to solve immediately the =
specific problem that .home was either delegated as a DNS TLD without =
appropriate process, or was designated as a Special Use Name without an =
associated entry in the registry.  (In my opinion, RFC 7788 is not clear =
about which of those two buckets ".home" falls into.)  Then we need to =
specify the behavior of the new label, which I assume will be a Special =
use name, and add it to the Special Use Names registry as quickly as =
possible.

- Ralph

> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_C7284EC6-6291-4D4C-9F54-95EF1A7E0B76
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXjPAUAAoJEINeeBNmFjV5nOEQAMEYBBE6cZO0AP1OH3uwZafp
WVKrN2moI/0epj71x29rmkgLxSchXzZFqZZw1ka9Usfr6vHSXVhw6fEJiVRe89mc
mggcr4P0Lc7NERjEasUA7q9ajlcwgHjSmgqn/F1HFP4p1q+cOqf8edD7ekzrhie2
TR6vSVG/199f5SNKnQHVV4mOkX5iOXhe6ELsryiWNlrito1vtuaB5c+JOhvWxEnD
36sSSMrLY3eNCOgWOVlTUHK3OmcrKFVeesFvs7lBUsTgr7FzC00B2NlxSEmCJ8Zw
hzWAOL+5iX92z5BKJ+pUfKsFrB2w8WySx6gcIbbxHWcs+KLDh38Z/Skiq/UOXJHe
LMAh1az3LIzZtHQid6vo2xleizGX60XRmrJu9hciFKCgESciiLEIxoscTzQpAgda
lDGyZaLUWuiy7v7LzaUBhKt7FhYcYVMHki00xR/E/uR+xdURFTHJMKuu/JK+EDdR
bUlgfhlSTCJ3+uTWhfZMStdsLK9Rs5um/TiWjoyCT20FscVv9a7XqJpEC8fBIedg
CwsP9zOMakTF/tfEXtM8T3AyB2DQUR2z669spAqkQnK3BgA1ovWJY5r13jyyOQsZ
RsuCtPWOZAs+jVLLj6Chp947aCeyWPWUGi1YxVkExz+9yFNQDBdxuMx0dTyqahpu
NeQxt1qIo749fKr1vig6
=9Or8
-----END PGP SIGNATURE-----

--Apple-Mail=_C7284EC6-6291-4D4C-9F54-95EF1A7E0B76--


From nobody Mon Jul 18 08:24:22 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33B3412DC3F for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:24:20 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 kk5QzCRnwbGX for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:24:18 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B89612DDC4 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:05:22 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id g62so23995402lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:05:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6fM/ZlVHB814eowD95/s0OHtV73ZYzBrEkCLTb2FFHk=; b=EIdbLvUpe9njQwUD6xuXdKlEygi0f72aVripwR0z7KHDp/ngOj8aLMTyIpNk07TYhW nbVNJu4IITeqUXeL9efygwBNnJNo9PuPe1Vi1LhXie1Yz0ENOvT6pBTbFMskIvuGrX/l mtuuZjZMg6HY8HPBR+a80MfywMfjgpKqM0FHT4MWPftcEUz7vmBgE2n8ucSqBrvJHZYf 9x2zSVqKPQKJnqdlqWwacJkmeyj8GCPAurcF2tw1+H8VnVP3nUS4ihS458mNgkypt9Kd +ivXo/8H4jal8JoR81/cZ4SE7QEDK2HKiCU4K3hh56iD5+ofSFULpCG84PNQGYlbRt7L skVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6fM/ZlVHB814eowD95/s0OHtV73ZYzBrEkCLTb2FFHk=; b=LIedUecQwXOxr4Pi7hgIIuaOjkNnwa0s6i0BnRkByqJDFP0VsDK/jBkKoO6hJ+fe7+ g08OUUYRmDG30VxgG+K8krEOv3bXQTljH6QNWWaGWcIa+dPzv6IFuyeElQN27WGfEiPX Ry2r+zI1cA1IReXO5qIjtCPEQAYni2cgmx0dpSfcUsunmh422wOO4Yc0Q6bsiUx1KByP 9IVrhohqcJsgY+tUPFVW3ECpT1F+zpNTiNugxNGV8mqNtNoa03AqdmpLqkbWf37/te17 IZ9fr0Uh8D9sU2+McgEyu2pZ8RaDCq0i3ovDlXlt1CLE4nomHsXt11mIrYxTd+YC1ZEt P5Vw==
X-Gm-Message-State: ALyK8tJ5zdkwr2WB4sMAROjpZ3LloRFtXx6hKIcDY7GM20uojxzOAnDaLS7CT9hsgkwdUudYYWMr9LwGf2z2vA==
X-Received: by 10.25.159.10 with SMTP id i10mr4460769lfe.131.1468854320446; Mon, 18 Jul 2016 08:05:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 08:04:29 -0700 (PDT)
In-Reply-To: <8760s30z49.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 17:04:29 +0200
Message-ID: <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11411c42ff41720537ea4be9
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/QmLJG42K1v7s0EvkAzFwR4nZvzI>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:24:20 -0000

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

I don't think the document is proscribing speaking HNCP without speaking
DNS.   A homenet router that doesn't support cross-link naming at all is
not useless.   It's just not as useful as one that does.

I think you are overestimating the complexity of implementing this, but
your undergrads can help us to test that theory.   :)

On Mon, Jul 18, 2016 at 5:01 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> >> From my perspective, though, there is nothing technically hard about
> >> what we're talking about here; the main issue is that it's a
> >> substantial amount of work.
>
> You're possibly right, I don't know, but I'm worried about
> implementability.
> I'm very worried that you're apparently proscribing speaking HNCP without
> speaking DNS.
>
> > And something that your grad students might be able to get some valuable
> > experience with! :)
>
> All of the students working on HNCP are undergrads.  Some of them first
> years.
> So ease of implementation is essential ;-)
>
> -- Juliusz
>

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

<div dir=3D"ltr">I don&#39;t think the document is proscribing speaking HNC=
P without speaking DNS. =C2=A0 A homenet router that doesn&#39;t support cr=
oss-link naming at all is not useless. =C2=A0 It&#39;s just not as useful a=
s one that does.<div><br></div><div>I think you are overestimating the comp=
lexity of implementing this, but your undergrads can help us to test that t=
heory. =C2=A0 :)</div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Mon, Jul 18, 2016 at 5:01 PM, Juliusz Chroboczek <span dir=3D=
"ltr">&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" target=3D"_blank=
">jch@pps.univ-paris-diderot.fr</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">&gt;&gt; From my perspective, though, there =
is nothing technically hard about<br>
&gt;&gt; what we&#39;re talking about here; the main issue is that it&#39;s=
 a<br>
&gt;&gt; substantial amount of work.<br>
<br>
</span>You&#39;re possibly right, I don&#39;t know, but I&#39;m worried abo=
ut implementability.<br>
I&#39;m very worried that you&#39;re apparently proscribing speaking HNCP w=
ithout<br>
speaking DNS.<br>
<span class=3D""><br>
&gt; And something that your grad students might be able to get some valuab=
le<br>
&gt; experience with! :)<br>
<br>
</span>All of the students working on HNCP are undergrads.=C2=A0 Some of th=
em first years.<br>
So ease of implementation is essential ;-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
</font></span></blockquote></div><br></div>

--001a11411c42ff41720537ea4be9--


From nobody Mon Jul 18 08:28:44 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1B912DC95 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 cv0JO0-diyOO for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:28:38 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A8D712DCCE for <homenet@ietf.org>; Mon, 18 Jul 2016 08:11:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3SxcJ7AcqMizUkqJZWImuxFmv0mu3NViNQfljX0h3SA=; b=bWFqqfNKdh5SUZfcaCJaA2QIWHOSChTOWzqd38PmZq0WBKo/LOFck9uz510RiwKjBFY8cettfFZrCiHWBbrWOKwutIuQ3wEhY+fS/x/wgVVZ0Zxxi6PksZDyRFWUDuLtbemD4ZD/AIbZHLbRodXB71X4n6Xa+S9I+HHkhd9ot74=
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0214.outbound.protection.outlook.com [213.199.154.214]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-9-Ipa_b5_mPdSH7oi9Gb9ibw-1; Mon, 18 Jul 2016 16:11:20 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (TLS) id 15.1.534.14; Mon, 18 Jul 2016 15:11:18 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.019; Mon, 18 Jul 2016 15:11:18 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [homenet] RFC 7788 and ".home"
Thread-Index: AQHR4PymvDPjF4js+UuI51F7RqZsnKAeOFIAgAATSAA=
Date: Mon, 18 Jul 2016 15:11:18 +0000
Message-ID: <D847985B-016C-411E-B80D-9020A23E0EB4@jisc.ac.uk>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com>
In-Reply-To: <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:152:3895:6b8e:f55b:2338]
x-ms-office365-filtering-correlation-id: 14cc344d-4654-437b-31c9-08d3af1dc53d
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 20:WCFWPZtki8+T4qbGXqXwfh2jtL2ZkyFDvv95W1J0A0FLkdWE2CdS8eUbrvGyAozkII+WVJ2V8VuLD+EKsrwqqaGoGb2g39iR4tuV8h6TXazRPDKNdcBzmi71NHH/5xrnnuvK7XJA/27DnQjHERhZbX7WDr6YAWqvO+lS0plSLFU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB4548E651D9A0FCC7292150CD6360@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(377454003)(189002)(24454002)(252514010)(199003)(50226002)(86362001)(8676002)(36756003)(87936001)(83716003)(5002640100001)(81166006)(10400500002)(106116001)(19617315012)(81156014)(105586002)(106356001)(8936002)(57306001)(101416001)(97736004)(122556002)(6116002)(102836003)(3280700002)(15975445007)(77096005)(16236675004)(92566002)(4326007)(586003)(68736007)(50986999)(2950100001)(76176999)(33656002)(3660700001)(110136002)(189998001)(82746002)(7736002)(19580395003)(7846002)(2900100001)(7906003)(19580405001)(2906002)(74482002)(93886004)(11100500001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2016 15:11:18.6835 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
X-MC-Unique: Ipa_b5_mPdSH7oi9Gb9ibw-1
Content-Type: multipart/alternative; boundary="_000_D847985B016C411EB80D9020A23E0EB4jiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/4WljMGCWf_uNhg8cRRdKC9lteZg>
Cc: HOMENET <homenet@ietf.org>, Terry Manderson <terry.manderson@icann.org>, Ray Bellis <ray@bellis.me.uk>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:28:43 -0000

--_000_D847985B016C411EB80D9020A23E0EB4jiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Hi Ted,

On 18 Jul 2016, at 15:03, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.c=
om>> wrote:

Zero.   See the discussion in draft-tldr-sutld-02 on this topic (search for=
 .home).

I don=92t see =93home=94 explicitly cited in https://tools.ietf.org/html/dr=
aft-tldr-sutld-ps-02, but it=92s an interesting read nonetheless.

Tim


On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahamsson <swmike@swm.pp.se<mailt=
o:swmike@swm.pp.se>> wrote:

The option 4 mentioned updating RFC7788. It's not clear to me what this upd=
ate would be.

.HOME has not been handed out by ICANN yet, what's the odds that RFC6761 pr=
ocess reserving .HOME for special use would succeed?

--
Mikael Abrahamsson    email: swmike@swm.pp.se<mailto:swmike@swm.pp.se>


_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet

_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet


--_000_D847985B016C411EB80D9020A23E0EB4jiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <C0046B005D0BBD4A9B3AF5ADDC810635@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Hi Ted,
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 18 Jul 2016, at 15:03, Ted Lemon &lt;<a href=3D"mailto:m=
ellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div dir=3D"ltr" class=3D"">Zero. &nbsp; See the discussion in draft-tldr-s=
utld-02 on this topic (search for .home).</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
I don=92t see =93home=94 explicitly cited in&nbsp;<a href=3D"https://tools.=
ietf.org/html/draft-tldr-sutld-ps-02" class=3D"">https://tools.ietf.org/htm=
l/draft-tldr-sutld-ps-02</a>, but it=92s an interesting read nonetheless.</=
div>
<div><br class=3D"">
</div>
<div>Tim</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahams=
son <span dir=3D"ltr" class=3D"">
&lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank" class=3D"">swmike=
@swm.pp.se</a>&gt;</span> wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br class=3D"">
The option 4 mentioned updating RFC7788. It's not clear to me what this upd=
ate would be.<br class=3D"">
<br class=3D"">
.HOME has not been handed out by ICANN yet, what's the odds that RFC6761 pr=
ocess reserving .HOME for special use would succeed?<span class=3D"HOEnZb">=
<font color=3D"#888888" class=3D""><br class=3D"">
<br class=3D"">
-- <br class=3D"">
Mikael Abrahamsson&nbsp; &nbsp; email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank" class=3D"">
swmike@swm.pp.se</a></font></span>
<div class=3D"HOEnZb">
<div class=3D"h5"><br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank" class=3D"">homenet@ie=
tf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank" class=3D"">https://www.ietf.org/mailman/listinfo/homene=
t</a><br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br clas=
s=3D"">
https://www.ietf.org/mailman/listinfo/homenet<br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_D847985B016C411EB80D9020A23E0EB4jiscacuk_--


From nobody Mon Jul 18 08:31:06 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C9C12DB52 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:31:04 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 ghh6h-SsSDAf for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:31:02 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5139812DECB for <homenet@ietf.org>; Mon, 18 Jul 2016 08:15:03 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id g62so24204739lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1Z/IUb9kAF6kMwzv0sXQv4YwY+xhxH0exfZKHsSmKvg=; b=rS/wlYsxQG330ILe6FKPw2TiZ4w1K63zn4lklMwD7EFDTCSPC2HmhG6HuR5aiRQ1ni FdPHs909o6y50WbihW2JTJKMeWNn+EU2WpTIKr75+JebQQLOWZ201ZMCbcRQlYrjts8N KW0/TSwfp2gSaz1zfAOWfDOdwjruHV3WwZ9dy8V7U3LXCigqy5NjRuZcj8B8MFpNV6Im Gc+s0134xF2vOjNIfs7o2hfcqybhERFBGKWsSS7SBCDO1FeF3hIrJz3KjhnYCunKokE0 J915tzLXfLWwx/sLqp5Olhl8yimYOjNe1Ct4whWZoCt6uGaX4u2etYa19bhQPvXnXOr8 L10w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1Z/IUb9kAF6kMwzv0sXQv4YwY+xhxH0exfZKHsSmKvg=; b=kqYePBYzNhWEALKkBeG4jwkH3FuuUON0v2N+VxWlLBg2mOBzphKm9gVoBWojZL9JL0 VqwXCNjpEmi0PejGZSFtaSTMhGnIjuh84koKXFVboS3VB39oo+U6yJXfjwierbWLRxxE PvqC2YxU1xdTuq4CQlQTVmj7moo/rF+suhyV0pn+N+a9igr7aXxWp+AA2weY0hT3E+U/ Bwb5LLeRBhFE51hlpLiwxJJH1CdBlXzQtoWgAMrIr5dkfbLrTQCtyMbyXQxwUlc/Qf1A gLTG2xHfBl+X1L3wZluOymbyoYLxTqOyBJV0qFYJYwT7uUIZYmt6cStohVvYvApeYmJM vxLg==
X-Gm-Message-State: ALyK8tLwmwaLpf7E9e8VKhiWHF5BtQlDfM145mI42rE341Hg6T3jPhLkaQdy0DczyNYoCQfmAvox9D/Vh1dALQ==
X-Received: by 10.25.42.207 with SMTP id q198mr13856997lfq.181.1468854901510;  Mon, 18 Jul 2016 08:15:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.148.11 with HTTP; Mon, 18 Jul 2016 08:14:21 -0700 (PDT)
In-Reply-To: <D847985B-016C-411E-B80D-9020A23E0EB4@jisc.ac.uk>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <CAPt1N1=G47cKSXMj4u0LKMTtnEakWOU_gArG41efCj8yOy3ogg@mail.gmail.com> <D847985B-016C-411E-B80D-9020A23E0EB4@jisc.ac.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 17:14:21 +0200
Message-ID: <CAPt1N1=Np3xMG13=H+sRCXiqLrrvYWkX=X1PaGdnJM_VzmAprQ@mail.gmail.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
Content-Type: multipart/alternative; boundary=001a11411dbaa19ed50537ea6e57
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/sk5VvIj9V6xUd-t7ln9cpGUuNFU>
Cc: HOMENET <homenet@ietf.org>, Terry Manderson <terry.manderson@icann.org>, Ray Bellis <ray@bellis.me.uk>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:31:05 -0000

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

I accidentally wrote ".local" in section 4.2.4 instead of ".home."

On Mon, Jul 18, 2016 at 5:11 PM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:

> Hi Ted,
>
> On 18 Jul 2016, at 15:03, Ted Lemon <mellon@fugue.com> wrote:
>
> Zero.   See the discussion in draft-tldr-sutld-02 on this topic (search
> for .home).
>
>
> I don=E2=80=99t see =E2=80=9Chome=E2=80=9D explicitly cited in
> https://tools.ietf.org/html/draft-tldr-sutld-ps-02, but it=E2=80=99s an
> interesting read nonetheless.
>
> Tim
>
>
> On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahamsson <swmike@swm.pp.se>
> wrote:
>
>>
>> The option 4 mentioned updating RFC7788. It's not clear to me what this
>> update would be.
>>
>> .HOME has not been handed out by ICANN yet, what's the odds that RFC6761
>> process reserving .HOME for special use would succeed?
>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
>

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

<div dir=3D"ltr">I accidentally wrote &quot;.local&quot; in section 4.2.4 i=
nstead of &quot;.home.&quot;</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Jul 18, 2016 at 5:11 PM, Tim Chown <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Tim.Chown@jisc.ac.uk" target=3D"_blank">Tim.Chown@=
jisc.ac.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi Ted,
<div><br>
<div><span class=3D"">
<blockquote type=3D"cite">
<div>On 18 Jul 2016, at 15:03, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue=
.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:</div>
<br>
<div>
<div dir=3D"ltr">Zero. =C2=A0 See the discussion in draft-tldr-sutld-02 on =
this topic (search for .home).</div>
</div>
</blockquote>
<div><br>
</div></span>
I don=E2=80=99t see =E2=80=9Chome=E2=80=9D explicitly cited in=C2=A0<a href=
=3D"https://tools.ietf.org/html/draft-tldr-sutld-ps-02" target=3D"_blank">h=
ttps://tools.ietf.org/html/draft-tldr-sutld-ps-02</a>, but it=E2=80=99s an =
interesting read nonetheless.</div><span class=3D"HOEnZb"><font color=3D"#8=
88888">
<div><br>
</div>
<div>Tim</div></font></span><span class=3D"">
<div><br>
<blockquote type=3D"cite">
<div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 3:33 PM, Mikael Abrahams=
son <span dir=3D"ltr">
&lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.se<=
/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">
<br>
The option 4 mentioned updating RFC7788. It&#39;s not clear to me what this=
 update would be.<br>
<br>
.HOME has not been handed out by ICANN yet, what&#39;s the odds that RFC676=
1 process reserving .HOME for special use would succeed?<span><font color=
=3D"#888888"><br>
<br>
-- <br>
Mikael Abrahamsson=C2=A0 =C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank">
swmike@swm.pp.se</a></font></span>
<div>
<div><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">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>
</div>
</blockquote>
</div>
<br>
</span></div>
</div>

</blockquote></div><br></div>

--001a11411dbaa19ed50537ea6e57--


From nobody Mon Jul 18 08:36:55 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624AB12DBA0 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WsxGfnjY977T for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:36:41 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9807412DBFB for <homenet@ietf.org>; Mon, 18 Jul 2016 08:22:59 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id f65so107810916wmi.0 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=1K7wK4YnKBOgwvhZYd/FDYpIm9XRYljZC9FpFsFwObI=; b=pobgHYnAHadLQ1MD8W1mXr115imsdlGlVpriNp+smm1ICxzVA3SujKJjNjZWbKIYnd Uk0X0qZDYI+lPooLYtKP7x9uvPADNAueX63vTklA1+90bHxZWfUsX2vAuTmM/vGlEQeJ J5IPfDnQ3NRxzrNraQ3vRvgwyVV9EipKXLqV0Jvo6vlmb5zrAg7S9nbNcSFbGBAxs9WD 04Nz0z2Jq2564UIPSFtcqhoUJWEVVGmEXvgtqCi8k3nMAWwb/ZFZLbCcP+R4Y2egju/W S+9CMUIjwFW2UtzYXo4nkB8Q5UFaZmgZbpmaWcN/PqephBUbSGx8Fsw8YXo5iUvQCH32 l1Ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=1K7wK4YnKBOgwvhZYd/FDYpIm9XRYljZC9FpFsFwObI=; b=GVgPKwjj3yh2Kx7LG6enj+u7e3+ymXc1lvQkNMOGqwY5MbSoWzPH+I+Qgoo50D7GNk Mtr8+oZZMU0AWlZ+MP+9gmuKYE/8uDP5jV9oAYi+j7ewvqAXRMbHIaJHcz4rohlikP4A /fc9aqtYc7rPattw6iR9VvZVpB7ljv0kj5xPLODDLFPMfxdlV5QJKlxCdGMBAVyfKrYN ZDKhMDnjSRpLq7WWKVq6Rj5HqLdnsq6zwtnnPUGpt5j+vgtI6DRCMlQh9tmWxEbklzhJ X3suYAjJPOc8zrl/D0TFStnxfjtqHFBdNQXecRBif1F5swFT1ewv91424yk/B4/a2c1C juog==
X-Gm-Message-State: ALyK8tIHY7eNPS2I1ivgbMDHWc4D3xPq4c2a/97ihyWWP50J92+MuX7tC6psJDXGnNMX5Q==
X-Received: by 10.195.13.34 with SMTP id ev2mr1804096wjd.117.1468855377861; Mon, 18 Jul 2016 08:22:57 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id vp5sm1809410wjb.43.2016.07.18.08.22.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 08:22:56 -0700 (PDT)
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com>
Date: Tue, 19 Jul 2016 03:22:57 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160718141641.GI43287@mx2.yitter.info>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/GV_bBNyHm1knCZnKuGOWbNZfgtY>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:36:53 -0000

On 19/07/2016 02:16, Andrew Sullivan wrote:
> On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
>>
>> .HOME has not been handed out by ICANN yet
> 
> There are several applications for home in the root zone.  To my mind,
> that means that home has been claimed as being inside the global DNS
> context, and therefore is not available under RFC 6761.

I don't get that. There's nothing about that in RFC 6761, which is mainly
very boring stuff that could be written up for this case, regardless
of the actual domain name. It's our own self-imposed bureaucracy.

RFC 6761 is one thing, but RFC 2860 is another. Under note (a)
to clause 4.3 of that MoU, the IETF can direct IANA to reserve
.$WHATEVER$. for technical use.

Doing so for .home. would be entertaining, of course. Doing so
for .homenet. seems plausible.

   Brian


From nobody Mon Jul 18 08:37:49 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4077412DA74 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:37:47 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 vDkFEGBQVDIN for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:37:45 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AB8612DC33 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:24:47 -0700 (PDT)
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/56228) with ESMTP id u6IFOjLD026218; Mon, 18 Jul 2016 17:24:45 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 6B79D61FA6; Mon, 18 Jul 2016 17:24:45 +0200 (CEST)
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 2-dsI22raePM; Mon, 18 Jul 2016 17:24:44 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0321B61FA2; Mon, 18 Jul 2016 17:24:43 +0200 (CEST)
Date: Mon, 18 Jul 2016 17:24:46 +0200
Message-ID: <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com>
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 [194.254.61.138]); Mon, 18 Jul 2016 17:24:45 +0200 (CEST)
X-Miltered: at korolev with ID 578CF4BD.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578CF4BD.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 : 578CF4BD.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: <https://mailarchive.ietf.org/arch/msg/homenet/xTRC8gF-D38eUd6oQVgvvOmz36k>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:37:48 -0000

> I don't think the document is proscribing speaking HNCP without speaking
> DNS.

Then I've misunderstood something, my bad.

Suppose you have routers A and B on a link, and A implements DNS while
B doesn't.  How does B find out that it should advertise A's DNS server in
RA, DHCPv4 and DHCPv6?

-- Juliusz



From nobody Mon Jul 18 08:45:21 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F98F12DA3B for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 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, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 XALIu2oQR_Q3 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:45:16 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1308C12DA91 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:40:04 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id EF456A3; Mon, 18 Jul 2016 17:40:01 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1468856401; bh=GQVcKViIMEM50w9/NT77e9lQvi05bAV1stEj9PKuVVc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=TDRQCBgmEC9CiuVm3XwW7/QgNUs32GicWAuuIUh4f0M2SXRZnJcdAANK2T3NQq9zj o7cCiMweGcmPoRd4/ZDoB0d61FgmGK6KUj44eG2c8/4/xxr2KrbKwtqoMXVTfoVORg likUasOgCnB6Ikfoz58zyGqRl37GiEHPRqSNvebQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E7187A2; Mon, 18 Jul 2016 17:40:01 +0200 (CEST)
Date: Mon, 18 Jul 2016 17:40:01 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com>
Message-ID: <alpine.DEB.2.02.1607181738440.2309@uplift.swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@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; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pJLgodUXZxScLdqv02rqWLU5mrA>
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:45:19 -0000

On Tue, 19 Jul 2016, Brian E Carpenter wrote:

> Doing so for .home. would be entertaining, of course. Doing so for 
> .homenet. seems plausible.

It seems to already be used for that, and as said before, ICANN has 
refused all applications for .home already.

.home is tainted by ad-hoc use. The ad-hoc use seems to be exactly the 
same use as RFC7788 uses it for.

Why not formalise it?

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


From nobody Mon Jul 18 08:47:02 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C768212DA60 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zyk-wh6nLJNF for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:46:59 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1E912DAE8 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:43:07 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id f126so108876742wma.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZDWjtHnZKatoUmSnfm3o/zE4jIsN/mTf7ee4EH19+AA=; b=cwM0zVm1JX1NY4ZDY8QIIFfzA+6KFfTV6SFuU6bRSmYtkaRr/nrWiKcqGqLDTJX5Js TPl/9FWhooP8kA243ZHM/hZ/YKjz0cUBg15+L8oXQpUmtEj2B1wQsSFFA1YFKqg7tEhn L233v2pYACS5EDYu+wiCsSdWteF2r1SBaveNDNyrqLooDxY94I1cSpWE6urdVsmvMk3e QGwFd+IjUKN3sYuYsNSkFLy/zBM0GGX+MiOek+xtxWApHhLvyUk23M9QuHrnpvm0acde bcz4pFFDVNsnoQcZ8papLMlTgVm6uodLwqrwwiy8gT8shAalM2WdALzxMamqVd+01Rgs igRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ZDWjtHnZKatoUmSnfm3o/zE4jIsN/mTf7ee4EH19+AA=; b=ciO4Fahc0wo1CEbnezzfP4V4B0hyvo04YCqoboufcpk9zrgl1tWvZFnzJBBDtv/454 U/58m73Hoj1wMkBI9mV+qmtBPycO9qNllYvNbJ0hzO49e9YvTVjXv8WsxdUtcaakSxEP GGGrb4fgado4MRDBbxodfEOTZM059sxl8ZRQEcsi2GMKmu2gNBOPle6zfYCPwyaMTxCm kYZZYBrsKsiM0kVLC4PtWaQJylFGrqk/9Pdc6ybjw8diUZMb8bGpT1aNu1wais9K8Mq5 S1FdaTqo6B50lte0Wod8CdW1QqEMoKERRn3RT6PBYh/p36OVmIl1dbkJiR7TAlCU45e6 FJWA==
X-Gm-Message-State: ALyK8tJiQKzME2kjPMGNlBI5ykGfuFfbVK99Mpm85DMkLDkAT56p3uzeGwLO9ZZelF/oIg==
X-Received: by 10.194.240.195 with SMTP id wc3mr1824581wjc.84.1468856586079; Mon, 18 Jul 2016 08:43:06 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r8sm1890998wjj.45.2016.07.18.08.43.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 08:43:05 -0700 (PDT)
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com> <alpine.DEB.2.02.1607181738440.2309@uplift.swm.pp.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <619cd564-7099-c032-1c49-c9111b978aa2@gmail.com>
Date: Tue, 19 Jul 2016 03:43:06 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1607181738440.2309@uplift.swm.pp.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ovMOdxtS68x4vPazj5ZcfQHsC7k>
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:47:01 -0000

On 19/07/2016 03:40, Mikael Abrahamsson wrote:
> On Tue, 19 Jul 2016, Brian E Carpenter wrote:
> 
>> Doing so for .home. would be entertaining, of course. Doing so for .homenet. seems plausible.
> 
> It seems to already be used for that, and as said before, ICANN has refused all applications for .home already.
> 
> .home is tainted by ad-hoc use. The ad-hoc use seems to be exactly the same use as RFC7788 uses it for.
> 
> Why not formalise it?

To be blunt, because ICANN and possibly the IETF would get sued for many M$.

   Brian


From nobody Mon Jul 18 08:49:24 2016
Return-Path: <wouter.cloetens@softathome.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD24012D0AF for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.069
X-Spam-Level: 
X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 dZy4f2Udvfol for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 08:49:10 -0700 (PDT)
Received: from mx20.yaziba.net (mx20.yaziba.net [85.233.204.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89A9712DAB6 for <homenet@ietf.org>; Mon, 18 Jul 2016 08:47:18 -0700 (PDT)
Received: from mta20.int.yaziba.net (mta20.int.yaziba.net [10.4.20.31]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx20.yaziba.net (mx10.yaziba.net) with ESMTPS id D07A11A78D5 for <homenet@ietf.org>; Mon, 18 Jul 2016 17:47:16 +0200 (CEST)
Received: from mta20.int.yaziba.net (localhost [127.0.0.1]) by mta20.int.yaziba.net (Postfix) with ESMTPS id DC6C5CA657 for <homenet@ietf.org>; Mon, 18 Jul 2016 17:47:16 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mta20.int.yaziba.net (Postfix) with ESMTP id CAD95CA76A for <homenet@ietf.org>; Mon, 18 Jul 2016 17:47:16 +0200 (CEST)
X-Virus-Scanned: amavisd-new at mta20.int.yaziba.net
Received: from mta20.int.yaziba.net ([127.0.0.1]) by localhost (mta20.int.yaziba.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id m_Q2HA2tEwSw for <homenet@ietf.org>; Mon, 18 Jul 2016 17:47:16 +0200 (CEST)
Received: from [31.133.163.151] (dhcp-a397.meeting.ietf.org [31.133.163.151]) by mta20.int.yaziba.net (Postfix) with ESMTPSA id 90355CA685 for <homenet@ietf.org>; Mon, 18 Jul 2016 17:47:16 +0200 (CEST)
To: homenet@ietf.org
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
From: Wouter Cloetens <wouter.cloetens@softathome.com>
Message-ID: <578CFA04.9030101@softathome.com>
Date: Mon, 18 Jul 2016 17:47:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060605040700000703050301"
X-DRWEB-SCAN: ok
X-VRSPAM-SCORE: 0
X-VRSPAM-STATE: legit
X-VRSPAM-CAUSE: gggruggvucftvghtrhhoucdtuddrfeeltddrgeelgdelfecutefuodetggdotefrucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpjgetkgfkueetnecuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtdgrrgdtfeejnecuhfhrohhmpeghohhuthgvrhcuvehlohgvthgvnhhsuceofihouhhtvghrrdgtlhhovghtvghnshesshhofhhtrghthhhomhgvrdgtohhmqeenucffohhmrghinhepghhoohhglhgvuhhsvghrtghonhhtvghnthdrtghomhdpihgtrghnnhifihhkihdrtghomhdpihgvthhfrdhorhhgnecukfhppeefuddrudeffedrudeifedrudehudenucfrrghrrghmpehmohguvgepshhmthhpohhuth
X-VRSPAM-EXTCAUSE: mhhouggvpehsmhhtphhouhht
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/DFai9bvAv3W7QnwtggHPxm83B1o>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:49:23 -0000

This is a multi-part message in MIME format.
--------------060605040700000703050301
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 18/07/16 17:01, Ted Lemon wrote:
> Yup.   In terms of minimizing risk to the IETF, switching to .homenet 
> is expedient--that's why I put it in the Homenet Naming/Service 
> Discovery Architecture doc.   Perhaps some homenet participants aren't 
> aware of the issues surrounding this.
> The reason we are getting so much top-down push from IETF leadership 
> on this is not that IETF leadership are being political--it's that 
> there's a real cost to the IETF if one of the GTLD people decides that 
> we have taken a name for which they paid an application fee.   I 
> apologize for glossing over this in my earlier response.
I'm a bit confused about this. Although Dothome Ltd. paid an application 
fee, they failed the initial evaluation. ICANN ultimately concluded in 
2013 that .home was high risk, or "dead" in the terminology used in an 
article to which ICANN links.

I can't reach this at the moment:
https://icannwiki.com/.home
So here's the Google cache:
https://webcache.googleusercontent.com/search?q=cache:OdSc1uEzj_cJ:https://icannwiki.com/.home+&cd=1&hl=en&ct=clnk&gl=de

So, why would ICANN's gTLD people not be open to declaring .home to be 
off their list, and open for redefinition by IETF?

>
> If people are interested in better understanding this problem, I 
> encourage you to read this: 
> https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3
" o IETF and ICANN independently have remit to assign names out of the 
namespace that Internet Names represent; a formal coordination process 
does not exist."

Can't that be fixed? Has anyone tried to speak to / negotiate with ICANN?
>
> You can get more background by reading section 4 as well. Bear in 
> mind, s/.local/.home/ in section 4.2.4.
>
> On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan 
> <ajs@anvilwalrusden.com <mailto:ajs@anvilwalrusden.com>> wrote:
>
>     On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
>     >
>     > .HOME has not been handed out by ICANN yet
>
>     There are several applications for home in the root zone.  To my mind,
>     that means that home has been claimed as being inside the global DNS
>     context, and therefore is not available under RFC 6761.
>
>     Best regards,
>
>     A
>


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">On 18/07/16 17:01, Ted Lemon wrote:<br=
>
    </div>
    <blockquote
cite=3D"mid:CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=3DvW0ua1xeWgdXA@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">Yup. =C2=A0 In terms of minimizing risk to the IET=
F,
        switching to .homenet is expedient--that's why I put it in the
        Homenet Naming/Service Discovery Architecture doc. =C2=A0 Perhaps
        some homenet participants aren't aware of the issues surrounding
        this. =C2=A0=C2=A0
        <div>The reason we are getting so much top-down push from IETF
          leadership on this is not that IETF leadership are being
          political--it's that there's a real cost to the IETF if one of
          the GTLD people decides that we have taken a name for which
          they paid an application fee. =C2=A0 I apologize for glossing o=
ver
          this in my earlier response.<br>
        </div>
      </div>
    </blockquote>
    I'm a bit confused about this. Although Dothome Ltd. paid an
    application fee, they failed the initial evaluation. ICANN
    ultimately concluded in 2013 that .home was high risk, or "dead" in
    the terminology used in an article to which ICANN links.<br>
    <br>
    I can't reach this at the moment:<br>
    =C2=A0<a href=3D"https://icannwiki.com/.home">https://icannwiki.com/.=
home</a><br>
    So here's the Google cache:<br>
    =C2=A0<a
href=3D"https://webcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj=
_cJ:https://icannwiki.com/.home+&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp=
;gl=3Dde"><a class=3D"moz-txt-link-freetext" href=3D"https://webcache.goo=
gleusercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https://icannwiki.com/.h=
ome+&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde">https://webcache.g=
oogleusercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https://icannwiki.com/=
.home+&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde</a></a><br>
    <br>
    So, why would ICANN's gTLD people not be open to declaring .home to
    be off their list, and open for redefinition by IETF?<br>
    <br>
    <blockquote
cite=3D"mid:CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=3DvW0ua1xeWgdXA@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <div><br>
          </div>
          <div>If people are interested in better understanding this
            problem, I encourage you to read this:=C2=A0<a
              moz-do-not-send=3D"true"
              href=3D"https://tools.ietf.org/html/draft-tldr-sutld-ps-02#=
section-3"><a class=3D"moz-txt-link-freetext" href=3D"https://tools.ietf.=
org/html/draft-tldr-sutld-ps-02#section-3">https://tools.ietf.org/html/dr=
aft-tldr-sutld-ps-02#section-3</a></a></div>
        </div>
      </div>
    </blockquote>
    " o IETF and ICANN independently have remit to assign names out of
    the namespace that Internet Names represent; a formal coordination
    process does not exist."<br>
    <br>
    Can't that be fixed? Has anyone tried to speak to / negotiate with
    ICANN?<br>
    <blockquote
cite=3D"mid:CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=3DvW0ua1xeWgdXA@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
        </div>
        <div>You can get more background by reading section 4 as well. =C2=
=A0
          Bear in mind, s/.local/.home/ in section 4.2.4.</div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:16 PM, Andre=
w
          Sullivan <span dir=3D"ltr">&lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">aj=
s@anvilwalrusden.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
              class=3D"">On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael
              Abrahamsson wrote:<br>
              &gt;<br>
              &gt; .HOME has not been handed out by ICANN yet<br>
              <br>
            </span>There are several applications for home in the root
            zone.=C2=A0 To my mind,<br>
            that means that home has been claimed as being inside the
            global DNS<br>
            context, and therefore is not available under RFC 6761.<br>
            <br>
            Best regards,<br>
            <br>
            A<br>
            <span class=3D"HOEnZb"><font color=3D"#888888"></font></span>=
</blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060605040700000703050301--


From nobody Mon Jul 18 09:03:49 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 864CA12DA2C for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:03:48 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 BoE1Z0yD4H1O for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:03:46 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0D4F12B00B for <homenet@ietf.org>; Mon, 18 Jul 2016 09:03:45 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id l69so78340381lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:03:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6wZv0rKrMkSAcqIlkRe7z+QUJYoPF5nVuX2KuA/hVlg=; b=dilF300rp4ovavLbAgMTlgeaRZ5AUpyNGPEVnwY3LIC54Mof3nuuglaDDiXEHjEjNR y7VPuNVaRp7lnNiFskU0TSFvpzfk1d/KO11jgXrgo1TD4jKc/jVrbN3SfzOeag+gX3cT elArlqPkgcJT6VcOzYTIY2F59jJKyxYSUNeN0eeFDi3uvEr0cj9B0I7eMM+uhx7XtnPk exTMXvM9FZfWWMSJAIix2NGebRL+s7FJkGFPFBslNLiDnMnTATFEJgK9C8X/1aouUoYr 4ddvWUGM3TjEwG5xBfKk/HOw8EJk2T0soxQ6jPVRwiugulLcNsWl7gTjgom+MMo6P0c2 A+eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=6wZv0rKrMkSAcqIlkRe7z+QUJYoPF5nVuX2KuA/hVlg=; b=P6Z6mYX6Vs6Do5VRaNC4SGFmtM9Tzk/PhBuybXUS2dWKJedEFOcbGHf71KplVdI88M 08cGtrPaHcDX2aIqzGMRosIUYdtuYp3NYL2a+MIZCOSpMKMuK77ed9ZvwiSrk+ID5nbX jqc8ibvToiMjY4n1hiEtYppQXWE2vaifsg41lPLA7M5l7n7Vx5O1IXDPQ+rs8dkUDQZG BLpDUjJPC2s52NxmflXEfkQ/2IRRFVYIKVFACN+P7EuL8WOsgTmm+4DuBIvszENLPR+U Q/gKionJlxVR/SMOub7RLCaVAAudHGB3xzzZDRQse75mC7Js1rP5ksOu5ZJu6ct7WXCX 1I1Q==
X-Gm-Message-State: ALyK8tJPty1JYdgHrN48X+r9EDn7LlqoFLKkh/mTMM/7K+MLm3US0yo4QEK3GBKLgp87sv0zMVDUgTBcCRjZSA==
MIME-Version: 1.0
X-Received: by 10.25.91.149 with SMTP id p143mr14231917lfb.39.1468857823853; Mon, 18 Jul 2016 09:03:43 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 09:03:43 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 09:03:43 -0700 (PDT)
In-Reply-To: <578CFA04.9030101@softathome.com>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com> <578CFA04.9030101@softathome.com>
Date: Mon, 18 Jul 2016 18:03:43 +0200
Message-ID: <CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Wouter Cloetens <wouter.cloetens@softathome.com>
Content-Type: multipart/alternative; boundary=001a114124b4d114ee0537eb1c19
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nh9t8sjUgGKxF25bdHyddNipTL8>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:03:48 -0000

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

It could be seen as collusion. Remember, lawyers are much more creative in
finding vulns than all but the most paranoid of security geeks. :)

On Jul 18, 2016 17:49, "Wouter Cloetens" <wouter.cloetens@softathome.com>
wrote:

> On 18/07/16 17:01, Ted Lemon wrote:
>
> Yup.   In terms of minimizing risk to the IETF, switching to .homenet is
> expedient--that's why I put it in the Homenet Naming/Service Discovery
> Architecture doc.   Perhaps some homenet participants aren't aware of the
> issues surrounding this.
> The reason we are getting so much top-down push from IETF leadership on
> this is not that IETF leadership are being political--it's that there's a
> real cost to the IETF if one of the GTLD people decides that we have taken
> a name for which they paid an application fee.   I apologize for glossing
> over this in my earlier response.
>
> I'm a bit confused about this. Although Dothome Ltd. paid an application
> fee, they failed the initial evaluation. ICANN ultimately concluded in 2013
> that .home was high risk, or "dead" in the terminology used in an article
> to which ICANN links.
>
> I can't reach this at the moment:
>  https://icannwiki.com/.home
> So here's the Google cache:
>
> https://webcache.googleusercontent.com/search?q=cache:OdSc1uEzj_cJ:https://icannwiki.com/.home+&cd=1&hl=en&ct=clnk&gl=de
>
> So, why would ICANN's gTLD people not be open to declaring .home to be off
> their list, and open for redefinition by IETF?
>
>
> If people are interested in better understanding this problem, I encourage
> you to read this:
> https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3
>
> " o IETF and ICANN independently have remit to assign names out of the
> namespace that Internet Names represent; a formal coordination process does
> not exist."
>
> Can't that be fixed? Has anyone tried to speak to / negotiate with ICANN?
>
>
> You can get more background by reading section 4 as well.   Bear in mind,
> s/.local/.home/ in section 4.2.4.
>
> On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
>
>> On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
>> >
>> > .HOME has not been handed out by ICANN yet
>>
>> There are several applications for home in the root zone.  To my mind,
>> that means that home has been claimed as being inside the global DNS
>> context, and therefore is not available under RFC 6761.
>>
>> Best regards,
>>
>> A
>>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<p dir=3D"ltr">It could be seen as collusion. Remember, lawyers are much mo=
re creative in finding vulns than all but the most paranoid of security gee=
ks. :)</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 18, 2016 1=
7:49, &quot;Wouter Cloetens&quot; &lt;<a href=3D"mailto:wouter.cloetens@sof=
tathome.com">wouter.cloetens@softathome.com</a>&gt; wrote:<br type=3D"attri=
bution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div>On 18/07/16 17:01, Ted Lemon wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Yup. =C2=A0 In terms of minimizing risk to the IETF,
        switching to .homenet is expedient--that&#39;s why I put it in the
        Homenet Naming/Service Discovery Architecture doc. =C2=A0 Perhaps
        some homenet participants aren&#39;t aware of the issues surroundin=
g
        this. =C2=A0=C2=A0
        <div>The reason we are getting so much top-down push from IETF
          leadership on this is not that IETF leadership are being
          political--it&#39;s that there&#39;s a real cost to the IETF if o=
ne of
          the GTLD people decides that we have taken a name for which
          they paid an application fee. =C2=A0 I apologize for glossing ove=
r
          this in my earlier response.<br>
        </div>
      </div>
    </blockquote>
    I&#39;m a bit confused about this. Although Dothome Ltd. paid an
    application fee, they failed the initial evaluation. ICANN
    ultimately concluded in 2013 that .home was high risk, or &quot;dead&qu=
ot; in
    the terminology used in an article to which ICANN links.<br>
    <br>
    I can&#39;t reach this at the moment:<br>
    =C2=A0<a href=3D"https://icannwiki.com/.home" target=3D"_blank">https:/=
/icannwiki.com/.home</a><br>
    So here&#39;s the Google cache:<br>
    =C2=A0<a href=3D"https://webcache.googleusercontent.com/search?q=3Dcach=
e:OdSc1uEzj_cJ:https://icannwiki.com/.home+&amp;cd=3D1&amp;hl=3Den&amp;ct=
=3Dclnk&amp;gl=3Dde" target=3D"_blank"><a href=3D"https://webcache.googleus=
ercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https://icannwiki.com/.home+&am=
p;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde" target=3D"_blank">https://w=
ebcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https://icannwi=
ki.com/.home+&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde</a></a><br>
    <br>
    So, why would ICANN&#39;s gTLD people not be open to declaring .home to
    be off their list, and open for redefinition by IETF?<br>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <div><br>
          </div>
          <div>If people are interested in better understanding this
            problem, I encourage you to read this:=C2=A0<a href=3D"https://=
tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3" target=3D"_blank"><a =
href=3D"https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3" targe=
t=3D"_blank">https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3</=
a></a></div>
        </div>
      </div>
    </blockquote>
    &quot; o IETF and ICANN independently have remit to assign names out of
    the namespace that Internet Names represent; a formal coordination
    process does not exist.&quot;<br>
    <br>
    Can&#39;t that be fixed? Has anyone tried to speak to / negotiate with
    ICANN?<br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div><br>
        </div>
        <div>You can get more background by reading section 4 as well. =C2=
=A0
          Bear in mind, s/.local/.home/ in section 4.2.4.</div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:16 PM, Andrew
          Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusd=
en.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><span>On Mon, Jul 18, 2016 at 03:3=
3:28PM +0200, Mikael
              Abrahamsson wrote:<br>
              &gt;<br>
              &gt; .HOME has not been handed out by ICANN yet<br>
              <br>
            </span>There are several applications for home in the root
            zone.=C2=A0 To my mind,<br>
            that means that home has been claimed as being inside the
            global DNS<br>
            context, and therefore is not available under RFC 6761.<br>
            <br>
            Best regards,<br>
            <br>
            A<br>
            <span><font color=3D"#888888"></font></span></blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </div>

<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
<br></blockquote></div></div>

--001a114124b4d114ee0537eb1c19--


From nobody Mon Jul 18 09:15:05 2016
Return-Path: <wouter.cloetens@softathome.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D809312B060 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 7AXiXaV97p1a for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:15:01 -0700 (PDT)
Received: from mx20.yaziba.net (mx20.yaziba.net [85.233.204.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AA4712D12D for <homenet@ietf.org>; Mon, 18 Jul 2016 09:14:59 -0700 (PDT)
Received: from mta20.int.yaziba.net (mta20.int.yaziba.net [10.4.20.31]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx20.yaziba.net (mx10.yaziba.net) with ESMTPS id E57831A78AE for <homenet@ietf.org>; Mon, 18 Jul 2016 18:14:57 +0200 (CEST)
Received: from mta20.int.yaziba.net (localhost [127.0.0.1]) by mta20.int.yaziba.net (Postfix) with ESMTPS id 09932CA657 for <homenet@ietf.org>; Mon, 18 Jul 2016 18:14:58 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mta20.int.yaziba.net (Postfix) with ESMTP id E60B1CA76B for <homenet@ietf.org>; Mon, 18 Jul 2016 18:14:57 +0200 (CEST)
X-Virus-Scanned: amavisd-new at mta20.int.yaziba.net
Received: from mta20.int.yaziba.net ([127.0.0.1]) by localhost (mta20.int.yaziba.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kuorzCGOhu7A for <homenet@ietf.org>; Mon, 18 Jul 2016 18:14:57 +0200 (CEST)
Received: from [31.133.163.151] (dhcp-a397.meeting.ietf.org [31.133.163.151]) by mta20.int.yaziba.net (Postfix) with ESMTPSA id AF797CA657 for <homenet@ietf.org>; Mon, 18 Jul 2016 18:14:57 +0200 (CEST)
To: HOMENET <homenet@ietf.org>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com> <578CFA04.9030101@softathome.com> <CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmail.com>
From: Wouter Cloetens <wouter.cloetens@softathome.com>
Message-ID: <578D0080.7020708@softathome.com>
Date: Mon, 18 Jul 2016 18:14:56 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040201080809060704000204"
X-DRWEB-SCAN: ok
X-VRSPAM-SCORE: 0
X-VRSPAM-STATE: legit
X-VRSPAM-CAUSE: gggruggvucftvghtrhhoucdtuddrfeeltddrgeelgdellecutefuodetggdotefrucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpjgetkgfkueetnecuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtdgrrgdtfeejnecuhfhrohhmpeghohhuthgvrhcuvehlohgvthgvnhhsuceofihouhhtvghrrdgtlhhovghtvghnshesshhofhhtrghthhhomhgvrdgtohhmqeenucffohhmrghinheplhhinhhkvgguihhnrdgtohhmpdhgohhoghhlvghushgvrhgtohhnthgvnhhtrdgtohhmpdhitggrnhhnfihikhhirdgtohhmpdhivghtfhdrohhrghdpshhofhhtrghthhhomhgvrdgtohhmnecukfhppeefuddrudeffedrudeifedrudehudenucfrrghrrghmpehmohguvgepshhmthhpohhuth
X-VRSPAM-EXTCAUSE: mhhouggvpehsmhhtphhouhht
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/X1adfUMEV0lP2HV4297sohVdDL4>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:15:04 -0000

This is a multi-part message in MIME format.
--------------040201080809060704000204
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Am I to interpret that response as a "no" to the question whether anyone=20
has spoken to ICANN? Which would mean that the rejection of .home is=20
based on an assumption?

bfn, Wouter

On 18/07/16 18:03, Ted Lemon wrote:
>
> It could be seen as collusion. Remember, lawyers are much more=20
> creative in finding vulns than all but the most paranoid of security=20
> geeks. :)
>
>
> On Jul 18, 2016 17:49, "Wouter Cloetens"=20
> <wouter.cloetens@softathome.com=20
> <mailto:wouter.cloetens@softathome.com>> wrote:
>
>     On 18/07/16 17:01, Ted Lemon wrote:
>>     Yup.   In terms of minimizing risk to the IETF, switching to
>>     .homenet is expedient--that's why I put it in the Homenet
>>     Naming/Service Discovery Architecture doc.   Perhaps some homenet
>>     participants aren't aware of the issues surrounding this.
>>     The reason we are getting so much top-down push from IETF
>>     leadership on this is not that IETF leadership are being
>>     political--it's that there's a real cost to the IETF if one of
>>     the GTLD people decides that we have taken a name for which they
>>     paid an application fee.   I apologize for glossing over this in
>>     my earlier response.
>     I'm a bit confused about this. Although Dothome Ltd. paid an
>     application fee, they failed the initial evaluation. ICANN
>     ultimately concluded in 2013 that .home was high risk, or "dead"
>     in the terminology used in an article to which ICANN links.
>
>     I can't reach this at the moment:
>     https://icannwiki.com/.home
>     So here's the Google cache:
>     https://webcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj_c=
J:https://icannwiki.com/.home+&cd=3D1&hl=3Den&ct=3Dclnk&gl=3Dde
>
>     So, why would ICANN's gTLD people not be open to declaring .home
>     to be off their list, and open for redefinition by IETF?
>
>>
>>     If people are interested in better understanding this problem, I
>>     encourage you to read this:
>>     https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3
>     " o IETF and ICANN independently have remit to assign names out of
>     the namespace that Internet Names represent; a formal coordination
>     process does not exist."
>
>     Can't that be fixed? Has anyone tried to speak to / negotiate with
>     ICANN?
>>
>>     You can get more background by reading section 4 as well.   Bear
>>     in mind, s/.local/.home/ in section 4.2.4.
>>
>>     On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan
>>     <ajs@anvilwalrusden.com <mailto:ajs@anvilwalrusden.com>> wrote:
>>
>>         On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson
>>         wrote:
>>         >
>>         > .HOME has not been handed out by ICANN yet
>>
>>         There are several applications for home in the root zone.  To
>>         my mind,
>>         that means that home has been claimed as being inside the
>>         global DNS
>>         context, and therefore is not available under RFC 6761.
>>
>>         Best regards,
>>
>>         A
>>
>
>
>     _______________________________________________
>     homenet mailing list
>     homenet@ietf.org <mailto:homenet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/homenet
>


--=20
Chief Home Gateway Architect     SoftAtHome  http://www.softathome.com/
https://www.linkedin.com/in/wcloetens Vaartdijk 3/B701, B-3018 Wijgmaal
Tel: +32-16-852010  Mobile: +32-492-277790   Conf. phone: +32-16-852097

This message and any attachments are confidential, intended solely for
the addressees and are SoftAtHome=E2=80=99s ownership.
Any unauthorized use or dissemination is prohibited. If you are not the
intended addressee of this message, please cancel it immediately and
inform the sender.


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">Am I to interpret that response as a
      "no" to the question whether anyone has spoken to ICANN? Which
      would mean that the rejection of .home is based on an assumption?<b=
r>
      <br>
      bfn, Wouter<br>
      <br>
      On 18/07/16 18:03, Ted Lemon wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmai=
l.com"
      type=3D"cite">
      <p dir=3D"ltr">It could be seen as collusion. Remember, lawyers are
        much more creative in finding vulns than all but the most
        paranoid of security geeks. :)</p>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Jul 18, 2016 17:49, "Wouter
          Cloetens" &lt;<a moz-do-not-send=3D"true"
            href=3D"mailto:wouter.cloetens@softathome.com">wouter.cloeten=
s@softathome.com</a>&gt;
          wrote:<br type=3D"attribution">
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text=3D"#000000" bgcolor=3D"#FFFFFF">
              <div>On 18/07/16 17:01, Ted Lemon wrote:<br>
              </div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">Yup. =C2=A0 In terms of minimizing risk =
to the
                  IETF, switching to .homenet is expedient--that's why I
                  put it in the Homenet Naming/Service Discovery
                  Architecture doc. =C2=A0 Perhaps some homenet participa=
nts
                  aren't aware of the issues surrounding this. =C2=A0=C2=A0
                  <div>The reason we are getting so much top-down push
                    from IETF leadership on this is not that IETF
                    leadership are being political--it's that there's a
                    real cost to the IETF if one of the GTLD people
                    decides that we have taken a name for which they
                    paid an application fee. =C2=A0 I apologize for gloss=
ing
                    over this in my earlier response.<br>
                  </div>
                </div>
              </blockquote>
              I'm a bit confused about this. Although Dothome Ltd. paid
              an application fee, they failed the initial evaluation.
              ICANN ultimately concluded in 2013 that .home was high
              risk, or "dead" in the terminology used in an article to
              which ICANN links.<br>
              <br>
              I can't reach this at the moment:<br>
              =C2=A0<a moz-do-not-send=3D"true"
                href=3D"https://icannwiki.com/.home" target=3D"_blank">ht=
tps://icannwiki.com/.home</a><br>
              So here's the Google cache:<br>
              =C2=A0<a moz-do-not-send=3D"true"
href=3D"https://webcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj=
_cJ:https://icannwiki.com/.home+&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp=
;gl=3Dde"
                target=3D"_blank">https://webcache.googleusercontent.com/=
search?q=3Dcache:OdSc1uEzj_cJ:https://icannwiki.com/.home+&amp;cd=3D1&amp=
;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde</a><br>
              <br>
              So, why would ICANN's gTLD people not be open to declaring
              .home to be off their list, and open for redefinition by
              IETF?<br>
              <br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div>
                    <div><br>
                    </div>
                    <div>If people are interested in better
                      understanding this problem, I encourage you to
                      read this:=C2=A0<a moz-do-not-send=3D"true"
                        href=3D"https://tools.ietf.org/html/draft-tldr-su=
tld-ps-02#section-3"
                        target=3D"_blank">https://tools.ietf.org/html/dra=
ft-tldr-sutld-ps-02#section-3</a></div>
                  </div>
                </div>
              </blockquote>
              " o IETF and ICANN independently have remit to assign
              names out of the namespace that Internet Names represent;
              a formal coordination process does not exist."<br>
              <br>
              Can't that be fixed? Has anyone tried to speak to /
              negotiate with ICANN?<br>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div><br>
                  </div>
                  <div>You can get more background by reading section 4
                    as well. =C2=A0 Bear in mind, s/.local/.home/ in sect=
ion
                    4.2.4.</div>
                </div>
                <div class=3D"gmail_extra"><br>
                  <div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:16
                    PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a
                        moz-do-not-send=3D"true"
                        href=3D"mailto:ajs@anvilwalrusden.com"
                        target=3D"_blank"><a class=3D"moz-txt-link-abbrev=
iated" href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><=
/a>&gt;</span>
                    wrote:<br>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
span>On
                        Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael
                        Abrahamsson wrote:<br>
                        &gt;<br>
                        &gt; .HOME has not been handed out by ICANN yet<b=
r>
                        <br>
                      </span>There are several applications for home in
                      the root zone.=C2=A0 To my mind,<br>
                      that means that home has been claimed as being
                      inside the global DNS<br>
                      context, and therefore is not available under RFC
                      6761.<br>
                      <br>
                      Best regards,<br>
                      <br>
                      A<br>
                      <span></span></blockquote>
                  </div>
                </div>
              </blockquote>
              <br>
            </div>
            <br>
            _______________________________________________<br>
            homenet mailing list<br>
            <a moz-do-not-send=3D"true" href=3D"mailto:homenet@ietf.org">=
homenet@ietf.org</a><br>
            <a moz-do-not-send=3D"true"
              href=3D"https://www.ietf.org/mailman/listinfo/homenet"
              rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/homenet</a><br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Chief Home Gateway Architect     SoftAtHome  <a class=3D"moz-txt-link-fre=
etext" href=3D"http://www.softathome.com/">http://www.softathome.com/</a>=
=20
<a class=3D"moz-txt-link-freetext" href=3D"https://www.linkedin.com/in/wc=
loetens">https://www.linkedin.com/in/wcloetens</a> Vaartdijk 3/B701, B-30=
18 Wijgmaal
Tel: +32-16-852010  Mobile: +32-492-277790   Conf. phone: +32-16-852097

This message and any attachments are confidential, intended solely for
the addressees and are SoftAtHome=E2=80=99s ownership.
Any unauthorized use or dissemination is prohibited. If you are not the
intended addressee of this message, please cancel it immediately and
inform the sender.
</pre>
  </body>
</html>

--------------040201080809060704000204--


From nobody Mon Jul 18 09:41:01 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB3312D193 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:40:59 -0700 (PDT)
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 autolearn_force=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 eFDcFKb23PXO for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:40:58 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 13BEB12B010 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:40:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id B2BE010D2A for <homenet@ietf.org>; Mon, 18 Jul 2016 16:40:57 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deVNI5TUzFTf for <homenet@ietf.org>; Mon, 18 Jul 2016 16:40:57 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-b2a2.meeting.ietf.org [31.133.178.162]) by mx2.yitter.info (Postfix) with ESMTPSA id E501610BCD for <homenet@ietf.org>; Mon, 18 Jul 2016 16:40:56 +0000 (UTC)
Date: Mon, 18 Jul 2016 12:40:54 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160718164054.GA44253@mx2.yitter.info>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Alvnh3B5FQsXgJ_gslF-tdiVnrc>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:40:59 -0000

On Tue, Jul 19, 2016 at 03:22:57AM +1200, Brian E Carpenter wrote:
> I don't get that. There's nothing about that in RFC 6761, which is mainly
> very boring stuff that could be written up for this case, regardless
> of the actual domain name. It's our own self-imposed bureaucracy.

Question 7 asks how registries and registrars should react to this
name.  Given that the home TLD is in-process in the ICANN delegation
procedures from the root zone, it is logically possible that at any
moment ICANN could change its administrative procedures and home would
get delegated.

So the answer to question 7 cannot be but ambiguous under these
circumstances.  To me, that means that the requirements of 6761 can't
possibly be met by home, and therefore home can't be allocated under
special use.

This is the point that Jari made and that I was going to make at the
mic: this isn't a mere political problem, but an actual functional one
under our own procedures.  There is just no way we could allocate home
under 6761 right now, without a very strong statement from ICANN that
it would be ok.

I also argue (see my note from yesterday) that generalizing from
"people seem to be doing somehting like this with this name, because I
talked to a guy from $vendor and he said so" to "using this as a
protocol switch in a protocol will not have a problem" seems to me to
require a pretty big leap.

> RFC 6761 is one thing, but RFC 2860 is another. Under note (a)
> to clause 4.3 of that MoU, the IETF can direct IANA to reserve
> .$WHATEVER$. for technical use.

I strongly agree -- that part is the very reason why 6761 was even
possible, in my opinion.
 
> Doing so for .home. would be entertaining, of course. Doing so
> for .homenet. seems plausible.

I know it can be entertainment to watch those films where someone
foolishly got into a car that was then swept over Niagara Falls.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 18 09:43:18 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C391812D0DE for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:43:16 -0700 (PDT)
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 autolearn_force=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 9TpvJeT3hDge for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:43:15 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBBF12B010 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:43:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 50F1610D2A for <homenet@ietf.org>; Mon, 18 Jul 2016 16:43:15 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcdgX8SjB1lR for <homenet@ietf.org>; Mon, 18 Jul 2016 16:43:13 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-b2a2.meeting.ietf.org [31.133.178.162]) by mx2.yitter.info (Postfix) with ESMTPSA id 5CDD110BCD for <homenet@ietf.org>; Mon, 18 Jul 2016 16:43:13 +0000 (UTC)
Date: Mon, 18 Jul 2016 12:43:11 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160718164310.GB44253@mx2.yitter.info>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com> <alpine.DEB.2.02.1607181738440.2309@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1607181738440.2309@uplift.swm.pp.se>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Bp9qF85odTeRKOH3bBXv9EBYml0>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:43:17 -0000

On Mon, Jul 18, 2016 at 05:40:01PM +0200, Mikael Abrahamsson wrote:
> It seems to already be used for that, and as said before, ICANN has refused
> all applications for .home already.

No, it has not.  If it had, it would have refunded all those
applicants' money and so on.  It has not formally decided anything as
a permanent matter.

> .home is tainted by ad-hoc use. The ad-hoc use seems to be exactly the same
> use as RFC7788 uses it for.

How exactly do you determine this "exactly the same" use among a large
swathe of unknown people all over the Internet?  

Best regards,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 18 09:45:40 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E50BE12D0BA for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:45:39 -0700 (PDT)
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 autolearn_force=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 rA1yK8GJN4nw for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:45:38 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 4108512D0C4 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:45:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 02F8710D28 for <homenet@ietf.org>; Mon, 18 Jul 2016 16:45:38 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tlt0pNe3VE8G for <homenet@ietf.org>; Mon, 18 Jul 2016 16:45:37 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-b2a2.meeting.ietf.org [31.133.178.162]) by mx2.yitter.info (Postfix) with ESMTPSA id 3ACF610BCD for <homenet@ietf.org>; Mon, 18 Jul 2016 16:45:37 +0000 (UTC)
Date: Mon, 18 Jul 2016 12:45:35 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160718164534.GC44253@mx2.yitter.info>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com> <578CFA04.9030101@softathome.com> <CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmail.com> <578D0080.7020708@softathome.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <578D0080.7020708@softathome.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MTlN15oOeJKTa5xoOMuuxz0GE40>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:45:40 -0000

On Mon, Jul 18, 2016 at 06:14:56PM +0200, Wouter Cloetens wrote:
> Am I to interpret that response as a "no" to the question whether anyone has
> spoken to ICANN?

You may interpret it as you wish, but it's worth noting that the IETF
has a liaison to the ICANN board.

Nevertheless, as I said upthread, this is not merely a political problem.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 18 09:49:07 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A35012DAFD for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 YMCWqIPuxaSG for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:49:03 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD04312D9F7 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:49:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LdS8ae9t5aIcaocVn6KTQnhxPk/8YmT2eIrv2kWWr4k=; b=X2O20VTWmFEbYx3ZW3L8FNWsedvITQnZPgg7IHl1fuMBGYn0icrYv3JhlW1JYOgaYOKOX7jGtCiNUYxH9MY3YWEnyagPndDC+afXON41f8H+NcM2XTpEJt3mEsJ8HkpPlx9636ZVrBdnbUc3zaygVYIgL8r9hzX8CljPbo12IkY=
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0214.outbound.protection.outlook.com [213.199.154.214]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-13-Fil3Wn6mP5yHknfCZEWRGQ-1; Mon, 18 Jul 2016 17:48:56 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) with Microsoft SMTP Server (TLS) id 15.1.539.14; Mon, 18 Jul 2016 16:48:53 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.019; Mon, 18 Jul 2016 16:48:53 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Wouter Cloetens <wouter.cloetens@softathome.com>
Thread-Topic: [homenet] RFC 7788 and ".home"
Thread-Index: AQHR4PymvDPjF4js+UuI51F7RqZsnKAePAiAgAAMmQCAAAy2AIAABJmAgAADIgCAAAnLgA==
Date: Mon, 18 Jul 2016 16:48:53 +0000
Message-ID: <A246A6C9-8AF7-4E33-86D0-6FD3374AE4A1@jisc.ac.uk>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com> <578CFA04.9030101@softathome.com> <CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w@mail.gmail.com> <578D0080.7020708@softathome.com>
In-Reply-To: <578D0080.7020708@softathome.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:152:7c81:1522:50da:c10]
x-ms-office365-filtering-correlation-id: 3a178921-9631-48ad-7fae-08d3af2b66df
x-microsoft-exchange-diagnostics: 1; AMSPR07MB455; 20:rrEuT9nKBgfSewwfhfuICo/keBNd3yJlqTCz+wImYbqNMvbTDLknaUuilR0HQx5cM2fHHAg2DwyIJYoIlY0V8B7D53jwJRuCHrfsyYrCAVv4Y3ARs9Czo9y5sEgx4sWvPSyf3b2uL6lNXX1V1DeaOqxSowA6FJQ0Z2shftsjwhw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB455;
x-microsoft-antispam-prvs: <AMSPR07MB455F4247E96A5F7C65D86BAD6360@AMSPR07MB455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(192374486261705)(128460861657000)(179696456005106)(81160342030619)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB455; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB455; 
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(24454002)(199003)(189002)(377454003)(87936001)(57306001)(122556002)(15975445007)(82746002)(36756003)(77096005)(83716003)(2900100001)(2950100001)(110136002)(97736004)(189998001)(93886004)(3660700001)(4326007)(102836003)(6116002)(586003)(86362001)(2906002)(74482002)(33656002)(3280700002)(11100500001)(19617315012)(101416001)(50986999)(16236675004)(10400500002)(8936002)(76176999)(7906003)(50226002)(7736002)(7846002)(81166006)(81156014)(68736007)(106356001)(8676002)(92566002)(5890100001)(19580395003)(19580405001)(106116001)(5002640100001)(105586002)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB455; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2016 16:48:53.2068 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB455
X-MC-Unique: Fil3Wn6mP5yHknfCZEWRGQ-1
Content-Type: multipart/alternative; boundary="_000_A246A6C98AF74E3386D06FD3374AE4A1jiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/q7PEmOwAoF5ZUFGGGCj_xYGDxng>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:49:06 -0000

--_000_A246A6C98AF74E3386D06FD3374AE4A1jiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Hi,

On 18 Jul 2016, at 17:14, Wouter Cloetens <wouter.cloetens@softathome.com<m=
ailto:wouter.cloetens@softathome.com>> wrote:

Am I to interpret that response as a "no" to the question whether anyone ha=
s spoken to ICANN? Which would mean that the rejection of .home is based on=
 an assumption?

There was an ICANN person present in a meeting as far back as IETF88 willin=
g to talk about this specific case.

Tim


bfn, Wouter

On 18/07/16 18:03, Ted Lemon wrote:

It could be seen as collusion. Remember, lawyers are much more creative in =
finding vulns than all but the most paranoid of security geeks. :)

On Jul 18, 2016 17:49, "Wouter Cloetens" <wouter.cloetens@softathome.com<ma=
ilto:wouter.cloetens@softathome.com>> wrote:
On 18/07/16 17:01, Ted Lemon wrote:
Yup.   In terms of minimizing risk to the IETF, switching to .homenet is ex=
pedient--that's why I put it in the Homenet Naming/Service Discovery Archit=
ecture doc.   Perhaps some homenet participants aren't aware of the issues =
surrounding this.
The reason we are getting so much top-down push from IETF leadership on thi=
s is not that IETF leadership are being political--it's that there's a real=
 cost to the IETF if one of the GTLD people decides that we have taken a na=
me for which they paid an application fee.   I apologize for glossing over =
this in my earlier response.
I'm a bit confused about this. Although Dothome Ltd. paid an application fe=
e, they failed the initial evaluation. ICANN ultimately concluded in 2013 t=
hat .home was high risk, or "dead" in the terminology used in an article to=
 which ICANN links.

I can't reach this at the moment:
 https://icannwiki.com/.home
So here's the Google cache:
 https://webcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https=
://icannwiki.com/.home+&cd=3D1&hl=3Den&ct=3Dclnk&gl=3Dde

So, why would ICANN's gTLD people not be open to declaring .home to be off =
their list, and open for redefinition by IETF?


If people are interested in better understanding this problem, I encourage =
you to read this: https://tools.ietf.org/html/draft-tldr-sutld-ps-02#sectio=
n-3
" o IETF and ICANN independently have remit to assign names out of the name=
space that Internet Names represent; a formal coordination process does not=
 exist."

Can't that be fixed? Has anyone tried to speak to / negotiate with ICANN?

You can get more background by reading section 4 as well.   Bear in mind, s=
/.local/.home/ in section 4.2.4.

On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan <<mailto:ajs@anvilwalrusde=
n.com>ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>> wrote:
On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:
>
> .HOME has not been handed out by ICANN yet

There are several applications for home in the root zone.  To my mind,
that means that home has been claimed as being inside the global DNS
context, and therefore is not available under RFC 6761.

Best regards,

A


_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet




--
Chief Home Gateway Architect     SoftAtHome  http://www.softathome.com/
https://www.linkedin.com/in/wcloetens Vaartdijk 3/B701, B-3018 Wijgmaal
Tel: +32-16-852010  Mobile: +32-492-277790   Conf. phone: +32-16-852097

This message and any attachments are confidential, intended solely for
the addressees and are SoftAtHome=92s ownership.
Any unauthorized use or dissemination is prohibited. If you are not the
intended addressee of this message, please cancel it immediately and
inform the sender.


_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet


--_000_A246A6C98AF74E3386D06FD3374AE4A1jiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <70EACFAF91FD0D4EB0AD373764B722F8@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
<div class=3D"">Hi,</div>
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 18 Jul 2016, at 17:14, Wouter Cloetens &lt;<a href=3D"ma=
ilto:wouter.cloetens@softathome.com" class=3D"">wouter.cloetens@softathome.=
com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
<div class=3D"moz-cite-prefix">Am I to interpret that response as a &quot;n=
o&quot; to the question whether anyone has spoken to ICANN? Which would mea=
n that the rejection of .home is based on an assumption?<br class=3D"">
</div>
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
There was an ICANN person present in a meeting as far back as IETF88 willin=
g to talk about this specific case.</div>
<div><br class=3D"">
</div>
<div>Tim</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
<div class=3D"moz-cite-prefix"><br class=3D"">
bfn, Wouter<br class=3D"">
<br class=3D"">
On 18/07/16 18:03, Ted Lemon wrote:<br class=3D"">
</div>
<blockquote cite=3D"mid:CAPt1N1no3AXSHyWa8JE-fj8gwJhm09CdusFFvenRPAWzvcaJ1w=
@mail.gmail.com" type=3D"cite" class=3D"">
<p dir=3D"ltr" class=3D"">It could be seen as collusion. Remember, lawyers =
are much more creative in finding vulns than all but the most paranoid of s=
ecurity geeks. :)</p>
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Jul 18, 2016 17:49, &quot;Wouter Cloetens&quo=
t; &lt;<a moz-do-not-send=3D"true" href=3D"mailto:wouter.cloetens@softathom=
e.com" class=3D"">wouter.cloetens@softathome.com</a>&gt; wrote:<br type=3D"=
attribution" class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
<div class=3D"">On 18/07/16 17:01, Ted Lemon wrote:<br class=3D"">
</div>
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">Yup. &nbsp; In terms of minimizing risk to the =
IETF, switching to .homenet is expedient--that's why I put it in the Homene=
t Naming/Service Discovery Architecture doc. &nbsp; Perhaps some homenet pa=
rticipants aren't aware of the issues surrounding
 this. &nbsp;&nbsp;
<div class=3D"">The reason we are getting so much top-down push from IETF l=
eadership on this is not that IETF leadership are being political--it's tha=
t there's a real cost to the IETF if one of the GTLD people decides that we=
 have taken a name for which they
 paid an application fee. &nbsp; I apologize for glossing over this in my e=
arlier response.<br class=3D"">
</div>
</div>
</blockquote>
I'm a bit confused about this. Although Dothome Ltd. paid an application fe=
e, they failed the initial evaluation. ICANN ultimately concluded in 2013 t=
hat .home was high risk, or &quot;dead&quot; in the terminology used in an =
article to which ICANN links.<br class=3D"">
<br class=3D"">
I can't reach this at the moment:<br class=3D"">
&nbsp;<a moz-do-not-send=3D"true" href=3D"https://icannwiki.com/.home" targ=
et=3D"_blank" class=3D"">https://icannwiki.com/.home</a><br class=3D"">
So here's the Google cache:<br class=3D"">
&nbsp;<a moz-do-not-send=3D"true" href=3D"https://webcache.googleuserconten=
t.com/search?q=3Dcache:OdSc1uEzj_cJ:https://icannwiki.com/.home&#43;&amp;cd=
=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde" target=3D"_blank" class=3D"">ht=
tps://webcache.googleusercontent.com/search?q=3Dcache:OdSc1uEzj_cJ:https://=
icannwiki.com/.home&#43;&amp;cd=3D1&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dde</=
a><br class=3D"">
<br class=3D"">
So, why would ICANN's gTLD people not be open to declaring .home to be off =
their list, and open for redefinition by IETF?<br class=3D"">
<br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D"">If people are interested in better understanding this probl=
em, I encourage you to read this:&nbsp;<a moz-do-not-send=3D"true" href=3D"=
https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3" target=3D"_bl=
ank" class=3D"">https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-=
3</a></div>
</div>
</div>
</blockquote>
&quot; o IETF and ICANN independently have remit to assign names out of the=
 namespace that Internet Names represent; a formal coordination process doe=
s not exist.&quot;<br class=3D"">
<br class=3D"">
Can't that be fixed? Has anyone tried to speak to / negotiate with ICANN?<b=
r class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D"">You can get more background by reading section 4 as well. &=
nbsp; Bear in mind, s/.local/.home/ in section 4.2.4.</div>
</div>
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan=
 <span dir=3D"ltr" class=3D"">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:ajs@anvilwalrusden.com" targ=
et=3D"_blank" class=3D""></a><a class=3D"moz-txt-link-abbreviated" href=3D"=
mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>&gt;</span> wrote:=
<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"">On Mon, Jul 18, 2016 at 03:33:28PM &#43;0200, Mikael Abrah=
amsson wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; .HOME has not been handed out by ICANN yet<br class=3D"">
<br class=3D"">
</span>There are several applications for home in the root zone.&nbsp; To m=
y mind,<br class=3D"">
that means that home has been claimed as being inside the global DNS<br cla=
ss=3D"">
context, and therefore is not available under RFC 6761.<br class=3D"">
<br class=3D"">
Best regards,<br class=3D"">
<br class=3D"">
A<br class=3D"">
<span class=3D""></span></blockquote>
</div>
</div>
</blockquote>
<br class=3D"">
</div>
<br class=3D"">
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a moz-do-not-send=3D"true" href=3D"mailto:homenet@ietf.org" class=3D"">hom=
enet@ietf.org</a><br class=3D"">
<a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listinfo/h=
omenet" rel=3D"noreferrer" target=3D"_blank" class=3D"">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br class=3D"">
<br class=3D"">
</blockquote>
</div>
</div>
</blockquote>
<br class=3D"">
<br class=3D"">
<pre class=3D"moz-signature" cols=3D"72">--=20
Chief Home Gateway Architect     SoftAtHome  <a class=3D"moz-txt-link-freet=
ext" href=3D"http://www.softathome.com/">http://www.softathome.com/</a>=20
<a class=3D"moz-txt-link-freetext" href=3D"https://www.linkedin.com/in/wclo=
etens">https://www.linkedin.com/in/wcloetens</a> Vaartdijk 3/B701, B-3018 W=
ijgmaal
Tel: &#43;32-16-852010  Mobile: &#43;32-492-277790   Conf. phone: &#43;32-1=
6-852097

This message and any attachments are confidential, intended solely for
the addressees and are SoftAtHome=92s ownership.
Any unauthorized use or dissemination is prohibited. If you are not the
intended addressee of this message, please cancel it immediately and
inform the sender.
</pre>
</div>
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br clas=
s=3D"">
https://www.ietf.org/mailman/listinfo/homenet<br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_A246A6C98AF74E3386D06FD3374AE4A1jiscacuk_--


From nobody Mon Jul 18 09:53:43 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F3C12D0DD for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=jisc365.onmicrosoft.com
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 RWjgtNnXfAw4 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 09:53:38 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E02C012D0B0 for <homenet@ietf.org>; Mon, 18 Jul 2016 09:53:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=F8V96bRz5pD6ni/XyiQgSB8G6pcHgrMZxN4m6tV1ZT0=; b=deeOGf0Un6ZBI9Zt9sG2z4NpgpBJIQwp1JSziceH0n6cfn43cru0a6Jn1veS1bEv/i3vNrriRQRuVFW6Lpo9+tTdcjjfXV+s171CyYJ/0imILKqj/Jf91tsmRWvFwvRUoulzF9aQ8uTWd/+6a/1Gll6O7bNrlKyCbPHHl1hYCJ8=
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-db5eur03lp0081.outbound.protection.outlook.com [94.245.120.81]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-36-_ax8D5jnOXasQzXH2Fqu7A-1; Mon, 18 Jul 2016 17:53:31 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (TLS) id 15.1.534.14; Mon, 18 Jul 2016 16:53:31 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.019; Mon, 18 Jul 2016 16:53:31 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Thread-Topic: [homenet] use of .home
Thread-Index: AQHR4PtWlvXz5L/R3USrs+fq1WXvz6AeQNKAgAAnWYA=
Date: Mon, 18 Jul 2016 16:53:30 +0000
Message-ID: <2CFE58DD-39C0-4F38-8DD4-34C1BE12AE71@jisc.ac.uk>
References: <3A7CABDD-4D6D-4DF6-8EF5-4B7BF89EFAAD@jisc.ac.uk> <20160718143347.GA26878@nic.fr>
In-Reply-To: <20160718143347.GA26878@nic.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:152:7c81:1522:50da:c10]
x-ms-office365-filtering-correlation-id: 65a84858-4ca6-4830-0391-08d3af2c0c70
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 20:WYJqJXmsLf64UOug+fQTeDv9ycEWLtsgUqDriwc9S/NkE9V1IwcAbdtv29k2g0VQFUs5J/R5us4ofMJBt4BHL0vb0/XsJ8SELNgeGswAiGuhXqVA87BkiCT5SR4hBVM5Tkzw/rc7KxMS8UhIaVhUo6uXFMuXwnM1Eti27v1iJg0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB454F8F5C2BC4103D3842BBED6360@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(274715658323672)(209352067349851);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(24454002)(199003)(189002)(288314003)(3660700001)(68736007)(50986999)(2950100001)(4326007)(586003)(33656002)(101416001)(76176999)(305945005)(19580405001)(19580395003)(2900100001)(7846002)(11100500001)(2906002)(74482002)(110136002)(189998001)(7736002)(82746002)(81166006)(5002640100001)(106116001)(10400500002)(50226002)(86362001)(83716003)(87936001)(8676002)(36756003)(81156014)(6116002)(102836003)(122556002)(97736004)(92566002)(15975445007)(3280700002)(77096005)(105586002)(106356001)(57306001)(8936002)(142923001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <003CB4AE1E16BD4997947DB0EBEEA4A1@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2016 16:53:30.9900 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
X-MC-Unique: _ax8D5jnOXasQzXH2Fqu7A-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/iFGe2USJH9EWbPmmvh00PZjEw6Y>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] use of .home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 16:53:40 -0000

> On 18 Jul 2016, at 15:33, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>=20
> On Mon, Jul 18, 2016 at 01:50:25PM +0000,
> Tim Chown <Tim.Chown@jisc.ac.uk> wrote=20
> a message of 69 lines which said:
>=20
>> There are articles online that suggest 500M hits/day to the roots
>> for .home,
>=20
> L-root alone receives 180 Mhits/day so it is possible. (Source:
> http://stats.dns.icann.org/hedgehog/ )
>=20
>> and that .home is the heaviest used unallocated TLD.
>=20
> No, it is .local. (Source: the same)

Well, that=92s a special use domain name, so allocated of sorts.

Tim


From nobody Mon Jul 18 10:08:18 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F3912D0CE for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 10:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FQL5Bb68US9S for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 10:08:15 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C252912D53D for <homenet@ietf.org>; Mon, 18 Jul 2016 10:08:14 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id o80so126339877wme.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 10:08:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ePC006xNHbtEtJATOa6ACu3HY8Ium85OE2NwFfkw1wY=; b=hJFYSoc/db7v/wKzTVgMCk8ZHQ9Ki/oP5dAKxc+iiEAHs+fgvReLYDKKzsFzU2zutd nDnZI7dBb02JS4YyjhNBB6J7aKGemRBixz1pOneYnS470c0qt+k1YsZQ2IrTFMBW04X2 v3OVgQyE4VYyr8WoHTuoAu20WOwbTgF0uHw+I8CYF25tcc9YkEJsdiHtWc1aCTU8jluR UKPyYWnryFdXduNSUllytjHyvcyeLfwEsTcprq62mdAUEZeYYdQ2yJeT2QUNaP0RB7RB WZOEXYPAFFyLxOkyhZqAxdQNKfVCUyVICZv5D+N1q2AQv8lxMJKTutv3cpGn3llD8kXm P/vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ePC006xNHbtEtJATOa6ACu3HY8Ium85OE2NwFfkw1wY=; b=ldhQRmu2JjhxN8hyz3qmt7nxkJT0abx+vBxA2XaxAXPFa+sSbqgMsiRZ1QtZj6qKVW ryp8MNwzIX+c1OUOrMClH4Fih7J2wvYiJgJueglVVSgYXl3snjkf6E2teilFUL5BZbBz Nv5Ru9Ko5ZPdJx0blW6d8DJ4kq1e9Kyo9zoPg8Zq7gjT5r50Q0Gg5jIV3cSpRMS1n16f k1O0fSRI9f7ipLwi2WCs39f7U1I5mYt0aqvjWpiEAwYbnD2abaMEsAV485OBmIF6j0A5 LP41lwmoATZ3I/pBLjDdDjPgre19l59Tn3KuI0XApTplIXsMcT9TcrMBlZVQu0Zg9qcD 0ntw==
X-Gm-Message-State: ALyK8tItwOHMQf+vZ7lzhaaslsPtumxOfhFlObBWUOIMxOpGDuOxLdxUn1xjmn9xlpZZXw==
X-Received: by 10.28.85.133 with SMTP id j127mr38987454wmb.103.1468861692861;  Mon, 18 Jul 2016 10:08:12 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r127sm4776961wmf.23.2016.07.18.10.08.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 10:08:11 -0700 (PDT)
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <aae6a47d-6be8-8a00-4db4-4ef0a5f28733@gmail.com> <20160718164054.GA44253@mx2.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <81a2aff4-325d-aac0-ba14-dc89ea9c3966@gmail.com>
Date: Tue, 19 Jul 2016 05:08:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160718164054.GA44253@mx2.yitter.info>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/7EwH3J7ZpQgn2BMll_Njt4b8kc4>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 17:08:17 -0000

On 19/07/2016 04:40, Andrew Sullivan wrote:
> On Tue, Jul 19, 2016 at 03:22:57AM +1200, Brian E Carpenter wrote:
>> I don't get that. There's nothing about that in RFC 6761, which is mainly
>> very boring stuff that could be written up for this case, regardless
>> of the actual domain name. It's our own self-imposed bureaucracy.
> 
> Question 7 asks how registries and registrars should react to this
> name.  Given that the home TLD is in-process in the ICANN delegation
> procedures from the root zone, it is logically possible that at any
> moment ICANN could change its administrative procedures and home would
> get delegated.
> 
> So the answer to question 7 cannot be but ambiguous under these
> circumstances.  To me, that means that the requirements of 6761 can't
> possibly be met by home, and therefore home can't be allocated under
> special use.

Oh, I didn't interpret q7 quite that way. I would have answered
it with virtually the same text as q7 for localhost in RFC6761.
In fact several of the answers for localhost would serve for this case,
I think.

> This is the point that Jari made and that I was going to make at the
> mic: this isn't a mere political problem, but an actual functional one
> under our own procedures.  There is just no way we could allocate home
> under 6761 right now, without a very strong statement from ICANN that
> it would be ok.

I agree, but I see that as a meta-issue rather than an RFC6761 issue.

> I also argue (see my note from yesterday) that generalizing from
> "people seem to be doing somehting like this with this name, because I
> talked to a guy from $vendor and he said so" to "using this as a
> protocol switch in a protocol will not have a problem" seems to me to
> require a pretty big leap.

I agree. A brand new name with no known usage is a safer path.

>> RFC 6761 is one thing, but RFC 2860 is another. Under note (a)
>> to clause 4.3 of that MoU, the IETF can direct IANA to reserve
>> .$WHATEVER$. for technical use.
> 
> I strongly agree -- that part is the very reason why 6761 was even
> possible, in my opinion.
>  
>> Doing so for .home. would be entertaining, of course. Doing so
>> for .homenet. seems plausible.
> 
> I know it can be entertainment to watch those films where someone
> foolishly got into a car that was then swept over Niagara Falls.

As long as it isn't your own car.

   Brian

> 
> A
> 


From nobody Mon Jul 18 10:56:42 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA8A12D16D for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 10:56:41 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jmEzBuybzP2A for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 10:56:39 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5921912D0DD for <homenet@ietf.org>; Mon, 18 Jul 2016 10:56:39 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id g62so27273721lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 10:56:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fA1qnCArZK8u8JEHqLShnIkdEq93QQ3Nr5ujuEvTXRE=; b=ws8RXRQ+6/NbmhiZct/h1Rw1sO/bNqaSR7EAw38u+i3MRu0tFaLbsWhE0MVnWeZL+S Md00ikribG4fdf2WDNG5N/NxRviQmpWgYThZdBs5vD7cOLzgD3L4eg9AqDWzS+rOVAmx BEech7hnL4OF1zVH7phzy1c7n4jXFtcouQlWZaDJSnv1Vuc/szAzk57r8vHcJnfB8R7N ohB/71VLrkvOXokTAAtTEerfFsqB87h/SPdqIcYvxld+CDp+Z0DpomaF9UCBm20q4Mse 2FKI/phOMx2lV1rZz9RNNg8IBdslNGZZv/JqbSaMImTZwRnlS32kUdaV3SOmfNI/AIeW kM9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fA1qnCArZK8u8JEHqLShnIkdEq93QQ3Nr5ujuEvTXRE=; b=WuqzvIxkL45uo0+LAsOa7K7QXa8Ou6bVULrX3U55cpCMgahQxHjczX0KQRf5kV+u1P t2sC73gqoAAbJxFxt14oZWIAxaw+8zLRXJ4d5rb/aD3RuWFd9XomwMtXhz3eVtGO4HoA RE5qlrWuIbL/gs/BqJE40u4nnmwRBlJq93ugK8VP+4pq1IHz9rq64gbhl5zMqsfo1SuY 8FaRErU4+H3uj2odyaQ37FK6YPikTtm1aTTs+A6fxHlK/3x446k3swq75KqgntVVSKu5 aQ94HgV5Xut+kzO17EDQ/VO+JIzJzCnRrqYoXm0HN+svyFbiZzIMgjpVPksJS64pWRhK zSkg==
X-Gm-Message-State: ALyK8tJXR1SxIuFTtKuYx+RfUp9qn5xZbDbwI5nWziLzfYaab5Jtk+UZKofFfG+MYz/YYOvaFF1M89rmG3Pw0Q==
X-Received: by 10.25.91.149 with SMTP id p143mr14370958lfb.39.1468864597393; Mon, 18 Jul 2016 10:56:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 10:55:57 -0700 (PDT)
In-Reply-To: <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com> <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Jul 2016 19:55:57 +0200
Message-ID: <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a114124b48d300f0537ecb0fd
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/08WLTilJegSvUgaPxN1BFhXaDWs>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 17:56:41 -0000

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

Right now HNCP doesn't actually seem to have a TLV for advertising
resolvers.   How does this work now?

On Mon, Jul 18, 2016 at 5:24 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> > I don't think the document is proscribing speaking HNCP without speaking
> > DNS.
>
> Then I've misunderstood something, my bad.
>
> Suppose you have routers A and B on a link, and A implements DNS while
> B doesn't.  How does B find out that it should advertise A's DNS server in
> RA, DHCPv4 and DHCPv6?
>
> -- Juliusz
>
>
>

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

<div dir=3D"ltr">Right now HNCP doesn&#39;t actually seem to have a TLV for=
 advertising resolvers. =C2=A0 How does this work now?</div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 5:24 PM,=
 Juliusz Chroboczek <span dir=3D"ltr">&lt;<a href=3D"mailto:jch@pps.univ-pa=
ris-diderot.fr" target=3D"_blank">jch@pps.univ-paris-diderot.fr</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; I don&#3=
9;t think the document is proscribing speaking HNCP without speaking<br>
&gt; DNS.<br>
<br>
</span>Then I&#39;ve misunderstood something, my bad.<br>
<br>
Suppose you have routers A and B on a link, and A implements DNS while<br>
B doesn&#39;t.=C2=A0 How does B find out that it should advertise A&#39;s D=
NS server in<br>
RA, DHCPv4 and DHCPv6?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a114124b48d300f0537ecb0fd--


From nobody Mon Jul 18 11:33:40 2016
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5331B12D128 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 11:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.822
X-Spam-Level: 
X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=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 0vYS6HNphrmx for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 11:33:35 -0700 (PDT)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 6C81F12D0BE for <homenet@ietf.org>; Mon, 18 Jul 2016 11:33:35 -0700 (PDT)
Received: from [192.168.43.129] (80.220.86.47) by julia1.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 5782991C003E35DF; Mon, 18 Jul 2016 21:32:51 +0300
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com>
Date: Mon, 18 Jul 2016 20:33:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C165EBBE-484A-4EBE-86FE-E85D69B31BA4@iki.fi>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com> <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/2-L2nE3gFbdlQ3SNXeXcLTeQh8Y>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 18:33:37 -0000

> On 18.7.2016, at 19.55, Ted Lemon <mellon@fugue.com> wrote:
> Right now HNCP doesn't actually seem to have a TLV for advertising =
resolvers.   How does this work now?

DHCP options have also DNS server options (for v4 and v6).

-Markus=


From nobody Mon Jul 18 11:45:45 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C29E012D1A9 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 11:45:44 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 RpmJSEVkmMnO for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 11:45:43 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D72D812B077 for <homenet@ietf.org>; Mon, 18 Jul 2016 11:45:42 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id l69so81256417lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 11:45:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=TD1eNAEybw/u0KCONVO/BpewJrXe4FV34xVXFL+5RSs=; b=YCu8M2aXCdpZJsFLPEeDNH0nZycy1xhIHNdGrzL0OQXS70nNfWLllPAHa4vsFa2Lco /2ULnJ9o/jIzZDI4aqdRi2gUSDV4C2bsQhz1TXb5ghCd3mQJWI7JElHcE6TzmcXkycHq LdwoPY3UrPCxQ8sZXnW14RdDOxsCVkdlPeF/1uiTwpDgL6NWLLPx72v9dhkgDqsIKlqC HhMzOO85nFWBVC5QkSkCd1xkL/06yJ5JNPhKN73lU6ur2V+eEjGMlc9J4LC3y+q+ZBIR uHzmJ61Z0MGQYD+K3VZdAw88UTlCOpFg8UsEYVWFHwH9v7n5JnAO4dKB6p6BsKcdfiTb 1BMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=TD1eNAEybw/u0KCONVO/BpewJrXe4FV34xVXFL+5RSs=; b=KZQmI82y4jZIUB0sjX1laPg12oCB46UOQDqCogd3ZTlkVjS7RnuQvIqMroctWQTuiR XOHShv83zIVJI2s78MBX3IMc3VXVT+uP+UMxFCJ2hPipTgisITOX3eXrdgFbGRmz0b04 McJggED6j8WBSB7fJDl9m/DHgfZSD9PFsrHZ0FtFbcgi+6pNzgcQUUdX9fQQp6NsgpRM cwVga/cXWXsZ9xI9MvQWeIag9ZFBdgUrXq2MMnjUPPobMjVnBWFd5VWqSPJ7Wl/derJd cwdIaToDn2zA0Oa8HeKjURvf6RNS+t7MuhBw0EeA4iR6ajOKf6SUPzkIi214CXkt8oEL m/Rw==
X-Gm-Message-State: ALyK8tLONNEb4/voLS+WXH1lmd+Lw1gsuevNAMh1vwYzd/bCLMTGA8oaPYMBG6P83bbocwU/cuVKcilnErTX8Q==
MIME-Version: 1.0
X-Received: by 10.25.159.10 with SMTP id i10mr4744897lfe.131.1468867540919; Mon, 18 Jul 2016 11:45:40 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 11:45:40 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 11:45:40 -0700 (PDT)
In-Reply-To: <C165EBBE-484A-4EBE-86FE-E85D69B31BA4@iki.fi>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com> <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com> <C165EBBE-484A-4EBE-86FE-E85D69B31BA4@iki.fi>
Date: Mon, 18 Jul 2016 20:45:40 +0200
Message-ID: <CAPt1N1mqYDEDrLj54Ck1MmOf+L7a6L43yL0tR_NfN5nXaLYNCg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: multipart/alternative; boundary=001a11411c42ffbc410537ed5fe5
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ETbBOt2LZixxdk9miGk_lRerYJ0>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 18:45:45 -0000

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

Ah, thanks.  So, this could be used, but would give limited functionality
to links served only by router b.

The right solution will involve using hncp, I hope, to elect the primary
server for the network, and all updates would be sent to that server. Other
router could act as secondaries, or just forward DNS messages to the
nearest (or any) primary or secondary.

I think the election process is probably the hardest thing in this
solution, and I am hoping someone already knows how to do it...  :)

On Jul 18, 2016 20:33, "Markus Stenberg" <markus.stenberg@iki.fi> wrote:

> > On 18.7.2016, at 19.55, Ted Lemon <mellon@fugue.com> wrote:
> > Right now HNCP doesn't actually seem to have a TLV for advertising
> resolvers.   How does this work now?
>
> DHCP options have also DNS server options (for v4 and v6).
>
> -Markus

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

<p dir=3D"ltr">Ah, thanks.=C2=A0 So, this could be used, but would give lim=
ited functionality to links served only by router b. </p>
<p dir=3D"ltr">The right solution will involve using hncp, I hope, to elect=
 the primary server for the network, and all updates would be sent to that =
server. Other router could act as secondaries, or just forward DNS messages=
 to the nearest (or any) primary or secondary.</p>
<p dir=3D"ltr">I think the election process is probably the hardest thing i=
n this solution, and I am hoping someone already knows how to do it...=C2=
=A0 :)</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 18, 2016 2=
0:33, &quot;Markus Stenberg&quot; &lt;<a href=3D"mailto:markus.stenberg@iki=
.fi">markus.stenberg@iki.fi</a>&gt; wrote:<br type=3D"attribution"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">&gt; On 18.7.2016, at 19.55, Ted Lemon &lt;<a href=
=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt; Right now HNCP doesn&#39;t actually seem to have a TLV for advertising=
 resolvers.=C2=A0 =C2=A0How does this work now?<br>
<br>
DHCP options have also DNS server options (for v4 and v6).<br>
<br>
-Markus</blockquote></div></div>

--001a11411c42ffbc410537ed5fe5--


From nobody Mon Jul 18 14:00:43 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A0E12B00D for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 15DZypONVzh7 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:00:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A2E6126FDC for <homenet@ietf.org>; Mon, 18 Jul 2016 14:00:40 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 4DB5C200A7; Mon, 18 Jul 2016 17:10:04 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CC75E638D1; Mon, 18 Jul 2016 17:00:38 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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: Mon, 18 Jul 2016 17:00:38 -0400
Message-ID: <17161.1468875638@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/rLRQ-EXeGRS6EtCAIA0Rb9KVRdQ>
Cc: homenet@ietf.org
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 21:00:42 -0000

--=-=-=
Content-Type: text/plain


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    > (4) Is there WG consensus on requiring a ULA?

I believe that this is.
a) it's in rfc7084 (so they are there even before homenet existed)
b) it's in rfc7368 (it's in our architecture)

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV41DcYCLcPvd0N1lAQJ0sQf+KmqhU923H8kQV/0fuXpTueWVxTkmktRr
MCIv5ZuwfQd0aUeMiuxTTG51ffBJw4CK4iRmY0fvk7MXubXSPCj073CHQNF9kkZw
Lo8vQTocEmVPob49SdzBmdKCBBimhrbp1OoUz/mI260qt5+6kUP+VVEIABlK2Thv
LTnErp7hJVNSqOdZdo3aIueR8VeS7PiBE6rUXMaI7k2gBZVbshSVo4MctjZegcW9
pRBU1/Zi27SiH8Rur8rFfpds1Spne1sChlVDMdObRlp9DG5KPQ7lM8T5U0rC3O64
OM3FApCmZhnmw3fkM0zab4g6ARrjzngO//fDIkjZzbcMAFDSXUZJ6w==
=uoyF
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jul 18 14:34:05 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0BB12D91A for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:34:03 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 eKoHeTHR5kDK for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:34:02 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8A3E12D504 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:34:01 -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/56228) with ESMTP id u6ILXxsb012400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Jul 2016 23:33:59 +0200
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/56228) with ESMTP id u6ILXw2C009735; Mon, 18 Jul 2016 23:33:59 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9790561FA2; Mon, 18 Jul 2016 23:33:58 +0200 (CEST)
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 1ZThUf7Gbe9t; Mon, 18 Jul 2016 23:33:57 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id F2F7161FA1; Mon, 18 Jul 2016 23:33:53 +0200 (CEST)
Date: Mon, 18 Jul 2016 23:33:56 +0200
Message-ID: <87poqazl4r.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mTU+AAFZHjw0FArPqUtsQG7z3dMqRmra3wFLgFL3+gDA@mail.gmail.com> <CAPt1N1no4PHe18aKM+wtaNM23a0UMkr8WBrQkwZXSockHuTCcQ@mail.gmail.com> <8760s30z49.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_dx+38=tZ3YdTKuYQcoZ3BLoE+B975hrDtSfW5nOmwQ@mail.gmail.com> <8737n70y0x.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mHKWiGxVBAz41FYupPiAFwsLc0rHEWgZUsvEue0gm7xQ@mail.gmail.com>
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]); Mon, 18 Jul 2016 23:33:59 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 18 Jul 2016 23:33:59 +0200 (CEST)
X-Miltered: at korolev with ID 578D4B47.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578D4B46.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578D4B47.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: 578D4B46.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 : 578D4B47.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578D4B46.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: <https://mailarchive.ietf.org/arch/msg/homenet/Qscgx8X2mIt567AHmwpXWDXw80g>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 21:34:04 -0000

> Right now HNCP doesn't actually seem to have a TLV for advertising
> resolvers.

That's exactly what I was trying to get at.

> How does this work now?

Not very well.

HNCP announces *external* resolvers in the DHCPv4- and DHCPv6-DATA
sub-TLVs of the EXTERNAL-CONNECTION TLV.  Hnetd uses this data to set up
a recursive DNS server which has all the usual smarts for selecting the
server to forward to, and also acts as an authoritative server for some
local zones (I'm shaky on the exact details).  Shncpd is much dumber, it
just merges all the EXTERNAL-CONNECTIONs' data and pushes the result to
the client using RA and DHCPv4 (shcnpd has no support for DHCPv6 yet).

There is no provision for advertising a DNS server that's not associated
with an external connection, i.e. that's within the Homenet.

> I think the election process is probably the hardest thing in this
> solution, and I am hoping someone already knows how to do it... :)

HNCP does perform a number of link-local elections, and uses two different
mechanisms:

  - for advertising assigned prefixes, it uses an OSPF-like election
    mechanism, but with no pre-elected backup;
  - for choosing e.g. DHCPv4 servers, it uses an ISIS-like election
    mechanism, which I happen to believe is a bad choice.

It should be possible to add a Homenet-local election mechanism to HNCP in
order to pick a recursive DNS server, but this would constitute a non-trivial
change to the protocol.  (Elections are fun, except in the UK, so I'd be
quite willing to help.)

-- Juliusz


From nobody Mon Jul 18 14:58:04 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEDAE12DAC9 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:58:02 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 asOCI3H-Du5z for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:58:01 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1204712DAB4 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:58:00 -0700 (PDT)
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/56228) with ESMTP id u6ILvw4P018156; Mon, 18 Jul 2016 23:57:58 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E682761FA2; Mon, 18 Jul 2016 23:57:58 +0200 (CEST)
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 rS8hrUwxdxPk; Mon, 18 Jul 2016 23:57:57 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id EFD9F61F9D; Mon, 18 Jul 2016 23:57:53 +0200 (CEST)
Date: Mon, 18 Jul 2016 23:57:56 +0200
Message-ID: <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <17161.1468875638@obiwan.sandelman.ca>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca>
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 [194.254.61.138]); Mon, 18 Jul 2016 23:57:59 +0200 (CEST)
X-Miltered: at korolev with ID 578D50E6.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578D50E6.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 : 578D50E6.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: <https://mailarchive.ietf.org/arch/msg/homenet/-bgbwSbZ-jCxAq3_Vtg4mCmx4sM>
Cc: homenet@ietf.org, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 21:58:03 -0000

>> (4) Is there WG consensus on requiring a ULA?

> I believe that this is.
> a) it's in rfc7084 (so they are there even before homenet existed)
> b) it's in rfc7368 (it's in our architecture)

RFC 7084 Section 4.3 says:

    The IPv6 CE router SHOULD be capable of generating a ULA prefix [RFC4193].

RFC 7368 Section 2.4 says:

    A home network running IPv6 should deploy ULAs

RFC 7788 Section 6.5 says:

    An HNCP router SHOULD create a ULA prefix if there is no other
    IPv6 prefix with a preferred time greater than 0 in the network.
    It MAY also do so if there are other delegated IPv6 prefixes

I do not believe that there is WG consensus that ULA generation should be
a MUST.

-- Juliusz


From nobody Mon Jul 18 14:58:58 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3962C12DAD1 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:58:56 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 YA-BnqoG5PQZ for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 14:58:54 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 042D212DA51 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:58:54 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id g62so25797lfe.3 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:58:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=92lSTpUcIjZGE6AAYzvxeHHEn92W6vLB6NX7TvijwZw=; b=A1xak4lEA/zt9HweNXdO4N1kuYQ1HXnGVzr70xvUbaVebAIo7xt1SKpFbqH2SOOkqW /Z4Nc4g/HAwIF+va7MV5/F1FVRh89WbG9LuqXFaa1MiPZSZ3fWBTAg+MP7FXZ54h5K7S 0sU0+H01n16slWCeKUEb1nG0+0PVCwWyDZ5OUjK6e42NKagHZ1y4O6wpy733CVbgb+n/ Eq4aV3I6xp/MawtqaDu7cXXWu+w6hc9bOJXaDiffUe1jf9HZbPGkupsOS/jYAt2Zpn2F hWUjpRRfvy7pvkrvd/pzqyLdkLCjZ8HUkVGl+pjmXEDgMcJbJaeZ8vlrnorzoBEZ1EWn nmjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=92lSTpUcIjZGE6AAYzvxeHHEn92W6vLB6NX7TvijwZw=; b=N+uW9FtOMIcy0R6/z31tkuLhCDK/Sk13e3PAauZ7wt3F/X1w73LDjEx/240m367l2r xTQnmxCsLnQtBgNo88W8sKiJKBKCBv2IywAm+YukjaCE6aqij/3JpsVS6Fds+ISRF2KL iPqLfkGqNHo9YOUPazkL2X04J03rqXqNb2yDXBGUXWCKdt/ZGbgjePg0S0vP1A6+3zNZ ogO8DkB0EgvPfo0t72hLrA5phZCWw8Vxq3ggkOTqUuwnbq0Gzk1ys2byHv5AGFnxfKJG g2WN36mH70yO6a1l281wfYMR6XAAYnV1gC2lZxh+IBC9CuRw0sH/fWIrTBaZiHJZw37O typA==
X-Gm-Message-State: ALyK8tIzOYbFAv5yvmKSf1Sl91DkRYaYBLrZZS3Mz8u4PEs567m/5wPgsNP+8/TJi+gZB22r+SMWTX2uSmylgw==
MIME-Version: 1.0
X-Received: by 10.25.131.150 with SMTP id f144mr13258892lfd.53.1468879132091;  Mon, 18 Jul 2016 14:58:52 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 14:58:51 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 14:58:51 -0700 (PDT)
In-Reply-To: <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 18 Jul 2016 23:58:51 +0200
Message-ID: <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a113f20b8e2fc180537f012cf
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/RTDJUtjhoe9zA_AdIxvno8tHlzg>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 21:58:56 -0000

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

Why wouldn't you allocate one?

On Jul 18, 2016 22:57, "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr>
wrote:

> >> (4) Is there WG consensus on requiring a ULA?
>
> > I believe that this is.
> > a) it's in rfc7084 (so they are there even before homenet existed)
> > b) it's in rfc7368 (it's in our architecture)
>
> RFC 7084 Section 4.3 says:
>
>     The IPv6 CE router SHOULD be capable of generating a ULA prefix
> [RFC4193].
>
> RFC 7368 Section 2.4 says:
>
>     A home network running IPv6 should deploy ULAs
>
> RFC 7788 Section 6.5 says:
>
>     An HNCP router SHOULD create a ULA prefix if there is no other
>     IPv6 prefix with a preferred time greater than 0 in the network.
>     It MAY also do so if there are other delegated IPv6 prefixes
>
> I do not believe that there is WG consensus that ULA generation should be
> a MUST.
>
> -- Juliusz
>

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

<p dir=3D"ltr">Why wouldn&#39;t you allocate one?</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 18, 2016 2=
2:57, &quot;Juliusz Chroboczek&quot; &lt;<a href=3D"mailto:jch@pps.univ-par=
is-diderot.fr">jch@pps.univ-paris-diderot.fr</a>&gt; wrote:<br type=3D"attr=
ibution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">&gt;&gt; (4) Is there WG consensus =
on requiring a ULA?<br>
<br>
&gt; I believe that this is.<br>
&gt; a) it&#39;s in rfc7084 (so they are there even before homenet existed)=
<br>
&gt; b) it&#39;s in rfc7368 (it&#39;s in our architecture)<br>
<br>
RFC 7084 Section 4.3 says:<br>
<br>
=C2=A0 =C2=A0 The IPv6 CE router SHOULD be capable of generating a ULA pref=
ix [RFC4193].<br>
<br>
RFC 7368 Section 2.4 says:<br>
<br>
=C2=A0 =C2=A0 A home network running IPv6 should deploy ULAs<br>
<br>
RFC 7788 Section 6.5 says:<br>
<br>
=C2=A0 =C2=A0 An HNCP router SHOULD create a ULA prefix if there is no othe=
r<br>
=C2=A0 =C2=A0 IPv6 prefix with a preferred time greater than 0 in the netwo=
rk.<br>
=C2=A0 =C2=A0 It MAY also do so if there are other delegated IPv6 prefixes<=
br>
<br>
I do not believe that there is WG consensus that ULA generation should be<b=
r>
a MUST.<br>
<br>
-- Juliusz<br>
</blockquote></div></div>

--001a113f20b8e2fc180537f012cf--


From nobody Mon Jul 18 15:28:09 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D93AE12DB3B for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 15:28:07 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 DiMoSNCpVExs for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 15:28:06 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8249E12DB36 for <homenet@ietf.org>; Mon, 18 Jul 2016 15:28:06 -0700 (PDT)
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/56228) with ESMTP id u6IMS4wq025646; Tue, 19 Jul 2016 00:28:04 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3E60B61FA1; Tue, 19 Jul 2016 00:28:04 +0200 (CEST)
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 iD3LhxC2fIeH; Tue, 19 Jul 2016 00:28:03 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6942A61F9D; Tue, 19 Jul 2016 00:28:02 +0200 (CEST)
Date: Tue, 19 Jul 2016 00:28:04 +0200
Message-ID: <874m7mh98r.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com>
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 [194.254.61.138]); Tue, 19 Jul 2016 00:28:04 +0200 (CEST)
X-Miltered: at korolev with ID 578D57F4.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578D57F4.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 : 578D57F4.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Qs8btN_Lpggoyny9-bpl3yhj8EU>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 22:28:08 -0000

> Why wouldn't you allocate one?

I would.  ULAs are a goodness.  Probably.  I'm planning to add ULA
generation to shncpd at some future date, and perhaps even enable it by
default.

The question is about the level of MUSTiness.  I only see two reasonable
possibilities:

  1. ULA is SHOULD, and we cannot rely on their existence;
  2. ULA is MUST, which puts an additional requirement on implementations,
     but allows us to rely on their existence except during reconvergence.

No compromise between these two positions is possible.  It is not reasonable
to say that ULA is SHOULD while simultaneously relying on their existence,
which is what we're apparently trying to do.

-- Juliusz


From nobody Mon Jul 18 15:51:17 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B16BF12B05C for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 15:51:15 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 U3jjpbsj_Lrf for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 15:51:14 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B64C712B03C for <homenet@ietf.org>; Mon, 18 Jul 2016 15:51:13 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id l69so694545lfg.1 for <homenet@ietf.org>; Mon, 18 Jul 2016 15:51:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Ts8b6JQSiB/BpVcZ/ep/OWqS1O8CDL5U98rq5CP12gc=; b=pOzKzyjilSvZXqutubaIblThIvu5Mbp0+7keKXKjsJgTDA3alk8JGX6DrfJUFMayBh xXaLeVH+XY6TkDVPtyjQ7Lv6wHgLfZIJ0tN+lvud6k+LTwWm1ptZuoSmnlGjbBCpnZ4d j7OBgrkVwmEUf4yT8V0rRfvXBFNva0vvye6cJ0Vzr1HKnJlzarE6q720BkXgYAUDos2w IxNGkWhTr8t6LU5lK1Ba31k4OjzECHcUVK1fDEr10YdlBJQBNm8B2rrZCwA6YZBAyETi 2xggKVxFWlWTvwuCCH3x0MXo328V8sf6LRVrpHl2oQPOBrK7sDAZuv9yMXPL6YzsfnW6 ZsjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Ts8b6JQSiB/BpVcZ/ep/OWqS1O8CDL5U98rq5CP12gc=; b=gK52OeRsXaoEaWddIRu+siB17uwmQNt3+mJ5T15mmU2JJ+NHNp+rqllJcbZHZjpdeV wWeDTXibE9Hr32W7313XvTbhsQjgl+guzdxqXP+DkwSEbn2wSNliIvM0zkFAeydR4b8h ETlhYFhj15x6f6Q3pYwGFGHgPt5tyRfABD9feDBiKUjvkJbjdqX0Y274ZI9fmHjnHBrr Q/az9uBWEyCs8s6GM/wRXRK8MexPQpJXXQU5pOHXH38qfRMZp8JFUfvgRNxRgipfDhB5 06/SDGplFaTLVNQZf7LcblqC1ULCbA3y2TBDGdIDaWhodERHHg4N8utXjMqSBWzeq1Wk ettQ==
X-Gm-Message-State: ALyK8tJVx7EQ0dtlzyxMivAojPwFpWmaMRq44HXr26OJB98b94ulG/TPFNFrCsMUtvZizi0ubImJQbrgPLpR2g==
MIME-Version: 1.0
X-Received: by 10.25.131.150 with SMTP id f144mr13299570lfd.53.1468882271935;  Mon, 18 Jul 2016 15:51:11 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 15:51:11 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Mon, 18 Jul 2016 15:51:11 -0700 (PDT)
In-Reply-To: <CAPt1N1negfEtAHto8_pujgbi53F7Ecb85pboV7hv5ZvpAHvH2g@mail.gmail.com>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com> <874m7mh98r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mPko=oaGfhWP9dZBbu+pWStfUNxwT22sMTCN9vY1RGmw@mail.gmail.com> <CAPt1N1negfEtAHto8_pujgbi53F7Ecb85pboV7hv5ZvpAHvH2g@mail.gmail.com>
Date: Tue, 19 Jul 2016 00:51:11 +0200
Message-ID: <CAPt1N1kyB_tWKEp4tSQLocSN4aAQnsBnL6_cU0X4y4gSvm+1fQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a113f20b80930e40537f0ced2
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/bn_rBw0q05zhcA-MWnpEX02Nfh8>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 22:51:16 -0000

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

I think it's should in the sense that there may be done reason not to do it
on some case and we don't want to preclude that because there is no
protocol reason to do so, but we expect that it will be allocated unless
there is some good reason. We talked about this at length a couple of years
ago and captured the intent in the architecture doc, but maybe not in
enough detail?

On Jul 18, 2016 23:28, "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr>
wrote:

> Why wouldn't you allocate one?

I would.  ULAs are a goodness.  Probably.  I'm planning to add ULA
generation to shncpd at some future date, and perhaps even enable it by
default.

The question is about the level of MUSTiness.  I only see two reasonable
possibilities:

  1. ULA is SHOULD, and we cannot rely on their existence;
  2. ULA is MUST, which puts an additional requirement on implementations,
     but allows us to rely on their existence except during reconvergence.

No compromise between these two positions is possible.  It is not reasonable
to say that ULA is SHOULD while simultaneously relying on their existence,
which is what we're apparently trying to do.

-- Juliusz

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

<p dir=3D"ltr">I think it&#39;s should in the sense that there may be done =
reason not to do it on some case and we don&#39;t want to preclude that bec=
ause there is no protocol reason to do so, but we expect that it will be al=
located unless there is some good reason. We talked about this at length a =
couple of years ago and captured the intent in the architecture doc, but ma=
ybe not in enough detail?</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 18, 2016 2=
3:28, &quot;Juliusz Chroboczek&quot; &lt;<a href=3D"mailto:jch@pps.univ-par=
is-diderot.fr">jch@pps.univ-paris-diderot.fr</a>&gt; wrote:<br type=3D"attr=
ibution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">&gt; Why would=
n&#39;t you allocate one?<br>
<br>
</div>I would.=C2=A0 ULAs are a goodness.=C2=A0 Probably.=C2=A0 I&#39;m pla=
nning to add ULA<br>
generation to shncpd at some future date, and perhaps even enable it by<br>
default.<br>
<br>
The question is about the level of MUSTiness.=C2=A0 I only see two reasonab=
le<br>
possibilities:<br>
<br>
=C2=A0 1. ULA is SHOULD, and we cannot rely on their existence;<br>
=C2=A0 2. ULA is MUST, which puts an additional requirement on implementati=
ons,<br>
=C2=A0 =C2=A0 =C2=A0but allows us to rely on their existence except during =
reconvergence.<br>
<br>
No compromise between these two positions is possible.=C2=A0 It is not reas=
onable<br>
to say that ULA is SHOULD while simultaneously relying on their existence,<=
br>
which is what we&#39;re apparently trying to do.<br>
<font color=3D"#888888"><br>
-- Juliusz<br>
</font></blockquote></div><br></div>

--001a113f20b80930e40537f0ced2--


From nobody Mon Jul 18 16:17:12 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001DC12DB77 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 16:17:10 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 U3QVHhLCNZve for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 16:17:08 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DC8812D66F for <homenet@ietf.org>; Mon, 18 Jul 2016 16:17:08 -0700 (PDT)
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/56228) with ESMTP id u6INH67m003221 for <homenet@ietf.org>; Tue, 19 Jul 2016 01:17:06 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 8150C61FA1 for <homenet@ietf.org>; Tue, 19 Jul 2016 01:17:06 +0200 (CEST)
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 yqFmJruw2Ehx for <homenet@ietf.org>; Tue, 19 Jul 2016 01:17:04 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 4AA3C61F9D for <homenet@ietf.org>; Tue, 19 Jul 2016 01:17:04 +0200 (CEST)
Date: Tue, 19 Jul 2016 01:17:07 +0200
Message-ID: <8737n6h6z0.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 [194.254.61.138]); Tue, 19 Jul 2016 01:17:06 +0200 (CEST)
X-Miltered: at korolev with ID 578D6372.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578D6372.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 : 578D6372.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: <https://mailarchive.ietf.org/arch/msg/homenet/0eSwknZ_5Dyx-PTGk-3SUcmKi44>
Subject: [homenet] More about lossy links and yo-yo neighbours
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 23:17:11 -0000

Dear all,

We only confirmed the yo-yo issue on Sunday, which caused me to send the
latest version of my slides at the very latest moment.  I therefore cannot
blame the chairs for forcing me to work with an older version of my talk
which didn't contain the explanation -- oh, what the heck, yes, I can ;-)
Please bear with me while I lecture a little.

It has been known since at least the early noughts that in a wireless mesh
network, no matter how well designed, persistently lossy links are
unavoidable.  Consider the following topology, where A, B and C are
wireless routers:

    . . . . .
   .         .
  A --- B --- C

By design, A and B are neighbours, as are B and C.  A and C are not
supposed to be neighbours (they are out of range of each other), but it is
unavoidable that once in a while C will hear a packet coming from A.

In the current version of HNCP, as soon as C receives a multicast
NETWORK-STATE from A, it inserts A in its list of peers, and, MS-Trickle
permitting, floods a new long NODE-STATE throughout the network.  Since it
no longer receives anything from C, it times out A from its list of
neighbours, and floods again.  The result is two long NODE-STATES flooded
across the network for every packet that manages to cross a highly
marginal link.  In a dense mesh, the number of such highly marginal links
is roughly quadratic in the number of routers -- the effect is that with
just 7 routers, we see one spurious reflooding every few seconds.  (Please
see the end of this message for a packet trace.)

HNCP, however, has a number of features that prevent the spurious topology
changes and associated refloodings from having any serious consequences.
First, the "ad-hoc" interface type (Section 5.1 of RFC 7788) is designed
so that a spurious topology change doesn't cause any renumbering -- since
the set of Common Links doesn't change, the PA algorithm is never invoked.
Second, even if the links are mis-configured, the PA algorithm is stable
enough to avoid renumbering outside of the affected link in most cases.
And last, reflooding is controlled by MS-Trickle (an algorithm that is
almost, but not quite, exactly unlike Trickle), which prevents refloodings
from happening too often.

I'm not sure what to do about this.  We could of course ignore the
issue -- after all, it's just a few hundred bytes per second extra control
traffic -- but I'm a little uncomfortable with that, I fear that it might
get us into trouble at some later stage.  Markus has a suggestion that
consists in tweaking the parameters of MS-Trickle.  My intuition is that
it's the wrong level at which to tackle the problem, but I have been wrong
about MS-Trickle before.

Appended below for your enjoyment is a fragment of a packet trace.  At
time 25.897 node ef:36:04:89 floods its node state.  At time 31.359, it
floods its state again, which is almost identical -- the only change is
the addition of the neighbour 9b:18:b7:26.

-- Juliusz

16:21:25.897046 IP6 (hlim 64, next-header UDP (17) payload length: 1396) fe80::e246:9aff:fe4e:912a.8231 > fe80::e246:9aff:fe4e:91e4.8231: [udp sum ok] hncp (1388)
	Node endpoint (12) NID: ef:36:04:89 EPID: 00000004
	Node state (1376) NID: ef:36:04:89 seqno: 72968 2.11s hash: c97a0c0c205d9de1
		Peer (16) Peer-NID: 24:1f:49:aa Peer-EPID: 00000002 Local-EPID: 00000004
		Peer (16) Peer-NID: 24:1f:49:aa Peer-EPID: 00000003 Local-EPID: 00000003
		Peer (16) Peer-NID: 75:05:c4:15 Peer-EPID: 00000002 Local-EPID: 00000003
		Peer (16) Peer-NID: 90:d1:74:28 Peer-EPID: 00000003 Local-EPID: 00000004
		Peer (16) Peer-NID: 90:d1:74:28 Peer-EPID: 00000004 Local-EPID: 00000003
		Peer (16) Peer-NID: 9b:18:b7:26 Peer-EPID: 00000002 Local-EPID: 00000004
		HNCP-Version (22) M: 0 P: 4 H: 4 L: 4 User-agent: hnetd/cda52dc
		Assigned-Prefix (18) EPID: 00000001 Prty: 2 Prefix: fd1f:f88c:e207:65::/64
		Assigned-Prefix (18) EPID: 00000002 Prty: 2 Prefix: fd1f:f88c:e207:47::/64
		Assigned-Prefix (18) EPID: 00000004 Prty: 2 Prefix: fd1f:f88c:e207:61::/64
		Assigned-Prefix (20) EPID: 00000001 Prty: 2 Prefix: 2001:660:3301:9209:1e::/80
		Assigned-Prefix (20) EPID: 00000002 Prty: 2 Prefix: 2001:660:3301:9209:41::/80
		Assigned-Prefix (20) EPID: 00000004 Prty: 3 Prefix: 2001:660:3301:9208:61::/80
		Assigned-Prefix (25) EPID: 00000001 Prty: 2 Prefix: 10.219.152.0/24
		Assigned-Prefix (25) EPID: 00000002 Prty: 2 Prefix: 10.191.218.0/24
		Assigned-Prefix (25) EPID: 00000004 Prty: 2 Prefix: 10.0.97.0/24
		Node-Address (24) EPID: 00000001 IP Address: 10.219.152.5
		Node-Address (24) EPID: 00000001 IP Address: 2001:660:3301:9209:1e::5
		Node-Address (24) EPID: 00000001 IP Address: fd1f:f88c:e207:65::5
		Node-Address (24) EPID: 00000002 IP Address: 10.191.218.61
		Node-Address (24) EPID: 00000002 IP Address: 2001:660:3301:9209:41::3d
		Node-Address (24) EPID: 00000002 IP Address: fd1f:f88c:e207:47::3d
		Node-Address (24) EPID: 00000003 IP Address: 10.0.116.30
		Node-Address (24) EPID: 00000003 IP Address: 2001:660:3301:9208:5b::1e
		Node-Address (24) EPID: 00000003 IP Address: fd1f:f88c:e207:dba3::1e
		Node-Address (24) EPID: 00000004 IP Address: 10.0.97.5
		Node-Address (24) EPID: 00000004 IP Address: 2001:660:3301:9208:61::5
		Node-Address (24) EPID: 00000004 IP Address: fd1f:f88c:e207:61::5
		DNS-Delegated-Zone (33) IP-Address: 2001:660:3301:9209:1e::5 lb- lan.r.home
		DNS-Delegated-Zone (35) IP-Address: 2001:660:3301:9208:61::5 lb- wlan1.r.home
		DNS-Delegated-Zone (35) IP-Address: 2001:660:3301:9209:41::3d lb- wlan0.r.home
		DNS-Delegated-Zone (36) IP-Address: 2001:660:3301:9208:5b::1e --- wlan01.r.home
		DNS-Delegated-Zone (43) IP-Address: 2001:660:3301:9208:61::5 --- 97.0.10.in-addr.arpa
		DNS-Delegated-Zone (46) IP-Address: 2001:660:3301:9209:1e::5 --- 152.219.10.in-addr.arpa
		DNS-Delegated-Zone (46) IP-Address: 2001:660:3301:9209:41::3d --- 218.191.10.in-addr.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9208:61::5 --- 1.6.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9209:1e::5 --- 5.6.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9209:41::3d --- 7.4.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9208:61::5 --- 1.6.0.0.8.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9209:1e::5 --- e.1.0.0.9.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9209:41::3d --- 1.4.0.0.9.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		Node-Name (22) IP-Address: 10.0.97.5 Name: "r"
		Node-Name (22) IP-Address: 2001:660:3301:9208:61::5 Name: "r"

[...]

16:21:31.359209 IP6 (hlim 64, next-header UDP (17) payload length: 1412) fe80::e246:9aff:fe4e:912a.8231 > fe80::e246:9aff:fe4e:91e4.8231: [udp sum ok] hncp (1404)
	Node endpoint (12) NID: ef:36:04:89 EPID: 00000004
	Node state (1392) NID: ef:36:04:89 seqno: 72974 1.87s hash: 79c431ca9a655adf
		Peer (16) Peer-NID: 24:1f:49:aa Peer-EPID: 00000002 Local-EPID: 00000004
		Peer (16) Peer-NID: 24:1f:49:aa Peer-EPID: 00000003 Local-EPID: 00000003
		Peer (16) Peer-NID: 75:05:c4:15 Peer-EPID: 00000002 Local-EPID: 00000003
		Peer (16) Peer-NID: 90:d1:74:28 Peer-EPID: 00000003 Local-EPID: 00000004
		Peer (16) Peer-NID: 90:d1:74:28 Peer-EPID: 00000004 Local-EPID: 00000003
		Peer (16) Peer-NID: 9b:18:b7:26 Peer-EPID: 00000002 Local-EPID: 00000004
		Peer (16) Peer-NID: 9b:18:b7:26 Peer-EPID: 00000003 Local-EPID: 00000003
		HNCP-Version (22) M: 0 P: 4 H: 4 L: 4 User-agent: hnetd/cda52dc
		Assigned-Prefix (18) EPID: 00000001 Prty: 2 Prefix: fd1f:f88c:e207:65::/64
		Assigned-Prefix (18) EPID: 00000002 Prty: 2 Prefix: fd1f:f88c:e207:47::/64
		Assigned-Prefix (18) EPID: 00000004 Prty: 2 Prefix: fd1f:f88c:e207:61::/64
		Assigned-Prefix (20) EPID: 00000001 Prty: 2 Prefix: 2001:660:3301:9209:1e::/80
		Assigned-Prefix (20) EPID: 00000002 Prty: 2 Prefix: 2001:660:3301:9209:41::/80
		Assigned-Prefix (20) EPID: 00000004 Prty: 3 Prefix: 2001:660:3301:9208:61::/80
		Assigned-Prefix (25) EPID: 00000001 Prty: 2 Prefix: 10.219.152.0/24
		Assigned-Prefix (25) EPID: 00000002 Prty: 2 Prefix: 10.191.218.0/24
		Assigned-Prefix (25) EPID: 00000004 Prty: 2 Prefix: 10.0.97.0/24
		Node-Address (24) EPID: 00000001 IP Address: 10.219.152.5
		Node-Address (24) EPID: 00000001 IP Address: 2001:660:3301:9209:1e::5
		Node-Address (24) EPID: 00000001 IP Address: fd1f:f88c:e207:65::5
		Node-Address (24) EPID: 00000002 IP Address: 10.191.218.61
		Node-Address (24) EPID: 00000002 IP Address: 2001:660:3301:9209:41::3d
		Node-Address (24) EPID: 00000002 IP Address: fd1f:f88c:e207:47::3d
		Node-Address (24) EPID: 00000003 IP Address: 10.0.116.30
		Node-Address (24) EPID: 00000003 IP Address: 2001:660:3301:9208:5b::1e
		Node-Address (24) EPID: 00000003 IP Address: fd1f:f88c:e207:dba3::1e
		Node-Address (24) EPID: 00000004 IP Address: 10.0.97.5
		Node-Address (24) EPID: 00000004 IP Address: 2001:660:3301:9208:61::5
		Node-Address (24) EPID: 00000004 IP Address: fd1f:f88c:e207:61::5
		DNS-Delegated-Zone (33) IP-Address: 2001:660:3301:9209:1e::5 lb- lan.r.home
		DNS-Delegated-Zone (35) IP-Address: 2001:660:3301:9208:61::5 lb- wlan1.r.home
		DNS-Delegated-Zone (35) IP-Address: 2001:660:3301:9209:41::3d lb- wlan0.r.home
		DNS-Delegated-Zone (36) IP-Address: 2001:660:3301:9208:5b::1e --- wlan01.r.home
		DNS-Delegated-Zone (43) IP-Address: 2001:660:3301:9208:61::5 --- 97.0.10.in-addr.arpa
		DNS-Delegated-Zone (46) IP-Address: 2001:660:3301:9209:1e::5 --- 152.219.10.in-addr.arpa
		DNS-Delegated-Zone (46) IP-Address: 2001:660:3301:9209:41::3d --- 218.191.10.in-addr.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9208:61::5 --- 1.6.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9209:1e::5 --- 5.6.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (63) IP-Address: 2001:660:3301:9209:41::3d --- 7.4.0.0.7.0.2.e.c.8.8.f.f.1.d.f.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9208:61::5 --- 1.6.0.0.8.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9209:1e::5 --- e.1.0.0.9.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		DNS-Delegated-Zone (71) IP-Address: 2001:660:3301:9209:41::3d --- 1.4.0.0.9.0.2.9.1.0.3.3.0.6.6.0.1.0.0.2.ip6.arpa
		Node-Name (22) IP-Address: 10.0.97.5 Name: "r"
		Node-Name (22) IP-Address: 2001:660:3301:9208:61::5 Name: "r"


From nobody Mon Jul 18 22:23:59 2016
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07A712D0DD for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 22:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.822
X-Spam-Level: 
X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=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 IIf8NbsZ5t93 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 22:23:55 -0700 (PDT)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.230]) by ietfa.amsl.com (Postfix) with ESMTP id 2309F12D08F for <homenet@ietf.org>; Mon, 18 Jul 2016 22:23:55 -0700 (PDT)
Received: from [192.168.43.129] (80.220.86.47) by julia1.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 5782991C0040761D; Tue, 19 Jul 2016 08:23:09 +0300
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <8737n6h6z0.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 19 Jul 2016 07:23:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <10F3094D-7B0C-4A05-B035-E6D6A1410D87@iki.fi>
References: <8737n6h6z0.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/gX0bQg0ULgb1MNpYxXc73avxn34>
Cc: homenet@ietf.org
Subject: Re: [homenet] More about lossy links and yo-yo neighbours
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 05:23:58 -0000

For the record, _within limits of current spec/implementation_ =
MS-Trickle parameter tuning can make the yo-yo effect arbitrarily rare. =
However, I think that the correct way of doing this would be either:

- Also not form neighbor links without indicator that the link is =
relatively stable; based on my experience, this is not 100% solution as =
some links exhibite loss that is function of time; however, this would =
limit the refloodings just to those links and they are most likely small =
subset of the whole.

- Something non-link-statey, notably not having global reachability =
graph (this implies TTLs, and selective flooding, so it is relatively =
different from DNCP as it is written now). As 'common link' concept is =
needed only by non-adhoc links in HNCP, this would work for adhoc =
networks _with_ same TLV content but different state synchronization =
algorithm. We discussed this privately in some group earlier and it also =
seemed workable.

Cheers,

-Markus=


From nobody Tue Jul 19 00:32:19 2016
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A90212DBA3 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 00:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.187
X-Spam-Level: 
X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 CFUnhUc_6pR6 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 00:32:15 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8655F12D15F for <homenet@ietf.org>; Tue, 19 Jul 2016 00:32:15 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:cd6e:85e:d558:8be8]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u6J7WADk091703 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 19 Jul 2016 07:32:11 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2001:67c:370:176:cd6e:85e:d558:8be8] claimed to be dhcp-b257.meeting.ietf.org
To: Ted Lemon <mellon@fugue.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk> <D3B0315C.95E19%terry.manderson@icann.org> <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se> <20160718141641.GI43287@mx2.yitter.info> <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <166c3ae5-aefb-f312-26f0-ac048cd46871@bogus.com>
Date: Tue, 19 Jul 2016 09:32:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1eJlUMLH8POL0krQWBSNoqbGmNCXFAWck"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/3iKXzu5cIQf7LOhdj9e0V0TBTp8>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 07:32:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1eJlUMLH8POL0krQWBSNoqbGmNCXFAWck
Content-Type: multipart/mixed; boundary="X0GgeogSUAlSHeUjtFvr2M2QkEAxPQw4d"
From: joel jaeggli <joelja@bogus.com>
To: Ted Lemon <mellon@fugue.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: HOMENET <homenet@ietf.org>
Message-ID: <166c3ae5-aefb-f312-26f0-ac048cd46871@bogus.com>
Subject: Re: [homenet] RFC 7788 and ".home"
References: <13d0215f-7868-d297-1cd9-4d50362aa67a@bellis.me.uk>
 <D3B0315C.95E19%terry.manderson@icann.org>
 <alpine.DEB.2.02.1607181532340.2309@uplift.swm.pp.se>
 <20160718141641.GI43287@mx2.yitter.info>
 <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>
In-Reply-To: <CAPt1N1kk9+sK0nm+zbpX+qXPk0a3H3WoUri-=vW0ua1xeWgdXA@mail.gmail.com>

--X0GgeogSUAlSHeUjtFvr2M2QkEAxPQw4d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 7/18/16 5:01 PM, Ted Lemon wrote:
> Yup.   In terms of minimizing risk to the IETF, switching to .homenet i=
s
> expedient--that's why I put it in the Homenet Naming/Service Discovery
> Architecture doc.   Perhaps some homenet participants aren't aware of
> the issues surrounding this.  =20
> The reason we are getting so much top-down push from IETF leadership on=

> this is not that IETF leadership are being political--it's that there's=

> a real cost to the IETF if one of the GTLD people decides that we have
> taken a name for which they paid an application fee.   I apologize for
> glossing over this in my earlier response.

The failure to direct IANA to assign the TLD also means that we
encouraged  the creation exactly the sort of attractive nuisance that
the consensus around advancing 6761 intended to adress. The situation we
find ourselves imperils developers as well as end-users both those
intending to employ it as is described in 7788 as well as those that do n=
ot.

> If people are interested in better understanding this problem, I
> encourage you to read
> this: https://tools.ietf.org/html/draft-tldr-sutld-ps-02#section-3
>=20
> You can get more background by reading section 4 as well.   Bear in
> mind, s/.local/.home/ in section 4.2.4.
>=20
> On Mon, Jul 18, 2016 at 4:16 PM, Andrew Sullivan <ajs@anvilwalrusden.co=
m
> <mailto:ajs@anvilwalrusden.com>> wrote:
>=20
>     On Mon, Jul 18, 2016 at 03:33:28PM +0200, Mikael Abrahamsson wrote:=

>     >
>     > .HOME has not been handed out by ICANN yet
>=20
>     There are several applications for home in the root zone.  To my mi=
nd,
>     that means that home has been claimed as being inside the global DN=
S
>     context, and therefore is not available under RFC 6761.
>=20
>     Best regards,
>=20
>     A
>=20
>     --
>     Andrew Sullivan
>     ajs@anvilwalrusden.com <mailto:ajs@anvilwalrusden.com>
>=20
>     _______________________________________________
>     homenet mailing list
>     homenet@ietf.org <mailto:homenet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/homenet
>=20
>=20
>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20



--X0GgeogSUAlSHeUjtFvr2M2QkEAxPQw4d--

--1eJlUMLH8POL0krQWBSNoqbGmNCXFAWck
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iEYEARECAAYFAleN13kACgkQ8AA1q7Z/VrJGBACfZMEhgf3pxRdsF26GZKRpdMZD
5BQAn0K5EvZ92IZAQpN/HHwVS4jrKuSp
=h4bs
-----END PGP SIGNATURE-----

--1eJlUMLH8POL0krQWBSNoqbGmNCXFAWck--


From nobody Tue Jul 19 01:14:27 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A03D412DC14 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 01:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 AZMadQ4jQH1y for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 01:14:20 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBA6012DC0F for <homenet@ietf.org>; Tue, 19 Jul 2016 01:14:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=tW1541CGfijoWLvDiwrwx+P6wPzuovp5zV9hDykbhls=; b=SUR1uf2exAqhISuzNphIttXMJvaxyhKRi3VDzneBd/WTvcnX7FvsexBly6tS3FScPfHqC9ud++hi0f7cqVAe5seocL8LIbbaX8s10JUgLSprrkHgYDpsbuaSUiBT0SCAKFa5AR7wEmf2iFhx7ZtpfF5RK70ltgPm67J1lHiYbPY=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0246.outbound.protection.outlook.com [213.199.154.246]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-65-f3RzLk-3POWu3CqPsnBUpg-1; Tue, 19 Jul 2016 09:14:11 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (TLS) id 15.1.534.14; Tue, 19 Jul 2016 08:14:10 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.019; Tue, 19 Jul 2016 08:14:09 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [homenet] My comment about Ted's naming draft
Thread-Index: AQHR4QK8RKC9rw4lqkudH7cFS+MWtqAerNkAgAAQAgCAAABCgIAACCoAgAAGikiAAJ2IAA==
Date: Tue, 19 Jul 2016 08:14:09 +0000
Message-ID: <EE6DA7CC-78E2-44A4-A4DF-E538B891B87B@jisc.ac.uk>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com> <874m7mh98r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1mPko=oaGfhWP9dZBbu+pWStfUNxwT22sMTCN9vY1RGmw@mail.gmail.com> <CAPt1N1negfEtAHto8_pujgbi53F7Ecb85pboV7hv5ZvpAHvH2g@mail.gmail.com> <CAPt1N1kyB_tWKEp4tSQLocSN4aAQnsBnL6_cU0X4y4gSvm+1fQ@mail.gmail.com>
In-Reply-To: <CAPt1N1kyB_tWKEp4tSQLocSN4aAQnsBnL6_cU0X4y4gSvm+1fQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.155.0]
x-ms-office365-filtering-correlation-id: b01724ad-88e5-4b98-1b30-08d3afaca95c
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 20:08vb2XCZIhvPyJbtCbt29D9bje6WAZp/pVXkT9TnmLExwCoejNhzxmHWM+k2Zm0iXhCK5bCnDD/ijM4Yp4NOJX0UqDVlPg7aL8aGWZdbPag4lahdhFD5sC1h76xJQDbRkCfKQAaObZCs/w4AFtkZ8rRbC335k4SBr+eys2yUe/w=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB454422A9E26FC96F7B47212D6370@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 000800954F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(189002)(24454002)(199003)(50226002)(86362001)(66066001)(8676002)(83716003)(5002640100001)(81156014)(36756003)(87936001)(81166006)(10400500002)(106116001)(105586002)(106356001)(101416001)(8936002)(57306001)(122556002)(3846002)(6116002)(102836003)(15975445007)(3280700002)(77096005)(16236675004)(92566002)(586003)(68736007)(2950100001)(50986999)(97736004)(33656002)(4326007)(3660700001)(110136002)(189998001)(74482002)(82746002)(7736002)(2900100001)(7846002)(76176999)(19580395003)(19580405001)(93886004)(2906002)(7756004)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2016 08:14:09.7471 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
X-MC-Unique: f3RzLk-3POWu3CqPsnBUpg-1
Content-Type: multipart/alternative; boundary="_000_EE6DA7CC78E244A4A4DFE538B891B87Bjiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/FQxppJWOknm-cKaRnoSOg06W9Uc>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 08:14:23 -0000

--_000_EE6DA7CC78E244A4A4DFE538B891B87Bjiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Hi,

On 18 Jul 2016, at 23:51, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.c=
om>> wrote:


I think it's should in the sense that there may be done reason not to do it=
 on some case and we don't want to preclude that because there is no protoc=
ol reason to do so, but we expect that it will be allocated unless there is=
 some good reason. We talked about this at length a couple of years ago and=
 captured the intent in the architecture doc, but maybe not in enough detai=
l?


The problem with making statements in RFC7368 was doing so while keeping co=
nsensus; the more detail you add, the harder it is to keep consensus. There=
 was consensus on =93should=94, and some rationale was given.

Of course since then we=92ve found that omitting detail (like more specific=
s on the routing protocol, in particular) did come back to bite us later in=
 that we really only deferred the decision.

Also, RFC7368 does not use RFC2119 language.

Tim

On Jul 18, 2016 23:28, "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr<=
mailto:jch@pps.univ-paris-diderot.fr>> wrote:
> Why wouldn't you allocate one?

I would.  ULAs are a goodness.  Probably.  I'm planning to add ULA
generation to shncpd at some future date, and perhaps even enable it by
default.

The question is about the level of MUSTiness.  I only see two reasonable
possibilities:

  1. ULA is SHOULD, and we cannot rely on their existence;
  2. ULA is MUST, which puts an additional requirement on implementations,
     but allows us to rely on their existence except during reconvergence.

No compromise between these two positions is possible.  It is not reasonabl=
e
to say that ULA is SHOULD while simultaneously relying on their existence,
which is what we're apparently trying to do.

-- Juliusz

_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet


--_000_EE6DA7CC78E244A4A4DFE538B891B87Bjiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <BD775DF9FCA8A24CA64CA1E2CF0D627A@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Hi,<br class=3D"">
<div class=3D"">
<div class=3D""><br class=3D"">
</div>
</div>
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 18 Jul 2016, at 23:51, Ted Lemon &lt;<a href=3D"mailto:m=
ellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<p dir=3D"ltr" class=3D"">I think it's should in the sense that there may b=
e done reason not to do it on some case and we don't want to preclude that =
because there is no protocol reason to do so, but we expect that it will be=
 allocated unless there is some good
 reason. We talked about this at length a couple of years ago and captured =
the intent in the architecture doc, but maybe not in enough detail?</p>
<div class=3D""><br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
The problem with making statements in RFC7368 was doing so while keeping co=
nsensus; the more detail you add, the harder it is to keep consensus. There=
 was consensus on =93should=94, and some rationale was given.</div>
<div><br class=3D"">
</div>
<div>Of course since then we=92ve found that omitting detail (like more spe=
cifics on the routing protocol, in particular) did come back to bite us lat=
er in that we really only deferred the decision.</div>
<div><br class=3D"">
</div>
<div>Also, RFC7368 does not use RFC2119 language.</div>
<div><br class=3D"">
Tim<br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Jul 18, 2016 23:28, &quot;Juliusz Chroboczek&=
quot; &lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" class=3D"">jch@p=
ps.univ-paris-diderot.fr</a>&gt; wrote:<br type=3D"attribution" class=3D"">
<blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div class=3D"quoted-text">&gt; Why wouldn't you allocate one?<br class=3D"=
">
<br class=3D"">
</div>
I would.&nbsp; ULAs are a goodness.&nbsp; Probably.&nbsp; I'm planning to a=
dd ULA<br class=3D"">
generation to shncpd at some future date, and perhaps even enable it by<br =
class=3D"">
default.<br class=3D"">
<br class=3D"">
The question is about the level of MUSTiness.&nbsp; I only see two reasonab=
le<br class=3D"">
possibilities:<br class=3D"">
<br class=3D"">
&nbsp; 1. ULA is SHOULD, and we cannot rely on their existence;<br class=3D=
"">
&nbsp; 2. ULA is MUST, which puts an additional requirement on implementati=
ons,<br class=3D"">
&nbsp; &nbsp; &nbsp;but allows us to rely on their existence except during =
reconvergence.<br class=3D"">
<br class=3D"">
No compromise between these two positions is possible.&nbsp; It is not reas=
onable<br class=3D"">
to say that ULA is SHOULD while simultaneously relying on their existence,<=
br class=3D"">
which is what we're apparently trying to do.<br class=3D"">
<font color=3D"#888888" class=3D""><br class=3D"">
-- Juliusz<br class=3D"">
</font></blockquote>
</div>
<br class=3D"">
</div>
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br clas=
s=3D"">
https://www.ietf.org/mailman/listinfo/homenet<br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</body>
</html>

--_000_EE6DA7CC78E244A4A4DFE538B891B87Bjiscacuk_--


From nobody Tue Jul 19 01:22:05 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C37912B02D for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 01:22:04 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 zbXlYiZlTBMS for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 01:22:02 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BC1112D162 for <homenet@ietf.org>; Tue, 19 Jul 2016 01:21:59 -0700 (PDT)
Received: from dhcp-b14e.meeting.ietf.org ([31.133.177.78]:58121) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bPQHt-0003TB-Cy (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Tue, 19 Jul 2016 09:21:57 +0100
To: homenet@ietf.org
References: <8737n6h6z0.wl-jch@pps.univ-paris-diderot.fr>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <2bc6135e-3322-97a5-426c-88c4040c2513@bellis.me.uk>
Date: Tue, 19 Jul 2016 10:21:58 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <8737n6h6z0.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/8Lkq-iVy7dnLlYp9sP93tqDWc68>
Subject: Re: [homenet] More about lossy links and yo-yo neighbours
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 08:22:04 -0000

On 19/07/2016 01:17, Juliusz Chroboczek wrote:
> I therefore cannot blame the chairs for forcing me to work with an
> older version of my talk which didn't contain the explanation -- oh,
> what the heck, yes, I can ;-) Please bear with me while I lecture a
> little.

The correct slides are available at:

<https://www.ietf.org/proceedings/96/slides/slides-96-homenet-1.pdf>

FWIW, I did get Juliusz's new slides, but managed to re-upload the
original set! :p

Ray


From nobody Tue Jul 19 02:08:57 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C00FF12DED4 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:08:56 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 fxaePL2g5xzp for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:08:50 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E67312DDAD for <homenet@ietf.org>; Tue, 19 Jul 2016 02:05:39 -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/56228) with ESMTP id u6J95bGZ001418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Jul 2016 11:05:37 +0200
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/56228) with ESMTP id u6J95ZtB026538; Tue, 19 Jul 2016 11:05:37 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5C5B361FA2; Tue, 19 Jul 2016 11:05:35 +0200 (CEST)
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 ZTbzOW-T7NHB; Tue, 19 Jul 2016 11:05:34 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1059661FAA; Tue, 19 Jul 2016 11:05:34 +0200 (CEST)
Date: Tue, 19 Jul 2016 11:05:31 +0200
Message-ID: <8760s2atgk.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, 19 Jul 2016 11:05:37 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 19 Jul 2016 11:05:37 +0200 (CEST)
X-Miltered: at korolev with ID 578DED61.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578DED5F.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578DED61.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: 578DED5F.003 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 : 578DED61.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578DED5F.003 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: <https://mailarchive.ietf.org/arch/msg/homenet/0LEZB9-z0oy_GQJPKRBmgeisoqU>
Cc: Ted Lemon <mellon@fugue.com>
Subject: [homenet] About ULAs in Ted's draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 09:08:57 -0000

Ted,

I've read the draft again, and I think that there's only one place where
you rely on having a ULA.  So I'd suggest:

  Section 3.3 point 2, replace "the homenet's ULA prefix" with "the
  homenet's ULA prefix (if any)".

  In Section 5.5, change "Homenets have at least one ULA prefix" with
  "Homenets usually have exactly one non-deprecated ULA prefix".

The only place where you actually rely on a ULA is Section 4.7, paragraph
2.  I have no idea what to do about that.

Alternatives to this include making ULA generation a MUST in the HNCP RFC,
or making naming support a SHOULD that depends on having a ULA.  I hold
a mild distaste for either of these possibilities, but I suppose I could
live with either.

-- Juliusz


From nobody Tue Jul 19 02:32:13 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A289412DFD3 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:32:10 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 6B6SBQK1gOUy for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:32:02 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 529A512DE06 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:22:13 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id l69so8405915lfg.1 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=j5AR7M66vMJRtbNuQQTHg6fuITq8+dP42cYrxk32HCk=; b=YwOKnm6WnoVgC75Zi7UgSHNUU3GQ4nbM55RvVnn/QTqbzaBhjCQ2FYFuUaP1CaDbZc o9oxs2JGBUd5TuJNh9/AefnktOjypZw/1e/BeXSDUY4nvW+IBdN/Ypewkz3Ik0ym6yaj tNS9RkPRYHK/kKOZ+JP23tVhKQEpk0E7HUeD2YVViRpkWdPFS2YNLMiDAuYMTHfkjisV +dUs+P3NgR3wJ+ou2SuwyWwwVnqV2xTTe0VfhiSp88CYrspdRRvWQ1A0q1pg0bhUFF8t ODtTyFEC/gvp33vlUBxfYszif276uJ4eqhhiIqvRm/W3QhX1D1RqlzDBFvJVPZVGT0QT 52iA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=j5AR7M66vMJRtbNuQQTHg6fuITq8+dP42cYrxk32HCk=; b=eGdo7mMofSx8UoW9klzJhglWefUji0mYQodnEemx7DTRGgiLXzKrpTJZ89xm8CWUcq 9Hqid1iqVQZzGjabZlHdXrNb5qH/vtSRb5alO+eOWvqs3SAOB0NESyhcr5Ho2zrxw0fk TISMqoCFehd2TsS0gEA6Urbg/cjFYCHvOF1K4ltIS4mz4gpXZM6gZ3aWyJ+gWy6CBZhP PjT4yVDuwxS8uesiB5xjXebMSeJO+O7JC9UB0Yisn4R++PJqhxiFLXgOVZ7/QXFeMUHb l+rHn27JVwyIHEmSth6YJqDIzPWUb13LoYzkoYcp0s8r1SOgv3rh89OBQ9IAG8OiL807 dvKw==
X-Gm-Message-State: ALyK8tIczN8rVaovqxyOWxZb3k1igeQCHfXYC+JPFM+jYygzl6pNhqNZmU/R75VLrb5o1+1ffMYNNqCOGJ4C1w==
MIME-Version: 1.0
X-Received: by 10.25.42.207 with SMTP id q198mr14892911lfq.181.1468920131436;  Tue, 19 Jul 2016 02:22:11 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 02:22:11 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 02:22:11 -0700 (PDT)
In-Reply-To: <8760s2atgk.wl-jch@pps.univ-paris-diderot.fr>
References: <8760s2atgk.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 19 Jul 2016 11:22:11 +0200
Message-ID: <CAPt1N1ksmmDDtVkspHDjzGXXCWkiLCdbpfiP6MaaQYpfjO5iqg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11411dbaa35ac60537f99eff
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/efBF3cBX7ge1fejASddiUPeHlRA>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] About ULAs in Ted's draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 09:32:11 -0000

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

Yeah, I think this is the right approach. I think a homenet with no ULA is
broken, but I don't want to insist. Things just get a lot more brittle if
you don't have ULAs.

On Jul 19, 2016 11:05, "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr>
wrote:

> Ted,
>
> I've read the draft again, and I think that there's only one place where
> you rely on having a ULA.  So I'd suggest:
>
>   Section 3.3 point 2, replace "the homenet's ULA prefix" with "the
>   homenet's ULA prefix (if any)".
>
>   In Section 5.5, change "Homenets have at least one ULA prefix" with
>   "Homenets usually have exactly one non-deprecated ULA prefix".
>
> The only place where you actually rely on a ULA is Section 4.7, paragraph
> 2.  I have no idea what to do about that.
>
> Alternatives to this include making ULA generation a MUST in the HNCP RFC,
> or making naming support a SHOULD that depends on having a ULA.  I hold
> a mild distaste for either of these possibilities, but I suppose I could
> live with either.
>
> -- Juliusz
>

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

<p dir=3D"ltr">Yeah, I think this is the right approach. I think a homenet =
with no ULA is broken, but I don&#39;t want to insist. Things just get a lo=
t more brittle if you don&#39;t have ULAs. </p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 19, 2016 1=
1:05, &quot;Juliusz Chroboczek&quot; &lt;<a href=3D"mailto:jch@pps.univ-par=
is-diderot.fr">jch@pps.univ-paris-diderot.fr</a>&gt; wrote:<br type=3D"attr=
ibution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">Ted,<br>
<br>
I&#39;ve read the draft again, and I think that there&#39;s only one place =
where<br>
you rely on having a ULA.=C2=A0 So I&#39;d suggest:<br>
<br>
=C2=A0 Section 3.3 point 2, replace &quot;the homenet&#39;s ULA prefix&quot=
; with &quot;the<br>
=C2=A0 homenet&#39;s ULA prefix (if any)&quot;.<br>
<br>
=C2=A0 In Section 5.5, change &quot;Homenets have at least one ULA prefix&q=
uot; with<br>
=C2=A0 &quot;Homenets usually have exactly one non-deprecated ULA prefix&qu=
ot;.<br>
<br>
The only place where you actually rely on a ULA is Section 4.7, paragraph<b=
r>
2.=C2=A0 I have no idea what to do about that.<br>
<br>
Alternatives to this include making ULA generation a MUST in the HNCP RFC,<=
br>
or making naming support a SHOULD that depends on having a ULA.=C2=A0 I hol=
d<br>
a mild distaste for either of these possibilities, but I suppose I could<br=
>
live with either.<br>
<br>
-- Juliusz<br>
</blockquote></div></div>

--001a11411dbaa35ac60537f99eff--


From nobody Tue Jul 19 02:44:19 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A864912DF84 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 fVvNR0lLuXaD for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:44:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BAD912DFA7 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:38:09 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 86546203AB; Tue, 19 Jul 2016 05:47:35 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4881F638D1; Tue, 19 Jul 2016 05:38:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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, 19 Jul 2016 05:38:08 -0400
Message-ID: <19139.1468921088@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pS37VYae1PYHT3Em0AqPNO6Z-cQ>
Cc: homenet@ietf.org, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 09:44:17 -0000

--=-=-=
Content-Type: text/plain


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    >>> (4) Is there WG consensus on requiring a ULA?

    >> I believe that this is.  a) it's in rfc7084 (so they are there even
    >> before homenet existed) b) it's in rfc7368 (it's in our architecture)

    > RFC 7084 Section 4.3 says:

    >     The IPv6 CE router SHOULD be capable of generating a ULA prefix
    > [RFC4193].

    > RFC 7368 Section 2.4 says:

    >     A home network running IPv6 should deploy ULAs

    > RFC 7788 Section 6.5 says:

    >     An HNCP router SHOULD create a ULA prefix if there is no other IPv6
    > prefix with a preferred time greater than 0 in the network.  It MAY
    > also do so if there are other delegated IPv6 prefixes

    > I do not believe that there is WG consensus that ULA generation should
    > be a MUST.

I don't think that Ted's document demands that there be a ULA.
Rather, I think that it demands that there is a prefix that can be used for
internal services.  That's a ULA on 99.9% of networks, the 0.1% being the 19
people on this list with their own RIR allocation.

If you have a situation where you have some other stable prefix that you can
use for your homenet, and you configure your routers to announce that rather
than a ULA, then you are in the edge case between a MUST and SHOULD.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV430/YCLcPvd0N1lAQIE2Af/Ucs33k6KmSi+9fsOLctmzcOSYegOuKiF
m9T+UBoB6mn1e6LRbqszcSnJeAbL6KN5kTB2w83t0cZvU76B6HfIakIXehTME/hH
5k72s2rUOptsIHJ7GfiBcc8asdu+KQLFVA1WToAU/0tIUuc5dN7YsbGlBvNHaWr1
63f70YSp8BnPIadNTz1R4Bk/QYBVG/EDd/DJK90SWOjKuaGiu/9ryTkIcAnBbdFZ
7J+0FMnvyLRqYxkqYa17XQ3C9As50I87yl34eErMLKYR9Iwd94DFJuWCyX+5P91l
Tb7Z8cgZ5Dcz2k6YWOKRB2sqIKoq/Wt77c9epWLxGGCzllq6z24uUA==
=EDON
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul 19 02:45:39 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDF312DDF8 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 XCCPhAjE0wSY for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:45:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F72712D0F7 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:39:40 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DAC5E203AB; Tue, 19 Jul 2016 05:49:06 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A32B7638D1; Tue, 19 Jul 2016 05:39:39 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <874m7mh98r.wl-jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n4SnQwPG25T3mqZWy6sRLwuAwj43p4tbC+P6otB9MYPQ@mail.gmail.com> <874m7mh98r.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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, 19 Jul 2016 05:39:39 -0400
Message-ID: <19511.1468921179@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/7BiFf8pDjkmXd5_oQmHA1kWGdrs>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 09:45:38 -0000

--=-=-=
Content-Type: text/plain


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    > I would.  ULAs are a goodness.  Probably.  I'm planning to add ULA
    > generation to shncpd at some future date, and perhaps even enable it by
    > default.

    > The question is about the level of MUSTiness.  I only see two reasonable
    > possibilities:

    > 1. ULA is SHOULD, and we cannot rely on their existence;
    > 2. ULA is MUST, which puts an additional requirement on implementations,
    > but allows us to rely on their existence except during reconvergence.

I think that you are parsing "SHOULD" in a way closer to "MAY".
SHOULD is really quite a strong statement.  Someone violating a SHOULD does
so with the knowledge that they may break something else.


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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV431WYCLcPvd0N1lAQJSOgf+KZ+rRJLQo2ongLS3ksrA/z9JLMF8QhCN
sGNoACythJK6yP6UfmGw3W29MlHuwh+qUkJLU7kMUIkMGrHFK07PlglNxkWz6MN0
m4SJc1+3nAHtWq+QqCDNqJADEbpRWMZ2EPpBhV+1CumT6DFM5UdQcNqN7JlM6VsC
qOiHCLwWFqGETYOISmLbdNB2mc1cmiIkCn8wWWC4SXJSj/XHj3jAg/HOQTS1lDQ4
IZFXrlZiglODCssZjyNh8sSj0zHod7YPB3JJ3K1OKJmred8vfguYa1SW8XZgeLMx
C/CB9Qxc19o3clkCnd+saVI18T9qgBW8+rpDCLOzbeDzVc/b17ECgA==
=b2JA
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul 19 02:49:24 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C442612E033 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:49:21 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 hPGpewnYbMLW for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 02:49:19 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457D912DEB4 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:43:38 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id f93so8918923lfi.2 for <homenet@ietf.org>; Tue, 19 Jul 2016 02:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=TiZrBYFvvYkTwVjhctK1zNdfZxnPCvZKxNhqRxAxNd4=; b=nFoxfXBT2LW3fLolJw6x4mygSX35QUHzrhVULXZR6097zAYfoKNCq+LGjLD64/niQL Xs6b71kX2U60oi71bMxgM7AF94lGBXPIVGg3cOOWc98tWO1jDqzG4LDn0RVhuQtud0FX sGsNvxqZIlvTGCOm0AmmsLyZEl/wD02aT1z3RKbrZ5vZqpGfGP1ajhOKLAVAM95/FbjN gPPRh94EETpBe2wgiI7VHnlQtl0Pkl92QE9gu4pGvBZoHqeJnIhZNtdgZZ1FxtzquAd8 SNP20V2GdpUha/bo6UOXTK8ii+13mB1Mp/Vr19EGP3qwr584tcjdQecbQw0YIzXuaqTC 5aeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=TiZrBYFvvYkTwVjhctK1zNdfZxnPCvZKxNhqRxAxNd4=; b=I2ZE6QETlJcbluehrBqOlGkm1q1Fn+UlL4wJGgea+qunYM7W10NN2NR7NbOjZPq/pU zyo18bLgnIL67WFE21MEFl5IZ364jSv37f8Qaz7P7zz2xj3O4x3VTQSzg+2M2rJk5Opt 7Bre2B5hpG925UUoRerSFY2BmGDO3mVsSVXa4jVlDz9mbAKOccTS3KNi/+f5VwDmlhOI k9E4Zgr0sjH0xJ+iof4dBucdNViy5TUp2Efdxjx3goVkNQM6VfO76qvUincGJfjKFsmx ZPVYgPy3pBGGzK771TS4t46+4TypEXtyDHEq0eLvNbbjtbEPKyTZ0QSJM7sNG5gGRdxd rCbg==
X-Gm-Message-State: ALyK8tIkgS/h69zwvU/buxh761xg19ykFg8tmteT3AsBFHTVutugUftk+t1W83QvnI49RxfRSQT1zJlm2motnQ==
MIME-Version: 1.0
X-Received: by 10.46.5.196 with SMTP id 187mr14351604ljf.13.1468921416469; Tue, 19 Jul 2016 02:43:36 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 02:43:36 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 02:43:36 -0700 (PDT)
In-Reply-To: <19139.1468921088@obiwan.sandelman.ca>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <17161.1468875638@obiwan.sandelman.ca> <87lh0yzk0r.wl-jch@pps.univ-paris-diderot.fr> <19139.1468921088@obiwan.sandelman.ca>
Date: Tue, 19 Jul 2016 11:43:36 +0200
Message-ID: <CAPt1N1=7i8OGR632yfZwR3A5OBi8-NuK6Arkf3k1tSWC+79VRg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a114a6bea3b61920537f9eba8
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/cgNkMMzgubA0AfI_xLYOnlsCn7g>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 09:49:22 -0000

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

Yes, this is a really good clarification. Thanks!

On Jul 19, 2016 11:38, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:

>
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>     >>> (4) Is there WG consensus on requiring a ULA?
>
>     >> I believe that this is.  a) it's in rfc7084 (so they are there even
>     >> before homenet existed) b) it's in rfc7368 (it's in our
> architecture)
>
>     > RFC 7084 Section 4.3 says:
>
>     >     The IPv6 CE router SHOULD be capable of generating a ULA prefix
>     > [RFC4193].
>
>     > RFC 7368 Section 2.4 says:
>
>     >     A home network running IPv6 should deploy ULAs
>
>     > RFC 7788 Section 6.5 says:
>
>     >     An HNCP router SHOULD create a ULA prefix if there is no other
> IPv6
>     > prefix with a preferred time greater than 0 in the network.  It MAY
>     > also do so if there are other delegated IPv6 prefixes
>
>     > I do not believe that there is WG consensus that ULA generation
> should
>     > be a MUST.
>
> I don't think that Ted's document demands that there be a ULA.
> Rather, I think that it demands that there is a prefix that can be used for
> internal services.  That's a ULA on 99.9% of networks, the 0.1% being the
> 19
> people on this list with their own RIR allocation.
>
> If you have a situation where you have some other stable prefix that you
> can
> use for your homenet, and you configure your routers to announce that
> rather
> than a ULA, then you are in the edge case between a MUST and SHOULD.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

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

<p dir=3D"ltr">Yes, this is a really good clarification. Thanks!</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 19, 2016 1=
1:38, &quot;Michael Richardson&quot; &lt;<a href=3D"mailto:mcr%2Bietf@sande=
lman.ca">mcr+ietf@sandelman.ca</a>&gt; wrote:<br type=3D"attribution"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><br>
Juliusz Chroboczek &lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr">jch=
@pps.univ-paris-diderot.fr</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt;&gt;&gt; (4) Is there WG consensus on requiring a ULA?<br=
>
<br>
=C2=A0 =C2=A0 &gt;&gt; I believe that this is.=C2=A0 a) it&#39;s in rfc7084=
 (so they are there even<br>
=C2=A0 =C2=A0 &gt;&gt; before homenet existed) b) it&#39;s in rfc7368 (it&#=
39;s in our architecture)<br>
<br>
=C2=A0 =C2=A0 &gt; RFC 7084 Section 4.3 says:<br>
<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0The IPv6 CE router SHOULD be capable =
of generating a ULA prefix<br>
=C2=A0 =C2=A0 &gt; [RFC4193].<br>
<br>
=C2=A0 =C2=A0 &gt; RFC 7368 Section 2.4 says:<br>
<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0A home network running IPv6 should de=
ploy ULAs<br>
<br>
=C2=A0 =C2=A0 &gt; RFC 7788 Section 6.5 says:<br>
<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0An HNCP router SHOULD create a ULA pr=
efix if there is no other IPv6<br>
=C2=A0 =C2=A0 &gt; prefix with a preferred time greater than 0 in the netwo=
rk.=C2=A0 It MAY<br>
=C2=A0 =C2=A0 &gt; also do so if there are other delegated IPv6 prefixes<br=
>
<br>
=C2=A0 =C2=A0 &gt; I do not believe that there is WG consensus that ULA gen=
eration should<br>
=C2=A0 =C2=A0 &gt; be a MUST.<br>
<br>
I don&#39;t think that Ted&#39;s document demands that there be a ULA.<br>
Rather, I think that it demands that there is a prefix that can be used for=
<br>
internal services.=C2=A0 That&#39;s a ULA on 99.9% of networks, the 0.1% be=
ing the 19<br>
people on this list with their own RIR allocation.<br>
<br>
If you have a situation where you have some other stable prefix that you ca=
n<br>
use for your homenet, and you configure your routers to announce that rathe=
r<br>
than a ULA, then you are in the edge case between a MUST and SHOULD.<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div></div>

--001a114a6bea3b61920537f9eba8--


From nobody Tue Jul 19 03:56:48 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 939C912D0B2 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 03:56:46 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 aGa04eX-911h for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 03:56:44 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D47D12B057 for <homenet@ietf.org>; Tue, 19 Jul 2016 03:56:44 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id f93so10621497lfi.2 for <homenet@ietf.org>; Tue, 19 Jul 2016 03:56:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=jQnoOvMMA6YMCAZ7MwS2D4ohhR1BLixUPX/nU9UszRQ=; b=Hmb+Wh1CoM134zjFm6xVVM/ixgYOVwamrkQQqqWBI9QAXcHqN6OKQ14OMUqNkkjIXp jkiJORxPDYrvsHdKGUM7+UFpMIR2B/9tcon+uXmMzgt7G43NddL4j+24GC56MIWAEyym LX1Tcfi64LXQjWJbVSx8BJF7Aq3aB0NIPOXjVBpPpHkqE5aFPsCkfstlIg1A6DEljBi7 8s2g4DNrQGBYB3eX1I2vNcWwg40bM4lCXsPZjNFjcX8OEKujvdLmgDrrhbfSJ0j/CLyh f0qJqM4s4GkVDdKtKmMBNjTMQiixzNY7nHQ5ywUB2zSu0W2rL4WoGPs3G0GNNQlzdotp QHgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jQnoOvMMA6YMCAZ7MwS2D4ohhR1BLixUPX/nU9UszRQ=; b=LmfDrW6ZJBEjA4Ud9FmFJlhkD9zC+eQ27YZVw0qNvYnYieSjDPJxYvK0GRku4XLfF4 uykqTcQQQz1fqdIBU6xQH7QJjUytqIc9VnBTAIdFSitzjXCrsfD7Y9rmLQBaVI7cwuzi nrfVQ83CcKsMjPGNb08OZ2MwfZae0BnfxUCpazRmtxX6DEA6aPk/CVBZRFt9wefI1B/4 u5WVNcw4mQT+7R171mSNV71r37hZUb9/6RbCGiWxbFq3O6dfh0SAwFW79rNimCVaZVRA J1q9CV2ozEAo4ekjL/N0T/h0ogfukEvNs4heYJzNYx9EJNv1P5aDclfnWR84MtcAn+B+ RTJQ==
X-Gm-Message-State: ALyK8tL2v2Oy2dNzUe8zAGwa1WrH3BvBi0Ie6FmhXGyY3Stf6BaqhQdtd80gvh5rJ58txDRvRNRk7MpcLasMdA==
X-Received: by 10.25.152.135 with SMTP id a129mr15032295lfe.226.1468925802593;  Tue, 19 Jul 2016 03:56:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 03:56:02 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 19 Jul 2016 12:56:02 +0200
Message-ID: <CAPt1N1kZA23yc0=VG8qKA_MDj9dgb7jOUYdSsY3HVVUuuU+JVQ@mail.gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a114035e2aa51310537faf0ed
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ZxMxFMmX4kOOWbmUFfytoFZI0L4>
Subject: [homenet] Attempt to summarize the value of various steps of 7788 fix
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 10:56:46 -0000

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

I'm writing this because I think there may still be a lack of clarity on
why various people are insisting on various things, and we can't just do
something simple.   I don't think that the reasons for each of the things
that have been proposed is clear to everybody--I hadn't really thought
about the reason I'm giving for Step 1 until just now, but I suspect this
reason is clear in the minds of Terry and various other people in
leadership roles.   I would appreciate being corrected if I have failed to
express it correctly.

Step 1: officially get ".home" out of 7788 by updating it
Reason: right now if someone releases software with ".home" in it, it's the
IETF's fault, because the IETF is explicitly recommending this.   This is
why "do nothing" isn't an option.

Step 2: recommend something else and get it through 6761 process
Reason: people will still use ".home" and blame the IETF if they get in
trouble, because we haven't said to use anything new.

Step 3: explain how this stuff works.
Reason: right now our story for how naming works on homenets is sketchy,
and I would argue is not likely to provide a happy user experience.
Existing implementations by participants work and interoperate, but it is
not clear that this is a consequence of a good spec, or whether it's
because the implementors are talking to each other.

We cannot assume that this happy situation will continue as router vendors
who are not participating directly in the discussion begin to produce
homenet routers.   I think this isn't likely to happen soon anyway, so we
have time to address this problem, but we need to start working on that
now, not later.   It is not the case that what we have now is good enough.

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

<div dir=3D"ltr"><div>I&#39;m writing this because I think there may still =
be a lack of clarity on why various people are insisting on various things,=
 and we can&#39;t just do something simple. =C2=A0 I don&#39;t think that t=
he reasons for each of the things that have been proposed is clear to every=
body--I hadn&#39;t really thought about the reason I&#39;m giving for Step =
1 until just now, but I suspect this reason is clear in the minds of Terry =
and various other people in leadership roles. =C2=A0 I would appreciate bei=
ng corrected if I have failed to express it correctly.</div><div><br></div>=
Step 1: officially get &quot;.home&quot; out of 7788 by updating it<div>Rea=
son: right now if someone releases software with &quot;.home&quot; in it, i=
t&#39;s the IETF&#39;s fault, because the IETF is explicitly recommending t=
his. =C2=A0 This is why &quot;do nothing&quot; isn&#39;t an option.</div><d=
iv><br></div><div>Step 2: recommend something else and get it through 6761 =
process</div><div>Reason: people will still use &quot;.home&quot; and blame=
 the IETF if they get in trouble, because we haven&#39;t said to use anythi=
ng new.</div><div><br></div><div>Step 3: explain how this stuff works.</div=
><div>Reason: right now our story for how naming works on homenets is sketc=
hy, and I would argue is not likely to provide a happy user experience. =C2=
=A0 Existing implementations by participants work and interoperate, but it =
is not clear that this is a consequence of a good spec, or whether it&#39;s=
 because the implementors are talking to each other.</div><div><br></div><d=
iv>We cannot assume that this happy situation will continue as router vendo=
rs who are not participating directly in the discussion begin to produce ho=
menet routers. =C2=A0 I think this isn&#39;t likely to happen soon anyway, =
so we have time to address this problem, but we need to start working on th=
at now, not later. =C2=A0 It is not the case that what we have now is good =
enough.</div><div><br></div></div>

--001a114035e2aa51310537faf0ed--


From nobody Tue Jul 19 05:24:16 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807C712D61A for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 05:24:15 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 ht3-rg8PH-o4 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 05:24:13 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E933F12D626 for <homenet@ietf.org>; Tue, 19 Jul 2016 05:24:12 -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/56228) with ESMTP id u6JCOAmP002900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Jul 2016 14:24:10 +0200
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/56228) with ESMTP id u6JCO93Y003619; Tue, 19 Jul 2016 14:24:10 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9293361FA2; Tue, 19 Jul 2016 14:24:09 +0200 (CEST)
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 UzEiPKMvIY_U; Tue, 19 Jul 2016 14:24:08 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id EB27B61FA3; Tue, 19 Jul 2016 14:24:05 +0200 (CEST)
Date: Tue, 19 Jul 2016 14:24:02 +0200
Message-ID: <87a8hd4xzx.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1kZA23yc0=VG8qKA_MDj9dgb7jOUYdSsY3HVVUuuU+JVQ@mail.gmail.com>
References: <CAPt1N1kZA23yc0=VG8qKA_MDj9dgb7jOUYdSsY3HVVUuuU+JVQ@mail.gmail.com>
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, 19 Jul 2016 14:24:11 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 19 Jul 2016 14:24:10 +0200 (CEST)
X-Miltered: at korolev with ID 578E1BEA.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578E1BE9.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578E1BEA.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: 578E1BE9.002 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 : 578E1BEA.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578E1BE9.002 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: <https://mailarchive.ietf.org/arch/msg/homenet/4AhcwIDVcFNAcdXVw-a8qwvI0Xw>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] Attempt to summarize the value of various steps of 7788	fix
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 12:24:15 -0000

> Existing implementations by participants work and interoperate,

Currently, shncpd doesn't do any naming at all except for pushing the
addresses of upstream DNS resolvers to clients over RA and DHCPv4.  You
will find the exact status of shncpd at the bottom of

  https://www.irif.univ-paris-diderot.fr/~jch/software/homenet/shncpd.html

-- Juliusz


From avri@doria.org  Mon Jul 18 07:50:30 2016
Return-Path: <avri@doria.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BAE712DEE3 for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 7ZOGpejH1cZh for <homenet@ietfa.amsl.com>; Mon, 18 Jul 2016 07:50:28 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0128.hostedemail.com [216.40.44.128]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCA7912E201 for <homenet@ietf.org>; Mon, 18 Jul 2016 07:22:36 -0700 (PDT)
Received: from filter.hostedemail.com (unknown [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id 447BA9ED95 for <homenet@ietf.org>; Mon, 18 Jul 2016 14:22:35 +0000 (UTC)
X-Session-Marker: 6176726940646F7269612E6F7267
X-Spam-Summary: 2, -10, 0, , d41d8cd98f00b204, avri@doria.org, :, RULES_HIT:41:152:355:379:599:800:960:962:967:973:988:989:1189:1221:1260:1313:1314:1345:1381:1394:1395:1436:1437:1516:1517:1518:1535:1542:1575:1588:1589:1592:1594:1711:1730:1776:1792:2525:2528:2553:2561:2564:2569:2682:2685:2689:2692:2859:2895:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3353:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4860:5007:6117:6119:6120:6674:6691:6703:7576:7652:7875:7901:7903:7974:8603:9010:9025:9545:10004:10400:10450:10455:10848:11232:11658:11783:11914:12043:12291:12379:12438:12517:12519:12555:12683:13095:13139:13149:13161:13229:13230:13436:13846:13891:14095:14181:14721:19904:19999:21080:21324:21325:21401:21433:30012:30022:30029:30054:30060:30063:30070:30090, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:2, LUA_SUMMARY:none
X-HE-Tag: salt13_6d77d08e6d432
X-Filterd-Recvd-Size: 5908
Received: from [31.133.154.161] (dhcp-9aa1.meeting.ietf.org [31.133.154.161]) (Authenticated sender: avri@doria.org) by omf04.hostedemail.com (Postfix) with ESMTPA for <homenet@ietf.org>; Mon, 18 Jul 2016 14:22:32 +0000 (UTC)
Date: Mon, 18 Jul 2016 16:22:29 +0200
Message-ID: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
Importance: normal
From: "avri@acm.org" <avri@doria.org>
To: HOMENET <homenet@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_1195070206386800"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/8BIwSNv5VSV0k2uOwuPuCi9CqFc>
X-Mailman-Approved-At: Tue, 19 Jul 2016 08:55:39 -0700
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 15:33:09 -0000

----_com.samsung.android.email_1195070206386800
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CklDQU5OIG1heSBub3QgaGF2ZSBoYW5kZWQgaXQgb3V0IHlldCwgYW5kIG1heSBiZSBvbiBhIGhv
bGQgYWJvdXQgZG9pbmcgc28sIGJ1dCBtYW55IHN0aWxsIGV4cGVjdCBzb21lIHJlc29sdXRpb24g
dG8gdGhhdCByb2FkIGJsb2NrLiBJIGNlcnRhaW5seSBkby4KTWFraW5nIGFzc3VtcHRpb25zIGFi
b3V0IGljYW5u4oCYcyBmdXR1cmUgYmVoYXZpb3Igb24gdGhpcyBfcG9saWN5XyBpc3N1ZSBpcyBh
IGJhZCBiZXQuClNvbWUgcXVlc3Rpb25zIEkgc3RpbGwgZG8gbm90IHVuZGVyc3RhbmQgdGhlIGFu
c3dlcnMgZm9yCi0gd2h5IGRvIHlvdSBuZWVkIGEgVExEPyBXaHkgd29uJ3QgYSBTTEQgd29yaz8K
LSB3aHkgZG8geW91IG5lZWQgYSB3b3JkIGZyb20gbmF0dXJhbCBsYW5ndWFnZT8gSSBrbm93IG1h
bnkgc3RpbGwgbWFpbnRhaW4gdGhlIG15dGggdGhhdCBpdCBpcyBhIGNvaW5jaWRlbmNlIHdoZW4g
YSBzdHJpbmcgbWF0Y2hlcyBuYXR1cmFsIGxhbmd1YWdlLCBidXQgbWFueSBoYXZlIG90aGVyIHVz
ZWQgZm9yIG5hdHVyYWwgbGFuZ3VhZ2Ugd29yZHMuIEluIGZhY3QgSSBhc3N1bWUgeW91IHBpY2tl
ZCBpdCBiZWNhdXNlIG9mIGl0cyBzaW1pbGFyaXR5IHRvIGEgbmF0dXJhbCB3b3JsZC4gQnV0IHdo
eSBkbyB5b3UgbmVlZCBpdD8KLSB3aGF0IHNvcnQgb2YgaW1wbGVtZW50ZXIgaGFyZCBjb2RlcyBu
YW1lIHN0cmluZ3MgaW4gdGhlaXIgY29kZT8KQXZyaSggY29pbmNpZGVudGFsbHkgQ28tY2hhaXIg
SUNBTk4gbmV3IGdUTEQgU3Vic2VxdWVudCBQcm9jZWR1cmVzIHdvcmtpbmcgZ3JvdXApClNlbnQg
ZnJvbSBteSBULU1vYmlsZSA0RyBMVEUgRGV2aWNlCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2Ug
LS0tLS0tLS1Gcm9tOiBNaWthZWwgQWJyYWhhbXNzb24gPHN3bWlrZUBzd20ucHAuc2U+IERhdGU6
IDcvMTgvMTYgIDE1OjMzICAoR01UKzAxOjAwKSBUbzogVGVycnkgTWFuZGVyc29uIDx0ZXJyeS5t
YW5kZXJzb25AaWNhbm4ub3JnPiBDYzogSE9NRU5FVCA8aG9tZW5ldEBpZXRmLm9yZz4sIFJheSBC
ZWxsaXMgPHJheUBiZWxsaXMubWUudWs+IFN1YmplY3Q6IFJlOiBbaG9tZW5ldF0gUkZDIDc3ODgg
YW5kICIuaG9tZSIgCgpUaGUgb3B0aW9uIDQgbWVudGlvbmVkIHVwZGF0aW5nIFJGQzc3ODguIEl0
J3Mgbm90IGNsZWFyIHRvIG1lIHdoYXQgdGhpcyAKdXBkYXRlIHdvdWxkIGJlLgoKLkhPTUUgaGFz
IG5vdCBiZWVuIGhhbmRlZCBvdXQgYnkgSUNBTk4geWV0LCB3aGF0J3MgdGhlIG9kZHMgdGhhdCBS
RkM2NzYxIApwcm9jZXNzIHJlc2VydmluZyAuSE9NRSBmb3Igc3BlY2lhbCB1c2Ugd291bGQgc3Vj
Y2VlZD8KCi0tIApNaWthZWwgQWJyYWhhbXNzb27CoMKgwqAgZW1haWw6IHN3bWlrZUBzd20ucHAu
c2UKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmhvbWVu
ZXQgbWFpbGluZyBsaXN0CmhvbWVuZXRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9ob21lbmV0Cg==

----_com.samsung.android.email_1195070206386800
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pjxicj48L2Rpdj48ZGl2PklD
QU5OIG1heSBub3QgaGF2ZSBoYW5kZWQgaXQgb3V0IHlldCwgYW5kIG1heSBiZSBvbiBhIGhvbGQg
YWJvdXQgZG9pbmcgc28sIGJ1dCBtYW55IHN0aWxsIGV4cGVjdCBzb21lIHJlc29sdXRpb24gdG8g
dGhhdCByb2FkIGJsb2NrLiBJIGNlcnRhaW5seSBkby48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2
Pk1ha2luZyBhc3N1bXB0aW9ucyBhYm91dCBpY2FubuKAmHMgZnV0dXJlIGJlaGF2aW9yIG9uIHRo
aXMgX3BvbGljeV8gaXNzdWUgaXMgYSBiYWQgYmV0LjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+
U29tZSBxdWVzdGlvbnMgSSBzdGlsbCBkbyBub3QgdW5kZXJzdGFuZCB0aGUgYW5zd2VycyBmb3I8
L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pi0gd2h5IGRvIHlvdSBuZWVkIGEgVExEPyBXaHkgd29u
J3QgYSBTTEQgd29yaz88L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pi0gd2h5IGRvIHlvdSBuZWVk
IGEgd29yZCBmcm9tIG5hdHVyYWwgbGFuZ3VhZ2U/IEkga25vdyBtYW55IHN0aWxsIG1haW50YWlu
IHRoZSBteXRoIHRoYXQgaXQgaXMgYSBjb2luY2lkZW5jZSB3aGVuIGEgc3RyaW5nIG1hdGNoZXMg
bmF0dXJhbCBsYW5ndWFnZSwgYnV0IG1hbnkgaGF2ZSBvdGhlciB1c2VkIGZvciBuYXR1cmFsIGxh
bmd1YWdlIHdvcmRzLiBJbiBmYWN0IEkgYXNzdW1lIHlvdSBwaWNrZWQgaXQgYmVjYXVzZSBvZiBp
dHMgc2ltaWxhcml0eSB0byBhIG5hdHVyYWwgd29ybGQuIEJ1dCB3aHkgZG8geW91IG5lZWQgaXQ/
PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4tIHdoYXQgc29ydCBvZiBpbXBsZW1lbnRlciBoYXJk
IGNvZGVzIG5hbWUgc3RyaW5ncyBpbiB0aGVpciBjb2RlPzwvZGl2PjxkaXY+PGJyPjwvZGl2Pjxk
aXY+QXZyaTwvZGl2PjxkaXY+KCBjb2luY2lkZW50YWxseSBDby1jaGFpciBJQ0FOTiBuZXcgZ1RM
RCBTdWJzZXF1ZW50IFByb2NlZHVyZXMgd29ya2luZyBncm91cCk8L2Rpdj48ZGl2Pjxicj48L2Rp
dj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUiPjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTo4NSU7
Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50IGZyb20gbXkgVC1Nb2JpbGUgNEcgTFRFIERl
dmljZTwvZGl2PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMDAl
O2NvbG9yOiMwMDAwMDAiPjwhLS0gb3JpZ2luYWxNZXNzYWdlIC0tPjxkaXY+LS0tLS0tLS0gT3Jp
Z2luYWwgbWVzc2FnZSAtLS0tLS0tLTwvZGl2PjxkaXY+RnJvbTogTWlrYWVsIEFicmFoYW1zc29u
ICZsdDtzd21pa2VAc3dtLnBwLnNlJmd0OyA8L2Rpdj48ZGl2PkRhdGU6IDcvMTgvMTYgIDE1OjMz
ICAoR01UKzAxOjAwKSA8L2Rpdj48ZGl2PlRvOiBUZXJyeSBNYW5kZXJzb24gJmx0O3RlcnJ5Lm1h
bmRlcnNvbkBpY2Fubi5vcmcmZ3Q7IDwvZGl2PjxkaXY+Q2M6IEhPTUVORVQgJmx0O2hvbWVuZXRA
aWV0Zi5vcmcmZ3Q7LCBSYXkgQmVsbGlzICZsdDtyYXlAYmVsbGlzLm1lLnVrJmd0OyA8L2Rpdj48
ZGl2PlN1YmplY3Q6IFJlOiBbaG9tZW5ldF0gUkZDIDc3ODggYW5kICIuaG9tZSIgPC9kaXY+PGRp
dj48YnI+PC9kaXY+PC9kaXY+PGJyPlRoZSBvcHRpb24gNCBtZW50aW9uZWQgdXBkYXRpbmcgUkZD
Nzc4OC4gSXQncyBub3QgY2xlYXIgdG8gbWUgd2hhdCB0aGlzIDxicj51cGRhdGUgd291bGQgYmUu
PGJyPjxicj4uSE9NRSBoYXMgbm90IGJlZW4gaGFuZGVkIG91dCBieSBJQ0FOTiB5ZXQsIHdoYXQn
cyB0aGUgb2RkcyB0aGF0IFJGQzY3NjEgPGJyPnByb2Nlc3MgcmVzZXJ2aW5nIC5IT01FIGZvciBz
cGVjaWFsIHVzZSB3b3VsZCBzdWNjZWVkPzxicj48YnI+LS0gPGJyPk1pa2FlbCBBYnJhaGFtc3Nv
biZuYnNwOyZuYnNwOyZuYnNwOyBlbWFpbDogc3dtaWtlQHN3bS5wcC5zZTxicj48YnI+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+aG9tZW5ldCBtYWls
aW5nIGxpc3Q8YnI+aG9tZW5ldEBpZXRmLm9yZzxicj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2hvbWVuZXQ8YnI+PC9ib2R5PjwvaHRtbD4=

----_com.samsung.android.email_1195070206386800--


From nobody Tue Jul 19 09:15:12 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8886212D0E5 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 09:15:10 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 KmUkcnU687XN for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 09:15:08 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71D9212D90A for <homenet@ietf.org>; Tue, 19 Jul 2016 09:10:56 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id g62so18601746lfe.3 for <homenet@ietf.org>; Tue, 19 Jul 2016 09:10:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/TNdh7w8TwLZwUsozUPmw11OXbqHYPToXqiNZ9yDv+4=; b=H/QV2OnZI91gcQGHT7K3JIBwgWprSQnEuU8bUqH02GTkxw42eNvEnAhn+Wwc4Mtkua tAbDA6419JljTaOTxTTen/8PfzIWJw1EX64wdgm522QxUt9Fx9ZzUGdvVKoUiTcgYYSL Vuq+a86kgf9oqDZY1n/IK/6vgyHNePruFcCS7hLw79wj3KlWTERV3HsRlF67P4b7/2R3 0EdbXTC+iAUNYyV/epvDijj8T8dKlmrJ2cdqfnpkfo6P8NBFWaYheirr5cLnK4/T/Jci XpezNCb6X1/PTAaRuxQdgh5UopVRPC4V3s9Z02YP4Vjeh1ZzlG2qWn6H6Q8uYxoEHdVt dTWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/TNdh7w8TwLZwUsozUPmw11OXbqHYPToXqiNZ9yDv+4=; b=amezAHqWHBup+Da7Wgvtw5/SXhyu+B4gxeR6dwT3fxgZDeerF+s+K6AuTVZAi/0jD1 fPRecEcp60Cjyt2PM87WxLbQcgpF4Pq+/5fR2ynFlg1alvD2seC+YSTnvSX2LbUqHNu3 E8h41vhk0wa7rA3J6VwLe4TDnl9ff7Y1Fcf5BsovpFQRaDZezrSejwipd+vVPMXHnne7 2ZZG84saks/0NxULgT7lkBhloQqvXCK8AH4Lxg2e82Cf7ukjYWDC3jfbNcXRjoFstcu6 rweVNbshdleYhUHloHLuLj8hZRSbNJqOqkWwpz2cVgQ6ubqE5p5WEH0yI1a7zeXEnCnz 5w/A==
X-Gm-Message-State: ALyK8tI94ZyPecBtZV0gc0bqQyk4D1hqXKpJpl9fkCk2qQjcPWqhIPt6+mAH6YvXBNo+hyKoqzCc4wmD0kTLYA==
X-Received: by 10.25.210.80 with SMTP id j77mr8237933lfg.139.1468944654606; Tue, 19 Jul 2016 09:10:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Tue, 19 Jul 2016 09:10:14 -0700 (PDT)
In-Reply-To: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 19 Jul 2016 18:10:14 +0200
Message-ID: <CAPt1N1mHp0bLtPFHkmZuOz54nQ5ZLObB=48g83+NGs4xv9xkEg@mail.gmail.com>
To: "avri@acm.org" <avri@doria.org>
Content-Type: multipart/alternative; boundary=001a11400ee655343e0537ff54b7
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/SRtiNI6EGXkVNG7sxATFwGfD7oQ>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 16:15:10 -0000

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

Please read draft-lemon-sutldr-ps, and participate in the discussion about
this on the dnsop mailing list.   Discussions about the RFC6761 problem are
off-topic for the homenet mailing list.   We are customers of the existing
IETF consensus process as documented in RFC 6761.   We get into enough
ratholes on the homenet mailing list; please don't get us into this rathole
as well.

On Mon, Jul 18, 2016 at 4:22 PM, avri@acm.org <avri@doria.org> wrote:

>
> ICANN may not have handed it out yet, and may be on a hold about doing so=
,
> but many still expect some resolution to that road block. I certainly do.
>
> Making assumptions about icann=E2=80=98s future behavior on this _policy_=
 issue is
> a bad bet.
>
> Some questions I still do not understand the answers for
>
> - why do you need a TLD? Why won't a SLD work?
>
> - why do you need a word from natural language? I know many still maintai=
n
> the myth that it is a coincidence when a string matches natural language,
> but many have other used for natural language words. In fact I assume you
> picked it because of its similarity to a natural world. But why do you ne=
ed
> it?
>
> - what sort of implementer hard codes name strings in their code?
>
> Avri
> ( coincidentally Co-chair ICANN new gTLD Subsequent Procedures working
> group)
>
> Sent from my T-Mobile 4G LTE Device
>
> -------- Original message --------
> From: Mikael Abrahamsson <swmike@swm.pp.se>
> Date: 7/18/16 15:33 (GMT+01:00)
> To: Terry Manderson <terry.manderson@icann.org>
> Cc: HOMENET <homenet@ietf.org>, Ray Bellis <ray@bellis.me.uk>
> Subject: Re: [homenet] RFC 7788 and ".home"
>
>
> The option 4 mentioned updating RFC7788. It's not clear to me what this
> update would be.
>
> .HOME has not been handed out by ICANN yet, what's the odds that RFC6761
> process reserving .HOME for special use would succeed?
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<div dir=3D"ltr">Please read draft-lemon-sutldr-ps, and participate in the =
discussion about this on the dnsop mailing list. =C2=A0 Discussions about t=
he RFC6761 problem are off-topic for the homenet mailing list. =C2=A0 We ar=
e customers of the existing IETF consensus process as documented in RFC 676=
1. =C2=A0 We get into enough ratholes on the homenet mailing list; please d=
on&#39;t get us into this rathole as well. =C2=A0=C2=A0</div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 18, 2016 at 4:22 PM=
, <a href=3D"mailto:avri@acm.org">avri@acm.org</a> <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:avri@doria.org" target=3D"_blank">avri@doria.org</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div><div>ICAN=
N may not have handed it out yet, and may be on a hold about doing so, but =
many still expect some resolution to that road block. I certainly do.</div>=
<div><br></div><div>Making assumptions about icann=E2=80=98s future behavio=
r on this _policy_ issue is a bad bet.</div><div><br></div><div>Some questi=
ons I still do not understand the answers for</div><div><br></div><div>- wh=
y do you need a TLD? Why won&#39;t a SLD work?</div><div><br></div><div>- w=
hy do you need a word from natural language? I know many still maintain the=
 myth that it is a coincidence when a string matches natural language, but =
many have other used for natural language words. In fact I assume you picke=
d it because of its similarity to a natural world. But why do you need it?<=
/div><div><br></div><div>- what sort of implementer hard codes name strings=
 in their code?</div><div><br></div><div>Avri</div><div>( coincidentally Co=
-chair ICANN new gTLD Subsequent Procedures working group)</div><div><br></=
div><div><div style=3D"font-size:85%;color:#575757" dir=3D"auto">Sent from =
my T-Mobile 4G LTE Device</div></div><span class=3D""><div><br></div><div s=
tyle=3D"font-size:100%;color:#000000"><div>-------- Original message ------=
--</div><div>From: Mikael Abrahamsson &lt;<a href=3D"mailto:swmike@swm.pp.s=
e" target=3D"_blank">swmike@swm.pp.se</a>&gt; </div><div>Date: 7/18/16  15:=
33  (GMT+01:00) </div><div>To: Terry Manderson &lt;<a href=3D"mailto:terry.=
manderson@icann.org" target=3D"_blank">terry.manderson@icann.org</a>&gt; </=
div><div>Cc: HOMENET &lt;<a href=3D"mailto:homenet@ietf.org" target=3D"_bla=
nk">homenet@ietf.org</a>&gt;, Ray Bellis &lt;<a href=3D"mailto:ray@bellis.m=
e.uk" target=3D"_blank">ray@bellis.me.uk</a>&gt; </div><div>Subject: Re: [h=
omenet] RFC 7788 and &quot;.home&quot; </div><div><br></div></div><br>The o=
ption 4 mentioned updating RFC7788. It&#39;s not clear to me what this <br>=
update would be.<br><br>.HOME has not been handed out by ICANN yet, what&#3=
9;s the odds that RFC6761 <br>process reserving .HOME for special use would=
 succeed?<br><br></span><span class=3D"">-- <br>Mikael Abrahamsson=C2=A0=C2=
=A0=C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmi=
ke@swm.pp.se</a><br><br></span><span class=3D"">___________________________=
____________________<br>homenet mailing list<br><a href=3D"mailto:homenet@i=
etf.org" target=3D"_blank">homenet@ietf.org</a><br><a href=3D"https://www.i=
etf.org/mailman/listinfo/homenet" target=3D"_blank">https://www.ietf.org/ma=
ilman/listinfo/homenet</a><br></span></div><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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
<br></blockquote></div><br></div>

--001a11400ee655343e0537ff54b7--


From nobody Tue Jul 19 15:13:07 2016
Return-Path: <toke@toke.dk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF3C12D504 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 15:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=toke.dk
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 2Y4CK07u5aOW for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 15:13:02 -0700 (PDT)
Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E796412D850 for <homenet@ietf.org>; Tue, 19 Jul 2016 15:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail2.tohojo.dk
DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk 69B7740472
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1468966378; bh=/weVLsQYUWeUVoFiYFqYD2Eb3KNXTIpHsS8bNq8x9ls=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=sJi8haAb5KSaXdhBUMCLEyXpiYuSkXDgOEpBEdCDKPTnowpy9QGGmb0Y2T0cTOJsJ ZaxBl37203IRkFw8oufl+QgZPP687CpH/KsqPUeK1/7O+HiI3hMBwQc4edeRnVqdrS DJavXrHiawlPT/SF35Eq3eVNZPSfPvKvjlbv4wzc=
Sender: toke@toke.dk
Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 4F4243290; Wed, 20 Jul 2016 00:12:55 +0200 (CEST)
From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 20 Jul 2016 00:12:55 +0200
In-Reply-To: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> (Juliusz Chroboczek's message of "Mon, 18 Jul 2016 16:14:26 +0200")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87mvldp994.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/UbmE01j5V6RQbNxdeNa8ldDecmI>
Cc: homenet@ietf.org
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 22:13:05 -0000

I have now also read the naming draft. I think it does a good job of
summarising the desirable feature set, but it does strike me as being
slightly on the complex side in certain respects, and trying to simplify
things a bit might be worthwhile.

(I've been following homenet for a while but haven't commented much. I
think having naming work right is an important piece of the puzzle, so
hoping to add some momentum to the effort by weighing in).

I'll start with Juliusz' comments below and maybe add one or two of my
own.

> These are some fairly ambitious requirements, and I believe that they
> deserve discussion separately from the naming issue.  More precisely:
>
> (1) Are wo to go to the effort of specifying and deploying a new ND option?

As I read this, it is mostly an optimisation and could be left out in
favour of simply timing out. Presumably the case it is solving (homenet
configuration lost) is so uncommon that having a simple timeout is
better than a new option that is probably not going to be very well
tested in any case.

> (2) Defining a management API goes against the Homenet tradition, which
>     is to negotiate things over HNCP rather than defining new APIs.

I agree that the "Restful API" sticks out a bit in the document.
Probably in part because it is a placeholder for something that is not
defined yet. But I'm not sure that it is actually needed. Could the
document not just specify that there must be some way to configure it
appropriately, and leave the details to the implementations?

> (3) HNCP does not currently mandate using a local resolver, and neither
>     does it define a means to advertise the address of a local resolver to
>     HNCP routers.  Are we requiring a full DNS server with DNSsec support
>     on each HNCP node, including an HNCP speaker that is not a router?
>     (Note that I'd be strongly opposed to requiring that every HNCP
>     speaker must be a router, and I think my opinion on putting a DNS
>     forwarder on every HNCP node is similar.)

As I read this, a resolver on each link is required to filter out
spurious DNS updates (last sentence in section 4.1). If some other
mechanism to prevent this is substituted, presumably the requirement to
have a resolver on every link could be dropped?


Another thing that stuck out to me was the suggestion (in section 6.1)
to stick a captive portal in the user's face if there's a configuration
problem (or does "triggering captive portal detection" instead refer to
hijacking just the DNS names that, say, Android uses to detect the
presence of a captive portal?). Not sure I agree that's a good idea -
apart from captive portals being annoying as hell, this is again
specifying a UI element in detail; should the spec really do that?

Finally, the mechanism outlined in section 4.8 to use the homenet
services outside the homenet seems somewhat brittle to me. It involves
both caching logic and key management. I'm not sure to what extent this
is considered a killer feature. Would it be unreasonable to tell users
to simply add services they want to access from off-network to the
public zone?

-Toke


From nobody Tue Jul 19 15:13:31 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA9E12D951 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 15:13:27 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 6TWA7o5YAlxh for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 15:13:25 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B626212D97F for <homenet@ietf.org>; Tue, 19 Jul 2016 15:13:21 -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/56228) with ESMTP id u6JMDH1f031932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Jul 2016 00:13:17 +0200
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/56228) with ESMTP id u6JMDGoG003601; Wed, 20 Jul 2016 00:13:17 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id CFA3561F9D; Wed, 20 Jul 2016 00:13:16 +0200 (CEST)
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 uX_y3tGcE7am; Wed, 20 Jul 2016 00:13:15 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7F3A861FA1; Wed, 20 Jul 2016 00:13:14 +0200 (CEST)
Date: Wed, 20 Jul 2016 00:13:12 +0200
Message-ID: <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "avri@acm.org" <avri@doria.org>
In-Reply-To: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
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]); Wed, 20 Jul 2016 00:13:17 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 20 Jul 2016 00:13:17 +0200 (CEST)
X-Miltered: at korolev with ID 578EA5FD.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578EA5FC.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578EA5FD.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: 578EA5FC.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 : 578EA5FD.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578EA5FC.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: <https://mailarchive.ietf.org/arch/msg/homenet/h2tXhtlJK_O6AkuS6h3Elh2betg>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Jul 2016 22:13:28 -0000

> - why do you need a TLD? Why won't a SLD work?

We want something short and memorable.  ".co.uk" is short and memorable.
".univ-paris-diderot.fr" is not.

> - why do you need a word from natural language?

We want something short and memorable.  ".home" is short and memorable.
".in-addr.arpa" is not.

> - what sort of implementer hard codes name strings in their code?

I do.

This group is designing a set of protocols that are meant to enable an
intelligent layman to deploy a well-designed (no NAT) local area network.
We use a number of techniques, such as highly refined distributed
consensus algorithms, but also defaulting to standardised values where
flexibility is not needed or not desirable.  In the particular case of the
choice of the top-level domain, there is agreement in this WG that having
a standardised default is more robust, more predictable, and easier to
understand than using a distributed consensus algorithm.

As to how this is implemented (hard-wired in the code or learned from
a configuration file that is shipped with standard-compliant defaults) --
with all due respect, that is none of your business.

-- Juliusz


From nobody Tue Jul 19 22:45:21 2016
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 430F512DA66 for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 22:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0hJ0_RRyogJG for <homenet@ietfa.amsl.com>; Tue, 19 Jul 2016 22:45:18 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3DB112DA78 for <homenet@ietf.org>; Tue, 19 Jul 2016 22:45:17 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id o80so51338520wme.1 for <homenet@ietf.org>; Tue, 19 Jul 2016 22:45:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=LLAaMmFsNSIIbaKmopSVigWrFnzA8Uq1nW9Xek00T8Y=; b=lat7YQcIeop4HEGPC/uobMRgZKpapgZFDca98vjbYK2MgSqCFc7M7vWcPVAQLcXBWO AwE/Tp+2Lrrpk3V2YDrDOIot7e0LA8LjFLEiN4eaa0IYbF2sKIUSO7lp2Kwh1+YyBAlb /xwGeXiEJZSbeDPJm2cUYEpwAuI4dI2vASSkqIK36gklrgW+KmZH+NbT4KEQJzkrdmnx Q9kXMBbOBwG78LKyjnc4PO5EYOcnX+OojarXAMTsDjDpVLimamIEvX6bHOWSGCWtr3ZO 4IvZlLJgWh9JeB6h05LN9qjxuYs/kCRdPVAPC1YXpPr8SxBenKfaw75ja03A+1RSh5KL TEMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LLAaMmFsNSIIbaKmopSVigWrFnzA8Uq1nW9Xek00T8Y=; b=OY92jJnHnD9Jx8XmE0eLcJ9NsKP8JEbBwoFO4Z0loGIYK6yzf69sm8DRr5nN15LbqA sUtVEd+y1RLYYj+OIe6SJlCp2mvEu8fmZSanb75t2FeLyDqhcNAcVVcXF2gTfm3iw8Nx XoClJZhQ3PrAllPjkrmGIz0eLyVg2OfF3b29MOF3bxtyekxqtpk4qKIaN4usbDLuo8cw 4ZUCE7HSgRCDb/pRtTqq2AI+EEIpl9NNVwotrfi1ahCHxbiijzExSLWvbT1uI+a70+1y FN4g5ynzRT6BJ4y1xqytEU4YUr1FJm3VDqlrU+1mrH/rf0595XmbTxghk3mj2mLksjkc L8qg==
X-Gm-Message-State: ALyK8tLzgTgD90/9V96IEYeGKgcIr13JWM5pLG9W7u3X4uBz8Dr7jOx0Xp+VtrTnYQmyZw==
X-Received: by 10.28.165.3 with SMTP id o3mr9621984wme.3.1468993515083; Tue, 19 Jul 2016 22:45:15 -0700 (PDT)
Received: from twicinski-ltm.internal.salesforce.com (port-83-236-242-106.static.qsc.de. [83.236.242.106]) by smtp.googlemail.com with ESMTPSA id 17sm2742761wmf.6.2016.07.19.22.45.14 for <homenet@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jul 2016 22:45:14 -0700 (PDT)
To: homenet@ietf.org
References: <8760s2atgk.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksmmDDtVkspHDjzGXXCWkiLCdbpfiP6MaaQYpfjO5iqg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <d32930f6-c221-8fdb-274a-a7da7f15ebe1@gmail.com>
Date: Wed, 20 Jul 2016 07:45:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1ksmmDDtVkspHDjzGXXCWkiLCdbpfiP6MaaQYpfjO5iqg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/c_9WZOiXuZ0IM_dAeok5nRCNpck>
Subject: Re: [homenet] About ULAs in Ted's draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 05:45:20 -0000

If you have no ULA, then you may have to fall back to manual creation of 
the homenet domain in 4.7, which is less than ideal.

tim

ps - i've read the draft and think it's ready for adoption.  Needs some 
fleshing out, but it's has a good foundation.


On 7/19/16 11:22 AM, Ted Lemon wrote:
> Yeah, I think this is the right approach. I think a homenet with no ULA
> is broken, but I don't want to insist. Things just get a lot more
> brittle if you don't have ULAs.
>
>
> On Jul 19, 2016 11:05, "Juliusz Chroboczek"
> <jch@pps.univ-paris-diderot.fr <mailto:jch@pps.univ-paris-diderot.fr>>
> wrote:
>
>     Ted,
>
>     I've read the draft again, and I think that there's only one place where
>     you rely on having a ULA.  So I'd suggest:
>
>       Section 3.3 point 2, replace "the homenet's ULA prefix" with "the
>       homenet's ULA prefix (if any)".
>
>       In Section 5.5, change "Homenets have at least one ULA prefix" with
>       "Homenets usually have exactly one non-deprecated ULA prefix".
>
>     The only place where you actually rely on a ULA is Section 4.7,
>     paragraph
>     2.  I have no idea what to do about that.
>
>     Alternatives to this include making ULA generation a MUST in the
>     HNCP RFC,
>     or making naming support a SHOULD that depends on having a ULA.  I hold
>     a mild distaste for either of these possibilities, but I suppose I could
>     live with either.
>
>     -- Juliusz
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>


From nobody Wed Jul 20 00:18:00 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73B3812D9B9 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 00:17:59 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 GexhprE8JHkk for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 00:17:57 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 707C312D5A3 for <homenet@ietf.org>; Wed, 20 Jul 2016 00:17:57 -0700 (PDT)
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/56228) with ESMTP id u6K7Htak015911; Wed, 20 Jul 2016 09:17:55 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0381B61FA6; Wed, 20 Jul 2016 09:17:55 +0200 (CEST)
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 ygP2dpN6Lyw7; Wed, 20 Jul 2016 09:17:53 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 70A4B61FA1; Wed, 20 Jul 2016 09:17:53 +0200 (CEST)
Date: Wed, 20 Jul 2016 09:17:52 +0200
Message-ID: <87r3ao7p7j.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Tim Wicinski <tjw.ietf@gmail.com>
In-Reply-To: <d32930f6-c221-8fdb-274a-a7da7f15ebe1@gmail.com>
References: <8760s2atgk.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksmmDDtVkspHDjzGXXCWkiLCdbpfiP6MaaQYpfjO5iqg@mail.gmail.com> <d32930f6-c221-8fdb-274a-a7da7f15ebe1@gmail.com>
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 [194.254.61.138]); Wed, 20 Jul 2016 09:17:55 +0200 (CEST)
X-Miltered: at korolev with ID 578F25A3.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578F25A3.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 : 578F25A3.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/IhU8ANTav-4liOXm5wLGD43iKyI>
Cc: homenet@ietf.org
Subject: Re: [homenet] About ULAs in Ted's draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 07:17:59 -0000

> ps - i've read the draft and think it's ready for adoption.

I most humbly disagree.  Let's please leave some time for people to think
it over and possibly come with counter-proposals.

-- Juliusz


From nobody Wed Jul 20 01:53:28 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B12912D0F9 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 01:53:27 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 iVgO_qYiNU1A for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 01:53:25 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C1F12D0B8 for <homenet@ietf.org>; Wed, 20 Jul 2016 01:53:18 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id l69so33360566lfg.1 for <homenet@ietf.org>; Wed, 20 Jul 2016 01:53:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=rWRZ6IxZSEfYA5GQMU1q+tnR9W9llo/ytkGZrCtgbe4=; b=h5jqhldPkqhkA6+y4DqJJlo4XvLryDtuFfuc+KumLl0mURUuQRLVmjL2RPa9SaDT+3 VrlSEg9rLkn4AuWXPVFW8FreenoPSGtqMyYFxF6joLpi1aAFvNDcJvXGnigaLmurOjnz uDvlAuHTf7G3ganyG9Z0bpNeDX+wYm8BO/def9HBMsLOBD3XIrPaGFu1uC3fVWC3YLrI mpdpNLCcwzCUqZjFCGk3iz8PxSnff7r/M7qWaEkhSacvlZcgpiCqHqoMR3SpXdj0sc7u E/0TxHlwDZeRvLjW5fBQI0v8IpK70zfAXxvjeF2J/qiJAdveLpy2RuAU7VvY/OE1eO8j YcsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=rWRZ6IxZSEfYA5GQMU1q+tnR9W9llo/ytkGZrCtgbe4=; b=HlcwaAuJJN+KZLSLdIma9qUEyKh+SXncaYIW801qE9RsSKVRfYJYtWG+3MhB0jISUb 6ZC1fYIShc/H/OtfM2VGzH9skeShci1FvBdHWHx2wb06vbgXgPs8ZuomoXrYTCSVSmph kVgCEZEo0ANb983Pcbf3L+KA2MFuzB3q1ZVcxN0K3ZjPsU2Z4EznEz29xKc5cv/dcv7O QsWyeQZiXu/sih710K2Sjk/PXxh8+gkB0nzrqivO5ONtFFLBOZJQj15xSLauwvfoWEJA pMHZ/TGKJBIaickwfIZ8xtnsJ8wki4jeksvVPg1BPUafgLymcl1HGIQUOYs6i1mMiWQO 6G4g==
X-Gm-Message-State: ALyK8tIDroGcov38WCBebiwd1BOQH6fLorwI5zvH86m27nPjNT9cNs3IXYFtz8eyegUr0l9HajhghXQY0C5GZg==
MIME-Version: 1.0
X-Received: by 10.46.5.196 with SMTP id 187mr18171360ljf.13.1469004796062; Wed, 20 Jul 2016 01:53:16 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 01:53:15 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 01:53:15 -0700 (PDT)
In-Reply-To: <87mvldp994.fsf@toke.dk>
References: <87d1mb11a5.wl-jch@pps.univ-paris-diderot.fr> <87mvldp994.fsf@toke.dk>
Date: Wed, 20 Jul 2016 10:53:15 +0200
Message-ID: <CAPt1N1=c7Ve9=imDy1iK1uiB2bzOjxVv6y7PJSYF=sJwpdC_Nw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= <toke@toke.dk>
Content-Type: multipart/alternative; boundary=001a114a6bea0affe905380d556f
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/sx7345HGoP_7VWbDOxHLAjTwCEI>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] My comment about Ted's naming draft
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 08:53:27 -0000

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

On Jul 20, 2016 00:13, "Toke H=C3=B8iland-J=C3=B8rgensen" <toke@toke.dk> wr=
ote:
> > These are some fairly ambitious requirements, and I believe that they
> > deserve discussion separately from the naming issue.  More precisely:
> >
> > (1) Are wo to go to the effort of specifying and deploying a new ND
option?

Why is this hard?

> As I read this, it is mostly an optimisation and could be left out in
> favour of simply timing out. Presumably the case it is solving (homenet
> configuration lost) is so uncommon that having a simple timeout is
> better than a new option that is probably not going to be very well
> tested in any case.

Maybe so. We should think about this. In any case, remember that the
architecture document is the list of what are trying to accomplish. Seeing
high goals is okay. If we realized that this is an optimization with little
value, we don't have to do it.

> > (2) Defining a management API goes against the Homenet tradition, which
> >     is to negotiate things over HNCP rather than defining new APIs.
>
> I agree that the "Restful API" sticks out a bit in the document.

Restful is probably overspecifying.

> Could the
> document not just specify that there must be some way to configure it
> appropriately, and leave the details to the implementations?

This would represent failure. Leaving it to the implementation means no
interop, which means vendor lock in.

> As I read this, a resolver on each link is required to filter out
> spurious DNS updates (last sentence in section 4.1). If some other
> mechanism to prevent this is substituted, presumably the requirement to
> have a resolver on every link could be dropped?

Send text proposing this new alternative. However, it doesn't need to be a
full blown resolver. It could just proxy. But there does need to be at
least one resolver in the homenet.

> Another thing that stuck out to me was the suggestion (in section 6.1)
> to stick a captive portal in the user's face if there's a configuration
> problem (or does "triggering captive portal detection" instead refer to
> hijacking just the DNS names that, say, Android uses to detect the
> presence of a captive portal?). Not sure I agree that's a good idea -
> apart from captive portals being annoying as hell, this is again
> specifying a UI element in detail; should the spec really do that?

We need a way to contact the user. This is an easy way. I am open to other
ideas.

> Finally, the mechanism outlined in section 4.8 to use the homenet
> services outside the homenet seems somewhat brittle to me. It involves
> both caching logic and key management. I'm not sure to what extent this
> is considered a killer feature. Would it be unreasonable to tell users
> to simply add services they want to access from off-network to the
> public zone?

No. However, this is certainly a nice to have, not a must.

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

<p dir=3D"ltr">On Jul 20, 2016 00:13, &quot;Toke H=C3=B8iland-J=C3=B8rgense=
n&quot; &lt;<a href=3D"mailto:toke@toke.dk">toke@toke.dk</a>&gt; wrote:<br>
&gt; &gt; These are some fairly ambitious requirements, and I believe that =
they<br>
&gt; &gt; deserve discussion separately from the naming issue.=C2=A0 More p=
recisely:<br>
&gt; &gt;<br>
&gt; &gt; (1) Are wo to go to the effort of specifying and deploying a new =
ND option?</p>
<p dir=3D"ltr">Why is this hard?</p>
<p dir=3D"ltr">&gt; As I read this, it is mostly an optimisation and could =
be left out in<br>
&gt; favour of simply timing out. Presumably the case it is solving (homene=
t<br>
&gt; configuration lost) is so uncommon that having a simple timeout is<br>
&gt; better than a new option that is probably not going to be very well<br=
>
&gt; tested in any case.</p>
<p dir=3D"ltr">Maybe so. We should think about this. In any case, remember =
that the architecture document is the list of what are trying to accomplish=
. Seeing high goals is okay. If we realized that this is an optimization wi=
th little value, we don&#39;t have to do it. </p>
<p dir=3D"ltr">&gt; &gt; (2) Defining a management API goes against the Hom=
enet tradition, which<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0is to negotiate things over HNCP rather than d=
efining new APIs.<br>
&gt;<br>
&gt; I agree that the &quot;Restful API&quot; sticks out a bit in the docum=
ent.</p>
<p dir=3D"ltr">Restful is probably overspecifying. </p>
<p dir=3D"ltr">&gt; Could the<br>
&gt; document not just specify that there must be some way to configure it<=
br>
&gt; appropriately, and leave the details to the implementations?</p>
<p dir=3D"ltr">This would represent failure. Leaving it to the implementati=
on means no interop, which means vendor lock in. <br></p>
<p dir=3D"ltr">&gt; As I read this, a resolver on each link is required to =
filter out<br>
&gt; spurious DNS updates (last sentence in section 4.1). If some other<br>
&gt; mechanism to prevent this is substituted, presumably the requirement t=
o<br>
&gt; have a resolver on every link could be dropped?</p>
<p dir=3D"ltr">Send text proposing this new alternative. However, it doesn&=
#39;t need to be a full blown resolver. It could just proxy. But there does=
 need to be at least one resolver in the homenet. </p>
<p dir=3D"ltr">&gt; Another thing that stuck out to me was the suggestion (=
in section 6.1)<br>
&gt; to stick a captive portal in the user&#39;s face if there&#39;s a conf=
iguration<br>
&gt; problem (or does &quot;triggering captive portal detection&quot; inste=
ad refer to<br>
&gt; hijacking just the DNS names that, say, Android uses to detect the<br>
&gt; presence of a captive portal?). Not sure I agree that&#39;s a good ide=
a -<br>
&gt; apart from captive portals being annoying as hell, this is again<br>
&gt; specifying a UI element in detail; should the spec really do that?</p>
<p dir=3D"ltr">We need a way to contact the user. This is an easy way. I am=
 open to other ideas. </p>
<p dir=3D"ltr">&gt; Finally, the mechanism outlined in section 4.8 to use t=
he homenet<br>
&gt; services outside the homenet seems somewhat brittle to me. It involves=
<br>
&gt; both caching logic and key management. I&#39;m not sure to what extent=
 this<br>
&gt; is considered a killer feature. Would it be unreasonable to tell users=
<br>
&gt; to simply add services they want to access from off-network to the<br>
&gt; public zone?</p>
<p dir=3D"ltr">No. However, this is certainly a nice to have, not a must. <=
br>
</p>

--001a114a6bea0affe905380d556f--


From nobody Wed Jul 20 02:11:05 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEF812DAFB for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:11:03 -0700 (PDT)
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 autolearn_force=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 MatfFdFMwa2E for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:10:55 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAA812D125 for <homenet@ietf.org>; Wed, 20 Jul 2016 02:10:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id BAD4910D38 for <homenet@ietf.org>; Wed, 20 Jul 2016 09:10:46 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6gbT7xszPCs for <homenet@ietf.org>; Wed, 20 Jul 2016 09:10:45 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-a9ee.meeting.ietf.org [31.133.169.238]) by mx2.yitter.info (Postfix) with ESMTPSA id F2E6E1067D for <homenet@ietf.org>; Wed, 20 Jul 2016 09:10:44 +0000 (UTC)
Date: Wed, 20 Jul 2016 05:10:35 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160720091034.GA48086@mx2.yitter.info>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/HRnCjssj0w6nRTXrcHbaz4Dhk-g>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 09:11:03 -0000

On Wed, Jul 20, 2016 at 12:13:12AM +0200, Juliusz Chroboczek wrote:
> > - why do you need a TLD? Why won't a SLD work?
> 
> We want something short and memorable.  ".co.uk" is short and memorable.
> ".univ-paris-diderot.fr" is not.

Why?  This is, I suspect, part of the issue: it seems that we have
some assumptions about the use of these names, and I'm not entirely
sure what they are.  It is not obvious to me that "short and
memorable" is a requirement that falls out of section 3.7 of RFC 7368. 
 
> > - why do you need a word from natural language?
> 
> We want something short and memorable.  ".home" is short and memorable.
> ".in-addr.arpa" is not.

"Something short and memorable" is again a requirement here that isn't
obviously imposed by RFC 7368.  But worse, "home" is actually only
memorable for people who know what that word is in English, and it's
only even useful to people who use Latin characters.  It's not like
internationalization considerations in naming are unknown (and it
would appear that if there is a requirement for natural language
strings then we haven't attended to RFC 2277 section 6).  Since the
point of this is to be intuitive for users who aren't professional
administrators, I guess I assumed that it also has to be intuitive for
such users who happen not to speak and read English.  I'm prepared to
admit my assumption may be wrong, but if so I'd like the WG to think
about that first.

> flexibility is not needed or not desirable.  In the particular case of the
> choice of the top-level domain, there is agreement in this WG that having
> a standardised default is more robust, more predictable, and easier to
> understand than using a distributed consensus algorithm.

It appears to me that an interpretation equally consistent with the
results of the WG is that the WG proceeded with a simplifying
assumption and more or less ignored the details implicit in this
issue, partly because the WG had already decided mostly to kick the
issue of naming down the road a little.

I appreciate that it's annoying to discover that there's a problem
quite this late, and it's super annoying that we have to cope with it
quickly.  And I take my full share of the blame: I missed this, and
should not have.  But cope with it we must, because the use of
home. or any other name without having answered the questions in
section 5 of RFC 6761, and without registering a well-known domain
name in the DNS, is bad for the network and a threat to the very users
we're supposed to be serving with this effort.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Jul 20 02:27:37 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20B2212D0DD for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:27:36 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 kmAaxMHQU3Eh for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:27:34 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EF47128E18 for <homenet@ietf.org>; Wed, 20 Jul 2016 02:27:34 -0700 (PDT)
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/56228) with ESMTP id u6K9RWMW030021 for <homenet@ietf.org>; Wed, 20 Jul 2016 11:27:32 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id D9F7061FA6 for <homenet@ietf.org>; Wed, 20 Jul 2016 11:27:32 +0200 (CEST)
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 5iLRemd_3lU5 for <homenet@ietf.org>; Wed, 20 Jul 2016 11:27:31 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7074961F9D for <homenet@ietf.org>; Wed, 20 Jul 2016 11:27:30 +0200 (CEST)
Date: Wed, 20 Jul 2016 11:27:30 +0200
Message-ID: <87zipcaccd.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 [194.254.61.138]); Wed, 20 Jul 2016 11:27:33 +0200 (CEST)
X-Miltered: at korolev with ID 578F4404.005 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578F4404.005 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 : 578F4404.005 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/DJA09ox8C4E5HEe14JjiHi8on0w>
Subject: [homenet] Naming: a strawman counter-proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 09:27:36 -0000

Not proposing this seriously, just attempting to explore the design space.
Some of the ideas are due to Toke.

Zones and authoritative nameservers are announced over HNCP together with
their set of addresses, which SHOULD include a LUA and MUST include at
least one IPv6 address.  There are two bits associated with each
authoritative nameserver:

  - default: set to 1 if the zone is suitable for name registration without
    explicit user configuration;
  - public: set to 1 if the zone is visible from the public internet.

When a router joins the homenet, it MAY announce itself as the new
authoritative nameserver for a zone.  It SHOULD do so if there is no
default public or private zone.

If there are two default private zones or two default public zones, we
call an election, Highlander-style.  If there are two authoritative
nameservers for the same zone, we call an election.

There are no secondaries.  If there are secondaries, their configuration
is outside the scope of this mail.

Stateful DHCP servers SHOULD register their clients with the authoritative
nameserver for the default private zone using your favourite unicast
mechanism.  Clients MAY register themselves with any zone currently
announced (they learn the server addresses through HNCP snooping or a from
new ND option, I don't care).

mDNS proxying into the default private zone is allowed.  Or recommended,
I'm not sure, only implementation experience will tell.

Why exactly am I speaking nonsense?

-- Juliusz


From nobody Wed Jul 20 02:29:27 2016
Return-Path: <wouter.cloetens@softathome.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20FC12D811 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 0Y7aOEqDpRiq for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:29:23 -0700 (PDT)
Received: from mx20.yaziba.net (mx20.yaziba.net [85.233.204.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15A1F12B01C for <homenet@ietf.org>; Wed, 20 Jul 2016 02:29:22 -0700 (PDT)
Received: from mta10.int.yaziba.net (mta10.int.yaziba.net [10.4.20.30]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx20.yaziba.net (mx10.yaziba.net) with ESMTPS id 76A081A7B12 for <homenet@ietf.org>; Wed, 20 Jul 2016 11:29:20 +0200 (CEST)
Received: from mta10.int.yaziba.net (localhost [127.0.0.1]) by mta10.int.yaziba.net (Postfix) with ESMTPS id A5E06CA65A for <homenet@ietf.org>; Wed, 20 Jul 2016 11:29:20 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mta10.int.yaziba.net (Postfix) with ESMTP id 95689CA75B for <homenet@ietf.org>; Wed, 20 Jul 2016 11:29:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at mta10.int.yaziba.net
Received: from mta10.int.yaziba.net ([127.0.0.1]) by localhost (mta10.int.yaziba.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id CmsKyNyu75xa for <homenet@ietf.org>; Wed, 20 Jul 2016 11:29:20 +0200 (CEST)
Received: from [31.133.160.150] (dhcp-a096.meeting.ietf.org [31.133.160.150]) by mta10.int.yaziba.net (Postfix) with ESMTPSA id 6319CCA75E for <homenet@ietf.org>; Wed, 20 Jul 2016 11:29:20 +0200 (CEST)
To: homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info>
From: Wouter Cloetens <wouter.cloetens@softathome.com>
Message-ID: <578F446F.9060104@softathome.com>
Date: Wed, 20 Jul 2016 11:29:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0
MIME-Version: 1.0
In-Reply-To: <20160720091034.GA48086@mx2.yitter.info>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-DRWEB-SCAN: ok
X-VRSPAM-SCORE: 50
X-VRSPAM-STATE: legit
X-VRSPAM-CAUSE: gggruggvucftvghtrhhoucdtuddrfeeltddrheefgdduhecutefuodetggdotefrucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpjgetkgfkueetnecuuegrihhlohhuthemuceftddtnecuogetfeejfedqtdegucdlhedtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtjegrtddtfeejnecuhfhrohhmpeghohhuthgvrhcuvehlohgvthgvnhhsuceofihouhhtvghrrdgtlhhovghtvghnshesshhofhhtrghthhhomhgvrdgtohhmqeenucffohhmrghinhepohhfrdhnvghtnecukfhppeefuddrudeffedrudeitddrudehtdenucfrrghrrghmpehmohguvgepshhmthhpohhuth
X-VRSPAM-EXTCAUSE: mhhouggvpehsmhhtphhouhht
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/XB5OqNV6eDcA53eD3axefvjh6JM>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 09:29:25 -0000

On 20/07/16 11:10, Andrew Sullivan wrote:
> On Wed, Jul 20, 2016 at 12:13:12AM +0200, Juliusz Chroboczek wrote:
>>> - why do you need a word from natural language?
>> We want something short and memorable.  ".home" is short and memorable.
>> ".in-addr.arpa" is not.
> "Something short and memorable" is again a requirement here that isn't
> obviously imposed by RFC 7368.  But worse, "home" is actually only
> memorable for people who know what that word is in English, and it's
> only even useful to people who use Latin characters.
Speaking as a residential gateway (stack) vendor who has deployed close 
to 20 million units in (at my last count) 15 countries across Europe, 
the Middle East and Africa, none of them English speaking, primarily in 
France which is very protective of its language, I would say that that 
is a non-issue. The DNS lingua franca started with Latin for .edu, .com, 
.mil, .org, and moved to English with the likes of .net, .biz and most 
gTLD's. There is a global acceptance that English and the Latin 
character set are used for some things on the Internet, and everyone can 
input left-to-right, Latin character strings on their keyboards. Nobody 
is calling for translations of "http" or "www", to my knowledge.

"Short and memorably" seems like an obvious goal to me. .home fits this, 
and is a well known word among non-English speakers. Even 
extraterrestrials point at the night sky and request to "phone home."

A notable exception is Deutsche Telekom whose gateways use ".lan". Which 
is an English acronym.

bfn, Wouter


From nobody Wed Jul 20 02:50:21 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F98812DA51 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:50:20 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 0iAqa6oFfnBc for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 02:50:11 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B9912DA1E for <homenet@ietf.org>; Wed, 20 Jul 2016 02:50:10 -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/56228) with ESMTP id u6K9o7rE011332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Jul 2016 11:50:07 +0200
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/56228) with ESMTP id u6K9o7iX030018; Wed, 20 Jul 2016 11:50:07 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 56CA161F9D; Wed, 20 Jul 2016 11:50:07 +0200 (CEST)
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 shEJu0nxM-xu; Wed, 20 Jul 2016 11:50:05 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-9bed.meeting.ietf.org [31.133.155.237]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id CDE2A61FA1; Wed, 20 Jul 2016 11:50:05 +0200 (CEST)
Date: Wed, 20 Jul 2016 11:50:05 +0200
Message-ID: <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20160720091034.GA48086@mx2.yitter.info>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info>
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]); Wed, 20 Jul 2016 11:50:07 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 20 Jul 2016 11:50:07 +0200 (CEST)
X-Miltered: at korolev with ID 578F494F.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 578F494F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578F494F.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: 578F494F.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 : 578F494F.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 578F494F.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: <https://mailarchive.ietf.org/arch/msg/homenet/i0UeQldPV8hvojloVBx_b5H17jA>
Cc: homenet@ietf.org
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 09:50:20 -0000

>> We want something short and memorable.  ".co.uk" is short and memorable.
>> ".univ-paris-diderot.fr" is not.

> Why?  This is, I suspect, part of the issue: it seems that we have
> some assumptions about the use of these names, and I'm not entirely
> sure what they are.  It is not obvious to me that "short and
> memorable" is a requirement that falls out of section 3.7 of RFC 7368.

I suggest we put this question to the WG.  Perhaps the chairs would be
willing to ask whether the WG would prefer a name that is short and
memorable, or one that is long and impossible to remember?

> But worse, "home" is actually only memorable for people who know what
> that word is in English,

I seem to always hear this argument from native speakers of English.
I have spent much of the last 20 years working with native speakers of
French and Maghribi Arabic, many of whom have very little English, and we
have never had any issue with remembering short English words without
complex consonant clusters ("for" and even "while" are fine, but "length"
tends to cause problems).  My sample is certainly biased, but these are
first year students at a non-elite university (no tuition fees), so they
are probably representative of the public we're aiming for.

> and it's only even useful to people who use Latin characters.

I could be wrong, but I do not believe there exists any country in the
world where literate people are not familiar with the Latin alphabet.

-- Juliusz


From nobody Wed Jul 20 03:01:45 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36D1E12DB02 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:01:43 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TINjLDfq61i4 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:01:41 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C69D612DAD1 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:01:40 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id s63so40287849qkb.2 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=2naxeDTqEb21o7vWNSaLwu2gk3dxvtjkXIF4sanmdEo=; b=dhWxeDHH5qf81AwKn4gOrC6bIK5DQo3COwJ6kkc6705h5bzm0iLtQhSL4EBKdYfpxy aLGDUo152OhWBAxDJkr2tfmgGgwrcl9Ed38sur+pWyMBdgbzC6sA3JKK0zwKtLm3selO 3TlsGosKQLCa8iiQeI/1ZhBCbX7i0Ns7EmE+mONblneWRBHs/rhk5PWhrGD1ZrY6gt2R Laut5uwaDhihMmLDdRcRJ0z/5LELT+H8Ols6ek8dScQuDe+elmuiP/ay/fpTAUrczm5n tI3G7KJz7KuznG7Eq+retPs/nIS+0nlDmz0CV2W5NiDgA9R3VKzL2HSuLDtf2a0X9eoh umpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=2naxeDTqEb21o7vWNSaLwu2gk3dxvtjkXIF4sanmdEo=; b=axdPhkRCpOXaBQywg6+BJ1bFNKLK/bRc1aQgceDLf0HcusmIGgxdzZ66KfWi2e6THw YDUl8JdcRbIo/Eiparm9jcL/a6tUKNkrY35u3KlZbkpVIoYLWlqv7rgelGlRpYodW7ci fNdamkfAkMi2ffHZgmU1SUTV1FRtE7PMVJVU+eIOChaOWNLk6GiHHnLTbVZNEDjLTPHO bGcfYDSjmsOejnEhl0+aUEPWqARTgn99d5c7NT+qekGcLb49TXh6b/5eTx3iIv9jDSlT BgBByD2b0uWeRTD///6h/LB3CzdJoUpH1t+Z0hrL5yEtEkTVRNmoamEp4J/JL9AFRxry NbAQ==
X-Gm-Message-State: ALyK8tJ156nUlmm+cVBWCKh5i+wAPHwMZdEppAr4wKFfhVowTvCbzh9NkhOFxejD4TT9Aw==
X-Received: by 10.55.72.17 with SMTP id v17mr59733264qka.44.1469008899935; Wed, 20 Jul 2016 03:01:39 -0700 (PDT)
Received: from rtp-vpn2-1410.cisco.com ([173.38.117.67]) by smtp.gmail.com with ESMTPSA id q187sm977638qke.42.2016.07.20.03.01.38 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jul 2016 03:01:39 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_32E7DA58-C728-497B-BD13-D9661F634E19"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 20 Jul 2016 12:01:35 +0200
Message-Id: <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
To: HOMENET <homenet@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ofp7OOibNqisJcUR4D3rphQPflc>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:01:43 -0000

--Apple-Mail=_32E7DA58-C728-497B-BD13-D9661F634E19
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 20, 2016, at 11:50 AM 7/20/16, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>>> We want something short and memorable.  ".co.uk" is short and =
memorable.
>>> ".univ-paris-diderot.fr" is not.
>=20
>> Why?  This is, I suspect, part of the issue: it seems that we have
>> some assumptions about the use of these names, and I'm not entirely
>> sure what they are.  It is not obvious to me that "short and
>> memorable" is a requirement that falls out of section 3.7 of RFC =
7368.
>=20
> I suggest we put this question to the WG.  Perhaps the chairs would be
> willing to ask whether the WG would prefer a name that is short and
> memorable, or one that is long and impossible to remember?

I think there are some important questions to answer first:

What is the meaning of .home and, precisely, how will names that end in =
.home be resolved?

Where and by whom will this label actually be used?  What is the =
research to back up the answer?

Although many people have given me a answer to the first question, and =
the answers often include phrases like "it just means..." or "everybody =
agrees that..." or "it's obvious...", I don't think I've seen a citable =
definition for the intention and semantics of .home; pointers welcome.

Without that definition, I don't think I know where and by whom the =
label will actually be used.  Will it turn out to be like .local, which, =
as far as I know, is rarely used anywhere and only ever by a certain =
class of expert user.

- Ralph

>=20
>> But worse, "home" is actually only memorable for people who know what
>> that word is in English,
>=20
> I seem to always hear this argument from native speakers of English.
> I have spent much of the last 20 years working with native speakers of
> French and Maghribi Arabic, many of whom have very little English, and =
we
> have never had any issue with remembering short English words without
> complex consonant clusters ("for" and even "while" are fine, but =
"length"
> tends to cause problems).  My sample is certainly biased, but these =
are
> first year students at a non-elite university (no tuition fees), so =
they
> are probably representative of the public we're aiming for.
>=20
>> and it's only even useful to people who use Latin characters.
>=20
> I could be wrong, but I do not believe there exists any country in the
> world where literate people are not familiar with the Latin alphabet.
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_32E7DA58-C728-497B-BD13-D9661F634E19
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXj0wAAAoJEINeeBNmFjV5ZAoP/jnvkAenNgYDTRrQ9lLnYEej
GUDBKT5OLp7N8+O8dGsICtT9b6g7WIZedpy8FXxIcL6//Ndr0Qj1lILRBq4iVExr
wyeyWWwPQx830nLhnjhDOjX8FA4LyOVYPjnRiw2KAUc+CWQArhM4A4QXiXZkrJNg
/0utnf4/mmXBWeaP9yqFyCQcCxhyw/O6+c7jnpbQNExcJo1PuQuzGe0p4nG0WZ+9
Jx8obrjshClOkm7t4KKy6VLCI+9o0icIh80HQV9UAMCP1zZ+2Gne/ILV5S5viLlL
m3cPM8EVA+bduyL06Ky6/39hhrzzc2bElXAhKOPsYP8/z9MWePiqMJPtDALOh59V
wmq3qKVfHXFDzWi7H+XWCnOGnZy/Axb4GYPRdY5lL0er3OhlpbTVEa8DWUW9XrGc
qGpCbcdA6mx6MMEe5GwUGqcR1Vuh//a5yuhdQKH6V1IClyaIVQKLYLiufoNfdMFg
4ktNEuIGP2kemTcRV2UAaCScnsV/1fzAe5HnKy6H4yQolpVzs21Ix1o4t9VEvVLn
OGv/S9XAKk/RscD11vVNkS8fD7dCxnDIPLMFRL0iN6L7KO/Hkl83o+0bnlTM48jA
/g2/TLQnoTDhcZSubrk9py6Wcc+9IfXeGei3VXz8QySVz9Kx8AwqVBzbKPYtArdM
bb7tC9FDe6s/OCog54DZ
=5lU9
-----END PGP SIGNATURE-----

--Apple-Mail=_32E7DA58-C728-497B-BD13-D9661F634E19--


From nobody Wed Jul 20 03:04:43 2016
Return-Path: <suzworldwide@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E9612D0A5 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BtcWlGpJer6y for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:04:40 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1348812D095 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:04:40 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id o80so60974519wme.1 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2jdSBDkxhh56+hahuHmhG2WLEaQmt0Bsm9ozPn5QGWM=; b=bBNlPpHdOELi2OT+drbVM7JkLcF0qhkNOqwlExeFceGzE8VhBtnropMAkwW0YnPunx Er/gRTOT7kR0r6lkXO9sSyZ94s8KSqfJBhRanuq8ufz69k50naLkDCRqIm9mVB3bub9x Tw/ZI22QcjDawNIu+eXPeCbkX+PhQUWyfNUiUeNG8uc3h32bkLVtVFHnlKJ3lBg36fIP Gg4v5DeVYQ7YV0twArxf5oeuTtTRM6aKYyzqrY6I1Tj0OyDlwx2Jgzx7GY3t4Q7zGjag +t2ja77gFBrdhPy+Jkv2NOKkyM1PSVCCOqmYmn2Posll0r0AH6fuw/IWEPftRw/xXWxy BYJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2jdSBDkxhh56+hahuHmhG2WLEaQmt0Bsm9ozPn5QGWM=; b=iQP+YaBD6E3zXSqnekxoNg6E1FUyfQl9rxPyG2mha0BdILrc8ACyrCnK1MadwJK7yw CsY/9ow8y/X9XRCeMLyhPM/8i5QeHnvLfXPY32gczXJrdKKNojQnbjVdgbxDK2KiEBVs VQGaDXbsbPS1OkGq/5MgdE/BXT7giJhR7zD+pQnPeYRZZd5Z/0r2FkeS52JSNiCoj9UM HKnzRpUJBCnstw1s4/3rQ7B0oJO22V3nNU6lUUQxbj08b2JcWmHfm0kRW0gzSsboZIj3 oauK9cyrMTP0pB+oTQle3d+oMz6oK5MWtHs2K4OfLTDhACmF+l64SLveJF8ztBzdtlws Di5g==
X-Gm-Message-State: ALyK8tJ6z504p9OfioESIIVOw6CtJK/PBAW4q6c3rWquAj1Iq49uULvOj3Gyt0Q+sc3q8w==
X-Received: by 10.194.62.97 with SMTP id x1mr460196wjr.79.1469009078437; Wed, 20 Jul 2016 03:04:38 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:550d:3481:f63c:d3ca? ([2001:67c:370:176:550d:3481:f63c:d3ca]) by smtp.gmail.com with ESMTPSA id e4sm421266wjy.20.2016.07.20.03.04.36 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jul 2016 03:04:37 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 20 Jul 2016 06:04:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <62B7FA8E-E696-4F30-9838-9478419BEEE9@gmail.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/mHWbHvFySG4gnwrkq9GPTkDVQBw>
Cc: homenet@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:04:42 -0000

> On Jul 20, 2016, at 5:50 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>>> We want something short and memorable.  ".co.uk" is short and =
memorable.
>>> ".univ-paris-diderot.fr" is not.
>=20
>> Why?  This is, I suspect, part of the issue: it seems that we have
>> some assumptions about the use of these names, and I'm not entirely
>> sure what they are.  It is not obvious to me that "short and
>> memorable" is a requirement that falls out of section 3.7 of RFC =
7368.
>=20
> I suggest we put this question to the WG.  Perhaps the chairs would be
> willing to ask whether the WG would prefer a name that is short and
> memorable, or one that is long and impossible to remember?

Plenty of useful names=E2=80=94 domain names and otherwise=E2=80=94 are =
neither short nor memorable. Some are one but not the other. And while =
=E2=80=9Cshort=E2=80=9D is an objectively quantifiable property, =
=E2=80=9Cmemorable=E2=80=9D is quite a lot fuzzier.=20

I admit I=E2=80=99m still not sure who=E2=80=99s going to see these =
names, so I don=E2=80=99t know for whom they=E2=80=99re intended to be =
memorable.

Which leads me to wonder why =E2=80=9Cshort, memorable, already known to =
be polluted by other uses, and already the subject of an allocation =
process in another organization=E2=80=9D is preferable to =E2=80=9Cshort, =
memorable, highly likely to be conflict-free, and uncontroversial=E2=80=9D=
?

I still hope for answers to the questions several of us have now asked =
repeatedly about how these names will be used. So far, I=E2=80=99ve =
heard repeatedly why =E2=80=9Chome=E2=80=9D is believed to be an =
acceptable string to serve this purpose. What continues to confuse me is =
why it=E2=80=99s apparently believed to be the one and only acceptable =
string, or even the most preferred one.



Suzanne



From nobody Wed Jul 20 03:06:05 2016
Return-Path: <brian@innovationslab.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D29B212D095 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:06:03 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 5V4Ybt-1EBge for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:06:01 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B87712DAE4 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:06:01 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 440C2880D1 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:06:01 -0700 (PDT)
Received: from dhcp-b3c7.meeting.ietf.org (unknown [IPv6:2001:67c:370:176:fca7:d020:9d19:a955]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id CFADF3280ADF for <homenet@ietf.org>; Wed, 20 Jul 2016 03:06:00 -0700 (PDT)
To: homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net>
Date: Wed, 20 Jul 2016 06:05:54 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CIMGx5n2QvJQ5LhofClI45BRI0Cf9FnWF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/xO_IKt51qm8M5t71hSC_9JVj0mA>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:06:04 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CIMGx5n2QvJQ5LhofClI45BRI0Cf9FnWF
Content-Type: multipart/mixed; boundary="x5e3vBLtEERbjGh6vsu86LxKhunKc4iri"
From: Brian Haberman <brian@innovationslab.net>
To: homenet@ietf.org
Message-ID: <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net>
Subject: Re: [homenet] RFC 7788 and ".home"
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
 <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr>
 <20160720091034.GA48086@mx2.yitter.info>
 <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
 <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
In-Reply-To: <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>

--x5e3vBLtEERbjGh6vsu86LxKhunKc4iri
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 7/20/16 6:01 AM, Ralph Droms wrote:
>=20
>> On Jul 20, 2016, at 11:50 AM 7/20/16, Juliusz Chroboczek
>> <jch@pps.univ-paris-diderot.fr> wrote:
>>=20
>>>> We want something short and memorable.  ".co.uk" is short and
>>>> memorable. ".univ-paris-diderot.fr" is not.
>>=20
>>> Why?  This is, I suspect, part of the issue: it seems that we
>>> have some assumptions about the use of these names, and I'm not
>>> entirely sure what they are.  It is not obvious to me that "short
>>> and memorable" is a requirement that falls out of section 3.7 of
>>> RFC 7368.
>>=20
>> I suggest we put this question to the WG.  Perhaps the chairs would
>> be willing to ask whether the WG would prefer a name that is short
>> and memorable, or one that is long and impossible to remember?
>=20
> I think there are some important questions to answer first:
>=20
> What is the meaning of .home and, precisely, how will names that end
> in .home be resolved?
>=20
> Where and by whom will this label actually be used?  What is the
> research to back up the answer?
>=20
> Although many people have given me a answer to the first question,
> and the answers often include phrases like "it just means..." or
> "everybody agrees that..." or "it's obvious...", I don't think I've
> seen a citable definition for the intention and semantics of .home;
> pointers welcome.
>=20
> Without that definition, I don't think I know where and by whom the
> label will actually be used.  Will it turn out to be like .local,
> which, as far as I know, is rarely used anywhere and only ever by a
> certain class of expert user.
>=20

If the above holds, I would suggest (only partly in jest) a TLD that
contains a certain unicode value that can be visually displayed by an OS.=
=2E.

http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0

Regards,
Brian


--x5e3vBLtEERbjGh6vsu86LxKhunKc4iri--

--CIMGx5n2QvJQ5LhofClI45BRI0Cf9FnWF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJXj00HAAoJEBOZRqCi7goqk2YIAKrDyWUYL1kUfGTkVWlry0Ra
Lw/IgzHveKd7M0Rffu3FF+odBkSnp61nReo8MmOm40912CFZd69jS0Ux5HUjHmMY
oVujEy2kgf6sHvChl4tvnN8zchWkgZsK7B+oHAOxXhlFgMFSOSl0xtk94wFkjBiN
f6JV7erdbXV4ZfRuEuFJHVnGkOR66LxLiHp2lm257C/z8LOEW0u32Pe/8ssujFmd
U0ZLc6CODYmkK4BFu2L7tRUtRXLDFx2yHV5eHOsXOZhdR+oQrLZqDxx3ZpP1ZwV7
S9jRYLACjtuE/QSaRqbHBuYKhfvvIx5V6phZe3/Is4DLO2tAA7iM8p0nb75zLkE=
=uolC
-----END PGP SIGNATURE-----

--CIMGx5n2QvJQ5LhofClI45BRI0Cf9FnWF--


From nobody Wed Jul 20 03:23:12 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E926312DB02 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:23:11 -0700 (PDT)
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 autolearn_force=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 j9GP6WSEVXnv for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:23:09 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id E7D0E12DB41 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:22:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 5465D10D2D for <homenet@ietf.org>; Wed, 20 Jul 2016 10:22:32 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aefIgu_uqjCo for <homenet@ietf.org>; Wed, 20 Jul 2016 10:22:31 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2001:67c:1231:998:c43a:cbfe:559a:1f82]) by mx2.yitter.info (Postfix) with ESMTPSA id 7297010BCD for <homenet@ietf.org>; Wed, 20 Jul 2016 10:22:31 +0000 (UTC)
Date: Wed, 20 Jul 2016 06:22:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160720102228.GB48306@mx2.yitter.info>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/adGTb6FRuJyC5OCDyougQOg8LlE>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:23:12 -0000

On Wed, Jul 20, 2016 at 11:50:05AM +0200, Juliusz Chroboczek wrote:
> willing to ask whether the WG would prefer a name that is short and
> memorable, or one that is long and impossible to remember?

I think the questions that Suz and Ralph have already posted are ones
that must be answered first.  But â€¦

> tends to cause problems).  My sample is certainly biased, but these are
> first year students at a non-elite university (no tuition fees), so they
> are probably representative of the public we're aiming for.

First year students in what, pray tell?  For I note that anyone who
works with any regularity on anything like computer code needs to have
some facility with Latin characters.  There was a presentation in the
HRPC RG in Buenos Aires claiming that this was a serious problem that
needed to be addressed.  I don't know that I agree, but it is a
significant difference between those who work with code and those who
merely want to be able to use their computers and networks.

> I could be wrong, but I do not believe there exists any country in the
> world where literate people are not familiar with the Latin alphabet.

"Familiar with the Latin alphabet" is hardly the point.  If your
writing system goes right to left, for instance, then plopping left to
right text into it is at least a pain in the neck and at worst a
significant source of bugs and security problems.  If I normally write
in Arabic, and use domain names that have U-labels in Arabic, then
suddenly running into a label "home" is going to make a mess.

Internationalization isn't hard because people doing it are morons.
It's hard in part because protocol elements that leak into user
interfaces haul in a whole bunch of UI considerations that the IETF is
traditionally very bad at.

Best regards.

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Jul 20 03:24:48 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09AB012D8DD for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:24:47 -0700 (PDT)
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 autolearn_force=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 odZrzevhINjQ for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:24:34 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id D2C8B12B020 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:24:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 962AB10D3A for <homenet@ietf.org>; Wed, 20 Jul 2016 10:24:34 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hGFk8k7HwV5 for <homenet@ietf.org>; Wed, 20 Jul 2016 10:24:33 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2001:67c:1231:998:c43a:cbfe:559a:1f82]) by mx2.yitter.info (Postfix) with ESMTPSA id 85DB710BCD for <homenet@ietf.org>; Wed, 20 Jul 2016 10:24:33 +0000 (UTC)
Date: Wed, 20 Jul 2016 06:24:30 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160720102430.GC48306@mx2.yitter.info>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nQxDQGNmnS6efLAS3v0FG08JE7Q>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:24:47 -0000

On Wed, Jul 20, 2016 at 06:05:54AM -0400, Brian Haberman wrote:
> If the above holds, I would suggest (only partly in jest) a TLD that
> contains a certain unicode value that can be visually displayed by an OS...
> 
> http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0

This is the second time this has been suggested, actually, and the
only problem with it is that anything not somehow a letter or digit
isn't permitted under IDNA2008, which means that no emoji are allowed.
(There are actually good reasons for this -- it turns out to be hard
to read emoji out loud, for instance.)

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Jul 20 03:32:37 2016
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEFB12DB23 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.187
X-Spam-Level: 
X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 i0g6HdAMdW_r for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:32:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FC5F12DB25 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:32:34 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:58de:bb5c:fc4a:1f99]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u6KAWUFT022663 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 20 Jul 2016 10:32:31 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2001:67c:370:176:58de:bb5c:fc4a:1f99] claimed to be dhcp-b257.meeting.ietf.org
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net> <20160720102430.GC48306@mx2.yitter.info>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <1a8de9f2-ecb5-e1da-7467-c53e70e01cb5@bogus.com>
Date: Wed, 20 Jul 2016 12:32:29 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
In-Reply-To: <20160720102430.GC48306@mx2.yitter.info>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGkHhHxs767R1lEgAv8MnngGUU7BGeUrk"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/CJ8xkp0HpS76lYC_4bJ9Def8scQ>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:32:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MGkHhHxs767R1lEgAv8MnngGUU7BGeUrk
Content-Type: multipart/mixed; boundary="uIW5F5Odgt0ex3T1GEUNd2BLLEGm0LL1X"
From: joel jaeggli <joelja@bogus.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, homenet@ietf.org
Message-ID: <1a8de9f2-ecb5-e1da-7467-c53e70e01cb5@bogus.com>
Subject: Re: [homenet] RFC 7788 and ".home"
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com>
 <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr>
 <20160720091034.GA48086@mx2.yitter.info>
 <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr>
 <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
 <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net>
 <20160720102430.GC48306@mx2.yitter.info>
In-Reply-To: <20160720102430.GC48306@mx2.yitter.info>

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

On 7/20/16 12:24 PM, Andrew Sullivan wrote:
> On Wed, Jul 20, 2016 at 06:05:54AM -0400, Brian Haberman wrote:
>> If the above holds, I would suggest (only partly in jest) a TLD that
>> contains a certain unicode value that can be visually displayed by an =
OS...
>>
>> http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0
>=20
> This is the second time this has been suggested, actually, and the
> only problem with it is that anything not somehow a letter or digit
> isn't permitted under IDNA2008, which means that no emoji are allowed.
> (There are actually good reasons for this -- it turns out to be hard
> to read emoji out loud, for instance.)

=E5=AE=B6 become homograph attacks are grand

> Best regards,
>=20
> A
>=20



--uIW5F5Odgt0ex3T1GEUNd2BLLEGm0LL1X--

--MGkHhHxs767R1lEgAv8MnngGUU7BGeUrk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iEYEARECAAYFAlePUz0ACgkQ8AA1q7Z/VrJDQgCfZ4jvMGMGz0tUB1CDq0OkM9NN
DYsAmwWcUpEDzy+wjKR8lxnKcrtS/DK5
=erXY
-----END PGP SIGNATURE-----

--MGkHhHxs767R1lEgAv8MnngGUU7BGeUrk--


From nobody Wed Jul 20 03:42:35 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA52012DB5B for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 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, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HnrzPp1izahW for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 03:42:32 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA7212DB45 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:42:20 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id 52so23863067qtq.3 for <homenet@ietf.org>; Wed, 20 Jul 2016 03:42:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=30AlZOUrfBv71z7EyZ2appYRi1DiOYOIeYgsmRPh1tI=; b=WnhlmQ+wiborNCvoraOfPct+GstkMJMUID5apfxju07mh/OvkNcvW7nMdQq3T117wj g43aXT7qytH/rIxh/9o7SWvLee4MySrCqrEkWhSejngczuggXcHFt5hMplfQDMmYnC+P dmC+qyUa74OrQdMmwuCMw5qEi1oq1sgJTZ9Wj9se+3+cvUweo1vEWPwvoWod5Nk6A/Cp 5aSJbtyQtV64aYs5GZxTsdklYtl/7pQUvsdoA+OF2DdmE70ch+D3Swz8ht3i+X673/ik oj70o6vhB4EQQbCtb8C8qwdbHJdnVTVd+G9o5RCbITGLf49brd3MDCVs5ycVdW5+9Dka uSJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=30AlZOUrfBv71z7EyZ2appYRi1DiOYOIeYgsmRPh1tI=; b=Vt1foYZJtQzkTFSb9T+ATGUUmhAIo49O7WLj8jTHJuKLYy/tSs9FhUsLTkSsEw1Hsa Ne/mHooYCXd01ybn80NsZaF6tMXrB+lDncPmA/ZslCK7Y/QJkYbWP7qdIGWmvv3qzKUq YMdXLFt62XMg+oMW6rT+D8WZLZwYku3aHkjwpsrNozr1+P5NLRvYbrdpZ0LdjZetdt7U HDM7AeD419lyLXuEGx87njyR3pZWgfiU2XdEY510J2toSSXYvOx4pkx8r/6spOiYXpdD +PUadGNTAtIgsHirtUMRdL9h9UYTrR9vov6p2ziJlgCMepwcGPgRJEyMMGQo+g2EakuG RKjw==
X-Gm-Message-State: ALyK8tK/ObcI1xdOAfdmBALVGQboN62S81IJMPH6IpUCLXY2s2HrIfa5zoBnM+sfGg9pbQ==
X-Received: by 10.237.53.19 with SMTP id a19mr67311666qte.67.1469011339590; Wed, 20 Jul 2016 03:42:19 -0700 (PDT)
Received: from ?IPv6:2001:420:c0c4:1002::c? ([2001:420:c0c4:1002::c]) by smtp.gmail.com with ESMTPSA id s52sm1094016qtc.4.2016.07.20.03.42.18 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jul 2016 03:42:18 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/html; charset=us-ascii
X-Apple-Auto-Saved: 1
X-Apple-Mail-Remote-Attachments: YES
From: Ralph Droms <rdroms.ietf@gmail.com>
X-Apple-Base-Url: x-msg://70/
In-Reply-To: <20160720102430.GC48306@mx2.yitter.info>
X-Apple-Windows-Friendly: 1
Date: Wed, 20 Jul 2016 12:41:09 +0200
X-Apple-Mail-Signature: SKIP_SIGNATURE
Content-Transfer-Encoding: quoted-printable
Message-Id: <661113BC-DE68-4C7F-B2B2-FB108057F511@gmail.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net> <20160720102430.GC48306@mx2.yitter.info>
To: HOMENET <homenet@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Rr5e50k8xLl_5jzW_ymuzKw4fik>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 10:42:33 -0000

<html><head></head><body dir=3D"auto" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><blockquote type=3D"cite">On Jul 20, 2016, at =
12:24 PM 7/20/16, Andrew Sullivan &lt;ajs@anvilwalrusden.com&gt; =
wrote:<br><br>On Wed, Jul 20, 2016 at 06:05:54AM -0400, Brian Haberman =
wrote:<br><blockquote type=3D"cite">If the above holds, I would suggest =
(only partly in jest) a TLD that<br>contains a certain unicode value =
that can be visually displayed by an =
OS...<br><br>http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0<br></b=
lockquote><br>This is the second time this has been suggested, actually, =
and the<br>only problem with it is that anything not somehow a letter or =
digit<br>isn't permitted under IDNA2008, which means that no emoji are =
allowed.<br>(There are actually good reasons for this -- it turns out to =
be hard<br>to read emoji out loud, for =
instance.)<br></blockquote><br>Perhaps we could use the punycode, =
xn--um8h? &nbsp;That choice would be wonderfully ironic in that the only =
people who ever use the label will get the joke...<br><br><blockquote =
type=3D"cite"><br>Best regards,<br><br>A<br><br>--<br>Andrew =
Sullivan<br>ajs@anvilwalrusden.com<br><br>________________________________=
_______________<br>homenet mailing =
list<br>homenet@ietf.org<br>https://www.ietf.org/mailman/listinfo/homenet<=
br></blockquote><br></body></html>=


From nobody Wed Jul 20 04:15:40 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE1A12D0DF for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 04:15:38 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 7NWn-x0y_628 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 04:15:36 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B50212D1A1 for <homenet@ietf.org>; Wed, 20 Jul 2016 04:15:35 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id l69so35820655lfg.1 for <homenet@ietf.org>; Wed, 20 Jul 2016 04:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NdxDtW2ZRhoXOjikLjn8Ks6m+uhaI7IryiDFqE/Cvww=; b=ZonTjr0c0z56NufKdq7bCWtd8AhbeMTToOlT4c9XGRLr2iPPiY3KGj9BKlVBoZyNdE 78f84Lc36JT+rDZrjUaKouu/h3+lzDfamG3QOyqz2MPMSb/rs0bVYHIP4IMOd+kcXUog yFPRR5jDgl8CrTtYCa9Rrga1DUki65pcNiAF+DlalqsZC+7X5hBAC9iUx+8JLFO5XnQh pG6u9ZBRhaJrSZfgpjddjpSW5V8gLxuxaJRANxCW00VN+APGZ3uNz5De3xfeUC3s+dmE MFDrmIaHI0A5rrEY1CRXwy4SagJZZjvGpiN2X37p0LiB4XWQ9UxmSGax/v8idngqhZBX Vfqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=NdxDtW2ZRhoXOjikLjn8Ks6m+uhaI7IryiDFqE/Cvww=; b=aCa5tEE1TaYbtO5KRDr/+N3Sj2WPouBD6eIsBsVpI2s9TWegyZr0J/deIQ3h41CK+x uNqx2MSMBWsUadSuFMFfy491F3Sk+8sK/r1Uk66rn5TbwJbAEqY/bpQjSxN6StpwmxW1 7cT8tWt6blSmJHzBparFflaP+N9i2HBYPn/fleaI+0IurilUguU1r+U9Uc5IJxmq6GM5 YxwDgI23WBREhwOBuALlVYuRNJw4MC18l3dBq2FdxiSp2mhTHgTmMXQ/wJMMtOES1NUH uPEGuMG1ukaybDwrKrZRvJrLTMb3gU+cVqfzDGXuEVTStUQEuCpaJX6SiB4B9X9T2oaZ L6xA==
X-Gm-Message-State: ALyK8tLxftAjn+hVF6dQq4BHbGNS4w9D1yG8VbiLQ6zYiCmN7hpyhX2bN8+OTZCI7oznsXggv0phgYnvzLsPEw==
MIME-Version: 1.0
X-Received: by 10.46.33.76 with SMTP id h73mr9024397ljh.41.1469013333431; Wed, 20 Jul 2016 04:15:33 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 04:15:32 -0700 (PDT)
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 04:15:32 -0700 (PDT)
In-Reply-To: <661113BC-DE68-4C7F-B2B2-FB108057F511@gmail.com>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <38e38abc-246d-10c7-d1d3-bce3bd1022aa@innovationslab.net> <20160720102430.GC48306@mx2.yitter.info> <661113BC-DE68-4C7F-B2B2-FB108057F511@gmail.com>
Date: Wed, 20 Jul 2016 13:15:32 +0200
Message-ID: <CAPt1N1m9uFwGidHnOZmSQf0OxxV6XTW+8JQTT2h97JRAiX9iYg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a1142c632e8e99a05380f5160
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/5qQRMwcBTfVsrhxy9xl2wUfX4Zg>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 11:15:38 -0000

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

The name should be short, easily recognized, and make some kind of sense.
It is important that the name look reasonable because we want the natural
human pattern matching ability that nearly all users can be expected to
have to notice when someone uses a name that is not quite correct, and to
not reject the name because it looks weird.

Honestly, discussions like this make me feel genuine despair for the IETF.
Why do we keep having this silly argument?  I was up until two in the
morning last night because I couldn't let go of the sorrow and frustration
that I feel about being forced to have this discussion again when we are
already doing with to address this problem in a different working group,
and we already had the same discussion over .onion.

Why do we need to talk this through again?

On Jul 20, 2016 12:42, "Ralph Droms" <rdroms.ietf@gmail.com> wrote:

>
> On Jul 20, 2016, at 12:24 PM 7/20/16, Andrew Sullivan <
> ajs@anvilwalrusden.com> wrote:
>
> On Wed, Jul 20, 2016 at 06:05:54AM -0400, Brian Haberman wrote:
>
> If the above holds, I would suggest (only partly in jest) a TLD that
> contains a certain unicode value that can be visually displayed by an OS...
>
> http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0
>
>
> This is the second time this has been suggested, actually, and the
> only problem with it is that anything not somehow a letter or digit
> isn't permitted under IDNA2008, which means that no emoji are allowed.
> (There are actually good reasons for this -- it turns out to be hard
> to read emoji out loud, for instance.)
>
>
> Perhaps we could use the punycode, xn--um8h?  That choice would be
> wonderfully ironic in that the only people who ever use the label will get
> the joke...
>
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<p dir=3D"ltr">The name should be short, easily recognized, and make some k=
ind of sense. It is important that the name look reasonable because we want=
 the natural human pattern matching ability that nearly all users can be ex=
pected to have to notice when someone uses a name that is not quite correct=
, and to not reject the name because it looks weird. </p>
<p dir=3D"ltr">Honestly, discussions like this make me feel genuine despair=
 for the IETF. Why do we keep having this silly argument?=C2=A0 I was up un=
til two in the morning last night because I couldn&#39;t let go of the sorr=
ow and frustration that I feel about being forced to have this discussion a=
gain when we are already doing with to address this problem in a different =
working group, and we already had the same discussion over .onion.</p>
<p dir=3D"ltr">Why do we need to talk this through again?</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 20, 2016 1=
2:42, &quot;Ralph Droms&quot; &lt;<a href=3D"mailto:rdroms.ietf@gmail.com">=
rdroms.ietf@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div dir=3D"auto" style=3D"word-wrap:break-word"><br><bloc=
kquote type=3D"cite">On Jul 20, 2016, at 12:24 PM 7/20/16, Andrew Sullivan =
&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwa=
lrusden.com</a>&gt; wrote:<br><br>On Wed, Jul 20, 2016 at 06:05:54AM -0400,=
 Brian Haberman wrote:<br><blockquote type=3D"cite">If the above holds, I w=
ould suggest (only partly in jest) a TLD that<br>contains a certain unicode=
 value that can be visually displayed by an OS...<br><br><a href=3D"http://=
apps.timwhitlock.info/unicode/inspect/hex/1F3E0" target=3D"_blank">http://a=
pps.timwhitlock.info/unicode/inspect/hex/1F3E0</a><br></blockquote><br>This=
 is the second time this has been suggested, actually, and the<br>only prob=
lem with it is that anything not somehow a letter or digit<br>isn&#39;t per=
mitted under IDNA2008, which means that no emoji are allowed.<br>(There are=
 actually good reasons for this -- it turns out to be hard<br>to read emoji=
 out loud, for instance.)<br></blockquote><br>Perhaps we could use the puny=
code, xn--um8h?=C2=A0 That choice would be wonderfully ironic in that the o=
nly people who ever use the label will get the joke...<br><br><blockquote t=
ype=3D"cite"><br>Best regards,<br><br>A<br><br>--<br>Andrew Sullivan<br><a =
href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden=
.com</a><br><br>_______________________________________________<br>homenet =
mailing list<br><a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homen=
et@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><br></div>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
<br></blockquote></div></div>

--001a1142c632e8e99a05380f5160--


From nobody Wed Jul 20 04:33:38 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F321812D52B for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 04:33:36 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 e9cE92iXv70o for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 04:33:34 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48AC712D544 for <homenet@ietf.org>; Wed, 20 Jul 2016 04:33:26 -0700 (PDT)
Received: from dhcp-b14e.meeting.ietf.org ([31.133.177.78]:51759) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bPpkh-0004q0-P9 (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Wed, 20 Jul 2016 12:33:23 +0100
To: homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk>
Date: Wed, 20 Jul 2016 13:33:25 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/5xOLoSZXfYzD6nC_viK1wXZ4EZA>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 11:33:37 -0000

On 20/07/2016 12:01, Ralph Droms wrote:

> Without that definition, I don't think I know where and by whom the
> label will actually be used.  Will it turn out to be like .local,
> which, as far as I know, is rarely used anywhere and only ever by a
> certain class of expert user.

<nohat>

I have three devices in my home that have web interfaces that are
accessible as http://<devicename>.local/ because they support Bonjour.

That URL is visible in the browser address bar, and not hidden away in
some device-specific control panel (e.g. the Printer chooser).  One of
those devices is a printer, and is therefore _also_ accessible like
that, hiding the '.local', but the other two are primarily accessed via
a browser.

Since those URLs must also be bookmarkable and because devices might
move around the network, any solution that mandates any subnet-specific
naming scheme would be unacceptable.

My expectation is that in a Homenet multi-subnet environment I will be
able to just use http://<device>.<TBD>/ and just have it work regardless
of which particular subnet that device is on [*].

It's also important to me that I be able to type those addresses in, and
for me that rules out the Unicode house symbol.

<still nohat>

I've previously argued that '.home' is fine for our purposes - I'm
coming around to the argument that it's better to start with a
greenfield "TBD" than to risk any conflict.

Ray

[*] notwithstanding name-collision issues...


From nobody Wed Jul 20 05:10:11 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D57212DBB2 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 05:10:09 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 LW55yVtNUpxP for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 05:10:08 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA63112DBB1 for <homenet@ietf.org>; Wed, 20 Jul 2016 05:10:07 -0700 (PDT)
Received: from dhcp-b14e.meeting.ietf.org ([31.133.177.78]:52429) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bPqKC-0005b9-OJ (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Wed, 20 Jul 2016 13:10:04 +0100
To: homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk>
Date: Wed, 20 Jul 2016 14:10:05 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/kIRmEzPDq0hGYjJjiZhg3vwkC8I>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 12:10:09 -0000

On 20/07/2016 13:33, Ray Bellis wrote:

> My expectation is that in a Homenet multi-subnet environment I will be
> able to just use http://<device>.<TBD>/ and just have it work regardless
> of which particular subnet that device is on [*].

<really still no hat>

There's a further corollary to this:  since we can't mandate host
changes, the resolution of that name MUST be unicast DNS to an *on-net*
resolver.

Having different resolvers for different parts of the namespace is a bad
idea [*] so furthermore that resolver must also be capable of handling
queries received for the global namespace (whether by forwarding to an
off-net resolver, or performing full iterative resolution itself).

Ray

[ Current host stacks don't have support for saying "if the suffix is
".TBD", go here, otherwise go there.  If you have one resolver for
".TDB" and another for everything else and then just send all queries to
both, you still need host changes to cope with how you'll get a valid
answer from one but not the other ]


From nobody Wed Jul 20 05:55:12 2016
Return-Path: <equinox@diac24.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5168D12D5BD; Wed, 20 Jul 2016 05:55:08 -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] autolearn=ham autolearn_force=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 0ZdNgMzVKdt4; Wed, 20 Jul 2016 05:55:04 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CBF012D611; Wed, 20 Jul 2016 05:55:04 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from <equinox@diac24.net>) id 1bPr1e-000Gou-NJ; Wed, 20 Jul 2016 14:55:00 +0200
Date: Wed, 20 Jul 2016 14:54:58 +0200
From: David Lamparter <equinox@diac24.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>, homenet <homenet@ietf.org>
Message-ID: <20160720125458.GO255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="L6iaP+gRLNZHKoI4"
Content-Disposition: inline
In-Reply-To: <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/-StwyMwlpwkQipwkVtE8Xqy3YyA>
Cc: Jen Linkova <furry@google.com>, "Fred Baker \(fred\)" <fred@cisco.com>, Chris Bowers <cbowers@juniper.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 12:55:08 -0000

--L6iaP+gRLNZHKoI4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

As mentioned on mic during rtgwg, I think the idea of affecting host
source address selection through 6724 rule 5.5 is potentially very
useful and IMHO should be explored.

Hence, I hacked it up for the Linux (4.5.0) kernel; patches are attached
to this mail.  I've been able to gleam a little more detail on the idea:

- it's a bit unclear how an address/prefix's "source" next-hop is kept
  in association.  The simplistic approach of adding a "PA source ipv6
  address" for each of a host's configured addresses falls flat when
  more than 1 router advertises the same prefix, so I implemented it as
  a list -- however, my hack never removes entries off that.  It should
  possibly have a copy of the PA's valid time?

  (Read as: the "Discussion" note in 6724 is right on the mark - the
  details are not quite specified.)

- in that avenue, I don't think it's possible to store the information
  in a route-centric way, because RA lifetimes tend to be shorter.
  If a router goes away and comes back, it seems to me that the prefix's
  associated origin/nexthop should still be there.

- rule 5.5 makes RA preference carry into source address selection.  I
  think this is described in the draft, I just failed to grasp that from
  the presentation.  Very useful for getting source selection right in
  the face of unequal performance uplinks.

- if you want to manage this in an userspace process on Linux, you can
  simply update the route's preferred source attribute.

The attached patchset also has the following caveats that result from me
just doing a quick hack:
- there is no debugging/user visibility of the value
- as mentioned above, tracked source addresses never go away unless the
  entire address dies.  It caps at 4 sources (so you can't exhaust
  kernel memory by spoofing...)
- I should probably pass Linux's "dst" instead of "rt6_info"
- I didn't check for locking/concurrentness violations
- there's a const warning which I ignored.

Either way if anyone wants to tinker with it, here it is.
No warranties, YMMV.  You touch it, it becomes your responsibility ;)

Cheers,


-David

On Wed, Jul 06, 2016 at 04:33:18PM +0000, Fred Baker (fred) wrote:
> At IETF 94, this working group advised the routing ADs and Routing Working Group that PA multihoming would not work without a source/destination routing solution. This draft was developed in response. Routing Working Group requests v6ops review.
> 
> > Begin forwarded message:
> > 
> > From: <internet-drafts@ietf.org>
> > Subject: New Version Notification for draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
> > Date: July 5, 2016 at 5:58:25 PM PDT
> > To: Chris Bowers <cbowers@juniper.net>, Jen Linkova <furry@google.com>, "Fred Baker" <fred@cisco.com>, "J. Linkova" <furry@google.com>
> > 
> > 
> > A new version of I-D, draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
> > has been successfully submitted by Fred Baker and posted to the
> > IETF repository.
> > 
> > Name:		draft-bowbakova-rtgwg-enterprise-pa-multihoming
> > Revision:	00
> > Title:		Enterprise Multihoming using Provider-Assigned Addresses without Network Prefix Translation: Requirements and Solution
> > Document date:	2016-07-05
> > Group:		Individual Submission
> > Pages:		44
> > URL:            https://www.ietf.org/internet-drafts/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
> > Status:         https://datatracker.ietf.org/doc/draft-bowbakova-rtgwg-enterprise-pa-multihoming/
> > Htmlized:       https://tools.ietf.org/html/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00
> > 
> > 
> > Abstract:
> >  Connecting an enterprise site to multiple ISPs using provider-
> >  assigned addresses is difficult without the use of some form of
> >  Network Address Translation (NAT).  Much has been written on this
> >  topic over the last 10 to 15 years, but it still remains a problem
> >  without a clearly defined or widely implemented solution.  Any
> >  multihoming solution without NAT requires hosts at the site to have
> >  addresses from each ISP and to select the egress ISP by selecting a
> >  source address for outgoing packets.  It also requires routers at the
> >  site to take into account those source addresses when forwarding
> >  packets out towards the ISPs.
> > 
> >  This document attempts to define a complete solution to this problem.
> >  It covers the behavior of routers to forward traffic taking into
> >  account source address, and it covers the behavior of host to select
> >  appropriate source addresses.  It also covers any possible role that
> >  routers might play in providing information to hosts to help them
> >  select appropriate source addresses.  In the process of exploring
> >  potential solutions, this documents also makes explicit requirements
> >  for how the solution would be expected to behave from the perspective
> >  of an enterprise site network administrator .
> > 
> > 
> > 
> > 
> > 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
> > 
> 



> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--L6iaP+gRLNZHKoI4
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="0001-net-ipv6-track-autoconfigured-address-origin.patch"

>From 2d1bf126d3e776deabcab4ef8b6f941636b8bc67 Mon Sep 17 00:00:00 2001
From: David Lamparter <equinox@diac24.net>
Date: Wed, 20 Jul 2016 10:37:54 +0200
Subject: [PATCH 1/3] net/ipv6: track autoconfigured address' origin

---
 include/net/addrconf.h |  3 ++-
 include/net/if_inet6.h | 11 +++++++++++
 net/ipv6/addrconf.c    | 15 ++++++++++++++-
 net/ipv6/ndisc.c       |  3 ++-
 4 files changed, 29 insertions(+), 3 deletions(-)

diff --git a/include/net/addrconf.h b/include/net/addrconf.h
index 47f52d3..33f2652 100644
--- a/include/net/addrconf.h
+++ b/include/net/addrconf.h
@@ -226,7 +226,8 @@ static inline bool ipv6_is_mld(struct sk_buff *skb, int nexthdr, int offset)
 }
 
 void addrconf_prefix_rcv(struct net_device *dev,
-			 u8 *opt, int len, bool sllao);
+			 u8 *opt, int len, bool sllao,
+			 const struct in6_addr *source);
 
 /*
  *	anycast prototypes (anycast.c)
diff --git a/include/net/if_inet6.h b/include/net/if_inet6.h
index 1c8b682..f79faa9 100644
--- a/include/net/if_inet6.h
+++ b/include/net/if_inet6.h
@@ -38,6 +38,14 @@ enum {
 	INET6_IFADDR_STATE_DEAD,
 };
 
+/* for RFC6724 rule 5.5, we want to know what router advertised a prefix;
+ * however, there may be multiple such routers, so it needs to be a list.
+ * (think redundant default gateways)
+ *
+ * to prevent spoofed packets filling memory - and to keep this simple -
+ * this is a fixed-size list. */
+#define INET6_IFADDR_ORIGINRTR_MAX	4
+
 struct inet6_ifaddr {
 	struct in6_addr		addr;
 	__u32			prefix_len;
@@ -75,6 +83,9 @@ struct inet6_ifaddr {
 
 	struct rcu_head		rcu;
 	struct in6_addr		peer_addr;
+
+	size_t			origin_rtr_count;
+	struct in6_addr		origin_rtr[INET6_IFADDR_ORIGINRTR_MAX];
 };
 
 struct ip6_sf_socklist {
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index fd065f2..f148278 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -2338,7 +2338,19 @@ static bool is_addr_mode_generate_stable(struct inet6_dev *idev)
 	       idev->addr_gen_mode == IN6_ADDR_GEN_MODE_RANDOM;
 }
 
-void addrconf_prefix_rcv(struct net_device *dev, u8 *opt, int len, bool sllao)
+static void addr_register_origin(struct inet6_ifaddr *addr,
+				 const struct in6_addr *rtr)
+{
+	if (!rtr)
+		return;
+	if (addr->origin_rtr_count == ARRAY_SIZE(addr->origin_rtr))
+		return;
+	addr->origin_rtr[addr->origin_rtr_count] = *rtr;
+	addr->origin_rtr_count++;
+}
+
+void addrconf_prefix_rcv(struct net_device *dev, u8 *opt, int len, bool sllao,
+			 const struct in6_addr *source)
 {
 	struct prefix_info *pinfo;
 	__u32 valid_lft;
@@ -2556,6 +2568,7 @@ ok:
 			in6_ifa_put(ifp);
 			addrconf_verify();
 		}
+		addr_register_origin(ifp, source);
 	}
 	inet6_prefix_notify(RTM_NEWPREFIX, in6_dev, pinfo);
 	in6_dev_put(in6_dev);
diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
index 84afb9a..b298da6 100644
--- a/net/ipv6/ndisc.c
+++ b/net/ipv6/ndisc.c
@@ -1385,7 +1385,8 @@ skip_routeinfo:
 		     p = ndisc_next_option(p, ndopts.nd_opts_pi_end)) {
 			addrconf_prefix_rcv(skb->dev, (u8 *)p,
 					    (p->nd_opt_len) << 3,
-					    ndopts.nd_opts_src_lladdr != NULL);
+					    ndopts.nd_opts_src_lladdr != NULL,
+					    &ipv6_hdr(skb)->saddr);
 		}
 	}
 
-- 
2.7.3


--L6iaP+gRLNZHKoI4
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="0002-net-ipv6-add-ipv6_rt_get_saddr.patch"

>From 57c57fdc9ddbfa627660117d4d257e17dc4c6b3f Mon Sep 17 00:00:00 2001
From: David Lamparter <equinox@diac24.net>
Date: Wed, 20 Jul 2016 11:24:46 +0200
Subject: [PATCH 2/3] net/ipv6: add ipv6_rt_get_saddr()

---
 include/net/addrconf.h  |  3 +++
 net/ipv6/addrconf.c     | 26 +++++++++++++++++++++++---
 net/ipv6/fib6_rules.c   |  4 +---
 net/ipv6/route.c        |  3 +--
 net/ipv6/xfrm6_policy.c |  3 ++-
 5 files changed, 30 insertions(+), 9 deletions(-)

diff --git a/include/net/addrconf.h b/include/net/addrconf.h
index 33f2652..95cee9a 100644
--- a/include/net/addrconf.h
+++ b/include/net/addrconf.h
@@ -83,6 +83,9 @@ struct inet6_ifaddr *ipv6_get_ifaddr(struct net *net,
 int ipv6_dev_get_saddr(struct net *net, const struct net_device *dev,
 		       const struct in6_addr *daddr, unsigned int srcprefs,
 		       struct in6_addr *saddr);
+int ipv6_rt_get_saddr(struct net *net, const struct rt6_info *rt,
+		      const struct in6_addr *daddr, unsigned int srcprefs,
+		      struct in6_addr *saddr);
 int __ipv6_get_lladdr(struct inet6_dev *idev, struct in6_addr *addr,
 		      u32 banned_flags);
 int ipv6_get_lladdr(struct net_device *dev, struct in6_addr *addr,
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index f148278..b0aedd3 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -1287,6 +1287,7 @@ struct ipv6_saddr_dst {
 	int scope;
 	int label;
 	unsigned int prefs;
+	const struct in6_addr *nh;
 };
 
 static inline int ipv6_saddr_preferred(int type)
@@ -1518,9 +1519,11 @@ out:
 	return hiscore_idx;
 }
 
-int ipv6_dev_get_saddr(struct net *net, const struct net_device *dst_dev,
-		       const struct in6_addr *daddr, unsigned int prefs,
-		       struct in6_addr *saddr)
+static int __ipv6_rtdev_get_saddr(struct net *net, const struct rt6_info *rt,
+				  const struct net_device *dst_dev,
+				  const struct in6_addr *daddr,
+				  unsigned int prefs,
+				  struct in6_addr *saddr)
 {
 	struct ipv6_saddr_score scores[2], *hiscore;
 	struct ipv6_saddr_dst dst;
@@ -1537,6 +1540,7 @@ int ipv6_dev_get_saddr(struct net *net, const struct net_device *dst_dev,
 	dst.scope = __ipv6_addr_src_scope(dst_type);
 	dst.label = ipv6_addr_label(net, daddr, dst_type, dst.ifindex);
 	dst.prefs = prefs;
+	dst.nh = rt ? &rt->rt6i_gateway : NULL;
 
 	scores[hiscore_idx].rule = -1;
 	scores[hiscore_idx].ifa = NULL;
@@ -1599,8 +1603,24 @@ int ipv6_dev_get_saddr(struct net *net, const struct net_device *dst_dev,
 	in6_ifa_put(hiscore->ifa);
 	return 0;
 }
+
+int ipv6_dev_get_saddr(struct net *net, const struct net_device *dst_dev,
+		       const struct in6_addr *daddr, unsigned int prefs,
+		       struct in6_addr *saddr)
+{
+	return __ipv6_rtdev_get_saddr(net, NULL, dst_dev, daddr, prefs, saddr);
+}
 EXPORT_SYMBOL(ipv6_dev_get_saddr);
 
+int ipv6_rt_get_saddr(struct net *net, const struct rt6_info *rt,
+		      const struct in6_addr *daddr, unsigned int prefs,
+		      struct in6_addr *saddr)
+{
+	const struct net_device *dst_dev = ip6_dst_idev(&rt->dst)->dev;
+	return __ipv6_rtdev_get_saddr(net, rt, dst_dev, daddr, prefs, saddr);
+}
+EXPORT_SYMBOL(ipv6_rt_get_saddr);
+
 int __ipv6_get_lladdr(struct inet6_dev *idev, struct in6_addr *addr,
 		      u32 banned_flags)
 {
diff --git a/net/ipv6/fib6_rules.c b/net/ipv6/fib6_rules.c
index ed33abf..d91b6f5 100644
--- a/net/ipv6/fib6_rules.c
+++ b/net/ipv6/fib6_rules.c
@@ -104,9 +104,7 @@ static int fib6_rule_action(struct fib_rule *rule, struct flowi *flp,
 		    r->src.plen && !(flags & RT6_LOOKUP_F_HAS_SADDR)) {
 			struct in6_addr saddr;
 
-			if (ipv6_dev_get_saddr(net,
-					       ip6_dst_idev(&rt->dst)->dev,
-					       &flp6->daddr,
+			if (ipv6_rt_get_saddr(net, rt, &flp6->daddr,
 					       rt6_flags2srcprefs(flags),
 					       &saddr))
 				goto again;
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index ed44663..8e6218d 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -2546,8 +2546,7 @@ int ip6_route_get_saddr(struct net *net,
 	if (rt && rt->rt6i_prefsrc.plen)
 		*saddr = rt->rt6i_prefsrc.addr;
 	else
-		err = ipv6_dev_get_saddr(net, idev ? idev->dev : NULL,
-					 daddr, prefs, saddr);
+		err = ipv6_rt_get_saddr(net, rt, daddr, prefs, saddr);
 	return err;
 }
 
diff --git a/net/ipv6/xfrm6_policy.c b/net/ipv6/xfrm6_policy.c
index c074771..19005e6 100644
--- a/net/ipv6/xfrm6_policy.c
+++ b/net/ipv6/xfrm6_policy.c
@@ -64,7 +64,8 @@ static int xfrm6_get_saddr(struct net *net, int oif,
 		return -EHOSTUNREACH;
 
 	dev = ip6_dst_idev(dst)->dev;
-	ipv6_dev_get_saddr(dev_net(dev), dev, &daddr->in6, 0, &saddr->in6);
+	ipv6_rt_get_saddr(dev_net(dev), (struct rt6_info *)dst,
+			  &daddr->in6, 0, &saddr->in6);
 	dst_release(dst);
 	return 0;
 }
-- 
2.7.3


--L6iaP+gRLNZHKoI4
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="0003-net-ipv6-implement-RFC6724-addrconf-rule-5.5.patch"

>From f396b90dc6dfd36f282ba574c1add619d7345ad3 Mon Sep 17 00:00:00 2001
From: David Lamparter <equinox@diac24.net>
Date: Wed, 20 Jul 2016 11:25:23 +0200
Subject: [PATCH 3/3] net/ipv6: implement RFC6724 (addrconf) rule 5.5

---
 net/ipv6/addrconf.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index b0aedd3..64ea39d 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -1262,6 +1262,7 @@ enum {
 	IPV6_SADDR_RULE_HOA,
 #endif
 	IPV6_SADDR_RULE_OIF,
+	IPV6_SADDR_RULE_OIF_RTR,
 	IPV6_SADDR_RULE_LABEL,
 	IPV6_SADDR_RULE_PRIVACY,
 	IPV6_SADDR_RULE_ORCHID,
@@ -1312,6 +1313,7 @@ static int ipv6_get_saddr_eval(struct net *net,
 			       int i)
 {
 	int ret;
+	size_t j;
 
 	if (i <= score->rule) {
 		switch (i) {
@@ -1390,6 +1392,18 @@ static int ipv6_get_saddr_eval(struct net *net,
 		ret = (!dst->ifindex ||
 		       dst->ifindex == score->ifa->idev->dev->ifindex);
 		break;
+	case IPV6_SADDR_RULE_OIF_RTR:
+		/* Rule 5.5: Prefer prefixes announced by nexthop */
+		ret = 0;
+		if (!dst->nh)
+			break;
+		for (j = 0; j < score->ifa->origin_rtr_count; j++)
+			if (ipv6_addr_equal(&score->ifa->origin_rtr[j],
+					    dst->nh)) {
+				ret = 1;
+				break;
+			}
+		break;
 	case IPV6_SADDR_RULE_LABEL:
 		/* Rule 6: Prefer matching label */
 		ret = ipv6_addr_label(net,
-- 
2.7.3


--L6iaP+gRLNZHKoI4--


From nobody Wed Jul 20 05:59:06 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806E212D5FB; Wed, 20 Jul 2016 05:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 MBcwpunoVrjj; Wed, 20 Jul 2016 05:59:02 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6A8E12D5D5; Wed, 20 Jul 2016 05:59:01 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id f65so174741282wmi.0; Wed, 20 Jul 2016 05:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=OzCd7t8Y0IZmofuJnSKXszFz0oJUMlWWv6XYtgTb6hE=; b=pwFlhGS+XapXrTwRrgpscrU9LGED5ikY76m+VhbGXJHOv92GoqoBp3MG6ZVdSkOuv7 grNqrHf+Eh4iwG7nCuIKfQ5T49nIzWt338BSgR8HcJ3Rk2+EEzFwWaZZiJ0e3ahppoM4 Yg80d9v6Cf9+hFgxNcr2bCbO5kVCVnd09m6TOwY4V+li5FQ6BecmPsBsSf1mwUddSeMT 0rcECtiEXl36xOS/+k5Vbab/QAHSC748gT3VU9gtNFYpmJcaIU9c8YqsDeKWDgWj7uZn BpFWsa5VnlnRZhtbyzOdxK83EbsHVoO06zMFVKdjlcHjataqDMFx8gFlwIZLazo/CPeb Vyhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=OzCd7t8Y0IZmofuJnSKXszFz0oJUMlWWv6XYtgTb6hE=; b=Of87buMWY+soCliRhNH92LFIGOg6nUESisz+on49O4fMFmlJmFY44K2NB20yPPBgXX MepCFhEX0iww6bvGjyNSj24QnxTeB3vnax8eBxncXRWtrKCmSnFqP031OP0OGJWAJfMX ETtTm9Y/il5AmDKA6iaXDqBSydZXelq8NFdwZWijcvWkk2LGd+MPaOl8v/n7xutz1qDr 6QkkI0P/nSqNAOEdEdqEqG85BzlVUkZnNHCSbjqDfp3lTTWpH9n6Q6HjoKF60JoVM/0E TdO7/AlvtgbdCXE94Pr3yBkRJ4EzIss4OX/MYJccjdfmYPMiWQS04+vYJspdLCweIsDF eGxg==
X-Gm-Message-State: ALyK8tJ8FVQE+1bnsvp/GhZSR8a5IWkPbmkVg0MWcUy3OOdweSRa/BFNOvJG/lOwoA2j5g==
X-Received: by 10.28.182.136 with SMTP id g130mr10896707wmf.21.1469019540395;  Wed, 20 Jul 2016 05:59:00 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g184sm31428393wme.15.2016.07.20.05.58.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 05:58:59 -0700 (PDT)
To: David Lamparter <equinox@diac24.net>, "v6ops@ietf.org" <v6ops@ietf.org>, homenet <homenet@ietf.org>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6097913e-d9e3-82ae-56ef-0476347af4e9@gmail.com>
Date: Thu, 21 Jul 2016 00:59:05 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160720125458.GO255916@eidolon>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/JLOlIk_7D1p6OdTVTHchoQ4qp1Q>
Cc: Jen Linkova <furry@google.com>, Chris Bowers <cbowers@juniper.net>
Subject: Re: [homenet] [v6ops] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 12:59:04 -0000

On 21/07/2016 00:54, David Lamparter wrote:
> As mentioned on mic during rtgwg, I think the idea of affecting host
> source address selection through 6724 rule 5.5 is potentially very
> useful and IMHO should be explored.

And please note that draft-ietf-6man-multi-homed-host-07 (in IETF Last Call)
recommends hosts to support this, exactly to assist SADR solutions.

    Brian

> Hence, I hacked it up for the Linux (4.5.0) kernel; patches are attached
> to this mail.  I've been able to gleam a little more detail on the idea:
> 
> - it's a bit unclear how an address/prefix's "source" next-hop is kept
>   in association.  The simplistic approach of adding a "PA source ipv6
>   address" for each of a host's configured addresses falls flat when
>   more than 1 router advertises the same prefix, so I implemented it as
>   a list -- however, my hack never removes entries off that.  It should
>   possibly have a copy of the PA's valid time?
> 
>   (Read as: the "Discussion" note in 6724 is right on the mark - the
>   details are not quite specified.)
> 
> - in that avenue, I don't think it's possible to store the information
>   in a route-centric way, because RA lifetimes tend to be shorter.
>   If a router goes away and comes back, it seems to me that the prefix's
>   associated origin/nexthop should still be there.
> 
> - rule 5.5 makes RA preference carry into source address selection.  I
>   think this is described in the draft, I just failed to grasp that from
>   the presentation.  Very useful for getting source selection right in
>   the face of unequal performance uplinks.
> 
> - if you want to manage this in an userspace process on Linux, you can
>   simply update the route's preferred source attribute.
> 
> The attached patchset also has the following caveats that result from me
> just doing a quick hack:
> - there is no debugging/user visibility of the value
> - as mentioned above, tracked source addresses never go away unless the
>   entire address dies.  It caps at 4 sources (so you can't exhaust
>   kernel memory by spoofing...)
> - I should probably pass Linux's "dst" instead of "rt6_info"
> - I didn't check for locking/concurrentness violations
> - there's a const warning which I ignored.
> 
> Either way if anyone wants to tinker with it, here it is.
> No warranties, YMMV.  You touch it, it becomes your responsibility ;)
> 
> Cheers,
> 
> 
> -David
> 
> On Wed, Jul 06, 2016 at 04:33:18PM +0000, Fred Baker (fred) wrote:
>> At IETF 94, this working group advised the routing ADs and Routing Working Group that PA multihoming would not work without a source/destination routing solution. This draft was developed in response. Routing Working Group requests v6ops review.
>>
>>> Begin forwarded message:
>>>
>>> From: <internet-drafts@ietf.org>
>>> Subject: New Version Notification for draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
>>> Date: July 5, 2016 at 5:58:25 PM PDT
>>> To: Chris Bowers <cbowers@juniper.net>, Jen Linkova <furry@google.com>, "Fred Baker" <fred@cisco.com>, "J. Linkova" <furry@google.com>
>>>
>>>
>>> A new version of I-D, draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
>>> has been successfully submitted by Fred Baker and posted to the
>>> IETF repository.
>>>
>>> Name:		draft-bowbakova-rtgwg-enterprise-pa-multihoming
>>> Revision:	00
>>> Title:		Enterprise Multihoming using Provider-Assigned Addresses without Network Prefix Translation: Requirements and Solution
>>> Document date:	2016-07-05
>>> Group:		Individual Submission
>>> Pages:		44
>>> URL:            https://www.ietf.org/internet-drafts/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-bowbakova-rtgwg-enterprise-pa-multihoming/
>>> Htmlized:       https://tools.ietf.org/html/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00
>>>
>>>
>>> Abstract:
>>>  Connecting an enterprise site to multiple ISPs using provider-
>>>  assigned addresses is difficult without the use of some form of
>>>  Network Address Translation (NAT).  Much has been written on this
>>>  topic over the last 10 to 15 years, but it still remains a problem
>>>  without a clearly defined or widely implemented solution.  Any
>>>  multihoming solution without NAT requires hosts at the site to have
>>>  addresses from each ISP and to select the egress ISP by selecting a
>>>  source address for outgoing packets.  It also requires routers at the
>>>  site to take into account those source addresses when forwarding
>>>  packets out towards the ISPs.
>>>
>>>  This document attempts to define a complete solution to this problem.
>>>  It covers the behavior of routers to forward traffic taking into
>>>  account source address, and it covers the behavior of host to select
>>>  appropriate source addresses.  It also covers any possible role that
>>>  routers might play in providing information to hosts to help them
>>>  select appropriate source addresses.  In the process of exploring
>>>  potential solutions, this documents also makes explicit requirements
>>>  for how the solution would be expected to behave from the perspective
>>>  of an enterprise site network administrator .
>>>
>>>
>>>
>>>
>>> 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
>>>
>>
> 
> 
> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From nobody Wed Jul 20 06:06:42 2016
Return-Path: <equinox@diac24.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4B012D62F; Wed, 20 Jul 2016 06:06:41 -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] autolearn=ham autolearn_force=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 Ay_3MQEpHRGy; Wed, 20 Jul 2016 06:06:40 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02DE012D612; Wed, 20 Jul 2016 06:06:40 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from <equinox@diac24.net>) id 1bPrCu-000H94-PD; Wed, 20 Jul 2016 15:06:37 +0200
Date: Wed, 20 Jul 2016 15:06:36 +0200
From: David Lamparter <equinox@diac24.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20160720130636.GP255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <6097913e-d9e3-82ae-56ef-0476347af4e9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6097913e-d9e3-82ae-56ef-0476347af4e9@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/NYADmpSIwm_WZii98aM9ZEjjyOs>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, Chris Bowers <cbowers@juniper.net>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] [v6ops] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:06:41 -0000

On Thu, Jul 21, 2016 at 12:59:05AM +1200, Brian E Carpenter wrote:
> On 21/07/2016 00:54, David Lamparter wrote:
> > As mentioned on mic during rtgwg, I think the idea of affecting host
> > source address selection through 6724 rule 5.5 is potentially very
> > useful and IMHO should be explored.
> 
> And please note that draft-ietf-6man-multi-homed-host-07 (in IETF Last Call)
> recommends hosts to support this, exactly to assist SADR solutions.

Yay!  I'm also happy to add that googling around the topic tells me at
least Windows already implements rule 5.5:
http://blog.ipspace.net/2016/01/ipv6-address-allocation-is-operating.html

-David


From nobody Wed Jul 20 06:13:28 2016
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E57B12D5B4 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.987
X-Spam-Level: 
X-Spam-Status: No, score=-3.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 xcYA4vWk_Apl for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:13:25 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D8E612D586 for <homenet@ietf.org>; Wed, 20 Jul 2016 06:13:25 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id f6so114800406ith.1 for <homenet@ietf.org>; Wed, 20 Jul 2016 06:13:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+HyN2MJuf8XNOEs1KCYsm1s9Yv88yEJiwPBpL/x8OyQ=; b=S7oWPZeQrW4A+u6ev8FxH1hU8nrv/efRC7Te9R/a/HZWLCcrO2NZH39/yeb0VqSOJp 0K1Xiv+8e98mj80WUtLDYGBhCwfWaMZSR6PVSSGI02zswCVgxlNtRffEhDyyjyHjUQt9 1PSJ39T/ozMX/6xPH2Fm697pa2fKpRAP+or9xgbAu8pdou347N2o+4S8ur0lr9hOR1Fh M587bXjthzUE8AKG86hMVfCgXL/5vlC4ue0Vs5kNUqhqshN/2wZix9rex/xaGrrjbCTh rZsS6DFS66gFFse2d/EorZiuzR4SpOki7Db0aawhxx36FJrdSMfylxsHRimzi6+V342q 8r8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+HyN2MJuf8XNOEs1KCYsm1s9Yv88yEJiwPBpL/x8OyQ=; b=YJpxVPTKEZ88czKZOYFVj6n81Obe+FVGs1nto/G0N34lsyA2k2v7Xyh610vUk7G+yp 7A9RpvHZqEARfKbSBnmkm0u1rNrNexkhfFcu5zAjkX8MOuDauDZ2gSORWZDnACtY3jGC hT9VM6Vy4YWy5WBctfUNPI8v3klDXbM5TXfYP9aBy4rVpw0jN4FxfJWGogg55fjj0m1H Y1eD35BQasly0bN0TIZ6KRnpNfKt+5xVQs4HkFFS0946b9x7krRqu+3fSAj4i5ZNcOfG WG3TbSYDu2suCRTCV4dbEXc60fQtFELxZjfhFnbkZ8Gas9wyl5W6V4wJL8qPBWXseZWQ 0pLw==
X-Gm-Message-State: ALyK8tKOV+jS5cVwMU+7p3MO1+UQYDIcoAw2eC9dI2SeQgX3X4sCYDKPWs9y1p+ytOu8fgtBJWlbWaQUFJ+DHJ96
X-Received: by 10.36.103.4 with SMTP id u4mr60046636itc.88.1469020404606; Wed, 20 Jul 2016 06:13:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.65.15.99 with HTTP; Wed, 20 Jul 2016 06:13:05 -0700 (PDT)
In-Reply-To: <20160720125458.GO255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 20 Jul 2016 15:13:05 +0200
Message-ID: <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com>
To: David Lamparter <equinox@diac24.net>
Content-Type: multipart/alternative; boundary=001a114ac8f862d25f053810f711
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/K3UzLP-1LWvJL8Vpbyc8XsdcSA0>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, Chris Bowers <cbowers@juniper.net>, "Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:13:27 -0000

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

On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:

> - it's a bit unclear how an address/prefix's "source" next-hop is kept
>   in association.  The simplistic approach of adding a "PA source ipv6
>   address" for each of a host's configured addresses falls flat when
>   more than 1 router advertises the same prefix, so I implemented it as
>   a list -- however, my hack never removes entries off that.  It should
>   possibly have a copy of the PA's valid time?
>

The way I thought of doing this would be to alternatively/additionally keep
a pointer from the default router that announced a given prefix (which does
have the link-local address of the router) to each address that was
configured from that prefix. That way, when an address goes away you can
scan the FIB and find another router to associate with that prefix.

As for lifetimes expiring, you would need to have somewhere to keep dummy
zero-lifetime default routes. It might be possible to do this in the FIB
itself by adding a special entry that doesn't ever match anything, or has
an infinite metric, or a different type...

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jul 20, 2016 at 2:54 PM, David Lamparter <span dir=3D"ltr">&lt;<a href=
=3D"mailto:equinox@diac24.net" target=3D"_blank">equinox@diac24.net</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">- it&#39;s a bit unclear h=
ow an address/prefix&#39;s &quot;source&quot; next-hop is kept<br>
=C2=A0 in association.=C2=A0 The simplistic approach of adding a &quot;PA s=
ource ipv6<br>
=C2=A0 address&quot; for each of a host&#39;s configured addresses falls fl=
at when<br>
=C2=A0 more than 1 router advertises the same prefix, so I implemented it a=
s<br>
=C2=A0 a list -- however, my hack never removes entries off that.=C2=A0 It =
should<br>
=C2=A0 possibly have a copy of the PA&#39;s valid time?<br></blockquote><di=
v><br></div><div>The way I thought of doing this would be to alternatively/=
additionally keep a pointer from the default router that announced a given =
prefix (which does have the link-local address of the router) to each addre=
ss that was configured from that prefix. That way, when an address goes awa=
y you can scan the FIB and find another router to associate with that prefi=
x.</div><div><br></div><div>As for lifetimes expiring, you would need to ha=
ve somewhere to keep dummy zero-lifetime default routes. It might be possib=
le to do this in the FIB itself by adding a special entry that doesn&#39;t =
ever match anything, or has an infinite metric, or a different type...</div=
></div></div></div>

--001a114ac8f862d25f053810f711--


From nobody Wed Jul 20 06:22:16 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DF112D5D3; Wed, 20 Jul 2016 06:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JhcAXsuziC6u; Wed, 20 Jul 2016 06:22:12 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926C312D648; Wed, 20 Jul 2016 06:22:12 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id o80so68892956wme.1; Wed, 20 Jul 2016 06:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xpm3+bC8G6QMirpjSVy0QpFy95OCAlyZnYKWwUkx46w=; b=OvKjENDvUsSolPgxfwZNlbs4708FjjgNWf9gFRkEQH+eEDj7QgcBK1e8QrAbCZMeAN qzw3Vsh+1rdsVLLPCtM7uZSN50pU9CBgR5NpdJScEex7thzUpREbIC9p+EQVTL7ot+Wi hFLoyGvXXr6byPLOV6hG6qs3FB9+2c/QIHyQOrxi1YufD6qmJ7QU1LGGb5EJ24Roa50s okV/htfd2wDT4gQX/cKFsFiI/ql8nY+05zX9x8e2XzbHzM4A0Pr+lL+ce9xNdlurHivH +ZWeALe9qtcmtYsfH0BVftpHduKVm+N59+3eLE50dwQL+Z07VzW3kxggy8NBHoczlrSq BNbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=xpm3+bC8G6QMirpjSVy0QpFy95OCAlyZnYKWwUkx46w=; b=acHwK6JXpbB/CKi3+QRweGDe4enZuw1l2Xd/HOVfL0Cct+p4SDHxSnFKkb2HvFpvOs JDiX/qkfY+g5PzVn3X/Y9ZRCPfdLV5jJp35prBz/OuXZ5C0egvRtuwRnBE1oLlZmn8gO wsHeSHNL0mTCIeRo8mokK7sEPxWTB041yPtJjvwFAmoGi3QcKre98iGSrN9G0H6JORkh WHLNcVNFB512S6my0ztwCTSSmTug20BGjsaZsCY4o5t5Y0zwyd+ggvZY+wgVG+9RDyWN So1dhgaKFGqKtvl2kxS8Os+MFyFWn7ViePR/L5Ugv08O45A5Qa0gemhTJDPQG1soxGWc cG+g==
X-Gm-Message-State: ALyK8tJ/twwLSLNwnEukKW4hKbvMJ4272fwkqq1yYA3q8hBkRGoHkzHTighS/LtZh9M4SQ==
X-Received: by 10.28.134.14 with SMTP id i14mr10927669wmd.59.1469020931057; Wed, 20 Jul 2016 06:22:11 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:28cc:dc4c:9703:6781? ([2001:67c:370:176:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g5sm1276410wji.37.2016.07.20.06.22.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 06:22:10 -0700 (PDT)
To: Lorenzo Colitti <lorenzo@google.com>, David Lamparter <equinox@diac24.net>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0b8fe558-768f-6407-6a58-26df0f3817c6@gmail.com>
Date: Thu, 21 Jul 2016 01:22:15 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/B_VWn0BDlbtm2iWAv12z6ikOTGQ>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, Chris Bowers <cbowers@juniper.net>, "Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:22:14 -0000

On 21/07/2016 01:13, Lorenzo Colitti wrote:
> On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:
> 
>> - it's a bit unclear how an address/prefix's "source" next-hop is kept
>>   in association.  The simplistic approach of adding a "PA source ipv6
>>   address" for each of a host's configured addresses falls flat when
>>   more than 1 router advertises the same prefix, so I implemented it as
>>   a list -- however, my hack never removes entries off that.  It should
>>   possibly have a copy of the PA's valid time?
>>
> 
> The way I thought of doing this would be to alternatively/additionally keep
> a pointer from the default router that announced a given prefix (which does
> have the link-local address of the router) to each address that was
> configured from that prefix. That way, when an address goes away you can
> scan the FIB and find another router to associate with that prefix.
> 
> As for lifetimes expiring, you would need to have somewhere to keep dummy
> zero-lifetime default routes. It might be possible to do this in the FIB
> itself by adding a special entry that doesn't ever match anything, or has
> an infinite metric, or a different type...

Please tell us ASAP if there is anything we should add to
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03#section-3.2
or thereabouts.

    Brian


From nobody Wed Jul 20 06:27:56 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915FA12D68A for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:27:54 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 lW3mVUweZAzq for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:27:52 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F365612D643 for <homenet@ietf.org>; Wed, 20 Jul 2016 06:27:50 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id f93so38328153lfi.2 for <homenet@ietf.org>; Wed, 20 Jul 2016 06:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FatOXsnEyr6fCABmtflh6MruGEt7sGsjIrPh/9nWwfg=; b=f8LPMcD/hzU8PdTOju4hAQ5b7qgkuduvWJ3rcdXlBIkdo50I4lR5UVO4KZXPwF8GSJ YIrDb0YircxMzJuIQIJY4IInW45vwvDx+6DAD39ePvV6IC+WQapZdXGtlRW2ZNf3NsoS /Fy5jvv2hhn6LBVeFkWXDClNB8xc+NIBWDqlXXQ7qWWloRvSMMX+yYx9UTIi9HepASnx nYVIFltNuiVgRtpA+g8/UlZsm7uHUsJOW8B0ERHxe+HdyjZn5HljjqKL5VXu9Dpakutw NykMPmFAZTos3QRYbA9KpSoKUA1vZ0VjBTGJsJ47HO4X3X3RA0rKGD/lgelMlI5bPAzI kf3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FatOXsnEyr6fCABmtflh6MruGEt7sGsjIrPh/9nWwfg=; b=ciFx1kmOELCqMvB7UtVzv+7GJukbAwRP0XKgEgbh1fEquaFZ+1w46bnEwZMZI3l9qH bMoXfYDu6qfWdZTqWea9KRd2VP2t9rPQznxadRucob7KNeVg3fDQsrGAHcn9Hv8qKho9 dqbCo3CK0UlRmE09D0lAub6M9SWm09UQBA1rAzi7fMafcq73sPDgR3yunXJ04khmauQq EnPTuHlHphaT4MfQXQl8xiMb32uSdxQRc91pO4FqGPj5swCD+FhzI4X2vVYlCpjusq1e +DTGr4af8dDvbOEZ824MsfXHcoK272jaRklsQZvrQFWwBwC3W4AYcGrpjlEQdZzpfjL7 /woQ==
X-Gm-Message-State: ALyK8tIcdFUhthofBMJB6w1HauRikF0KgystjtW73Ff+eFomb+SeeWvrk+06FCsHlTotqu69NJpytmBliqfhFQ==
X-Received: by 10.25.91.149 with SMTP id p143mr19432470lfb.39.1469021269097; Wed, 20 Jul 2016 06:27:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 06:27:09 -0700 (PDT)
In-Reply-To: <87zipcaccd.wl-jch@pps.univ-paris-diderot.fr>
References: <87zipcaccd.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 20 Jul 2016 15:27:09 +0200
Message-ID: <CAPt1N1muDX6EFjQy6N3T4HCe13r3Z3BL-x_GUq9CsbT+mz=2Bg@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a114124b4e9983e0538112ad2
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/C5yxK7gSE4EL10XNckWCdZwW4WY>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] Naming: a strawman counter-proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:27:54 -0000

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

This proposal doesn't satisfy the problem statement.

(which nobody wrote. :)

I don't want to tube on writing a formal requirements doc before we finish
doing a naming architecture, but I think now that I've taken a stab at
this, we should think about our reactions to and see if we can scope the
problem we are trying to solve in a bit more detail than just "naming and
service discovery on homenets."

On Wed, Jul 20, 2016 at 11:27 AM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> Not proposing this seriously, just attempting to explore the design space.
> Some of the ideas are due to Toke.
>
> Zones and authoritative nameservers are announced over HNCP together with
> their set of addresses, which SHOULD include a LUA and MUST include at
> least one IPv6 address.  There are two bits associated with each
> authoritative nameserver:
>
>   - default: set to 1 if the zone is suitable for name registration without
>     explicit user configuration;
>   - public: set to 1 if the zone is visible from the public internet.
>
> When a router joins the homenet, it MAY announce itself as the new
> authoritative nameserver for a zone.  It SHOULD do so if there is no
> default public or private zone.
>
> If there are two default private zones or two default public zones, we
> call an election, Highlander-style.  If there are two authoritative
> nameservers for the same zone, we call an election.
>
> There are no secondaries.  If there are secondaries, their configuration
> is outside the scope of this mail.
>
> Stateful DHCP servers SHOULD register their clients with the authoritative
> nameserver for the default private zone using your favourite unicast
> mechanism.  Clients MAY register themselves with any zone currently
> announced (they learn the server addresses through HNCP snooping or a from
> new ND option, I don't care).
>
> mDNS proxying into the default private zone is allowed.  Or recommended,
> I'm not sure, only implementation experience will tell.
>
> Why exactly am I speaking nonsense?
>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">This proposal doesn&#39;t satisfy the problem statement.<d=
iv><br></div><div>(which nobody wrote. :)</div><div><br></div><div>I don&#3=
9;t want to tube on writing a formal requirements doc before we finish doin=
g a naming architecture, but I think now that I&#39;ve taken a stab at this=
, we should think about our reactions to and see if we can scope the proble=
m we are trying to solve in a bit more detail than just &quot;naming and se=
rvice discovery on homenets.&quot;</div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Wed, Jul 20, 2016 at 11:27 AM, Juliusz Chro=
boczek <span dir=3D"ltr">&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.f=
r" target=3D"_blank">jch@pps.univ-paris-diderot.fr</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Not proposing this seriously, just attempti=
ng to explore the design space.<br>
Some of the ideas are due to Toke.<br>
<br>
Zones and authoritative nameservers are announced over HNCP together with<b=
r>
their set of addresses, which SHOULD include a LUA and MUST include at<br>
least one IPv6 address.=C2=A0 There are two bits associated with each<br>
authoritative nameserver:<br>
<br>
=C2=A0 - default: set to 1 if the zone is suitable for name registration wi=
thout<br>
=C2=A0 =C2=A0 explicit user configuration;<br>
=C2=A0 - public: set to 1 if the zone is visible from the public internet.<=
br>
<br>
When a router joins the homenet, it MAY announce itself as the new<br>
authoritative nameserver for a zone.=C2=A0 It SHOULD do so if there is no<b=
r>
default public or private zone.<br>
<br>
If there are two default private zones or two default public zones, we<br>
call an election, Highlander-style.=C2=A0 If there are two authoritative<br=
>
nameservers for the same zone, we call an election.<br>
<br>
There are no secondaries.=C2=A0 If there are secondaries, their configurati=
on<br>
is outside the scope of this mail.<br>
<br>
Stateful DHCP servers SHOULD register their clients with the authoritative<=
br>
nameserver for the default private zone using your favourite unicast<br>
mechanism.=C2=A0 Clients MAY register themselves with any zone currently<br=
>
announced (they learn the server addresses through HNCP snooping or a from<=
br>
new ND option, I don&#39;t care).<br>
<br>
mDNS proxying into the default private zone is allowed.=C2=A0 Or recommende=
d,<br>
I&#39;m not sure, only implementation experience will tell.<br>
<br>
Why exactly am I speaking nonsense?<br>
<br>
-- Juliusz<br>
<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote></div><br></div>

--001a114124b4e9983e0538112ad2--


From nobody Wed Jul 20 06:38:21 2016
Return-Path: <equinox@diac24.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E8512D695; Wed, 20 Jul 2016 06:38:19 -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] autolearn=ham autolearn_force=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 br8PYI_cBeJf; Wed, 20 Jul 2016 06:38:18 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA9C812D6AF; Wed, 20 Jul 2016 06:38:10 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from <equinox@diac24.net>) id 1bPrhP-000I1s-49; Wed, 20 Jul 2016 15:38:07 +0200
Date: Wed, 20 Jul 2016 15:38:07 +0200
From: David Lamparter <equinox@diac24.net>
To: Lorenzo Colitti <lorenzo@google.com>
Message-ID: <20160720133807.GR255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/JE0JaMxo54EP7B_Sx2koACYZ29w>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Chris Bowers <cbowers@juniper.net>, homenet <homenet@ietf.org>, Jen Linkova <furry@google.com>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:38:19 -0000

On Wed, Jul 20, 2016 at 03:13:05PM +0200, Lorenzo Colitti wrote:
> On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:
> 
> > - it's a bit unclear how an address/prefix's "source" next-hop is kept
> >   in association.  The simplistic approach of adding a "PA source ipv6
> >   address" for each of a host's configured addresses falls flat when
> >   more than 1 router advertises the same prefix, so I implemented it as
> >   a list -- however, my hack never removes entries off that.  It should
> >   possibly have a copy of the PA's valid time?
> >
> 
> The way I thought of doing this would be to alternatively/additionally keep
> a pointer from the default router that announced a given prefix (which does
> have the link-local address of the router) to each address that was
> configured from that prefix.

That turns nontrivial as soon as you have 4191 RIOs, especially if the
router is trying to do walled gardens by sending its RAs with lifetime =
0 (as suggested in section 4.2.2 of pa-multihoming).

> That way, when an address goes away you can scan the FIB and find
> another router to associate with that prefix.

[I assume "address goes away" meant "router goes away"]

> As for lifetimes expiring, you would need to have somewhere to keep dummy
> zero-lifetime default routes. It might be possible to do this in the FIB
> itself by adding a special entry that doesn't ever match anything, or has
> an infinite metric, or a different type...

That sounds quite a bit more complicated than address-centric
handling...  we're 1:N for router['s LL address] to routes and also 1:N
for router['s LL address] to prefixes, and then 1:N for prefix to
derived addresses.

I'd rather copy the prefix lifetime (either valid or preferred -
probably former?) onto the same list entry where a configured address's
RA source LL is also stored; that replicates only the last 1:N step...
(So, for each address, in its list of RA sources that the prefix was
seen from, there will be a potentially-distinct lifetime.)


-David

P.S.: Does anyone know the details of how Windows implements this?


From nobody Wed Jul 20 06:47:29 2016
Return-Path: <avri@acm.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7998012D758 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.255
X-Spam-Level: 
X-Spam-Status: No, score=-1.255 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 9YfKKn8FUoMj for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 06:47:25 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0030.hostedemail.com [216.40.44.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6200D12D54B for <homenet@ietf.org>; Wed, 20 Jul 2016 06:47:25 -0700 (PDT)
Received: from filter.hostedemail.com (unknown [216.40.38.60]) by smtprelay05.hostedemail.com (Postfix) with ESMTP id 3913C269195 for <homenet@ietf.org>; Wed, 20 Jul 2016 13:47:24 +0000 (UTC)
X-Session-Marker: 6176726940646F7269612E6F7267
X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, avri@acm.org, :, RULES_HIT:41:355:379:599:854:967:973:988:989:1042:1260:1261:1277:1311:1313:1314:1345:1359:1381:1437:1513:1515:1516:1518:1521:1534:1542:1593:1594:1605:1683:1711:1730:1747:1777:1792:2110:2198:2199:2393:2525:2553:2560:2563:2682:2685:2692:2731:2859:2910:2911:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4425:5007:6117:6119:6120:7652:7901:7903:7974:8660:8985:9010:9025:10004:10400:10848:11232:11658:11914:12043:12214:12517:12519:12663:12740:13019:13148:13230:14037:14096:14097:14181:14721:21080:21324:21325:21366:21433:30022:30029:30030:30054:30056:30060:30090, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fp, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:1, LUA_SUMMARY:none
X-HE-Tag: look56_4013f26429f0a
X-Filterd-Recvd-Size: 3986
Received: from [127.0.0.1] (tmo-098-168.customers.d1-online.com [80.187.98.168]) (Authenticated sender: avri@doria.org) by omf13.hostedemail.com (Postfix) with ESMTPA for <homenet@ietf.org>; Wed, 20 Jul 2016 13:47:20 +0000 (UTC)
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <CAPt1N1mHp0bLtPFHkmZuOz54nQ5ZLObB=48g83+NGs4xv9xkEg@mail.gmail.com>
To: homenet@ietf.org
From: avri doria <avri@acm.org>
Message-ID: <b2d1aa10-b8db-9f2f-2823-ab54da248d5a@acm.org>
Date: Wed, 20 Jul 2016 15:47:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1mHp0bLtPFHkmZuOz54nQ5ZLObB=48g83+NGs4xv9xkEg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Antivirus: avast! (VPS 160720-0, 07/20/2016), Outbound message
X-Antivirus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/P4y0gZ9vX_Pa1E8J5N9WVW68XxI>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: avri@acm.org
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 13:47:27 -0000

On 19-Jul-16 18:10, Ted Lemon wrote:
> Please read draft-lemon-sutldr-ps, and participate in the discussion
> about this on the dnsop mailing list.   Discussions about the RFC6761
> problem are off-topic for the homenet mailing list.   We are customers
> of the existing IETF consensus process as documented in RFC 6761.   We
> get into enough ratholes on the homenet mailing list; please don't get
> us into this rathole as well.   

I have done my reading.  Not only of your draft, the discussion in DNSOP
and the other drafts. Do not know why you presumed i hadn't.  Why, I
have even read RFC6761, several times.

I am also happy to avoid rat holes, but as far as I understand the case,
you did not follow the requirements of RFC6761 and thus this unassigned
usage does not have the imprimatur even of RFC6761, for whatever that
ends up being worth.  It was a decision made by this WG for this group's
reasons.  And it was missed in the review cycle.  Unfortunately I find I
only ended up working on this issue on 23 October, just as IET was
ending its last call.  Though I might have missed it as well.

I would also like to point out that the studies done for ICANN are by no
means the end of the story and do not represent a consensus decision of
ICANN at this point.  While there may be a 'restraining order' from the
ICANN Board on assigning the names at this point, that is not a
permanent consensus decision and is a situation that people in ICANN are
still actively working on.  To allocate a name that is under discussion
and contention and had been applied for in 2012,  at this point seems to
me to constitute an infringement of the policy prerogative given to
ICANN by RFC2860.  And while the recent 2015 study may have recommended
that ICANN ask IETF to reserve then name, an incredibly bad idea when
ICANN has its own policy development methods for reserving names, the
ICANN Board has not to my knowledge made any such formal request.

While IETF can certainly assign a name as a protocol parameter according
to RFC6761 ( despite any dispute that may or may not exist on the
validity of that process ) that does not mean they have the ability to
chose any name they wish, only that they may assign a name.  I would
recommend in the spirit of RFC2860 that you chose a name that is not the
point of a disagreement and that had not been applied for in 2012.  I
assume there is no technical reason why .home and only .home must be
used for protocol reasons alone.  As a protocol parameter, I would
assume any relationship between a string and dictionary word was just an
unhappy coincidence, and one to avoid.

If you want to hardcode a name into your protocol, I suggest you pick a
neologism like .homenet  or even .hmnt it you want something short and
pithy, and avoid the rat hole that is .home.

cheers,
avri



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From nobody Wed Jul 20 07:34:26 2016
Return-Path: <equinox@diac24.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB2B12D836; Wed, 20 Jul 2016 07:34:21 -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] autolearn=ham autolearn_force=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 2_rjRvBqHvTs; Wed, 20 Jul 2016 07:34:17 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92C312D82C; Wed, 20 Jul 2016 07:34:17 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from <equinox@diac24.net>) id 1bPsZe-000JmN-V1; Wed, 20 Jul 2016 16:34:12 +0200
Date: Wed, 20 Jul 2016 16:34:10 +0200
From: David Lamparter <equinox@diac24.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20160720143410.GS255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com> <0b8fe558-768f-6407-6a58-26df0f3817c6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0b8fe558-768f-6407-6a58-26df0f3817c6@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/lpuafETP0fOgnScsNViIonmvf08>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Chris Bowers <cbowers@juniper.net>, homenet <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, Jen Linkova <furry@google.com>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 14:34:21 -0000

On Thu, Jul 21, 2016 at 01:22:15AM +1200, Brian E Carpenter wrote:
> On 21/07/2016 01:13, Lorenzo Colitti wrote:
> > On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:
> > 
> >> - it's a bit unclear how an address/prefix's "source" next-hop is kept
> >>   in association.  The simplistic approach of adding a "PA source ipv6
> >>   address" for each of a host's configured addresses falls flat when
> >>   more than 1 router advertises the same prefix, so I implemented it as
> >>   a list -- however, my hack never removes entries off that.  It should
> >>   possibly have a copy of the PA's valid time?
> >>
> > 
> > The way I thought of doing this would be to alternatively/additionally keep
> > a pointer from the default router that announced a given prefix (which does
> > have the link-local address of the router) to each address that was
> > configured from that prefix. That way, when an address goes away you can
> > scan the FIB and find another router to associate with that prefix.
> > 
> > As for lifetimes expiring, you would need to have somewhere to keep dummy
> > zero-lifetime default routes. It might be possible to do this in the FIB
> > itself by adding a special entry that doesn't ever match anything, or has
> > an infinite metric, or a different type...
> 
> Please tell us ASAP if there is anything we should add to
> https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03#section-3.2
> or thereabouts.

I do see some trouble in use-cases where more than one actual router
(actual = not counting extra link-local addresses on the same router) is
present on a link, advertising the same prefix to hosts.  (This is
reasonably likely in homenet scenarios, maybe less in enterprise.)

If the host only tracks a maximum of one RA source LL for a
prefix/address, but the router with that LL happens to not be the one
actually used (e.g. preference, router gone, more specific route from
RIO, whatever else) then the functionality is lost.  It's particularly
bad if the one RA source LL is the one prefix was first seen from (and
then, worst-case, never updated).

(The neccessary precondition / assumption being broken there is that the
test "was prefix X announced by router Y" doesn't report false
negatives.  I haven't applied brain to false positives yet.)


-David


From nobody Wed Jul 20 08:17:49 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D003712D7F6 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 08:17:48 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=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 uGYR6f5XsQ-Z for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 08:17:45 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18B7A12D838 for <homenet@ietf.org>; Wed, 20 Jul 2016 08:11:16 -0700 (PDT)
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/56228) with ESMTP id u6KFBESW004034; Wed, 20 Jul 2016 17:11:14 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 42D1561FA2; Wed, 20 Jul 2016 17:11:14 +0200 (CEST)
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 58UgS_btk8tm; Wed, 20 Jul 2016 17:11:13 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (dhcp-a24d.meeting.ietf.org [31.133.162.77]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id D49D761FAE; Wed, 20 Jul 2016 17:11:12 +0200 (CEST)
Date: Wed, 20 Jul 2016 17:11:12 +0200
Message-ID: <87y44wqr8v.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk> <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk>
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 [194.254.61.138]); Wed, 20 Jul 2016 17:11:14 +0200 (CEST)
X-Miltered: at korolev with ID 578F9492.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 578F9492.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 : 578F9492.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: <https://mailarchive.ietf.org/arch/msg/homenet/Iv57fOW_W5FtdLXZg1UOzxsqcKk>
Cc: homenet@ietf.org
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 15:17:49 -0000

> Current host stacks don't have support for saying "if the suffix is
> ".TBD", go here, otherwise go there.

Right, and I missed this point in my strawman.  I guess I've been spoiled
by dnsmasq.

-- Juliusz


From nobody Wed Jul 20 09:32:15 2016
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0FDD12D895 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 09:32:12 -0700 (PDT)
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 autolearn_force=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 DP0WyZ3CBioG for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 09:32:11 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 2089B12D8B3 for <homenet@ietf.org>; Wed, 20 Jul 2016 09:32:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id B2F2610D2D for <homenet@ietf.org>; Wed, 20 Jul 2016 16:32:10 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mWfEfyBRhg6 for <homenet@ietf.org>; Wed, 20 Jul 2016 16:32:10 +0000 (UTC)
Received: from mx2.yitter.info (dhcp-a9ee.meeting.ietf.org [31.133.169.238]) by mx2.yitter.info (Postfix) with ESMTPSA id 912211067D for <homenet@ietf.org>; Wed, 20 Jul 2016 16:32:09 +0000 (UTC)
Date: Wed, 20 Jul 2016 12:32:06 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: homenet@ietf.org
Message-ID: <20160720163205.GA693@mx2.yitter.info>
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk> <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MQIoN1ocm02ZUzpkiT1wX1bEk5M>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 16:32:12 -0000

Hi,

On Wed, Jul 20, 2016 at 02:10:05PM +0200, Ray Bellis wrote:
> 
> On 20/07/2016 13:33, Ray Bellis wrote:
> 
> > My expectation is that in a Homenet multi-subnet environment I will be
> > able to just use http://<device>.<TBD>/ and just have it work regardless
> > of which particular subnet that device is on [*].

Note that only one of those expectations is actually given you by RFC
7368 -- that it will just work no matter which subnet you're on.  The
<device>.<TBD> pattern (assuming TBD is a single label) is not.

> There's a further corollary to this:  since we can't mandate host
> changes, the resolution of that name MUST be unicast DNS to an *on-net*
> resolver.

I think this is probably entailed, but RFC 7368 doesn't say that
either.  It just says that it probably needs to be (or needs to work
somehow with DNS).

> Having different resolvers for different parts of the namespace is a bad
> idea [*]

Except, of course, that's precisely what we have with Bonjour: DNS for
everything except names ending in local.  That label functions as a
protocol switch to tell your combined resolver which names to resolve
by mDNS and which ones to resolve by DNS.

> [ Current host stacks don't have support for saying "if the suffix is
> ".TBD", go here, otherwise go there.  If you have one resolver for
> ".TDB" and another for everything else and then just send all queries to
> both, you still need host changes to cope with how you'll get a valid
> answer from one but not the other ]

Not necessarily.  For instance, you could use Bonjour and the hybrid
proxy approach and do it that way.  It's not clear to me from RFC 7368
whether we're allowed to assume mDNS is available on any host, but
given the zeroconf pattern and the stated desirability of it, probably
we are.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Jul 20 09:59:13 2016
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D882812D786 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 09:59:09 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 NUERqTmYc8yR for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 09:58:59 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A401912D7BC for <homenet@ietf.org>; Wed, 20 Jul 2016 09:58:53 -0700 (PDT)
Received: from dhcp-b14e.meeting.ietf.org ([31.133.177.78]:55660) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bPupd-0004nF-Dh (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Wed, 20 Jul 2016 17:58:49 +0100
To: homenet@ietf.org
References: <fuuuepeyx6tjwn0n5djmyxbf.1468851488934@email.android.com> <87inw1e0p3.wl-jch@pps.univ-paris-diderot.fr> <20160720091034.GA48086@mx2.yitter.info> <87y44wabaq.wl-jch@pps.univ-paris-diderot.fr> <6B69F952-743D-40CA-A4F1-FC5486FFF6FA@gmail.com> <0a15b78f-c2fa-c623-ecb2-1bd8a3bfb30f@bellis.me.uk> <3acaffbe-7fee-4d97-1666-2d13322052e9@bellis.me.uk> <20160720163205.GA693@mx2.yitter.info>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <9c120764-a594-aeb4-a4da-11832b3abb21@bellis.me.uk>
Date: Wed, 20 Jul 2016 18:58:51 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160720163205.GA693@mx2.yitter.info>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/STQooQL_oaCd3H2nlBvdRWtPIXE>
Subject: Re: [homenet] RFC 7788 and ".home"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 16:59:10 -0000

On 20/07/2016 18:32, Andrew Sullivan wrote:

> Except, of course, that's precisely what we have with Bonjour: DNS for
> everything except names ending in local.  That label functions as a
> protocol switch to tell your combined resolver which names to resolve
> by mDNS and which ones to resolve by DNS.

I was talking in the context of unicast DNS, without a 'protocol switch'.

Ray


From nobody Wed Jul 20 13:10:58 2016
Return-Path: <york@isoc.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6353312D976 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 13:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
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 UzMtxTdl1O4y for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 13:10:53 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0087.outbound.protection.outlook.com [104.47.42.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C47C12D73D for <homenet@ietf.org>; Wed, 20 Jul 2016 13:10:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qIfylWCl4MkGlEB3VeMyASBiCXaxQlxD0mUTRWfM2bo=; b=A8YGiLA1atsIPyTf5ABqWKlP25En6OY+lCdfKkyo4rOdb0UaBRQM/racEhMBB1THENyO6CDorKlenkdpwPVkGdm4b1H57CQwgC93vQ/2/gYVLEL5LYpgQnu044eqSahlsggcfKJJClLext9qH3tVJsi+suNAXKk0FNay6/w+Pww=
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com (10.163.232.19) by CY1PR0601MB1658.namprd06.prod.outlook.com (10.163.232.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Wed, 20 Jul 2016 20:10:50 +0000
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com ([10.163.232.19]) by CY1PR0601MB1657.namprd06.prod.outlook.com ([10.163.232.19]) with mapi id 15.01.0539.021; Wed, 20 Jul 2016 20:10:50 +0000
From: Dan York <york@isoc.org>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: Thinking about the implementer - my comments at mic about .home and RFC 7788
Thread-Index: AQHR4sLPtVKzvq2or0m0X00gJhbMiw==
Date: Wed, 20 Jul 2016 20:10:50 +0000
Message-ID: <157EF926-8286-4496-858B-21625EF41C35@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=york@isoc.org; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:136:9d7b:4627:342f:1680]
x-ms-office365-filtering-correlation-id: f221a8ba-e0f9-4bbe-13a6-08d3b0d9f23b
x-microsoft-exchange-diagnostics: 1; CY1PR0601MB1658; 6:5LwhSDeuCmxL05Rr5qK3uq/sRkwfJBSAew1lkNIAO2QFJczpsZ7VhR1BwBrRsCGVB660AM5O4+T+Y5tCQdIKSkYdhh9WAODUdksGbd2opUKYZ2tcIVsNc3WkEQXbFNiszUrMuCndDmu2C7ijia4VmVpjs+blt09RDej8rk7hHXIf086SY2h+dJIymMyQVzv+ye+j6DjfhsVnL0VS0G+GlVZAxY7KshvNlTvocpMmwPnQDLmZQVtiqAvOzY0zDbEGB2F7Tcb3xRARZGrQCqkC3ha218K/nfS7f+/PgGyUbR0=; 5:qBQOVDV2rIb/AA/ssaQb+5h1xdPoLJtCXw///MLCveOVBBc80n2MXBXO9NneNFOJ19cx3I2qnB3TLw0USsV42ZfXpZ16uECNKf4a8ddvF1ESSD3I+Xzp7fvuo2UowKdzAwh6+kepVUwR5WJjEZb0PQ==; 24:YDaKsmTLPWN4KG5vY/EkrTL95UBd2m+SKlbdynXLtpWgj61r+yxIFSEWn4NvNcTQEDV0TJc1M1v0z7XPxY4zVqeUGumWOv5q/hoYQiXkfEU=; 7:IjLWrbAsMFUu7bEErbOsNQBP9ZbaXBDhTUE98Vq/OwVANRmR+uu6BqFlWf79DCR4dLIKuqcMUOIv+SygpYBxZHc5JLvfSXU/ZiOF4MfBQHJBcasW6ZBI298kEyjvRZcixPpdesKEteN9JLIyraRHcHe3eL87EWq+SPQW+FyV+yKUueyd8V1P0JLkEPBc0O886xemJja2Aqg8qU6LXQJB7cD2LzS1z/niRGDiTow1sAzr4eBhS/HqXe+FFKJMUjqH
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1658;
x-microsoft-antispam-prvs: <CY1PR0601MB165897A15E08AD927BCC2B50B7080@CY1PR0601MB1658.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(31418570063057);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:CY1PR0601MB1658; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1658; 
x-forefront-prvs: 000947967F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(189002)(199003)(36756003)(2501003)(1730700003)(15395725005)(189998001)(110136002)(101416001)(8676002)(229853001)(107886002)(7846002)(8936002)(97736004)(87936001)(7906003)(86362001)(105586002)(99286002)(81156014)(81166006)(68736007)(11100500001)(7736002)(6116002)(450100001)(106116001)(5640700001)(10400500002)(5002640100001)(106356001)(2351001)(83716003)(19580395003)(19580405001)(92566002)(82746002)(3660700001)(2900100001)(102836003)(16236675004)(54356999)(50986999)(2906002)(3280700002)(15975445007)(122556002)(19617315012)(33656002)(586003)(77096005)(142923001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1658; H:CY1PR0601MB1657.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_157EF92682864496858B21625EF41C35isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jul 2016 20:10:50.1105 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1658
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/hl2AOeVz3Dk0YtY81M_hWGWJ7io>
Subject: [homenet] Thinking about the implementer - my comments at mic about .home and RFC 7788
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2016 20:10:56 -0000

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

Just relaying to the list the comments I made at the mic in the WG session =
on Monday...

I did not agree with any of the four choices offered by the chairs to the W=
G for the resolution of the RFC 7788 / .home issue.

I've spent a good bit time over the past four years helping people try to i=
mplement standards that we create for technologies such as IPv6, DNSSEC, TL=
S, etc.  Developers often attempt to use the RFCs and many wind up finding =
it too confusing of an experience. A few observations:

- Some developers don't pay attention to (or don't see) the "errata" that e=
xists on some of the RFCs. (There was a comment in the room on Monday that =
some views of the RFCs don't make it easy to find the errata - I've not exp=
lored that myself to confirm.) [1]

- Some developers don't understand how our systems work with regard to "upd=
ates".  They don't understand that an RFC may be updated by another RFC and=
 that update may fundamentally alter the original RFC.

They are generally told "you need to implement RFC <####> - go do it!" and =
are left to figure that out.

In talking to a couple of developers over the years, they just go to their =
favorite search engine, enter the RFC number and pretty much take the first=
 link they find (which may or may not be one of our primary repositories).

I think the easier we can make it for developers to figure out how to imple=
ment our standards, the better the chance for more deployment.  If we want =
HOMENET to be widely used, we need to make the standards as easy to underst=
and and implement.

To me that means a couple of things with regard to RFC 7788 and the .home i=
ssue:

1. I would NOT publish any changes we want to make as "errata".

2. I would NOT publish a new RFC that "updates" RFC 7788.

3. I would NOT publish a new RFC that is filled with "internal" analysis of=
 how the process broke down AND THEN also updates RFC 7788.  (Someone seeki=
ng to implement the standard is not going to want to wade through the analy=
sis.)

I think the cleanest, simplest thing we can do *for the implementers* is to=
 publish a new RFC that *obsoletes* RFC 7788.  We can then promote the new =
RFC as the definitive standard for HNCP.  RFC 7788 can get a big "Obsolete"=
 warning in the places we publish it - and documentation and other new RFCs=
 can reference the new RFC.

Just my 2 cents,
Dan

[1] I also know that RFCs are sometimes copied to other locations on the In=
ternet where things such as errata and update links are sometimes lost.  I =
realize that's not something we can really address - and we can only hope d=
evelopers seek out the "official" source - but that is also a reality.

--
Dan York
Senior Content Strategist, Internet Society
york@isoc.org<mailto:york@isoc.org>   +1-802-735-1624
Jabber: york@jabber.isoc.org<mailto:york@jabber.isoc.org>
Skype: danyork   http://twitter.com/danyork

http://www.internetsociety.org/





--_000_157EF92682864496858B21625EF41C35isocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <04469B966DAE944E99500AAF6B3A5D42@namprd06.prod.outlook.com>
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;" class=3D"">
<div class=3D"">Just relaying to the list the comments I made at the mic in=
 the WG session on Monday...</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I did not agree with any of the four choices offered by the=
 chairs to the WG for the resolution of the RFC 7788 / .home issue.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I've spent a good bit time over the past four years helping=
 people try to implement standards that we create for technologies such as =
IPv6, DNSSEC, TLS, etc. &nbsp;Developers often attempt to use the RFCs and =
many wind up finding it too confusing of
 an experience. A few observations:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">- Some developers don't pay attention to (or don't see) the=
 &quot;errata&quot; that exists on some of the RFCs. (There was a comment i=
n the room on Monday that some views of the RFCs don't make it easy to find=
 the errata - I've not explored that myself
 to confirm.) [1]</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">- Some developers don't understand how our systems work wit=
h regard to &quot;updates&quot;. &nbsp;They don't understand that an RFC ma=
y be updated by another RFC and that update may fundamentally alter the ori=
ginal RFC.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">They are generally told &quot;you need to implement RFC &lt=
;####&gt; - go do it!&quot; and are left to figure that out. &nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">In talking to a couple of developers over the years, they j=
ust go to their favorite search engine, enter the RFC number and pretty muc=
h take the first link they find (which may or may not be one of our primary=
 repositories).</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I think the easier we can make it for developers to figure =
out how to implement our standards, the better the chance for more deployme=
nt. &nbsp;If we want HOMENET to be widely used, we need to make the standar=
ds as easy to understand and implement.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">To me that means a couple of things with regard to RFC 7788=
 and the .home issue:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">1. I would NOT publish any changes we want to make as &quot=
;errata&quot;. &nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">2. I would NOT publish a new RFC that &quot;updates&quot; R=
FC 7788.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">3. I would NOT publish a new RFC that is filled with &quot;=
internal&quot; analysis of how the process broke down AND THEN also updates=
 RFC 7788. &nbsp;(Someone seeking to implement the standard is not going to=
 want to wade through the analysis.)</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I think the cleanest, simplest thing we can do *for the imp=
lementers* is to publish a new RFC that *obsoletes* RFC 7788. &nbsp;We can =
then promote the new RFC as the definitive standard for HNCP. &nbsp;RFC 778=
8 can get a big &quot;Obsolete&quot; warning in the places
 we publish it - and documentation and other new RFCs can reference the new=
 RFC.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Just my 2 cents,</div>
<div class=3D"">Dan</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">[1] I also know that RFCs are sometimes copied to other loc=
ations on the Internet where things such as errata and update links are som=
etimes lost. &nbsp;I realize that's not something we can really address - a=
nd we can only hope developers seek out
 the &quot;official&quot; source - but that is also a reality.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-w=
rap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-=
space;" class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-w=
rap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-=
space;" class=3D"">
<div apple-content-edited=3D"true" class=3D"">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
--</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D"">Dan York</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D"">Senior Content Strategist, Int=
ernet Society</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D""><a href=3D"mailto:york@isoc.or=
g" class=3D"">york@isoc.org</a>&nbsp;&nbsp; &#43;1-802-735-1624</font></div=
>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D"">Jabber:&nbsp;<a href=3D"mailto=
:york@jabber.isoc.org" class=3D"">york@jabber.isoc.org</a>&nbsp;</font></di=
v>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D"">Skype: danyork &nbsp;&nbsp;<a =
href=3D"http://twitter.com/danyork" class=3D"">http://twitter.com/danyork</=
a></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<font face=3D"Calibri,sans-serif" class=3D""><br class=3D"">
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; background=
-color: rgb(255, 255, 255);" class=3D"">
<a href=3D"http://www.internetsociety.org/" class=3D"">http://www.internets=
ociety.org/</a></div>
</div>
</div>
<br class=3D"Apple-interchange-newline">
</div>
<br class=3D"Apple-interchange-newline">
<br class=3D"Apple-interchange-newline">
</div>
<br class=3D"">
</body>
</html>

--_000_157EF92682864496858B21625EF41C35isocorg_--


From SRS0=4LxX=TL=darou.fr=pierre.pfister@bounces.m4x.org  Wed Jul 20 23:56:06 2016
Return-Path: <SRS0=4LxX=TL=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADA212DA53 for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 23:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 vcNEp10jWcbp for <homenet@ietfa.amsl.com>; Wed, 20 Jul 2016 23:56:03 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B861012DA3F for <homenet@ietf.org>; Wed, 20 Jul 2016 23:56:03 -0700 (PDT)
Received: from [10.61.243.102] (unknown [173.38.220.38]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 723645647DC; Thu, 21 Jul 2016 08:56:00 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <157EF926-8286-4496-858B-21625EF41C35@isoc.org>
Date: Thu, 21 Jul 2016 08:56:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31576049-F3B3-4B89-B68A-0BE95BEAEE94@darou.fr>
References: <157EF926-8286-4496-858B-21625EF41C35@isoc.org>
To: Dan York <york@isoc.org>
X-Mailer: Apple Mail (2.3124)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Jul 21 08:56:00 2016 +0200 (CEST))
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nb8zdTY0hcogAuy2joDvVZ9Iahc>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Thinking about the implementer - my comments at mic about .home and RFC 7788
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2016 07:02:46 -0000

Hello Dan,=20

> I did not agree with any of the four choices offered by the chairs to =
the WG for the resolution of the RFC 7788 / .home issue.
[...]
>=20
> I think the cleanest, simplest thing we can do *for the implementers* =
is to publish a new RFC that *obsoletes* RFC 7788.  We can then promote =
the new RFC as the definitive standard for HNCP.  RFC 7788 can get a big =
"Obsolete" warning in the places we publish it - and documentation and =
other new RFCs can reference the new RFC.
>=20

If my memory is correct, what you describe was actually choice #1, which =
got little humming in the room compared to 3 and 4 (and 5...).

Cheers,

- Pierre=


From nobody Thu Jul 21 00:24:35 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208EA12DA79 for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 00:24:33 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 1Q1B5JChxq4h for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 00:24:31 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CF0512DA5A for <homenet@ietf.org>; Thu, 21 Jul 2016 00:24:31 -0700 (PDT)
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/56228) with ESMTP id u6L7OTIh032079; Thu, 21 Jul 2016 09:24:29 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9C13261FB3; Thu, 21 Jul 2016 09:24:29 +0200 (CEST)
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 aK2WIc_maYTf; Thu, 21 Jul 2016 09:24:28 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2EE3961FC9; Thu, 21 Jul 2016 09:24:25 +0200 (CEST)
Date: Thu, 21 Jul 2016 09:24:28 +0200
Message-ID: <87a8hbqwr7.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1muDX6EFjQy6N3T4HCe13r3Z3BL-x_GUq9CsbT+mz=2Bg@mail.gmail.com>
References: <87zipcaccd.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1muDX6EFjQy6N3T4HCe13r3Z3BL-x_GUq9CsbT+mz=2Bg@mail.gmail.com>
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 [194.254.61.138]); Thu, 21 Jul 2016 09:24:29 +0200 (CEST)
X-Miltered: at korolev with ID 579078AD.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579078AD.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 : 579078AD.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: <https://mailarchive.ietf.org/arch/msg/homenet/hHMsMK6u475FAnfgfqmTtnPJFxA>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] Naming: a strawman counter-proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2016 07:24:33 -0000

> This proposal doesn't satisfy the problem statement.

> (which nobody wrote. :)

Perhaps we could start by writing up the usage scenarios we have in mind?
I'll start:

1. I want to point a web browser at the configuration interface of the
   router in my attic;
2. I want to point a web browser at the boom-box in my living room
     2a. the boom-box speaks IP and is Homenet-aware;
     2b. the boom-box speaks IP but is not Homenet-aware;
3. I want you to join in a game that I'm playing, so I need a memorable
   public URL for the Nethack server
     3a. the Nethack server is in my Homenet;
     3b. the Nethack server is outside my Homenet;
4. I'm running a BitTorrent seeder, and I want the RIAA to be able to
   perform a reverse mapping on my IP address so they can use a memorable
   name in their correspondence.

Naming of routers and hosts is likely to use different mechanisms, which
is why I separate (1) and (2).  I've never understood the purpose of
reverse mapping except for debugging, so (4) is the best I could come up
with.

-- Juliusz


From nobody Thu Jul 21 00:25:45 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE0C12DA8D; Thu, 21 Jul 2016 00:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OBSNGvTpeVSh; Thu, 21 Jul 2016 00:25:41 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219B612D098; Thu, 21 Jul 2016 00:25:41 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id o80so13028342wme.1; Thu, 21 Jul 2016 00:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=N5dzZKkXQMGkRlNWZAx7fgQwsMLV4y2BrGt3QCTBE7I=; b=LUSqixYreR7Di5uFju0xwwu6eEF4RPQkM3uw1x3edJ0JCeWW0OHV7gn9AQotGfBy5l BZ6On+ufMDYzkVX6YwPAjCFeUMMAyOwWpf8XcNmOG5QnaNLEFYdHTuC2s6wioxTbFD/R izoxM+vvO/sTSlcOmjWibGJy1l9DMcpYXitQS99qzLWe072FdwgBGkhIgD0dmTUe+ww6 BVeXzju9saqjVdCPSG7eTWNIDxavZZCijRMMOLK32W1Pd4DfjQAzZoLydbJn1AkI7YpQ rvytHUGIETYxKoXJVuDpgmlQ70eFXBpA6X9p+jpREe4oQu9UzGw3jIkknKA64v/HQlvV eP0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=N5dzZKkXQMGkRlNWZAx7fgQwsMLV4y2BrGt3QCTBE7I=; b=CJT4sJWBgf5A3ZhFykeueOu9imgm1fCcCtSTS7CPDij8M5kaujd8dGs+WhwKcJVwA/ DePcufKi1NDz0xkQK7BILWzaGcQVFCK63cdmuUTFzK1YAq7sL6+ZomJ51dHRRagLHsOz tnTbmsC5wPGREE33K/dGO2fPbFMKX0yhngsixiSyeKX8YpHzOuCikjUO39qAsKUrJteR utEiZcnVtn+ZFAAuPL4v14zhhIkhQVNA55WrYduHkMHgwg4JwieK+Y34t/DA/fzdpE1F IN34P92/Kba32qh9lcJKS6KS6eX6SVy9RuKm1AeE9ljBDGQEBKRkyXQA+MwoI4X/Aqzp fcnw==
X-Gm-Message-State: ALyK8tK7ge5Y7vVDwT7mXKAQ2iDoaPdccUAwEx3rF/ENruZPj0ms/yjemW64CpUlALDdUA==
X-Received: by 10.28.156.6 with SMTP id f6mr16660199wme.1.1469085939558; Thu, 21 Jul 2016 00:25:39 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:152:28cc:dc4c:9703:6781? ([2001:67c:370:152:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id a194sm1825603wmd.24.2016.07.21.00.25.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jul 2016 00:25:38 -0700 (PDT)
To: David Lamparter <equinox@diac24.net>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <CAKD1Yr0yw=CXSroDuA-qKxsOPe8FdVd-7f_RO2H2HVVyeYL9ug@mail.gmail.com> <0b8fe558-768f-6407-6a58-26df0f3817c6@gmail.com> <20160720143410.GS255916@eidolon>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b636b7c7-0a9a-c32e-8752-42cdd464a5d9@gmail.com>
Date: Thu, 21 Jul 2016 19:25:45 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160720143410.GS255916@eidolon>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/6UqwZtE5_d_TDRVzoIm73Ndj9V4>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Chris Bowers <cbowers@juniper.net>, homenet <homenet@ietf.org>, Jen Linkova <furry@google.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2016 07:25:43 -0000

On 21/07/2016 02:34, David Lamparter wrote:
> On Thu, Jul 21, 2016 at 01:22:15AM +1200, Brian E Carpenter wrote:
>> On 21/07/2016 01:13, Lorenzo Colitti wrote:
>>> On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:
>>>
>>>> - it's a bit unclear how an address/prefix's "source" next-hop is kept
>>>>   in association.  The simplistic approach of adding a "PA source ipv6
>>>>   address" for each of a host's configured addresses falls flat when
>>>>   more than 1 router advertises the same prefix, so I implemented it as
>>>>   a list -- however, my hack never removes entries off that.  It should
>>>>   possibly have a copy of the PA's valid time?
>>>>
>>>
>>> The way I thought of doing this would be to alternatively/additionally keep
>>> a pointer from the default router that announced a given prefix (which does
>>> have the link-local address of the router) to each address that was
>>> configured from that prefix. That way, when an address goes away you can
>>> scan the FIB and find another router to associate with that prefix.
>>>
>>> As for lifetimes expiring, you would need to have somewhere to keep dummy
>>> zero-lifetime default routes. It might be possible to do this in the FIB
>>> itself by adding a special entry that doesn't ever match anything, or has
>>> an infinite metric, or a different type...
>>
>> Please tell us ASAP if there is anything we should add to
>> https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03#section-3.2
>> or thereabouts.
> 
> I do see some trouble in use-cases where more than one actual router
> (actual = not counting extra link-local addresses on the same router) is
> present on a link, advertising the same prefix to hosts.  (This is
> reasonably likely in homenet scenarios, maybe less in enterprise.)
> 
> If the host only tracks a maximum of one RA source LL for a
> prefix/address, but the router with that LL happens to not be the one
> actually used (e.g. preference, router gone, more specific route from
> RIO, whatever else) then the functionality is lost.  It's particularly
> bad if the one RA source LL is the one prefix was first seen from (and
> then, worst-case, never updated).
> 
> (The neccessary precondition / assumption being broken there is that the
> test "was prefix X announced by router Y" doesn't report false
> negatives.  I haven't applied brain to false positives yet.)

Is this any worse than if the single default router in a traditional host
goes away, which will break all off-link packets until something happens?

I'm not saying it isn't a problem, but it doesn't sound like it's a new
problem that applies only in the multihomed case.

    Brian


From nobody Thu Jul 21 00:50:13 2016
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD1E312DADC for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 00:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.987
X-Spam-Level: 
X-Spam-Status: No, score=-3.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 jwsnPvZh5OxK for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 00:50:06 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE14C12DB19 for <homenet@ietf.org>; Thu, 21 Jul 2016 00:50:06 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id u186so8487621ita.0 for <homenet@ietf.org>; Thu, 21 Jul 2016 00:50:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BXOFuuzJ9TrlPpDdlag+yosRcD9jfOU/HsAMXO9OZ4E=; b=nS6tMP8a9FiBbzkL65lCY90OI94h4X3yPNzNOORCOHYIna8ehXGme0Jg7uJFaXGoSc yX309KQMAmWPO5eNOAAhfmFJBLIzyPoTgqyjVGBG8YG7AHJNDZ48Qy4mrj9WeF38IKRi MKiJTdRpx/MpjTrWNDxQ1z8IC7ptlpHMgXaebtqXyxofamVg1RM2tj8spZtSukhiL3fx 3UdvbXwMlzxg18TFAHb5n12g9Z7R1hn0hqs4wLQRCSmVUvc9Kafy2rnmIZJFWVH7d3QY 4g8le4cK1nm6J5c5Hzwtg1K+LRWQg4v4QMZA9upDVXiyhgmyI3dzGXIs/Zx79HMtnkei haCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BXOFuuzJ9TrlPpDdlag+yosRcD9jfOU/HsAMXO9OZ4E=; b=O+XOuXcgaP09G0AcSZd2ASFJshKWl9fm1nAOpQ8frTW+lAQyKAnD8jcKgtA40UrzfT ViHhfc5e9FrUl/C1gGMXn/FVRPMxcEUlfZ2fsbQEbYLawfINaQMRtJ7fcABXFETFkIus rG755gFgMPaeu1M8ohBlkQ1sBYKG4ZZUDNw33m24bBQZvKlNEW5qqcR1ksD3NiHrwoou HRHL1/jOu6MO5VVV2faiMMdkW9+Yarc22s3RFBSG8w3bP7ix62vFVTE8K5kY6pfnPWka lTqhaY9URf2V0r4C6JwQIYCTIpN+sORHS4PfbEigE6amcxOHwzMnu8dT5plX62kejsxX WKmw==
X-Gm-Message-State: ALyK8tISq9V7eOsfHGzaxZ81eIe5H0SNsW8Jh6YewOG6JJ8YxDs55d+r55YzB9pvbCoqwfrRAjJY4EFSUSdZmrO5
X-Received: by 10.36.137.215 with SMTP id s206mr14177462itd.82.1469087405867;  Thu, 21 Jul 2016 00:50:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.65.15.99 with HTTP; Thu, 21 Jul 2016 00:49:46 -0700 (PDT)
In-Reply-To: <20160720125458.GO255916@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 21 Jul 2016 09:49:46 +0200
Message-ID: <CAKD1Yr1-d-Bi25ZJJB4FzoRdTstAFEFjDYR_91M+dh8ZDzEQGA@mail.gmail.com>
To: David Lamparter <equinox@diac24.net>
Content-Type: multipart/alternative; boundary=94eb2c05e6ecf9495505382090b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Cb8ZLJXAxnC5eSlVQFrfHma3fRk>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, Chris Bowers <cbowers@juniper.net>, "Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2016 07:50:10 -0000

--94eb2c05e6ecf9495505382090b1
Content-Type: text/plain; charset=UTF-8

On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:

> Hence, I hacked it up for the Linux (4.5.0) kernel; patches are attached
> to this mail.  I've been able to gleam a little more detail on the idea:
>

David, do you intend to keep working on the patches? Think you could send
them to netdev as an RFC patchset, with proper signoff? Once it's on netdev
other people can iterate on them, even if you lose interest :-)

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jul 20, 2016 at 2:54 PM, David Lamparter <span dir=3D"ltr">&lt;<a href=
=3D"mailto:equinox@diac24.net" target=3D"_blank">equinox@diac24.net</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">Hence, I hacked it up for =
the Linux (4.5.0) kernel; patches are attached<br>
to this mail.=C2=A0 I&#39;ve been able to gleam a little more detail on the=
 idea:<br></blockquote><div><br></div><div>David, do you intend to keep wor=
king on the patches? Think you could send them to netdev as an RFC patchset=
, with proper signoff? Once it&#39;s on netdev other people can iterate on =
them, even if you lose interest :-)</div></div></div></div>

--94eb2c05e6ecf9495505382090b1--


From nobody Thu Jul 21 07:46:41 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377CB12D675 for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 07:46:40 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 EiH4BMNwHZGC for <homenet@ietfa.amsl.com>; Thu, 21 Jul 2016 07:46:38 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C5E12D67D for <homenet@ietf.org>; Thu, 21 Jul 2016 07:46:37 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id b199so64151904lfe.0 for <homenet@ietf.org>; Thu, 21 Jul 2016 07:46:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jT8PvqL0Cy14aSAbkapRjIZJDwpc0WzLB/cECMH7kqs=; b=anZrSrzNtzRHQE58Jlng5OeL0FWyC/y18zUkIFkSN2nThVmRhIHCnJLK5Yb1Cydgxj twTTTMV46VAbcT+AcEg9hc3FwTyD/KNI/5UtemMIligC9AxMMmM+JdIhcJVx7KNH1oua tZO6ifwpvaIkbDM/R0RNqstuv3cbxlqVMjNpMx3cU2VkvhMWQcaBYj8rSFT5Nt0xEBXJ QdRjC+c1QR/BoYSLEtN0fZL/CVbGRtg3wWk06X0XqUAaEXJsgkTWyoBKd5c4J6NL3rrv NeFkuaddKOIwtDtwkldLeKNXQJFZ6vt4+3rKcs4nvVQbPn5x8yGL6pZOiXlQ3babMTr4 Hisw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jT8PvqL0Cy14aSAbkapRjIZJDwpc0WzLB/cECMH7kqs=; b=bsrcbK6hxpZfnqoXpXbkrIiyXBp0XjoeQxbgvPtcWuwVL0lBG9y78qwss6znJkBPay kl69Zsk7NF1fQqn+ZIFEx4NlI92SNJk/10uV/pBmkZPjllbVyQSmMj3yg1fH5xOvYvUz lrgookQQ8a3+3WkjLSQ7mopga5hm6lInoEgcSWg2d6Y+lWmW7z6oYZIyYoM8V+DVK1TT kbIPQkjOOALtgq6fH/D1AQFgUISCGAi0zI2N5PJwhdlpeL+cSc+zwttIHW+dn2owljFP C5PmzUbTPCh83bS0bCbtq8FvwJxCTmMSkNkMC1Td40gwZhDcChPlqN5e4Fka/wD9ZCD1 Y8MQ==
X-Gm-Message-State: ALyK8tI0bsKoycw5JPDiHMsxoBIf4iFko4Jk+QVucpzpXHzmM8/ahE3XlA8I6a2wlT5K7BYEN9yViiwKXUUkAw==
X-Received: by 10.25.159.10 with SMTP id i10mr12478308lfe.131.1469112395361; Thu, 21 Jul 2016 07:46:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.93 with HTTP; Thu, 21 Jul 2016 07:45:55 -0700 (PDT)
In-Reply-To: <31576049-F3B3-4B89-B68A-0BE95BEAEE94@darou.fr>
References: <157EF926-8286-4496-858B-21625EF41C35@isoc.org> <31576049-F3B3-4B89-B68A-0BE95BEAEE94@darou.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 21 Jul 2016 16:45:55 +0200
Message-ID: <CAPt1N1mSQcX1osTzvPnmbrRn8adxjZ04=K=ZujCe+=ZXfc4tzg@mail.gmail.com>
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: multipart/alternative; boundary=001a11411c42760b620538266222
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/bI3vLwCto_PzSHNJ4Ftf10b31zs>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Dan York <york@isoc.org>
Subject: Re: [homenet] Thinking about the implementer - my comments at mic about .home and RFC 7788
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2016 14:46:40 -0000

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

The problem with option 1 is that it amounts to the IESG making a change to
a document that the authors don't want made and that doesn't have working
group consensus, or else you open up the document.   I think that right now
we are not really in danger of widespread implementation of homenet,
although I would be overjoyed to hear you tell me that I am wrong (Dan).

So I think the more expedient and kinder route to go is to just do a
follow-on document for now, and wrap the ultimate change, which I hope will
be to allocate .homenet as the default, into the next genuine rev of the
document.   This is less likely to demotivate the authors and the working
group by compressing the update schedule for the document, or by forcing
them/us to do a rev with only one change.

This is _not_ to say that your point (Dan) was wrong.   Just that I don't
think your proposed approach is necessary.   We still do need to consider
implementors, and that's why I think that doing two updates and _then_ a
7788bis is better than just waiting until 7788bis.   However, if we are
going to have a big fight over the followon-document that allocates a
special-use TLN for homenets, that might change my opinion.


On Thu, Jul 21, 2016 at 8:56 AM, Pierre Pfister <pierre.pfister@darou.fr>
wrote:

> Hello Dan,
>
> > I did not agree with any of the four choices offered by the chairs to
> the WG for the resolution of the RFC 7788 / .home issue.
> [...]
> >
> > I think the cleanest, simplest thing we can do *for the implementers* is
> to publish a new RFC that *obsoletes* RFC 7788.  We can then promote the
> new RFC as the definitive standard for HNCP.  RFC 7788 can get a big
> "Obsolete" warning in the places we publish it - and documentation and
> other new RFCs can reference the new RFC.
> >
>
> If my memory is correct, what you describe was actually choice #1, which
> got little humming in the room compared to 3 and 4 (and 5...).
>
> Cheers,
>
> - Pierre
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr">The problem with option 1 is that it amounts to the IESG m=
aking a change to a document that the authors don&#39;t want made and that =
doesn&#39;t have working group consensus, or else you open up the document.=
 =C2=A0 I think that right now we are not really in danger of widespread im=
plementation of homenet, although I would be overjoyed to hear you tell me =
that I am wrong (Dan).<div><br></div><div>So I think the more expedient and=
 kinder route to go is to just do a follow-on document for now, and wrap th=
e ultimate change, which I hope will be to allocate .homenet as the default=
, into the next genuine rev of the document. =C2=A0 This is less likely to =
demotivate the authors and the working group by compressing the update sche=
dule for the document, or by forcing them/us to do a rev with only one chan=
ge.</div><div><br></div><div>This is _not_ to say that your point (Dan) was=
 wrong. =C2=A0 Just that I don&#39;t think your proposed approach is necess=
ary. =C2=A0 We still do need to consider implementors, and that&#39;s why I=
 think that doing two updates and _then_ a 7788bis is better than just wait=
ing until 7788bis. =C2=A0 However, if we are going to have a big fight over=
 the followon-document that allocates a special-use TLN for homenets, that =
might change my opinion.</div><div><br></div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Thu, Jul 21, 2016 at 8:56 AM, Pierre P=
fister <span dir=3D"ltr">&lt;<a href=3D"mailto:pierre.pfister@darou.fr" tar=
get=3D"_blank">pierre.pfister@darou.fr</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Hello Dan,<br>
<span class=3D""><br>
&gt; I did not agree with any of the four choices offered by the chairs to =
the WG for the resolution of the RFC 7788 / .home issue.<br>
</span>[...]<br>
<span class=3D"">&gt;<br>
&gt; I think the cleanest, simplest thing we can do *for the implementers* =
is to publish a new RFC that *obsoletes* RFC 7788.=C2=A0 We can then promot=
e the new RFC as the definitive standard for HNCP.=C2=A0 RFC 7788 can get a=
 big &quot;Obsolete&quot; warning in the places we publish it - and documen=
tation and other new RFCs can reference the new RFC.<br>
&gt;<br>
<br>
</span>If my memory is correct, what you describe was actually choice #1, w=
hich got little humming in the room compared to 3 and 4 (and 5...).<br>
<br>
Cheers,<br>
<br>
- Pierre<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" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote></div><br></div>

--001a11411c42760b620538266222--


From nobody Fri Jul 22 04:59:34 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497DF12DB61 for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 04:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ez7Fn0yKrAAc for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 04:59:31 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EECC12D1D3 for <homenet@ietf.org>; Fri, 22 Jul 2016 04:59:31 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id x1so99021299qkb.3 for <homenet@ietf.org>; Fri, 22 Jul 2016 04:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=vbUfMqTZSgZXGas6MMQ+0/BB5MWnnGNwXQyT/3A/V2w=; b=MQ6AKGceGtIvjyAkS9Jk2vsgB7HCHNxBcdkq+2eDShunjFxAc/uea7YxORen2Mdd7c dEdTiWrnvDxgYf41v3xBGWjE764bto86ccX+PlXHrIhF6FjSZZcZHNtJHssdK10L1tmc WHTPFVb98PenbQ8Gwh+aj8qv5qPbCvAcyUEyugiv/vjL0k6nDBlqucb8YaZeqFEh3Gp3 1WQCM3OM4BNb6IejuTYFJBPngrHxVjw6uYKMLU6ZWl0/br1kt2A9iFOqdVtQJuZ9GXFQ BWBdaxs4Iw32C0oOy3Bp5Pa1u5DnakfPLgMz4YWRQx1r/LeqQFWEgOeAYWu4k8ILtGxn s00A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=vbUfMqTZSgZXGas6MMQ+0/BB5MWnnGNwXQyT/3A/V2w=; b=WWxLWQCz8/4HvmwP8woU9l8ACJhsIW+aST5S17aJl3pJUYor7Q4c3myxMxXKgjwkLk lTAcn2abYtjvfIOW/SaP60bGgRARf62HEn1kusoHXnCG0ovX3XN+YMW9NPem903MtXo/ a/C/wrflH3H9nHPnFFA0+3Pg0EgsENXDH6rC1jfTfXVU7IbC+SylrD9vMrwJQS3IwRTE jBrvQYPlVTwU59k9V7QLsV1rmFQXEP1jpCpPiUxfAYsPXmKydLigiTqCD6y/1YO6PR/w JNTAK6TWbWMVzlV0OvkelJ2g6l4qZphOXKZB1AzbG6SPqZjFJ/2XtboJCGP5ZwlTlT++ RG3A==
X-Gm-Message-State: AEkoouvy+oiVa5i4BULP3yJ1+n8e/7ft5NQsAHSaU3HCUGCg8OkmxXD6XC/9wr4p5Px4Ww==
X-Received: by 10.55.165.216 with SMTP id o207mr4172182qke.153.1469188770400;  Fri, 22 Jul 2016 04:59:30 -0700 (PDT)
Received: from rtp-vpn1-1829.cisco.com ([173.38.117.78]) by smtp.gmail.com with ESMTPSA id 55sm7145922qtm.36.2016.07.22.04.59.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 22 Jul 2016 04:59:29 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_549725A2-97DA-4928-AF66-66A962110F41"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAPt1N1mSQcX1osTzvPnmbrRn8adxjZ04=K=ZujCe+=ZXfc4tzg@mail.gmail.com>
Date: Fri, 22 Jul 2016 13:59:25 +0200
Message-Id: <CE19CB05-2B6C-486A-9DD9-1980ADBB25F0@gmail.com>
References: <157EF926-8286-4496-858B-21625EF41C35@isoc.org> <31576049-F3B3-4B89-B68A-0BE95BEAEE94@darou.fr> <CAPt1N1mSQcX1osTzvPnmbrRn8adxjZ04=K=ZujCe+=ZXfc4tzg@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/LeGCr3K1F_N-QpjcQXHbS6FD6Ro>
Cc: Dan York <york@isoc.org>, "homenet@ietf.org" <homenet@ietf.org>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Thinking about the implementer - my comments at mic about .home and RFC 7788
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 22 Jul 2016 11:59:34 -0000

--Apple-Mail=_549725A2-97DA-4928-AF66-66A962110F41
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_31254BB3-2024-43D1-80CA-7347B5B84C3B"


--Apple-Mail=_31254BB3-2024-43D1-80CA-7347B5B84C3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 21, 2016, at 4:45 PM 7/21/16, Ted Lemon <mellon@fugue.com> =
wrote:
>=20
> The problem with option 1 is that it amounts to the IESG making a =
change to a document that the authors don't want made and that doesn't =
have working group consensus, or else you open up the document.   I =
think that right now we are not really in danger of widespread =
implementation of homenet, although I would be overjoyed to hear you =
tell me that I am wrong (Dan).
>=20
> So I think the more expedient and kinder route to go is to just do a =
follow-on document for now, and wrap the ultimate change, which I hope =
will be to allocate .homenet as the default, into the next genuine rev =
of the document.   This is less likely to demotivate the authors and the =
working group by compressing the update schedule for the document, or by =
forcing them/us to do a rev with only one change.

Ted - can you say more about what, exactly, would be in your follow-on =
document, and how it would affect the status of RFC 7788?  Or, (below) =
what would be in two updates and then a 7788bis?

My suggestion is to publish an RFC 7788bis as soon as possible.  7788bis =
would omit sections 7.4 and 8, which describe DNS matters in HNCP, and =
include appropriate modifications to section 10.  7788bis would also =
obsolete RFC 7788.  Note there is an errata filed (but not verified) =
against section 7.4 that would be resolved by this step.

In my opinion, 7788bis would capture the good work in the document and =
clearly make the rest of the good technology in RFC 7788 available for =
implementation.  The WG would then revise sections 7.4 and 8 and publish =
a second RFC that extends 7788bis with the TLVs and behavior for the DNS =
matters from RFC 7788, including a name to be used as the default for =
the Domain-Name TLV and appropriate instructions to IANA to add the name =
to the Special Use Names registry.  This second RFC would take advantage =
of the IANA Registry and basic function in 7788bis to extend the =
protocol for the DNS matters.

- Ralph


>=20
> This is _not_ to say that your point (Dan) was wrong.   Just that I =
don't think your proposed approach is necessary.   We still do need to =
consider implementors, and that's why I think that doing two updates and =
_then_ a 7788bis is better than just waiting until 7788bis.   However, =
if we are going to have a big fight over the followon-document that =
allocates a special-use TLN for homenets, that might change my opinion.
>=20
>=20
> On Thu, Jul 21, 2016 at 8:56 AM, Pierre Pfister =
<pierre.pfister@darou.fr <mailto:pierre.pfister@darou.fr>> wrote:
> Hello Dan,
>=20
> > I did not agree with any of the four choices offered by the chairs =
to the WG for the resolution of the RFC 7788 / .home issue.
> [...]
> >
> > I think the cleanest, simplest thing we can do *for the =
implementers* is to publish a new RFC that *obsoletes* RFC 7788.  We can =
then promote the new RFC as the definitive standard for HNCP.  RFC 7788 =
can get a big "Obsolete" warning in the places we publish it - and =
documentation and other new RFCs can reference the new RFC.
> >
>=20
> If my memory is correct, what you describe was actually choice #1, =
which got little humming in the room compared to 3 and 4 (and 5...).
>=20
> Cheers,
>=20
> - Pierre
> _______________________________________________
> homenet mailing list
> homenet@ietf.org <mailto:homenet@ietf.org>
> https://www.ietf.org/mailman/listinfo/homenet =
<https://www.ietf.org/mailman/listinfo/homenet>
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_31254BB3-2024-43D1-80CA-7347B5B84C3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<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-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jul 21, 2016, at 4:45 PM 7/21/16, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">The problem with option 1 is that it amounts to =
the IESG making a change to a document that the authors don't want made =
and that doesn't have working group consensus, or else you open up the =
document. &nbsp; I think that right now we are not really in danger of =
widespread implementation of homenet, although I would be overjoyed to =
hear you tell me that I am wrong (Dan).<div class=3D""><br =
class=3D""></div><div class=3D"">So I think the more expedient and =
kinder route to go is to just do a follow-on document for now, and wrap =
the ultimate change, which I hope will be to allocate .homenet as the =
default, into the next genuine rev of the document. &nbsp; This is less =
likely to demotivate the authors and the working group by compressing =
the update schedule for the document, or by forcing them/us to do a rev =
with only one change.</div></div></div></blockquote><div><br =
class=3D""></div>Ted - can you say more about what, exactly, would be in =
your follow-on document, and how it would affect the status of RFC 7788? =
&nbsp;Or, (below) what would be in two updates and then a =
7788bis?</div><div><br class=3D""></div><div>My suggestion is to publish =
an RFC 7788bis as soon as possible. &nbsp;7788bis would omit sections =
7.4 and 8, which describe DNS matters in HNCP, and include appropriate =
modifications to section 10. &nbsp;7788bis would also obsolete RFC 7788. =
&nbsp;Note there is an errata filed (but not verified) against section =
7.4 that would be resolved by this step.</div><div><br =
class=3D""></div><div>In my opinion, 7788bis would capture the good work =
in the document and clearly make the rest of the good technology in RFC =
7788 available for implementation. &nbsp;The WG would then revise =
sections 7.4 and 8 and publish a second RFC that extends 7788bis with =
the TLVs and behavior for the DNS matters from RFC 7788, including a =
name to be used as the default for the Domain-Name TLV and appropriate =
instructions to IANA to add the name to the Special Use Names registry. =
&nbsp;This second RFC would take advantage of the IANA Registry and =
basic function in 7788bis to extend the protocol for the DNS =
matters.</div><div><br class=3D""></div><div>- Ralph</div><div><br =
class=3D""></div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><br=
 class=3D""></div><div class=3D"">This is _not_ to say that your point =
(Dan) was wrong. &nbsp; Just that I don't think your proposed approach =
is necessary. &nbsp; We still do need to consider implementors, and =
that's why I think that doing two updates and _then_ a 7788bis is better =
than just waiting until 7788bis. &nbsp; However, if we are going to have =
a big fight over the followon-document that allocates a special-use TLN =
for homenets, that might change my =
opinion.</div></div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><br =
class=3D""></div></div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Thu, Jul 21, 2016 at 8:56 AM, Pierre Pfister =
<span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:pierre.pfister@darou.fr" target=3D"_blank" =
class=3D"">pierre.pfister@darou.fr</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Dan,<br =
class=3D"">
<span class=3D""><br class=3D"">
&gt; I did not agree with any of the four choices offered by the chairs =
to the WG for the resolution of the RFC 7788 / .home issue.<br class=3D"">=

</span>[...]<br class=3D"">
<span class=3D"">&gt;<br class=3D"">
&gt; I think the cleanest, simplest thing we can do *for the =
implementers* is to publish a new RFC that *obsoletes* RFC 7788.&nbsp; =
We can then promote the new RFC as the definitive standard for =
HNCP.&nbsp; RFC 7788 can get a big "Obsolete" warning in the places we =
publish it - and documentation and other new RFCs can reference the new =
RFC.<br class=3D"">
&gt;<br class=3D"">
<br class=3D"">
</span>If my memory is correct, what you describe was actually choice =
#1, which got little humming in the room compared to 3 and 4 (and =
5...).<br class=3D"">
<br class=3D"">
Cheers,<br class=3D"">
<br class=3D"">
- Pierre<br class=3D"">
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br =
class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet</a><br =
class=3D"">
</blockquote></div><br class=3D""></div>
_______________________________________________<br class=3D"">homenet =
mailing list<br class=3D""><a href=3D"mailto:homenet@ietf.org" =
class=3D"">homenet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet<br =
class=3D""></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_31254BB3-2024-43D1-80CA-7347B5B84C3B--

--Apple-Mail=_549725A2-97DA-4928-AF66-66A962110F41
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXkgqdAAoJEINeeBNmFjV5780P/RD9xbbk5NZVnmItn2bwrBRU
7nOPtz0SzR5omUC0Uz7cl/PBOx37GbFukOlUDduAsH9kUAgJY6+MzZUhj1pLD76u
PsezEBDgQ+7RdEQrOIT6hHeN7S2aa6ACTmc+85PNIIFiaI/SCV0aOF7BzaMdftXg
G4G6aqdeyVE56xctHIEEAjujrI0S4R2VmieRUjh4iybcfu3ZKSWnuORdDxBvAbbo
Qsf7LIj2d0mtYDWAiuMCeN7j3gSdBD2lA2eiJjfAkvbSF+pvys5xXfKS+gC58TNV
FjoI8C3HwOkETp/FwIDFjT1pOKzJjrl0N0FQrCOWExGjkbkTxOnzFRDSTjCUZAiz
4pbMqjcow5HmTtxCuRNuWRyYWdaM/ONgyeAfy1YKlNRurtBlCbH+cl5bsYoXtUE8
qrZ6EH4gfsKFSGNGN/3VD6CeX/osSjyz6NwAnqpHdaRcAvSePpyK9WS2Fd23q00/
vVCXNiy/z91PLOJHZDb2ZvdleoiAfA6WWEfGRhEs0ypdfYt4/T1A3RBsA3w8yOY6
lKuf0uZBsRmQS/hAj6II/5ECLsmipRHQapQVvF/dbtESvl3fE4ejdgxJxWQ7tSPb
sK/yDmgJEqviEFjFc8aLs4ufmVMs+iV07bcs71qGn0i/2Am0iM6CEC+4A+awMbQC
nsr/Ggpk8NKe3R3fqJLt
=SrCf
-----END PGP SIGNATURE-----

--Apple-Mail=_549725A2-97DA-4928-AF66-66A962110F41--


From nobody Fri Jul 22 16:17:21 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6ED12E16D; Fri, 22 Jul 2016 16:17:14 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 O5KN-ahBNsh7; Fri, 22 Jul 2016 16:17:12 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8AD512E16C; Fri, 22 Jul 2016 16:17:11 -0700 (PDT)
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/56228) with ESMTP id u6MNH981008973; Sat, 23 Jul 2016 01:17:09 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C74A661F9D; Sat, 23 Jul 2016 01:17:09 +0200 (CEST)
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 UXqL42TuGLCy; Sat, 23 Jul 2016 01:17:08 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8164561FA2; Sat, 23 Jul 2016 01:17:06 +0200 (CEST)
Date: Sat, 23 Jul 2016 01:17:13 +0200
Message-ID: <87r3al5kli.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: manet@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 [194.254.61.138]); Sat, 23 Jul 2016 01:17:09 +0200 (CEST)
X-Miltered: at korolev with ID 5792A975.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5792A975.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 : 5792A975.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: <https://mailarchive.ietf.org/arch/msg/homenet/ZsYxZSX8vHTkC8e7SNEjVVOhxxA>
Cc: homenet@ietf.org
Subject: [homenet] Manet address assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 22 Jul 2016 23:17:14 -0000

This message is being sent to the manet mailing list, with homenet in CC.

I took to the microphone during this week's manet meeting to remind people
that Homenet has designed HNCP (RFC 7788), a protocol for autonomous
configuration of multilink home networks, and that it would be a terrible
missed opportunity if a protocol for manet autoconfiguration were standardised
that did not interoperate with HNCP.

We at Babel Towers are currently experimenting with HNCP in a small mesh
network.  The results are encouraging: up to some minor bugs in the
current implementation, HNCP is able to configure a (non-mobile) mesh
network with no operator intervention.  We are planning to spend some time
working on shncpd, our implementation of HNCP, until it is able to work
well in our mesh network:

  - change the link sensing mechanism to work better on persistently lossy
    links;
  - add the ability to configure just a single /128 on loopback (shncpd is
    already able to configure a /128 on each interface, which is useful
    for mesh networks but out-of-spec -- HNCP requires a /64).

If this works out, the plan is then to implement an HNCP protocol
extension that allows it to scale better in large and mobile mesh
networks; this will necessarily involve some tradeoffs, such as being
restricted to allocating /128.  I'll let you know more when I have code to
show.

Note that HNCP only does address configuration and naming; it does not
negotiate routing protocol parameters nor provide monitoring facilities.
Thus, it is not a complete solution for a MANET management protocol, and
I believe it does not conflict with the management work being done within
MANET.

Regards,

-- Juliusz


From nobody Fri Jul 22 16:28:20 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8015412E185 for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 16:28:18 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 1rteCYzxPgqp for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 16:28:17 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D34F312E18D for <homenet@ietf.org>; Fri, 22 Jul 2016 16:28:15 -0700 (PDT)
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/56228) with ESMTP id u6MNSEHA012129 for <homenet@ietf.org>; Sat, 23 Jul 2016 01:28:14 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 516FE61FA2 for <homenet@ietf.org>; Sat, 23 Jul 2016 01:28:14 +0200 (CEST)
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 XaP3wjVn_weE for <homenet@ietf.org>; Sat, 23 Jul 2016 01:28:13 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A269D61FA1 for <homenet@ietf.org>; Sat, 23 Jul 2016 01:28:12 +0200 (CEST)
Date: Sat, 23 Jul 2016 01:28:20 +0200
Message-ID: <87poq55k2z.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 [194.254.61.138]); Sat, 23 Jul 2016 01:28:14 +0200 (CEST)
X-Miltered: at korolev with ID 5792AC0E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5792AC0E.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 : 5792AC0E.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/2D4lGMh5WQ5ReyRfXmXd_CIg9t0>
Subject: [homenet] Why configuration and routing are separate
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 22 Jul 2016 23:28:18 -0000

Speaking with people at this week's IETF meeting, I've realised that some
are confused about why configuration and routing are implemented by
different protocols in Homenet.  Contrary to what might seem, this is not
some sort of weird political compromise, but a conscious technical
decision.

Routing and configuration have very different dynamics -- configuration is
much more static.  If a link becomes lossy, the prefix it is assigned by
the configuration protocol does not change, but its routing metric must
increase and be propagated across the metric.  If a router crashes, it
doesn't harm if the prefixes it assigned to its interfaces remain marked
as used for a few minutes; the routing protocol, on the other hand, must
be able to reroute within a fraction of a second.

On the other hand, the configuration protocol must be able to carry
a fairly large amount of data (on the order of 1kB per node in the current
implementation of HNCP), while the routing protocol does not -- it only
carries a single metric per address, or, in the case of link state,
a single metric per interface.

Because of that, it is best to implement routing and configuration in
different protocols, each of which is carefully designed for its intended
usage.  What is more, it avoids the need to include large amounts of
non-routing code in a routing daemon, something that the routing people,
who have spent years fine-tuning their implementation, are not likely to
take in a friendly manner (and, IMHO, rightly so).

Please let me know if you're still unconvinced.  I love arguing.

Regards,

-- Juliusz


From nobody Fri Jul 22 20:31:35 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A407612D95A for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 20:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nCmCTjssOMPC for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 20:31:31 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC0612D95E for <homenet@ietf.org>; Fri, 22 Jul 2016 20:31:31 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id o67so117094000qke.1 for <homenet@ietf.org>; Fri, 22 Jul 2016 20:31:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=VAtQlJj6fcywI24O7zRSdNJETjwQXsMufkCMM+War1k=; b=AcJTwAMxkbW2qawAhvNRHgC5mPRKbRtjewV8GW1yEKOm5ICkFDeer+XXe4TLiTOLf+ S0bZDVLNbEqTwdkG2z46K3rDNjJVokV5bKFSEeNXYA7WlqUHVvlzhLuoEEV+ngepACZO baqlvi6LojHqoYEaOTWPGJTPxR6+7/to5fs/PokrAIdkQH8y1W8u17ND3/bC4rbxtt0W VbTvCggLeQbtNjzuebEtlJ+sfvhrMe11Wp5m/+3B+zOAq/2ld7kOsc62grleZwrsBSsM aG+JBAPum1GLFnvHCkc8DNgmUCs0rkwL6/msODE3HFziXbecz19zmJDC4kG0ihDj16DN /Okw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=VAtQlJj6fcywI24O7zRSdNJETjwQXsMufkCMM+War1k=; b=e4M+JZjki90DIBF12PErNNmLvmoxMPs3G3+hSEClnUdMSF/Z5/kzdBy692QS7VCSph QRT79QSCFTfudAMWFvwVnGEug5VS478naPmKzJL0uEGhH0ko6q+0Da81DTswQaFw4vPj cCcQZdTP2WGzLXQtB0+xMfQ5dszEzkX6U2LwVpr4Khj1dBlZV+HJO44ChN9MvNyMEJtn rV4iCto4Sc4aDRjcNFDYQJ2fqqNGziYHxUU4WhhsL7Mp+ntCY5zn3ErFoG1uCeNhbeyj LO0lyI+1MfMYYjNN/UkljCir4aViddfAWIOH7W6prd6l3GggHsmmRIaj7/PPD87LXI26 gTwQ==
X-Gm-Message-State: AEkoous83tokvAGiuMtDtOrLv4X+m4PJLCIuQXVbyirY1d9mZEhA8U7CMbcr36ePPZ/aZw==
X-Received: by 10.233.216.2 with SMTP id u2mr9035788qkf.203.1469244690223; Fri, 22 Jul 2016 20:31:30 -0700 (PDT)
Received: from richs-mbp-4505.lan (pool-64-222-236-200.port.east.myfairpoint.net. [64.222.236.200]) by smtp.gmail.com with ESMTPSA id 127sm9103906qkk.19.2016.07.22.20.31.28 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 22 Jul 2016 20:31:29 -0700 (PDT)
From: Rich Brown <richb.hanover@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com>
Date: Fri, 22 Jul 2016 23:31:27 -0400
To: homenet@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pGd-HEN9nD3FelXS2rP71YK4pAk>
Subject: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 03:31:34 -0000

Folks,

I submitted this report to the LEDE bug tracker. I realize that LEDE is =
slightly different from OpenWrt, but they still track pretty closely, so =
I wonder if anyone here has thoughts about what might be happening. Many =
thanks.

Rich

---- https://bugs.lede-project.org/index.php?do=3Ddetails&task_id=3D58 =
---
I have always wanted to try out homenet. In light of the recommendation =
expressed in =
http://lists.infradead.org/pipermail/lede-dev/2016-July/001772.html, it =
looks as if LEDE would be a good platform for further experimentation.

I followed Tore Anderson=E2=80=99s excellent instructions at: =
https://blog.toreanderson.no/2015/10/11/making-a-homenet-router-out-of-ope=
nwrt.html The following is based on: LEDE r1006 and the default packages =
for hnet-full (ipset 6.24-1, and hnet-full 2016-06-28-606d7e9046..e-1).

The problem came when =E2=80=9CStep 3 - Converting WAN interface to =
Homenet=E2=80=9D didn=E2=80=99t work as described. I clicked Delete for =
the WAN interface. The entry lost its address info, but did not to =
disappear as expected. Repeated clicks made no further difference. =
Here=E2=80=99s a screenshot of what I saw. (WAN and WAN6 looked similar =
before clicking the WAN Delete button.)

http://richb-hanover.com/wp-content/uploads/2016/07/PastedGraphic-1.png

Subsequently clicking Delete for WAN6 caused the WAN6 entry to =
disappear. The WAN entry remained, keeping only its RX & TX info. =
Here=E2=80=99s the resulting screenshot.

http://richb-hanover.com/wp-content/uploads/2016/07/PastedGraphic-2.png

At this point, I should have bailed. (I did try to go further, but =
nothing that happened was encouraging.)

Other observations:=20
- I tried the same process with OpenWrt 15.05.1, ipset 6.24-1, and =
hnet-full 2015-07-10-ea2bd2bc2d..9-1. These worked as expected.
- I did not try LEDE r1006 with the older ipset & hnet-full.

My questions:

- What other troubleshooting information would be valuable?
- Is the list the right venue for this kind of report?

Thanks!

Rich=


From nobody Fri Jul 22 22:48:54 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73B6412D5E8 for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 22:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5tG2EsXDhE8N for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 22:48:51 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A8F112D19E for <homenet@ietf.org>; Fri, 22 Jul 2016 22:48:50 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id o67so118423469qke.1 for <homenet@ietf.org>; Fri, 22 Jul 2016 22:48:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=LsE3KJH0h8Rj4PxrDteT5uvRf+sJAsQpNQ7UgQ6C/gE=; b=wJYMN9eE3Z0Il74R6kvm/VSRoA58HlwZRSMzTuzZbI0h62LW4a2iCSsWqSDHIT0Fgc 5Yn2K8OT4iN7IBUZ/WU1cTc3kbPDmB8AxLVpa01GGO/YSvWSdFpqE7BCmbHlQjSBrBxV +wuhL0qFPhaez38FqylltXY7apkczHNj+xpJWTbBOAvu1uMmpZtWXEo/Fe7PgT5EtVAH 4m3u4fFGtOT3NJZNxgn7BNkhbXcVZdQQ/lR9pCheK2CS5kDWFvkgd+waqyDIGTFBfnc7 CiF5gl00ZbyfNtJCpkxSKi4Y23I5YME+RLoeFvKK4n65hKJ4aLcvVghVbjWH6TVa8EZO 61+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=LsE3KJH0h8Rj4PxrDteT5uvRf+sJAsQpNQ7UgQ6C/gE=; b=bVJXVGrjdHCmK6pZX4MV8RoaBhmwuqnwKLxDf5MYJckz1bQETpGUXROJd9WBZoJl/M 5mfltqpSumiDDYM14plaQ7JdeoFMs7B41WeyEk7a0ozSe1AoL7E/7SxEOpSAfpZRw2sn +6856SKJDAEiRUwvN38o24LL5ViGttn0InQfkrTKWuhgaYM3nTATZqRfsa45aSTPrmhe akDHwYxbiynQ6ABoCX5KMb8TEbHMZeGbXo0LpsnccbayW3H/5sn9w58PIan4xSDREIBw yBgySJjTCURGNDcILcYBOTAWsjA4ZJtkV58PoYmpFNkPOzxooh04eUVQy0AIc2boGnIA prWw==
X-Gm-Message-State: AEkoouuh5u+5SWgkv5keOApAtqjGIjElouZ3wYy8K0maBzLxBn1+9CzcpY7aYmzZUEXing==
X-Received: by 10.55.97.18 with SMTP id v18mr9078478qkb.102.1469252929804; Fri, 22 Jul 2016 22:48:49 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:136:28cc:dc4c:9703:6781? ([2001:67c:370:136:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z1sm9343070qkc.40.2016.07.22.22.48.48 for <homenet@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 22:48:48 -0700 (PDT)
To: homenet@ietf.org
References: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <abdbc950-4caa-04f1-7c19-8964dc2ac254@gmail.com>
Date: Sat, 23 Jul 2016 17:48:51 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/bNjd5ymW3bnF5oyhKaPAuNTXAAI>
Subject: Re: [homenet] Why configuration and routing are separate
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 05:48:53 -0000

On 23/07/2016 11:28, Juliusz Chroboczek wrote:
> Speaking with people at this week's IETF meeting, I've realised that some
> are confused about why configuration and routing are implemented by
> different protocols in Homenet.  Contrary to what might seem, this is not
> some sort of weird political compromise, but a conscious technical
> decision.

...

> Please let me know if you're still unconvinced.  I love arguing.

You are 100% correct. They should be separately pluggable, in fact,
in case either of the current choices proves to be a mistake later on.

(Some people may recall that I used homenet as a use case in the UCAN
BOF that preceded the Anima working group. I wish I had articulated
it as clearly as Juliusz has done in the text deleted above. It will
be an interesting exercise, once Anima has done its work, to check that
it would in fact work for a homenet, although its style would be very
different from HNCP.)

   Brian


From nobody Fri Jul 22 23:30:56 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7413F12D979 for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 23:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.588
X-Spam-Level: 
X-Spam-Status: No, score=-5.588 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, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 Nvk1cKWTvG-g for <homenet@ietfa.amsl.com>; Fri, 22 Jul 2016 23:30:52 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F2B912D5AE for <homenet@ietf.org>; Fri, 22 Jul 2016 23:30:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id F32F8A2; Sat, 23 Jul 2016 08:30:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1469255450; bh=bDXI2J+sDK75dsI9fZmNntjXmg62PJWx7BNzUFGQBYQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=4XaYy84sOpgyhClDyZDs8gAwiGLnuxR3UqhDKvCod/ykp/dwO1tH/5ZHBMlIpCxka BCnYAyr0e9h9/6U/uXVsQNKsnJOsv4Da6PJPWmY7jKAhVtc6WTLWFPHFrMTaOXrEb5 2fncna8Itwkuz/UpcupfGi1or+ZzTsrYfa13SYVk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E6FD8A1; Sat, 23 Jul 2016 08:30:49 +0200 (CEST)
Date: Sat, 23 Jul 2016 08:30:49 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
References: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr>
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: <https://mailarchive.ietf.org/arch/msg/homenet/oB5kHQNunFlFjzapGpdoNLM5qkI>
Cc: homenet@ietf.org
Subject: Re: [homenet] Why configuration and routing are separate
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 06:30:54 -0000

On Sat, 23 Jul 2016, Juliusz Chroboczek wrote:

> Please let me know if you're still unconvinced.  I love arguing.

Well, in my testing I got the feeling (hard to tell since it was really 
hard to get a comprehensive picture of what was going on over time), that 
sometimes HNCP lost its connection to other HNCP nodes on the lan, while 
babel was still working, and the other way around, babel went down and 
HNCP was up.

Having these two protocols knowing nothing about each other and each 
others' state is potential source of problems.

I'm trying to think of another case where this has caused problem. A 
non-perfect example is MPLS requiring LDP to be up before the IGP starts 
trying to use the LSP switch path. Thus the "ldp igp sync" feature that 
came in RFC5443 which was quite a lot later in time than when RFC3031 
first defined MPLS architecture. This feature came around after 
operational experience with the protocols and that them not knowing 
anything about each other caused operational problems and outages.

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


From nobody Sat Jul 23 01:27:18 2016
Return-Path: <hrogge@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED6212D67A; Sat, 23 Jul 2016 01:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DnegetzrEJHc; Sat, 23 Jul 2016 01:27:15 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCE8512D5AE; Sat, 23 Jul 2016 01:27:14 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id x1so120004430qkb.3; Sat, 23 Jul 2016 01:27:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NCyK5h18g/mzLIPR4W1kj1+PDUmMX+JV5Ek8Gj1F4NQ=; b=KcLfhSOBwfH5zMR76rmsjgjHw5K4/Chu5PUVr6tnT9UOVhbtt4E9igWP2dXgF2BiI+ 0nQYZYgSU1bWdtcKlIRrEn7hpNApz42pnB4WgR8rWK8aOa25QNP3FgAs69zogFKnMs++ T4pS7+5DGhWXdx3icHzhwaUGJ4i1sTrs5RqJD2EeaR8fB38zK6sScgynQzxoT42G5VcU 542e1+Pp4/YBFzVod2nV+FsksrI7bSU5vRhi4ubrurBONQqsY+emTGJ6vvHoglKPyHq7 Ry/pmGH5vaVoO2K8HxluyK/j3s4AHWfVDbTPu4ql92aailNo0qe0y7z+0wYrlcXU7Jne smnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NCyK5h18g/mzLIPR4W1kj1+PDUmMX+JV5Ek8Gj1F4NQ=; b=hzLO2F3uQsmz14O3abl8Y64ymMujYLfdQ3TWBfTBXl7X2WLqURDlo15KKfUyltIZyP ppYXUufCRpNihwG/YUBMC9IllpslJqCfELeyE7fdQXoM+uwlTxzLjhljNIpylMrqRaBd XU+Oqy02iDIJzCqoVg0gZv1W1wP8CkBYTyEEm7uBQwwa3dRo28wiODyvzJmFX5WIobSv 1FY9C6rRbXn0x9zszV+VvV1mR0eVAO3uriYM79OzMqwoIW1TIWNn2KKaUPa+OhVagVZe IhG2t8SsBkPoK217PDkh786fXhqdsnVbjdH7y4hPgrCb8wOerUMGXc3qfZMv0xbLxyvo V8og==
X-Gm-Message-State: AEkoousRmoDEeJOGp4RXyU5ZxQRk8KpTp0Uu5B4Jo4i5Dklg/GHybdZK6JpwL9PcXVLtXZEVhtvX2ZzuFTp62A==
X-Received: by 10.55.5.136 with SMTP id 130mr9876993qkf.185.1469262434095; Sat, 23 Jul 2016 01:27:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.46.102 with HTTP; Sat, 23 Jul 2016 01:26:44 -0700 (PDT)
In-Reply-To: <87r3al5kli.wl-jch@pps.univ-paris-diderot.fr>
References: <87r3al5kli.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Sat, 23 Jul 2016 10:26:44 +0200
Message-ID: <CAGnRvur3-Htk-iuaVwgi6R9gFXB3LCzZ9dM904aS0LYfZ=pN=Q@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/4bO3T3YX-QABERQk3pz7hJQXO3E>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [homenet] [manet] Manet address assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 08:27:17 -0000

Hi,

on the other side a well designed routing protocol does not need much
(or any) node-specific configuration... and any mesh-wide
configuration could easily deployed by the gateway inside a DNCP/HNCP
TLV.

Henning Rogge

On Sat, Jul 23, 2016 at 1:17 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
> This message is being sent to the manet mailing list, with homenet in CC.
>
> I took to the microphone during this week's manet meeting to remind people
> that Homenet has designed HNCP (RFC 7788), a protocol for autonomous
> configuration of multilink home networks, and that it would be a terrible
> missed opportunity if a protocol for manet autoconfiguration were standardised
> that did not interoperate with HNCP.
>
> We at Babel Towers are currently experimenting with HNCP in a small mesh
> network.  The results are encouraging: up to some minor bugs in the
> current implementation, HNCP is able to configure a (non-mobile) mesh
> network with no operator intervention.  We are planning to spend some time
> working on shncpd, our implementation of HNCP, until it is able to work
> well in our mesh network:
>
>   - change the link sensing mechanism to work better on persistently lossy
>     links;
>   - add the ability to configure just a single /128 on loopback (shncpd is
>     already able to configure a /128 on each interface, which is useful
>     for mesh networks but out-of-spec -- HNCP requires a /64).
>
> If this works out, the plan is then to implement an HNCP protocol
> extension that allows it to scale better in large and mobile mesh
> networks; this will necessarily involve some tradeoffs, such as being
> restricted to allocating /128.  I'll let you know more when I have code to
> show.
>
> Note that HNCP only does address configuration and naming; it does not
> negotiate routing protocol parameters nor provide monitoring facilities.
> Thus, it is not a complete solution for a MANET management protocol, and
> I believe it does not conflict with the management work being done within
> MANET.
>
> Regards,
>
> -- Juliusz
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Sat Jul 23 01:31:59 2016
Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43DE612D781; Sat, 23 Jul 2016 01:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Ame8ial2qa0U; Sat, 23 Jul 2016 01:31:51 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5F3512D755; Sat, 23 Jul 2016 01:31:50 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Sat, 23 Jul 2016 09:31:25 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [manet] Manet address assignment
Thread-Index: AQHR5G8zCuDVDZHbVUCFheQ/B2BvjKAlnkIAgAAR5WA=
Date: Sat, 23 Jul 2016 08:31:25 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801C3AA5BEC@tss-server1.home.tropicalstormsoftware.com>
References: <87r3al5kli.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvur3-Htk-iuaVwgi6R9gFXB3LCzZ9dM904aS0LYfZ=pN=Q@mail.gmail.com>
In-Reply-To: <CAGnRvur3-Htk-iuaVwgi6R9gFXB3LCzZ9dM904aS0LYfZ=pN=Q@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/D5SLQpmGXvF14jZFm0zu92d6LfA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [homenet] [manet] Manet address assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 08:31:53 -0000

Either way, it's useful information Juliusz, thanks for bringing it to the =
list!

Rick

-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
Sent: 23 July 2016 09:27
To: Juliusz Chroboczek
Cc: homenet@ietf.org Group; MANET IETF
Subject: Re: [manet] Manet address assignment

Hi,

on the other side a well designed routing protocol does not need much (or a=
ny) node-specific configuration... and any mesh-wide configuration could ea=
sily deployed by the gateway inside a DNCP/HNCP TLV.

Henning Rogge

On Sat, Jul 23, 2016 at 1:17 AM, Juliusz Chroboczek <jch@pps.univ-paris-did=
erot.fr> wrote:
> This message is being sent to the manet mailing list, with homenet in CC.
>
> I took to the microphone during this week's manet meeting to remind=20
> people that Homenet has designed HNCP (RFC 7788), a protocol for=20
> autonomous configuration of multilink home networks, and that it would=20
> be a terrible missed opportunity if a protocol for manet=20
> autoconfiguration were standardised that did not interoperate with HNCP.
>
> We at Babel Towers are currently experimenting with HNCP in a small=20
> mesh network.  The results are encouraging: up to some minor bugs in=20
> the current implementation, HNCP is able to configure a (non-mobile)=20
> mesh network with no operator intervention.  We are planning to spend=20
> some time working on shncpd, our implementation of HNCP, until it is=20
> able to work well in our mesh network:
>
>   - change the link sensing mechanism to work better on persistently loss=
y
>     links;
>   - add the ability to configure just a single /128 on loopback (shncpd i=
s
>     already able to configure a /128 on each interface, which is useful
>     for mesh networks but out-of-spec -- HNCP requires a /64).
>
> If this works out, the plan is then to implement an HNCP protocol=20
> extension that allows it to scale better in large and mobile mesh=20
> networks; this will necessarily involve some tradeoffs, such as being=20
> restricted to allocating /128.  I'll let you know more when I have=20
> code to show.
>
> Note that HNCP only does address configuration and naming; it does not=20
> negotiate routing protocol parameters nor provide monitoring facilities.
> Thus, it is not a complete solution for a MANET management protocol,=20
> and I believe it does not conflict with the management work being done=20
> within MANET.
>
> Regards,
>
> -- Juliusz
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet


From nobody Sat Jul 23 01:51:23 2016
Return-Path: <hrogge@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD3D12D626 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 01:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 m_lyro0cQ9Cb for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 01:51:19 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42E5A12B056 for <homenet@ietf.org>; Sat, 23 Jul 2016 01:51:19 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id w38so74012515qtb.0 for <homenet@ietf.org>; Sat, 23 Jul 2016 01:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m8uycQuEIWHhh6AJecJobLCXikBlNqTlzN36FGdh9Sg=; b=WXNlpEtQu1548rzSQbSfVHJb4FeZYaussBqY0ezy39llJPbhFV29L+sxtYBU6LLnTA kfVmVjZRs1sIpyMG53/EJjLoTWlObMN9xRq7GkAk10y6rRu8eBIHuHacvpnShZhZLsRk FdtqOiwo2bY7XSWLwBYRlI2EIKkLQtayDqs5GvZWfPaHQcUqcXlcUnSL219RNAzJTe7U Nizb5ljydixCgO0hlzVBPz+UHrgoRTi6t8jsY35ZU6eWm8cz6DQucLIKV3YvE4Zy8LEX mkcUJmWQvLQdQaVKhCF1jm2hPywIGxTDJes5q1EUT6q/vyZz+YH8Knr889k81eeiYoU/ 3b6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m8uycQuEIWHhh6AJecJobLCXikBlNqTlzN36FGdh9Sg=; b=kfLGNxB390ZDqvME8Yox4GN1VWOUv04KONpCZwsif2MeMDWhsls2EEZiVq2/epMuN1 nyjPZbCNv9JabAPRaJ3WE8cywEOoX50i/DGMYvJP2goCj38USOmH2UIjAbmh0mKQq2NM RPfOWCDZkwNyVoLulJy4eLkLSWRgN0bCwElLMiFge59WNtvldPqpvpHERKcHF00zSbvQ +d9gOEihsQzls+J8hxb4bn49B01tr4uir6rjFzG9u7+etc/0h92xDZu4WSSPcA4f+KdO rh6kX+RIWTVvKmqJucob0hYSjLNjVb2X6yRfBIh8Igz6x2BgpVWhZ0x4TfGj9Ap95yYp 7BfQ==
X-Gm-Message-State: AEkoousrXfeJ/XlfsjiVRyEL5bI+28wlICiqu02K+L++oL0qpvsbu6kqj9enZMxQSDAiG3WTEjNfDWpw+H8ZVg==
X-Received: by 10.200.54.243 with SMTP id b48mr13155105qtc.0.1469263878285; Sat, 23 Jul 2016 01:51:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.46.102 with HTTP; Sat, 23 Jul 2016 01:50:48 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
References: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
From: Henning Rogge <hrogge@gmail.com>
Date: Sat, 23 Jul 2016 10:50:48 +0200
Message-ID: <CAGnRvupb2_uXp28vTKOQjSc1_B0gnNfMeK_cYkfem45K3hMrXg@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/W1i7P8xikBMfeKskOnFUCgpH1aE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Why configuration and routing are separate
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 08:51:21 -0000

On Sat, Jul 23, 2016 at 8:30 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Sat, 23 Jul 2016, Juliusz Chroboczek wrote:
>
>> Please let me know if you're still unconvinced.  I love arguing.
>
> Well, in my testing I got the feeling (hard to tell since it was really hard
> to get a comprehensive picture of what was going on over time), that
> sometimes HNCP lost its connection to other HNCP nodes on the lan, while
> babel was still working, and the other way around, babel went down and HNCP
> was up.

I wonder if HNCP could have a local "port" where a routing protocol
could deliver the information that a certain linklocal neighbor
address is still reachable.

HNCP would still do its own neighbor detection, but it could take
advantage of the (regularly happening) checks of the links of the
routing.

Henning Rogge


From nobody Sat Jul 23 02:34:20 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB18012B056 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 02:34:18 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 wxPbI2VGrSoU for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 02:34:17 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2EB412B054 for <homenet@ietf.org>; Sat, 23 Jul 2016 02:34:16 -0700 (PDT)
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/56228) with ESMTP id u6N9YEx5025787; Sat, 23 Jul 2016 11:34:14 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9709961FA1; Sat, 23 Jul 2016 11:34:14 +0200 (CEST)
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 mDlqXREj3exv; Sat, 23 Jul 2016 11:34:13 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6E4CD61F9D; Sat, 23 Jul 2016 11:34:10 +0200 (CEST)
Date: Sat, 23 Jul 2016 11:34:20 +0200
Message-ID: <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 23 Jul 2016 11:34:14 +0200 (CEST)
X-Miltered: at korolev with ID 57933A16.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57933A16.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 : 57933A16.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: <https://mailarchive.ietf.org/arch/msg/homenet/uOmOCe6oB0PU42Aqh1qNCcBtqDg>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 09:34:19 -0000

> The problem came when â€śStep 3 - Converting WAN interface to Homenetâ€ť
> didnâ€™t work as described. I clicked Delete for the WAN interface.

Don't use the web interface.  Ssh into the router, and use vi on
/etc/config/network, it's easier and more reliable.

Here's how we make a Homenet router:

  opkg update
  opkg install hnet-full ip tcpdump strace
  vi /etc/config/system
  vi /etc/config/network
  vi /etc/config/wireless
  vi /etc/config/firewall
  /etc/init.d/network restart
  (check the output for errors)
  sync
  reboot

I'll publish Dorine's configuration files when I'm back in Paris, they're
a little beyond what you're interested in (they set up two mesh interfaces
and one AP on each node), but they're a good example.

-- Juliusz


From nobody Sat Jul 23 02:41:14 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A475412D587 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 02:41:13 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 bDOJ4CJV1G8a for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 02:41:12 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8245012D1A4 for <homenet@ietf.org>; Sat, 23 Jul 2016 02:41:11 -0700 (PDT)
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/56228) with ESMTP id u6N9fACG028128; Sat, 23 Jul 2016 11:41:10 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1045961F9D; Sat, 23 Jul 2016 11:41:10 +0200 (CEST)
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 po8EuxKOs4p8; Sat, 23 Jul 2016 11:41:08 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 5E54261FA1; Sat, 23 Jul 2016 11:41:06 +0200 (CEST)
Date: Sat, 23 Jul 2016 11:41:16 +0200
Message-ID: <87d1m4sncz.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
References: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
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 [194.254.61.138]); Sat, 23 Jul 2016 11:41:10 +0200 (CEST)
X-Miltered: at korolev with ID 57933BB6.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57933BB6.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 : 57933BB6.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: <https://mailarchive.ietf.org/arch/msg/homenet/kjS8GdYTyBabqf9EH5KDsUo29As>
Cc: homenet@ietf.org
Subject: Re: [homenet] Why configuration and routing are separate
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 09:41:13 -0000

> Well, in my testing I got the feeling (hard to tell since it was really
> hard to get a comprehensive picture of what was going on over time), that
> sometimes HNCP lost its connection to other HNCP nodes on the lan, while
> babel was still working, and the other way around, babel went down and
> HNCP was up.

Agreed, that's the price of having two distinct link-sensing mechanisms.

> Having these two protocols knowing nothing about each other and each
> others' state is potential source of problems.

Things are meant to be so the network will survive desynchronisation
between the two protocols:

  - HNCP up, Babel down => numbered link not used for transit;
  - HNCP down, Babel up => unnumbered link used for transit.

If either of these causes problems in your network, then something is
wrong, and I'm interested in knowing more.

-- Juliusz


From nobody Sat Jul 23 03:10:14 2016
Return-Path: <tim+ietf.org@coote.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BEF12D672 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 03:10:13 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=coote.org header.b=Knl1yFNt; dkim=pass (1024-bit key) header.d=coote.org header.b=f5Oi4A2b
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 BU4q6m9VcehK for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 03:10:11 -0700 (PDT)
Received: from mercury.coote.org (575185b4.skybroadband.com [87.81.133.180]) by ietfa.amsl.com (Postfix) with ESMTP id 19ABE12D64F for <homenet@ietf.org>; Sat, 23 Jul 2016 03:10:11 -0700 (PDT)
Received: by mercury.coote.org (Postfix, from userid 1000) id 3223316C1257; Sat, 23 Jul 2016 11:10:05 +0100 (BST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mercury.coote.org 3223316C1257
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=coote.org; s=default; t=1469268606; bh=V368oaR4s2aBmFBFa9nKE8ki9CY25+VEMVxDsUG1Fc0=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=Knl1yFNtN0Q5q42qB1FYNFk6cI4zrN8qqHEQwjFCR0HXNZD/vWMVR4mxsFIXswBjz ovYY2awp40YxB4RXCUPrYHzoVElDjArz9YUjr3VVig5zSF1GiRbYab6ND0BIpzeNUi Dd5OJcSXmvCU19I9ndbM6oGGfyGkhz4OdAEXTmNg=
X-Original-To: homenet@ietf.org
Received: from [127.0.0.1] (localhost [IPv6:::1]) by mercury.coote.org (Postfix) with ESMTP id AB04A16C0F1E; Sat, 23 Jul 2016 11:10:04 +0100 (BST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mercury.coote.org AB04A16C0F1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=coote.org; s=default; t=1469268604; bh=V368oaR4s2aBmFBFa9nKE8ki9CY25+VEMVxDsUG1Fc0=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=f5Oi4A2bMmub72c5sSL2fxrXKkB0TtIYH+OBSWAPWhUJjTyeiidKkvd6jjpZfMiIV DLjxVH9yPZLyzcqJJKgv07bFUu/gA0E0w6oKCTaFJiXMZcU7Qy6mFUmXftrWFRyUrG HP7rL2BONPAJQx8cOuyNe96UCNsZwh2fsM5bjZTc=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Tim Coote <tim+ietf.org@coote.org>
In-Reply-To: <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 23 Jul 2016 11:10:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <82409DAF-1E26-453D-84A9-097D72C1F60F@coote.org>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
X-Spambayes-Classification: ham; 0.00
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Lzb68jPF4Pp1CcSiQfjPiqHIW4c>
Cc: Rich Brown <richb.hanover@gmail.com>, homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 10:10:13 -0000

> On 23 Jul 2016, at 10:34, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> The problem came when =E2=80=9CStep 3 - Converting WAN interface to =
Homenet=E2=80=9D
>> didn=E2=80=99t work as described. I clicked Delete for the WAN =
interface.
>=20
> Don't use the web interface.  Ssh into the router, and use vi on
> /etc/config/network, it's easier and more reliable.
>=20
> Here's how we make a Homenet router:
>=20
>  opkg update
>  opkg install hnet-full ip tcpdump strace
>  vi /etc/config/system
>  vi /etc/config/network
>  vi /etc/config/wireless
>  vi /etc/config/firewall
>  /etc/init.d/network restart
>  (check the output for errors)
>  sync
>  reboot
>=20
> I'll publish Dorine's configuration files when I'm back in Paris, =
they're
> a little beyond what you're interested in (they set up two mesh =
interfaces
> and one AP on each node), but they're a good example.

Configuring and smoke testing >1 router, > once starts to look like a =
devops problem. Not least because getting consistency becomes very error =
prone and difficult to reconstruct what worked/failed.  fwiw, I found =
that tools like R/make + git on a controlling computer make the work =
more repeatable.  I see that others are using more mainstream tools such =
as Ansible.

tim=


From nobody Sat Jul 23 03:25:01 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2103612D995 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 03:25:00 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 f6hrp0jrOn0x for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 03:24:59 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C357C12D977 for <homenet@ietf.org>; Sat, 23 Jul 2016 03:24:58 -0700 (PDT)
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/56228) with ESMTP id u6NAOujq010641; Sat, 23 Jul 2016 12:24:56 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E453D61F9D; Sat, 23 Jul 2016 12:24:56 +0200 (CEST)
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 YPyVHkymZmFN; Sat, 23 Jul 2016 12:24:55 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 81D5E61FA2; Sat, 23 Jul 2016 12:24:55 +0200 (CEST)
Date: Sat, 23 Jul 2016 12:25:05 +0200
Message-ID: <87a8h8slby.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Tim Coote <tim+ietf.org@coote.org>
In-Reply-To: <82409DAF-1E26-453D-84A9-097D72C1F60F@coote.org>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <82409DAF-1E26-453D-84A9-097D72C1F60F@coote.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 [194.254.61.138]); Sat, 23 Jul 2016 12:24:56 +0200 (CEST)
X-Miltered: at korolev with ID 579345F8.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579345F8.002 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 : 579345F8.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/llA2tHS4Vl4DHMMi0L53Zzc_7RE>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 10:25:00 -0000

> Configuring and smoke testing >1 router, > once starts to look like
> a devops problem.

I think you're overthinking it.  Once your routers are up and reachable
from outside, propagating a new version of the config files is easily done
using scp.  Matthieu tends to automate that using a throw-away shell
script, I prefer to do it by hand so I know when something breaks.

-- Juliusz


From nobody Sat Jul 23 05:39:10 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68DC812B038 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 05:39:08 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 3HPjV19ZDRf7 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 05:39:06 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CDAD12B025 for <homenet@ietf.org>; Sat, 23 Jul 2016 05:39:05 -0700 (PDT)
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/56228) with ESMTP id u6NCd3tN016484; Sat, 23 Jul 2016 14:39:03 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5BD6661FA2; Sat, 23 Jul 2016 14:39:03 +0200 (CEST)
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 h2aTge5IXUnq; Sat, 23 Jul 2016 14:39:02 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id C0BE061FA1; Sat, 23 Jul 2016 14:39:00 +0200 (CEST)
Date: Sat, 23 Jul 2016 14:39:10 +0200
Message-ID: <87vazwr0k1.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
References: <87poq55k2z.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1607230821280.2309@uplift.swm.pp.se>
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 [194.254.61.138]); Sat, 23 Jul 2016 14:39:04 +0200 (CEST)
X-Miltered: at korolev with ID 57936567.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57936567.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 : 57936567.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/gPrAEE4LWae7mmPk-PghfmppgsA>
Cc: homenet@ietf.org
Subject: [homenet] More about desynchronisation [was: Why configuration and routing are separate]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 12:39:08 -0000

> Having these two protocols knowing nothing about each other and each
> others' state is potential source of problems.

I've thought about it some more (warm showers increase the flow of blood
to my brain), and I've realised that this is an important point, and one
that is close to my research interests.  So please let me ramble some more.

Given a distributed system (such as, say, a network of IS-IS nodes, or
a network of Kademlia nodes, or a network of HNCP + Babel nodes), in
transitory situtations the different states will temporarily be
inconsistent.  For example, the LS databases of OSPF nodes will
temporarily desynchronise, a node will leave the Kademlia network without
notifying its neighbours, or HNCP and Babel will have different ideas
about an adjacency being up or down.  I believe this is a law of nature --
but I haven't been able to find the theorem that says that.

(Aside: I'm positive there's a theorem that says that distributed consensus
cannot be achieved by a symmetric, deterministic algorithm, but
disappointingly enough this doesn't apply to networking protocols which use
random backoff (non-deterministic) or break ties by picking the larger
node-id (broken symmetry).  End of aside.)

It is generally considered ungentlemanly to attempt to change the laws of
nature, so people have taken two approaches to work around the problem:

  (1) minimise the time window during which nodes are desynchronised;
  (2) minimise the consequences of desynchronisation.

To give an example of approach (1), link-state routing protocols have been
carefully engineered to reflood in a timely and reliable manner -- this
aims to minimise the time during which the network is pushing packets in
the wrong direction.  Examples of (2) include Kademlia, which is designed
to survive large numbers of broken nodes (our measurements indicate that
40 to 60% of nodes in the BitTorrent DHT are broken), and protocols such
as EIGRP, DSDV or Babel, which are designed to keep pushing packets in the
right direction following loop-free paths even during reconvergence.

Note that the two approaches are not exclusive -- just because Kademlia
can deal with broken nodes doesn't mean we should be encouraging
brokenness, and just because Babel is loop-avoiding doesn't mean we should
be slowing down its convergence.  (I am not aware of any work about
transient behaviour of link-state protocols, perhaps the OLSR community
has done something related?)

I don't think it has ever been stated explicitly, but my view is that (2)
is what we are doing with HNCP + Babel: allowing the two protocols to
transiently have different ideas about adjacencies, and making sure that
nothing important breaks when that happens.  Of course, just because
nothing breaks doesn't mean that it's a desirable situation, so adding
(optional) mechanisms to minimise the likelihood of this happening is
something we should be considering.  I'm not sure that Henning's
suggestion is worth the implementation cost, however.

-- Juliusz


From nobody Sat Jul 23 08:31:39 2016
Return-Path: <tim+ietf.org@coote.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA3912D1AC for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 08:31:38 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=coote.org header.b=qY4aQ2+v; dkim=pass (1024-bit key) header.d=coote.org header.b=gT0IoJJy
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 XpF1zcQm5FaN for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 08:31:36 -0700 (PDT)
Received: from mercury.coote.org (575185b4.skybroadband.com [87.81.133.180]) by ietfa.amsl.com (Postfix) with ESMTP id 9337212B03A for <homenet@ietf.org>; Sat, 23 Jul 2016 08:31:36 -0700 (PDT)
Received: by mercury.coote.org (Postfix, from userid 1000) id 7D48D16C105A; Sat, 23 Jul 2016 16:31:03 +0100 (BST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mercury.coote.org 7D48D16C105A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=coote.org; s=default; t=1469287863; bh=PB9/1o4lYHgT98ts+ZNtKJYc8ut2AvW30w8X2FCW+Wk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=qY4aQ2+vuGi4nyCBDTXafwHI5rNp7uZHE+lmqw4pCnyQr7kUWAWYUSTLag6cNkjo1 /EdO1V0LfQoQMfkHjvJca+esv5NXbLcXdA6N50sBpHo8JXyz+PEzmr9wkyQxTFGwqt n6kzgJ7U6k1Hm+ChdZpLlPrZ5DKPG5JGB8rnDUbg=
X-Original-To: homenet@ietf.org
Received: from [127.0.0.1] (localhost [IPv6:::1]) by mercury.coote.org (Postfix) with ESMTP id 89D3116C105A; Sat, 23 Jul 2016 16:31:02 +0100 (BST)
DKIM-Filter: OpenDKIM Filter v2.10.3 mercury.coote.org 89D3116C105A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=coote.org; s=default; t=1469287862; bh=PB9/1o4lYHgT98ts+ZNtKJYc8ut2AvW30w8X2FCW+Wk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=gT0IoJJynH9Qamy/1N9XT0R1E9v9FkFh6DsAXBoK7ZssEAQUeFGK+vhThlUeQbNK5 dTB3UCaiRhSrSJ87KqXrckYVKPkXBRjwvU1Ub1M0i2A8YoGlB7YNylNLChZbiPvZhR aXh8eQJYpZC5NMwoRF0C/2NVbXYgMJXGsEVhejOw=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Tim Coote <tim+ietf.org@coote.org>
In-Reply-To: <87a8h8slby.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 23 Jul 2016 16:31:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F32EDA7-FF45-4844-9E86-153ED7689F05@coote.org>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <82409DAF-1E26-453D-84A9-097D72C1F60F@coote.org> <87a8h8slby.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
X-Spambayes-Classification: ham; 0.00
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/_FG_0dB6WHZAJx_RWvP4fpv8vQE>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 15:31:38 -0000

> On 23 Jul 2016, at 11:25, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
> I think you're overthinking it.  Once your routers are up and =
reachable
> from outside, propagating a new version of the config files is easily =
done
> using scp.  Matthieu tends to automate that using a throw-away shell
> script, I prefer to do it by hand so I know when something breaks.


scp + control (bash is fine, if that=E2=80=99s what comes to hand) was =
all that I had in mind, with git to manage variation over time and so =
that I could see what I=E2=80=99d actually set up. Smoke tests just =
catch the intermittent errors, that either I=E2=80=99d typically miss or =
get frustrated restarting a bunch of devices until they came up in the =
right order. =20

Maybe I=E2=80=99m just much less good at getting the configurations =
right first time ;-)

Whatever works.=


From nobody Sat Jul 23 12:25:14 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5113B12D66C for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 12:25:13 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 8Z5tcy1AwA_K for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 12:25:11 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CA0F12D639 for <homenet@ietf.org>; Sat, 23 Jul 2016 12:25:11 -0700 (PDT)
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/56228) with ESMTP id u6NJP9JK017783; Sat, 23 Jul 2016 21:25:09 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3A63661FA3; Sat, 23 Jul 2016 21:25:09 +0200 (CEST)
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 78WFiyshnMEz; Sat, 23 Jul 2016 21:25:08 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A3FAD61FA2; Sat, 23 Jul 2016 21:25:06 +0200 (CEST)
Date: Sat, 23 Jul 2016 21:25:17 +0200
Message-ID: <871t2kyx5u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Tim Coote <tim+ietf.org@coote.org>
In-Reply-To: <8F32EDA7-FF45-4844-9E86-153ED7689F05@coote.org>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <82409DAF-1E26-453D-84A9-097D72C1F60F@coote.org> <87a8h8slby.wl-jch@pps.univ-paris-diderot.fr> <8F32EDA7-FF45-4844-9E86-153ED7689F05@coote.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 23 Jul 2016 21:25:09 +0200 (CEST)
X-Miltered: at korolev with ID 5793C495.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5793C495.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 : 5793C495.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: <https://mailarchive.ietf.org/arch/msg/homenet/-G4cxc63kujmpKavlJ8Kuc9EGns>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 19:25:13 -0000

> Maybe Iâ€™m just much less good at getting the configurations right first
> time

In my experience, it's only the first two or three years that are difficult.

-- Juliusz


From nobody Sat Jul 23 14:16:59 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A702712D0E2 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 14:16:57 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 W7EqqOr3FVIt for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 14:16:56 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CCAE12B074 for <homenet@ietf.org>; Sat, 23 Jul 2016 14:16:55 -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/56228) with ESMTP id u6NLGsnQ003524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 23 Jul 2016 23:16:54 +0200
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/56228) with ESMTP id u6NLGrAv008358; Sat, 23 Jul 2016 23:16:54 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C651A61FA1; Sat, 23 Jul 2016 23:16:53 +0200 (CEST)
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 P57RpHD7rZLR; Sat, 23 Jul 2016 23:16:52 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [80.156.72.98]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id CA72161F9D; Sat, 23 Jul 2016 23:16:51 +0200 (CEST)
Date: Sat, 23 Jul 2016 23:17:01 +0200
Message-ID: <87fur0xdf6.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com>
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]); Sat, 23 Jul 2016 23:16:54 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 23 Jul 2016 23:16:54 +0200 (CEST)
X-Miltered: at korolev with ID 5793DEC6.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5793DEC5.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5793DEC6.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: 5793DEC5.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 : 5793DEC6.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5793DEC5.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: <https://mailarchive.ietf.org/arch/msg/homenet/vVai-CSl3yQW-4vuF0HCw6eETZw>
Cc: HOMENET <homenet@ietf.org>
Subject: [homenet] dot-homenet [was: What I really meant by option 5]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 23 Jul 2016 21:16:58 -0000

> But I think we all accept that there's going to have to be a special-use
> top-level name allocated. That name is either going to be '.home' or
> '.homenet' as far as I can tell.

Ted,

Is this domain meant to be specific to HNCP, or is it a generic site-local
domain for home networks?  If the former, then I'm mostly okay with .homenet.
If the latter, then I amn't.

(Do you think we could get .tbd?  That would be the best way to confuse
implementers.)

-- Juliusz


From nobody Sat Jul 23 17:51:35 2016
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D270312D650 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 17:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JBppmv13MnAg for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 17:51:32 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F042012D7F4 for <homenet@ietf.org>; Sat, 23 Jul 2016 17:51:31 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id x1so130484465qkb.3 for <homenet@ietf.org>; Sat, 23 Jul 2016 17:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=dlr31vVLAJf92XB0ddPhZmY7YmCwRMSijITImGvUmvQ=; b=R+VrHIWAgSKiepS1h9Kn8JOJujX/FmTB2r20CR2+6mEcrobeATgvQwqxUzAa0jy+D3 jv2ETByhq1TGra9y9952i2iyvYb46aVCxmk5fvU1dgyCQRRFVRAler17Rza8eulx1QQt fM39lZ+fB2MbGGQzxhsQmcqWXgQK684tYy3NAopDkVZ9qhOJ58BvkDvX6hq2ymakfgNX suNgAdDzWOBnuXsxYIzJhy3B9vuJnpm7vqPmz1G3giRm202zF8yx324Nh7XSz0D0U9eQ XifC6vXIBsXwtzaIKXGVBL3oUrv9VWxlQZR66XvGAsmiyWpapRbPYbzumuY1TuNoFO0E XN5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=dlr31vVLAJf92XB0ddPhZmY7YmCwRMSijITImGvUmvQ=; b=YNKUc5h9VFUotchW5LfuNc75BsUtzYUIVp2HY3aQ2b+jupTaYARCyVq7cDeUj2Jcr6 xV7y6lSyNab1xtDbYg93HLADVCdeFlNI1SuGxdMZFs9l3eQusbeiG6GMm76R2i+Vwwo6 fjQm6bfQD9o2HIQvIHSfd61zYbU7zC5EV8pYZfDMlp4rQSF/dVafn+OQSQyW4CdDZ8Yn vbv2dVaVRfY+30GXnkm0lBGBlAALaDa9xuEw9ZB2kw9ldEcfHPLQFctBmTFpjg/XHbBp olxIfgqe/C/Ii4LXfbFfiP7/5rYzmAPeCg7v37O1RfZzfxJQD41osCBUgC0aIfwZjCfe rGcg==
X-Gm-Message-State: AEkoouvwwy4qjfmeblxptzfpT0ZFvOftTWfGUCaHw9xG2W594kezw8z+T3lfQwtU3GP8sQ==
X-Received: by 10.55.87.194 with SMTP id l185mr13623328qkb.78.1469321484733; Sat, 23 Jul 2016 17:51:24 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:247e:9998:e088:c16b? ([2601:18f:801:600:247e:9998:e088:c16b]) by smtp.gmail.com with ESMTPSA id s52sm11392435qtc.4.2016.07.23.17.51.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 23 Jul 2016 17:51:24 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0A3B0F3F-140C-4329-BBEC-0080E7E9BD1F"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <87fur0xdf6.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 23 Jul 2016 20:51:22 -0400
Message-Id: <1A5E1810-70C7-4B10-9A6C-C5484207A917@gmail.com>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com> <87fur0xdf6.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/C7ZX0ez7eSk2_KB0uwUB2Y99P6M>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] dot-homenet [was: What I really meant by option 5]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 24 Jul 2016 00:51:34 -0000

--Apple-Mail=_0A3B0F3F-140C-4329-BBEC-0080E7E9BD1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jul 23, 2016, at 5:17 PM 7/23/16, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> But I think we all accept that there's going to have to be a =
special-use
>> top-level name allocated. That name is either going to be '.home' or
>> '.homenet' as far as I can tell.
>=20
> Ted,
>=20
> Is this domain meant to be specific to HNCP, or is it a generic =
site-local
> domain for home networks?  If the former, then I'm mostly okay with =
.homenet.
> If the latter, then I amn't.

Good question.  Seems like we need to come to consensus on a reasonably =
formal definition of the desired behavior for ".new-label", and then we =
can decide whether that definition is just appropriate for a home =
network or for other scenarios, as well.

For example, if the scope of the "site" used for site-local evaluation =
depends on the network edge definition from HNCP, then ".new-local" =
might only be appropriate for deployment scenarios that include HNCP.

- Ralph

>=20
> (Do you think we could get .tbd?  That would be the best way to =
confuse
> implementers.)
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_0A3B0F3F-140C-4329-BBEC-0080E7E9BD1F
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 - http://gpgtools.org

iQIcBAEBCAAGBQJXlBEKAAoJEINeeBNmFjV5H8IP/2UpGxmNP7g348+Wnge8n4/1
I9dg1KdKJSAGmgP9830ycJhRyh8O2hPij1yM7vrglcy0Nx/wgyFFXgj1iM7/2F5u
iTABX2VYXLMkCfgbHScQekShT6cytj63NqdN51xegagpJ6JrgnlvRHwg1sp9jHfC
ckzKJnWdZwh9kAAoXzwiPkTwVbtgxQ2B7O/wvEGqgJCjgx5I+KXSe5iKNSkILmNc
viP+okf6vR6Q6zlqY2od6E6FxLSZTuAd2KG/pK6qeaZJKSq8x2+JQ9OvbdvgpM6V
YylhinsBLij1jHlmi0C4XE/yFbyEysHsL4vaEpF0Lfgl4I2RUNQ6TRmmjS5Ddaym
52021fvKaRSDX9AGkzyHTehbZjCVH2JpAIWjGaQ0daW4cGunqp9/ZZ3frN1lBxRP
HkLYEWjRsWxxdzmBRetWJ9dV0C3K+dXnZgJ1CXa9L0FMWofJqrnXozKJcC0eA07f
V3QvC8nMG+yV4k8u0LCt7FegcaSbVdbvUyMYdJghE7khfxJvF6sc6SEOeh6HC1IK
ehA6693d4jX9qrSrD7xaK2c4cNd6J4A+lcISbVsLRYt2xixJkFlZx8qzZWyXyyb/
0kkSoJiAjaG3820tPKiLDyvx6lle9KbEQO8qbOb4oPwIQRJUavgWnwT1WbeA4C2n
6NVvZ1tMMpUqdoOXcHkB
=jjeo
-----END PGP SIGNATURE-----

--Apple-Mail=_0A3B0F3F-140C-4329-BBEC-0080E7E9BD1F--


From nobody Sat Jul 23 23:46:50 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB2C12D802 for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 23:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 WKF3W0XxC22c for <homenet@ietfa.amsl.com>; Sat, 23 Jul 2016 23:46:46 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE8B12D7BE for <homenet@ietf.org>; Sat, 23 Jul 2016 23:46:46 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id g62so109640125lfe.3 for <homenet@ietf.org>; Sat, 23 Jul 2016 23:46:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=q6nUkCsIYRBuupOTU+YBQMrTmE7gbJjDewPkSEFIdhQ=; b=pHasdZPuVlTeY4nv5ghOboz4AdkcuuuOmHo4IqY4oOk8OooO5zJwuaKK0p8R7GJFkz i1UcsC4r1xYQbi1KRJdYp1xsb4s+W1KoEHeGo2C5gXic36nEBPaGaom3DTmON3Zwag/4 Os8ULsduYjTJPeaZ4o3vgn+xrFOW/YUsYQz9IzwOJC+E8NWV3jrhClZC+csiQ8PrJgvA Ft2+ASSIyY6vLtOVgsla//hZSuOUTGvmYHk97WVSok3LcQUCZG+Nj61CJNHpq48hBlEQ LDHYnUMQbvuzxA/9tBy/SVofMyDFbpytqtTSL0q2DhOxS+i6/AlWmKe8CzMeNhiMfVHQ SfDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=q6nUkCsIYRBuupOTU+YBQMrTmE7gbJjDewPkSEFIdhQ=; b=bg6JoEM2U2yyAs1Lgijrk8AOkkDySYC0EJ6vpdGHtOaQBINHtQfVcWc8C6fSH+9JBk Gmopstbj5+wS+dMYG3iCg4EMp9ThKVSY5IRI3dAOjZPWOsuiq1SvbwMgm1cIoCUwPilH Xg7RrBmxcjZMTw4EduQiMe1DHzbVXDLepsbf+KXt81tTwv0LqG4wV/MC8FlESGGl+h1S Bn7urDDUIrwGQPjzpcPWNh0GMF9Cn5avwv80ik54zOF6LYQ33EaemupWUetKnahWfusj lmZ8SgZVLiS+bEdPInxJ4lZi+8tBOi45NPPKTRLcabE6iazhooIpK+IzNt34aEXT1cLo l2PQ==
X-Gm-Message-State: AEkoouu+WbaR/HcmTJs0zoWQb/NOU7apOmUeBgQB/TwvsUdq4wysWyOm2S4EbgSwvwmU+8Wqb0DZMl9eMC6YiQ==
MIME-Version: 1.0
X-Received: by 10.25.131.150 with SMTP id f144mr5029699lfd.53.1469342804412; Sat, 23 Jul 2016 23:46:44 -0700 (PDT)
Received: by 10.25.217.93 with HTTP; Sat, 23 Jul 2016 23:46:44 -0700 (PDT)
Received: by 10.25.217.93 with HTTP; Sat, 23 Jul 2016 23:46:44 -0700 (PDT)
In-Reply-To: <1A5E1810-70C7-4B10-9A6C-C5484207A917@gmail.com>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com> <87fur0xdf6.wl-jch@pps.univ-paris-diderot.fr> <1A5E1810-70C7-4B10-9A6C-C5484207A917@gmail.com>
Date: Sun, 24 Jul 2016 08:46:44 +0200
Message-ID: <CAPt1N1kFcyCxYNR=2mnSMOmwm4=zmWbdVMfYxvDf7jEorocQ6Q@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a113f20b8e91ff305385c07ae
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/NKmbFdBh-fW_EluWKyZ4mGzilNU>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] dot-homenet [was: What I really meant by option 5]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 24 Jul 2016 06:46:49 -0000

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

.LSD would be the obvious choice (local service discovery). However, it
would be confusing to users. .LAN would be another good alternative except
that it's already a bit polluted, and the meaning isn't widely understood.
I think in the general case what we want is a global name. In the cases
where .HOMENET would be wrong, a global name would be more appropriate
anyway. The motivating used case for .HOMENET really is the homenet. The
problem we have in 7788 is that the hncp doc really wasn't the right place
to make that choice in the first place. So trying to fit the choice to all
possible uses of hncp, for which I know you have great ambitions, is
probably the wrong thing to do.

On Jul 24, 2016 02:51, "Ralph Droms" <rdroms.ietf@gmail.com> wrote:

>
> > On Jul 23, 2016, at 5:17 PM 7/23/16, Juliusz Chroboczek <
> jch@pps.univ-paris-diderot.fr> wrote:
> >
> >> But I think we all accept that there's going to have to be a special-use
> >> top-level name allocated. That name is either going to be '.home' or
> >> '.homenet' as far as I can tell.
> >
> > Ted,
> >
> > Is this domain meant to be specific to HNCP, or is it a generic
> site-local
> > domain for home networks?  If the former, then I'm mostly okay with
> .homenet.
> > If the latter, then I amn't.
>
> Good question.  Seems like we need to come to consensus on a reasonably
> formal definition of the desired behavior for ".new-label", and then we can
> decide whether that definition is just appropriate for a home network or
> for other scenarios, as well.
>
> For example, if the scope of the "site" used for site-local evaluation
> depends on the network edge definition from HNCP, then ".new-local" might
> only be appropriate for deployment scenarios that include HNCP.
>
> - Ralph
>
> >
> > (Do you think we could get .tbd?  That would be the best way to confuse
> > implementers.)
> >
> > -- Juliusz
> >
> > _______________________________________________
> > homenet mailing list
> > homenet@ietf.org
> > https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<p dir=3D"ltr">.LSD would be the obvious choice (local service discovery). =
However, it would be confusing to users. .LAN would be another good alterna=
tive except that it&#39;s already a bit polluted, and the meaning isn&#39;t=
 widely understood. I think in the general case what we want is a global na=
me. In the cases where .HOMENET would be wrong, a global name would be more=
 appropriate anyway. The motivating used case for .HOMENET really is the ho=
menet. The problem we have in 7788 is that the hncp doc really wasn&#39;t t=
he right place to make that choice in the first place. So trying to fit the=
 choice to all possible uses of hncp, for which I know you have great ambit=
ions, is probably the wrong thing to do. </p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 24, 2016 0=
2:51, &quot;Ralph Droms&quot; &lt;<a href=3D"mailto:rdroms.ietf@gmail.com">=
rdroms.ietf@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><br>
&gt; On Jul 23, 2016, at 5:17 PM 7/23/16, Juliusz Chroboczek &lt;<a href=3D=
"mailto:jch@pps.univ-paris-diderot.fr">jch@pps.univ-paris-diderot.fr</a>&gt=
; wrote:<br>
&gt;<br>
&gt;&gt; But I think we all accept that there&#39;s going to have to be a s=
pecial-use<br>
&gt;&gt; top-level name allocated. That name is either going to be &#39;.ho=
me&#39; or<br>
&gt;&gt; &#39;.homenet&#39; as far as I can tell.<br>
&gt;<br>
&gt; Ted,<br>
&gt;<br>
&gt; Is this domain meant to be specific to HNCP, or is it a generic site-l=
ocal<br>
&gt; domain for home networks?=C2=A0 If the former, then I&#39;m mostly oka=
y with .homenet.<br>
&gt; If the latter, then I amn&#39;t.<br>
<br>
Good question.=C2=A0 Seems like we need to come to consensus on a reasonabl=
y formal definition of the desired behavior for &quot;.new-label&quot;, and=
 then we can decide whether that definition is just appropriate for a home =
network or for other scenarios, as well.<br>
<br>
For example, if the scope of the &quot;site&quot; used for site-local evalu=
ation depends on the network edge definition from HNCP, then &quot;.new-loc=
al&quot; might only be appropriate for deployment scenarios that include HN=
CP.<br>
<br>
- Ralph<br>
<br>
&gt;<br>
&gt; (Do you think we could get .tbd?=C2=A0 That would be the best way to c=
onfuse<br>
&gt; implementers.)<br>
&gt;<br>
&gt; -- Juliusz<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; homenet mailing list<br>
&gt; <a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><=
br>
<br>
</blockquote></div></div>

--001a113f20b8e91ff305385c07ae--


From nobody Sun Jul 24 14:03:18 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D41512D169 for <homenet@ietfa.amsl.com>; Sun, 24 Jul 2016 14:03:17 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 ozdI0Fkvm6yk for <homenet@ietfa.amsl.com>; Sun, 24 Jul 2016 14:03:15 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A64212B00B for <homenet@ietf.org>; Sun, 24 Jul 2016 14:03:15 -0700 (PDT)
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/56228) with ESMTP id u6OL3DQA010165 for <homenet@ietf.org>; Sun, 24 Jul 2016 23:03:13 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3729261F9D for <homenet@ietf.org>; Sun, 24 Jul 2016 23:03:13 +0200 (CEST)
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 8R0GWJt4fXCJ for <homenet@ietf.org>; Sun, 24 Jul 2016 23:03:12 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E03AB61FA1 for <homenet@ietf.org>; Sun, 24 Jul 2016 23:03:10 +0200 (CEST)
Date: Sun, 24 Jul 2016 23:03:26 +0200
Message-ID: <8737myiw9t.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=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 24 Jul 2016 23:03:13 +0200 (CEST)
X-Miltered: at korolev with ID 57952D11.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57952D11.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 : 57952D11.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: <https://mailarchive.ietf.org/arch/msg/homenet/96rluS0mI0Nuj1vWT3-6yUTVuaw>
Subject: [homenet] xn--home
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 24 Jul 2016 21:03:17 -0000

I have been informed by private mail that xn--home encodes to ăŻťăŻź.

(Just kidding.  Thanks to all for a pleasant IETF.)

-- Juliusz


From nobody Mon Jul 25 07:13:45 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: homenet@ietf.org
Delivered-To: homenet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5EC12D87A; Mon, 25 Jul 2016 07:13:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <homenet-chairs@ietf.org>, <homenet@ietf.org>, <draft-lemon-homenet-naming-architecture@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160725141344.11445.49375.idtracker@ietfa.amsl.com>
Date: Mon, 25 Jul 2016 07:13:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/VGJefQWOfiYL6erXjzCxw1ZXej8>
Subject: [homenet] The HOMENET WG has placed draft-lemon-homenet-naming-architecture in state "Candidate for WG Adoption"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 25 Jul 2016 14:13:44 -0000

The HOMENET WG has placed draft-lemon-homenet-naming-architecture in
state 
Candidate for WG Adoption (entered by Ray Bellis)

The document is available at
https://datatracker.ietf.org/doc/draft-lemon-homenet-naming-architecture/


From nobody Mon Jul 25 13:24:01 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFDF12DA03 for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 13:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 PgHTbVtORCJv for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 13:23:57 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC44912D885 for <homenet@ietf.org>; Mon, 25 Jul 2016 13:23:57 -0700 (PDT)
Received: from trurl.pps.univ-paris-diderot.fr (unknown [IPv6:2a01:e34:ec22:84a1:4149:227c:fa5b:2b1c]) by smtp6-g21.free.fr (Postfix) with ESMTPS id 7487E78039F for <homenet@ietf.org>; Mon, 25 Jul 2016 18:44:51 +0200 (CEST)
Date: Mon, 25 Jul 2016 22:23:54 +0200
Message-ID: <87k2g9xy91.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
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/m05uUCGT2XyQ3NYEOVglKHhqb7Y>
Subject: Re: [homenet] The HOMENET WG has placed draft-lemon-homenet-naming-architecture in state "Candidate for WG Adoption"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 25 Jul 2016 20:23:59 -0000

I would like to reiterate my opposition to four requirements of this
draft (as described in my mail of 18 July):

 - the requirement for a new ND option;
 - the requirement for a RESTful management API;
 - the requirement for a local DNS resolver on each link;
 - the requirement for a ULA.

Speaking as the author of one of only two implementations of HNCP, I would
like to be very clear that I shall not implement a RESTful management API,
and I shall not implement a local DNS resolver.  I will also not make it
compulsory to deploy a ULA, although I'm willing to make it the default
behaviour.  (I have no objection to implementing the ND option, assuming
that somebody else gets it deployed in host implementations.)

I believe that it would be premature to adopt this draft now, at least
until people have had a chance to consider the consequences for
implementations.  The best way IMO would be to have a prototype implementation,
which I will be glad to review.

I shall not make too much of a fuss should the WG decide to adopt this
draft notwithstanding my objections.  However, I reserve the right to say
"I told you so" when we eventually run into trouble.

-- Juliusz

P.S. Our mail server is down until Thursday, please reply to the list.


From nobody Mon Jul 25 14:19:10 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3AF12D0CE for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 14:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 9kkrHxn3Vhr9 for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 14:19:07 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E7A012D0CA for <homenet@ietf.org>; Mon, 25 Jul 2016 14:19:07 -0700 (PDT)
Received: from trurl.pps.univ-paris-diderot.fr (unknown [IPv6:2a01:e34:ec22:84a1:4149:227c:fa5b:2b1c]) by smtp6-g21.free.fr (Postfix) with ESMTPS id 84573780374 for <homenet@ietf.org>; Mon, 25 Jul 2016 19:40:02 +0200 (CEST)
Date: Mon, 25 Jul 2016 23:19:05 +0200
Message-ID: <87fuqxxvp2.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
In-Reply-To: <87k2g9xy91.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/9BSTlK5ev1OIYK2bfHC8tPeO0T4>
Subject: Re: [homenet] The HOMENET WG has placed draft-lemon-homenet-naming-architecture in state "Candidate for WG Adoption"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 25 Jul 2016 21:19:09 -0000

> I have no objection to implementing the ND option

I retract that.  I realise I don't know how difficult this is to implement
in deployed host implementations, so I shouldn't be expressing an opinion.

-- Juliusz


From nobody Mon Jul 25 14:30:37 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969FA12D0FA for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 14:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 tpVg-oSHXArs for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 14:30:32 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B929312D0CA for <homenet@ietf.org>; Mon, 25 Jul 2016 14:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Jl5cMPcjlNmGS+3UDPqNY+0OVrjO1OlE23AloTP/5u4=; b=DlbKvddoy7hc63KAZz1zM0CI0MiJLwX3D7hiXDCLjukhqBfbEqRrLurgiUweWWwAkNnEjdlujX7ItYGji8IRaKks8DSyrhXsvEUsPGJt9m0fNx0R7GMasbpU1yejzwZNeRcfrIHGwFdxaTRyLUp9auUEb1ZpFVURp038zi/aimE=
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-ve1eur03lp0152.outbound.protection.outlook.com [213.199.154.152]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-7-U0GCZFIONbq-9ljXSz-7Gg-1; Mon, 25 Jul 2016 22:30:27 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Mon, 25 Jul 2016 21:30:24 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0539.023; Mon, 25 Jul 2016 21:30:25 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [homenet] Naming: a strawman counter-proposal
Thread-Index: AQHR4mkGAbTYPSpN70yleE0YM5J1W6AhUAKAgAhjFgA=
Date: Mon, 25 Jul 2016 21:30:24 +0000
Message-ID: <176130D7-43F7-4B0D-BB79-FFE3ABE52890@jisc.ac.uk>
References: <87zipcaccd.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1muDX6EFjQy6N3T4HCe13r3Z3BL-x_GUq9CsbT+mz=2Bg@mail.gmail.com>
In-Reply-To: <CAPt1N1muDX6EFjQy6N3T4HCe13r3Z3BL-x_GUq9CsbT+mz=2Bg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:a88:d510:1101:829:f3ee:fc02:77e0]
x-ms-office365-filtering-correlation-id: 677fcacc-bc82-4b97-1640-08d3b4d2e40f
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 20:IzPMi/PA6wVBvmvYQB/2I8wS9LBBXjmXT/XBeLEANQyIhCEdjf8tIduqfWJnCvqQjbB7nO5/6JPd3yKXC/qjhUD9z7/I5q/PUvDnbS4aS2kb6dqf5AdX89KUqZUdLNta+3Op4uvYp1hsqYGgbCBSab2Bt2OuGNawjDVyDS57cHw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB4543A2F0DE88DB75680FE36D60D0@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 0014E2CF50
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(199003)(377454003)(189002)(24454002)(81166006)(81156014)(122556002)(8936002)(189998001)(50986999)(57306001)(101416001)(50226002)(19580395003)(19580405001)(36756003)(3280700002)(77096005)(10400500002)(76176999)(97736004)(106356001)(2906002)(82746002)(7736002)(7846002)(8676002)(92566002)(7906003)(106116001)(4326007)(16236675004)(19617315012)(110136002)(74482002)(83716003)(2900100001)(33656002)(68736007)(2950100001)(5002640100001)(86362001)(586003)(87936001)(105586002)(15975445007)(102836003)(6116002)(561944003)(3660700001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2016 21:30:25.0156 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
X-MC-Unique: U0GCZFIONbq-9ljXSz-7Gg-1
Content-Type: multipart/alternative; boundary="_000_176130D743F74B0DBB79FFE3ABE52890jiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ZX0YUe-4ka_Rwjgwsyi65TihxvI>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Naming: a strawman counter-proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 25 Jul 2016 21:30:35 -0000

--_000_176130D743F74B0DBB79FFE3ABE52890jiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

On 20 Jul 2016, at 14:27, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.c=
om>> wrote:

This proposal doesn't satisfy the problem statement.

(which nobody wrote. :)

I don't want to tube on writing a formal requirements doc before we finish =
doing a naming architecture, but I think now that I've taken a stab at this=
, we should think about our reactions to and see if we can scope the proble=
m we are trying to solve in a bit more detail than just "naming and service=
 discovery on home nets."

I think we came to this conclusion in dnssd too, from you seeding the discu=
ssion in the context of service discovery in a =93flat namespace homenet" t=
here.

Tim


On Wed, Jul 20, 2016 at 11:27 AM, Juliusz Chroboczek <jch@pps.univ-paris-di=
derot.fr<mailto:jch@pps.univ-paris-diderot.fr>> wrote:
Not proposing this seriously, just attempting to explore the design space.
Some of the ideas are due to Toke.

Zones and authoritative nameservers are announced over HNCP together with
their set of addresses, which SHOULD include a LUA and MUST include at
least one IPv6 address.  There are two bits associated with each
authoritative nameserver:

  - default: set to 1 if the zone is suitable for name registration without
    explicit user configuration;
  - public: set to 1 if the zone is visible from the public internet.

When a router joins the homenet, it MAY announce itself as the new
authoritative nameserver for a zone.  It SHOULD do so if there is no
default public or private zone.

If there are two default private zones or two default public zones, we
call an election, Highlander-style.  If there are two authoritative
nameservers for the same zone, we call an election.

There are no secondaries.  If there are secondaries, their configuration
is outside the scope of this mail.

Stateful DHCP servers SHOULD register their clients with the authoritative
nameserver for the default private zone using your favourite unicast
mechanism.  Clients MAY register themselves with any zone currently
announced (they learn the server addresses through HNCP snooping or a from
new ND option, I don't care).

mDNS proxying into the default private zone is allowed.  Or recommended,
I'm not sure, only implementation experience will tell.

Why exactly am I speaking nonsense?

-- Juliusz

_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet

_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet


--_000_176130D743F74B0DBB79FFE3ABE52890jiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <019C250126844E4D8BB06BF93A855259@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
On 20 Jul 2016, at 14:27, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com"=
 class=3D"">mellon@fugue.com</a>&gt; wrote:<br class=3D"">
<div>
<blockquote type=3D"cite" class=3D""><br class=3D"Apple-interchange-newline=
">
<div class=3D"">
<div dir=3D"ltr" class=3D"">This proposal doesn't satisfy the problem state=
ment.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">(which nobody wrote. :)</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I don't want to tube on writing a formal requirements doc b=
efore we finish doing a naming architecture, but I think now that I've take=
n a stab at this, we should think about our reactions to and see if we can =
scope the problem we are trying to
 solve in a bit more detail than just &quot;naming and service discovery on=
 home nets.&quot;</div>
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
<div>I think we came to this conclusion in dnssd too, from you seeding the =
discussion in the context of service discovery in a =93flat namespace homen=
et&quot; there.</div>
<div><br class=3D"">
</div>
Tim</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Wed, Jul 20, 2016 at 11:27 AM, Juliusz Chrobo=
czek <span dir=3D"ltr" class=3D"">
&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" target=3D"_blank" clas=
s=3D"">jch@pps.univ-paris-diderot.fr</a>&gt;</span> wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Not proposing this seriously, just attempting to explore the design space.<=
br class=3D"">
Some of the ideas are due to Toke.<br class=3D"">
<br class=3D"">
Zones and authoritative nameservers are announced over HNCP together with<b=
r class=3D"">
their set of addresses, which SHOULD include a LUA and MUST include at<br c=
lass=3D"">
least one IPv6 address.&nbsp; There are two bits associated with each<br cl=
ass=3D"">
authoritative nameserver:<br class=3D"">
<br class=3D"">
&nbsp; - default: set to 1 if the zone is suitable for name registration wi=
thout<br class=3D"">
&nbsp; &nbsp; explicit user configuration;<br class=3D"">
&nbsp; - public: set to 1 if the zone is visible from the public internet.<=
br class=3D"">
<br class=3D"">
When a router joins the homenet, it MAY announce itself as the new<br class=
=3D"">
authoritative nameserver for a zone.&nbsp; It SHOULD do so if there is no<b=
r class=3D"">
default public or private zone.<br class=3D"">
<br class=3D"">
If there are two default private zones or two default public zones, we<br c=
lass=3D"">
call an election, Highlander-style.&nbsp; If there are two authoritative<br=
 class=3D"">
nameservers for the same zone, we call an election.<br class=3D"">
<br class=3D"">
There are no secondaries.&nbsp; If there are secondaries, their configurati=
on<br class=3D"">
is outside the scope of this mail.<br class=3D"">
<br class=3D"">
Stateful DHCP servers SHOULD register their clients with the authoritative<=
br class=3D"">
nameserver for the default private zone using your favourite unicast<br cla=
ss=3D"">
mechanism.&nbsp; Clients MAY register themselves with any zone currently<br=
 class=3D"">
announced (they learn the server addresses through HNCP snooping or a from<=
br class=3D"">
new ND option, I don't care).<br class=3D"">
<br class=3D"">
mDNS proxying into the default private zone is allowed.&nbsp; Or recommende=
d,<br class=3D"">
I'm not sure, only implementation experience will tell.<br class=3D"">
<br class=3D"">
Why exactly am I speaking nonsense?<br class=3D"">
<br class=3D"">
-- Juliusz<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br clas=
s=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank" class=3D"">https://www.ietf.org/mailman/listinfo/homene=
t</a><br class=3D"">
</blockquote>
</div>
<br class=3D"">
</div>
_______________________________________________<br class=3D"">
homenet mailing list<br class=3D"">
<a href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br clas=
s=3D"">
https://www.ietf.org/mailman/listinfo/homenet<br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</body>
</html>

--_000_176130D743F74B0DBB79FFE3ABE52890jiscacuk_--


From nobody Tue Jul 26 05:38:16 2016
Return-Path: <marka@isc.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAD7812D7B3 for <homenet@ietfa.amsl.com>; Tue, 26 Jul 2016 05:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.188
X-Spam-Level: 
X-Spam-Status: No, score=-8.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 SYyJvFSS1Utv for <homenet@ietfa.amsl.com>; Tue, 26 Jul 2016 05:38:14 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 985A912D78F for <homenet@ietf.org>; Tue, 26 Jul 2016 05:29:08 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 24DCE34930F; Tue, 26 Jul 2016 12:29:06 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 1487F16007E; Tue, 26 Jul 2016 12:29:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EB2DB160088; Tue, 26 Jul 2016 12:29:05 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yMS9Kq3v8Ew0; Tue, 26 Jul 2016 12:29:05 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 6EE7F16007E; Tue, 26 Jul 2016 12:29:05 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 54EA34F7CC97; Tue, 26 Jul 2016 20:11:37 +1000 (EST)
To: Ralph Droms <rdroms.ietf@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com> <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com>
In-reply-to: Your message of "Mon, 18 Jul 2016 17:04:51 +0200." <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com>
Date: Tue, 26 Jul 2016 20:11:37 +1000
Message-Id: <20160726101137.54EA34F7CC97@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/zkOG3Xqs7JUhLFx5zdTnEhekbyI>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 26 Jul 2016 12:38:15 -0000

In message <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com>, Ralph Droms writes:
> > On Jul 18, 2016, at 3:44 PM 7/18/16, Ted Lemon <mellon@fugue.com> wrote:
> >
> > The document as written causes some harm, but less harm than updating
> > it.   The text in the document as written as to how domain names are
> > resolved is not very good, and really really needs to be clarified with a
> > detailed document that explains how name resolution works on the homenet.
>
> I agree with Ted 100% about the text in the document regarding name
> resolution.  In my opinion, the proper organization for the
> specifications here would be to ensure that the details of name
> resolution in homenet are correctly specified in Ted's document or
> another separate document, with text in the HNCP document the specifies
> how the requisite configuration information is carried in HNCP.
>
> > But I think we all accept that there's going to have to be a
> > special-use top-level name allocated.   That name is either going to be
> > '.home' or '.homenet' as far as I can tell.
> >
> > Andrew made a very good case for why it shouldn't be .home.   I agree
> > with him, but not strongly enough that I would kick up a fuss of the
> > consensus was to allocate .home anyway.    I also don't mind the
> > two-stage process if IETF leadership is willing to do what I asked at the
> > mic and actively keep the debate on track.
> >
> > But it's really a three-stage process: do the erratum as an update,
> > then do the 6761 allocation of either .home or .homenet, then do the
> > document that explains how it all works.   We need step two to happen
> > _soon_ or we are in trouble.   Step 1 may be necessary and highly
> > motivating because of the layer 9 problems that this mistake caused, but
> > if we only do step 1 and then trail off on step 2, the effect in the
> > market is either going to be that everybody uses .home anyway, or else
> > that everybody uses something different.   Neither of these outcomes are
> > good outcomes.
>
> I agree with Ted 100% here, as well.  We need to solve immediately the
> specific problem that .home was either delegated as a DNS TLD without
> appropriate process, or was designated as a Special Use Name without an
> associated entry in the registry.  (In my opinion, RFC 7788 is not clear
> about which of those two buckets ".home" falls into.)  Then we need to
> specify the behavior of the new label, which I assume will be a Special
> use name, and add it to the Special Use Names registry as quickly as
> possible.
>
> - Ralph

The behaviour needs to be similar to that of the RFC 1918 in-addr.arpa
suffixes.  There needs to be a insecure DNSSEC delegation to servers
that return NXDOMAIN for all names below the chosen label.  This
way validating clients do not get BOGUS as validation result when
handed a foo.<TBD> lookup result.  Additionally validating clients
do not need special knowledge for .<TBD>.

The root servers will return a authoritative NOERROR NODATA for
DS/<TBD>.

Mark

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


From nobody Tue Jul 26 20:17:28 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4B812DA25 for <homenet@ietfa.amsl.com>; Tue, 26 Jul 2016 20:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ENydE3_NYvdN for <homenet@ietfa.amsl.com>; Tue, 26 Jul 2016 20:17:25 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E15D012D9AF for <homenet@ietf.org>; Tue, 26 Jul 2016 20:17:24 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id s63so23779634qkb.2 for <homenet@ietf.org>; Tue, 26 Jul 2016 20:17:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hdrUYeslwqc+Qbob3azwMHsfslMdlnng44UeHxzQ5ck=; b=eDVbcZHpVFJRNDDOcdLWvWNTbH6usi4BF1JezpuZ/yQ55WxfyI6M/Qm+0+tfuUAsM4 jJnvbC3ZKr2jjdaDkUThKMkPfSZMGkXGnRQHKgINsQauhkNVQ0s7lzJ+fDeMS0Pt2d9x h7nq0OMrTimVTdoCiOGqCpk7CsD7RVfJGZQlv/hNM4VHCRu8W0bmwY4kfAOkZGqvih4h 0awnpPAgESWBYplE6wIXwTv4nKqpebg8Wq/ewt9+DTj1+puMPb21BnmXXsrI06pcvcGb Nxt2dIFIofPytJLn2Y1Yb13e0VKCaVcnASK/a2BIkE9DkrDv5ONCzzZLRWeIfXxsTp3c We6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hdrUYeslwqc+Qbob3azwMHsfslMdlnng44UeHxzQ5ck=; b=N1XuZUZARZyLe6FBDt1ac2Wg/cBhA/H6HoelxUTE8saRiUY2ENQDn5Qbza4pz++Ezo ATg5yNoN3o/5Thdwx1pvbPB+8zafNeGOab4E4a68aH/tFzao7WZCMfc35UsH3QMRQZ1c Oe/10z/cn3F+yXKZyrkH2stC541bwBcMvCtowdlPwJ8Ph1TILlNutWBRVTtv5JJBOalY 3yqmuKVqM6Oyiv4Qnb1xJJDyRqHYc57p+w4Y+ND56evpXgaM978dmuKFEi3X5vM8KoTf 9efSXURpXWhHtZXuBEKxjo/ikACM98+yWokzh1lC+ZPkfLnIm7oltrd7TWzP/urX/ieg r+gw==
X-Gm-Message-State: AEkoouvepYEit+jv9fSnRdv5nuLQW8wmAbLQt9qiawAqzHvjcOY47EBK76ojpDAyn70xHg==
X-Received: by 10.55.168.2 with SMTP id r2mr34912220qke.24.1469589444006; Tue, 26 Jul 2016 20:17:24 -0700 (PDT)
Received: from richs-mbp-4543.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id l1sm2706868qtd.49.2016.07.26.20.17.22 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 26 Jul 2016 20:17:22 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 26 Jul 2016 23:17:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/kj4uOhSshhZwqvktDtuCvZgFUBA>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 Jul 2016 03:17:27 -0000

> On Jul 23, 2016, at 5:34 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> The problem came when =E2=80=9CStep 3 - Converting WAN interface to =
Homenet=E2=80=9D
>> didn=E2=80=99t work as described. I clicked Delete for the WAN =
interface.
>=20
> Don't use the web interface.  Ssh into the router, and use vi on
> /etc/config/network, it's easier and more reliable.

OK. I read all the documentation I can find (I note that =
http://www.homewrt.org is off the air at this time), and have come up =
with what I thought would be a good process for configuring Homenet. =
Unfortunately, it doesn't quite work.

Rather than describe the symptoms, I think it might be more efficient =
for someone to read through the steps outlined at =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901 =
and tell me if I've got it right?=20

I would appreciate corrections, suggestions, edits, etc. Many thanks.

Rich

>=20
> Here's how we make a Homenet router:
>=20
>  opkg update
>  opkg install hnet-full ip tcpdump strace
>  vi /etc/config/system
>  vi /etc/config/network
>  vi /etc/config/wireless
>  vi /etc/config/firewall
>  /etc/init.d/network restart
>  (check the output for errors)
>  sync
>  reboot
>=20
> I'll publish Dorine's configuration files when I'm back in Paris, =
they're
> a little beyond what you're interested in (they set up two mesh =
interfaces
> and one AP on each node), but they're a good example.
>=20
> -- Juliusz


From nobody Wed Jul 27 00:44:48 2016
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BB512D5C2 for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 00:44:47 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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-lxxh95XcG for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 00:44:45 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 804BB12D1DA for <homenet@ietf.org>; Wed, 27 Jul 2016 00:44:44 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id g62so21206098lfe.3 for <homenet@ietf.org>; Wed, 27 Jul 2016 00:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h6J1T058IlEfdM6+dU/g9orquhf/WsS5WU7gRc6XznM=; b=g65n8dUoNNZwJeW9RBcPXlt7uK1Hm9chy1Nil0WOHnwkUSZ8l4fgVh4vkszYtHnTCp QvxzCf1Ga3f/qO2AGoNATJJT0K6/kVEX8PnAnZDBQW7P7/jGy+JflQxhHGlNIVyQ6hAH EyCX7fSXrvkjsqUMgCvQWX5qG+PQdLBWm+DCVd24R/RqS38CPdCCpe6P+sDwa7i0kNrs mfJAHoEOENTZ2bLhXCydUZEszJnPsfOKGY28JMXT/jaJa2GnsDvIO04JtdPPGQ8SD7+1 YIIjjJu3h/nJdVnTFIDMbU/R5EeBqELUY2Gpedw8aCyyP0KgCcobGo05s8+uiJcsG7Ps htCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h6J1T058IlEfdM6+dU/g9orquhf/WsS5WU7gRc6XznM=; b=jB5pqWxIyKgTsHf8zdNKmFQXsZ2v4Fq4oiArVvh+Fju9f0mZfSqtQvB76Ujhs6faDt Srv3VvlFBRVogkJntILMXCzUafIcifSA8wE8nUwA9i/gJ59xG+PgvwqRj4G/u3t5sUZT 5QDl1rbLJZU6Xq3r7o7S819PDdmmbxJvoMbxMnnMetDiaWInp/Hqo7gum/akkOoroqH7 HfNlp8su/wLxy3sZKZ0+Dek3lxTBWWNceCDHW3fTBe+1pqkh8z2iK08XT8OA5x+S6Ed5 z0MlkY74RDRR+CLhjmm45WCp9du9auLmZH3T/LztoxoVwlJJFo5viy07y/DItVZTESDu K6UA==
X-Gm-Message-State: AEkoous82EUBm5OXZt1OPkDPLFUre5R1YSmCim5tqpNeieWXiXfKU7MJ+0sqzirM1IQrCWJUMcHFa4lf8YlGXA==
X-Received: by 10.25.26.194 with SMTP id a185mr11484739lfa.167.1469605482530;  Wed, 27 Jul 2016 00:44:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.93 with HTTP; Wed, 27 Jul 2016 00:44:02 -0700 (PDT)
In-Reply-To: <20160726101137.54EA34F7CC97@rock.dv.isc.org>
References: <CAPt1N1nbTimM1tyfGQVjeSJQbbrT1D319boM6Z67OhvyyZ4ucA@mail.gmail.com> <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com> <20160726101137.54EA34F7CC97@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 27 Jul 2016 09:44:02 +0200
Message-ID: <CAPt1N1=kzw3j=x24ecvQN_-sEk9Hm51RzKTwJBh6jEiYHEMrzg@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=001a11403bd8bf201605389930ab
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/JCFDMf2G1ILF4-GzvPWsMsL4KDI>
Cc: HOMENET <homenet@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] What I really meant by option 5
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 Jul 2016 07:44:47 -0000

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

Yes, this would be a "locally-served domain."

On Tue, Jul 26, 2016 at 12:11 PM, Mark Andrews <marka@isc.org> wrote:

>
> In message <1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com>, Ralph Droms
> writes:
> > > On Jul 18, 2016, at 3:44 PM 7/18/16, Ted Lemon <mellon@fugue.com>
> wrote:
> > >
> > > The document as written causes some harm, but less harm than updating
> > > it.   The text in the document as written as to how domain names are
> > > resolved is not very good, and really really needs to be clarified
> with a
> > > detailed document that explains how name resolution works on the
> homenet.
> >
> > I agree with Ted 100% about the text in the document regarding name
> > resolution.  In my opinion, the proper organization for the
> > specifications here would be to ensure that the details of name
> > resolution in homenet are correctly specified in Ted's document or
> > another separate document, with text in the HNCP document the specifies
> > how the requisite configuration information is carried in HNCP.
> >
> > > But I think we all accept that there's going to have to be a
> > > special-use top-level name allocated.   That name is either going to be
> > > '.home' or '.homenet' as far as I can tell.
> > >
> > > Andrew made a very good case for why it shouldn't be .home.   I agree
> > > with him, but not strongly enough that I would kick up a fuss of the
> > > consensus was to allocate .home anyway.    I also don't mind the
> > > two-stage process if IETF leadership is willing to do what I asked at
> the
> > > mic and actively keep the debate on track.
> > >
> > > But it's really a three-stage process: do the erratum as an update,
> > > then do the 6761 allocation of either .home or .homenet, then do the
> > > document that explains how it all works.   We need step two to happen
> > > _soon_ or we are in trouble.   Step 1 may be necessary and highly
> > > motivating because of the layer 9 problems that this mistake caused,
> but
> > > if we only do step 1 and then trail off on step 2, the effect in the
> > > market is either going to be that everybody uses .home anyway, or else
> > > that everybody uses something different.   Neither of these outcomes
> are
> > > good outcomes.
> >
> > I agree with Ted 100% here, as well.  We need to solve immediately the
> > specific problem that .home was either delegated as a DNS TLD without
> > appropriate process, or was designated as a Special Use Name without an
> > associated entry in the registry.  (In my opinion, RFC 7788 is not clear
> > about which of those two buckets ".home" falls into.)  Then we need to
> > specify the behavior of the new label, which I assume will be a Special
> > use name, and add it to the Special Use Names registry as quickly as
> > possible.
> >
> > - Ralph
>
> The behaviour needs to be similar to that of the RFC 1918 in-addr.arpa
> suffixes.  There needs to be a insecure DNSSEC delegation to servers
> that return NXDOMAIN for all names below the chosen label.  This
> way validating clients do not get BOGUS as validation result when
> handed a foo.<TBD> lookup result.  Additionally validating clients
> do not need special knowledge for .<TBD>.
>
> The root servers will return a authoritative NOERROR NODATA for
> DS/<TBD>.
>
> Mark
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

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

<div dir=3D"ltr">Yes, this would be a &quot;locally-served domain.&quot;</d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Jul 26=
, 2016 at 12:11 PM, Mark Andrews <span dir=3D"ltr">&lt;<a href=3D"mailto:ma=
rka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
In message &lt;<a href=3D"mailto:1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail=
.com">1DD06EA4-D903-4E14-B1E2-5854C4EBDF37@gmail.com</a>&gt;, Ralph Droms w=
rites:<br>
&gt; &gt; On Jul 18, 2016, at 3:44 PM 7/18/16, Ted Lemon &lt;<a href=3D"mai=
lto:mellon@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; The document as written causes some harm, but less harm than upda=
ting<br>
&gt; &gt; it.=C2=A0 =C2=A0The text in the document as written as to how dom=
ain names are<br>
&gt; &gt; resolved is not very good, and really really needs to be clarifie=
d with a<br>
&gt; &gt; detailed document that explains how name resolution works on the =
homenet.<br>
&gt;<br>
&gt; I agree with Ted 100% about the text in the document regarding name<br=
>
&gt; resolution.=C2=A0 In my opinion, the proper organization for the<br>
&gt; specifications here would be to ensure that the details of name<br>
&gt; resolution in homenet are correctly specified in Ted&#39;s document or=
<br>
&gt; another separate document, with text in the HNCP document the specifie=
s<br>
&gt; how the requisite configuration information is carried in HNCP.<br>
&gt;<br>
&gt; &gt; But I think we all accept that there&#39;s going to have to be a<=
br>
&gt; &gt; special-use top-level name allocated.=C2=A0 =C2=A0That name is ei=
ther going to be<br>
&gt; &gt; &#39;.home&#39; or &#39;.homenet&#39; as far as I can tell.<br>
&gt; &gt;<br>
&gt; &gt; Andrew made a very good case for why it shouldn&#39;t be .home.=
=C2=A0 =C2=A0I agree<br>
&gt; &gt; with him, but not strongly enough that I would kick up a fuss of =
the<br>
&gt; &gt; consensus was to allocate .home anyway.=C2=A0 =C2=A0 I also don&#=
39;t mind the<br>
&gt; &gt; two-stage process if IETF leadership is willing to do what I aske=
d at the<br>
&gt; &gt; mic and actively keep the debate on track.<br>
&gt; &gt;<br>
&gt; &gt; But it&#39;s really a three-stage process: do the erratum as an u=
pdate,<br>
&gt; &gt; then do the 6761 allocation of either .home or .homenet, then do =
the<br>
&gt; &gt; document that explains how it all works.=C2=A0 =C2=A0We need step=
 two to happen<br>
&gt; &gt; _soon_ or we are in trouble.=C2=A0 =C2=A0Step 1 may be necessary =
and highly<br>
&gt; &gt; motivating because of the layer 9 problems that this mistake caus=
ed, but<br>
&gt; &gt; if we only do step 1 and then trail off on step 2, the effect in =
the<br>
&gt; &gt; market is either going to be that everybody uses .home anyway, or=
 else<br>
&gt; &gt; that everybody uses something different.=C2=A0 =C2=A0Neither of t=
hese outcomes are<br>
&gt; &gt; good outcomes.<br>
&gt;<br>
&gt; I agree with Ted 100% here, as well.=C2=A0 We need to solve immediatel=
y the<br>
&gt; specific problem that .home was either delegated as a DNS TLD without<=
br>
&gt; appropriate process, or was designated as a Special Use Name without a=
n<br>
&gt; associated entry in the registry.=C2=A0 (In my opinion, RFC 7788 is no=
t clear<br>
&gt; about which of those two buckets &quot;.home&quot; falls into.)=C2=A0 =
Then we need to<br>
&gt; specify the behavior of the new label, which I assume will be a Specia=
l<br>
&gt; use name, and add it to the Special Use Names registry as quickly as<b=
r>
&gt; possible.<br>
&gt;<br>
&gt; - Ralph<br>
<br>
</div></div>The behaviour needs to be similar to that of the RFC 1918 in-ad=
dr.arpa<br>
suffixes.=C2=A0 There needs to be a insecure DNSSEC delegation to servers<b=
r>
that return NXDOMAIN for all names below the chosen label.=C2=A0 This<br>
way validating clients do not get BOGUS as validation result when<br>
handed a foo.&lt;TBD&gt; lookup result.=C2=A0 Additionally validating clien=
ts<br>
do not need special knowledge for .&lt;TBD&gt;.<br>
<br>
The root servers will return a authoritative NOERROR NODATA for<br>
DS/&lt;TBD&gt;.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Mark<br>
<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</font></span></blockquote></div><br></div>

--001a11403bd8bf201605389930ab--


From nobody Wed Jul 27 04:03:00 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5886D12DFC2 for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 04:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 qW5CazWpNk4G for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 04:02:56 -0700 (PDT)
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D728812DFC6 for <homenet@ietf.org>; Wed, 27 Jul 2016 04:02:51 -0700 (PDT)
Received: from trurl.pps.univ-paris-diderot.fr (unknown [IPv6:2a01:e34:ec22:84a3:8c69:c32b:4a76:dfea]) by smtp2-g21.free.fr (Postfix) with ESMTPS id 291BD2003B1; Wed, 27 Jul 2016 10:57:04 +0200 (CEST)
Date: Wed, 27 Jul 2016 13:02:45 +0200
Message-ID: <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/j3y_BtdSiGTjjehrB76tiDnZOgs>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 Jul 2016 11:02:59 -0000

> Rather than describe the symptoms, I think it might be more efficient
> for someone to read through the steps outlined at
> https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901
> and tell me if I've got it right?

Looks good to me.  You've correctly removed the software bridge and run
everything on the right interfaces.

Note that the firewall configuration is probably not necessary, hnetd does
weird things to the firewall.  But it doesn't harm, and it allows you to
easily switch back to a static configuration if Homenet doesn't meet your
needs.

If I were you, I'd explicitly tell hnetd that the E0 interface is external
("option mode external"), since I don't trust the edge detection mechanism.

I suggest adding two things:

  - before you start hacking, write down the IPv6 link-local address of
    the LAN interface, to make sure you can log in;
  - you should review /etc/config/upnpd, and list the interfaces you want
    to allow NAT-PMP on.

-- Juliusz


From nobody Wed Jul 27 06:14:59 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B5812D774 for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 06:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1AhceNHvg_QK for <homenet@ietfa.amsl.com>; Wed, 27 Jul 2016 06:14:56 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D09812D78D for <homenet@ietf.org>; Wed, 27 Jul 2016 06:14:56 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id u25so29022547qtb.1 for <homenet@ietf.org>; Wed, 27 Jul 2016 06:14:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Di5zFaA3VHNCrnA78bjqyHn7LMjOmu67NOOKUv8Weq8=; b=ud6H3QVK77hheS8hqLisQ3yyEU3o5Uj6Y8rA4e0KneuneVp2RE5PGunPgRqVWxFcpD Md0UhWBEzFCPtxptz0kAM60YVMAaeBkXUkxKNqknobD6hjynRutnqVh0t98C2AxzXQQv Lcmd2pg7gr8+d/TnacAYwzO6nn6k8VishfAuRbS0Lfy6ODAsTSarAPsipSi7LV1ElKAL tfEKdCPrSntkudfWVivQZ3P4hRQRm1HJodKoK6f5hGDwwTkaRUD/yZO8jHfVlxx/U5P5 Y4LEWf/wIOsvh98e/9KAdBRw/5fHH2fd7FlJZU1e7jMVqKeJZ0JX2hjiPcsJxKcYTBIW OtVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Di5zFaA3VHNCrnA78bjqyHn7LMjOmu67NOOKUv8Weq8=; b=PqG1UouKIem3/GoXbe5PZHyYaySf8AZaxf4kPHY18ovF5/rpyAsVBJUPjLilMZ4/kR OIBNIcWFA8aQwLkxkxRBybXa4YhT2TGDSWzD85yD+epxhngm6/b89fL7vqmHReG2dfSH yyLPcoI+Jj2eyDHDv3D4lqYvUQhaX2cPNzQQCuHVCDiPAADThmd9USeY/mxhURMyJIHo reAP+ctpBhdiGuAoI3rTcHilVgD0GTx+8yOCHoTXVxp8Wm3oDo+CR3XFDkQ4klBxmEEg zPO5sNRkv41v1BeIJIdNkMddF3A+dn7jJxqjJY/po/WblSqtOGEm5+6jOEKkfBQaSJeW TvfQ==
X-Gm-Message-State: AEkoouurGlr6/susX5Cv05kJuYnHJIjVzrhgu+2plwZwmjmT0yQRRIzNPSCJP5s0WvpaDg==
X-Received: by 10.237.59.161 with SMTP id r30mr45529777qte.22.1469625295211; Wed, 27 Jul 2016 06:14:55 -0700 (PDT)
Received: from richs-mbp-4543.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id d190sm4098488qke.18.2016.07.27.06.14.54 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 27 Jul 2016 06:14:54 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 27 Jul 2016 09:14:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <446CF596-B9C4-4FC4-B00F-A40FB04FB1A1@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/QIcBIgbfrXwcT7JNThVHUKZD79Q>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 Jul 2016 13:14:58 -0000

Thanks for these comments. I'll review them, try them out on my routers, =
and come back with further questions.

Rich

> On Jul 27, 2016, at 7:02 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> Rather than describe the symptoms, I think it might be more efficient
>> for someone to read through the steps outlined at
>> =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901
>> and tell me if I've got it right?
>=20
> Looks good to me.  You've correctly removed the software bridge and =
run
> everything on the right interfaces.
>=20
> Note that the firewall configuration is probably not necessary, hnetd =
does
> weird things to the firewall.  But it doesn't harm, and it allows you =
to
> easily switch back to a static configuration if Homenet doesn't meet =
your
> needs.
>=20
> If I were you, I'd explicitly tell hnetd that the E0 interface is =
external
> ("option mode external"), since I don't trust the edge detection =
mechanism.
>=20
> I suggest adding two things:
>=20
>  - before you start hacking, write down the IPv6 link-local address of
>    the LAN interface, to make sure you can log in;
>  - you should review /etc/config/upnpd, and list the interfaces you =
want
>    to allow NAT-PMP on.
>=20
> -- Juliusz


From nobody Wed Jul 27 11:39:24 2016
Return-Path: <equinox@diac24.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFD9712D50A; Wed, 27 Jul 2016 11:39:18 -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] autolearn=ham autolearn_force=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 LqPAi1oAwDqn; Wed, 27 Jul 2016 11:39:16 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEAF312D12D; Wed, 27 Jul 2016 11:39:14 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from <equinox@diac24.net>) id 1bSTja-000Dq3-UT; Wed, 27 Jul 2016 20:39:11 +0200
Date: Wed, 27 Jul 2016 20:39:10 +0200
From: David Lamparter <equinox@diac24.net>
To: Lorenzo Colitti <lorenzo@google.com>
Message-ID: <20160727183910.GF996866@eidolon>
References: <20160706005825.22318.33162.idtracker@ietfa.amsl.com> <1D424B70-9241-453D-85FF-A296A4DCE653@cisco.com> <20160720125458.GO255916@eidolon> <CAKD1Yr1-d-Bi25ZJJB4FzoRdTstAFEFjDYR_91M+dh8ZDzEQGA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr1-d-Bi25ZJJB4FzoRdTstAFEFjDYR_91M+dh8ZDzEQGA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/DXRQgsKIDAy0I395ooYDz8jSUz0>
Cc: Dave Taht <dave.taht@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 Jul 2016 18:39:19 -0000

On Thu, Jul 21, 2016 at 09:49:46AM +0200, Lorenzo Colitti wrote:
> On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wrote:
> > Hence, I hacked it up for the Linux (4.5.0) kernel; patches are attached
> > to this mail.  I've been able to gleam a little more detail on the idea:
> >
> 
> David, do you intend to keep working on the patches? Think you could send
> them to netdev as an RFC patchset, with proper signoff? Once it's on netdev
> other people can iterate on them, even if you lose interest :-)

I've uploaded the patches (with signoffs) to:
https://aurora.nox.tf/tmp/rule55/

NB: patch 2 of 3 is slightly different from the version I mailed, I
accidentally lost a NULL check in ipv6_rt_get_saddr().

I do _not_ intend to continue working on these since I now believe the
functionality should be put on neighbor cache entries.  This requires
some (minor IMHO) rework to make these neighbor entries stay alive until
their prefix information times out.  By putting it there, it can support
addresses that are configured from dhcpv6 or static/admin.  The code
linked above only works for SLAAC.

=> the patches are intended purely for testing, for example if someone
hacks on the router side and wants to use Linux VMs to test the full
picture.

Cheers,


-David


From nobody Wed Jul 27 21:38:33 2016
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44F7412D54F; Wed, 27 Jul 2016 21:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AN7hqbpFdHs0; Wed, 27 Jul 2016 21:38:29 -0700 (PDT)
Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7134112B047; Wed, 27 Jul 2016 21:38:29 -0700 (PDT)
Received: by mail-io0-x244.google.com with SMTP id g86so6845717ioj.1; Wed, 27 Jul 2016 21:38:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=AEBdorNld1/Q0C4ElnpjLQWTJu2MJCCgYHiOenhZ8kI=; b=MIhHwf1vVTKGY78VtaXhDchTh+xHeI35Lxo4ij4MF04ujWx4nyYUPWQeQ0bttWuf9N cOad8NlcGwxvXCjK9B5+P/u6UErBAUP4/hBvU6+qu/AWVY+mFttMEDhBGQwVa0g5tNtf UjT7XlS6oQxHwEowy7YEr5lH8Otf27H45rnfu2cupUrt8kBBEFeQSdbnHlGPnCmPfw+L XOVnvdfBwSL6f1vOCMYIenf3I9WgsJ8A52gtS832M0SGY913YDtti4S2p3Be7OanLwxq gJQYPPhvRXZrMHw8OkOqukLvIUIAS1Kdh4T7dCRJ5NntvrGY6/dL4HGNZ+tPu/uCpLCD cDDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=AEBdorNld1/Q0C4ElnpjLQWTJu2MJCCgYHiOenhZ8kI=; b=G//DjGLnazq2VHvUTSVDCVd4dkZisiCkWmrLRVRsGMz0w+H+PU72VArRbi+NjmRufJ fddgVfZft5rnQcG7Z6AcBsE2d0Fuyj1CqjWE+dvzzREIk+v06I+VlaB4EhRXc1C0RTKy LjmIlosKesGjw1JOcaclJPkJuYD8VYd/F5oqEsZdhMFucko0twsfoBg5TyYaD59OVeg3 WEnKZhlpJkqVaODZwrqaWboLIXVZEbcrLUH58uQ9FZZl3ZKkIvjgU3IagC+smU32jc9V K8rRJo9uYqfSZapNTHJtWs11QLMWAR4sJa85qspKS+aFiuApk6JM56vc7/vsEtiiTMLB V3CQ==
X-Gm-Message-State: AEkoouuOcF1ncQ5ZdAatKHoJ6oJrrnfL9Rft1dedcgUqd343Aim/3Szq9hW9/prvZSKjOv4EwOprhV4LCM9z+Q==
X-Received: by 10.107.8.140 with SMTP id h12mr37646722ioi.95.1469680708730; Wed, 27 Jul 2016 21:38:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.14.17 with HTTP; Wed, 27 Jul 2016 21:38:28 -0700 (PDT)
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, 28 Jul 2016 06:38:28 +0200
Message-ID: <CAA93jw4rDQBvke3sFJ3GT2NqDYLTFdrJBtNDr+1VSXgFL7U7Jw@mail.gmail.com>
To: David Lamparter <equinox@diac24.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MvRoPjU4ewNvr0kNK23YeWOu8Mo>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Jen Linkova <furry@google.com>, homenet <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Linux 6724 rule 5.5 (Re: draft-bowbakova-rtgwg-enterprise-pa-multihoming-00)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2016 04:38:31 -0000

On Wed, Jul 27, 2016 at 8:39 PM, David Lamparter <equinox@diac24.net> wrote=
:
> On Thu, Jul 21, 2016 at 09:49:46AM +0200, Lorenzo Colitti wrote:
>> On Wed, Jul 20, 2016 at 2:54 PM, David Lamparter <equinox@diac24.net> wr=
ote:
>> > Hence, I hacked it up for the Linux (4.5.0) kernel; patches are attach=
ed
>> > to this mail.  I've been able to gleam a little more detail on the ide=
a:
>> >
>>
>> David, do you intend to keep working on the patches? Think you could sen=
d
>> them to netdev as an RFC patchset, with proper signoff? Once it's on net=
dev
>> other people can iterate on them, even if you lose interest :-)
>
> I've uploaded the patches (with signoffs) to:
> https://aurora.nox.tf/tmp/rule55/

Thank you for posting the patches. I will try them out the next time I get =
time.

I think I object to landing IPV6_SADDR_RULE_OIF_RTR in the middle of
the existing enum rather than at the end, but will twiddle further.

> NB: patch 2 of 3 is slightly different from the version I mailed, I
> accidentally lost a NULL check in ipv6_rt_get_saddr().
>
> I do _not_ intend to continue working on these since I now believe the
> functionality should be put on neighbor cache entries.  This requires
> some (minor IMHO) rework to make these neighbor entries stay alive until
> their prefix information times out.  By putting it there, it can support
> addresses that are configured from dhcpv6 or static/admin.

I think I agree, but looking over the existing patches is a goodness.
I was only just made aware that getting source specific routing to
work well in other base ipv6 protocols had entered ietf consideration
in this past ietf, and have some catching up to do.

Has there been any work on improving how the std APIs might work on
choosing a better source address for a given destination? I see some
work has happened in mptcp....

> The code
> linked above only works for SLAAC.

One thing that has bothered me of late has been the lack of symmetry
regarding address assignment's sources, vs how routes are handled.

ip -6 route add fd01::1 via fe80::1 dev whatever proto static #
rip/babel/dhcp/etc

vs

ip -6 addr add fd01::2/64 dev whatever # with no means to specify that
it came from slaac/dhcpv6/static/hncp/background radiation.

The existing bits for things like tmpaddr, mgmt_tmpaddr and scope
seems to be breaking down in the representability...

>
> =3D> the patches are intended purely for testing, for example if someone
> hacks on the router side and wants to use Linux VMs to test the full
> picture.
>
> Cheers,
>
>
> -David



--=20
Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org


From nobody Thu Jul 28 08:08:34 2016
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B625412D7F0 for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 08:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gshnqkcY0ATW for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 08:08:30 -0700 (PDT)
Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAA3912D809 for <homenet@ietf.org>; Thu, 28 Jul 2016 08:08:29 -0700 (PDT)
Received: by mail-it0-x243.google.com with SMTP id f6so5026987ith.2 for <homenet@ietf.org>; Thu, 28 Jul 2016 08:08:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=YRVnhHGbrKS/T2eFreRGH9KtoH2DXQQMvrZvIOU3RmE=; b=ZbxSOQ9GxTjWJ3SkTXqgw0IvaP1UVCfoO4w2MY0g9REE0MTNqwHAQUJVM+l9iBbHlF /2tRhY174kdBsn7Wy3NiD07dJJYZGABM6wlzWK9rj8YsbA7dsuGX9c3cpMsNIV+Dz4LC LIXG4HtZF6h18L8V0eZBsHI7cT4nCNCy9AHc8b+NTnLvTgnNaLab1CoxHRzdtQaK/Hp/ Z1VlGyTNSdffFgT2qV3pSiS0OWrPgkOihPG0SkiHBv64cRh37a8tVPd/qclQ/U8eQYId 7snsMxLg60Jja+U7fgb0jdJWt3iX7/3WQoH+vy7vKkJ1kXkYPMcl92dh7QQZbHOLi1Bd MfFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=YRVnhHGbrKS/T2eFreRGH9KtoH2DXQQMvrZvIOU3RmE=; b=E+8TcTfFMsKCnmC0Rs3dgvvlxKpDatkHTJLGo6Nibr7H51KBR2xyH594t4lfGYSRBj crW+SCqx8InzHtlTX3tr4qlXnVMof8KIivj0KV0rABhj8jsDhgJUzgEIzWU5bTHtstWF WvyHiq8fP43nLmqSIS68Uuqx1p0dk0zL29z6EsCgnNUwt5MMKv05Stg7YCHRd1Gl6fRm QDjG7CKFNe25dw4gc2kkr6IvWEZaSkNqR9DkVZMJylvMk9KRAL6f9eeUhK7/wmYxG4Lw 8vvAwmiuN6GeD+2NIh3XgzM1BuRAHQkTe5/AHiWpabe9+ley+y1szas8nPjVgGMqbt3f fEzg==
X-Gm-Message-State: AEkoouuX723mAV6tXsphVv65WVIcX1KUCfq/Tsr6oCrGrvG31kBZxoOwpCoWIibC0Sgods6vXf/JqG5OOXyzRg==
X-Received: by 10.36.5.200 with SMTP id 191mr31551460itl.50.1469718509055; Thu, 28 Jul 2016 08:08:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.14.17 with HTTP; Thu, 28 Jul 2016 08:08:28 -0700 (PDT)
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, 28 Jul 2016 17:08:28 +0200
Message-ID: <CAA93jw6SirV+5E1KPXzDhTUpYmprZO4E3dKW-3mmNEwpCfRbpQ@mail.gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/LBdBzun-9cbOx3cDxsk2hQLWayc>
Subject: [homenet] integrating homenet with multiple OSes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2016 15:08:31 -0000

If anyone would like to talk to how to integrate homenet's stuff with
existing OSes,
there is still a call for proposals out here ending aug 1.

https://lists.freedesktop.org/archives/systemd-devel/2016-July/037235.html

For systemd. (*please* don't turn this fora into a debate about
systemd's qualities and/or lack thereof. It's out there, it's widely
used, it would be good to integrate better with it, leave it at that?
There's been enough debate on that subsystem elsewhere).

The only OS I know well is Linux, and homenet's ideas on that OS can
sometimes conflict with current default configurations of avahi-mdns
name services, dnsmasq and other dns proxies/resolvers, "connman" and
"network manager", several existing dhcp and dhcp server
implementations, routing protocols, and so on.

In terms of other init/networking subsystems than openwrt and
lede-project's - there are the oldstyle debian interfaces to
networking, std init, OSX, and a few "minor" others, like windows,
android and iOS. And IOS. And no doubt dozens I didn't manage to list.

I don't think the integration discussion needs to take place here - I
am just thinking that with the complex interplay of protocols and
daemons, that more implementation experience was needed... and systemd
is a toughie, and I saw that conference slot go by to remind me about
mentioning this.

... while I have few ideas as to how to go about it, I don't plan on
giving any more talks for a while, on anything, but would gladly
collaborate to grok the issues.

Please note that in many cases we are still stuck at ipv6 basics -
dhcpv6-pd is barely deployed in particular, there's still debate here
and elsewhere on how to do naming more right (and needing
implementations), and so on.

--=20
Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org


From nobody Thu Jul 28 12:14:24 2016
Return-Path: <toke@toke.dk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A5512E02C for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 12:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=toke.dk
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 syKsX3vx-a74 for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 12:14:20 -0700 (PDT)
Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11E8C12DD4A for <homenet@ietf.org>; Thu, 28 Jul 2016 12:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail2.tohojo.dk
DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk ABE7040D5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1469733254; bh=WkuOokZLsotBI2zWExAn1/zCabaMpSgajWE0LuIhUvc=; h=From:To:Subject:Date:From; b=icaHlPhrdkKgif3FDjdsSqrgyXNocnrCW8WGJoYWF0rXF3pe0xsShYFqnJ9F5Xvxk AtuA2arJlyQxx9SwvC1qIbee5ZiBhF5/STy7q+nM+JQWRMv2vMI6QkWJZsr7dUdN5B ZGn37ibKXhnay2feneGnifui8allUG0hx/KDD+L8=
Sender: toke@toke.dk
Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id EE1AB3C82; Thu, 28 Jul 2016 21:14:13 +0200 (CEST)
From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
To: homenet@ietf.org
Date: Thu, 28 Jul 2016 21:14:13 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <871t2dlgmy.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/QKrhbsIv6zfhta_ujoIwrBtXM_A>
Subject: [homenet] Fwd: [babel] A quick summary of babel@ietf
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2016 19:14:23 -0000

--=-=-=
Content-Type: text/plain

This might be of interest to people here. In particular, checking out
Dave's "homenet on hackerboards" talk could be worthwhile.

-Toke


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <SRS0+3VB+=TN=ietf.org=babel-bounces@tohojo.dk>
Received: from mail2.tohojo.dk ([unix socket])
	 by mail2.tohojo.dk (Cyrus git2.5+0-Kolab-2.5-48.6.el6.kolab_3.3) with LMTPA;
	 Sat, 23 Jul 2016 23:47:18 +0200
X-Sieve: CMU Sieve 2.4
Authentication-Results: mail2.tohojo.dk (amavisd-new);
	dkim=pass (1024-bit key) header.d=ietf.org
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
	by mail2.tohojo.dk (Postfix) with ESMTPS id 147473F459
	for <toke@toke.dk>; Sat, 23 Jul 2016 23:47:16 +0200 (CEST)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 80A3712D1EB;
	Sat, 23 Jul 2016 14:47:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1469310434; bh=M/4qWICGpM0IZIDwaNYU8dKJrMSKwDLd3DhHC2kVgss=;
	h=Date:From:To:Cc:Subject:List-Id:List-Unsubscribe:List-Archive:
	List-Post:List-Help:List-Subscribe;
	b=Z3GkMwEHIC4A0JE1afFEAoZclSVreDfG+/2dn/Cb3ObSxUtgkiGouixg7QFwaJrnt
	UFSGl6NsiYI/Zt/rvqQqZS7x1ytffrB4vlfsDGFdmgxTq8vF6nEUNdP2TeQF1vng71
	EaC5qfxJCKoEIJUvvrWJwZxMaKd6spJxRUqlWO7g=
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr
	[IPv6:2001:660:3301:8000::1:2])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by ietfa.amsl.com (Postfix) with ESMTPS id 6FA8912B01F
	for <babel@ietf.org>; Sat, 23 Jul 2016 14:47:10 -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/56228) with ESMTP id
	u6NLl8O9007891
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=NO); Sat, 23 Jul 2016 23:47:08 +0200
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/56228) with ESMTP id
	u6NLl8CT011649; Sat, 23 Jul 2016 23:47:08 +0200
Date: Sat, 23 Jul 2016 23:47:11 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87d1m4xc0w.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: babel-users@lists.alioth.debian.org
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
	(korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]);
	Sat, 23 Jul 2016 23:47:08 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
	(potemkin.univ-paris7.fr [194.254.61.141]);
	Sat, 23 Jul 2016 23:47:08 +0200 (CEST)
X-Miltered: at korolev with ID 5793E5DC.001 by Joe's j-chkmail (http : //
	j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5793E5DC.001 by Joe's j-chkmail (http : //
	j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5793E5DC.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: 5793E5DC.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 : 5793E5DC.001 on korolev.univ-paris7.fr : j-chkmail
	score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5793E5DC.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: <https://mailarchive.ietf.org/arch/msg/babel/kF2xTOTa5oKrFmgW6-A5Qnp51do>
Cc: babel@ietf.org
Subject: [babel] A quick summary of babel@ietf
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol."
	<babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>,
	<mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>,
	<mailto:babel-request@ietf.org?subject=subscribe>
Errors-To: babel-bounces@ietf.org
Sender: "babel" <babel-bounces@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain

Dear all,

IETF is over, we've had the first meeting of the Babel WG.  It went
pleasantly smoothly.  You'll find the full recording of the meeting[1],
the minutes, as well as all the meeting materials, including slides[2].

[1] http://recs.conf.meetecho.com/Playout/watch.jsp?recording=IETF96_BABEL&chapter=chapter_1
[2] https://datatracker.ietf.org/meeting/96/materials.html#babel

In short:

  - the chairs said some things;
  - I gave a talk about my plans for evolving the protocol, the audience
    seemed to agree;
  - Barbara Stark gave a talk about her proposed management information
    model, in which she notably recommended to debloat the model; there
    was a short misunderstanding between her and Margaret Cullen, which
    was quickly cleared up;
  - Dave gave a talk about routing with hackerboards, a talk that was not
    specific to Babel but was well-received and appeared to me to be
    eye-opening to at least some audience members.

My feeling right now -- unless we f*ck up really badly, this is going to
be a productive and fun working group.

-- Juliusz

_______________________________________________
babel mailing list
babel@ietf.org
https://www.ietf.org/mailman/listinfo/babel

--=-=-=--


From nobody Thu Jul 28 16:32:33 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B94A12D9A8 for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 16:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level: 
X-Spam-Status: No, score=-1.679 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 r9FCLh51HQu2 for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 16:32:31 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C32B212D9B0 for <homenet@ietf.org>; Thu, 28 Jul 2016 16:32:28 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id s63so77199019qkb.2 for <homenet@ietf.org>; Thu, 28 Jul 2016 16:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references; bh=hKJ+V+KnbMkcQZFNuDUvifBjDm52366i2GKrhYQe1g0=; b=PIprmXBoWqtIaa2mN6zaQPZ2pQRh004IjbzOG/wTv+3zIQURe+WtQ5n266bI4EVPtv bElE/DOJOhc9HmxJaKZ9a0Fl/sFJlGhuomm+GJrg8M2Oq8BJEMN/6e1xTJcHqdQHtuBq pn4Bev9N/LchU/ZgMOnfRtoPeiug+MbQFJfakqu1iXZgRy4esacU5Sb2dFjgM03LisLs 22a9w4R1R/4uEKfzyJaW03mewu7yCZVB3cJAVJblVNxQiQbysUAgorou/iHZlzoKVT4y CbIsuywnEvfLc0YmnZDm0gAcAEcf0DTK8di6cy/S7n0YVi2dq0P1kWOXn/l8dPVMTpIz +QeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references; bh=hKJ+V+KnbMkcQZFNuDUvifBjDm52366i2GKrhYQe1g0=; b=CL7XnHmJ4ySGn7RkwFGOLKFXZh8ri0HjvVAa1UXrSlJ5hpoQtpONKf7ML0jj1OK586 q2WliGcGWLsvdH153qE6k2zzU0gAhplBWbmMv1/QkhqHUT2/UxDxgF08XUjZI6bmZ92h /PJ1Fcx8ty1MqeAM3WnATKpYM4QKY68U7zBEUM3uoKSsSZoCDgY1/0OOk2aokKuuRV3e GWrrPUrqw2MVo7zhw+z3WdX5ojQ4zzFvJorkqeSclq3aPapwq0YE9uHyPNrbCIWZEA+H rz8btvRf2F6rA7bUOwZMLi/v+aKKZHuTCPRNbw+DuUQJsCDuVQ4zzUIIyjJlQ2BHtBaq edcQ==
X-Gm-Message-State: AEkoous42XA9XTtsZn53lnuZrMdaykg91LT7xB4Ol/9Xz4GOVPpjjnyBSlEVWYdsT8/xhA==
X-Received: by 10.233.237.136 with SMTP id c130mr6977334qkg.126.1469748747840;  Thu, 28 Jul 2016 16:32:27 -0700 (PDT)
Received: from richs-mbp-4661.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id g3sm2120571qkf.35.2016.07.28.16.32.26 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 28 Jul 2016 16:32:26 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 28 Jul 2016 19:32:25 -0400
Cc: homenet@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/uDjw-ZXEsiQbAdNqe3UI-LkksG8>
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2016 23:32:32 -0000

Thanks for reading this through.

> On Jul 27, 2016, at 7:02 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> Rather than describe the symptoms, I think it might be more efficient
>> for someone to read through the steps outlined at
>> =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901
>> and tell me if I've got it right?
>=20
> Looks good to me.  You've correctly removed the software bridge and =
run
> everything on the right interfaces.

OK. I updated the gist as a result of these comments. =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901

> Note that the firewall configuration is probably not necessary, hnetd =
does
> weird things to the firewall.  But it doesn't harm, and it allows you =
to
> easily switch back to a static configuration if Homenet doesn't meet =
your
> needs.

Should the procedure remain silent on the firewall? Or should people =
just put all interfaces into the lan zone? Or something else?

> If I were you, I'd explicitly tell hnetd that the E0 interface is =
external
> ("option mode external"), since I don't trust the edge detection =
mechanism.

I think you mean E1 - that's what the instructions use for the wide area =
interface. And 'option mode external' goes in /etc/config/network?=20

And is there a man page for hnetd that gives other options? The Googles =
didn't help me...
>=20
> I suggest adding two things:
>=20
>  - before you start hacking, write down the IPv6 link-local address of
>    the LAN interface, to make sure you can log in;

Done. The newest draft also tells people to make backups :-)

>  - you should review /etc/config/upnpd, and list the interfaces you =
want
>    to allow NAT-PMP on.

I'm not quite sure how that affects things. Where would NAT-PMP be =
important in my home net?=20

And finally, a prosaic question: There is a wide variety of single quote =
usage in config files. Are there any places that quotes are mandatory? =
What is the best practice here?

Many thanks!

Rich=


From nobody Thu Jul 28 16:33:05 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5526112D7B7 for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 16:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 y5uwKoBk1Z9z for <homenet@ietfa.amsl.com>; Thu, 28 Jul 2016 16:33:00 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0085012D9B0 for <homenet@ietf.org>; Thu, 28 Jul 2016 16:32:59 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id s63so77207236qkb.2 for <homenet@ietf.org>; Thu, 28 Jul 2016 16:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=yATzIuC3dKvCYhn6H5zke/t3LUF4421TFMUuc/7QBwg=; b=y4TKR6LkyeyE3hsjmv50BsKbatIjpNWFS52KDUs09bpBiC7r/TGEDgMbCXApHcOfBn 5cxMaiVImKjfXVjtTr3qSiPaW9PFenSJn8gQDZHhoH6s2IoG4RKBbLCNYuV61sPJgC67 +bAXoiJcfHIQAOEc+qfjbJHpV7HgnzpXVm7BMue41MWmIHnFVRzFxLlui0nvDKYYYoYY KkOhcf3O2vn4avd6nDVCjlogDj6gbVdGVxlhkSOe9EFUWbnv2S7liE6YWluVJYSVsapS w4o5w0h3JOYvfMJ4+pvHJHj6EHaG5LActnKbNV3EDFQ2EJ2V4U3w/RdVG7laxNTyaVQr BPLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=yATzIuC3dKvCYhn6H5zke/t3LUF4421TFMUuc/7QBwg=; b=aTjf6QbNjKQWIi7m3A1cnaPyo4xNrjGi/ctITvMPS0J//yXlqAVzWbn7IrYH//K4dK 9c3/KKRgoNILQvhpsJ3rXYDiF1kh1MTS7JMPZFfL5hY854+xacnSfEfU2vrA5EeUURuz 1zPXfB50+j+Qw5tgMPW+vwBY8ifVd5nFZ5u+7TjG0+LbOe/xV6zRlNmqQHlXiUsLR8S0 DvvowvuJAocnUcym36R8miO29XJJREFIApb2Sls8pIZnAoMmM7f8Whc4KH4Yod1aEJ0s hJdc096H0HAh0uNt75nARX8aT6iga4LmJa5SFoRrb+Mg/ppeL6Wk/UZOx6cR5vb6/fMY sYKg==
X-Gm-Message-State: AEkoouvPzn50n8C/+8TSNYN69CARmcx7oKcTkBmAxrTTBpg8QHH1s0Yl4oz+9vDFoJbUhg==
X-Received: by 10.233.237.136 with SMTP id c130mr6979616qkg.126.1469748778808;  Thu, 28 Jul 2016 16:32:58 -0700 (PDT)
Received: from richs-mbp-4661.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id g3sm2120571qkf.35.2016.07.28.16.32.58 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 28 Jul 2016 16:32:58 -0700 (PDT)
From: Rich Brown <richb.hanover@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com>
Date: Thu, 28 Jul 2016 19:32:57 -0400
To: homenet@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/E9w-7GKu3XzA4O78eRFOgjzTqzU>
Subject: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2016 23:33:04 -0000

I have had half-success (that is, one out of two routers worked) =
installing hnet-full.
=20
1) I have a Netgear WNDR3800 where the instructions I posted at =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901 =
seem to work fine.=20

2) I have had trouble with a mqmaker.com WiTi router. Steps 1-9 (above) =
work fine. I can configure the two radios and the WAN port to hnet, =
leaving the LAN port on 192.168.1.1, and the router works as expected. =
Both W24 and W5 give out DHCP addresses, and E0 acquires a DHCP address =
from the upstream (Ethernet) router.

When I convert the lan port to hnet as described in Step 10, everything =
comes to tears. After the reboot, the LAN ports do not give DHCP =
addresses, and I cannot connect to either wireless interface...

What other information could I provide? Would it help to have a copy of =
/etc for the afflicted router? I also have a serial interface, so could =
send along the boot logs...

Many thanks,

Rich=


From nobody Fri Jul 29 03:37:23 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF0D512DC3B for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:37:21 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 rmY_CifYRgCP for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:37:19 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AE4312DC2B for <homenet@ietf.org>; Fri, 29 Jul 2016 03:37:18 -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/56228) with ESMTP id u6TAbF8n001517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Jul 2016 12:37:15 +0200
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/56228) with ESMTP id u6TAbF1J003210; Fri, 29 Jul 2016 12:37:15 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C1C7261F9D; Fri, 29 Jul 2016 12:37:15 +0200 (CEST)
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 RY0E4_1RiHtz; Fri, 29 Jul 2016 12:37:14 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 37CC161FA1; Fri, 29 Jul 2016 12:37:13 +0200 (CEST)
Date: Fri, 29 Jul 2016 12:37:13 +0200
Message-ID: <87oa5gafxi.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=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 29 Jul 2016 12:37:16 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 29 Jul 2016 12:37:15 +0200 (CEST)
X-Miltered: at korolev with ID 579B31DB.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 579B31DB.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579B31DB.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: 579B31DB.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 : 579B31DB.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 579B31DB.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: <https://mailarchive.ietf.org/arch/msg/homenet/YHPunj-c-oKTR-PmUOspdITDzcw>
Cc: Gaglione =?ISO-8859-1?Q?Jean-Rapha=EBl?= <jr.gaglione@yahoo.fr>, "antonin.decimo@gmail.com" <antonin.decimo@gmail.com>
Subject: [homenet] Tcpdump support for HNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 10:37:22 -0000

Hi,

A cleaned-up version of Antonin's and Jean-Raphaël's code for tcpdump is
available in the hncp-20160728 branch of their github repository:

  https://github.com/MisterDA/tcpdump/tree/hncp-20160728

  git clone -b hncp-20160728 https://github.com/MisterDA/tcpdump

The pull request is here:

  https://github.com/the-tcpdump-group/tcpdump/pull/534

If you need to get in touch with them, they're in CC of this mail.

-- Juliusz


From nobody Fri Jul 29 03:43:01 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4CB12DC6C for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:43:00 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 IHGCciBx5E3I for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:42:59 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32BA312DC63 for <homenet@ietf.org>; Fri, 29 Jul 2016 03:42:56 -0700 (PDT)
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/56228) with ESMTP id u6TAgs5i004900; Fri, 29 Jul 2016 12:42:54 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 57A0061F9A; Fri, 29 Jul 2016 12:42:54 +0200 (CEST)
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 FpMhbgvfbSox; Fri, 29 Jul 2016 12:42:53 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1C7CD61FA1; Fri, 29 Jul 2016 12:42:53 +0200 (CEST)
Date: Fri, 29 Jul 2016 12:42:53 +0200
Message-ID: <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com>
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 [194.254.61.138]); Fri, 29 Jul 2016 12:42:54 +0200 (CEST)
X-Miltered: at korolev with ID 579B332E.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579B332E.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 : 579B332E.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: <https://mailarchive.ietf.org/arch/msg/homenet/B2dm7XCxWnBjP-ve55E8jEPhP4A>
Cc: homenet@ietf.org
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 10:43:00 -0000

> When I convert the lan port to hnet as described in Step 10, everything
> comes to tears. After the reboot, the LAN ports do not give DHCP
> addresses, and I cannot connect to either wireless interface...

I assume you have no serial console on this board?

What I would suggest would be to convert the WAN and WLAN interfaces to
Homenet, but keep the LAN statically configured.  Then, log in on the LAN
interface twice, and in one window say

  logread -f

and in the other say

  /etc/init.d/networking restart

-- Juliusz




From nobody Fri Jul 29 03:55:39 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B19612DCE0 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:55:35 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 7lpjgYFoH2Go for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 03:55:34 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E0712DD02 for <homenet@ietf.org>; Fri, 29 Jul 2016 03:54:25 -0700 (PDT)
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/56228) with ESMTP id u6TAsOHN011283; Fri, 29 Jul 2016 12:54:24 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 211D661F9A; Fri, 29 Jul 2016 12:54:24 +0200 (CEST)
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 sIVhOpVqn1JZ; Fri, 29 Jul 2016 12:54:22 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id DF84E61FA2; Fri, 29 Jul 2016 12:54:22 +0200 (CEST)
Date: Fri, 29 Jul 2016 12:54:22 +0200
Message-ID: <87h9b8af4x.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com> <87k2g4afo2.wl-jch@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: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 29 Jul 2016 12:54:24 +0200 (CEST)
X-Miltered: at korolev with ID 579B35E0.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579B35E0.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 : 579B35E0.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/W76-9_FZrzbwmg6j5ZOFuTb49Cw>
Cc: homenet@ietf.org
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 10:55:35 -0000

> What I would suggest would be to convert the WAN and WLAN interfaces to
> Homenet, but keep the LAN statically configured.

Er, sorry.  I missed the bit where you say that things only go wrong when
you convert the LAN interface to hnet.

I'm afraid you're going to have to log in through the WAN interface, which
requires some minor firewall tweaks.

-- Juliusz


From nobody Fri Jul 29 04:12:19 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A2412DCFA for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 04:12:17 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 04Ga98mh8idz for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 04:12:15 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA0112DD12 for <homenet@ietf.org>; Fri, 29 Jul 2016 04:12:08 -0700 (PDT)
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/56228) with ESMTP id u6TBC6nX018786; Fri, 29 Jul 2016 13:12:06 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 35EC561F9A; Fri, 29 Jul 2016 13:12:06 +0200 (CEST)
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 o2LcgnptmzS1; Fri, 29 Jul 2016 13:12:04 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 43B2B61F9D; Fri, 29 Jul 2016 13:12:04 +0200 (CEST)
Date: Fri, 29 Jul 2016 13:12:04 +0200
Message-ID: <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com>
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 [194.254.61.138]); Fri, 29 Jul 2016 13:12:06 +0200 (CEST)
X-Miltered: at korolev with ID 579B3A06.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579B3A06.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 : 579B3A06.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/LsN_F7JBuU_QmKvgdfBtPFOn8M0>
Cc: homenet@ietf.org
Subject: Re: [homenet] hnet-full & LEDE bug report
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 11:12:17 -0000

> Should the procedure remain silent on the firewall? Or should people
> just put all interfaces into the lan zone? Or something else?

Pleae leave it as it is, it's fine.  I'd remove the bits about making E0
internal, it just confuses things -- if the router has a 4-port switch,
it's not likely that getting an extra internal interface is likely to be
a critical feature.

>> If I were you, I'd explicitly tell hnetd that the E0 interface is external
>> ("option mode external"), since I don't trust the edge detection mechanism.

> I think you mean E1 - that's what the instructions use for the wide area
> interface.

It looks like one of us is confused.

> And 'option mode external' goes in /etc/config/network?

Yes, in the interface section.

> And is there a man page for hnetd that gives other options?

https://wiki.openwrt.org/doc/uci/network#protocol_hnet_self-managing_home_network_hncp

>> - before you start hacking, write down the IPv6 link-local address of
>> the LAN interface, to make sure you can log in;

> Done. The newest draft also tells people to make backups :-)

Please tone it down -- no need to frighten people, and if things go wrong,
you just boot into failsafe mode and either fix things or reset the router:

  https://wiki.openwrt.org/doc/howto/generic.failsafe

Please use "sysupgrade -b backup.tar.gz" to do the backup -- I'd rather
you didn't mention the web interface at all, I've found it to be more
hassle than it's worth, and it's not included by default in the snapshot
(unstable) builds.

>> - you should review /etc/config/upnpd, and list the interfaces you want
>> to allow NAT-PMP on.

> I'm not quite sure how that affects things. Where would NAT-PMP be
> important in my home net?

It allows clients to perform port redirection automatically.  Firewalls
are evil.

I also add the following to the firewall config:

config rule
        option target 'ACCEPT'
        option src 'wan'
        option name 'Accept-v6'
        option family 'ipv6'
        option dest 'lan'
        option dest_port '1024-65535'

Of course, since you've renamed wan and lan, you'll need to tweak the
relevant tweakanda.

> And finally, a prosaic question: There is a -wide variety of single
> quote usage in config files. Are there any places that quotes are
> mandatory?

The syntax is the same as the shell's.  Actually, the config files are
shell script fragments -- 'config' and 'option' are shell functions,
defined in /lib/functions.sh.

> What is the best practice here?

Put single quotes everywhere, it avoids having to think about special
characters.

Thanks again for your work, Rich.

-- Juliusz


From nobody Fri Jul 29 07:38:46 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 506E612D758 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 bOv_2GoIe8Ic for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:38:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90E6612D752 for <homenet@ietf.org>; Fri, 29 Jul 2016 07:38:43 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 539E1200A3; Fri, 29 Jul 2016 10:48:44 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9215638D1; Fri, 29 Jul 2016 10:38:42 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87oa5gafxi.wl-jch@pps.univ-paris-diderot.fr>
References: <87oa5gafxi.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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: Fri, 29 Jul 2016 10:38:42 -0400
Message-ID: <4576.1469803122@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/oiG1idTDHs0KVFwwZwwmtwZW754>
Cc: homenet@ietf.org, "antonin.decimo@gmail.com" <antonin.decimo@gmail.com>, Gaglione =?us-ascii?Q?=3D=3FISO-8859-1=3FQ=3FJean-Rapha=3DEBl=3F=3D?= <jr.gaglione@yahoo.fr>
Subject: Re: [homenet] Tcpdump support for HNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 14:38:45 -0000

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


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    > A cleaned-up version of Antonin's and Jean-Rapha=C3=ABl's code for tc=
pdump is
    > available in the hncp-20160728 branch of their github repository:

    > https://github.com/MisterDA/tcpdump/tree/hncp-20160728

    > git clone -b hncp-20160728 https://github.com/MisterDA/tcpdump

    > The pull request is here:

    > https://github.com/the-tcpdump-group/tcpdump/pull/534

<tcpdump.org hat>
Thank you... the 4.8.0-rc2 will go out on Monday with it.
There are some wpcap.dll issues that we are also waiting on.
</tcpdump.org hat>

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV5tqb4CLcPvd0N1lAQKMOwf+Ne6+PbCKnV+xHp62m0Rp5GadF0bI5qEB
PLGUPmKukpKlD7QkkPJFH2y7xO0Q+fvG7Z2fFcniQurB4LgLgLqPT4MPRpKceciZ
3cFB4hctAEg8kqYB6q4A7vwoBf/7PGD0Qr+B7aBnQNnqQGjT6Mg5dJZ4ypznHQBp
qbm/+nw6mgyX6YtUuEfruT2WtKkrQsO9ROIMQyDXg+yLtMrxET6yJMpCf37BtZu2
mFvOOSMWTUQqNTEy6/NR5VgG58X8j47llWdMMub2fy4t/K1gtzoadlO+aQ5fYRja
7As+hefeN8DT0IApC6+VfnKVew37IjfJ/W7GkxB6464tfmB1xsrOXg==
=Rz+Y
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 29 07:42:47 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7926912D764 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 B6VQJmqhIstM for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:42:41 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E450312D75E for <homenet@ietf.org>; Fri, 29 Jul 2016 07:42:40 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id p74so92497615qka.0 for <homenet@ietf.org>; Fri, 29 Jul 2016 07:42:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YAggQHUI0DjGtHr2wALIbo5apE5u82rrD9r6EnoCA1E=; b=WtpgUWuZ2bIQLeSYEplvocziFQhpzSSv3znOk6ywhsh8mgwv48kjk6MWqHPzdsBm/N UR130gopWv3h/i4IU/woFt6130TcM5pnC5PvIpIuyc+prvgGiX2mRP+dI7U2kK4CPaxB kp7phIioLwp538zVgVSwODTwuYb9cLNaSsEz4K02qcmg2e9Qht3X6f2Qb5xyiEx1f0kF By1RbUgdJHMSbO8VO8V0d/8u36Sb5ma+DiuvyvmV1ZU/liRH0yDgrjbEI451Ckyz/5XW 9rrfTNWwamZWqPwLmph8b0EcsPLqxklCNJ0o2zl1mvCjAYX5XPwUKAIMNurdngkr3II9 XF/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YAggQHUI0DjGtHr2wALIbo5apE5u82rrD9r6EnoCA1E=; b=f8GEIq4cgYZkGUF/HJ4zJTaoJwV4LR1Dbf9ksLwbddd2vmRh7mpjgYrvleQXuZSZc2 S7hgE7V5C9wbyix0gUNCYD6qhcbLoy/fD4KIyb1J2eyzgHi7PqVESt4dOOsJsgUcy7X/ W9hzjYJ7LYmnz4qHtmdvO2rLi3OslcmYV64XbHOkqpR2GUp/oLvhQWK5WXbmNGlznU+p f3zOl2mMDV3rP3XED+4CI8OWUWmiE2P+MM6yvHvjxtN9bZt7LH6A3RdkhDyk5P5qOLjs C0qzqklKeoDJQ0POmqROquAWj67QLzqpwgmfNnu24pLJqRtwOU4jKaBL7PloOo7wjU+e iZ6Q==
X-Gm-Message-State: AEkooutAel1PCpeKeOuVu2r/Q7Jjwu+BtGyfp14LsGWjhTzl5qEvLJy3V9IHT4bAoLLl0g==
X-Received: by 10.55.72.17 with SMTP id v17mr50350517qka.44.1469803359957; Fri, 29 Jul 2016 07:42:39 -0700 (PDT)
Received: from richs-mbp-4661.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id j6sm10217569qke.26.2016.07.29.07.42.38 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 29 Jul 2016 07:42:38 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 29 Jul 2016 10:42:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/HT0wz8hlBSHkF1sohcf3AoT6C2Q>
Cc: homenet@ietf.org
Subject: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 14:42:45 -0000

Thanks again for your comments. They're reflected in the new draft: =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901

> On Jul 29, 2016, at 7:12 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> Should the procedure remain silent on the firewall? Or should people
>> just put all interfaces into the lan zone? Or something else?
>=20
> Pleae leave it as it is, it's fine.  I'd remove the bits about making =
E0
> internal, it just confuses things -- if the router has a 4-port =
switch,
> it's not likely that getting an extra internal interface is likely to =
be
> a critical feature.

Done.

>>> If I were you, I'd explicitly tell hnetd that the E0 interface is =
external
>>> ("option mode external"), since I don't trust the edge detection =
mechanism.
>=20
>> I think you mean E1 - that's what the instructions use for the wide =
area
>> interface.
>=20
> It looks like one of us is confused.

It looks like it was me. :-)=20

>> And 'option mode external' goes in /etc/config/network?
>=20
> Yes, in the interface section.

I have updated E0 /etc/config/network to mention "option 'mode' =
'external'"

>> And is there a man page for hnetd that gives other options?
>=20
> =
https://wiki.openwrt.org/doc/uci/network#protocol_hnet_self-managing_home_=
network_hncp

Added to the External References section along with a link to RFC7788

>>> - before you start hacking, write down the IPv6 link-local address =
of
>>> the LAN interface, to make sure you can log in;
>=20
>> Done. The newest draft also tells people to make backups :-)
>=20
> Please tone it down -- no need to frighten people,

Actually, I'm writing this for a less knowledgeable audience. (Me, for =
example. I'm learning as I go along, with your kind assistance :-)=20

My goal is to produce an approachable document that has a good balance =
between background information and "Just Do This". I want to produce the =
"guide" that I wish I had when I started with Homenet. That's why I'm =
also adding in bits of knowledge (in the External References, =
Troubleshooting Procedures, etc.) that might help other people get =
themselves out of trouble.

This is a corollary of your assertion at IETF the other day ("if it=E2=80=99=
s not implemented, it didn=E2=80=99t happen") It's also true that if no =
one can install it, it's not going to be tested in the real world. :-)

> and if things go wrong,
> you just boot into failsafe mode and either fix things or reset the =
router:
>=20
>  https://wiki.openwrt.org/doc/howto/generic.failsafe

This is useful advice. There's now a link to the page in the =
Troubleshooting Procedures.=20

<rant> That OpenWrt page is a primary example of the style of =
documentation I abhor. It's enough to make the shields come down over my =
eyes. Huge blocks of text. Starts with a description of what it does =
("bypasses all configuration...") without initially saying *why* you =
might want to use it. Three alternative methods, giving equal prominence =
to a) the most common case that's easy and will work 99% of the time, b) =
a super-techie process (packet sniffer) and c) using a serial connection =
that most people don't have. In fact, I had never looked at that page =
until you recommended it, since it was so inscrutable, and I wasn't sure =
it would ever apply to me...</rant>

> Please use "sysupgrade -b backup.tar.gz" to do the backup -- I'd =
rather
> you didn't mention the web interface at all, I've found it to be more
> hassle than it's worth, and it's not included by default in the =
snapshot
> (unstable) builds.

I have added sysupgrade to the Backup procedure. But I like to recommend =
the LuCI GUI because:
	a) it gets the backup off the device onto my computer
	b) it date-stamps the backup
	c) it adds the router's name to the filename

>>> - you should review /etc/config/upnpd, and list the interfaces you =
want
>>> to allow NAT-PMP on.
>=20
>> I'm not quite sure how that affects things. Where would NAT-PMP be
>> important in my home net?
>=20
> It allows clients to perform port redirection automatically.  =
Firewalls
> are evil.
>=20
> I also add the following to the firewall config:
>=20
> config rule
>        option target 'ACCEPT'
>        option src 'wan'
>        option name 'Accept-v6'
>        option family 'ipv6'
>        option dest 'lan'
>        option dest_port '1024-65535'
>=20
> Of course, since you've renamed wan and lan, you'll need to tweak the
> relevant tweakanda.

I have added both these to a "Next Steps" section since they're not core =
to switching to hnet. I don't know much about them, and will study them =
more when I get time.

>> And finally, a prosaic question: There is a -wide variety of single
>> quote usage in config files. Are there any places that quotes are
>> mandatory?
>=20
> The syntax is the same as the shell's.  Actually, the config files are
> shell script fragments -- 'config' and 'option' are shell functions,
> defined in /lib/functions.sh.
>=20
>> What is the best practice here?
>=20
> Put single quotes everywhere, it avoids having to think about special
> characters.

Done.

> Thanks again for your work, Rich.
>=20
> -- Juliusz

And thank you for your patience.=20

Rich=


From nobody Fri Jul 29 07:49:22 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9719712D73A for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FvOCwfI6MR4h for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 07:49:20 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 189C712D76B for <homenet@ietf.org>; Fri, 29 Jul 2016 07:49:16 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id x1so92713415qkb.3 for <homenet@ietf.org>; Fri, 29 Jul 2016 07:49:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=Bhb0eKCtdU0zfq8HIfkRfmXp5hUAjRdY2RC65T7mzN0=; b=s92XAsDG7IRXFNEjhQHqEoqPnSEwFd7PGYNgFJBAr0DjTzkB9OH4EtOZsq+/9Bnrbp ndQDQL96VMIAesWv+IxLRMsMm5wpbYwvlqdcJbtCCW2bpo7tb/7deSWs6cGO6C6AhV6H lGhVrwwU4hp5HDLOrOdOBsetwbbQTYmHNX44Im5yEoPhBa7L6rUAsnvwZRN5l44beGlr nMKFULmlFu2R/CNm2hf0LJ/I5dmoOyDgFb+Sfy4/HSDtT+c8jnGcGashuK4Z838HSpyB sBoV3sB7Oe//C7C1/GF5bp9L4hhc+95yuNbEH6ozvnUE1Y+HuJePVcRKmE2qZ8B54X9t Esqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=Bhb0eKCtdU0zfq8HIfkRfmXp5hUAjRdY2RC65T7mzN0=; b=d9dCHoRx72xHF+wQ7BsE+5s389X2s6izPg7iSJPRmIv02LlI43K4pXWKak4fcTUQVH X4UNnsZvpC2iPWrMDBuNoHV64vlno7pOEfa9shK0xECH2PkgPReu/VwH0cU4y73vIjKg 0puye+4bu3e4ieSaHy/IUT5ndtVZKwo8Rt3gYSVTZm673VqjugS2jjGawR5w8Fz+qOob +3VYRHOpWSttI2VTJXm8rQ1RhiwCwS7OsnqEXQ99yqpIOKY7FYIUOs4jownuhJeFLNg6 bwmPXCe1gWcUrU2vaF2QJT0MMjxv+GHmE3kV4V3KPY0h1eTd5pEwfKbHIxxZA0SLZBrF MyKg==
X-Gm-Message-State: AEkoousjC5Uv466UD6UgopHRsArLbCOn5fed5yI2ehcyOQ8tidXHqShaKVrtP6ANY/PPEg==
X-Received: by 10.55.148.67 with SMTP id w64mr49105420qkd.137.1469803755235; Fri, 29 Jul 2016 07:49:15 -0700 (PDT)
Received: from richs-mbp-4661.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id c25sm10242687qta.6.2016.07.29.07.49.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 29 Jul 2016 07:49:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87d1lwadaj.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 29 Jul 2016 10:49:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D44BF14-8927-4EF0-AE8E-6AD57E09B49D@gmail.com>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com> <87d1lwadaj.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, homenet@ietf.org
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/RUpyWIaw8Els0nJjWsmZqenNrzE>
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 14:49:21 -0000

Hi Juliusz,

Thanks again for your insights.

> On Jul 29, 2016, at 7:34 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> WiTi router.
>=20
> That looks like a nice board.  Please let me know how well it goes.

I got it at a good price through kickstarter/indiegogo/can't remember. =
But I wouldn't recommend it (they're undercapitalized, poor English =
skills, not particularly forthcoming with technical info). Virtually all =
their support comes from their community forum, but they continue to say =
good things about it.

>> When I convert the lan port to hnet as described in Step 10, =
everything
>> comes to tears.
>=20
> The Ethernets are connected in strange ways.  Are you sure you got =
your
> ifnames right?

I thought so, but I'm a real beginner here. What's the best way to get =
info to you? I thought of:

- sending a zip of /etc/
- sending the console log (I do have a serial interface)
- Anything else?
>=20
> -- Juliusz

Thanks again.

Rich=


From nobody Fri Jul 29 08:09:55 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1770E12D782 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 08:09:54 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 FrN7ufy-HKcn for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 08:09:51 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F27B912D53C for <homenet@ietf.org>; Fri, 29 Jul 2016 08:09:50 -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/56228) with ESMTP id u6TF9mlk015517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Jul 2016 17:09:48 +0200
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/56228) with ESMTP id u6TF9mb2030405; Fri, 29 Jul 2016 17:09:48 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 22B0B61FA1; Fri, 29 Jul 2016 17:09:48 +0200 (CEST)
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 7_ieS1x4vo2k; Fri, 29 Jul 2016 17:09:46 +0200 (CEST)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B79A061F9D; Fri, 29 Jul 2016 17:09:46 +0200 (CEST)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.87) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1bT9Q2-0002r5-HX; Fri, 29 Jul 2016 17:09:46 +0200
Date: Fri, 29 Jul 2016 17:09:46 +0200
Message-ID: <7ishuswked.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <4576.1469803122@obiwan.sandelman.ca>
References: <87oa5gafxi.wl-jch@pps.univ-paris-diderot.fr> <4576.1469803122@obiwan.sandelman.ca>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 29 Jul 2016 17:09:48 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 29 Jul 2016 17:09:48 +0200 (CEST)
X-Miltered: at korolev with ID 579B71BC.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 579B71BC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579B71BC.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: 579B71BC.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 : 579B71BC.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 579B71BC.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: <https://mailarchive.ietf.org/arch/msg/homenet/WlzjWWvE2EQxLaIADNJekJFfzTM>
Cc: homenet@ietf.org, "antonin.decimo@gmail.com" <antonin.decimo@gmail.com>, Gaglione =?ISO-8859-1?Q?Jean-Rapha=EBl?= <jr.gaglione@yahoo.fr>
Subject: Re: [homenet] Tcpdump support for HNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 15:09:54 -0000

> Thank you... the 4.8.0-rc2 will go out on Monday with it.

Jean-Raphaël is in my office, he's telling me "I thought upstreaming was
supposed to be difficult" ;-)

-- Juliusz


From nobody Fri Jul 29 08:16:15 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21D9512D186 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 08:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 R8iyvrpFFzo9 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 08:16:11 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 241A912D17A for <homenet@ietf.org>; Fri, 29 Jul 2016 08:16:11 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id 52so68379115qtq.3 for <homenet@ietf.org>; Fri, 29 Jul 2016 08:16:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PBINO3jpkYh2uUjRT0kucKaWqBuFX4nWlfDqGS7gRDQ=; b=WPZnhDkqh2y9Yq9rsZej2A8dO6TrcdsE8hrH60oQQx5Y8b/LR0ZtNXMDymT/TSPnYS ZQaBZY46wVWq3EwPFV9mph/S+rsgSoUym9PdlXdK+945SbaEhMSy0Hja0UT0Ue3KBn/y bo50QM2rNdfAlLoB0WK4IFRoGNlrG5ZwbexR9u+JRfx0+G/cRUeBy6O6LoGeVHiD9TO1 nKtU+e4eD64pwxQ2//7GqKJuSA6vN/85JGo0asMYeElW8xdDQip1eRFs9rlWdJEX9Yoc RLo9/Rox69UMu9X2YJNY1bTt33oQ1B8dZOygZ2t1rSC+w0MjekQIb5powN7YCbI917U3 bnOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PBINO3jpkYh2uUjRT0kucKaWqBuFX4nWlfDqGS7gRDQ=; b=Z0Uiygqab4iOppfuMkvlZl9bzkcCljVVGEvOFA6ZeEnpR6Dib+iQVpKWSSAcVwc7rR QKGa7oIC8ik0SMdVebHPBzYcWO2KWtR84BwsufpL+0Xy1Tg5ZJgsymbZ1IeqBuYzxhQi mcavcitf0+jcgNTsZd2EkojQzZEnYL8FFcqV37HTjmWDVtscxV1jcMHcoY3tCHbgEjju lfyRTR6BEGyduumQpScpqPJD0QaTu7byEeho7neQ+c4OSEgBRYLvj320zOW0f4wHbXQ5 ViG12TDacp/JOHOrdeiAIk73XkP5/6bZUXuG7TUz7F4evRsVR5aHsBzyaYupJ0AN1ymi i8Fg==
X-Gm-Message-State: AEkooutv2lE9lkSg6BkNiuEJPCbh/VZOTEMwt6p+mhpuuDLPCqDyfdF6R5i+Oe1DytSJ/Q==
X-Received: by 10.200.51.251 with SMTP id d56mr69088655qtb.36.1469805370065; Fri, 29 Jul 2016 08:16:10 -0700 (PDT)
Received: from richs-mbp-4661.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id t42sm10290203qte.24.2016.07.29.08.16.08 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 29 Jul 2016 08:16:08 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com>
Date: Fri, 29 Jul 2016 11:16:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6C349E8-D745-4DF5-A734-2682685EE8D4@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com>
To: "Richard E. Brown" <richb.hanover@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/ujFUnEKu7aeHbLBV8NRVk2lP8vo>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 15:16:13 -0000

Also... I'm aware that the Installing Homenet guide elides the reasons =
for using it. Do we have a short paragraph that tells *why* a lay person =
would want to use Homenet?=20

If I'm not mistaken, these are the big attributes:

- No configuration - Homenet routers figure out how things are connected =
and do the right thing
- Local devices (printers, servers, etc) can be discovered easily (using =
mDNS, et al, but I don't want to use those acronyms...)
- Is it true that if a vendor shipped a fully-Homenet router, you could =
take it out of the box, plug it in, and you'd be 'on the air'?

I looked to see if there was anything on homewrt.org (it's currently =
down, but the Wayback Machine archived a few pages - =
https://web.archive.org/web/20150912135701/http://www.homewrt.org/doku.php=
 ) Nothing there that I could use.=20

Thanks.

Rich


> On Jul 29, 2016, at 10:42 AM, Rich Brown <richb.hanover@gmail.com> =
wrote:
>=20
> Thanks again for your comments. They're reflected in the new draft: =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901
>=20
>> On Jul 29, 2016, at 7:12 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>>=20
>>> Should the procedure remain silent on the firewall? Or should people
>>> just put all interfaces into the lan zone? Or something else?
>>=20
>> Pleae leave it as it is, it's fine.  I'd remove the bits about making =
E0
>> internal, it just confuses things -- if the router has a 4-port =
switch,
>> it's not likely that getting an extra internal interface is likely to =
be
>> a critical feature.
>=20
> Done.
>=20
>>>> If I were you, I'd explicitly tell hnetd that the E0 interface is =
external
>>>> ("option mode external"), since I don't trust the edge detection =
mechanism.
>>=20
>>> I think you mean E1 - that's what the instructions use for the wide =
area
>>> interface.
>>=20
>> It looks like one of us is confused.
>=20
> It looks like it was me. :-)=20
>=20
>>> And 'option mode external' goes in /etc/config/network?
>>=20
>> Yes, in the interface section.
>=20
> I have updated E0 /etc/config/network to mention "option 'mode' =
'external'"
>=20
>>> And is there a man page for hnetd that gives other options?
>>=20
>> =
https://wiki.openwrt.org/doc/uci/network#protocol_hnet_self-managing_home_=
network_hncp
>=20
> Added to the External References section along with a link to RFC7788
>=20
>>>> - before you start hacking, write down the IPv6 link-local address =
of
>>>> the LAN interface, to make sure you can log in;
>>=20
>>> Done. The newest draft also tells people to make backups :-)
>>=20
>> Please tone it down -- no need to frighten people,
>=20
> Actually, I'm writing this for a less knowledgeable audience. (Me, for =
example. I'm learning as I go along, with your kind assistance :-)=20
>=20
> My goal is to produce an approachable document that has a good balance =
between background information and "Just Do This". I want to produce the =
"guide" that I wish I had when I started with Homenet. That's why I'm =
also adding in bits of knowledge (in the External References, =
Troubleshooting Procedures, etc.) that might help other people get =
themselves out of trouble.
>=20
> This is a corollary of your assertion at IETF the other day ("if =
it=E2=80=99s not implemented, it didn=E2=80=99t happen") It's also true =
that if no one can install it, it's not going to be tested in the real =
world. :-)
>=20
>> and if things go wrong,
>> you just boot into failsafe mode and either fix things or reset the =
router:
>>=20
>> https://wiki.openwrt.org/doc/howto/generic.failsafe
>=20
> This is useful advice. There's now a link to the page in the =
Troubleshooting Procedures.=20
>=20
> <rant> That OpenWrt page is a primary example of the style of =
documentation I abhor. It's enough to make the shields come down over my =
eyes. Huge blocks of text. Starts with a description of what it does =
("bypasses all configuration...") without initially saying *why* you =
might want to use it. Three alternative methods, giving equal prominence =
to a) the most common case that's easy and will work 99% of the time, b) =
a super-techie process (packet sniffer) and c) using a serial connection =
that most people don't have. In fact, I had never looked at that page =
until you recommended it, since it was so inscrutable, and I wasn't sure =
it would ever apply to me...</rant>
>=20
>> Please use "sysupgrade -b backup.tar.gz" to do the backup -- I'd =
rather
>> you didn't mention the web interface at all, I've found it to be more
>> hassle than it's worth, and it's not included by default in the =
snapshot
>> (unstable) builds.
>=20
> I have added sysupgrade to the Backup procedure. But I like to =
recommend the LuCI GUI because:
> 	a) it gets the backup off the device onto my computer
> 	b) it date-stamps the backup
> 	c) it adds the router's name to the filename
>=20
>>>> - you should review /etc/config/upnpd, and list the interfaces you =
want
>>>> to allow NAT-PMP on.
>>=20
>>> I'm not quite sure how that affects things. Where would NAT-PMP be
>>> important in my home net?
>>=20
>> It allows clients to perform port redirection automatically.  =
Firewalls
>> are evil.
>>=20
>> I also add the following to the firewall config:
>>=20
>> config rule
>>       option target 'ACCEPT'
>>       option src 'wan'
>>       option name 'Accept-v6'
>>       option family 'ipv6'
>>       option dest 'lan'
>>       option dest_port '1024-65535'
>>=20
>> Of course, since you've renamed wan and lan, you'll need to tweak the
>> relevant tweakanda.
>=20
> I have added both these to a "Next Steps" section since they're not =
core to switching to hnet. I don't know much about them, and will study =
them more when I get time.
>=20
>>> And finally, a prosaic question: There is a -wide variety of single
>>> quote usage in config files. Are there any places that quotes are
>>> mandatory?
>>=20
>> The syntax is the same as the shell's.  Actually, the config files =
are
>> shell script fragments -- 'config' and 'option' are shell functions,
>> defined in /lib/functions.sh.
>>=20
>>> What is the best practice here?
>>=20
>> Put single quotes everywhere, it avoids having to think about special
>> characters.
>=20
> Done.
>=20
>> Thanks again for your work, Rich.
>>=20
>> -- Juliusz
>=20
> And thank you for your patience.=20
>=20
> Rich


From nobody Fri Jul 29 09:41:14 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5276012D7F5 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 09:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 8owNuf9G9YU0 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 09:41:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B155712D103 for <homenet@ietf.org>; Fri, 29 Jul 2016 09:41:11 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 60444200A3; Fri, 29 Jul 2016 12:51:12 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 835B1638D1; Fri, 29 Jul 2016 12:41:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <7ishuswked.wl-jch@pps.univ-paris-diderot.fr>
References: <87oa5gafxi.wl-jch@pps.univ-paris-diderot.fr> <4576.1469803122@obiwan.sandelman.ca> <7ishuswked.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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: Fri, 29 Jul 2016 12:41:10 -0400
Message-ID: <30404.1469810470@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/CcL3E2ypRnyqD_Wi3xGUdpA9dDk>
Cc: homenet@ietf.org, "antonin.decimo@gmail.com" <antonin.decimo@gmail.com>, Gaglione =?us-ascii?Q?=3D=3FISO-8859-1=3FQ=3FJean-Rapha=3DEBl=3F=3D?= <jr.gaglione@yahoo.fr>
Subject: Re: [homenet] Tcpdump support for HNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 16:41:13 -0000

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


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    >> Thank you... the 4.8.0-rc2 will go out on Monday with it.

    > Jean-Rapha=C3=ABl is in my office, he's telling me "I thought upstrea=
ming was
    > supposed to be difficult" ;-)

You guys did your homework, posted your code with (unit) test cases, and so
all the other tests passed.  (Thanks travis-ci.org!)

More packet captures from homenet systems would naturally be very welcome...


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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV5uHI4CLcPvd0N1lAQJbegf/ZjAKQejb4DXclarQO/9vDX56pFdiNMhY
6s2nNlo/Uwzwy3zS06Vx3FGvrSB5xCuDQWFBB/8M9SqkSk+DT3hA5mcXCLnMrGPC
3ibR6jQPRW4scy5Q0dXjHyz7p9zLVcKWPym/Ox99FK1sr9N+p5C4aan9sbJ7ryjd
BtNE+zJJFVZDq9jYYAa1DJOg9uqzc4mUA9qkXeMn1FHu7OYjuEimbW/4BvW8UVON
JG6X2XUljvLXSTKLyMi6TAQspSnGi4EzhCjx96I4eUrn20/bnZ2bgz+NiQtjmyOo
e8vNAjqeWNG+/MJ4oSZVZ+7SAltwt0Qbfuyt+7iZQqC74XvzqsFH1A==
=kVgv
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 29 12:55:38 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F9612B057 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 12:55:36 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 Xdm8QQtH3c47 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 12:55:35 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0A8C12D7F5 for <homenet@ietf.org>; Fri, 29 Jul 2016 12:55:34 -0700 (PDT)
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/56228) with ESMTP id u6TJtWwN007104; Fri, 29 Jul 2016 21:55:32 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5283461FA1; Fri, 29 Jul 2016 21:55:32 +0200 (CEST)
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 RX3pqMNwmtqP; Fri, 29 Jul 2016 21:55:31 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id BF18861F9A; Fri, 29 Jul 2016 21:55:30 +0200 (CEST)
Date: Fri, 29 Jul 2016 21:55:31 +0200
Message-ID: <87bn1g6wy4.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <30404.1469810470@obiwan.sandelman.ca>
References: <87oa5gafxi.wl-jch@pps.univ-paris-diderot.fr> <4576.1469803122@obiwan.sandelman.ca> <7ishuswked.wl-jch@pps.univ-paris-diderot.fr> <30404.1469810470@obiwan.sandelman.ca>
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 [194.254.61.138]); Fri, 29 Jul 2016 21:55:32 +0200 (CEST)
X-Miltered: at korolev with ID 579BB4B4.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579BB4B4.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 : 579BB4B4.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/wF5kjDquvcZNagLBRgxx57pzbCI>
Cc: homenet@ietf.org, "antonin.decimo@gmail.com" <antonin.decimo@gmail.com>, Gaglione =?ISO-8859-1?Q?Jean-Rapha=EBl?= <jr.gaglione@yahoo.fr>
Subject: Re: [homenet] Tcpdump support for HNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 19:55:36 -0000

> You guys did your homework, posted your code with (unit) test cases, and so
> all the other tests passed.

Thanks for the kind words.  And thanks to you for the speedy pull, guys
can go for holidays with clear confirmation that their internship was
a success.

-- Juliusz


From nobody Fri Jul 29 13:06:26 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 463F212D833 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 13:06:25 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 cPqOZYV011u7 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 13:06:24 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3488512D80E for <homenet@ietf.org>; Fri, 29 Jul 2016 13:06:24 -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/56228) with ESMTP id u6TK6MvU010059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Jul 2016 22:06:22 +0200
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/56228) with ESMTP id u6TK6MNx009394; Fri, 29 Jul 2016 22:06:22 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 4E02661FA1; Fri, 29 Jul 2016 22:06:22 +0200 (CEST)
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 5-hN1O2VrNlX; Fri, 29 Jul 2016 22:06:21 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1049661F9A; Fri, 29 Jul 2016 22:06:21 +0200 (CEST)
Date: Fri, 29 Jul 2016 22:06:21 +0200
Message-ID: <878twk6wg2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 29 Jul 2016 22:06:22 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 29 Jul 2016 22:06:22 +0200 (CEST)
X-Miltered: at korolev with ID 579BB73E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 579BB73E.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579BB73E.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: 579BB73E.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 : 579BB73E.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 579BB73E.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: <https://mailarchive.ietf.org/arch/msg/homenet/WnZxckESg1EUaeTW7U4BrBo1ixw>
Cc: homenet@ietf.org
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug	report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 20:06:25 -0000

>>> I think you mean E1 - that's what the instructions use for the wide area
>>> interface.
>> 
>> It looks like one of us is confused.

> It looks like it was me. :-)

Why not rename the interfaces to "internal" and "external"?

> This is a corollary of your assertion at IETF the other day ("if itâ€™s
> not implemented, it didnâ€™t happen")

The next slide said "If it's deployed, it did happen".  With HNCP, we're
in the gray area between the two.

> <rant> That OpenWrt page is a primary example of the style of
> documentation I abhor.

Please speak to the LEDE guys.  Have a chat with "jow" and "HentaiMonster"
on Freenode, either on #openwrt or on #lede-dev.  "Nbd" is also extremely
competent, but he's more difficult to catch.

> I have added sysupgrade to the Backup procedure. But I like to recommend
> the LuCI GUI...

De gustibus non disputandum.  That's Latin for "you're wrong and I'm right" ;-)

-- Juliusz


From nobody Fri Jul 29 14:28:18 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1C512D112 for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 14:28:17 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 L0MBji8U3i9d for <homenet@ietfa.amsl.com>; Fri, 29 Jul 2016 14:28:15 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99CFD12D534 for <homenet@ietf.org>; Fri, 29 Jul 2016 14:28:15 -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/56228) with ESMTP id u6TLSDE8027243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Jul 2016 23:28:13 +0200
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/56228) with ESMTP id u6TLSDeO023920; Fri, 29 Jul 2016 23:28:13 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 17C3361F9D; Fri, 29 Jul 2016 23:28:13 +0200 (CEST)
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 GW1AoImyucRD; Fri, 29 Jul 2016 23:28:11 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id EF15F61F9A; Fri, 29 Jul 2016 23:28:08 +0200 (CEST)
Date: Fri, 29 Jul 2016 23:28:09 +0200
Message-ID: <87vazo5e3a.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <E6C349E8-D745-4DF5-A734-2682685EE8D4@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com> <E6C349E8-D745-4DF5-A734-2682685EE8D4@gmail.com>
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]); Fri, 29 Jul 2016 23:28:13 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 29 Jul 2016 23:28:13 +0200 (CEST)
X-Miltered: at korolev with ID 579BCA6D.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 579BCA6D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579BCA6D.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: 579BCA6D.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 : 579BCA6D.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 579BCA6D.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: <https://mailarchive.ietf.org/arch/msg/homenet/PwOpGEwJQf0L-nqys2KxWi0kMxM>
Cc: homenet@ietf.org
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 29 Jul 2016 21:28:17 -0000

> Also... I'm aware that the Installing Homenet guide elides the reasons for using it. Do we have a short paragraph that tells *why* a lay person would want to use Homenet? 

> - No configuration - Homenet routers figure out how things are connected
>   and do the right thing

Agreed, but see below.

> - Local devices (printers, servers, etc) can be discovered easily (using
>   mDNS, et al, but I don't want to use those acronyms...)

Yes, although I understand this is still in flux.

> - Is it true that if a vendor shipped a fully-Homenet router, you could
>   take it out of the box, plug it in, and you'd be 'on the air'?

That's just restating point (1) above in more user-friendly terms.

I think that the above is a little dry, you need to speak of user-visible
features:

 - you can extend your wireless range by just connecting an extra router.
   As the network expands, the routers will automatically compute the best
   paths and route packets accordingly;

 - new routers can be connected wirelessly -- you can put a new router in
   any place that's in range of an existing router.  Note that this
   requires some configuration (putting an interface in client mode, or
   putting a bunch of interfaces in ad-hoc mode);
pp
 - ability to use multiple providers at the same time -- connect your
   Homenet routers to two providers, and the network will automatically
   route to one, the other, or both, depending on whether you have
   sufficiently smart host software.  This requires no cooperation from
   the provider.

The Commission for Truth in Advertising requires me to mention that the
last feature is not quite ready yet -- with current software, when one
provider goes down, you might need to manually disable the router that's
connected to that provider.

-- Juliusz


From nobody Sat Jul 30 07:46:14 2016
Return-Path: <gert@space.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C44E12D635 for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 07:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.887
X-Spam-Level: 
X-Spam-Status: No, score=-3.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 7mjpKI3XegvL for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 07:46:11 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 636CE12D0E8 for <homenet@ietf.org>; Sat, 30 Jul 2016 07:46:10 -0700 (PDT)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 4AA0260699 for <homenet@ietf.org>; Sat, 30 Jul 2016 16:46:08 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 0D9AB602D3; Sat, 30 Jul 2016 16:46:08 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 0A4BEB837; Sat, 30 Jul 2016 16:46:08 +0200 (CEST)
Date: Sat, 30 Jul 2016 16:46:07 +0200
From: Gert Doering <gert@space.net>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20160730144607.GE79185@Space.Net>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com> <E6C349E8-D745-4DF5-A734-2682685EE8D4@gmail.com> <87vazo5e3a.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87vazo5e3a.wl-jch@pps.univ-paris-diderot.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/rF48gfo2UHihRKhOzVlvZsHI3dg>
Cc: Rich Brown <richb.hanover@gmail.com>, homenet@ietf.org
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jul 2016 14:46:13 -0000

Hi,

On Fri, Jul 29, 2016 at 11:28:09PM +0200, Juliusz Chroboczek wrote:
>  - you can extend your wireless range by just connecting an extra router.
>    As the network expands, the routers will automatically compute the best
>    paths and route packets accordingly;
[..]
> The Commission for Truth in Advertising requires me to mention that the
> last feature is not quite ready yet -- with current software, when one
> provider goes down, you might need to manually disable the router that's
> connected to that provider.

The Commission for Truth in Advertising also remarks that the "just
expand your wireless range by hooking up additional routers" is not working
very nicely with (wifi-)roaming clients yet, as the clients today seem
to have funny ideas about TCP sessions and new v6 addresses when changing
AP...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Sat Jul 30 08:29:29 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C721B12D630 for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 08:29:28 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 f7gsyTFSDh31 for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 08:29:27 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAE9012B01E for <homenet@ietf.org>; Sat, 30 Jul 2016 08:29:26 -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/56228) with ESMTP id u6UFTOoU007479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Jul 2016 17:29:24 +0200
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/56228) with ESMTP id u6UFTNau008149; Sat, 30 Jul 2016 17:29:23 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E1F5961F9A; Sat, 30 Jul 2016 17:29:23 +0200 (CEST)
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 ZgvzQdeScryI; Sat, 30 Jul 2016 17:29:22 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id CD4D661FA1; Sat, 30 Jul 2016 17:29:21 +0200 (CEST)
Date: Sat, 30 Jul 2016 17:29:22 +0200
Message-ID: <87lh0jjga5.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Gert Doering <gert@space.net>
In-Reply-To: <20160730144607.GE79185@Space.Net>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com> <E6C349E8-D745-4DF5-A734-2682685EE8D4@gmail.com> <87vazo5e3a.wl-jch@pps.univ-paris-diderot.fr> <20160730144607.GE79185@Space.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]); Sat, 30 Jul 2016 17:29:24 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 30 Jul 2016 17:29:24 +0200 (CEST)
X-Miltered: at korolev with ID 579CC7D4.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 579CC7D3.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579CC7D4.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: 579CC7D3.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 : 579CC7D4.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 579CC7D3.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: <https://mailarchive.ietf.org/arch/msg/homenet/eUmMh8wf6xQqpxwIu6uQTPHvDIw>
Cc: Rich Brown <richb.hanover@gmail.com>, homenet@ietf.org
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jul 2016 15:29:29 -0000

>> The Commission for Truth in Advertising requires me to mention that the
>> last feature is not quite ready yet -- with current software, when one
>> provider goes down, you might need to manually disable the router that's
>> connected to that provider.

> The Commission for Truth in Advertising also remarks that the "just
> expand your wireless range by hooking up additional routers" is not working
> very nicely with (wifi-)roaming clients yet, as the clients today seem
> to have funny ideas about TCP sessions and new v6 addresses when changing
> AP...

The Commission for Truth in Advertising has been doing some excellent work
of late.

-- Juliusz


From nobody Sat Jul 30 09:54:22 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D48512B064 for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 09:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DnZL5L7eKApE for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 09:54:20 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAD6B12B009 for <homenet@ietf.org>; Sat, 30 Jul 2016 09:54:19 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id x1so114596961qkb.3 for <homenet@ietf.org>; Sat, 30 Jul 2016 09:54:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=vp0d60j35hq+7HZuuvpkMQnPRJLf1XhB2OmE+0U2kds=; b=wlwTUdAGcwi1sDiPkqjUs8IGcjdt9eSOnBCwgCMc4a/bnr1U/ggJj72kuoiFLOGOz6 nOXrZFnH0Ytp4sdZ6J5y4fRPRyrJ0IbZ5jBu8JXtnMWRA/GDnHMT+QBdN+88rewnWrli LXaOm0yXtqcFuec1qbETAvTDe6wd9luJa52+2aBWbSvoPV3TA4vnbR324RCiLWrvk9KD ZXIsCZhd9d9OKzs3mnlEFUxbu+vdkK3s1RKAtfJbpxCOcksZUcaPtnbjWKd44xAFwG3d p7ubvCI7Ls359scAl6gWX95LtKVXAAjebRkchUNcmir1QuBz1T0oiWewv28yCTVWSsfd kzwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=vp0d60j35hq+7HZuuvpkMQnPRJLf1XhB2OmE+0U2kds=; b=TiGxUcKeaz00sWN+OJS12ybzWI73cKEVuyl1xtX0K9C7UsZHe8LTmU2VWyQiet7PbW C0DACHm+eHF9ID4bW2WIzTeF3RgwTWBCVw716538MOfPgY/FJcIdOlBpgC/lxaFvwxT4 A8yGA8tOlKS//XWF7IaDFC8yN+++iyuoRm2uAgppzpGkspfpabb5QaS7MKB0h2OIbOCE 0uct81J8E0I5L/qhaZDrwUalQj1X36YYcaptl3UoFJ1S7/umNnstMmzFYHnKpNE7MnO+ 9iLQlunya/4/O8wvb5Gc3R+tQHOIHuxHumifCGTGX4tThzJLUXCQqdKZEaxY5mYsVPx/ lJmA==
X-Gm-Message-State: AEkoout9c0jbykGTFeiYae6AdiZsyet1REewFEwD2BKoudHLq88zApetA8hSY7HS1rJlig==
X-Received: by 10.55.106.195 with SMTP id f186mr55709136qkc.52.1469897658969;  Sat, 30 Jul 2016 09:54:18 -0700 (PDT)
Received: from richs-mbp-4673.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id 55sm13010526qtp.32.2016.07.30.09.54.17 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 30 Jul 2016 09:54:17 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <878twk6wg2.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 30 Jul 2016 12:54:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <680D9D67-DC77-4B9F-AEA6-3A3F756DB6C6@gmail.com>
References: <F5181AD3-DC1B-4AD7-B42E-C24CE1879056@gmail.com> <87eg6ksnoj.wl-jch@pps.univ-paris-diderot.fr> <A4FCAF74-5296-4B2A-B869-95C95F7DE3B1@gmail.com> <87eg6fqr6y.wl-jch@pps.univ-paris-diderot.fr> <C25934D4-C54D-47AA-AB9F-9A64770AF3D0@gmail.com> <87fuqsaebf.wl-jch@pps.univ-paris-diderot.fr> <3A70AFE4-0505-4A55-87B0-ECDDE9E5920B@gmail.com> <878twk6wg2.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, homenet@ietf.org
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/JzD1Twk3_XZU1DZJrowH1qg3xbQ>
Subject: Re: [homenet] "Installing Homenet" guide (was: hnet-full & LEDE bug report)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jul 2016 16:54:21 -0000

> On Jul 29, 2016, at 4:06 PM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>>>> I think you mean E1 - that's what the instructions use for the wide =
area
>>>> interface.
>>>=20
>>> It looks like one of us is confused.
>=20
>> It looks like it was me. :-)
>=20
> Why not rename the interfaces to "internal" and "external"?

Or, follow the pattern of the W24 and W5 interface names, and use EINT =
and EEXT
Or W-24, W-5, E-INT, E-EXT
Or an "h" prefix, for homenet: hW24, hW5, hInternal, hExternal
Or, because names seem to be converted to uppercase, use a "H-" prefix: =
H-24, H-W5, H-Internal, H-External
I'm not in love with any of these: they all kind of hurt my eyes. But I =
will try one variation in my next draft.

>> This is a corollary of your assertion at IETF the other day ("if =
it=E2=80=99s
>> not implemented, it didn=E2=80=99t happen")
>=20
> The next slide said "If it's deployed, it did happen".  With HNCP, =
we're
> in the gray area between the two.

If a package is available in the woods, but nobody tries it out, does it =
make a sound? (That's one of my motivations for this new guide - to =
broaden the test base.)

>> <rant> That OpenWrt page is a primary example of the style of
>> documentation I abhor.
>=20
> Please speak to the LEDE guys.  Have a chat with "jow" and =
"HentaiMonster"
> on Freenode, either on #openwrt or on #lede-dev.  "Nbd" is also =
extremely
> competent, but he's more difficult to catch.

I have permissions edit the OpenWrt wiki. However, I have never taken =
the time to become sufficiently knowledgeable on the subject to feel =
comfortable that my rewriting would improve its quality. (Thus far - =
touch wood - I have successfully avoided needing to know about failsafe =
booting...)

>> I have added sysupgrade to the Backup procedure. But I like to =
recommend
>> the LuCI GUI...
>=20
> De gustibus non disputandum.  That's Latin for "you're wrong and I'm =
right" ;-)

:-)

re: my dry description of homenet.=20

I agree - it's dry. I was hoping to trick someone on the list into =
blurting out something memorable (sometimes it works :-)=20

I'll draft a 30-second "elevator pitch" about homenet and post it to the =
list. It'll definitely include:
	- no/minimal configuration;=20
	- naming;=20
	- some use cases (repeating wireless).=20
	- oh, and IPv6.=20
	- Anything else?

Thanks again.

Rich=


From nobody Sat Jul 30 12:50:06 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F248412D0CD for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 12:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6dlz_biW_j71 for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 12:50:03 -0700 (PDT)
Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480A2128E19 for <homenet@ietf.org>; Sat, 30 Jul 2016 12:50:03 -0700 (PDT)
Received: by mail-qk0-x244.google.com with SMTP id q62so9281259qkf.2 for <homenet@ietf.org>; Sat, 30 Jul 2016 12:50:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=zJD2EUlF0s1TX23efh4QElexTWfCm3H7rFVDnsbWElA=; b=SUqyDt1CGNo3RR1cUQguQqaHk9yE5QBPpcZeVvDw9c+L7BSr656pOpgpcYhKBMMQlN 7Z01Y41FCggBr4pLB3m0d3X05frFNgAqnhH1tfR/9jimuzkvbKN1MEmL8cO5hG1KOzbA ygwAz3hXIY4opIlRavkIzWd65pcMS0LAJqaYZI1+m++5DyM6D1B/k/HQ5UkEJgoRY7gR 6wajj9/4ZZUnbpbt6PyBvoDAbO+Wab1i3Ua7r96s2OOIkgRh7kyOwq8JQhAUcoL5A12c JJOnkLp6usOIF2KT5Ox+2FF2um5lNQk2ot0XaNMkn0mI3RTxqV3gJRaoFmKyYNxo3UvN PeDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=zJD2EUlF0s1TX23efh4QElexTWfCm3H7rFVDnsbWElA=; b=mb1ONMFEjwWRJPTt/PSXqrVgtw7PdU+z4n93L03R+/1FXJ3g7bDxk3dkWcmu5/V9eS m1oakUPKr5v/SU4xrutTzUjrEVxXGZOKhA2czUlvvkNqrVcMTSudvBtbUmKzYfHv9fk9 HmX5lMJwr6GuEZAHAizinDSHh4Hyx0qiajZPXhngNkFk1sJ5A7ePo3ob6PZvbpg//00b BqQmh3LMI3UYkrwOFnda6fPtANoi+W/q86dvkbX5I30qNpMeeVDmBgSNNhQz1wfF9Zus WxrIeFbLbr1yxUVZ86A4/kf3Iq7fr4WwBnLy3hZPIWBYc+kaz9kSBreLqWWlI5qFL+Yq h07g==
X-Gm-Message-State: AEkoousTxhWUF6XU7hi3FlPrqlkWbgYFUX2lfdBFDuPLaAt5RivObL6SkCNs/C29Tu74uw==
X-Received: by 10.55.79.146 with SMTP id d140mr142607qkb.43.1469908202199; Sat, 30 Jul 2016 12:50:02 -0700 (PDT)
Received: from richs-mbp-4673.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id r5sm6066886qkf.34.2016.07.30.12.50.00 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 30 Jul 2016 12:50:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 30 Jul 2016 15:49:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CDD35AD-1CB4-4786-814E-2D29C0C6DA1B@gmail.com>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com> <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr>
To: homenet@ietf.org
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/utIFut8ArhfT1yQ9lzkmygX398s>
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jul 2016 19:50:05 -0000

It's still not working, but I have a new clue... Here's the experimental =
setup:

- Install LEDE r1141 (28Jul2016 version) with current hnet-full =
2016-06-28-606dye9046..e-1

- Config hnet on W24, W5 & E0 (but not LAN Ethernet) as described in =
Steps 1-9 of the Guide =
https://gist.github.com/richb-hanover/ec88b851c4da074e48003e6fe9276901

- Everything looks fine. I can connect to W24 & W5, ping external =
addresses, connect to https://lede-witi.home and ssh root@lede-witi.home

Then do step 10, disabling 'lan' interface and creating E1. The pastebin =
at http://pastebin.com/Aj6BGf79 shows the state of the config files =
before issuing /etc/init.d/network restart

I have a serial console attached, and it shows the lines at the end of =
this message.=20

After restarting the network, neither the LAN ethernet, nor the W24/W5 =
ports work (no DHCP on E1, my Macbook refuses to connect to either W24 =
or W5...)

I suspect it has something to do with the "disabling br-lan" messages, =
but I don't know where that config comes from. (I searched all files in =
/etc, and there is no occurrence of 'br-lan')

What other information could I provide? Thanks.

Rich

--- Serial console after /etc/init.d/network restart shows:

[  995.350000] br-lan: port 1(eth0.1) entered disabled state
[  995.380000] device eth0.1 left promiscuous mode
[  995.390000] br-lan: port 1(eth0.1) entered disabled state
[  995.420000] device eth0 left promiscuous mode
[  995.440000] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[  998.110000] device eth0 entered promiscuous mode
[  999.340000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  999.660000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 1000.070000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1000.740000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready


From nobody Sat Jul 30 14:45:19 2016
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F140312D0FC for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 14:45:17 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 qgIrSGYcgqZZ for <homenet@ietfa.amsl.com>; Sat, 30 Jul 2016 14:45:16 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61CB412B012 for <homenet@ietf.org>; Sat, 30 Jul 2016 14:45:16 -0700 (PDT)
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/56228) with ESMTP id u6ULjDBM003375; Sat, 30 Jul 2016 23:45:13 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id EB07B61F9D; Sat, 30 Jul 2016 23:45:13 +0200 (CEST)
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 yWu9LL8l1L9a; Sat, 30 Jul 2016 23:45:12 +0200 (CEST)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 9D15361F9A; Sat, 30 Jul 2016 23:45:11 +0200 (CEST)
Date: Sat, 30 Jul 2016 23:45:12 +0200
Message-ID: <8737mqkdg7.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <5CDD35AD-1CB4-4786-814E-2D29C0C6DA1B@gmail.com>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com> <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr> <5CDD35AD-1CB4-4786-814E-2D29C0C6DA1B@gmail.com>
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 [194.254.61.138]); Sat, 30 Jul 2016 23:45:14 +0200 (CEST)
X-Miltered: at korolev with ID 579D1FE9.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 579D1FE9.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 : 579D1FE9.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: <https://mailarchive.ietf.org/arch/msg/homenet/JR200vpzXvc1UyNtdlhmoYYmlHY>
Cc: homenet@ietf.org
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jul 2016 21:45:18 -0000

> I suspect it has something to do with the "disabling br-lan" messages,
> but I don't know where that config comes from.

No, that's just that as you change the configuration, the software bridge
is being removed.  What you're seeing are STP state transitions.

Can you please paste a full boot log with the new configuration?

-- Juliusz


From nobody Sun Jul 31 12:49:16 2016
Return-Path: <richb.hanover@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A37112B017 for <homenet@ietfa.amsl.com>; Sun, 31 Jul 2016 12:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AUHEcoTaZJCY for <homenet@ietfa.amsl.com>; Sun, 31 Jul 2016 12:49:13 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7338128B44 for <homenet@ietf.org>; Sun, 31 Jul 2016 12:49:13 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id s63so130187752qkb.2 for <homenet@ietf.org>; Sun, 31 Jul 2016 12:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MqHtb5oTl7uFYqfC+E7ncHjer1TuxiLhaIIX/4NCwWM=; b=RZZbWT68W4twJPrbBe3qp1xJfBZX4YyKDWKMvRMykBordxfBzmEn16H7QqCeuPTht5 +YCTiW8WSieIXLPlZjSx4n7zmBfHMYJ1pENyk0p33/caRIWEj5BKEsObp8ugwbIMDwNY 1faDyh58Ly3bqRGjaw/xypAKT3xir2NYQJRzHoNTjlIIoiLiViYG4cTg4CjD7rJKNicx YGL0mdM7uRKAFl4ZI9ME4q3SglxMyr7TmFWeYLsCzIqM093xxgOFvOP0UVbYhAkCES8d uZK/a9tEQWV66G8q6Xa4u79Z51zwphcv/+GeKMmkUzc/r39c6ulpSyp2o31xkta9mATu /eIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MqHtb5oTl7uFYqfC+E7ncHjer1TuxiLhaIIX/4NCwWM=; b=fr4lG3UolMksmdgtsy9F3tRETWT7cvArwNf1ZvB5RpQLjbCh8AEuQsHCaR2n1lIK8c 5HpOuzxk8MnWcySV50GGpYjJnCA0OA+QEW10M6R4H6yqKzGmjfMb+pyys8mDbnji5P6x dYzVZyRjZCltSKuNqK87a8l2023TXdCrHOBhP+8NLEWHMPU1bN3jg4zCZ8NnTu1mM9rT bw4wL9KDliMM3c+z31PiigQcF2CxZNKYFbGcX1mPHvvNyuNFaKdtjNjFbx4J4tt4gaKu ljcNOjtDTp7cbiPhvKX+Gb1JQSkLencyQUYQ41SaUoWLGtTdY7uZBcc8oX0xDoNwup6h 77LA==
X-Gm-Message-State: AEkoouus5vItzO/8IoZOb2ZAQETz9Dt+psCOadb/HExCmPF8QLoRUioCJ/R+wi+rg/+vHQ==
X-Received: by 10.55.68.81 with SMTP id r78mr64588947qka.129.1469994552768; Sun, 31 Jul 2016 12:49:12 -0700 (PDT)
Received: from richs-mbp-4673.lan (pool-70-16-107-9.port.east.myfairpoint.net. [70.16.107.9]) by smtp.gmail.com with ESMTPSA id 23sm15712362qki.1.2016.07.31.12.49.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 31 Jul 2016 12:49:12 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Rich Brown <richb.hanover@gmail.com>
In-Reply-To: <8737mqkdg7.wl-jch@pps.univ-paris-diderot.fr>
Date: Sun, 31 Jul 2016 15:49:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FC10D09-3DC1-415C-9B06-C8308FEBF698@gmail.com>
References: <D22120A0-5081-4F6E-8ECD-35F8AE95F7D5@gmail.com> <87k2g4afo2.wl-jch@pps.univ-paris-diderot.fr> <5CDD35AD-1CB4-4786-814E-2D29C0C6DA1B@gmail.com> <8737mqkdg7.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/4vjKaG5l6EXUm34ZJw0y9QKxids>
Cc: homenet@ietf.org
Subject: Re: [homenet] Trouble with hnet-full on WiTi Router from mqmaker
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 31 Jul 2016 19:49:15 -0000

> On Jul 30, 2016, at 5:45 PM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>> I suspect it has something to do with the "disabling br-lan" =
messages,
>> but I don't know where that config comes from.
>=20
> No, that's just that as you change the configuration, the software =
bridge
> is being removed.  What you're seeing are STP state transitions.
>=20
> Can you please paste a full boot log with the new configuration?

I added it to: http://pastebin.com/Aj6BGf79

Thanks.

Rich=

