
From nobody Wed May  4 08:12:39 2016
Return-Path: <cbowers@juniper.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 97EDF12D713; Wed,  4 May 2016 08:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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=junipernetworks.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 biZcV6LSuhjr; Wed,  4 May 2016 08:12:29 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0102.outbound.protection.outlook.com [65.55.169.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C39C12D714; Wed,  4 May 2016 08:11:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=w7ie00ptq+2hUMZ9UCV/oDV2oKA1ovdUmKLWn7n5raU=; b=gNSw6/xthvUsZRIzXoecB31GyhJEd5X+wq2CV8K7lP2Nw9huNwC1GRZA8VmwoVz6dHrvPPXs8TOX/MHauW4ZaySIh/AStjBr/Kz/5cAwhGAzKChXYzNf8WKXW8jHZs3yT/HE7IaSK7xFy7wVcPYDirHJZH9pOoDkqJRd8oNk6/4=
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com (10.160.35.143) by BLUPR0501MB1043.namprd05.prod.outlook.com (10.160.35.142) with Microsoft SMTP Server (TLS) id 15.1.477.8; Wed, 4 May 2016 15:10:58 +0000
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) by BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) with mapi id 15.01.0477.016; Wed, 4 May 2016 15:10:58 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Thread-Topic: RTGWG Virtual Interim Meeting: May 31, 2016
Thread-Index: AdGlkFH1140hKmcyTVCsepgcooS0Tw==
Date: Wed, 4 May 2016 15:10:58 +0000
Message-ID: <BLUPR0501MB104486BB670240E97CD18976A97B0@BLUPR0501MB1044.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.239.11]
x-ms-office365-filtering-correlation-id: 8cc861f5-964e-4640-37d9-08d3742e4c3b
x-microsoft-exchange-diagnostics: 1; BLUPR0501MB1043; 5:CitYsA2hzdNmJAdwkSrAbXXA/NLZEaM/KCdoPH5iG4QEhtSjRXcd818zmReb6J7wOEl5NGwF2oM2RBl037DF8Ll0gESF9K3JvObglTTmWMvMwtWr2/Lg0ZX4EsA1IaBhNgxSBiwByNB9uyD1puyvTg==; 24:oBzdpuZlsaHSujzxPwkIdjcE27S+u1/rlAH3puQM4Ccf9SuF7VrS9AhJ68e9wxYZOwNqjjCKX2CFrOTRRjb43KbMAZcu0d/V5JF/iJXZQqM=; 7:LNZuBFVWAA2PMJiTzKeMQAYc1WALI2pfmyb7dQ954qZEDBxSlAeFGbTPODZAJKr82VD1GO0mFpoUO5Y9wN385n8er12yXu8vVBs7/jCqOr0MLoj9zpV6yT+gp/snX3ibhl31v4SogLBsuCTDARTtpNx06255LHrcmXD2TbzFMXB3N67HWXsii7OnPuX3Na+3
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB1043;
x-microsoft-antispam-prvs: <BLUPR0501MB104335A96BE36AFF63D4EDD9A97B0@BLUPR0501MB1043.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521098)(9101528026)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:BLUPR0501MB1043; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0501MB1043; 
x-forefront-prvs: 093290AD39
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(243025005)(377454003)(9686002)(77096005)(551544002)(3846002)(102836003)(50986999)(6116002)(74316001)(81166005)(4326007)(11100500001)(229853001)(5002640100001)(87936001)(1220700001)(10400500002)(5003600100002)(8936002)(5008740100001)(15975445007)(3480700004)(122556002)(92566002)(76576001)(16799955002)(86362001)(2201001)(2900100001)(2906002)(450100001)(19580395003)(2501003)(586003)(99286002)(3660700001)(19580405001)(5004730100002)(5001770100001)(3280700002)(33656002)(189998001)(66066001)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0501MB1043; H:BLUPR0501MB1044.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 May 2016 15:10:58.4232 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB1043
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HHxKvbmofx8rN1jRZ7veLl-J21g>
Cc: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtgwg-ads@ietf.org" <rtgwg-ads@ietf.org>
Subject: [homenet] RTGWG Virtual Interim Meeting: May 31, 2016
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, 04 May 2016 15:12:35 -0000

RTGWG,=20

RTGWG will hold a virtual interim meeting on Tuesday May 31, 2016 from=20
10:00-12:00 Eastern Daylight Time (14:00-16:00 UTC).=20

The virtual interim will focus on the problem of ipv6 multi-homing with=20
provider-assigned addressing without NAT, and a proposed solution for=20
this problem, destination/source routing.=20

We have contacted several potential presenters based on the discussion=20
of this topic in Buenos Aires and on the RTGWG list and in v6ops. If you=20
are interested in presenting at this virtual interim and we have not=20
already contacted you, please contact us at rtgwg-chairs@ietf.org. We=20
are particularly interested in hearing from enterprises and service=20
providers, who are the ones affected by this problem and would need to=20
deploy and operate any solution we come up with.=20

A detailed agenda will be posted to the rtgwg mailing list at least a=20
week before the meeting.

This initial announcement is being posted to rtgwg, v6ops, homenet,=20
6man, and routing-discussion mailing lists. We only plan to post=20
follow-up email related to this virtual interim to the rtgwg list, so=20
please subscribe to the rtgwg mailing list if you are interested in=20
following this.

The WebEx details are as follows:

RTGWG Virtual Interim Meeting=20
Tuesday, May 31, 2016=20
10:00 am  |  Eastern Daylight Time (New York, GMT-04:00)  |  2 hrs=20

Meeting link:
https://ietf.webex.com/ietf/j.php?MTID=3Dma9394d256b2331260bd5416dc08fb5bd

Meeting number: 648 728 108=20
Meeting password:interim1

Join by phone (US/Canada): 1-650-479-3208

International dial-in (PDF):=20
<http://www.webex.com/pdf/tollfree_restrictions.pdf>

Thanks,
Chris and Jeff


From nobody Thu May  5 05:00:52 2016
Return-Path: <tjc@ecs.soton.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 B8AA212D1BC for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 05:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.516
X-Spam-Level: 
X-Spam-Status: No, score=-4.516 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_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 Hn-yvTgx1zpR for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 05:00:47 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0AF12D193 for <homenet@ietf.org>; Thu,  5 May 2016 05:00:44 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u45C0Up8029093; Thu, 5 May 2016 13:00:30 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u45C0Up8029093
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1462449630; bh=ZVt4jlm/07rAGknqbroNtBEa60I=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=wgfXRx1kW9jTng6sn0TWdtCKQJWefTGAJOG+glvIfv2W6WFYhNUEJEt3RGQJ++2bc n0R/iXUQgrexolDIyVor3kecWKSt9lRqo6OdHusFsJHD9G0KGcfVkjp1CqND548YOO 8K+2IU3vE+VxwVZkeOik1C9RJZVzin6IkMWGtIDI=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s44D0U2391104686Jl ret-id none; Thu, 05 May 2016 13:00:30 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:5d16:8598:2c35:8495] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u45C0KaG020553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 May 2016 13:00:20 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_F028E08E-3236-48CC-A6F8-FDED1688F63D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com>
Date: Thu, 5 May 2016 13:00:20 +0100
Message-ID: <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s44D0U239110468600; tid=s44D0U2391104686Jl; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u45C0Up8029093
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vFdiswZyhQdd03q5QdOWGDiFF4c>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 05 May 2016 12:00:51 -0000

--Apple-Mail=_F028E08E-3236-48CC-A6F8-FDED1688F63D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 25 Apr 2016, at 03:39, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Sun, Apr 24, 2016 at 12:29 PM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr <mailto:jch@pps.univ-paris-diderot.fr>> =
wrote:
> > Juliusz, the problem is that existing home network devices that do
> > DNS-based service discovery do not support DNS update. They could, =
but
> > they don't, because we didn't define an easy way for them to do it.
>=20
> I'd be grateful if you could expand on that.  Why can't we define a =
way
> for clients to do DDNS?
>=20
> We can and should.   The problem is that we won't see that code ship =
in new devices anytime soon, so we still have to make mDNS work.

And this is why the dnssd WG is focused on making mDNS work on =
multi-subnet networks.

But Ted has raised the question of DNS Update there, and we agreed in BA =
that we=E2=80=99d accept a draft on issues around coexistence of mDNS =
and DNS Update.

> > Just 2136 isn't enfough, because there's no authentication scheme,
>=20
> I don't understand this argument.  How is non-secured DDNS any less =
secure
> than mDNS?  What am I missing?
>=20
> This is an implementation issue, not a security issue--sorry for not =
making that clear.   In order to preserve the same security =
characteristics that mDNS has, we have to ensure that the update =
actually originated on the local link, which requires a different sort =
of listener than is present in a typical DNS server.   And existing DNS =
servers typically don't have any way to support unauthenticated updates =
on a first-come, first-served basis, so if you allow unauthenticated =
updates, you don't have any way to avoid collisions.   Otherwise you are =
correct.   The answer is to write a document that describes how to do =
that, and if you read the homenet naming arch document, you can see that =
I actually sketched out a solution there, which I expect to go in a =
different document, likely in a different working group.

There are many worms in that can :)

> Oh, sure, we Poles are not quite as pessimistic as the Finns.  I'm
> actually of a divided mind here -- I rather like distributed solutions
> (hence prefer mDNS to DDNS) but dislike proxying.  Part of me just =
wishes
> we'd mandate site-local multicast and do mDNS over that
>=20
> The problem with site-local multicast for mDNS is that multicast isn't =
a great solution even on the local wire when that wire is wireless.    =
And, you have to do modify the client anyway.

Indeed; this was discussed early on in the dnssd WG, and not considered =
for those reasons.=20

> Furthermore, if you consider the mdns hybrid proxy stateless, then you =
can have a DNS server that is roughly that stateless too.   I think it =
provides better service continuity if you are willing to retain some =
state, but everything will still work even if you don't, just as the =
hybrid proxy does.

Agreed.

Tim

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


--Apple-Mail=_F028E08E-3236-48CC-A6F8-FDED1688F63D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
25 Apr 2016, at 03:39, 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""><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Sun, =
Apr 24, 2016 at 12:29 PM, Juliusz Chroboczek <span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" =
target=3D"_blank" class=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:1px #ccc solid;padding-left:1ex"><span =
class=3D"">&gt; Juliusz, the problem is that existing home network =
devices that do<br class=3D"">
&gt; DNS-based service discovery do not support DNS update. They could, =
but<br class=3D"">
&gt; they don't, because we didn't define an easy way for them to do =
it.<br class=3D"">
<br class=3D"">
</span>I'd be grateful if you could expand on that.&nbsp; Why can't we =
define a way<br class=3D"">
for clients to do DDNS?</blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">We can and should. &nbsp; The problem =
is that we won't see that code ship in new devices anytime soon, so we =
still have to make mDNS =
work.</div></div></div></div></div></blockquote><div><br =
class=3D""></div>And this is why the dnssd WG is focused on making mDNS =
work on multi-subnet networks.</div><div><br class=3D""></div><div>But =
Ted has raised the question of DNS Update there, and we agreed in BA =
that we=E2=80=99d accept a draft on issues around coexistence of mDNS =
and DNS Update.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; Just 2136 =
isn't enfough, because there's no authentication scheme,<br class=3D"">
<br class=3D"">
I don't understand this argument.&nbsp; How is non-secured DDNS any less =
secure<br class=3D"">
than mDNS?&nbsp; What am I missing?<br class=3D""></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">This is an =
implementation issue, not a security issue--sorry for not making that =
clear. &nbsp; In order to preserve the same security characteristics =
that mDNS has, we have to ensure that the update actually originated on =
the local link, which requires a different sort of listener than is =
present in a typical DNS server. &nbsp; And existing DNS servers =
typically don't have any way to support unauthenticated updates on a =
first-come, first-served basis, so if you allow unauthenticated updates, =
you don't have any way to avoid collisions. &nbsp; Otherwise you are =
correct. &nbsp; The answer is to write a document that describes how to =
do that, and if you read the homenet naming arch document, you can see =
that I actually sketched out a solution there, which I expect to go in a =
different document, likely in a different working =
group.</div></div></div></div></blockquote><div><br class=3D""></div>There=
 are many worms in that can :)<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Oh, sure, we Poles are not quite as pessimistic =
as the Finns.&nbsp; I'm<br class=3D"">
actually of a divided mind here -- I rather like distributed =
solutions<br class=3D"">
(hence prefer mDNS to DDNS) but dislike proxying.&nbsp; Part of me just =
wishes<br class=3D"">
we'd mandate site-local multicast and do mDNS over that</blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">The problem with =
site-local multicast for mDNS is that multicast isn't a great solution =
even on the local wire when that wire is wireless. &nbsp; &nbsp;And, you =
have to do modify the client =
anyway.</div></div></div></div></blockquote><div><br =
class=3D""></div>Indeed; this was discussed early on in the dnssd WG, =
and not considered for those reasons.&nbsp;</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div =
class=3D"">Furthermore, if you consider the mdns hybrid proxy stateless, =
then you can have a DNS server that is roughly that stateless too. =
&nbsp; I think it provides better service continuity if you are willing =
to retain some state, but everything will still work even if you don't, =
just as the hybrid proxy =
does.</div></div></div></div></blockquote><div><br =
class=3D""></div><div>Agreed.</div><div><br =
class=3D""></div>Tim</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><br =
class=3D""></div></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=_F028E08E-3236-48CC-A6F8-FDED1688F63D--


From nobody Thu May  5 05:37:36 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 3C4D312D586 for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 05:37:34 -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 SEiCr6GovIsd for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 05:37:32 -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 E3DF112D57C for <homenet@ietf.org>; Thu,  5 May 2016 05:37:31 -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 u45CbSlP030047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 May 2016 14:37:29 +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 u45CbRaD032464; Thu, 5 May 2016 14:37:27 +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 6AE0E61FF2; Thu,  5 May 2016 14:37:27 +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 KTtHCYbehSh7; Thu,  5 May 2016 14:37:25 +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 2CCF461FF7; Thu,  5 May 2016 14:37:24 +0200 (CEST)
Date: Thu, 05 May 2016 14:37:26 +0200
Message-ID: <87mvo4n0jd.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.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 [IPv6:2001:660:3301:8000::1:2]); Thu, 05 May 2016 14:37:29 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 05 May 2016 14:37:28 +0200 (CEST)
X-Miltered: at korolev with ID 572B3E88.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 572B3E87.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 572B3E88.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 572B3E87.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 : 572B3E88.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 572B3E87.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1pAnDSuEb1Bqv2FOnndY3n4-iv8>
Cc: homenet@ietf.org, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 05 May 2016 12:37:34 -0000

>> We can and should.  The problem is that we won't see that code ship in
>> new devices anytime soon, so we still have to make mDNS work.

> And this is why the dnssd WG is focused on making mDNS work on
> multi-subnet networks.

Is there something I can read on this particular subject?

-- Juliusz


From nobody Thu May  5 06:57:12 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 31BCC12D8E7 for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 06:57:11 -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_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 (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 TVKfrzbEhL0Q for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 06:57:08 -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 EB36112D81A for <homenet@ietf.org>; Thu,  5 May 2016 06:54:33 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lrp0010.outbound.protection.outlook.com [213.199.154.10]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-13-dLgJ9qjfTk6dGbPbHrq3qQ-1; Thu, 05 May 2016 14:54:26 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=fEfbKzD1peR28k10HXOrA9rHbmA/ayKnz8wK7nhff8w=; b=CsbNIqkfCpqwUyvOUEWk9Ci6ceg9qpNV3o3eY1CY2PMjwJwZfrv7QJRFOT71PFFrX2lN1s30vELRFy2goiz4UuHEkRojWLdCNwoVNqdNi2C8MkSWll+u8EfSHlvvgXLA1/LAi5kkpIQmkZoBcGci708j1zV2mx/e1E2kf35StaU=
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.485.9; Thu, 5 May 2016 13:54:23 +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.0485.011; Thu, 5 May 2016 13:54:23 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] Updating DNS [was: How many people have installed the homenet code?]
Thread-Index: AQHRpsXbmA7UhtPWP02AZdWH+hpp/p+Z6dOAgBBUBQCAAApeAIAAFX8A
Date: Thu, 5 May 2016 13:54:23 +0000
Message-ID: <7DAA0940-5F80-4974-BD06-0DADA8CCF41A@jisc.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <87mvo4n0jd.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87mvo4n0jd.wl-jch@pps.univ-paris-diderot.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:a88:d510:1101:5d16:8598:2c35:8495]
x-ms-office365-filtering-correlation-id: 5a2a84bc-58d1-4dad-a21d-08d374ecc3d1
x-microsoft-exchange-diagnostics: 1; AMSPR07MB455; 5:Xx+YuLNPpA+snneA4SFfcICsMynqbMRyorgsMaRAeISIE3W/U5aXJAE4YxPiBiYFzuDzl4qDcpmGyyr6mXKT1l/+Rm+L9eWIsCsHa5/ujvNnnDPhG5eC3QZ+LTU5GVsCuii++g+6L1hLF6Mv+rF/RA==; 24:ayorXeLBAaxv8L09g+zNmG7xSd3zXq/sKSEIRfb9zjD4fxEoUeBdS7VCFv1qh0hL6FXq9ExNp2jOSdo82BaCprHP8xay86VNDvJZYwTcraY=; 7:bgKmi/hVtpE4Q7r6dPKNoydF3ZVOsWibAjgxEITtSgFvWYGH7sY6HIUH1kw7cbgWx0hDTTKP6O37ELoJ431anZLoJSc3yvHc+rqY0Q4BWwrQfSPLb30pIVnTzZW1zHkH9TDaPKAdydFDnBJrv3nQ3Fu8H0m0xvp/KPq5my/szWLJPTzf7DJfHHJu8GXJN7np; 20:M6rM5dv8T94vAKoHwbZS99b7zr5FDBf6b+9CMbybwNQog6PDaN3NLWeznIujjvzlW8FJnrQjmPI7TlS1dJ2WODdtvpu3jD1v6ZWtVqGh5wvwQNLfuAdmYUCBXo2dxoR7YGdr2E+vcNueV9lQJxyVgPz8k4P1e/jE61OrZkOE8Dk=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB455;
x-microsoft-antispam-prvs: <AMSPR07MB4551DB196C7A46D02E01A46D67C0@AMSPR07MB455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521098)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AMSPR07MB455; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB455; 
x-forefront-prvs: 0933E9FD8D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(93886004)(586003)(87936001)(36756003)(1220700001)(76176999)(50226002)(2900100001)(102836003)(50986999)(86362001)(83716003)(6116002)(3660700001)(8936002)(2906002)(81166005)(10400500002)(15975445007)(19580405001)(19580395003)(3280700002)(74482002)(106116001)(189998001)(77096005)(33656002)(5008740100001)(2950100001)(92566002)(11100500001)(5002640100001)(4326007)(122556002)(5004730100002)(82746002)(110136002)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB455; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-ID: <03188A3939BC934384963309B48A8409@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 May 2016 13:54:23.4521 (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: dLgJ9qjfTk6dGbPbHrq3qQ-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DFtRAh0QB4vMZ-um1GZ-F2j4Ccc>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 05 May 2016 13:57:11 -0000

SGksDQoNCj4gT24gNSBNYXkgMjAxNiwgYXQgMTM6MzcsIEp1bGl1c3ogQ2hyb2JvY3playA8amNo
QHBwcy51bml2LXBhcmlzLWRpZGVyb3QuZnI+IHdyb3RlOg0KPiANCj4+PiBXZSBjYW4gYW5kIHNo
b3VsZC4gIFRoZSBwcm9ibGVtIGlzIHRoYXQgd2Ugd29uJ3Qgc2VlIHRoYXQgY29kZSBzaGlwIGlu
DQo+Pj4gbmV3IGRldmljZXMgYW55dGltZSBzb29uLCBzbyB3ZSBzdGlsbCBoYXZlIHRvIG1ha2Ug
bUROUyB3b3JrLg0KPiANCj4+IEFuZCB0aGlzIGlzIHdoeSB0aGUgZG5zc2QgV0cgaXMgZm9jdXNl
ZCBvbiBtYWtpbmcgbUROUyB3b3JrIG9uDQo+PiBtdWx0aS1zdWJuZXQgbmV0d29ya3MuDQo+IA0K
PiBJcyB0aGVyZSBzb21ldGhpbmcgSSBjYW4gcmVhZCBvbiB0aGlzIHBhcnRpY3VsYXIgc3ViamVj
dD8NCg0KVGhlIFdHIGNoYXJ0ZXIgaXMgYXQ6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
d2cvZG5zc2QvY2hhcnRlci8uIA0KQSB0aGluZyB0byBub3RlIGlzIHRoYXQgYm90aCBsYXJnZSBl
bnRlcnByaXNlcyBhbmQgKHNtYWxsKSBob21lbmV0cyBhcmUgaW4gc2NvcGUsIG9uZSBvZiB3aGlj
aCBpcyBtYW5hZ2VkLCBvbmUgb2Ygd2hpY2ggaXNu4oCZdC4NCg0KVGhlIHJlcXVpcmVtZW50cyBh
cmUgZG9jdW1lbnRlZCBpbiBSRkMgNzU1OCwgd2hpY2ggd2FzIHB1Ymxpc2hlZCBsYXN0IHllYXIu
DQoNClRoZSBjdXJyZW50IGh5YnJpZCBwcm94eSBkcmFmdCBpcyBhdCBodHRwczovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kbnNzZC1oeWJyaWQtMDMsIGFuZCBpcyBsaWtlbHkgdG8g
YmUgcHVzaGVkIHRvIHRoZSBJRVNHIGFmdGVyIHRoZSBuZXh0IHVwZGF0ZSwgYmFzZWQgb24gZGlz
Y3Vzc2lvbiBhdCB0aGUgQkEgbWVldGluZy4gDQpTZWN0aW9uIDYgZGVzY3JpYmVzIHRoZSBjdXJy
ZW50IGltcGxlbWVudGF0aW9uIHN0YXR1cy4gDQpUaGUgYXV0aG9yIGlzIFN0dWFydCBDaGVzaGly
ZSwgd2hvIGFsc28gb2YgY291cnNlIGlzIGFuIGF1dGhvciBvZiBtRE5TIGFuZCBETlMtU0QuDQoN
CkEgcGFyYWxsZWwgRE5TIFB1c2ggZHJhZnQgYWxsb3dzIG9wdGltaXNhdGlvbiwgc2VlOiBodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kbnNzZC1wdXNoLTA3DQooVGhpcyBk
cmFmdCBpcyBiZWluZyBzcGxpdCBpbnRvIHR3byBwYXJ0cyBhZnRlciBkaXNjdXNzaW9uIGF0IHRo
ZSBCQSBtZWV0aW5nLCBvbmUgb2Ygd2hpY2ggd2lsbCBiZSBkb25lIGluIHRoZSBkbnNvcCBXRykN
Cg0KRmluYWxseSwgTWFya3VzIGhhcyB3cml0dGVuIGEgaG9tZW5ldC1vcmllbnRlZCBoeWJyaWQg
cHJveHkgZHJhZnQ6IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWhvbWVu
ZXQtaHlicmlkLXByb3h5LXplcm9jb25mLTAyLCB3aGljaCBhaW1zIHRvIGhhbmRsZSB0aGUgdW5t
YW5hZ2VkIHVzZSBvZiBoeWJyaWQgcHJveHkuDQoNClRpbQ0KDQoNCg==


From nobody Thu May  5 07:08:18 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 37DBE12D6C3 for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 07:08: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 jFJRP28CZuN7 for <homenet@ietfa.amsl.com>; Thu,  5 May 2016 07:08:14 -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 9B09812D9CE for <homenet@ietf.org>; Thu,  5 May 2016 07:03:07 -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 85A8F880E4 for <homenet@ietf.org>; Thu,  5 May 2016 07:03:07 -0700 (PDT)
Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 598A7328081A for <homenet@ietf.org>; Thu,  5 May 2016 07:03:07 -0700 (PDT)
To: homenet@ietf.org
References: <CAL0WyWw-kjpwNzXa-EZY1fzWXmXuNEGdMWR7Ui+265jDYj=4HQ@mail.gmail.com> <87d1pesr1o.wl-jch@pps.univ-paris-diderot.fr> <1B850307-5496-4F57-A669-95AAA1B1BC39@gmail.com>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <572B5294.5060008@innovationslab.net>
Date: Thu, 5 May 2016 10:03:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <1B850307-5496-4F57-A669-95AAA1B1BC39@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fOLanfUhD5vgjocQcsLx61p3oWQNKVVgk"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/zUlCxZmua2SQwdjF1yqcvdcTjWU>
Subject: Re: [homenet] Site-local multicast [was: Updating DNS]
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, 05 May 2016 14:08:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--fOLanfUhD5vgjocQcsLx61p3oWQNKVVgk
Content-Type: multipart/mixed; boundary="JbD2gTablOKVAUeKnH8CGsSFA4M8oCauc"
From: Brian Haberman <brian@innovationslab.net>
To: homenet@ietf.org
Message-ID: <572B5294.5060008@innovationslab.net>
Subject: Re: [homenet] Site-local multicast [was: Updating DNS]
References: <CAL0WyWw-kjpwNzXa-EZY1fzWXmXuNEGdMWR7Ui+265jDYj=4HQ@mail.gmail.com>
 <87d1pesr1o.wl-jch@pps.univ-paris-diderot.fr>
 <1B850307-5496-4F57-A669-95AAA1B1BC39@gmail.com>
In-Reply-To: <1B850307-5496-4F57-A669-95AAA1B1BC39@gmail.com>

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



On 4/24/16 5:00 PM, Dino Farinacci wrote:
>> Assuming you've got only transitive links, then any multicast routing
>> protocol should work fine at the scale we envision for Homenet as long=
 as
>> it is able to avoid wireless links whenever possible.  Pierre was
>> suggesting PIM-BIDIR, and actually provided a suitable implementation =
[1].
>> Some people have hinted to me in private conversations that they'd pre=
fer
>> something simpler, perhaps more akin to DVMRP [2] but without the
>> automatic tunnelling.
>=20
> If you don't want any source discovery issues, use Bidir-PIM.=20
>=20

bidir-PIM makes sense in this environment. In addition, there should be
implementation guidance on how to establish the site-local border (see
RFC 4007).

Brian



--JbD2gTablOKVAUeKnH8CGsSFA4M8oCauc--

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

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

iQEcBAEBCAAGBQJXK1KaAAoJEBOZRqCi7goqqE8H/iONXLjEhWm0UbmG3RfFr/4o
ApNSsaqWisAq8aRo4k/GEFaeat82gWEKz2Cill42yy30jgojT+Yi4IlUNkpOCQoA
8S6CDMs8D+q6EdaF0mLkgXiIW1Vc2Z/mNkkho8kFx8NmzywOm3iFJgDnPKlp2Ye8
c18/juJHZsBUdriT8yUcszPANMJs+hA69hnThLg5scabuD48IbWncsnytzz8YeI6
aQqjEL3MFBix49Zoiv/E3vVjrIdKmdcWd2szDZfYuBlAxzfqK/+vkQpi3Q3+QQyb
TdbFAKHZW7cRq8hIDpsOWm7ae1amVE4+6rHYOEyqvwmboBYmgaiXrMFwLTXrgo8=
=O1m3
-----END PGP SIGNATURE-----

--fOLanfUhD5vgjocQcsLx61p3oWQNKVVgk--


From nobody Wed May 11 07:02:02 2016
Return-Path: <v6ops@globis.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 2F26212D6C1 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 07:02:01 -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, HTML_MESSAGE=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 j6oCCtpBFV61 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 07:01:58 -0700 (PDT)
Received: from globis01.globis.net (092-111-140-212.static.chello.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id 230E212D5C7 for <homenet@ietf.org>; Wed, 11 May 2016 07:01:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id C88D540360; Wed, 11 May 2016 16:01:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lj0_jxC4y_Mn; Wed, 11 May 2016 16:01:39 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 397344035E; Wed, 11 May 2016 16:01:37 +0200 (CEST)
Message-ID: <57333B3F.7000009@globis.net>
Date: Wed, 11 May 2016 16:01:35 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="------------010905010908010703000309"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Q48YqPq2a1dPe8j7akajGZtJY0s>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 14:02:01 -0000

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



Tim Chown wrote:
>> On 25 Apr 2016, at 03:39, Ted Lemon <mellon@fugue.com 
>> <mailto:mellon@fugue.com>> wrote:
>>
>> On Sun, Apr 24, 2016 at 12:29 PM, Juliusz Chroboczek 
>> <jch@pps.univ-paris-diderot.fr 
>> <mailto:jch@pps.univ-paris-diderot.fr>> wrote:
>>
>>     > Juliusz, the problem is that existing home network devices that do
>>     > DNS-based service discovery do not support DNS update. They
>>     could, but
>>     > they don't, because we didn't define an easy way for them to do it.
>>
>>     I'd be grateful if you could expand on that.  Why can't we define
>>     a way
>>     for clients to do DDNS?
>>
>>
>> We can and should.   The problem is that we won't see that code ship 
>> in new devices anytime soon, so we still have to make mDNS work.
>
> And this is why the dnssd WG is focused on making mDNS work on 
> multi-subnet networks.
That to me seems to be putting pragmatism before requirements.

I'm not entirely convinced by the dnssd work, and have said so on the 
relevant WG.
>
> But Ted has raised the question of DNS Update there, and we agreed in 
> BA that we’d accept a draft on issues around coexistence of mDNS and 
> DNS Update.
If "it" (multi-subnet mDNS) is going to cause more issues down the line, 
is it sensible to pull this into Homenet now?

Is that the intended question to be answered by that draft?
>
>>     > Just 2136 isn't enfough, because there's no authentication scheme,
>>
>>     I don't understand this argument.  How is non-secured DDNS any
>>     less secure
>>     than mDNS?  What am I missing?
>>
>>
>> This is an implementation issue, not a security issue--sorry for not 
>> making that clear.   In order to preserve the same security 
>> characteristics that mDNS has, we have to ensure that the update 
>> actually originated on the local link, which requires a different 
>> sort of listener than is present in a typical DNS server.   And 
>> existing DNS servers typically don't have any way to support 
>> unauthenticated updates on a first-come, first-served basis, so if 
>> you allow unauthenticated updates, you don't have any way to avoid 
>> collisions.   Otherwise you are correct.   The answer is to write a 
>> document that describes how to do that, and if you read the homenet 
>> naming arch document, you can see that I actually sketched out a 
>> solution there, which I expect to go in a different document, likely 
>> in a different working group.
>
> There are many worms in that can :)
I understand that this is potentially a huge can of worms, but if no one 
opens it, it'll never get solved.

So my preference would be to write down what we want in Homenet (in the 
naming architecture document, in a technology-agnostic way), analyse the 
gaps against competing current technologies, and then see what people 
propose to close those gaps.

If multi-subnet mDNS comes out a clear winner, then I'll shut up.

But I'm not even convinced that the gaps are understood/ documented at 
this time.

>
>>     Oh, sure, we Poles are not quite as pessimistic as the Finns.  I'm
>>     actually of a divided mind here -- I rather like distributed
>>     solutions
>>     (hence prefer mDNS to DDNS) but dislike proxying.  Part of me
>>     just wishes
>>     we'd mandate site-local multicast and do mDNS over that
>>
>>
>> The problem with site-local multicast for mDNS is that multicast 
>> isn't a great solution even on the local wire when that wire is 
>> wireless.    And, you have to do modify the client anyway.
>
> Indeed; this was discussed early on in the dnssd WG, and not 
> considered for those reasons.
>
>> Furthermore, if you consider the mdns hybrid proxy stateless, then 
>> you can have a DNS server that is roughly that stateless too.   I 
>> think it provides better service continuity if you are willing to 
>> retain some state, but everything will still work even if you don't, 
>> just as the hybrid proxy does.
>
> Agreed.
>
> Tim
>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org <mailto:homenet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/homenet
>

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------010905010908010703000309
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html><head>
<meta content="text/html; charset=windows-1252" 
http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<span>Tim Chown wrote:</span><br>
<blockquote style="word-wrap: break-word;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; 
charset=windows-1252">
  <div><blockquote type="cite" class=""><div class="">On 25 Apr 2016, at
 03:39, Ted Lemon &lt;<a moz-do-not-send="true" 
href="mailto:mellon@fugue.com" class="">mellon@fugue.com</a>&gt; wrote:</div><br
 class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div
 class="gmail_extra"><div class="gmail_quote">On Sun, Apr 24, 2016 at 
12:29 PM, Juliusz Chroboczek <span dir="ltr" class="">&lt;<a 
moz-do-not-send="true" href="mailto:jch@pps.univ-paris-diderot.fr" 
target="_blank" class="">jch@pps.univ-paris-diderot.fr</a>&gt;</span> 
wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">&gt; 
Juliusz, the problem is that existing home network devices that do<br 
class="">
&gt; DNS-based service discovery do not support DNS update. They could, 
but<br class="">
&gt; they don't, because we didn't define an easy way for them to do it.<br
 class="">
<br class="">
</span>I'd be grateful if you could expand on that.  Why can't we define
 a way<br class="">
for clients to do DDNS?</blockquote><div class=""><br class=""></div><div
 class="">We can and should.   The problem is that we won't see that 
code ship in new devices anytime soon, so we still have to make mDNS 
work.</div></div></div></div></div></blockquote><div><br class=""></div>And
 this is why the dnssd WG is focused on making mDNS work on multi-subnet
 networks.</div>
</blockquote>
That to me seems to be putting pragmatism before requirements.<br>
<br>
I'm not entirely convinced by the dnssd work, and have said so on the 
relevant WG.<br>
<blockquote style="word-wrap: break-word;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite">
  <div><br class=""></div>
  <div>But Ted has raised the question of DNS Update there, and we 
agreed in BA that we’d accept a draft on issues around coexistence of 
mDNS and DNS Update.</div>
</blockquote>
If "it" (multi-subnet mDNS) is going to cause more issues down the line,
 is it sensible to pull this into Homenet now?<br>
<br>
Is that the intended question to be answered by that draft?<br>
<blockquote style="word-wrap: break-word;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite">
  <div><br class=""><blockquote type="cite" class=""><div dir="ltr" 
class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote 
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc 
solid;padding-left:1ex">&gt; Just 2136 isn't enfough, because there's no
 authentication scheme,<br class="">
<br class="">
I don't understand this argument.  How is non-secured DDNS any less 
secure<br class="">
than mDNS?  What am I missing?<br class=""></blockquote><div class=""><br
 class=""></div><div class="">This is an implementation issue, not a 
security issue--sorry for not making that clear.   In order to preserve 
the same security characteristics that mDNS has, we have to ensure that 
the update actually originated on the local link, which requires a 
different sort of listener than is present in a typical DNS server.   
And existing DNS servers typically don't have any way to support 
unauthenticated updates on a first-come, first-served basis, so if you 
allow unauthenticated updates, you don't have any way to avoid 
collisions.   Otherwise you are correct.   The answer is to write a 
document that describes how to do that, and if you read the homenet 
naming arch document, you can see that I actually sketched out a 
solution there, which I expect to go in a different document, likely in a
 different working group.</div></div></div></div></blockquote><div><br 
class=""></div>There are many worms in that can :)<br class=""></div>
</blockquote>
I understand that this is potentially a huge can of worms, but if no one
 opens it, it'll never get solved.<br>
<br>
So my preference would be to write down what we want in Homenet (in the 
naming architecture document, in a technology-agnostic way), analyse the
 gaps against competing current technologies, and then see what people 
propose to close those gaps.<br>
<br>
If multi-subnet mDNS comes out a clear winner, then I'll shut up.<br>
<br>
But I'm not even convinced that the gaps are understood/ documented at 
this time.<br>
<br>
<blockquote style="word-wrap: break-word; -webkit-nbsp-mode: space; 
-webkit-line-break: after-white-space;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite">
  <div><br class=""><blockquote type="cite" class=""><div dir="ltr" 
class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote 
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc 
solid;padding-left:1ex">Oh, sure, we Poles are not quite as pessimistic 
as the Finns.  I'm<br class="">
actually of a divided mind here -- I rather like distributed solutions<br
 class="">
(hence prefer mDNS to DDNS) but dislike proxying.  Part of me just 
wishes<br class="">
we'd mandate site-local multicast and do mDNS over that</blockquote><div
 class=""><br class=""></div><div class="">The problem with site-local 
multicast for mDNS is that multicast isn't a great solution even on the 
local wire when that wire is wireless.    And, you have to do modify the
 client anyway.</div></div></div></div></blockquote><div><br class=""></div>Indeed;
 this was discussed early on in the dnssd WG, and not considered for 
those reasons. </div>
  <div><br class=""><blockquote type="cite" class=""><div dir="ltr" 
class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Furthermore,
 if you consider the mdns hybrid proxy stateless, then you can have a 
DNS server that is roughly that stateless too.   I think it provides 
better service continuity if you are willing to retain some state, but 
everything will still work even if you don't, just as the hybrid proxy 
does.</div></div></div></div></blockquote><div><br class=""></div><div>Agreed.</div><div><br
 class=""></div>Tim</div>
  <div><br class=""><blockquote type="cite" class=""><div dir="ltr" 
class=""><div class="gmail_extra"><br class=""></div></div>
_______________________________________________<br class="">homenet 
mailing list<br class=""><a moz-do-not-send="true" 
href="mailto:homenet@ietf.org" class="">homenet@ietf.org</a><br class=""><a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a><br
 class=""></blockquote></div>
  <br class="">



</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------010905010908010703000309--


From nobody Wed May 11 07:40:32 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 D2AF412D09C for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 07:40:29 -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 XSWn9n4xCPrL for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 07:40:26 -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 65D0A12DAAC for <homenet@ietf.org>; Wed, 11 May 2016 07:40:25 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lrp0012.outbound.protection.outlook.com [213.199.154.12]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-22-fXmR85QGSbqdijylWGHUUw-1; Wed, 11 May 2016 15:40:16 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nZ8RaVq6qb19Bz08Yzw1mhPDT2bX/LVISFvW3ct54bg=; b=U4CurcG56QcvZz9rCm7QKGtzMFtKBUCig/tlBOSadvkobB5kTXbnQAriw4BxKmvLPUgCdLl8/L0c6WIGydw6X7o4Uy2yd+m4BejHDrz5hXgYaDhwopoktgXTF63xE+TeZbckk8/H2Tq/vnwmiig5WhTzjL7x3PAUG0nb6amUa2w=
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB456.eurprd07.prod.outlook.com (10.242.106.149) with Microsoft SMTP Server (TLS) id 15.1.492.11; Wed, 11 May 2016 14:40:09 +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.0492.016; Wed, 11 May 2016 14:40:09 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
Thread-Topic: [homenet] Updating DNS [was: How many people have installed the homenet code?]
Thread-Index: AQHRpsXbmA7UhtPWP02AZdWH+hpp/p+Z6dOAgBBUBQCACY/egIAACsUA
Date: Wed, 11 May 2016 14:40:09 +0000
Message-ID: <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net>
In-Reply-To: <57333B3F.7000009@globis.net>
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: [194.82.140.195]
x-ms-office365-filtering-correlation-id: 18326950-0660-49d5-4258-08d379aa26ec
x-microsoft-exchange-diagnostics: 1; AMSPR07MB456; 5:QAayIipBp4q5K/oKRrg0I5b9jR/YOPICOCppUz2bTfDPb9rST06xJVPn/dFV/IfS9CcUF7qhAl/zs/79Xht4PjoYZoqkB1rQnqmpekwhDsGDogNlM+cgZOrN4+TB4EuNpNErKUlVnWH2/oNaa7hU/w==; 24:NQrXwHqmRaTyJ28aBl7SKkOLoO4UCWBmCSx1w40CBAcDxfY5gJLWd5qQq0bPqXcgLrtT5WDQGB6zZzlyrB7YRZpmVWiP3ha+4gnzUM71Un8=; 7:YCMtO6O9qKcrucqdHnFQZaELzqoOAFRmnO6GezesBTzMapktCN6oe35s9NT1LWJrrq1FMRWLGZFgiGOBX/6WJL1owCJ/EgKFwuG82EFP1JH7wUNLkorNH297FdCqsR9OYzJUxdqVamM+V1K8LqoRaEYRdUk44+ICyHa8sIjULDpx7olSuBPsBA6h4ErVCPys; 20:VIdjvy3HmWm4TsOioTStyw7Z65Xt1MKZVWsTk3waDd85stEQSn61sGkm+6mIw5SFz9D2rTlJlVt1s2zAHB56Az4V7VxjQ7he7TWM+l94T83fcmmn0nltf5k2aorZefHsXNzbpu+njj5tPJNKAini8TLVHrTKhPmMVhhNNxXufQ8=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB456;
x-microsoft-antispam-prvs: <AMSPR07MB4568E90DA8BA5F6C9A09B57D6720@AMSPR07MB456.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:AMSPR07MB456; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB456; 
x-forefront-prvs: 0939529DE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(377454003)(24454002)(106116001)(110136002)(189998001)(5008740100001)(122556002)(86362001)(93886004)(50226002)(87936001)(92566002)(11100500001)(8936002)(19580405001)(81166006)(2950100001)(19617315012)(2900100001)(19580395003)(33656002)(66066001)(5004730100002)(5002640100001)(50986999)(76176999)(15975445007)(3280700002)(4326007)(77096005)(586003)(16236675004)(74482002)(10400500002)(3660700001)(6116002)(3846002)(102836003)(57306001)(1220700001)(2906002)(36756003)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB456; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2016 14:40:09.2697 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB456
X-MC-Unique: fXmR85QGSbqdijylWGHUUw-1
Content-Type: multipart/alternative; boundary="_000_CC7597904F9B47B8A42CA85F78AC9773jiscacuk_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fpoRKYL41vB71H2w933eXqaZaas>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 14:40:30 -0000

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

Hi Ray,

On 11 May 2016, at 15:01, Ray Hunter (v6ops) <v6ops@globis.net<mailto:v6ops=
@globis.net>> wrote:

Tim Chown wrote:
On 25 Apr 2016, at 03:39, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.c=
om>> wrote:

On Sun, Apr 24, 2016 at 12:29 PM, Juliusz Chroboczek <jch@pps.univ-paris-di=
derot.fr<mailto:jch@pps.univ-paris-diderot.fr>> wrote:
> Juliusz, the problem is that existing home network devices that do
> DNS-based service discovery do not support DNS update. They could, but
> they don't, because we didn't define an easy way for them to do it.

I'd be grateful if you could expand on that.  Why can't we define a way
for clients to do DDNS?

We can and should.   The problem is that we won't see that code ship in new=
 devices anytime soon, so we still have to make mDNS work.

And this is why the dnssd WG is focused on making mDNS work on multi-subnet=
 networks.
That to me seems to be putting pragmatism before requirements.

To an extent it is. The Bonjour protocols are much more widely implemented =
and deployed than DNS Update.

I'm not entirely convinced by the dnssd work, and have said so on the relev=
ant WG.

Do you mean the need for it based on Bonjour, or the solution given we=92re=
 building on that?

Note that one requirement was that other SD protocols could be integrated i=
nto the hybrid proxy model. That=92s still possible, but no one has express=
ed any interest as yet.

But Ted has raised the question of DNS Update there, and we agreed in BA th=
at we=92d accept a draft on issues around coexistence of mDNS and DNS Updat=
e.
If "it" (multi-subnet mDNS) is going to cause more issues down the line, is=
 it sensible to pull this into Homenet now?

I think this is why Ted is doing what he is doing.  Homenet is a different =
environment - smaller and unmanaged, generally.

Is that the intended question to be answered by that draft?

The question is what happens in environments where both might mix.  Well, t=
hat=92s one question.  Ted offered to draft a -00 on that topic, in one of =
his spare moments ;)

> Just 2136 isn't enfough, because there's no authentication scheme,

I don't understand this argument.  How is non-secured DDNS any less secure
than mDNS?  What am I missing?

This is an implementation issue, not a security issue--sorry for not making=
 that clear.   In order to preserve the same security characteristics that =
mDNS has, we have to ensure that the update actually originated on the loca=
l link, which requires a different sort of listener than is present in a ty=
pical DNS server.   And existing DNS servers typically don't have any way t=
o support unauthenticated updates on a first-come, first-served basis, so i=
f you allow unauthenticated updates, you don't have any way to avoid collis=
ions.   Otherwise you are correct.   The answer is to write a document that=
 describes how to do that, and if you read the homenet naming arch document=
, you can see that I actually sketched out a solution there, which I expect=
 to go in a different document, likely in a different working group.

There are many worms in that can :)
I understand that this is potentially a huge can of worms, but if no one op=
ens it, it'll never get solved.

So my preference would be to write down what we want in Homenet (in the nam=
ing architecture document, in a technology-agnostic way), analyse the gaps =
against competing current technologies, and then see what people propose to=
 close those gaps.

That sounds like a good start.

If multi-subnet mDNS comes out a clear winner, then I'll shut up.

But I'm not even convinced that the gaps are understood/ documented at this=
 time.

No, and I agree there. But that doesn=92t preclude delivering the hybrid pr=
oxy model, which is certainly applicable in campus environments (and was in=
 response in part to an educause petition), and for which Markus has presen=
ted a draft for how that model could work in homenets.

Tim

Oh, sure, we Poles are not quite as pessimistic as the Finns.  I'm
actually of a divided mind here -- I rather like distributed solutions
(hence prefer mDNS to DDNS) but dislike proxying.  Part of me just wishes
we'd mandate site-local multicast and do mDNS over that

The problem with site-local multicast for mDNS is that multicast isn't a gr=
eat solution even on the local wire when that wire is wireless.    And, you=
 have to do modify the client anyway.

Indeed; this was discussed early on in the dnssd WG, and not considered for=
 those reasons.

Furthermore, if you consider the mdns hybrid proxy stateless, then you can =
have a DNS server that is roughly that stateless too.   I think it provides=
 better service continuity if you are willing to retain some state, but eve=
rything will still work even if you don't, just as the hybrid proxy does.

Agreed.

Tim


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


--
regards,
RayH
<https://www.postbox-inc.com/?utm_source=3Demail&utm_medium=3Dsiglink&utm_c=
ampaign=3Dreach>
_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet


--_000_CC7597904F9B47B8A42CA85F78AC9773jiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <50E4C03DDB193442944CEAE3DAD868DE@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 Ray,<br class=3D"">
<br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 11 May 2016, at 15:01, Ray Hunter (v6ops) &lt;<a href=3D=
"mailto:v6ops@globis.net" class=3D"">v6ops@globis.net</a>&gt; wrote:</div>
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""><br class=3D"">
<span class=3D"">Tim Chown wrote:</span><br class=3D"">
<blockquote style=3D"word-wrap: break-word;" cite=3D"mid:%3CEMEW3|87dc38b1e=
390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-=
BB0BE0ED9693@ecs.soton.ac.uk%3E" type=3D"cite" class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 25 Apr 2016, at 03:39, Ted Lemon &lt;<a moz-do-not-send=
=3D"true" 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"">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">On Sun, Apr 24, 2016 at 12:29 PM, Juliusz Chrobo=
czek <span dir=3D"ltr" class=3D"">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:jch@pps.univ-paris-diderot.f=
r" target=3D"_blank" class=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=20
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"">&gt; Juliusz, the problem is that existing home network de=
vices that do<br class=3D"">
&gt; DNS-based service discovery do not support DNS update. They could, but=
<br class=3D"">
&gt; they don't, because we didn't define an easy way for them to do it.<br=
 class=3D"">
<br class=3D"">
</span>I'd be grateful if you could expand on that.&nbsp; Why can't we defi=
ne a way<br class=3D"">
for clients to do DDNS?</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">We can and should. &nbsp; The problem is that we won't see =
that code ship in new devices anytime soon, so we still have to make mDNS w=
ork.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
And this is why the dnssd WG is focused on making mDNS work on multi-subnet=
 networks.</div>
</blockquote>
That to me seems to be putting pragmatism before requirements.<br class=3D"=
">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
To an extent it is. The Bonjour protocols are much more widely implemented =
and deployed than DNS Update.</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">I'm not entirely convi=
nced by the dnssd work, and have said so on the relevant WG.<br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
Do you mean the need for it based on Bonjour, or the solution given we=92re=
 building on that?</div>
<div><br class=3D"">
</div>
<div>Note that one requirement was that other SD protocols could be integra=
ted into the hybrid proxy model. That=92s still possible, but no one has ex=
pressed any interest as yet.</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">
<blockquote style=3D"word-wrap: break-word;" cite=3D"mid:%3CEMEW3|87dc38b1e=
390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-=
BB0BE0ED9693@ecs.soton.ac.uk%3E" type=3D"cite" class=3D"">
<div class=3D"">But Ted has raised the question of DNS Update there, and we=
 agreed in BA that we=92d accept a draft on issues around coexistence of mD=
NS and DNS Update.</div>
</blockquote>
If &quot;it&quot; (multi-subnet mDNS) is going to cause more issues down th=
e line, is it sensible to pull this into Homenet now?<br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
I think this is why Ted is doing what he is doing. &nbsp;Homenet is a diffe=
rent environment - smaller and unmanaged, generally.</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">Is that the intended q=
uestion to be answered by that draft?<br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
The question is what happens in environments where both might mix. &nbsp;We=
ll, that=92s one question. &nbsp;Ted offered to draft a -00 on that topic, =
in one of his spare moments ;)</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">
<blockquote style=3D"word-wrap: break-word;" cite=3D"mid:%3CEMEW3|87dc38b1e=
390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-=
BB0BE0ED9693@ecs.soton.ac.uk%3E" type=3D"cite" class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc=20
solid;padding-left:1ex">
&gt; Just 2136 isn't enfough, because there's no authentication scheme,<br =
class=3D"">
<br class=3D"">
I don't understand this argument.&nbsp; How is non-secured DDNS any less se=
cure<br class=3D"">
than mDNS?&nbsp; What am I missing?<br class=3D"">
</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">This is an implementation issue, not a security issue--sorr=
y for not making that clear. &nbsp; In order to preserve the same security =
characteristics that mDNS has, we have to ensure that the update actually o=
riginated on the local link, which requires
 a different sort of listener than is present in a typical DNS server. &nbs=
p; And existing DNS servers typically don't have any way to support unauthe=
nticated updates on a first-come, first-served basis, so if you allow unaut=
henticated updates, you don't have any
 way to avoid collisions. &nbsp; Otherwise you are correct. &nbsp; The answ=
er is to write a document that describes how to do that, and if you read th=
e homenet naming arch document, you can see that I actually sketched out a =
solution there, which I expect to go in a
 different document, likely in a different working group.</div>
</div>
</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
There are many worms in that can :)<br class=3D"">
</div>
</blockquote>
I understand that this is potentially a huge can of worms, but if no one op=
ens it, it'll never get solved.<br class=3D"">
<br class=3D"">
So my preference would be to write down what we want in Homenet (in the nam=
ing architecture document, in a technology-agnostic way), analyse the gaps =
against competing current technologies, and then see what people propose to=
 close those gaps.<br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
That sounds like a good start.</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">If multi-subnet mDNS c=
omes out a clear winner, then I'll shut up.<br class=3D"">
<br class=3D"">
But I'm not even convinced that the gaps are understood/ documented at this=
 time.<br class=3D"">
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
No, and I agree there. But that doesn=92t preclude delivering the hybrid pr=
oxy model, which is certainly applicable in campus environments (and was in=
 response in part to an educause petition), and for which Markus has presen=
ted a draft for how that model could
 work in homenets.</div>
<div><br class=3D"">
</div>
<div>Tim</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">
<blockquote style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=20
-webkit-line-break: after-white-space;" cite=3D"mid:%3CEMEW3|87dc38b1e39049=
6e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE=
0ED9693@ecs.soton.ac.uk%3E" type=3D"cite" class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc=20
solid;padding-left:1ex">
Oh, sure, we Poles are not quite as pessimistic as the Finns.&nbsp; I'm<br =
class=3D"">
actually of a divided mind here -- I rather like distributed solutions<br c=
lass=3D"">
(hence prefer mDNS to DDNS) but dislike proxying.&nbsp; Part of me just wis=
hes<br class=3D"">
we'd mandate site-local multicast and do mDNS over that</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The problem with site-local multicast for mDNS is that mult=
icast isn't a great solution even on the local wire when that wire is wirel=
ess. &nbsp; &nbsp;And, you have to do modify the client anyway.</div>
</div>
</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
Indeed; this was discussed early on in the dnssd WG, and not considered for=
 those reasons.&nbsp;</div>
<div class=3D""><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div class=3D"">Furthermore, if you consider the mdns hybrid proxy stateles=
s, then you can have a DNS server that is roughly that stateless too. &nbsp=
; I think it provides better service continuity if you are willing to retai=
n some state, but everything will still
 work even if you don't, just as the hybrid proxy does.</div>
</div>
</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Agreed.</div>
<div class=3D""><br class=3D"">
</div>
Tim</div>
<div class=3D""><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail_extra"><br class=3D"">
</div>
</div>
_______________________________________________<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 class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a><br class=
=3D"">
</blockquote>
</div>
<br class=3D"">
</blockquote>
<br class=3D"">
<div class=3D"moz-signature">-- <br class=3D"">
<div class=3D"">regards,<br class=3D"">
RayH<span style=3D"text-decoration: underline;" class=3D""><br class=3D"">
</span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm_m=
edium=3Dsiglink&amp;utm_campaign=3Dreach" class=3D""><span style=3D"color: =
rgb(51, 102, 153);" class=3D""></span></a></div>
</div>
</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_CC7597904F9B47B8A42CA85F78AC9773jiscacuk_--


From nobody Wed May 11 09:16:42 2016
Return-Path: <v6ops@globis.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 39A0612D1B7 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, 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 V3SZhawHrE73 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:16:37 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D982112D6DE for <homenet@ietf.org>; Wed, 11 May 2016 09:16:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0E0AA4035E; Wed, 11 May 2016 18:16:34 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVpWgpDGa9Ds; Wed, 11 May 2016 18:16:29 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 59D384032B; Wed, 11 May 2016 18:15:56 +0200 (CEST)
Message-ID: <57335AB6.8060305@globis.net>
Date: Wed, 11 May 2016 18:15:50 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk>
In-Reply-To: <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk>
Content-Type: multipart/alternative; boundary="------------010209000202030601050702"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HakAflw6nEnfdPz2ZIF_EHzQay8>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 16:16:41 -0000

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

>> On 11 May 2016, at 15:01, Ray Hunter (v6ops) <v6ops@globis.net 
>> <mailto:v6ops@globis.net>> wrote:
>>
>> Tim Chown wrote:
>>>> On 25 Apr 2016, at 03:39, Ted Lemon <mellon@fugue.com 
>>>> <mailto:mellon@fugue.com>> wrote:
>>>>
>>>> On Sun, Apr 24, 2016 at 12:29 PM, Juliusz Chroboczek 
>>>> <jch@pps.univ-paris-diderot.fr 
>>>> <mailto:jch@pps.univ-paris-diderot.fr>> wrote:
>>>>
>>>>     > Juliusz, the problem is that existing home network devices that do
>>>>     > DNS-based service discovery do not support DNS update. They
>>>>     could, but
>>>>     > they don't, because we didn't define an easy way for them to
>>>>     do it.
>>>>
>>>>     I'd be grateful if you could expand on that.  Why can't we
>>>>     define a way
>>>>     for clients to do DDNS?
>>>>
>>>>
>>>> We can and should.   The problem is that we won't see that code 
>>>> ship in new devices anytime soon, so we still have to make mDNS work.
>>>
>>> And this is why the dnssd WG is focused on making mDNS work on 
>>> multi-subnet networks.
>> That to me seems to be putting pragmatism before requirements.
>
> To an extent it is. The Bonjour protocols are much more widely 
> implemented and deployed than DNS Update.
>
Yes. I've seen a lot of printers shipping with it, and it works great at 
that scale.

I've also seen enterprises working with fully integrated DNS, together 
with managed Windows Domain Controllers, at monster scale.

Homenet is somewhere in the middle: we have more complexity, but no 
"computer certificates" to fall back on.

>> I'm not entirely convinced by the dnssd work, and have said so on the 
>> relevant WG.
>
> Do you mean the need for it based on Bonjour, or the solution given 
> we’re building on that?
Both.

Bonjour is a great protocol for a flat L2 network.

Bonjour is not designed for L3 networks (no inherent hop count, nor loop 
protection), nor support for multiple/overlapping name spaces.

The Homenet architecture calls for administrative zones.

I may have a guest LAN.
I may have a printer LAN (that is shared with guests)
I may have a media server (which is not shared with guests)

The Homenet architecture calls for multiple upstream providers.

I may have an electricity provider who allows me some special log on via 
the power network to control home automation, or feed back from my solar 
panels. They may publish (private) names for use by contracted customers 
that are not available over the Internet. Yes, that could also be done 
over Internet, but a specialised "walled garden" could be so much more 
secure and less vulnerable to external disruption.

Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against 
Appletalk Phase II, so if Bonjour was extended to provide an equivalent 
function to Appletalk Phase II Zone Information Protocol = ZIP then I'd 
be happier. That would cover concerns on non-overlapping name spaces. 
And Appletalk NBP/ZIP resolution also prevents loops in routed networks.

Otherwise I struggle to map the Homenet requirements onto the solution.

[BTW for the record, I don't consider DNS "as-is today" a great 
contender either. So I'm not just bashing Bonjour by any means]

>
> Note that one requirement was that other SD protocols could be 
> integrated into the hybrid proxy model. That’s still possible, but no 
> one has expressed any interest as yet.
>
I don't like the hybrid proxy model either.

It promises the union of the problems and intersection of the functionality.

Proxying flies in the face of the trend of smart devices and dumb networks.

If you get any device that bypasses, or misunderstands, the proxy 
topology, we could get very nasty name resolution loops [no inherent 
loop protection in Bonjour].

>>> But Ted has raised the question of DNS Update there, and we agreed 
>>> in BA that we’d accept a draft on issues around coexistence of mDNS 
>>> and DNS Update.
>> If "it" (multi-subnet mDNS) is going to cause more issues down the 
>> line, is it sensible to pull this into Homenet now?
>
> I think this is why Ted is doing what he is doing.  Homenet is a 
> different environment - smaller and unmanaged, generally.
>
>> Is that the intended question to be answered by that draft?
>
> The question is what happens in environments where both might mix. 
>  Well, that’s one question.  Ted offered to draft a -00 on that topic, 
> in one of his spare moments ;)
>
That seems like a worthwhile draft.

>>>>     > Just 2136 isn't enfough, because there's no authentication
>>>>     scheme,
>>>>
>>>>     I don't understand this argument.  How is non-secured DDNS any
>>>>     less secure
>>>>     than mDNS?  What am I missing?
>>>>
>>>>
>>>> This is an implementation issue, not a security issue--sorry for 
>>>> not making that clear.   In order to preserve the same security 
>>>> characteristics that mDNS has, we have to ensure that the update 
>>>> actually originated on the local link, which requires a different 
>>>> sort of listener than is present in a typical DNS server.   And 
>>>> existing DNS servers typically don't have any way to support 
>>>> unauthenticated updates on a first-come, first-served basis, so if 
>>>> you allow unauthenticated updates, you don't have any way to avoid 
>>>> collisions.   Otherwise you are correct.   The answer is to write a 
>>>> document that describes how to do that, and if you read the homenet 
>>>> naming arch document, you can see that I actually sketched out a 
>>>> solution there, which I expect to go in a different document, 
>>>> likely in a different working group.
>>>
>>> There are many worms in that can :)
>> I understand that this is potentially a huge can of worms, but if no 
>> one opens it, it'll never get solved.
>>
>> So my preference would be to write down what we want in Homenet (in 
>> the naming architecture document, in a technology-agnostic way), 
>> analyse the gaps against competing current technologies, and then see 
>> what people propose to close those gaps.
>
> That sounds like a good start.
>
>> If multi-subnet mDNS comes out a clear winner, then I'll shut up.
>>
>> But I'm not even convinced that the gaps are understood/ documented 
>> at this time.
>
> No, and I agree there. But that doesn’t preclude delivering the hybrid 
> proxy model, which is certainly applicable in campus environments (and 
> was in response in part to an educause petition), and for which Markus 
> has presented a draft for how that model could work in homenets.
>
> Tim
>

--------------010209000202030601050702
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html><head>
<meta content="text/html; charset=windows-1252" 
http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
  <blockquote style="display: block;" type="cite" class=""><div class="">On
 11 May 2016, at 15:01, Ray Hunter (v6ops) &lt;<a 
href="mailto:v6ops@globis.net" class="">v6ops@globis.net</a>&gt; wrote:</div>
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><br class="">
<span class="">Tim Chown wrote:</span><br class="">
<blockquote style="word-wrap: break-word; display: block;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite" class=""><div class="">
<blockquote style="display: block;" type="cite" class=""><div class="">On
 25 Apr 2016, at 03:39, Ted Lemon &lt;<a moz-do-not-send="true" 
href="mailto:mellon@fugue.com" class="">mellon@fugue.com</a>&gt; wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div style="display: block;" class="gmail_quote">On Sun, Apr 24, 2016 at
 12:29 PM, Juliusz Chroboczek <span dir="ltr" class="">
&lt;<a moz-do-not-send="true" 
href="mailto:jch@pps.univ-paris-diderot.fr" target="_blank" class="">jch@pps.univ-paris-diderot.fr</a>&gt;</span>
 wrote:<br class="">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; 
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; display: 
block;"><span class="">&gt; Juliusz, the problem is that existing home 
network devices that do<br class="">
&gt; DNS-based service discovery do not support DNS update. They could, 
but<br class="">
&gt; they don't, because we didn't define an easy way for them to do it.<br
 class="">
<br class="">
</span>I'd be grateful if you could expand on that.  Why can't we define
 a way<br class="">
for clients to do DDNS?</blockquote>
<div class=""><br class="">
</div>
<div class="">We can and should.   The problem is that we won't see that
 code ship in new devices anytime soon, so we still have to make mDNS 
work.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
And this is why the dnssd WG is focused on making mDNS work on 
multi-subnet networks.</div>
</blockquote>
That to me seems to be putting pragmatism before requirements.<br 
class="">
</div>
</div>
  </blockquote>

  <div><br class="">
  </div>

To an extent it is. The Bonjour protocols are much more widely 
implemented and deployed than DNS Update.
  <div><br class=""></div>
</blockquote>
Yes. I've seen a lot of printers shipping with it, and it works great at
 that scale.<br>
<br>
I've also seen enterprises working with fully integrated DNS, together 
with managed Windows Domain Controllers, at monster scale.<br>
<br>
Homenet is somewhere in the middle: we have more complexity, but no 
"computer certificates" to fall back on.<br>
<br>
<blockquote type="cite">
  <div>
<blockquote style="display: block;" type="cite" class=""><div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">I'm not entirely 
convinced by the dnssd work, and have said so on the relevant WG.<br 
class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Do you mean the need for it based on Bonjour, or the solution given 
we’re building on that?</div>
</blockquote>
Both.<br>
<br>
Bonjour is a great protocol for a flat L2 network.<br>
<br>
Bonjour is not designed for L3 networks (no inherent hop count, nor loop
 protection), nor support for multiple/overlapping name spaces.<br>
<br>
The Homenet architecture calls for administrative zones.<br>

<br>
I may have a guest LAN.<br>
I may have a printer LAN (that is shared with guests)<br>
I may have a media server (which is not shared with guests)<br>
<br>
The Homenet architecture calls for multiple upstream providers.<br>
<br>
I may have an electricity provider who allows me some special log on via
 the power network to control home automation, or feed back from my 
solar panels. They may publish (private) names for use by contracted 
customers that are not available over the Internet. Yes, that could also
 be done over Internet, but a specialised "walled garden" could be so 
much more secure and less vulnerable to external disruption.<br>
<br>
Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against 
Appletalk Phase II, so if Bonjour was extended to provide an equivalent 
function to Appletalk Phase II Zone Information Protocol = ZIP then I'd 
be happier. That would cover concerns on non-overlapping name spaces. 
And Appletalk NBP/ZIP resolution also prevents loops in routed networks.<br>
<br>
Otherwise I struggle to map the Homenet requirements onto the solution.<br>
<br>
[BTW for the record, I don't consider DNS "as-is today" a great 
contender either. So I'm not just bashing Bonjour by any means]<br>
<br>
<blockquote type="cite">
  <div><br class="">
  </div>

  <div>Note that one requirement was that other SD protocols could be 
integrated into the hybrid proxy model. That’s still possible, but no 
one has expressed any interest as yet.</div>

  <div><br class=""></div>
</blockquote>
I don't like the hybrid proxy model either.<br>
<br>
It promises the union of the problems and intersection of the 
functionality.<br>
<br>
Proxying flies in the face of the trend of smart devices and dumb 
networks.<br>
<br>
If you get any device that bypasses, or misunderstands, the proxy 
topology, we could get very nasty name resolution loops [no inherent 
loop protection in Bonjour].<br>
<br>
<blockquote type="cite">
  <div>
<blockquote style="display: block;" type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<blockquote style="word-wrap: break-word; display: block;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite" class="">
<div class="">But Ted has raised the question of DNS Update there, and 
we agreed in BA that we’d accept a draft on issues around coexistence of
 mDNS and DNS Update.</div>
</blockquote>
If "it" (multi-subnet mDNS) is going to cause more issues down the line,
 is it sensible to pull this into Homenet now?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
I think this is why Ted is doing what he is doing.  Homenet is a 
different environment - smaller and unmanaged, generally.</div>

  <div><br class="">
<blockquote style="display: block;" type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">Is that the intended 
question to be answered by that draft?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
The question is what happens in environments where both might mix. 
 Well, that’s one question.  Ted offered to draft a <span 
__postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding: 0pt;">-00</span> on
 that topic, in one of his spare moments ;)</div>

  <div><br class=""></div>
</blockquote>
That seems like a worthwhile draft.<br>
<br>
<blockquote type="cite">
  <div>
<blockquote style="display: block;" type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<blockquote style="word-wrap: break-word; display: block;" 
cite="mid:%3CEMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk%3E"
 type="cite" class="">
<div class="">
<blockquote style="display: block;" type="cite" class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div style="display: block;" class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; 
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; display: 
block;">
&gt; Just 2136 isn't enfough, because there's no authentication scheme,<br
 class="">
<br class="">
I don't understand this argument.  How is non-secured DDNS any less 
secure<br class="">
than mDNS?  What am I missing?<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">This is an implementation issue, not a security 
issue--sorry for not making that clear.   In order to preserve the same 
security characteristics that mDNS has, we have to ensure that the 
update actually originated on the local link, which requires
 a different sort of listener than is present in a typical DNS server.  
 And existing DNS servers typically don't have any way to support 
unauthenticated updates on a first-come, first-served basis, so if you 
allow unauthenticated updates, you don't have any
 way to avoid collisions.   Otherwise you are correct.   The answer is 
to write a document that describes how to do that, and if you read the 
homenet naming arch document, you can see that I actually sketched out a
 solution there, which I expect to go in a
 different document, likely in a different working group.</div>
</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
There are many worms in that can :)<br class="">
</div>
</blockquote>
I understand that this is potentially a huge can of worms, but if no one
 opens it, it'll never get solved.<br class="">
<br class="">
So my preference would be to write down what we want in Homenet (in the 
naming architecture document, in a technology-agnostic way), analyse the
 gaps against competing current technologies, and then see what people 
propose to close those gaps.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
That sounds like a good start.</div>

  <div><br class="">
<blockquote style="display: block;" type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">If multi-subnet mDNS 
comes out a clear winner, then I'll shut up.<br class="">
<br class="">
But I'm not even convinced that the gaps are understood/ documented at 
this time.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
No, and I agree there. But that doesn’t preclude delivering the hybrid 
proxy model, which is certainly applicable in campus environments (and 
was in response in part to an educause petition), and for which Markus 
has presented a draft for how that model could
 work in homenets.</div>

  <div><br class="">
  </div>

  <div>Tim</div>

  <br class="">
</blockquote>
</body></html>

--------------010209000202030601050702--


From nobody Wed May 11 09:29: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 1664612D11F for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:29: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 JsOyt2iHI6cb for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:29:55 -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 4ECDA12B048 for <homenet@ietf.org>; Wed, 11 May 2016 09:29:54 -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 u4BGTp67027812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 May 2016 18:29:51 +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 u4BGTpWl026655; Wed, 11 May 2016 18:29:51 +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 3EC6961F9A; Wed, 11 May 2016 18:29:51 +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 iGHMaW7LMpCa; Wed, 11 May 2016 18:29:49 +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 7B8B761FA7; Wed, 11 May 2016 18:29:49 +0200 (CEST)
Date: Wed, 11 May 2016 18:29:49 +0200
Message-ID: <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
In-Reply-To: <57335AB6.8060305@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=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]); Wed, 11 May 2016 18:29:51 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 11 May 2016 18:29:51 +0200 (CEST)
X-Miltered: at korolev with ID 57335DFF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 57335DFF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57335DFF.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: 57335DFF.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 : 57335DFF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 57335DFF.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_7dTjfV7JD3wVMF44AQ3GeTYYd4>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 16:29:57 -0000

> Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against
> Appletalk Phase II, so if Bonjour was extended to provide an equivalent
> function to Appletalk Phase II Zone Information Protocol = ZIP then I'd be
> happier. That would cover concerns on non-overlapping name spaces. And
> Appletalk NBP/ZIP resolution also prevents loops in routed networks.

« The AppleTalk Zone Information Protocol (ZIP) manages the relationship
  between network numbers and zone names. »

While I could in principle go and pick a copy of Inside Appletalk at the
library, I'd be grateful if you could explain what you have in mind.

> I don't like the hybrid proxy model either.  It promises the union of
> the problems and intersection of the functionality.  Proxying flies in
> the face of the trend of smart devices and dumb networks.

Very well put.

-- Juliusz


From nobody Wed May 11 09:38: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 42C4B12D4FE for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:38:13 -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 ua6oxcuc7dsb for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:38:10 -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 9FCA412D4FC for <homenet@ietf.org>; Wed, 11 May 2016 09:38:10 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id y84so55867086lfc.0 for <homenet@ietf.org>; Wed, 11 May 2016 09:38:10 -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=oIfvYqpZm9i4sIOXOatGJ+S6RmHBZdaEBBlkQC0oaAg=; b=ZCVv/OmyKMNZeTua8V4jyBL6axLyYVFaMf2sRkTk1PZ1VZXmHjoDhoXi65X76EvoAu Y3rNYnJqWBH64vhyGL7JTJbbb6kqskHRQPn3YAyIs/jWN5GsGvh8z3f1KNsMGMVYDgJQ umEynRQECA4dfzEX+s7tJT6pHUP7oLQROGhS1t8YPJjgbXfKk9yyCuo1rLfuFJL9jnL3 FhNb2riw2lAStMwKolybKYUh+s0STPYCgStnO019QA/E40zIbgL+6Lcd9TxaB5JxN+LR xJNBElrAdpp0/BGgRIeUGn8FB1kmLYfb4JqSMpTpGJXiPGN6LIP401CE5uoHQ9Omtlss +rGg==
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=oIfvYqpZm9i4sIOXOatGJ+S6RmHBZdaEBBlkQC0oaAg=; b=gGWd/X6/zoCVnWgn+U62+lb/nCL8Twzkg5Akj1yeXl+8ieNWsVOAwB6e/BmmWJY+FN fpKGWXlXwmJuuMUSBPuOEujrAm/k9jnoKHJjCMtAmP7y+ycFDqwvomc8pfyqYi4AGOkc g+guu/Ebc++MFQPvr2cC8WupyBN0mY6wibd9MV7ipNfhXryzs1a0+fpcsSeUh5UUbViO 8eGUpNLUwu2uuTE+9POizcJqz+CfEE6PwhYbvbH+TS0wWypmoWVX0CnpPtux41nJFDFe NmEwZUwYS2EB1bOCpjYKm4+C0+VKl+3UBXk0vpKH4TKV5W+g1qAbpAhQOrVUD92ztfaG QSGA==
X-Gm-Message-State: AOPr4FXN06FxatZc02JOsCxKaQe5wqsBEAllCCz+0NWQrHVMt0/D9qSeQV3xbbwO73Ed+hm/aqECf+jwEI6q0w==
X-Received: by 10.25.79.132 with SMTP id d126mr2025256lfb.119.1462984688714; Wed, 11 May 2016 09:38:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 09:37:29 -0700 (PDT)
In-Reply-To: <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 12:37:29 -0400
Message-ID: <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a114251aaaedaa8053293aad7
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7vEGeTSzHdLpcgP06BqRK65VAqI>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "Ray Hunter \(v6ops\)" <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 16:38:13 -0000

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

On Wed, May 11, 2016 at 12:29 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> > I don't like the hybrid proxy model either.  It promises the union of
> > the problems and intersection of the functionality.  Proxying flies in
> > the face of the trend of smart devices and dumb networks.
>
> Very well put.
>

Be that as it may, Homenet in general flies in the face of that trend.
And if you think about it, that trend isn't really a very smart trend,
because the burden it places on devices is extreme, and not all devices
have infinite resources to spend mapping the network and figuring out how
to publish their services on it.

--001a114251aaaedaa8053293aad7
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, May 11, 2016 at 12:29 PM, Juliusz Chroboczek <span dir=3D"ltr">&lt;<a h=
ref=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;padding-left:1ex"><=
span class=3D"">&gt; I don&#39;t like the hybrid proxy model either.=C2=A0 =
It promises the union of<br>
&gt; the problems and intersection of the functionality.=C2=A0 Proxying fli=
es in<br>
&gt; the face of the trend of smart devices and dumb networks.<br>
<br>
</span>Very well put.<br></blockquote><div><br></div><div>Be that as it may=
, Homenet in general flies in the face of that trend. =C2=A0 And if you thi=
nk about it, that trend isn&#39;t really a very smart trend, because the bu=
rden it places on devices is extreme, and not all devices have infinite res=
ources to spend mapping the network and figuring out how to publish their s=
ervices on it.=C2=A0</div></div></div></div>

--001a114251aaaedaa8053293aad7--


From nobody Wed May 11 09:47:44 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 6ECAE12D11F for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:47:43 -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 DQ-2N-jN5Qxa for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:47:42 -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 E069712B007 for <homenet@ietf.org>; Wed, 11 May 2016 09:47:41 -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 u4BGldP8002739; Wed, 11 May 2016 18:47:39 +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 4724261FAD; Wed, 11 May 2016 18:47:39 +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 ik0bKwO5QBB3; Wed, 11 May 2016 18:47:37 +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 0344F61FA7; Wed, 11 May 2016 18:47:34 +0200 (CEST)
Date: Wed, 11 May 2016 18:47:34 +0200
Message-ID: <87k2j0h789.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: <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@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]); Wed, 11 May 2016 18:47:39 +0200 (CEST)
X-Miltered: at korolev with ID 5733622B.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5733622B.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 : 5733622B.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: <http://mailarchive.ietf.org/arch/msg/homenet/VJIUSHfb8Df-15dxyP0sHLOJCKE>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "Ray Hunter \(v6ops\)" <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 16:47:43 -0000

>>> Proxying flies in the face of the trend of smart devices and dumb
>>> networks.

> Be that as it may, Homenet in general flies in the face of that trend.

Not sure.  If you look at HNCP, the only intelligence there is a bunch of
election algorithms (prefix assignment is just election with non-local
constraints, all the rest are just instances of two standard election
algorithms).

It's not as bad as it looks ;-)

-- Juliusz


From nobody Wed May 11 09:50:52 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 55B3E12D1E7 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:50:50 -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 HmMkfjBfPKS6 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 09:50:49 -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 B909712D0C3 for <homenet@ietf.org>; Wed, 11 May 2016 09:50:48 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id j8so55771561lfd.2 for <homenet@ietf.org>; Wed, 11 May 2016 09:50:48 -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=xtAnqmZxDHYzDyFazMhV+pY6AKuBPfc7nuRcOQLB5EI=; b=JHehaIxsm5LBjvjW+A7m19D/pfAHaCKCflCd4zQEEC4oLLJOwuX1ODS9dzqTghV0up GAChCFg0ibhYB5ibi0pNe34+CO2xk6Rt9RuqJebb/LX3w2zkn8w0WwXqTPYpZFT6KUEt MEqJaW9NhDO8BCQpQNSFux0lU111eyBU90hKaoBbCkokv9WEQ5lZEdY3wTqNT/Hadm6c pJ+qmr+1WPDJoO/f1SbqeoHuiTz4dtn9oVwzej+I0wqTYiESSG5otVG/uP+kvgCV6+bC JlZKdDLGtfJVJv5YYBh8+M+wVYDCKAuX234ooVoqP3YT1nSJqiPnvUz1GVHPSmjKVuCV 3yrQ==
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=xtAnqmZxDHYzDyFazMhV+pY6AKuBPfc7nuRcOQLB5EI=; b=QKtpnc9zrp2h29WfmIGQqU+SjNqrrNKbx2Fuixpwgjkr8aVJlD+Y9vD83wJV8DRbBR J1soDN2dolTPKfZCAiR8FmQnRjpQd4pHqgHcH+1qHhdQpc5lrMkht7/aSwgO3496X8uK 4+N9q17p7uGmm1KNSwquK2j9xJdb+yC3QlfwOTug584GyGKyCqhjnbErg3JgXdYU5jWa iMQCCZ3SGAxdqdAfmcnk1YxnKX3DPGKffc07rWwp9A/olpYl1psIRJBl/VzC0SDfMRUC D238bxb4MrKDKwfvGpj51kwCbjamol77uQqpXVv9jJnw9fPKEe8dJKSWqoYQZTCz2u0Q ZrlQ==
X-Gm-Message-State: AOPr4FUBt+VczSHsYP7UptXg0vyrUOTdoYa7MQYqmAeuwCQwJ5ee9Uc2TF+HncC0ORnJEFTlc0FMGHcsL5fzcQ==
X-Received: by 10.112.161.41 with SMTP id xp9mr2009348lbb.133.1462985447019; Wed, 11 May 2016 09:50:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 09:50:07 -0700 (PDT)
In-Reply-To: <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 12:50:07 -0400
Message-ID: <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11c26b2ae1b1d1053293d7de
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1o6u7v9YozLyEcS5fvwYbZ9WAj0>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "Ray Hunter \(v6ops\)" <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 16:50:50 -0000

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

I tend to think of routing protocols and election protocols as
"intelligent", but perhaps you meant something different... :)

E.g., did you mean "stateful?"

On Wed, May 11, 2016 at 12:47 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> >>> Proxying flies in the face of the trend of smart devices and dumb
> >>> networks.
>
> > Be that as it may, Homenet in general flies in the face of that trend.
>
> Not sure.  If you look at HNCP, the only intelligence there is a bunch of
> election algorithms (prefix assignment is just election with non-local
> constraints, all the rest are just instances of two standard election
> algorithms).
>
> It's not as bad as it looks ;-)
>
> -- Juliusz
>

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

<div dir=3D"ltr">I tend to think of routing protocols and election protocol=
s as &quot;intelligent&quot;, but perhaps you meant something different... =
:)<div><br></div><div>E.g., did you mean &quot;stateful?&quot;</div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 11, 20=
16 at 12:47 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"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">&gt;&gt;&gt; Proxying flies in the face of the trend of smart devices and=
 dumb<br>
&gt;&gt;&gt; networks.<br>
<br>
</span><span class=3D"">&gt; Be that as it may, Homenet in general flies in=
 the face of that trend.<br>
<br>
</span>Not sure.=C2=A0 If you look at HNCP, the only intelligence there is =
a bunch of<br>
election algorithms (prefix assignment is just election with non-local<br>
constraints, all the rest are just instances of two standard election<br>
algorithms).<br>
<br>
It&#39;s not as bad as it looks ;-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
</font></span></blockquote></div><br></div>

--001a11c26b2ae1b1d1053293d7de--


From nobody Wed May 11 10:00: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 E17E412B02C for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:00: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 M_WpoRlus0M2 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:00: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 9D74012B01F for <homenet@ietf.org>; Wed, 11 May 2016 10:00: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 u4BH0D9w009303; Wed, 11 May 2016 19:00: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 8561A61FA7; Wed, 11 May 2016 19:00: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 9aHEHfLpa6qY; Wed, 11 May 2016 19:00: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 2EA3461FAB; Wed, 11 May 2016 19:00:11 +0200 (CEST)
Date: Wed, 11 May 2016 19:00:10 +0200
Message-ID: <87inykh6n9.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_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@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]); Wed, 11 May 2016 19:00:13 +0200 (CEST)
X-Miltered: at korolev with ID 5733651D.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5733651D.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 : 5733651D.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7h8cXuhCXsFPhciSI8UO5aHvaD8>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "Ray Hunter \(v6ops\)" <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 17:00:19 -0000

> I tend to think of routing protocols and election protocols as "intelligent",
> but perhaps you meant something different... :)

> E.g., did you mean "stateful?"

No (HNCP manages quite a bit of hard state, unfortunately).  I think
I meant "able to interpret higher-layer data", but I'm no longer sure ;-)

-- Juliusz


From nobody Wed May 11 10:22:18 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 3480A12D140 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:22:17 -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 KwrY80lYNqsU for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:22:15 -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 1148012D0EE for <homenet@ietf.org>; Wed, 11 May 2016 10:22:15 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id y84so57150373lfc.0 for <homenet@ietf.org>; Wed, 11 May 2016 10:22:14 -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=xjFbIoZxdPFzG2pf0Ex80UscWyiB0thbStfCWie7veA=; b=g/Xf2qiBzU31U7DJoQGUlbQKnS1Fke9Pnxgi/wKPU3yzZUdd1wJq/x6/Y8JucrvltR rygmZqXM99i4p9yteWgqqfzuHgh0Zc7fQ+3gJTksneDhKe/EMVtiBksM/6YC0ghnRN3I YZ6agVDLLoDw+a4UnB7EnsHw7dNMfx4GhcSSvxx+CODG+qkRHX38GMb/s+OxGvFNFVih JYOorFvyhskR+qArw44eEnVjfsxYhqBNT8yXZ5yCCZQdYo6uEZ5RUltLTJSAa8UNS1YB ceIdYIrqQGn66RF35h7TxwjOVILvSf/N0NgVKoDTsvgtcVMKc+r6l8O6jlW7Dv7VeCOW U3Ng==
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=xjFbIoZxdPFzG2pf0Ex80UscWyiB0thbStfCWie7veA=; b=UuUntQRH+uTHGzIpejGzXSgCFlxnU8XZ0d4q9enyhBTDYozlvJ2PttAl6qhiLVdUco 0W9lBmWYmK1C7FzPjBSEzcrU7hBaKD4oA3NGVd8f/ZlGVgTPBWE0l6vWQFJOL1kWjcFF vOFeoIQlZHKtJNItqOPpoZJBsitzrz4mxvFSOc6Ui4w7L6751pPgjOboWUdg9xsdk0oJ mjahlTnzoXnD0kSV81ZoLdLXoYW7P+NFUI4t+AXY3GAFjia/EjI9TSGAcq+8y3tEqcMs Kh6dKODE6fuOuGbYTyY9ji1xfFiWkJy5Zui8ddUxHM3g1iolbwMB9ohMiQwj6qjh6k11 bLLg==
X-Gm-Message-State: AOPr4FUihsgKGWZTevwzR1goOHhjQp3oE9uNiPzVasqizkcVMey8NzjC2GvKVr0JJnjpXyqnOFY8WjGe6ZeKEg==
X-Received: by 10.112.63.136 with SMTP id g8mr2129342lbs.135.1462987333286; Wed, 11 May 2016 10:22:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 10:21:33 -0700 (PDT)
In-Reply-To: <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 13:21:33 -0400
Message-ID: <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11c3fd2a4fd0de0532944866
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/r3yK9ufXO2abhXPOfDyE1RPSK2U>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "Ray Hunter \(v6ops\)" <v6ops@globis.net>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 17:22:17 -0000

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

Hm, okay.   So perhaps you think of DNS data as being higher-layer than
routing data and numbering data?

On Wed, May 11, 2016 at 1:00 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> > I tend to think of routing protocols and election protocols as
> "intelligent",
> > but perhaps you meant something different... :)
>
> > E.g., did you mean "stateful?"
>
> No (HNCP manages quite a bit of hard state, unfortunately).  I think
> I meant "able to interpret higher-layer data", but I'm no longer sure ;-)
>
> -- Juliusz
>

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

<div dir=3D"ltr">Hm, okay. =C2=A0 So perhaps you think of DNS data as being=
 higher-layer than routing data and numbering data?</div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Wed, May 11, 2016 at 1:00 PM, Ju=
liusz 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;bor=
der-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; I tend to t=
hink of routing protocols and election protocols as &quot;intelligent&quot;=
,<br>
&gt; but perhaps you meant something different... :)<br>
<br>
&gt; E.g., did you mean &quot;stateful?&quot;<br>
<br>
</span>No (HNCP manages quite a bit of hard state, unfortunately).=C2=A0 I =
think<br>
I meant &quot;able to interpret higher-layer data&quot;, but I&#39;m no lon=
ger sure ;-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
</font></span></blockquote></div><br></div>

--001a11c3fd2a4fd0de0532944866--


From nobody Wed May 11 10:57:26 2016
Return-Path: <v6ops@globis.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 95FFF12D0BE for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:57: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, HTML_MESSAGE=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 Ext5Q1-pLWG0 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 10:57:23 -0700 (PDT)
Received: from globis01.globis.net (092-111-140-212.static.chello.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id 02E3412B04A for <homenet@ietf.org>; Wed, 11 May 2016 10:57:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 207464035E; Wed, 11 May 2016 19:57:21 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MIY74nT24aWP; Wed, 11 May 2016 19:57:15 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id CCAF74032B; Wed, 11 May 2016 19:57:10 +0200 (CEST)
Message-ID: <57337274.1040000@globis.net>
Date: Wed, 11 May 2016 19:57:08 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com>
In-Reply-To: <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090303090408060904050809"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kuvERF4Ys2SBHadIhvjRNAoaTr8>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 17:57:25 -0000

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



> Ted Lemon <mailto:mellon@fugue.com>
> 11 May 2016 18:37
>
>     > I don't like the hybrid proxy model either.  It promises the union of
>     > the problems and intersection of the functionality.  Proxying
>     flies in
>     > the face of the trend of smart devices and dumb networks.
>
>     Very well put.
>
>
> Be that as it may, Homenet in general flies in the face of that trend. 
>   And if you think about it, that trend isn't really a very smart 
> trend, because the burden it places on devices is extreme, and not all 
> devices have infinite resources to spend mapping the network and 
> figuring out how to publish their services on it.
>
But if we were to build a smart network from scratch, I also wouldn't 
start with proxies, nor maintain a distributed database in the hosts.

I'd start with letting the routers build a naming infra, together with 
defining a (simple) name registration protocol between host and on-link 
router(s) (together with conflict resolution to communicate "sorry, that 
names already taken")

And the starting point would then probably be HNCP + DNS to elect a max 
of 'n' authoritative name servers per homenet, where 'n' NS and AAAA 
records can fit it a single UDP packet.

So whether you prefer a "smart host" or "smart network" model, hybrid 
proxies seem a poor compromise.

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------090303090408060904050809
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>

</span><br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com"
 type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:mellon@fugue.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ted Lemon</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">11 
May 2016 18:37</span></font></div>    </div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div dir="ltr"><div 
class="gmail_extra"><div class="gmail_quote"><span dir="ltr"></span><blockquote
 style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" 
class="gmail_quote"><span class="">&gt; I don't like the hybrid proxy 
model either.Â  It promises the union of<br>
&gt; the problems and intersection of the functionality.Â  Proxying flies
 in<br>
&gt; the face of the trend of smart devices and dumb networks.<br>
<br>
</span>Very well put.<br></blockquote><div><br></div><div>Be that as it 
may, Homenet in general flies in the face of that trend. Â  And if you 
think about it, that trend isn't really a very smart trend, because the 
burden it places on devices is extreme, and not all devices have 
infinite resources to spend mapping the network and figuring out how to 
publish their services on it.Â </div></div></div></div>

  </div>
  <br>
</blockquote>
But if we were to build a smart network from scratch, I also wouldn't 
start with proxies, nor maintain a distributed database in the hosts.<br>
<br>
I'd start with letting the routers build a naming infra, together with 
defining a (simple) name registration protocol between host and on-link 
router(s) (together with conflict resolution to communicate "sorry, that
 names already taken")<br>
<br>
And the starting point would then probably be HNCP + DNS to elect a max 
of 'n' authoritative name servers per homenet, where 'n' NS and AAAA 
records can fit it a single UDP packet.<br>
<br>
So whether you prefer a "smart host" or "smart network" model, hybrid 
proxies seem a poor compromise.<br>
<div class="moz-signature"><br>
-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------090303090408060904050809--


From nobody Wed May 11 11:04: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 F3A3812D505 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:04: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 4zpPVquGwWBx for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:04:35 -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 343BE12D53D for <homenet@ietf.org>; Wed, 11 May 2016 11:04:17 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id u64so58289780lff.3 for <homenet@ietf.org>; Wed, 11 May 2016 11:04: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:from:date:message-id:subject:to :cc; bh=ZEeH5Kr42bFzhrAfH3dIN1SnZGAeekt9gNGW8CMzpms=; b=wh2WRfmICbCf28QnRd3qlxL7wSQG+JTiy2eeCRRAJ/8pIx5bhzsR1jo76IAE11d37A 4++NHH0fABeq6oDTEwIIiC/EwOixcDS7czzI+y4ZnWJNqoetJeUmkj1HI6wZkEM0/JiX xJfuQ7NgT2iQvm0RHvmDmBbdYu5Vx0kqZGUTT6wijJ7TQM1G1ku04xrjG6wjRlxuwT0R xROTIhbshQzcRHZGyLjfRNlaHLMjP9JbxNeclCPT+Cb2Zs7KB5/jF1rAkbvilbVcdOTX qI+ZBqdtSaIoPPLuO4QXFCSrnw3+cb1+m3SYHqowrPCbWh8CE3mL0x9wkvJzeAQGkBBW 084g==
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=ZEeH5Kr42bFzhrAfH3dIN1SnZGAeekt9gNGW8CMzpms=; b=H3GHG2RVU1o6RyWmJ2sun1o+qKd/ZHP5jPdO6FPCawMFOK4G+3SD5liMmk3aiuSHM0 NK7n4q3/vfxypLtU2J2DiQdHJAlsZaTog3n/LH9YTXE46A9a/5CG1hssQPPl9sM8+Bwn i0HiDGWbmJXeck6MAP0hG1Zrer2l6PhpfJ4ou8o0ZDuAb1OUIVpltaq7Z9iMrcn+TIVK hDR9uG21uqPhpLqQz9auD55jp2ZSdSc2nLQHbKmjCOBFQHYhVdE4bsjMKVBvymsMyEc6 OuCF4nOsco/v4qWE8XG6OONaKiEAvLlgWnXbnpxLoUx38kmtBlt+vl2Np8Z8WKK81VlG gdIg==
X-Gm-Message-State: AOPr4FW7r0yEwJ1CFFk1gPZWDrprUupzzd5bb7NSjDdF/z7sk3K5tLiekuQYFESGLa3Zt3F0RyKP/49QVT9xXA==
X-Received: by 10.112.161.41 with SMTP id xp9mr2157052lbb.133.1462989855351; Wed, 11 May 2016 11:04:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 11:03:35 -0700 (PDT)
In-Reply-To: <57337274.1040000@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 14:03:35 -0400
Message-ID: <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=001a11c26b2aa3820c053294de59
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HV7EHbT7tEavQ52ZgizMXmLMAPA>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 18:04:48 -0000

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

DNS update is pretty simple.   Any problem with using that?

I think you may be slightly conclusing "authoritative" and "primary."
There is no need to elect authoritative servers--just make them secondary
to the elected primary.   You can't have two primaries with stock
DNS--that's probably the biggest fly in the ointment.

The reason to have a hybrid proxy is because we have to support existing
devices.   Clearly it's not the right long-term solution, but we can't
force vendors to implement something new if they don't want to.


On Wed, May 11, 2016 at 1:57 PM, Ray Hunter (v6ops) <v6ops@globis.net>
wrote:

>
>
> Ted Lemon <mellon@fugue.com>
> 11 May 2016 18:37
>
>> > I don't like the hybrid proxy model either.  It promises the union of
>> > the problems and intersection of the functionality.  Proxying flies in
>> > the face of the trend of smart devices and dumb networks.
>>
>> Very well put.
>>
>
> Be that as it may, Homenet in general flies in the face of that trend.
> And if you think about it, that trend isn't really a very smart trend,
> because the burden it places on devices is extreme, and not all devices
> have infinite resources to spend mapping the network and figuring out how
> to publish their services on it.
>
> But if we were to build a smart network from scratch, I also wouldn't
> start with proxies, nor maintain a distributed database in the hosts.
>
> I'd start with letting the routers build a naming infra, together with
> defining a (simple) name registration protocol between host and on-link
> router(s) (together with conflict resolution to communicate "sorry, that
> names already taken")
>
> And the starting point would then probably be HNCP + DNS to elect a max of
> 'n' authoritative name servers per homenet, where 'n' NS and AAAA records
> can fit it a single UDP packet.
>
> So whether you prefer a "smart host" or "smart network" model, hybrid
> proxies seem a poor compromise.
>
> --
> regards,
> RayH
>
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>

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

<div dir=3D"ltr">DNS update is pretty simple. =C2=A0 Any problem with using=
 that?<div><br></div><div>I think you may be slightly conclusing &quot;auth=
oritative&quot; and &quot;primary.&quot; =C2=A0 There is no need to elect a=
uthoritative servers--just make them secondary to the elected primary. =C2=
=A0 You can&#39;t have two primaries with stock DNS--that&#39;s probably th=
e biggest fly in the ointment.</div><div><br></div><div>The reason to have =
a hybrid proxy is because we have to support existing devices. =C2=A0 Clear=
ly it&#39;s not the right long-term solution, but we can&#39;t force vendor=
s to implement something new if they don&#39;t want to.</div><div><br></div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Ma=
y 11, 2016 at 1:57 PM, Ray Hunter (v6ops) <span dir=3D"ltr">&lt;<a href=3D"=
mailto:v6ops@globis.net" target=3D"_blank">v6ops@globis.net</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">

<div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
<span>

</span><br>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"margin:30px 25px 10px 25px"><div style=3D"width:100%;border=
-top:1px solid #edeef0;padding-top:5px">   <div style=3D"display:inline-blo=
ck;white-space:nowrap;vertical-align:middle;width:49%">
   	<a href=3D"mailto:mellon@fugue.com" style=3D"color:#737f92!important;pa=
dding-right:6px;font-weight:bold;text-decoration:none!important" target=3D"=
_blank">Ted Lemon</a></div>   <div style=3D"display:inline-block;white-spac=
e:nowrap;vertical-align:middle;width:48%;text-align:right">     <font color=
=3D"#9FA2A5"><span style=3D"padding-left:6px">11=20
May 2016 18:37</span></font></div>    </div></div><span class=3D"">
  <div style=3D"color:#888888;margin-left:24px;margin-right:24px"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span dir=3D=
"ltr"></span><blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex" class=3D"gmail_quote"><span>&gt; I don&#39;t like the=
 hybrid proxy=20
model either.=C2=A0 It promises the union of<br>
&gt; the problems and intersection of the functionality.=C2=A0 Proxying fli=
es
 in<br>
&gt; the face of the trend of smart devices and dumb networks.<br>
<br>
</span>Very well put.<br></blockquote><div><br></div><div>Be that as it=20
may, Homenet in general flies in the face of that trend. =C2=A0 And if you=
=20
think about it, that trend isn&#39;t really a very smart trend, because the=
=20
burden it places on devices is extreme, and not all devices have=20
infinite resources to spend mapping the network and figuring out how to=20
publish their services on it.=C2=A0</div></div></div></div>

  </div>
  <br>
</span></blockquote>
But if we were to build a smart network from scratch, I also wouldn&#39;t=
=20
start with proxies, nor maintain a distributed database in the hosts.<br>
<br>
I&#39;d start with letting the routers build a naming infra, together with=
=20
defining a (simple) name registration protocol between host and on-link=20
router(s) (together with conflict resolution to communicate &quot;sorry, th=
at
 names already taken&quot;)<br>
<br>
And the starting point would then probably be HNCP + DNS to elect a max=20
of &#39;n&#39; authoritative name servers per homenet, where &#39;n&#39; NS=
 and AAAA=20
records can fit it a single UDP packet.<br>
<br>
So whether you prefer a &quot;smart host&quot; or &quot;smart network&quot;=
 model, hybrid=20
proxies seem a poor compromise.<span class=3D"HOEnZb"><font color=3D"#88888=
8"><br>
<div><br>
-- <br>
<div>regards,<br>
RayH<span style=3D"text-decoration:underline"><br>
  </span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm=
_medium=3Dsiglink&amp;utm_campaign=3Dreach" target=3D"_blank"><span style=
=3D"color:rgb(51,102,153)"></span></a></div>
</div>
</font></span></div>
</blockquote></div><br></div>

--001a11c26b2aa3820c053294de59--


From nobody Wed May 11 11:13: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 960D912D539 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:13: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 apuOy0-gtBBQ for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:13: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 50FD412D10A for <homenet@ietf.org>; Wed, 11 May 2016 11:13:18 -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 u4BIDG3T010789; Wed, 11 May 2016 20:13:16 +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 7A16961F9A; Wed, 11 May 2016 20: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 ZQcq2KQIwTlp; Wed, 11 May 2016 20:13:15 +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 E763F61FAB; Wed, 11 May 2016 20:13:14 +0200 (CEST)
Date: Wed, 11 May 2016 20:13:14 +0200
Message-ID: <87d1osh39h.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: <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@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]); Wed, 11 May 2016 20:13:16 +0200 (CEST)
X-Miltered: at korolev with ID 5733763C.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5733763C.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 : 5733763C.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/W9NhVIp5JW2BTnR-Db5lmSsh9iI>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 18:13:21 -0000

>> No (HNCP manages quite a bit of hard state, unfortunately). I think
>> I meant "able to interpret higher-layer data", but I'm no longer sure ;-)

> So perhaps you think of DNS data as being higher-layer than routing data
> and numbering data?

Do you not?

-- Juliusz


From nobody Wed May 11 11:22:23 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 9C8AF12D54A for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:22: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 VoLK0nSu441M for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:22:19 -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 D6C2C12D0B1 for <homenet@ietf.org>; Wed, 11 May 2016 11:22:16 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id y84so58815283lfc.0 for <homenet@ietf.org>; Wed, 11 May 2016 11:22:16 -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=vICxEQPP+bMbzFJ8jM2TgovJ3gPY4qVpm5l3fj3DXDM=; b=SSfz2p9uIhqoQIcospKD1KpUo8qAC8xLLTOpmFHlk0B1f2aIRPkynte33FoPDz+Uxt 5SCpaboE7LmG3/cfiNhFz7Q0ltPNpy5DUdtt0ia4duvNnoj6yNX9heZ5KB9x7J56hey7 ud4WJWFgouJDVruEAfkYaY/+aSIu9nHJcPjoA6sr2sbji2/KS0ENbLJ3zYFjXryjmimX uIsbAE+9Zh3oV4oa7HNvOFQvnTYAlqZ7Ig5pmKc+0zVqtVvlH9eiKdv3dvDDM18LTY8Y Q/E+w3zZ+L9lRbFt/3yX2I6JZVpFCXvGSERp70/15OYcI5bea/x2ctCInKFqzeOK5u1P eb4g==
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=vICxEQPP+bMbzFJ8jM2TgovJ3gPY4qVpm5l3fj3DXDM=; b=abwGZs6lkPmEMInrzjrQpKgyhXHKP/M/uuN6DKdmot7E17ADLoqNYJURJCC51SUnZ6 ZWk3ColrmcOrPHTpcqMYJOiwofNm3P1GsYeWvAbGkjf5xAqJLE6wBYhey3trUVgy8tKM Zqjttp/9FDqKJK57fNFBqa+zvLqwpHhdQQ0yUCm6k+5S09y0ySwLa5xeRuubTVeSIEeG xst6wfGKkoShTWSWCNZQISS4R+5IWgLxDOXK4z0dYU70TDUek6GnQNaQmEasyJKt7sfI /je4IGBbuisZcDDoN0aWupGoFuuXsy3AD9JNigpEkiJJJZxk0J4WXXPg5SlF5zRYn6JH 98xg==
X-Gm-Message-State: AOPr4FVl12o+WFlwJB1Hcc2pJzVGj6TXBB68AgVW2jA1ZHXGVWaMs8KF/KE2BDN0AdAWFmWHCxFnehQai/UOaw==
X-Received: by 10.25.145.19 with SMTP id t19mr2355855lfd.109.1462990934630; Wed, 11 May 2016 11:22:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 11:21:34 -0700 (PDT)
In-Reply-To: <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 14:21:34 -0400
Message-ID: <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a11401faaf802de0532951ef4
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/mI9ZA1uDbJztvV2GGCoLxbSHgxw>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 18:22:21 -0000

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

No.   Why are names different than numbers?

On Wed, May 11, 2016 at 2:13 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> >> No (HNCP manages quite a bit of hard state, unfortunately). I think
> >> I meant "able to interpret higher-layer data", but I'm no longer sure
> ;-)
>
> > So perhaps you think of DNS data as being higher-layer than routing data
> > and numbering data?
>
> Do you not?
>
> -- Juliusz
>

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

<div dir=3D"ltr">No. =C2=A0 Why are names different than numbers?</div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 11, 2016 =
at 2:13 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;padding-left:1ex"><span class=3D"">&g=
t;&gt; No (HNCP manages quite a bit of hard state, unfortunately). I think<=
br>
&gt;&gt; I meant &quot;able to interpret higher-layer data&quot;, but I&#39=
;m no longer sure ;-)<br>
<br>
</span><span class=3D"">&gt; So perhaps you think of DNS data as being high=
er-layer than routing data<br>
&gt; and numbering data?<br>
<br>
</span>Do you not?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
</font></span></blockquote></div><br></div>

--001a11401faaf802de0532951ef4--


From nobody Wed May 11 11:57: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 67B6712D749 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:57:37 -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 8VIU4t0kicbe for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 11:57:36 -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 DDF4412D5A3 for <homenet@ietf.org>; Wed, 11 May 2016 11:57:35 -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 u4BIvX1S022020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 May 2016 20:57:33 +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 u4BIvWii008645; Wed, 11 May 2016 20:57: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 E404A61FA5; Wed, 11 May 2016 20:57: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 Z8tg62FOwZMd; Wed, 11 May 2016 20:57: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 23E8261F9A; Wed, 11 May 2016 20:57:28 +0200 (CEST)
Date: Wed, 11 May 2016 20:57:28 +0200
Message-ID: <878tzgh17r.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: <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@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]); Wed, 11 May 2016 20:57:33 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 11 May 2016 20:57:33 +0200 (CEST)
X-Miltered: at korolev with ID 5733809D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5733809C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5733809D.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: 5733809C.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 : 5733809D.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5733809C.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dE7wF3rjqNjKSuWaYfL3__irpl4>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 18:57:37 -0000

>>> So perhaps you think of DNS data as being higher-layer than routing data
>>> and numbering data?

>> Do you not?

> No. Why are names different than numbers?

I should be able to renumber without telling my users.

-- Juliusz


From nobody Wed May 11 12:29:25 2016
Return-Path: <v6ops@globis.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 DFC2712D75C for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 12:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, 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 fxJF2XL92lU2 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 12:29:21 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C666612D7BA for <homenet@ietf.org>; Wed, 11 May 2016 12:29:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id E46EC4035E; Wed, 11 May 2016 21:29:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QyehPmmaHj9z; Wed, 11 May 2016 21:29:14 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 1475A4032B; Wed, 11 May 2016 21:29:11 +0200 (CEST)
Message-ID: <57338805.2050806@globis.net>
Date: Wed, 11 May 2016 21:29:09 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary="------------000703020809020904030003"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/62mv8YaZ73PE6DRyVMeLjT704a0>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 19:29:24 -0000

This is a multi-part message in MIME format.
--------------000703020809020904030003
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit



> Juliusz Chroboczek <mailto:jch@pps.univ-paris-diderot.fr>
> 11 May 2016 18:29
>> Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against
>> Appletalk Phase II, so if Bonjour was extended to provide an equivalent
>> function to Appletalk Phase II Zone Information Protocol = ZIP then I'd be
>> happier. That would cover concerns on non-overlapping name spaces. And
>> Appletalk NBP/ZIP resolution also prevents loops in routed networks.
>
> « The AppleTalk Zone Information Protocol (ZIP) manages the relationship
>    between network numbers and zone names. »
>
> While I could in principle go and pick a copy of Inside Appletalk at the
> library, I'd be grateful if you could explain what you have in mind.
I do happen to have a (yellowed) copy of "Inside Appletalk" on my 
bookshelf ;)

It would be new functionality to Bonjour, so strictly speaking it's out 
of scope for Homenet.

AFAIK (and I'm sure someone will keep me honest here) Appletalk strongly 
binds network numbers/cable ranges (prefixes in IPv6) to zones (logical 
groupings). Zone associations to network numbers/links are controlled by 
the Appletalk routers (not the hosts directly) and are associated with 
either a logical or physical link. The routing of name resolution 
requests to (extended) networks is based on zones. There can be multiple 
zones per network number, but the first zone is the "default zone" that 
hosts should use if they have no other preference. Host interfaces can 
only have a single network address and be a member of a single zone 
(although I've never actually seen that defined anywhere).

I leave it as a discussion point of whether that's a good model for 
Homenet, especially since IPv6 explicitly supports multiple prefixes per 
link and multiple addresses per interface per host.

Allowing a tight binding of IPv6 prefix <-> Homenet namespace zone could 
possibly work and simplify any solution for e.g. reverse resolution.

The key characteristics (that currently seem to be missing) would be:

1) a mechanism to route name resolution requests in an L3 network

2) a mechanism to prevent/ mitigate the effect of any (transient) loops 
in the name resolution infra (could be sub-function of 1)

3) a mechanism to advertise "zones" between Homenet routers.

4) a mechanism to advertise zones to hosts.

5) a field to indicate "zone membership" of a particular name/label to 
be used by hosts when advertising/resolving names.

>> I don't like the hybrid proxy model either.  It promises the union of
>> the problems and intersection of the functionality.  Proxying flies in
>> the face of the trend of smart devices and dumb networks.
>
> Very well put.
>
> -- Juliusz

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------000703020809020904030003
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>

</span><br>
<blockquote style="border: 0px none;" 
cite="mid:87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" 
href="mailto:jch@pps.univ-paris-diderot.fr" style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Juliusz Chroboczek</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">11 
May 2016 18:29</span></font></div>    </div></div>
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><blockquote
 type="cite"><pre wrap="">Bonjour is (roughly) based on Appletalk AFAIK. I've got nothing against
Appletalk Phase II, so if Bonjour was extended to provide an equivalent
function to Appletalk Phase II Zone Information Protocol = ZIP then I'd be
happier. That would cover concerns on non-overlapping name spaces. And
Appletalk NBP/ZIP resolution also prevents loops in routed networks.
</pre></blockquote><pre wrap=""><!---->
&laquo; The AppleTalk Zone Information Protocol (ZIP) manages the relationship
  between network numbers and zone names. &raquo;

While I could in principle go and pick a copy of Inside Appletalk at the
library, I'd be grateful if you could explain what you have in mind.
</pre></div>
</blockquote>
I do happen to have a (yellowed) copy of "Inside Appletalk" on my 
bookshelf ;)<br>
<br>
It would be new functionality to Bonjour, so strictly speaking it's out 
of scope for Homenet.<br>
<br>
AFAIK (and I'm sure someone will keep me honest here) Appletalk strongly
 binds network numbers/cable ranges (prefixes in IPv6) to zones (logical
 groupings). Zone associations to network numbers/links are controlled 
by the Appletalk routers (not the hosts directly) and are associated 
with either a logical or physical link. The routing of name resolution 
requests to (extended) networks is based on zones. There can be multiple
 zones per network number, but the first zone is the "default zone" that
 hosts should use if they have no other preference. Host interfaces can 
only have a single network address and be a member of a single zone 
(although I've never actually seen that defined anywhere). <br>
<br>
I leave it as a discussion point of whether that's a good model for 
Homenet, especially since IPv6 explicitly supports multiple prefixes per
 link and multiple addresses per interface per host.<br>
<br>
Allowing a tight binding of IPv6 prefix &lt;-&gt; Homenet namespace zone
 could possibly work and simplify any solution for e.g. reverse 
resolution.<br>
<br>
The key characteristics (that currently seem to be missing) would be:<br>

<br>

1) a mechanism to route name resolution requests in an L3 network<br>

<br>

2) a mechanism to prevent/ mitigate the effect of any (transient) loops 
in the name resolution infra (could be sub-function of 1)<br>

<br>

3) a mechanism to advertise "zones" between Homenet routers.<br>

<br>

4) a mechanism to advertise zones to hosts.<br>

<br>

5) a field to indicate "zone membership" of a particular name/label to 
be used by hosts when advertising/resolving names.<br>

<br>
<blockquote style="border: 0px none;" 
cite="mid:87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">
    <pre wrap="">
</pre>
<blockquote type="cite"><pre wrap="">I don't like the hybrid proxy model either.  It promises the union of
the problems and intersection of the functionality.  Proxying flies in
the face of the trend of smart devices and dumb networks.
</pre></blockquote><pre wrap=""><!---->
Very well put.

-- Juliusz
</pre></div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------000703020809020904030003--


From nobody Wed May 11 13:37: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 A624A12D558 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 13:37: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 BUdPUd1wu0cS for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 13:37:36 -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 6842312D5D0 for <homenet@ietf.org>; Wed, 11 May 2016 13:37:18 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id m64so60733894lfd.1 for <homenet@ietf.org>; Wed, 11 May 2016 13:37:18 -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=LBeAaaMEnJw+3dy1qGDgX0o0ndBnLE6zbzoyIEWcHX4=; b=bWOTNNIXO8WtDRdOfPhpZUgAeMvzjlboLoXCuAcIBkKYdas6nkfJ597mWh/iBbmJqh OG28VJHU4D8VUpqvcnAWYK5CafSctoFA+ED5IsOi+VgrLBrOOmUVIZM3tAebx3WWFasv NxmCW6K2/GEuVLocFjSBrxfNgPf2D423vIyZ3mCywTvHMxzwSWlpQiG9/OEH/T3UBETQ ZgyeUfDi2+eUsTX28r1A/RzorVwBijcftqCBzd+B3kPOvTh/RG/48tkrC7EgKINJGVxy 4JjYP/y9gBvk/5GC2XiCKLLH8Sc1i8tCerlVeDlk/KZydYrgGwPh1pPle3jLM88otFj0 q3EQ==
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=LBeAaaMEnJw+3dy1qGDgX0o0ndBnLE6zbzoyIEWcHX4=; b=SQ+oCxsfngYFhceMfHxU1cA/ACwKeaw/rdX7Mi+/MIdSaXBFpGM6tzL9Pau5GOhMNb E7XUe6JH9WKkLunHJlg8v8/u+UQ1e5yEjCetyvPAfGklEG5kUweozgtClB85yCSvJb9w DeUUgx35rLERjnh3BHxV+lh+7FfLwdN6GQUKASONsT7QpmGiBAyEEd2FCyXXjG0Nu/jF xebv+4ABcUhtsvzLDXyOp85xjRtf3NXl/p767iniKdZb9kWOvX5E5pDrPddlV1VjO5Jc 1LAGfkuuWvLNn7zFC42/ioY6HAOT7qF4j/UmfzFCAuGi0sks+dvd9VRL6g5n/9PdjXt/ lGAw==
X-Gm-Message-State: AOPr4FWZVaDGZtfnP7v80tLV8mAl/X5Exi4mJXykCpYO3rC8M+wN73mQN3B/SBL6RPbC0WMw08cUT+1Sz+2Fsw==
X-Received: by 10.25.8.204 with SMTP id 195mr2220409lfi.132.1462999037078; Wed, 11 May 2016 13:37:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 13:36:37 -0700 (PDT)
In-Reply-To: <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 16:36:37 -0400
Message-ID: <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a113ebdc4e985b40532970111
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/h8a7JP-esWF00D4tq3qa69OPtnc>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 20:37:39 -0000

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

Spoken like a network administrator.   Of course, homenets have to be able
to renumber, but there is no "I" involved.   So the naming protocol has to
work with renumbering; ideally though intra-homenet communications would
use the homenet's ULA, and so renumbering wouldn't happen other than when
two homenets merged, and then it wouldn't be urgent.

On Wed, May 11, 2016 at 2:57 PM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> >>> So perhaps you think of DNS data as being higher-layer than routing
> data
> >>> and numbering data?
>
> >> Do you not?
>
> > No. Why are names different than numbers?
>
> I should be able to renumber without telling my users.
>
> -- Juliusz
>

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

<div dir=3D"ltr">Spoken like a network administrator. =C2=A0 Of course, hom=
enets have to be able to renumber, but there is no &quot;I&quot; involved. =
=C2=A0 So the naming protocol has to work with renumbering; ideally though =
intra-homenet communications would use the homenet&#39;s ULA, and so renumb=
ering wouldn&#39;t happen other than when two homenets merged, and then it =
wouldn&#39;t be urgent.</div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, May 11, 2016 at 2:57 PM, Juliusz Chroboczek <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" target=3D"_bl=
ank">jch@pps.univ-paris-diderot.fr</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><span class=3D"">&gt;&gt;&gt; So perhaps you think of DNS d=
ata as being higher-layer than routing data<br>
&gt;&gt;&gt; and numbering data?<br>
<br>
&gt;&gt; Do you not?<br>
<br>
</span><span class=3D"">&gt; No. Why are names different than numbers?<br>
<br>
</span>I should be able to renumber without telling my users.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Juliusz<br>
</font></span></blockquote></div><br></div>

--001a113ebdc4e985b40532970111--


From nobody Wed May 11 14:06: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 1404312D0C4 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 14:06:37 -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 1KZvP7N-Bkxd for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 14:06: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 069BB12D820 for <homenet@ietf.org>; Wed, 11 May 2016 14:06:23 -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 u4BL6M5c018379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 May 2016 23: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 u4BL6JRS031109; Wed, 11 May 2016 23:06:21 +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 3562D61FA5; Wed, 11 May 2016 23:06:19 +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 Jks_yjaJQQ0T; Wed, 11 May 2016 23:06:17 +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 9EFBB61F9A; Wed, 11 May 2016 23:06:17 +0200 (CEST)
Date: Wed, 11 May 2016 23:06:17 +0200
Message-ID: <8737pogv92.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: <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@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]); Wed, 11 May 2016 23: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]); Wed, 11 May 2016 23:06:22 +0200 (CEST)
X-Miltered: at korolev with ID 57339ECE.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 57339ECB.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57339ECE.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: 57339ECB.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 : 57339ECE.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 57339ECB.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jeG6E-_-TqorOIASr1KfPybBSXU>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 11 May 2016 21:06:37 -0000

> So the naming protocol has to work with renumbering; ideally though
> intra-homenet communications would use the homenet's ULA,

That's not the point I'm making.  I mean that numbers are not user-visible,
while names obviously are.  That would seem to imply that naming is at
a higher level than either numbering or routing.  (I'm pretty sure there's
a paper by Clark on the subject somewhere.)

I'm curious why you think otherwise.

-- Juliusz


From nobody Wed May 11 17:34:07 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 40AF812D5D5 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 17:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.897
X-Spam-Level: 
X-Spam-Status: No, score=-7.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 D2scqOlEngqH for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 17:34:04 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2D2D12D5C9 for <homenet@ietf.org>; Wed, 11 May 2016 17:34:03 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id E48311FCBC4; Thu, 12 May 2016 00:34:00 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C54C7160092; Thu, 12 May 2016 00:33:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9B400160094; Thu, 12 May 2016 00:33:59 +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 kjkgDxqIx4Be; Thu, 12 May 2016 00:33:59 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 4B69C160092; Thu, 12 May 2016 00:33:59 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id B79B2489A437; Thu, 12 May 2016 10:33:56 +1000 (EST)
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
From: Mark Andrews <marka@isc.org>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87k2j0h789.wl-jch@pps.u niv-paris-diderot.fr> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com> <8737pogv92.wl-jch@pps.univ-paris-diderot.fr>
In-reply-to: Your message of "Wed, 11 May 2016 23:06:17 +0200." <8737pogv92.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 12 May 2016 10:33:56 +1000
Message-Id: <20160512003356.B79B2489A437@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wBDAlDjAqcEaaHsLuP1LCn1u7Zs>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 00:34:06 -0000

SIG(0) works fine for DDNS once you have a KEY record installed in
the DNS.

KEY can be installed on a "add if name does not exist basis" for
forward zone and add if TCP self (owner name is the matching
in-addr.arpa/ip6.arpa name of the TCP source address) is true for
the reverse zones.  This requires policy enforcement in the server
but is do able.  nameservers already have policy rules (e.g. tcp-self
has existed for years in named).  Adding more is not a hard thing
to do.

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


From nobody Wed May 11 18:54:37 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 1145C12D58E for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 18:54:29 -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 nxYU8BMll1qq for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 18:54:27 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::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 A848F12D17F for <homenet@ietf.org>; Wed, 11 May 2016 18:54:24 -0700 (PDT)
Received: by mail-lb0-x230.google.com with SMTP id jj5so4005734lbc.0 for <homenet@ietf.org>; Wed, 11 May 2016 18:54:24 -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=kmlWgxVn3IzC0d/AotDvaBsMk7ol8AA+0N2oOpPe+kY=; b=1/+RBVzb2FxDXdHYhV+o7j5lvalB9sy2GYXQo9N8OgKOuHgmus/7/RizAN/L4juy38 uXSz9BtczQrJBQWMnePN1hWO8GkwblIhg0dl8gDvxY9SdMF8xJ6u1lG1YMwuyQnqnmvE VAvV8ANKzQkxk/MEsV4EqE3yPGXF6Ebg5kE7DVhWuWwVpiUTtWvdcamBaUzAOhFonF66 xZxdkw7LyG3YNa14iU/aELN15mbU4csFrQcormBL82d333S50g7SLQPncyhu9ZmeEgw5 8MBJKppqjFsLAJCOn+SVAxCxyl9PPfNmequtgbrTSfGrTSs3KGchn9V7R6cTtZB8Kl3A X8hQ==
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=kmlWgxVn3IzC0d/AotDvaBsMk7ol8AA+0N2oOpPe+kY=; b=AU4x4+U/eYrZ8nQkhqeUi2moHBseWuV4PuWz6lQWxZseyjkjhdkahdk73iTFpGeJDW xyHB7TCArCvXap7zz2bI8Y1SPEMhP/ZZyr9m1oA1na0U1GqWWexNhivKcaJ+teHitY0T /IdIdV8ys5ugXy8AckfQgpN+7kw5YU9R1crxmAp5Ww8aE9s79D5WHdRlEcdI9seCENE2 0o6MxqC+OLVMtWmZiEJ08wB+TegxIzCs6S4uh5IcCEF1//L9/mJAAQQpbqiZYv0Xmk/u TNTJrPHnsllOhQbvZcbF7pexQaB/HYCxVexlSBxZX34xllEq803LYREINSnXSGz21Soz FzKQ==
X-Gm-Message-State: AOPr4FWgiLcf5GuDyR3uq3XgKjA+/i9Fs9PKpXchPsxelWf9qU3R483fAtEFcVTny0Rh1A0Wxn6g3fQX4YEGgA==
X-Received: by 10.112.161.41 with SMTP id xp9mr3036304lbb.133.1463018062209; Wed, 11 May 2016 18:54:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 18:53:42 -0700 (PDT)
In-Reply-To: <20160512003356.B79B2489A437@rock.dv.isc.org>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <CAPt1N1n_-XrLtqm_sKGqaHPw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com> <8737pogv92.wl-jch@pps.univ-paris-diderot.fr> <20160512003356.B79B2489A437@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 11 May 2016 21:53:42 -0400
Message-ID: <CAPt1N1nOFM5cQd+WXTtJR9-Gg=ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=001a11c26b2ae5fabf05329b6f8a
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HYUZ5d5vSt4ea3maou7uWj6Nn94>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 01:54:29 -0000

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

You don't even need SIG(0) to get the level of security that mDNS provides.
  And SIG(0) doesn't work right now, because it relies on an older version
of DNSSEC keys.   Remember the flag day?

On Wed, May 11, 2016 at 8:33 PM, Mark Andrews <marka@isc.org> wrote:

>
> SIG(0) works fine for DDNS once you have a KEY record installed in
> the DNS.
>
> KEY can be installed on a "add if name does not exist basis" for
> forward zone and add if TCP self (owner name is the matching
> in-addr.arpa/ip6.arpa name of the TCP source address) is true for
> the reverse zones.  This requires policy enforcement in the server
> but is do able.  nameservers already have policy rules (e.g. tcp-self
> has existed for years in named).  Adding more is not a hard thing
> to do.
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

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

<div dir=3D"ltr">You don&#39;t even need SIG(0) to get the level of securit=
y that mDNS provides. =C2=A0 And SIG(0) doesn&#39;t work right now, because=
 it relies on an older version of DNSSEC keys. =C2=A0 Remember the flag day=
?</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Ma=
y 11, 2016 at 8:33 PM, Mark Andrews <span dir=3D"ltr">&lt;<a href=3D"mailto=
:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><br>
SIG(0) works fine for DDNS once you have a KEY record installed in<br>
the DNS.<br>
<br>
KEY can be installed on a &quot;add if name does not exist basis&quot; for<=
br>
forward zone and add if TCP self (owner name is the matching<br>
in-addr.arpa/ip6.arpa name of the TCP source address) is true for<br>
the reverse zones.=C2=A0 This requires policy enforcement in the server<br>
but is do able.=C2=A0 nameservers already have policy rules (e.g. tcp-self<=
br>
has existed for years in named).=C2=A0 Adding more is not a hard thing<br>
to do.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><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>

--001a11c26b2ae5fabf05329b6f8a--


From nobody Wed May 11 19:57:03 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 6FD4E12D0E1 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 19:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.897
X-Spam-Level: 
X-Spam-Status: No, score=-7.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 fq9EwyH969m6 for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 19:56:59 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDFF512D0B7 for <homenet@ietf.org>; Wed, 11 May 2016 19:56:59 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D544E349422; Thu, 12 May 2016 02:56:57 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B7191160067; Thu, 12 May 2016 02:56:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A0FBD160079; Thu, 12 May 2016 02:56:57 +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 Ns8TwIKydO3x; Thu, 12 May 2016 02:56:57 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 266D7160067; Thu, 12 May 2016 02:56:57 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 884C1489E1B3; Thu, 12 May 2016 12:56:53 +1000 (EST)
To: Ted Lemon <mellon@fugue.com>
From: Mark Andrews <marka@isc.org>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <CAPt1N1n_-XrLtqm_sKGqaH Pw1q4pgKyir-bvv=cbwE_vgHDPMA@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com> <8737pogv92.wl-jch@pps.univ-paris-diderot.fr> <20160512003356.B79B2489A437@rock.dv.isc.org> <CAPt1N1nOFM5cQd+WXTtJR9-Gg=ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com>
In-reply-to: Your message of "Wed, 11 May 2016 21:53:42 -0400." <CAPt1N1nOFM5cQd+WXTtJR9-Gg=ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com>
Date: Thu, 12 May 2016 12:56:53 +1000
Message-Id: <20160512025653.884C1489E1B3@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1f8ZsDuVnpE1RZbGKfGJrsJciHY>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 02:57:01 -0000

In message <CAPt1N1nOFM5cQd+WXTtJR9-Gg=ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com>, Ted Lemon writes:
> You don't even need SIG(0) to get the level of security that mDNS provides.
> And SIG(0) doesn't work right now, because it relies on an older version
> of DNSSEC keys.   Remember the flag day?

DNSSEC depends on DNSKEY as of RFC 403[345]
SIG(0) depends on KEY.

The flag day seperated DNSSEC from other uses of KEY.  It did not
say "stop using KEY for everything" just for DNSSEC.

Mark

> On Wed, May 11, 2016 at 8:33 PM, Mark Andrews <marka@isc.org> wrote:
> 
> >
> > SIG(0) works fine for DDNS once you have a KEY record installed in
> > the DNS.
> >
> > KEY can be installed on a "add if name does not exist basis" for
> > forward zone and add if TCP self (owner name is the matching
> > in-addr.arpa/ip6.arpa name of the TCP source address) is true for
> > the reverse zones.  This requires policy enforcement in the server
> > but is do able.  nameservers already have policy rules (e.g. tcp-self
> > has existed for years in named).  Adding more is not a hard thing
> > to do.
> >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
> 
> --001a11c26b2ae5fabf05329b6f8a
> Content-Type: text/html; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr">You don&#39;t even need SIG(0) to get the level of securit=
> y that mDNS provides. =C2=A0 And SIG(0) doesn&#39;t work right now, because=
>  it relies on an older version of DNSSEC keys. =C2=A0 Remember the flag day=
> ?</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Ma=
> y 11, 2016 at 8:33 PM, Mark Andrews <span dir=3D"ltr">&lt;<a href=3D"mailto=
> :marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span> wrote:<br><b=
> lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
> #ccc solid;padding-left:1ex"><br>
> SIG(0) works fine for DDNS once you have a KEY record installed in<br>
> the DNS.<br>
> <br>
> KEY can be installed on a &quot;add if name does not exist basis&quot; for<=
> br>
> forward zone and add if TCP self (owner name is the matching<br>
> in-addr.arpa/ip6.arpa name of the TCP source address) is true for<br>
> the reverse zones.=C2=A0 This requires policy enforcement in the server<br>
> but is do able.=C2=A0 nameservers already have policy rules (e.g. tcp-self<=
> br>
> has existed for years in named).=C2=A0 Adding more is not a hard thing<br>
> to do.<br>
> <span class=3D"HOEnZb"><font color=3D"#888888"><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>
> 
> --001a11c26b2ae5fabf05329b6f8a--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed May 11 20:00: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 6234D12D0AD for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 20:00: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=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 zNVu3a8zYZ5l for <homenet@ietfa.amsl.com>; Wed, 11 May 2016 20:00:09 -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 0833F12B033 for <homenet@ietf.org>; Wed, 11 May 2016 20:00:09 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id j8so64187272lfd.2 for <homenet@ietf.org>; Wed, 11 May 2016 20:00:08 -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=7TaMGC1ZQrCt0KfvypXqIX8ySBD0SR6zOOdpBuVNJnA=; b=SAV7b3zwaKcF3ejGaBC+XU5YUAsU0k1d7JjiWCvkbJS5Kf6jplZB3zfxREv0pxaAwZ zfgWnVJ1ClNrsuE9Ll6UZLnLommQIZBXNsAbXvg8FLEhJ9IAXI85dyoJVGXBIEGxjyOH zzMierOkcJJnbKuAMf1RgQ1Ry5hr00yqX5a3WLFdGdU7XH9LPbO6PsJpzVIoc2iad8BO xXIfqcdZ2TvPOQV7ovi3pH7Xc2vxfhS5VifOfzepU+ctZmB36ve63XysktKZJ7jrfkka 1gX0CQdRUHbCxusoGEDDejwhC6FFc8cDp2P83FuFPkqyb5nGQEeg24fWGXr9O9E8sCeo 6Vuw==
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=7TaMGC1ZQrCt0KfvypXqIX8ySBD0SR6zOOdpBuVNJnA=; b=GGGDcj8OVqip1DL7ieNQiCEOdPrh+2go4iPy4nkHHfBjVAvozgonzilnVZo4Q3XGcB amhiZ0iKwHAOpPC+0Di+nQlKZ+OlzV7+ytxyAgmeguYA0qOPpVTH5rjsnDVi1gFYMQUC V4lZHwwRLTF29q9BSVcERxm2xa3Bsg79KArVcUzxqtExnSATiphF1otDz0i3tubuSsRB 4MQV5VuqF+JFrErytEoObwEghBqR6mudE57wcuF2yQM2YexXJynWPhdtvnQSIetcjBvn GqEvBYwCnUcQX6MX10d+86ZeDGBSB8xcfrrRs9nKxbSN8L5POfpS1/T2FvRu6QgSPhlR Yv+Q==
X-Gm-Message-State: AOPr4FV+o5azj11mbJpmTs2aeIGrlagzSHEUoi3F9rQBPEWA3Jaoy+8VKYDA7FdWcHfZ4Ehoofu4xK1fPd41DQ==
MIME-Version: 1.0
X-Received: by 10.25.17.234 with SMTP id 103mr3150894lfr.145.1463022007254; Wed, 11 May 2016 20:00:07 -0700 (PDT)
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 20:00:07 -0700 (PDT)
Received: by 10.25.153.135 with HTTP; Wed, 11 May 2016 20:00:07 -0700 (PDT)
In-Reply-To: <CAPt1N1=05ozMZk3h+HMSc0Js7SdzPvCB-wQhp_dRSUpNsBJxeA@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr> <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <87inykh6n9.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kSKEqjsG5KN165h6YUALbY4eeRYb3Y_9ye3mN_RSnbyg@mail.gmail.com> <87d1osh39h.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1ksB1wCEfjqCVAn_Eca4Bh5vPy3SEO3bBGOWHJfX6zXxg@mail.gmail.com> <878tzgh17r.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1kGtUGP68e44FOH6yuw0AvDmK8A4bNW+1YpXv31ywzvQw@mail.gmail.com> <8737pogv92.wl-jch@pps.univ-paris-diderot.fr> <20160512003356.B79B2489A437@rock.dv.isc.org> <CAPt1N1nOFM5cQd+WXTtJR9-Gg=ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com> <20160512025653.884C1489E1B3@rock.dv.isc.org> <CAPt1N1=05ozMZk3h+HMSc0Js7SdzPvCB-wQhp_dRSUpNsBJxeA@mail.gmail.com>
Date: Wed, 11 May 2016 23:00:07 -0400
Message-ID: <CAPt1N1mg8u97zngjdQ5=5LFcnN6gr64V3rGs20-0eyuiVDsBiA@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=001a113fb5800aa64005329c5bfe
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/KgQZaPnBrdbieYCnTE6q8h_D0Tk>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 03:00:11 -0000

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

Hm. Ok, good news. Makes the job a wee bit easier.
On May 11, 2016 10:57 PM, "Mark Andrews" <marka@isc.org> wrote:


In message <CAPt1N1nOFM5cQd+WXTtJR9-Gg=
ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com>, Ted Lemon writes:
> You don't even need SIG(0) to get the level of security that mDNS
provides.
> And SIG(0) doesn't work right now, because it relies on an older version
> of DNSSEC keys.   Remember the flag day?

DNSSEC depends on DNSKEY as of RFC 403[345]
SIG(0) depends on KEY.

The flag day seperated DNSSEC from other uses of KEY.  It did not
say "stop using KEY for everything" just for DNSSEC.

Mark

> On Wed, May 11, 2016 at 8:33 PM, Mark Andrews <marka@isc.org> wrote:
>
> >
> > SIG(0) works fine for DDNS once you have a KEY record installed in
> > the DNS.
> >
> > KEY can be installed on a "add if name does not exist basis" for
> > forward zone and add if TCP self (owner name is the matching
> > in-addr.arpa/ip6.arpa name of the TCP source address) is true for
> > the reverse zones.  This requires policy enforcement in the server
> > but is do able.  nameservers already have policy rules (e.g. tcp-self
> > has existed for years in named).  Adding more is not a hard thing
> > to do.
> >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
>
> --001a11c26b2ae5fabf05329b6f8a
> Content-Type: text/html; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> <div dir=3D"ltr">You don&#39;t even need SIG(0) to get the level of
securit=
> y that mDNS provides. =C2=A0 And SIG(0) doesn&#39;t work right now,
because=
>  it relies on an older version of DNSSEC keys. =C2=A0 Remember the flag
day=
> ?</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed,
Ma=
> y 11, 2016 at 8:33 PM, Mark Andrews <span dir=3D"ltr">&lt;<a
href=3D"mailto=
> :marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span>
wrote:<br><b=
> lockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-left:1px =
> #ccc solid;padding-left:1ex"><br>
> SIG(0) works fine for DDNS once you have a KEY record installed in<br>
> the DNS.<br>
> <br>
> KEY can be installed on a &quot;add if name does not exist basis&quot;
for<=
> br>
> forward zone and add if TCP self (owner name is the matching<br>
> in-addr.arpa/ip6.arpa name of the TCP source address) is true for<br>
> the reverse zones.=C2=A0 This requires policy enforcement in the
server<br>
> but is do able.=C2=A0 nameservers already have policy rules (e.g.
tcp-self<=
> br>
> has existed for years in named).=C2=A0 Adding more is not a hard thing<br>
> to do.<br>
> <span class=3D"HOEnZb"><font color=3D"#888888"><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>
>
> --001a11c26b2ae5fabf05329b6f8a--
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

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

<p dir=3D"ltr">Hm. Ok, good news. Makes the job a wee bit easier. </p>
<div class=3D"gmail_quote">On May 11, 2016 10:57 PM, &quot;Mark Andrews&quo=
t; &lt;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text"><br>
In message &lt;CAPt1N1nOFM5cQd+WXTtJR9-Gg=3D<a href=3D"mailto:ztyCeDqC7RRFh=
cfhzyGZX-zg@mail.gmail.com">ztyCeDqC7RRFhcfhzyGZX-zg@mail.gmail.com</a>&gt;=
, Ted Lemon writes:<br>
&gt; You don&#39;t even need SIG(0) to get the level of security that mDNS =
provides.<br>
&gt; And SIG(0) doesn&#39;t work right now, because it relies on an older v=
ersion<br>
&gt; of DNSSEC keys.=C2=A0 =C2=A0Remember the flag day?<br>
<br>
</div>DNSSEC depends on DNSKEY as of RFC 403[345]<br>
SIG(0) depends on KEY.<br>
<br>
The flag day seperated DNSSEC from other uses of KEY.=C2=A0 It did not<br>
say &quot;stop using KEY for everything&quot; just for DNSSEC.<br>
<br>
Mark<br>
<div class=3D"quoted-text"><br>
&gt; On Wed, May 11, 2016 at 8:33 PM, Mark Andrews &lt;<a href=3D"mailto:ma=
rka@isc.org">marka@isc.org</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; SIG(0) works fine for DDNS once you have a KEY record installed i=
n<br>
&gt; &gt; the DNS.<br>
&gt; &gt;<br>
&gt; &gt; KEY can be installed on a &quot;add if name does not exist basis&=
quot; for<br>
&gt; &gt; forward zone and add if TCP self (owner name is the matching<br>
&gt; &gt; in-addr.arpa/ip6.arpa name of the TCP source address) is true for=
<br>
&gt; &gt; the reverse zones.=C2=A0 This requires policy enforcement in the =
server<br>
&gt; &gt; but is do able.=C2=A0 nameservers already have policy rules (e.g.=
 tcp-self<br>
&gt; &gt; has existed for years in named).=C2=A0 Adding more is not a hard =
thing<br>
&gt; &gt; to do.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Mark Andrews, ISC<br>
&gt; &gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
&gt; &gt; PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714=
742">+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><b=
r>
&gt; &gt;<br>
&gt;<br>
</div>&gt; --001a11c26b2ae5fabf05329b6f8a<br>
&gt; Content-Type: text/html; charset=3DUTF-8<br>
&gt; Content-Transfer-Encoding: quoted-printable<br>
&gt;<br>
&gt; &lt;div dir=3D3D&quot;ltr&quot;&gt;You don&amp;#39;t even need SIG(0) =
to get the level of securit=3D<br>
&gt; y that mDNS provides. =3DC2=3DA0 And SIG(0) doesn&amp;#39;t work right=
 now, because=3D<br>
&gt;=C2=A0 it relies on an older version of DNSSEC keys. =3DC2=3DA0 Remembe=
r the flag day=3D<br>
&gt; ?&lt;/div&gt;&lt;div class=3D3D&quot;gmail_extra&quot;&gt;&lt;br&gt;&l=
t;div class=3D3D&quot;gmail_quote&quot;&gt;On Wed, Ma=3D<br>
&gt; y 11, 2016 at 8:33 PM, Mark Andrews &lt;span dir=3D3D&quot;ltr&quot;&g=
t;&amp;lt;&lt;a href=3D3D&quot;mailto=3D<br>
&gt; :<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&quot; target=3D3D&=
quot;_blank&quot;&gt;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&lt;=
/a&gt;&amp;gt;&lt;/span&gt; wrote:&lt;br&gt;&lt;b=3D<br>
&gt; lockquote class=3D3D&quot;gmail_quote&quot; style=3D3D&quot;margin:0 0=
 0 .8ex;border-left:1px =3D<br>
&gt; #ccc solid;padding-left:1ex&quot;&gt;&lt;br&gt;<br>
&gt; SIG(0) works fine for DDNS once you have a KEY record installed in&lt;=
br&gt;<br>
&gt; the DNS.&lt;br&gt;<br>
&gt; &lt;br&gt;<br>
&gt; KEY can be installed on a &amp;quot;add if name does not exist basis&a=
mp;quot; for&lt;=3D<br>
&gt; br&gt;<br>
&gt; forward zone and add if TCP self (owner name is the matching&lt;br&gt;=
<br>
&gt; in-addr.arpa/ip6.arpa name of the TCP source address) is true for&lt;b=
r&gt;<br>
&gt; the reverse zones.=3DC2=3DA0 This requires policy enforcement in the s=
erver&lt;br&gt;<br>
&gt; but is do able.=3DC2=3DA0 nameservers already have policy rules (e.g. =
tcp-self&lt;=3D<br>
&gt; br&gt;<br>
&gt; has existed for years in named).=3DC2=3DA0 Adding more is not a hard t=
hing&lt;br&gt;<br>
&gt; to do.&lt;br&gt;<br>
&gt; &lt;span class=3D3D&quot;HOEnZb&quot;&gt;&lt;font color=3D3D&quot;#888=
888&quot;&gt;&lt;br&gt;<br>
&gt; --&lt;br&gt;<br>
&gt; Mark Andrews, ISC&lt;br&gt;<br>
&gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia&lt;br&gt;<br>
&gt; PHONE: &lt;a href=3D3D&quot;tel:%2B61%202%209871%204742&quot; value=3D=
3D&quot;+61298714742&quot;&gt;+61 2=3D<br>
&gt;=C2=A0 9871 4742&lt;/a&gt;=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =
=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3D<br>
&gt; =3DA0INTERNET: &lt;a href=3D3D&quot;mailto:<a href=3D"mailto:marka@isc=
.org">marka@isc.org</a>&quot;&gt;<a href=3D"mailto:marka@isc.org">marka@isc=
.org</a>&lt;/a&gt;&lt;br&gt;<br>
&gt; &lt;/font&gt;&lt;/span&gt;&lt;/blockquote&gt;&lt;/div&gt;&lt;br&gt;&lt=
;/div&gt;<br>
&gt;<br>
&gt; --001a11c26b2ae5fabf05329b6f8a--<br>
<div class=3D"elided-text">--<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>
</div></blockquote></div>

--001a113fb5800aa64005329c5bfe--


From nobody Thu May 12 01:44:05 2016
Return-Path: <v6ops@globis.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 3736F12B04F for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 01:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, 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 chdwEeAnY4Sm for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 01:44:01 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 44B9512B02D for <homenet@ietf.org>; Thu, 12 May 2016 01:44:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1E0554033E; Thu, 12 May 2016 10:44:00 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LhQNCkkDhHh5; Thu, 12 May 2016 10:43:54 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id E7B36402E4; Thu, 12 May 2016 10:43:53 +0200 (CEST)
Message-ID: <57344249.8070907@globis.net>
Date: Thu, 12 May 2016 10:43:53 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com>
In-Reply-To: <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080106090605030902030708"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/O9kzea0rrC4T4w0LyNVJzkXBpqs>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 08:44:03 -0000

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



> Ted Lemon <mailto:mellon@fugue.com>
> 11 May 2016 20:03
> DNS update is pretty simple.   Any problem with using that?
Not with the update mechanism itself
>
> I think you may be slightly conclusing "authoritative" and "primary." 
>   There is no need to elect authoritative servers--just make them 
> secondary to the elected primary.   You can't have two primaries with 
> stock DNS--that's probably the biggest fly in the ointment.
>
Exactly.

The challenge is the Homenet requirement to support network segmentation 
and remerging.

We have multiple independent address spaces (ULA per router + GUA per 
provider), so why not multiple namespaces?

If a new router is added, a new ULA is added, together with associated 
namespace, and infra.
If a router is removed or dies, the ULA prefix expires, together with 
associated namespace and infra.

If a new ISP uplink is added, a new GUA is added, together with 
associated (upstream) (globally resolvable) namespace and infra.
If an ISP is removed or dies, the GUA expires, together with associated 
namespace and infra.

Then the namespace infra/ update server could be tightly bound to the 
device that delegates/creates it (either the homenet router, homenet 
border router, or the ISP infra)

I know people don't like DNS search lists, but they do work, and are 
widely supported. Or else a recursive resolver running on the local 
homenet router could handle the search work for the end hosts.

I also realize this creates a new challenge of how to update all of 
these various namespaces.

> The reason to have a hybrid proxy is because we have to support 
> existing devices.   Clearly it's not the right long-term solution, but 
> we can't force vendors to implement something new if they don't want to.
>
>

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------080106090605030902030708
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>

</span><br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com"
 type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:mellon@fugue.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ted Lemon</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">11 
May 2016 20:03</span></font></div>    </div></div>
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div 
dir="ltr">DNS update is pretty simple. Â  Any problem with using that?</div></div>
</blockquote>
Not with the update mechanism itself<br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com"
 type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
    <div dir="ltr"><div><br></div><div>I think you may be slightly 
conclusing "authoritative" and "primary." Â  There is no need to elect 
authoritative servers--just make them secondary to the elected primary. Â 
 You can't have two primaries with stock DNS--that's probably the 
biggest fly in the ointment.</div><div><br></div></div>
  </div>
</blockquote>
Exactly.<br>
<br>
The challenge is the Homenet requirement to support network segmentation
 and remerging.<br>
<br>
We have multiple independent address spaces (ULA per router + GUA per 
provider), so why not multiple namespaces?<br>
<br>
If a new router is added, a new ULA is added, together with associated 
namespace, and infra.<br>
If a router is removed or dies, the ULA prefix expires, together with 
associated namespace and infra.<br>
<br>
If a new ISP uplink is added, a new GUA is added, together with 
associated (upstream) (globally resolvable) namespace and infra.<br>

If an ISP is removed or dies, the GUA expires, together with associated 
namespace and infra.<br>
<br>
Then the namespace infra/ update server could be tightly bound to the 
device that delegates/creates it (either the homenet router, homenet 
border router, or the ISP infra)<br>
<br>
I know people don't like DNS search lists, but they do work, and are 
widely supported. Or else a recursive resolver running on the local 
homenet router could handle the search work for the end hosts.<br>
<br>
I also realize this creates a new challenge of how to update all of 
these various namespaces.<br>
<br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com"
 type="cite">
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">
    <div dir="ltr"><div>The reason to have a hybrid proxy is because we 
have to support existing devices. Â  Clearly it's not the right long-term
 solution, but we can't force vendors to implement something new if they
 don't want to.</div><div><br></div></div>
<div class="gmail_extra"><br>
</div></div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------080106090605030902030708--


From nobody Thu May 12 06:11:15 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 5FEF212D66C for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:11: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 hIKyiizJiUOB for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:11: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 E452B12D673 for <homenet@ietf.org>; Thu, 12 May 2016 06:11:03 -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 u4CDB13G017411; Thu, 12 May 2016 15:11:01 +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 EA0B661FA7; Thu, 12 May 2016 15:11:00 +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 ynsQlYSUocIN; Thu, 12 May 2016 15:10:56 +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 0D96A61F9A; Thu, 12 May 2016 15:10:56 +0200 (CEST)
Date: Thu, 12 May 2016 15:10:55 +0200
Message-ID: <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
In-Reply-To: <57344249.8070907@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87lh47vtpe.wl-jch@pps.univ-paris-diderot.fr> <02CF43FB-CF81-4C0C-84E1-A8DFB27B3F8C@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 12 May 2016 15:11:01 +0200 (CEST)
X-Miltered: at korolev with ID 573480E5.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573480E5.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 : 573480E5.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: <http://mailarchive.ietf.org/arch/msg/homenet/kS9XEdrZSEPPBPWivJN7DtVRhSc>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 13:11:14 -0000

If I'm reading you correctly, Ray, you're promoting unstable naming.  If
I have two routers called trurl and pirx in my network, then my printer
will becalled diablo630.pirx.home whe pirx is up, diablo630.trurl.home
when trurl is up, and either I reconfigure all of my hosts every time
I swap a router, or rely on the DNS search list being correct?

> We have multiple independent address spaces (ULA per router + GUA per
> provider),

No, we have a GUA per provider, and *optionally* a single ULA for the
whole Homenet:

      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, but none of
      which is locally generated [...]  In case multiple locally generated
      ULA prefixes are present, only the one published by the node with
      the greatest node identifier is kept

> If a new router is added, a new ULA is added,

No, that's not the case.

> If a router is removed or dies, the ULA prefix expires

Nope.  If a router dies, any ULA should remain stable, even if it's the
router who originally generated the ULA that dies:

   When a new ULA prefix is created, the prefix is selected [...] using
   the last non-deprecated ULA prefix

That's the whole point of using a ULA.


From nobody Thu May 12 06:41:52 2016
Return-Path: <v6ops@globis.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 A34B212D12F for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:41:51 -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, HTML_MESSAGE=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 SioPboMDB7hW for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:41:49 -0700 (PDT)
Received: from globis01.globis.net (092-111-140-212.static.chello.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id 848F512B00E for <homenet@ietf.org>; Thu, 12 May 2016 06:41:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 6371A4033E; Thu, 12 May 2016 15:41:48 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-fwBF9pnJ1w; Thu, 12 May 2016 15:41:45 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 1C58C402E4; Thu, 12 May 2016 15:41:45 +0200 (CEST)
Message-ID: <57348817.1090200@globis.net>
Date: Thu, 12 May 2016 15:41:43 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary="------------060503020408060808060100"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JPoAjzID6k2AgxfMAq_azojP4DE>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 13:41:51 -0000

This is a multi-part message in MIME format.
--------------060503020408060808060100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> Juliusz Chroboczek <mailto:jch@pps.univ-paris-diderot.fr>
> 12 May 2016 15:10
> If I'm reading you correctly, Ray, you're promoting unstable naming.
Not promoting. Looking at the consequences.
>    If
> I have two routers called trurl and pirx in my network, then my printer
> will becalled diablo630.pirx.home whe pirx is up, diablo630.trurl.home
> when trurl is up, and either I reconfigure all of my hosts every time
> I swap a router, or rely on the DNS search list being correct?
>
>> We have multiple independent address spaces (ULA per router + GUA per
>> provider),
actually I was thinking more along the lines of the printer being called

diablo630.default_zone.ula1.home (ULA1)

and

diablo630.default_zone.ula2.home (ULA2 if it exists)

and

diablo630.my_isp1.com (GUA1)

and

diablo630.my_isp2.net (GUA2)


simultaneously.

The DNSSL would indeed be updated automatically when the homenet 
autoconfigures, and advertised by RA.

The name registration and resolution for the various namespaces could 
run independently.
> No, we have a GUA per provider, and *optionally* a single ULA for the
> whole Homenet:
>
>        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, but none of
>        which is locally generated [...]  In case multiple locally generated
>        ULA prefixes are present, only the one published by the node with
>        the greatest node identifier is kept
Thanks for that explanation.
>> If a new router is added, a new ULA is added,
>
> No, that's not the case.
What happens if that new router has been booted stand-alone (so it 
creates its own ULA), and then joins the Homenet by being plugged in, 
and has a higher node identifier?

Shouldn't this be a voting mechanism to retain the "most popular" 
existing ULA?
>> If a router is removed or dies, the ULA prefix expires
>
> Nope.  If a router dies, any ULA should remain stable, even if it's the
> router who originally generated the ULA that dies:
>
>     When a new ULA prefix is created, the prefix is selected [...] using
>     the last non-deprecated ULA prefix
>
> That's the whole point of using a ULA.
Well even then you have the corner case of a split, stable operation, 
remerge, where one of the two ULA prefixes will disappear.

If the namespace relies in any way on the ULA, it'll change if the ULA 
changes.

If the namespace doesn't rely on the ULA, we'll likely get hit by the 
same (security) problems as mobile devices moving between disjoint 
.local networks.

Or else we have to manually configure a "Homenet root name"/ "Homenet 
identifier"?

Thoughts?

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------060503020408060808060100
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" 
href="mailto:jch@pps.univ-paris-diderot.fr" style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Juliusz Chroboczek</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">12 
May 2016 15:10</span></font></div>    </div></div>
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><pre wrap="">If I'm reading you correctly, Ray, you're promoting unstable naming.</pre></div>
</blockquote>
Not promoting. Looking at the consequences.<br>
<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
    <pre wrap="">  If
I have two routers called trurl and pirx in my network, then my printer
will becalled diablo630.pirx.home whe pirx is up, diablo630.trurl.home
when trurl is up, and either I reconfigure all of my hosts every time
I swap a router, or rely on the DNS search list being correct?

</pre>
<blockquote type="cite"><pre wrap="">We have multiple independent address spaces (ULA per router + GUA per
provider),
</pre></blockquote><pre wrap=""><!----></pre></div>
</blockquote>
actually I was thinking more along the lines of the printer being called<br>

<pre wrap="">diablo630.default_zone.ula1.home (ULA1)</pre>


and<br>

<pre wrap="">diablo630.default_zone.ula2.home (ULA2 if it exists)

and

diablo630.my_isp1.com (GUA1)

and

diablo630.my_isp2.net (GUA2)

</pre>


simultaneously.<br>

<br>

The DNSSL would indeed be updated automatically when the homenet 
autoconfigures, and advertised by RA.<br>

<br>

The name registration and resolution for the various namespaces could 
run independently.<br>

<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
    <pre wrap="">
</pre>
  </div>
</blockquote>
<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
    <pre wrap="">
No, we have a GUA per provider, and *optionally* a single ULA for the
whole Homenet:

      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, but none of
      which is locally generated [...]  In case multiple locally generated
      ULA prefixes are present, only the one published by the node with
      the greatest node identifier is kept
</pre>
  </div>
</blockquote>
Thanks for that explanation.<br>
<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
    <pre wrap="">
</pre>
<blockquote type="cite"><pre wrap="">If a new router is added, a new ULA is added,
</pre></blockquote><pre wrap=""><!---->
No, that's not the case.</pre></div>
</blockquote>
What happens if that new router has been booted stand-alone (so it 
creates its own ULA), and then joins the Homenet by being plugged in, 
and has a higher node identifier?<br>
<br>
Shouldn't this be a voting mechanism to retain the "most popular" 
existing ULA?<br>


<blockquote style="border: 0px none;" 
cite="mid:874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr" type="cite">
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><blockquote
 type="cite"><pre wrap="">If a router is removed or dies, the ULA prefix expires
</pre></blockquote><pre wrap=""><!---->
Nope.  If a router dies, any ULA should remain stable, even if it's the
router who originally generated the ULA that dies:

   When a new ULA prefix is created, the prefix is selected [...] using
   the last non-deprecated ULA prefix

That's the whole point of using a ULA.
</pre></div>
</blockquote>
Well even then you have the corner case of a split, stable operation, 
remerge, where one of the two ULA prefixes will disappear.<br>
<br>
If the namespace relies in any way on the ULA, it'll change if the ULA 
changes.<br>
<br>
If the namespace doesn't rely on the ULA, we'll likely get hit by the 
same (security) problems as mobile devices moving between disjoint 
.local networks.<br>
<br>
Or else we have to manually configure a "Homenet root name"/ "Homenet 
identifier"?<br>
<br>
Thoughts?<br>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------060503020408060808060100--


From nobody Thu May 12 06:49:01 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 B9AA212D64B for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:48: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 t9Jcmz-O9rhg for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 06:48: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 F109712D66E for <homenet@ietf.org>; Thu, 12 May 2016 06:48:50 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id m64so71993550lfd.1 for <homenet@ietf.org>; Thu, 12 May 2016 06:48: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=8nahVVrOKB/GAUBuMaDzA12TwBheWyiy4KD2s0WPjfI=; b=HTLTd3pMd37+plQkm8Z8JVxLsRwSKZokDo0btraUU28H1BuS0gBzuda7Dk70zyCfx7 EHUd/t5u801sptjNoA0n4J9Ad148QgUXQwA9jVd2XxkMWFakAOesbezzhVoIoxEPGRlp 4dbW3h4pjxmwdqD5D2ZsuY6YbhM1uy7rbdFm6eeSSmGbB8DG3b0kmGrDvR3XOat4WLv3 v4K4pPJtQAA22S19/1XqP41lj6aJRZYpCGNcVYuvtjA8E2enJxdWYppJCDJGML2TBTGe SOkc5hWJ9OjaiiN3qoEREPgTA9YXliNk2Qp0qSuSbPiVQoFJSOx0cMEyq7MFBNXnkW92 crDg==
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=8nahVVrOKB/GAUBuMaDzA12TwBheWyiy4KD2s0WPjfI=; b=nNDOqsPA2c0k9UhFFicFo6FHFNT/sq8t51SEAWhE4gOI5ieyfTIA1UyOccPH73Hpu0 sjZ6O4r6ULcBdHv7PDC22eLozVOrnGaHinLs0o8TWXNVvfxuEYZE48nJWSzXpMhc5IdU GyOlvpfS6jHMR9Pyq8kncMi6RkopawphziUglMI55ZjQlxCX69rklfNFl4pW2Y8uuoqT PEQ0mZmR7C1egonHMNu1aB/dgmw0/tlXeU9XCIkjXQT6nhUI5FcZWSUEcr8O+U1VqDGV vhyvGKH8QshKn0mO3gU3QFf5jdA7X8oLpQnONxeWosfl3tYKhod2uwhLv4JV8m3+oG4I YQvQ==
X-Gm-Message-State: AOPr4FUOf06GKN4n1X3fQNvsf07VlSoq68HZZqaidpPisozT717fJmkp7vLg6sBsPXO2h8a6xS+ETmyEV863Mw==
X-Received: by 10.25.73.212 with SMTP id w203mr3949539lfa.22.1463060929006; Thu, 12 May 2016 06:48:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Thu, 12 May 2016 06:48:09 -0700 (PDT)
In-Reply-To: <57348817.1090200@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 12 May 2016 09:48:09 -0400
Message-ID: <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=001a114b1592f572d40532a56ae3
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xhaVo4LdCAoPs5sCMDJcfsa-hlE>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 13:48:59 -0000

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

As long as the renumbering process is clean, there is no downside to
renumbering, and no reason to be careful about which ULA you ultimately
wind up with.

On Thu, May 12, 2016 at 9:41 AM, Ray Hunter (v6ops) <v6ops@globis.net>
wrote:

>
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
> 12 May 2016 15:10
>
> If I'm reading you correctly, Ray, you're promoting unstable naming.
>
> Not promoting. Looking at the consequences.
>
>   If
> I have two routers called trurl and pirx in my network, then my printer
> will becalled diablo630.pirx.home whe pirx is up, diablo630.trurl.home
> when trurl is up, and either I reconfigure all of my hosts every time
> I swap a router, or rely on the DNS search list being correct?
>
>
> We have multiple independent address spaces (ULA per router + GUA per
> provider),
>
> actually I was thinking more along the lines of the printer being called
>
> diablo630.default_zone.ula1.home (ULA1)
>
> and
>
> diablo630.default_zone.ula2.home (ULA2 if it exists)
>
> and
> diablo630.my_isp1.com (GUA1)
>
> and
> diablo630.my_isp2.net (GUA2)
>
>
> simultaneously.
>
> The DNSSL would indeed be updated automatically when the homenet
> autoconfigures, and advertised by RA.
>
> The name registration and resolution for the various namespaces could run
> independently.
>
> No, we have a GUA per provider, and *optionally* a single ULA for the
> whole Homenet:
>
>       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, but none of
>       which is locally generated [...]  In case multiple locally generated
>       ULA prefixes are present, only the one published by the node with
>       the greatest node identifier is kept
>
> Thanks for that explanation.
>
> If a new router is added, a new ULA is added,
>
> No, that's not the case.
>
> What happens if that new router has been booted stand-alone (so it creates
> its own ULA), and then joins the Homenet by being plugged in, and has a
> higher node identifier?
>
> Shouldn't this be a voting mechanism to retain the "most popular" existing
> ULA?
>
> If a router is removed or dies, the ULA prefix expires
>
> Nope.  If a router dies, any ULA should remain stable, even if it's the
> router who originally generated the ULA that dies:
>
>    When a new ULA prefix is created, the prefix is selected [...] using
>    the last non-deprecated ULA prefix
>
> That's the whole point of using a ULA.
>
> Well even then you have the corner case of a split, stable operation,
> remerge, where one of the two ULA prefixes will disappear.
>
> If the namespace relies in any way on the ULA, it'll change if the ULA
> changes.
>
> If the namespace doesn't rely on the ULA, we'll likely get hit by the same
> (security) problems as mobile devices moving between disjoint .local
> networks.
>
> Or else we have to manually configure a "Homenet root name"/ "Homenet
> identifier"?
>
> Thoughts?
>
> --
> regards,
> RayH
>
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

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

<div dir=3D"ltr">As long as the renumbering process is clean, there is no d=
ownside to renumbering, and no reason to be careful about which ULA you ult=
imately wind up with.</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Thu, May 12, 2016 at 9:41 AM, Ray Hunter (v6ops) <span dir=3D"=
ltr">&lt;<a href=3D"mailto:v6ops@globis.net" target=3D"_blank">v6ops@globis=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"margin:30px 25px 10px 25px"><div style=3D"width:100%;border=
-top:1px solid #edeef0;padding-top:5px">   <div style=3D"display:inline-blo=
ck;white-space:nowrap;vertical-align:middle;width:49%">
   	<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" style=3D"color:#737f92=
!important;padding-right:6px;font-weight:bold;text-decoration:none!importan=
t" target=3D"_blank">Juliusz Chroboczek</a></div>   <div style=3D"display:i=
nline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:r=
ight">     <font color=3D"#9FA2A5"><span style=3D"padding-left:6px">12=20
May 2016 15:10</span></font></div>    </div></div><span class=3D"">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">=
<pre>If I&#39;m reading you correctly, Ray, you&#39;re promoting unstable n=
aming.</pre></div>
</span></blockquote>
Not promoting. Looking at the consequences.<span class=3D""><br>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">
    <pre>  If
I have two routers called trurl and pirx in my network, then my printer
will becalled diablo630.pirx.home whe pirx is up, diablo630.trurl.home
when trurl is up, and either I reconfigure all of my hosts every time
I swap a router, or rely on the DNS search list being correct?

</pre>
<blockquote type=3D"cite"><pre>We have multiple independent address spaces =
(ULA per router + GUA per
provider),
</pre></blockquote><pre></pre></div>
</blockquote></span>
actually I was thinking more along the lines of the printer being called<br=
>

<pre>diablo630.default_zone.ula1.home (ULA1)</pre>


and<br>

<pre>diablo630.default_zone.ula2.home (ULA2 if it exists)

and

<a href=3D"http://diablo630.my_isp1.com" target=3D"_blank">diablo630.my_isp=
1.com</a> (GUA1)

and

<a href=3D"http://diablo630.my_isp2.net" target=3D"_blank">diablo630.my_isp=
2.net</a> (GUA2)

</pre>


simultaneously.<br>

<br>

The DNSSL would indeed be updated automatically when the homenet=20
autoconfigures, and advertised by RA.<br>

<br>

The name registration and resolution for the various namespaces could=20
run independently.<span class=3D""><br>

<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">
    <pre></pre>
  </div>
</blockquote>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">
    <pre>No, we have a GUA per provider, and *optionally* a single ULA for =
the
whole Homenet:

      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, but none of
      which is locally generated [...]  In case multiple locally generated
      ULA prefixes are present, only the one published by the node with
      the greatest node identifier is kept
</pre>
  </div>
</blockquote></span>
Thanks for that explanation.<span class=3D""><br>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">
    <pre></pre>
<blockquote type=3D"cite"><pre>If a new router is added, a new ULA is added=
,
</pre></blockquote><pre>No, that&#39;s not the case.</pre></div>
</blockquote></span>
What happens if that new router has been booted stand-alone (so it=20
creates its own ULA), and then joins the Homenet by being plugged in,=20
and has a higher node identifier?<br>
<br>
Shouldn&#39;t this be a voting mechanism to retain the &quot;most popular&q=
uot;=20
existing ULA?<span class=3D""><br>


<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"color:rgb(136,136,136);margin-left:24px;margin-right:24px">=
<blockquote type=3D"cite"><pre>If a router is removed or dies, the ULA pref=
ix expires
</pre></blockquote><pre>Nope.  If a router dies, any ULA should remain stab=
le, even if it&#39;s the
router who originally generated the ULA that dies:

   When a new ULA prefix is created, the prefix is selected [...] using
   the last non-deprecated ULA prefix

That&#39;s the whole point of using a ULA.
</pre></div>
</blockquote></span>
Well even then you have the corner case of a split, stable operation,=20
remerge, where one of the two ULA prefixes will disappear.<br>
<br>
If the namespace relies in any way on the ULA, it&#39;ll change if the ULA=
=20
changes.<br>
<br>
If the namespace doesn&#39;t rely on the ULA, we&#39;ll likely get hit by t=
he=20
same (security) problems as mobile devices moving between disjoint=20
.local networks.<br>
<br>
Or else we have to manually configure a &quot;Homenet root name&quot;/ &quo=
t;Homenet=20
identifier&quot;?<br>
<br>
Thoughts?<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<div>-- <br>
<div>regards,<br>
RayH<span style=3D"text-decoration:underline"><br>
  </span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm=
_medium=3Dsiglink&amp;utm_campaign=3Dreach" target=3D"_blank"><span style=
=3D"color:rgb(51,102,153)"></span></a></div>
</div>
</font></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>

--001a114b1592f572d40532a56ae3--


From nobody Thu May 12 08:04: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 E23CA12B022 for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 08:04: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 R8uhUyLDTRhF for <homenet@ietfa.amsl.com>; Thu, 12 May 2016 08:04: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 E2AAC12B012 for <homenet@ietf.org>; Thu, 12 May 2016 08:04:05 -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 u4CF43fl002347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 May 2016 17:04:03 +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 u4CF437R007879; Thu, 12 May 2016 17:04: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 4732C61FA5; Thu, 12 May 2016 17:04: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 cafpzFfCFFna; Thu, 12 May 2016 17:04:01 +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 AB5E361FA7; Thu, 12 May 2016 17:04:01 +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 1b0s9h-0004Bn-Gn; Thu, 12 May 2016 17:04:01 +0200
Date: Thu, 12 May 2016 17:04:01 +0200
Message-ID: <7iposrco7y.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
In-Reply-To: <57348817.1090200@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87lh44fff7.wl-jch@pps.univ-paris-diderot.fr> <48A9C52C-85BC-4123-A3ED-FB269AD03126@iki.fi> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 12 May 2016 17:04:03 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 12 May 2016 17:04:03 +0200 (CEST)
X-Miltered: at korolev with ID 57349B63.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 57349B63.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57349B63.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: 57349B63.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 : 57349B63.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 57349B63.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8Lv8EzOgDkurDL23Q_4BHXqpW8M>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 12 May 2016 15:04:08 -0000

> What happens if that new router has been booted stand-alone (so it creates
> its own ULA), and then joins the Homenet by being plugged in, and has
> a higher node identifier?

Each partition has at most one ULA.  When the partition heals, a single
ULA is retained.

> Shouldn't this be a voting mechanism to retain the "most popular" existing
> ULA?

If I read the intent correctly, HNCP assumes that partitions are an
exceptional occurrence, so when the partition heals an arbitrary ULA is
retained (the one with the higher id).

> Well even then you have the corner case of a split, stable operation,
> remerge, where one of the two ULA prefixes will disappear.

Yes.

> Thoughts?

HNCP already contains provisions for naming -- see Sections 8 and 10.5 of
RFC 7788.  The procedures described there are fairly primitive, and don't
do anything to enforce stability.  Its main flaw is that it doesn't
provide a priority field, so there is no obvious way to prefer a human-
configured name to an automatically generated one.

If partitions are indeed a rare occurrence, then what is already in
RFC 7788 should be sufficient.  If you feel that this is not good enough,
we could doubtless devise something more refined.

-- Juliusz


From nobody Thu May 12 10:39:40 2016
Return-Path: <wwwrun@rfc-editor.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 6ED9212D51B; Thu, 12 May 2016 10:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level: 
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 TIvR_TWYJUOB; Thu, 12 May 2016 10:39:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C15712D142; Thu, 12 May 2016 10:39:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 14715180005; Thu, 12 May 2016 10:38:32 -0700 (PDT)
To: tjw.ietf@gmail.com, markus.stenberg@iki.fi, cyrus@openwrt.org, pierre.pfister@darou.fr
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160512173832.14715180005@rfc-editor.org>
Date: Thu, 12 May 2016 10:38:32 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fYiRt6a51av98icM8WYJg0ZvONI>
Cc: homenet@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org, terry.manderson@icann.org
Subject: [homenet] [Errata Verified] RFC7788 (4677)
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, 12 May 2016 17:39:33 -0000

The following errata report has been verified for RFC7788,
"Home Networking Control Protocol". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7788&eid=4677

--------------------------------------
Status: Verified
Type: Technical

Reported by: Tim Wicinski <tjw.ietf@gmail.com>
Date Reported: 2016-04-26
Verified by: Terry Manderson (IESG)

Section: 8

Original Text
-------------
A network-wide
   zone is appended to all single labels or unqualified zones in order
   to qualify them. ".home" is the default; however, an administrator
   MAY configure the announcement of a Domain-Name TLV (Section 10.6)
   for the network to use a different one.

Corrected Text
--------------
A network-wide zone is appended to all single labels or unqualified 
zones in order to qualify them. 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.

Notes
-----
It may appear that the use of the label ".home" is unofficially assigning this to be added to the Special Use Domain Registry. That registry can only be updated using the process outlined in RFC6761, therefore the text identifying ".home" as the default network-wide zone is in error.

It is unclear of the IESG and the IETF in publishing this proposed standard if the intent was to use ".home" as an example or placeholder until a name can be reserved.

AD Note: A default label is a requirement for HNCP and its interoperability. As such the Homenet chosen label, ".home", is a strong candidate for the RFC6761 process. The WG will be directed to follow this process and seek (again) the consensus on the ".home" label and work with other IETF WGs as appropriate.

--------------------------------------
RFC7788 (draft-ietf-homenet-hncp-10)
--------------------------------------
Title               : Home Networking Control Protocol
Publication Date    : April 2016
Author(s)           : M. Stenberg, S. Barth, P. Pfister
Category            : PROPOSED STANDARD
Source              : Home Networking
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Fri May 13 03:45:10 2016
Return-Path: <v6ops@globis.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 C2FE512B032 for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 03:45: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, HTML_MESSAGE=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 wUIK0VY2XmWE for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 03:45:07 -0700 (PDT)
Received: from globis01.globis.net (092-111-140-212.static.chello.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id F1B7812B05E for <homenet@ietf.org>; Fri, 13 May 2016 03:45:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id C374840015; Fri, 13 May 2016 12:45:05 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YayJj_kf5YT0; Fri, 13 May 2016 12:45:03 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id E0F1140012; Fri, 13 May 2016 12:45:02 +0200 (CEST)
Message-ID: <5735B02D.8080304@globis.net>
Date: Fri, 13 May 2016 12:45:01 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net> <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com>
In-Reply-To: <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040109050703050700020404"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YaDxC6OqqGM_PF8F1S0upHdVUic>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 13 May 2016 10:45:09 -0000

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


> Ted Lemon <mailto:mellon@fugue.com>
> 12 May 2016 15:48
> As long as the renumbering process is clean, there is no downside to 
> renumbering, and no reason to be careful about which ULA you 
> ultimately wind up with.
>
So are you suggesting the Homenet (internal) namespace should be 
independent of ULA address space?

In which case

1) how do we avoid the ".local" security problem where mobile devices 
are unable to distinguish whether they've actually moved to a different 
Homenet, or whether they've stayed still and their own Homenet has just 
renumbered.

Or else

2) Does the renumbering mechanism also trigger an automatic renaming too?

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------040109050703050700020404
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><span></span><br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com"
 type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:mellon@fugue.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ted Lemon</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">12 
May 2016 15:48</span></font></div>    </div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div dir="ltr">As long as the 
renumbering process is clean, there is no downside to renumbering, and 
no reason to be careful about which ULA you ultimately wind up with.</div><div
 class="gmail_extra"><br>
</div></div>
</blockquote>
So are you suggesting the Homenet (internal) namespace should be 
independent of ULA address space?<br>
<br>
In which case<br>
<br>
1) how do we avoid the ".local" security problem where mobile devices 
are unable to distinguish whether they've actually moved to a different 
Homenet, or whether they've stayed still and their own Homenet has just 
renumbered.<br>
<br>
Or else<br>
<br>
2) Does the renumbering mechanism also trigger an automatic renaming 
too?<br>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------040109050703050700020404--


From nobody Fri May 13 06:40:55 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 B24A512D519 for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 06:40:53 -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 KiC6Rx9sxF5E for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 06:40:51 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::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 26E0A12D1E7 for <homenet@ietf.org>; Fri, 13 May 2016 06:40:43 -0700 (PDT)
Received: by mail-lb0-x236.google.com with SMTP id ww9so17268706lbc.2 for <homenet@ietf.org>; Fri, 13 May 2016 06:40:43 -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=zYdTO5CtkWruUrK6j9CTj4fs/hDlG3+AIorF0/jTSh0=; b=YhMy661zGAlgwpzhHZ338A4xX4KegTZa7TUBJZ6mHFjsoqECJJ5MYygGC8Z+ThSaF5 Ww49Cow0myIDC4Is8MlrPfoSmfRY5+2Zc3sGuwzyHWri8/tULueedWM5C+LnUT+Nx7l1 ISXI1eMM1d737rF4GJZ4pqx5KnbuyINiG2Z2iSWtHaWjqtLC6m04C7QrXTSEwBUlNQtz L30YFqmcpr1meRP/vAQ5EDHlXL9zw/QQtI78dvujF2AaykivojyeYkjsDI2mZRFI8MA4 qvnHgEQAYLMo+bnhMQp27MguWRGFthQUnfJbrvgIaal7eh235FuA3GkDNUQpWCn90s5q 3ZGQ==
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=zYdTO5CtkWruUrK6j9CTj4fs/hDlG3+AIorF0/jTSh0=; b=jTHAkLlTEsIj7dOhRAzbrZalZhNBmB8DBku2r/TLnI945IfA9oRD3UgfqVX9IUsaRi WmEpTwEA6ZGJtTXLD/Y7bL9fxEVhqejIXPi0FdIWHtKRWAuTk0UrIxhPhnn6ifSxRdeb AtLUwBafSrcUq3YPdtzWgINAdcobV+gj+CFw+aMKg4qVSqzLk77Fi6wtltjOs8l4jxIj ZbuG5NrTFgfehJCl1b9DWVZfeBdwfqUIv5ueiHuV9usKXgG9S9SVnbcqgI81W4rzcBAf sr3nVljQKxhmHWD8SA3LfMb76iqbRD8yFI/NjMaxrfBL/tS42sCGGwtJfOnykO7XY+qN Bhww==
X-Gm-Message-State: AOPr4FXphi1OWaZZHulpbxUWy4NxAjzuqaQMzXydDA3s5zoe17+T2h8rvNe8Ua23DS8gF6YUNBCK8u1NDHUwJQ==
MIME-Version: 1.0
X-Received: by 10.112.77.2 with SMTP id o2mr6484548lbw.83.1463146841325; Fri, 13 May 2016 06:40:41 -0700 (PDT)
Received: by 10.25.153.135 with HTTP; Fri, 13 May 2016 06:40:40 -0700 (PDT)
Received: by 10.25.153.135 with HTTP; Fri, 13 May 2016 06:40:40 -0700 (PDT)
In-Reply-To: <CAPt1N1m96gpEz4GXrpr+eA3OjQyhQfbAACyi83noYovE1WSx7Q@mail.gmail.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87eg9wfctc.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nq1CTMmQHFQXnaFY73SyRPKpWagiMVfrHODakbeT2Wxw@mail.gmail.com> <87a8kj3r7p.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nN+ih8xpBV_-T_JaGtbBG6d5zYqW==tph8yN_UB34NNw@mail.gmail.com> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net> <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com> <5735B02D.8080304@globis.net> <CAPt1N1kAks=pAF-rcHRGWFbWLgWN5qEPZK+-6=c4VeZRi5VHcQ@mail.gmail.com> <CAPt1N1m96gpEz4GXrpr+eA3OjQyhQfbAACyi83noYovE1WSx7Q@mail.gmail.com>
Date: Fri, 13 May 2016 09:40:40 -0400
Message-ID: <CAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=001a11c3a6f4bb585f0532b96b23
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/NJnMGaKpQwX9Ij8-cFCxPnAxEqQ>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 13 May 2016 13:40:54 -0000

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

If devices publish keys, then you can use those keys to make sure you are
still talking to them. And the dnssec validation of local names would also
work. Graceful renumbering should indeed result in DNS updates. Bear in
mind that this is graceful, so the old and new ULAs coexist for a while.
On May 13, 2016 06:45, "Ray Hunter (v6ops)" <v6ops@globis.net> wrote:


Ted Lemon <mellon@fugue.com>
12 May 2016 15:48
As long as the renumbering process is clean, there is no downside to
renumbering, and no reason to be careful about which ULA you ultimately
wind up with.

So are you suggesting the Homenet (internal) namespace should be
independent of ULA address space?

In which case

1) how do we avoid the ".local" security problem where mobile devices are
unable to distinguish whether they've actually moved to a different
Homenet, or whether they've stayed still and their own Homenet has just
renumbered.

Or else

2) Does the renumbering mechanism also trigger an automatic renaming too?

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

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

<p dir=3D"ltr">If devices publish keys, then you can use those keys to make=
 sure you are still talking to them. And the dnssec validation of local nam=
es would also work. Graceful renumbering should indeed result in DNS update=
s. Bear in mind that this is graceful, so the old and new ULAs coexist for =
a while. </p>
<div class=3D"gmail_quote">On May 13, 2016 06:45, &quot;Ray Hunter (v6ops)&=
quot; &lt;<a href=3D"mailto:v6ops@globis.net">v6ops@globis.net</a>&gt; wrot=
e:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div bgcolor=3D"#FFFFFF" text=3D"#000000"><span></span><br>
<blockquote style=3D"border:0px none" type=3D"cite">
  <div style=3D"margin:30px 25px 10px 25px"><div style=3D"width:100%;border=
-top:1px solid #edeef0;padding-top:5px">   <div style=3D"display:inline-blo=
ck;white-space:nowrap;vertical-align:middle;width:49%">
   	<a href=3D"mailto:mellon@fugue.com" style=3D"color:#737f92!important;pa=
dding-right:6px;font-weight:bold;text-decoration:none!important" target=3D"=
_blank">Ted Lemon</a></div>   <div style=3D"display:inline-block;white-spac=
e:nowrap;vertical-align:middle;width:48%;text-align:right">     <font color=
=3D"#9FA2A5"><span style=3D"padding-left:6px">12=20
May 2016 15:48</span></font></div>    </div></div><div class=3D"quoted-text=
">
  <div style=3D"color:#888888;margin-left:24px;margin-right:24px"><div dir=
=3D"ltr">As long as the=20
renumbering process is clean, there is no downside to renumbering, and=20
no reason to be careful about which ULA you ultimately wind up with.</div><=
div class=3D"gmail_extra"><br>
</div></div>
</div></blockquote>
So are you suggesting the Homenet (internal) namespace should be=20
independent of ULA address space?<br>
<br>
In which case<br>
<br>
1) how do we avoid the &quot;.local&quot; security problem where mobile dev=
ices=20
are unable to distinguish whether they&#39;ve actually moved to a different=
=20
Homenet, or whether they&#39;ve stayed still and their own Homenet has just=
=20
renumbered.<br>
<br>
Or else<br>
<br>
2) Does the renumbering mechanism also trigger an automatic renaming=20
too?<font color=3D"#888888"><br>
<br>
<div>-- <br>
<div>regards,<br>
RayH<span style=3D"text-decoration:underline"><br>
  </span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm=
_medium=3Dsiglink&amp;utm_campaign=3Dreach" target=3D"_blank"><span style=
=3D"color:rgb(51,102,153)"></span></a></div>
</div>
</font></div>
</blockquote></div>

--001a11c3a6f4bb585f0532b96b23--


From nobody Fri May 13 13:22: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 E985F12D105 for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 13:22:19 -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 QLvq7CJiyhYr for <homenet@ietfa.amsl.com>; Fri, 13 May 2016 13:22:18 -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 A5CFD12B039 for <homenet@ietf.org>; Fri, 13 May 2016 13:22:17 -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 u4DKMFki005362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <homenet@ietf.org>; Fri, 13 May 2016 22:22: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 u4DKMFEH015892 for <homenet@ietf.org>; Fri, 13 May 2016 22:22: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 587BE61F9A for <homenet@ietf.org>; Fri, 13 May 2016 22:22: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 bh300GsRS7lF for <homenet@ietf.org>; Fri, 13 May 2016 22:22: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 D708561FA7 for <homenet@ietf.org>; Fri, 13 May 2016 22:22:12 +0200 (CEST)
Date: Fri, 13 May 2016 22:22:13 +0200
Message-ID: <878tzdso7e.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]); Fri, 13 May 2016 22:22:15 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 13 May 2016 22:22:15 +0200 (CEST)
X-Miltered: at korolev with ID 57363777.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 57363777.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 57363777.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: 57363777.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 : 57363777.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 57363777.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/NcMMGpnBYtw8qwbvU4_2USF6Z2U>
Subject: [homenet] Shncpd updated to 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, 13 May 2016 20:22:20 -0000

I've just updated shncpd to follow the changes made between the draft
I had used and RFC 7788.  The consequence is that shncpd no longer
interoperates with the version of hnetd in current OpenWRT head :-/

You can work around that by using the flags

  -p 8808 -m ff02::8808

on shcnpd's command line.

-- Juliusz


From nobody Sat May 14 05:51:53 2016
Return-Path: <v6ops@globis.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 0B87812D109 for <homenet@ietfa.amsl.com>; Sat, 14 May 2016 05:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, 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 F3lRCvVoh0Qp for <homenet@ietfa.amsl.com>; Sat, 14 May 2016 05:51:50 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 27B0112B05F for <homenet@ietf.org>; Sat, 14 May 2016 05:51:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0DE7B4034B; Sat, 14 May 2016 14:51:49 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRmK6wAT0PJe; Sat, 14 May 2016 14:51:46 +0200 (CEST)
Received: from MacBook-Pro.local (178-84-244-32.dynamic.upc.nl [178.84.244.32]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 3D7DD4000F; Sat, 14 May 2016 14:51:46 +0200 (CEST)
Message-ID: <57371F60.6060605@globis.net>
Date: Sat, 14 May 2016 14:51:44 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net> <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com> <5735B02D.8080304@globis.net> <CAPt1N1kAks=pAF-rcHRGWFbWLgWN5qEPZK+-6=c4VeZRi5VHcQ@mail.gmail.com> <CAPt1N1m96gpEz4GXrpr+eA3OjQyhQfbAACyi83noYovE1WSx7Q@mail.gmail.com> <CAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com>
In-Reply-To: <CAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080803010801060107080503"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BTzyZUUaCZBGzqR4qJxo-yB0iTg>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 14 May 2016 12:51:52 -0000

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



Ted Lemon wrote:
>
> If devices publish keys, then you can use those keys to make sure you 
> are still talking to them. And the dnssec validation of local names 
> would also work. Graceful renumbering should indeed result in DNS 
> updates. Bear in mind that this is graceful, so the old and new ULAs 
> coexist for a while.
>

Sounds good.

So can we assume

1) a single ULA namespace for resolving all active ULAs, that will 
eventually converge to only containing RRs from a single ULA?

2) And that ULA namespace is disjoint from/completely independent of any 
GUA namespace?


> On May 13, 2016 06:45, "Ray Hunter (v6ops)" <v6ops@globis.net 
> <mailto:v6ops@globis.net>> wrote:
>
>
>>     Ted Lemon <mailto:mellon@fugue.com>
>>     12 May 2016 15:48
>>     As long as the renumbering process is clean, there is no downside
>>     to renumbering, and no reason to be careful about which ULA you
>>     ultimately wind up with.
>>
>     So are you suggesting the Homenet (internal) namespace should be
>     independent of ULA address space?
>
>     In which case
>
>     1) how do we avoid the ".local" security problem where mobile
>     devices are unable to distinguish whether they've actually moved
>     to a different Homenet, or whether they've stayed still and their
>     own Homenet has just renumbered.
>
>     Or else
>
>     2) Does the renumbering mechanism also trigger an automatic
>     renaming too?
>
>     -- 
>     regards,
>     RayH
>     <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------080803010801060107080503
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<span>Ted Lemon wrote:</span><br>
<blockquote 
cite="mid:%3CCAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com%3E"
 type="cite">
  <p dir="ltr">If devices publish keys, then you can use those keys to 
make sure you are still talking to them. And the dnssec validation of 
local names would also work. Graceful renumbering should indeed result 
in DNS updates. Bear in mind that this is graceful, so the old and new 
ULAs coexist for a while. </p>
</blockquote>
<br>
Sounds good.<br>
<br>
So can we assume<br>
<br>
1) a single ULA namespace for resolving all active ULAs, that will 
eventually converge to only containing RRs from a single ULA?<br>
<br>
2) And that ULA namespace is disjoint from/completely independent of any
 GUA namespace?<br>
<br>
<br>
<blockquote 
cite="mid:%3CCAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com%3E"
 type="cite">
  <div class="gmail_quote">On May 13, 2016 06:45, "Ray Hunter (v6ops)" 
&lt;<a moz-do-not-send="true" href="mailto:v6ops@globis.net">v6ops@globis.net</a>&gt;
 wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div 
bgcolor="#FFFFFF" text="#000000"><span></span><br>
<blockquote style="border:0px none" type="cite"><div style="margin:30px 
25px 10px 25px"><div style="width:100%;border-top:1px solid 
#edeef0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%">
   	<a moz-do-not-send="true" href="mailto:mellon@fugue.com" 
style="color:#737f92!important;padding-right:6px;font-weight:bold;text-decoration:none!important"
 target="_blank">Ted Lemon</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:right">
     <font color="#9FA2A5"><span style="padding-left:6px">12 
May 2016 15:48</span></font></div>    </div></div><div 
class="quoted-text">
  <div style="color:#888888;margin-left:24px;margin-right:24px"><div 
dir="ltr">As long as the 
renumbering process is clean, there is no downside to renumbering, and 
no reason to be careful about which ULA you ultimately wind up with.</div><div
 class="gmail_extra"><br>
</div></div>
</div></blockquote>
So are you suggesting the Homenet (internal) namespace should be 
independent of ULA address space?<br>
<br>
In which case<br>
<br>
1) how do we avoid the ".local" security problem where mobile devices 
are unable to distinguish whether they've actually moved to a different 
Homenet, or whether they've stayed still and their own Homenet has just 
renumbered.<br>
<br>
Or else<br>
<br>
2) Does the renumbering mechanism also trigger an automatic renaming 
too?<font color="#888888"><br>
<br>
<div>-- <br>
<div>regards,<br>
RayH<span style="text-decoration:underline"><br>
  </span><a moz-do-not-send="true" 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"
 target="_blank"><span style="color:rgb(51,102,153)"></span></a></div>
</div>
</font></div></blockquote></div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------080803010801060107080503--


From nobody Sat May 14 06:19:34 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 94A1A12D1B6 for <homenet@ietfa.amsl.com>; Sat, 14 May 2016 06:19:33 -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 tOxnph2uDcTw for <homenet@ietfa.amsl.com>; Sat, 14 May 2016 06:19:31 -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 DAFA612D1A0 for <homenet@ietf.org>; Sat, 14 May 2016 06:19:30 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id u64so100331976lff.3 for <homenet@ietf.org>; Sat, 14 May 2016 06:19:30 -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=5+DuRAm7nijIKkPY7LQxVVBMYGsRBG1Kmk2h4yyDoPA=; b=IwJewTSG9UihAtN2Mo0Ebb2Cxs/dMqiiDpabVOURXrWBzX6SE5X4slmW2TR6WU/ME+ iwYe2cm1XUX4+PxRHmB2v6jM9sKYNzd44BFsdstTlWiVGNyv0fk+I/dkBqWRMrFNY0JI qvm3/sDdjjQt5m/vbhPwh0RwuvCrQX2q/MNvBqiRphhAx6pHi4W3VAaB1yhpU+y40ora e0RMkLVsHhr72SpjOUw688hhqaDZdIQkReHGEaHzLkHj7e+RAccJz0reSixScLibGIpw rpdcJuUy+BXUXVCmn23PrBi0b6jdbrm9o541Kdp6LW//EGv3FNzraX9zW1RY0UMotF35 50hg==
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=5+DuRAm7nijIKkPY7LQxVVBMYGsRBG1Kmk2h4yyDoPA=; b=Ysn3I5ptr8tyuxH1G4Dp8kKw7lTHiZ6icL24ANreYKK8ScZyIkTowJujqi5qZQrgfs /xEeXSMa2jJ67vuCWIh69xqIFEkChd0D/HaOMtRCiR7p979OcouXUwm7gKc4GR/mAcsB W/PSHvVaU7DNZcxdM/JqEQKiGYwjMwZl2LmH0BuJP6MHabImYOKR9/yfxv/1p0zJbr6d tHwiKFWVaK04IavSkEJJu8YyBum+AXsJGyG7UuOWX826wCma8c+txANmgPud0xSZ4+Dv zpOwdV9MBjD1cRrstytULswR45Wkj7hKrd3DbQtubaO/ibpBVUmUdKWOPUNjJSzSC2Y/ jBgA==
X-Gm-Message-State: AOPr4FUjh9wLk4aOOA19JKeAwdsVf/q0ecq7rQwKaM5Jggf3iKhxmbEoXy/cIiERf2Q2AWUcjgtv0K1kRoiobA==
X-Received: by 10.25.17.234 with SMTP id 103mr8344727lfr.145.1463231968967; Sat, 14 May 2016 06:19:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Sat, 14 May 2016 06:18:49 -0700 (PDT)
In-Reply-To: <57371F60.6060605@globis.net>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <EMEW3|87dc38b1e390496e02166dafe2490d8as44D0U03tjc|ecs.soton.ac.uk|56DB4264-1769-443A-86F2-BB0BE0ED9693@ecs.soton.ac.uk> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net> <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com> <5735B02D.8080304@globis.net> <CAPt1N1kAks=pAF-rcHRGWFbWLgWN5qEPZK+-6=c4VeZRi5VHcQ@mail.gmail.com> <CAPt1N1m96gpEz4GXrpr+eA3OjQyhQfbAACyi83noYovE1WSx7Q@mail.gmail.com> <CAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com> <57371F60.6060605@globis.net>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 14 May 2016 09:18:49 -0400
Message-ID: <CAPt1N1kMtZ+TKveVxN-Lq5C4tKmBdMNy7n7zRyN0wVyQEZjE+g@mail.gmail.com>
To: "Ray Hunter (v6ops)" <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=001a113fb580bc17a00532cd3d92
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/b3nCyceXNXJqtybnc5nZYk2OOHA>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 14 May 2016 13:19:33 -0000

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

The only problem with that is that in the homenet ideally we'd like to have
local names signed and validatable via DNSSEC, and that requires that the
local namespace be global in scope, even if the names published in that
namespace are not.

On Sat, May 14, 2016 at 8:51 AM, Ray Hunter (v6ops) <v6ops@globis.net>
wrote:

>
>
> Ted Lemon wrote:
>
> If devices publish keys, then you can use those keys to make sure you are
> still talking to them. And the dnssec validation of local names would also
> work. Graceful renumbering should indeed result in DNS updates. Bear in
> mind that this is graceful, so the old and new ULAs coexist for a while.
>
>
> Sounds good.
>
> So can we assume
>
> 1) a single ULA namespace for resolving all active ULAs, that will
> eventually converge to only containing RRs from a single ULA?
>
> 2) And that ULA namespace is disjoint from/completely independent of any
> GUA namespace?
>
>
> On May 13, 2016 06:45, "Ray Hunter (v6ops)" <v6ops@globis.net> wrote:
>
>
> Ted Lemon <mellon@fugue.com>
> 12 May 2016 15:48
> As long as the renumbering process is clean, there is no downside to
> renumbering, and no reason to be careful about which ULA you ultimately
> wind up with.
>
> So are you suggesting the Homenet (internal) namespace should be
> independent of ULA address space?
>
> In which case
>
> 1) how do we avoid the ".local" security problem where mobile devices are
> unable to distinguish whether they've actually moved to a different
> Homenet, or whether they've stayed still and their own Homenet has just
> renumbered.
>
> Or else
>
> 2) Does the renumbering mechanism also trigger an automatic renaming too?
>
> --
> regards,
> RayH
>
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>
>
> --
> regards,
> RayH
>
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>

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

<div dir=3D"ltr">The only problem with that is that in the homenet ideally =
we&#39;d like to have local names signed and validatable via DNSSEC, and th=
at requires that the local namespace be global in scope, even if the names =
published in that namespace are not.</div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Sat, May 14, 2016 at 8:51 AM, Ray Hunter (v6ops=
) <span dir=3D"ltr">&lt;<a href=3D"mailto:v6ops@globis.net" target=3D"_blan=
k">v6ops@globis.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>

<div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D""><br>
<br>
<span>Ted Lemon wrote:</span><br>
<blockquote type=3D"cite">
  <p dir=3D"ltr">If devices publish keys, then you can use those keys to=20
make sure you are still talking to them. And the dnssec validation of=20
local names would also work. Graceful renumbering should indeed result=20
in DNS updates. Bear in mind that this is graceful, so the old and new=20
ULAs coexist for a while. </p>
</blockquote>
<br></span>
Sounds good.<br>
<br>
So can we assume<br>
<br>
1) a single ULA namespace for resolving all active ULAs, that will=20
eventually converge to only containing RRs from a single ULA?<br>
<br>
2) And that ULA namespace is disjoint from/completely independent of any
 GUA namespace?<span class=3D""><br>
<br>
<br>
<blockquote type=3D"cite">
  <div class=3D"gmail_quote">On May 13, 2016 06:45, &quot;Ray Hunter (v6ops=
)&quot;=20
&lt;<a href=3D"mailto:v6ops@globis.net" target=3D"_blank">v6ops@globis.net<=
/a>&gt;
 wrote:<br type=3D"attribution"><blockquote style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#=
000000"><span></span><br>
<blockquote style=3D"border:0px none" type=3D"cite"><div style=3D"margin:30=
px 25px 10px 25px"><div style=3D"width:100%;border-top:1px solid #edeef0;pa=
dding-top:5px">   <div style=3D"display:inline-block;white-space:nowrap;ver=
tical-align:middle;width:49%">
   	<a href=3D"mailto:mellon@fugue.com" style=3D"color:#737f92!important;pa=
dding-right:6px;font-weight:bold;text-decoration:none!important" target=3D"=
_blank">Ted Lemon</a></div>   <div style=3D"display:inline-block;white-spac=
e:nowrap;vertical-align:middle;width:48%;text-align:right">
     <font color=3D"#9FA2A5"><span style=3D"padding-left:6px">12=20
May 2016 15:48</span></font></div>    </div></div><div>
  <div style=3D"color:#888888;margin-left:24px;margin-right:24px"><div dir=
=3D"ltr">As long as the=20
renumbering process is clean, there is no downside to renumbering, and=20
no reason to be careful about which ULA you ultimately wind up with.</div><=
div class=3D"gmail_extra"><br>
</div></div>
</div></blockquote>
So are you suggesting the Homenet (internal) namespace should be=20
independent of ULA address space?<br>
<br>
In which case<br>
<br>
1) how do we avoid the &quot;.local&quot; security problem where mobile dev=
ices=20
are unable to distinguish whether they&#39;ve actually moved to a different=
=20
Homenet, or whether they&#39;ve stayed still and their own Homenet has just=
=20
renumbered.<br>
<br>
Or else<br>
<br>
2) Does the renumbering mechanism also trigger an automatic renaming=20
too?<font color=3D"#888888"><br>
<br>
<div>-- <br>
<div>regards,<br>
RayH<span style=3D"text-decoration:underline"><br>
  </span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm=
_medium=3Dsiglink&amp;utm_campaign=3Dreach" target=3D"_blank"><span style=
=3D"color:rgb(51,102,153)"></span></a></div>
</div>
</font></div></blockquote></div>
</blockquote>
<br>
</span><span class=3D"HOEnZb"><font color=3D"#888888"><div>-- <br>
<div>regards,<br>
RayH<span style=3D"text-decoration:underline"><br>
  </span><a href=3D"https://www.postbox-inc.com/?utm_source=3Demail&amp;utm=
_medium=3Dsiglink&amp;utm_campaign=3Dreach" target=3D"_blank"><span style=
=3D"color:rgb(51,102,153)"></span></a></div>
</div>
</font></span></div>
</blockquote></div><br></div>

--001a113fb580bc17a00532cd3d92--


From nobody Mon May 16 23:30:49 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 BFC8512D56F for <homenet@ietfa.amsl.com>; Mon, 16 May 2016 23:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level: 
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 eCBLIZ1CUr6F for <homenet@ietfa.amsl.com>; Mon, 16 May 2016 23:30:45 -0700 (PDT)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 2449412D565 for <homenet@ietf.org>; Mon, 16 May 2016 23:30:40 -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 56E14E9D049E01C9; Tue, 17 May 2016 09:30:07 +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: <878tzdso7e.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 17 May 2016 09:30:34 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5807984-1485-451D-A56D-4E79B586A428@iki.fi>
References: <878tzdso7e.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/eI7jqY8K0f8BBzpUF_cCktHv9Pk>
Cc: homenet@ietf.org
Subject: Re: [homenet] Shncpd updated to 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: Tue, 17 May 2016 06:30:48 -0000

> On 13.5.2016, at 23.22, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> I've just updated shncpd to follow the changes made between the draft
> I had used and RFC 7788.  The consequence is that shncpd no longer
> interoperates with the version of hnetd in current OpenWRT head :-/
>=20
> You can work around that by using the flags
>=20
>  -p 8808 -m ff02::8808
>=20
> on shcnpd's command line.

Hopefully the HEAD case gets resolved in a bit, as I tested and =
committed the RFC7787/7788 version to openwrt-routing yesterday.

Cheers,

-Markus=


From nobody Tue May 17 06:48:00 2016
Return-Path: <cbowers@juniper.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 6641912D5DC; Tue, 17 May 2016 06:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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=junipernetworks.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 tobbBEhO2hPU; Tue, 17 May 2016 06:47:56 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0102.outbound.protection.outlook.com [65.55.169.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC2E12D169; Tue, 17 May 2016 06:47:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SKJT+sUKGm/DVAWcnoi/PLc22/doeS8psKuZaqlTc6I=; b=aoLEFvnL7V/DJe+V08EPF1BaYVncmCoGFGSLFCxfCtnNfO/N7BdHGdFwasmdKFEgUwfWd7rRPJhVE7n8edSuqQMvzcmwOnvt3R19glvJZAyQF282hvtei4kIfVJav4GCtCrGSHcPRt3xQWHIgyR1tmAeGCuEtGxNmbH6NUduHvM=
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com (10.160.35.143) by BLUPR0501MB1043.namprd05.prod.outlook.com (10.160.35.142) with Microsoft SMTP Server (TLS) id 15.1.492.11; Tue, 17 May 2016 13:47:54 +0000
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) by BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) with mapi id 15.01.0492.020; Tue, 17 May 2016 13:47:55 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: RTGWG Virtual Interim Meeting: May 31, 2016
Thread-Index: AdGlkFH1140hKmcyTVCsepgcooS0TwKsQqqw
Date: Tue, 17 May 2016 13:47:54 +0000
Message-ID: <BLUPR0501MB1044F7F8AFF154B542AD2728A9480@BLUPR0501MB1044.namprd05.prod.outlook.com>
References: <BLUPR0501MB104486BB670240E97CD18976A97B0@BLUPR0501MB1044.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR0501MB104486BB670240E97CD18976A97B0@BLUPR0501MB1044.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.239.14]
x-ms-office365-filtering-correlation-id: 23ab07d1-cafa-481f-09d4-08d37e59d92b
x-microsoft-exchange-diagnostics: 1; BLUPR0501MB1043; 5:nXIRB9BTFZDS+r/5/fDdiR+nVEEQKhHHe254UPyqsAXlJ+t4h5Dixw/tFM5wU+/Gcvo0RWjEiqNlzOQ73xAshxQKrW78OGcsXQlNL7Nt2skx1qLsrYB4+LsLm4Qc85kDylLBQ/tWU6Cyh99LdqwXqQ==; 24:FhlCPYQMSg7sEpfyC7yTsAVhLkfdulmM1gzq6I0OLzJYybnBqgrwhnphNaM6hUYwnIQvDJGT7ReEb1WXDHMDSo+oBKanx28JNR13+9+A3pY=; 7:dTtGTAztlnKuVUeXVTybAbE4GrGvtuPq+QV/0WzMIZbCzgiWRMLiJcwGoYVkTW2xW1QIT8yt94Ijy8chpBCKlxvF8z5ZjbObf6LqbVH0sp+b51rIB0KsJKamM51HxCUGnIpKxJ5iSvIq1g5PT3sQMIdahmKen64FoafItOPz5B8IJumOE+CcHoPgME5X67Qu
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB1043;
x-microsoft-antispam-prvs: <BLUPR0501MB1043377AE4FB250D90A50106A9480@BLUPR0501MB1043.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026);  SRVR:BLUPR0501MB1043; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0501MB1043; 
x-forefront-prvs: 0945B0CC72
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(243025005)(13464003)(377454003)(54356999)(87936001)(10400500002)(92566002)(76176999)(76576001)(2501003)(50986999)(5003600100002)(122556002)(586003)(102836003)(2906002)(2950100001)(77096005)(2900100001)(3846002)(8936002)(19580405001)(33656002)(19580395003)(66066001)(1220700001)(86362001)(5002640100001)(3480700004)(4326007)(15975445007)(6116002)(5004730100002)(189998001)(5008740100001)(110136002)(3660700001)(1730700003)(16799955002)(551544002)(5640700001)(2351001)(99286002)(9686002)(74316001)(3280700002)(81166006)(8676002)(450100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0501MB1043; H:BLUPR0501MB1044.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 May 2016 13:47:54.8945 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB1043
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vAK92aK1OQ8uoL2PuwmyCB1qNkc>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtgwg-ads@ietf.org" <rtgwg-ads@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [homenet] RTGWG Virtual Interim Meeting: May 31, 2016
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, 17 May 2016 13:47:58 -0000

RTGWG,

We have posted the tentative agenda for the RTGWG Virtual Interim=20
on Tuesday, May 31.  It can be found at:
https://www.ietf.org/proceedings/interim/2016/05/31/rtgwg/agenda/agenda-int=
erim-2016-rtgwg-1

Thanks to everyone who volunteered to present.  We should have a very=20
interesting set of presentations and discussions.

Here is the iCalendar invite as well:
https://ietf.webex.com/ietf/j.php?MTID=3Dm4ab707a77ed821f6978b2614f15cff96

Thanks,
Chris and Jeff

-----Original Message-----
From: Chris Bowers [mailto:cbowers@juniper.net]=20
Sent: Wednesday, May 04, 2016 10:11 AM
To: rtgwg@ietf.org; v6ops@ietf.org; homenet@ietf.org; ipv6@ietf.org; routin=
g-discussion@ietf.org
Cc: rtgwg-chairs@ietf.org; rtgwg-ads@ietf.org
Subject: RTGWG Virtual Interim Meeting: May 31, 2016

RTGWG,=20

RTGWG will hold a virtual interim meeting on Tuesday May 31, 2016 from=20
10:00-12:00 Eastern Daylight Time (14:00-16:00 UTC).=20

The virtual interim will focus on the problem of ipv6 multi-homing with=20
provider-assigned addressing without NAT, and a proposed solution for=20
this problem, destination/source routing.=20

We have contacted several potential presenters based on the discussion=20
of this topic in Buenos Aires and on the RTGWG list and in v6ops. If you=20
are interested in presenting at this virtual interim and we have not=20
already contacted you, please contact us at rtgwg-chairs@ietf.org. We=20
are particularly interested in hearing from enterprises and service=20
providers, who are the ones affected by this problem and would need to=20
deploy and operate any solution we come up with.=20

A detailed agenda will be posted to the rtgwg mailing list at least a=20
week before the meeting.

This initial announcement is being posted to rtgwg, v6ops, homenet,=20
6man, and routing-discussion mailing lists. We only plan to post=20
follow-up email related to this virtual interim to the rtgwg list, so=20
please subscribe to the rtgwg mailing list if you are interested in=20
following this.

The WebEx details are as follows:

RTGWG Virtual Interim Meeting=20
Tuesday, May 31, 2016=20
10:00 am  |  Eastern Daylight Time (New York, GMT-04:00)  |  2 hrs=20

Meeting link:
https://ietf.webex.com/ietf/j.php?MTID=3Dma9394d256b2331260bd5416dc08fb5bd

Meeting number: 648 728 108=20
Meeting password:interim1

Join by phone (US/Canada): 1-650-479-3208

International dial-in (PDF):=20
<http://www.webex.com/pdf/tollfree_restrictions.pdf>

Thanks,
Chris and Jeff


From nobody Tue May 17 08:31:45 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 06EF412D1D8 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 08:31:45 -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 2PbY2Qnw5Ceb for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 08:31:42 -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 8190712B04E for <homenet@ietf.org>; Tue, 17 May 2016 08:31:42 -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 u4HFVe1b018457 for <homenet@ietf.org>; Tue, 17 May 2016 17:31:40 +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 BEE4661FA8 for <homenet@ietf.org>; Tue, 17 May 2016 17:31:40 +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 wevCb62Rbqx2 for <homenet@ietf.org>; Tue, 17 May 2016 17:31:39 +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 39F7C61F9D for <homenet@ietf.org>; Tue, 17 May 2016 17:31:38 +0200 (CEST)
Date: Tue, 17 May 2016 17:31:39 +0200
Message-ID: <87wpms8zvo.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, 17 May 2016 17:31:40 +0200 (CEST)
X-Miltered: at korolev with ID 573B395C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573B395C.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 : 573B395C.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: <http://mailarchive.ietf.org/arch/msg/homenet/M1iWXeIw5hHkWn_cy6J9DHlqEjk>
Subject: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 15:31:45 -0000

Hi,

I just received a bug report for shncpd from somebody who noted that
shncpd's DHCPv4 server will happily assign addresses a.b.c.0 and a.b.c.255
to clients.  That's obviously broken.

Which addresses must be avoided, for both v4 and v6?  I'm already setting
the g and u bits in modified EUI-64 to 0 (silly as it is), what else
should I take care of?

-- Juliusz


From nobody Tue May 17 08:55:16 2016
Return-Path: <touch@isi.edu>
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 3F38B12DA33 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 08:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 OkL4TVhN7O5A for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 08:55:13 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 BBA2E12DA32 for <homenet@ietf.org>; Tue, 17 May 2016 08:55:13 -0700 (PDT)
Received: from [192.168.1.130] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u4HFsW4R019621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 May 2016 08:54:43 -0700 (PDT)
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <1EB127FA-8E52-4288-AEA2-E76006CAC4E7@isi.edu>
X-Mailer: iPad Mail (13E238)
From: Joe Touch <touch@isi.edu>
Date: Tue, 17 May 2016 08:54:31 -0700
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/aBxKw8ZYictdX96JAgEeujR5t44>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 15:55:15 -0000

> On May 17, 2016, at 8:31 AM, Juliusz Chroboczek <jch@pps.univ-paris-didero=
t.fr> wrote:
>=20
> Hi,
>=20
> I just received a bug report for shncpd from somebody who noted that
> shncpd's DHCPv4 server will happily assign addresses a.b.c.0 and a.b.c.255=

> to clients.  That's obviously broken.

Not since 1993 and RFC 1519, depending on the subnet mask.

See also RFC 3021.

> Which addresses must be avoided, for both v4 and v6?

All 0's and all 1's within a subnet range except for /31 in IPv4.

I don't think there are prohibited or reserved interface or group IDs in IPv=
6.=20

Specific addresses and ranges for both, but I think that's a different issue=
.

Joe

>  I'm already setting
> the g and u bits in modified EUI-64 to 0 (silly as it is), what else
> should I take care of?
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Tue May 17 09:02:13 2016
Return-Path: <roland.bless@kit.edu>
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 9DA9912DA2A for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 N08dU88CmW0d for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:02:10 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.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 BB71312DA33 for <homenet@ietf.org>; Tue, 17 May 2016 09:02:01 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  iface 141.3.10.81 id 1b2hRX-00020u-6g; Tue, 17 May 2016 18:01:59 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id 1BB21B00299; Tue, 17 May 2016 18:01:59 +0200 (CEST)
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
Message-ID: <573B4076.304@kit.edu>
Date: Tue, 17 May 2016 18:01:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1463500919.
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/G5dlfgTJI76Vs0uiMZpAeVUM1v8>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 16:02:12 -0000

Hi,

> Which addresses must be avoided, for both v4 and v6?  I'm already setting
> the g and u bits in modified EUI-64 to 0 (silly as it is), what else
> should I take care of?

https://tools.ietf.org/html/rfc5453
provides an answer w.r.t. IPv6.

https://tools.ietf.org/html/rfc7136
is probably also of interest.

Regards,
 Roland



From nobody Tue May 17 09:35:22 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 D82B512DACC for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:35: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 HJiVgGZQba_l for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:35:19 -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 4645B12DAE1 for <homenet@ietf.org>; Tue, 17 May 2016 09:35:18 -0700 (PDT)
Received: from [46.227.151.81] (port=53452 helo=rays-mbp.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 1b2hxi-0006Nn-98 (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Tue, 17 May 2016 17:35:14 +0100
To: homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk>
Date: Tue, 17 May 2016 17:35:16 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QkiqRRjVSMX3tiU9Skg--bwWbiQ>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 16:35:21 -0000

On 17/05/2016 16:31, Juliusz Chroboczek wrote:

> I just received a bug report for shncpd from somebody who noted that
> shncpd's DHCPv4 server will happily assign addresses a.b.c.0 and a.b.c.255
> to clients.  That's obviously broken.

As others have pointed out, that's actually perfectly legal.

However some operators have (had?) "classful" firewall rules that
prohibit packets that come from IP addresses that would have been
considered a broadcast address in a pre-CIDR world.

This very problem bit me on the backside back in about 2001 when I had
to update the RADIUS server I had written to prevent it from issuing .0
and .255 because my DSL customers getting assigned those addresses
couldn't reach Microsoft's website.

Ray


From nobody Tue May 17 09:45:57 2016
Return-Path: <touch@isi.edu>
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 A4BE912D70C for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 fQuTPzkaD-fI for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:45:54 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 DE8D512B074 for <homenet@ietf.org>; Tue, 17 May 2016 09:45:54 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u4HGjQkq016877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 17 May 2016 09:45:27 -0700 (PDT)
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <1EB127FA-8E52-4288-AEA2-E76006CAC4E7@isi.edu>
From: Joe Touch <touch@isi.edu>
Message-ID: <573B4AA4.8080002@isi.edu>
Date: Tue, 17 May 2016 09:45:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <1EB127FA-8E52-4288-AEA2-E76006CAC4E7@isi.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u4HGjQkq016877
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/b7PtVKjjZNMKgdnT0gQnehdkip4>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 16:45:56 -0000

On 5/17/2016 8:54 AM, Joe Touch wrote:
>
>> On May 17, 2016, at 8:31 AM, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>>
>> Hi,
>>
>> I just received a bug report for shncpd from somebody who noted that
>> shncpd's DHCPv4 server will happily assign addresses a.b.c.0 and a.b.c.255
>> to clients.  That's obviously broken.
> Not since 1993 and RFC 1519, depending on the subnet mask.
>
> See also RFC 3021.
>
>> Which addresses must be avoided, for both v4 and v6?
> All 0's and all 1's within a subnet range except for /31 in IPv4.
>
> I don't think there are prohibited or reserved interface or group IDs in IPv6. 

I stand corrected:

On 5/17/2016 9:01 AM, Bless, Roland (TM) wrote:
> https://tools.ietf.org/html/rfc5453
> provides an answer w.r.t. IPv6.
>
> https://tools.ietf.org/html/rfc7136
> is probably also of interest.
>
> Regards,
>  Roland

That's a useful pointer, but those two docs aren't the whole story
apparently. The full registry, as created by RFC5354, is here:

http://www.iana.org/assignments/ipv6-interface-ids/ipv6-interface-ids.xhtml#ipv6-interface-ids-1

It's more than I had originally expected and includes all 0s, but not
all 1's.

Joe

>
> Specific addresses and ranges for both, but I think that's a different issue.
>
> Joe
>
>>  I'm already setting
>> the g and u bits in modified EUI-64 to 0 (silly as it is), what else
>> should I take care of?
>>
>> -- Juliusz
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet


From nobody Tue May 17 09:50:40 2016
Return-Path: <touch@isi.edu>
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 610A812D723 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 JB3bc_4yYq5C for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 09:50:37 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 97A4012D72A for <homenet@ietf.org>; Tue, 17 May 2016 09:50:28 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u4HGnfXp017358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 17 May 2016 09:49:43 -0700 (PDT)
To: Ray Bellis <ray@bellis.me.uk>, homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <573B4BA3.9020709@isi.edu>
Date: Tue, 17 May 2016 09:49:39 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u4HGnfXp017358
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kOErxaj8loqmVxqr5AQkL7vyLcY>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 16:50:38 -0000

On 5/17/2016 9:35 AM, Ray Bellis wrote:
> However some operators have (had?) "classful" firewall rules that
> prohibit packets that come from IP addresses that would have been
> considered a broadcast address in a pre-CIDR world.

It's been 23 years since pre-CIDR and 15 years since you experienced
this error.

If we can't assume a fix here, then we can't assume any of the IPv6
reserved IDs are actually reserved either - they could easily be in use
by legacy equipment.

I.e,, the Postel principle applies here:

    - avoid assigning these addresses
    - test your equipment to ensure that they allow these addresses
correctly

If only we had compliance testing (again)....

Joe


From nobody Tue May 17 13:13:48 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 4F8F212DDB9 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:13:46 -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 OREUES3v4JHR for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:13:44 -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 1F2B112DDBA for <homenet@ietf.org>; Tue, 17 May 2016 13:13:42 -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 u4HKDeQx027833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 May 2016 22:13:41 +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 u4HKDeTV024294; Tue, 17 May 2016 22:13:40 +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 524D261FA6; Tue, 17 May 2016 22:13:40 +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 sR0IxAz7fRrp; Tue, 17 May 2016 22:13:39 +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 AF97B61FA1; Tue, 17 May 2016 22:13:38 +0200 (CEST)
Date: Tue, 17 May 2016 22:13:38 +0200
Message-ID: <87futg8mtp.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <1EB127FA-8E52-4288-AEA2-E76006CAC4E7@isi.edu>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <1EB127FA-8E52-4288-AEA2-E76006CAC4E7@isi.edu>
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, 17 May 2016 22:13:41 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 17 May 2016 22:13:40 +0200 (CEST)
X-Miltered: at korolev with ID 573B7B74.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 573B7B74.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573B7B74.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: 573B7B74.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 : 573B7B74.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 573B7B74.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Fdgrd6nIcuu2rGoZDJ2pAOFhRGI>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 20:13:47 -0000

>> I just received a bug report for shncpd from somebody who noted that
>> shncpd's DHCPv4 server will happily assign addresses a.b.c.0 and a.b.c.255
>> to clients.  That's obviously broken.

> Not since 1993 and RFC 1519, depending on the subnet mask.

Right.  I was thinking of a /24, sorry for not being more precise.

-- Juliusz


From nobody Tue May 17 13:14:52 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 D8B6012DDBC for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:14:51 -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 umKUeH95aUpb for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:14: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 902ED12DDB8 for <homenet@ietf.org>; Tue, 17 May 2016 13:14:50 -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 u4HKEnFw028148; Tue, 17 May 2016 22:14:49 +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 0CFA161FA1; Tue, 17 May 2016 22:14:49 +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 6yRFLKWybtlU; Tue, 17 May 2016 22:14:47 +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 382CC61F9D; Tue, 17 May 2016 22:14:47 +0200 (CEST)
Date: Tue, 17 May 2016 22:14:47 +0200
Message-ID: <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
In-Reply-To: <573B4076.304@kit.edu>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu>
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, 17 May 2016 22:14:49 +0200 (CEST)
X-Miltered: at korolev with ID 573B7BB9.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573B7BB9.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 : 573B7BB9.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: <http://mailarchive.ietf.org/arch/msg/homenet/QJpmX6ilaEzqNbsbeNJS0t7r_O8>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 20:14:52 -0000

> https://tools.ietf.org/html/rfc5453
> provides an answer w.r.t. IPv6.

Do I need to avoid these addresses when assigning a /128 or a /127?

-- Juliusz


From nobody Tue May 17 13:37:23 2016
Return-Path: <touch@isi.edu>
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 3956A12DDC5 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 t5XD6KtQQRUk for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 13:37:21 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 20D7E12DDBC for <homenet@ietf.org>; Tue, 17 May 2016 13:37:21 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u4HKavDH008427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 17 May 2016 13:37:01 -0700 (PDT)
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "Bless, Roland (TM)" <roland.bless@kit.edu>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu> <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
From: Joe Touch <touch@isi.edu>
Message-ID: <512f684a-58ad-dcca-dd7f-c79006aa7f73@isi.edu>
Date: Tue, 17 May 2016 13:36:57 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_XG6sSxSTkxx8EJGi001CChw2Hk>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 20:37:22 -0000

On 5/17/2016 1:14 PM, Juliusz Chroboczek wrote:
>> https://tools.ietf.org/html/rfc5453
>> provides an answer w.r.t. IPv6.
> 
> Do I need to avoid these addresses when assigning a /128 or a /127?

Yes - these are reserved IDs. You need to avoid any IPv6 address that
would be the result of using these values as the ID portion.

Joe


From nobody Tue May 17 14:15:25 2016
Return-Path: <roland.bless@kit.edu>
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 CEE0412D9DD for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 14:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 UxV-JSc3rg6J for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 14:15:21 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.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 975FE12DA10 for <homenet@ietf.org>; Tue, 17 May 2016 14:15:20 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  iface 141.3.10.81 id 1b2mKl-0005Pc-4Y; Tue, 17 May 2016 23:15:19 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id E726FB003AA; Tue, 17 May 2016 23:15:18 +0200 (CEST)
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu> <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
Message-ID: <573B89E6.4050605@kit.edu>
Date: Tue, 17 May 2016 23:15:18 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
In-Reply-To: <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1463519719.
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/X4u46T9ObrvRt3CnBSwrMElVaug>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 21:15:24 -0000

Hi Juliusz,

On 17.05.2016 at 22:14 Juliusz Chroboczek wrote:
>> https://tools.ietf.org/html/rfc5453
>> provides an answer w.r.t. IPv6.
> 
> Do I need to avoid these addresses when assigning a /128 or a /127?

Yes, especially the subnet router anycast IID 0000:0000:0000:0000
is widely used and may cause problems if assigned to hosts.
However, as Joe pointed out, the full registry is here:
http://www.iana.org/assignments/ipv6-interface-ids/ipv6-interface-ids.xhtml#ipv6-interface-ids-1

Regards,
 Roland


From nobody Tue May 17 14:25: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 467FD12D9D5 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 14:25: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 JTYv2XO7XZ7k for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 14:25: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 8E3CA12D0BE for <homenet@ietf.org>; Tue, 17 May 2016 14:25:09 -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 u4HLP71D014432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 May 2016 23:25: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 u4HLP7lZ006629; Tue, 17 May 2016 23:25: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 5FAC161F9D; Tue, 17 May 2016 23:25: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 Dg1ad3qSy4Ha; Tue, 17 May 2016 23:25:02 +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 8EBD661FA2; Tue, 17 May 2016 23:25:01 +0200 (CEST)
Date: Tue, 17 May 2016 23:25:01 +0200
Message-ID: <87bn448jiq.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <512f684a-58ad-dcca-dd7f-c79006aa7f73@isi.edu>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu> <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr> <512f684a-58ad-dcca-dd7f-c79006aa7f73@isi.edu>
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, 17 May 2016 23:25:08 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 17 May 2016 23:25:07 +0200 (CEST)
X-Miltered: at korolev with ID 573B8C33.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 573B8C33.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573B8C33.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: 573B8C33.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 : 573B8C33.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 573B8C33.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/-fiF6so4-VJ5rkipAaLlZXpLC2g>
Cc: homenet@ietf.org, "Bless, Roland \(TM\)" <roland.bless@kit.edu>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 21:25:20 -0000

> Yes - these are reserved IDs. You need to avoid any IPv6 address that
> would be the result of using these values as the ID portion.

I see, thanks to both of you.

-- Juliusz


From nobody Tue May 17 15:21:50 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 04E0612DAB0 for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 15:21:49 -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 r-TEXJESVxHB for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 15:21:47 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::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 5117512DAAC for <homenet@ietf.org>; Tue, 17 May 2016 15:21:47 -0700 (PDT)
Received: by mail-pa0-x22d.google.com with SMTP id xk12so10672407pac.0 for <homenet@ietf.org>; Tue, 17 May 2016 15:21:47 -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=Z9iHbuK6+dWZwZoa3DAio1jdg/vqz+Uu5I6b69DaVdw=; b=0y3pnx/8deoT0gZ64fUgVMbpUwxnYXGcjlJdZJMEIvQJ4ZDDbC2Q2Afi+VVWcRjTAy tC//idOf//3/vAoZNwRMXo7vyU50CTL8fiztltMx5nrBUUbjOdp/YgQbBBBinUYhJJ+H aE+hssO2q/WnP23iokFEi3Hch+qr1UxnPP2+SCFy31gLOMLqLntz48s6q+fieguBLaW5 XTxWw4Qqit9Z66mlops8O6fFfJ9YuoIkbpYdlU1slBfBR+SAymEOrfK7sFBkZ0ERF7vn dFuc8uiPnoqVd5lvawy8gJp5AvoxXjXmFli/kxWqfLCyO0f4kqv8QvvofadLXYwsKep3 98SA==
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=Z9iHbuK6+dWZwZoa3DAio1jdg/vqz+Uu5I6b69DaVdw=; b=GmaFTbakEjk1KOFuNj4uBCAxEwHvYl8m1kwJ3cGHLna647zG1kzg6+X0QuT0R2SWj5 Uh3vr7XvzWX9C9M3iSvpZ8MejaWc3mDYsnaWbnrmWdQbNc7iQh3okUdPQ/dAXSg6IOQt BXggzAgkYkjkHSPN2ZtAb73Zx33301tAy52r8P8loSGZRPv2ruHfmp6/9BVDBR9Kuxhn r4e1guZ4PIVAe4UFbNOWn3q2UVDCN+YWANSeZziAXurFO0FcWfx5exu/qSx1ddn2Ioeu ZUbG6Q57Xa0Q8FsfyVULQmQ4GKw0RDV/ML8CcoQucLCjTstdf+fS75bofqak2yjtLjU5 M21g==
X-Gm-Message-State: AOPr4FVFQD2teRnYqP4AuJU64yxZr59XN41B2hm8W5IWgoB78Io6Qo+h1yEO35AXfNCtKg==
X-Received: by 10.66.164.133 with SMTP id yq5mr5617081pab.107.1463523706916; Tue, 17 May 2016 15:21:46 -0700 (PDT)
Received: from ?IPv6:2406:e007:79a7:1:28cc:dc4c:9703:6781? ([2406:e007:79a7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id o80sm7059345pfa.37.2016.05.17.15.21.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 15:21:45 -0700 (PDT)
To: "Bless, Roland (TM)" <roland.bless@kit.edu>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5c7d5fd9-a225-d419-7962-840d10e54ba4@gmail.com>
Date: Wed, 18 May 2016 10:21:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <573B4076.304@kit.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/F0j-vZF1YHdR1WZTm0vxy53btaw>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 22:21:49 -0000

On 18/05/2016 04:01, Bless, Roland (TM) wrote:
...
> https://tools.ietf.org/html/rfc7136
> is probably also of interest.

In particular, it means you do *not* need specific values for the u/g bits these days.

    Brian


From nobody Tue May 17 15:39:35 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 BBA0012DAEC for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 15:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 A7tT58ZKClJQ for <homenet@ietfa.amsl.com>; Tue, 17 May 2016 15:39:30 -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 434D812DAB1 for <homenet@ietf.org>; Tue, 17 May 2016 15:39:30 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4204:51:591a:551d:2ead:2204]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4HMdOGO059240 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 17 May 2016 22:39:25 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4204:51:591a:551d:2ead:2204] claimed to be mb-2.local
To: Joe Touch <touch@isi.edu>, Ray Bellis <ray@bellis.me.uk>, homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk> <573B4BA3.9020709@isi.edu>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com>
Date: Tue, 17 May 2016 15:39:23 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1
MIME-Version: 1.0
In-Reply-To: <573B4BA3.9020709@isi.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8um77LDtCWNrDPGtkO3rxAb6CEKAEXsMf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bPAPXAA8KjeGJWGkr8i73cuJtQU>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 17 May 2016 22:39:32 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8um77LDtCWNrDPGtkO3rxAb6CEKAEXsMf
Content-Type: multipart/mixed; boundary="99Rl6AK5HtFJkD3heCRLtV77iFuWPOc8N"
From: joel jaeggli <joelja@bogus.com>
To: Joe Touch <touch@isi.edu>, Ray Bellis <ray@bellis.me.uk>, homenet@ietf.org
Message-ID: <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com>
Subject: Re: [homenet] Which IP addresses must be avoided?
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr>
 <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk>
 <573B4BA3.9020709@isi.edu>
In-Reply-To: <573B4BA3.9020709@isi.edu>

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

On 5/17/16 9:49 AM, Joe Touch wrote:
>=20
>=20
> On 5/17/2016 9:35 AM, Ray Bellis wrote:
>> However some operators have (had?) "classful" firewall rules that
>> prohibit packets that come from IP addresses that would have been
>> considered a broadcast address in a pre-CIDR world.
>=20
> It's been 23 years since pre-CIDR and 15 years since you experienced
> this error.
>=20
> If we can't assume a fix here, then we can't assume any of the IPv6
> reserved IDs are actually reserved either - they could easily be in use=

> by legacy equipment.
>=20
> I.e,, the Postel principle applies here:
>=20
>     - avoid assigning these addresses
>     - test your equipment to ensure that they allow these addresses
> correctly
>=20
> If only we had compliance testing (again)....

I'm not really concerned that we broke windows95, neither is Microsoft.

We use these IPs for production VIPs and testing in a CDN (as /32s) and
they are fine.

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



--99Rl6AK5HtFJkD3heCRLtV77iFuWPOc8N--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlc7nZsACgkQ8AA1q7Z/VrIjqgCfSU60guJFNUfuj0dMcqD0nocY
EtoAn0kbxNoMa00hpbecbg9TJMuGQTeA
=+/w9
-----END PGP SIGNATURE-----

--8um77LDtCWNrDPGtkO3rxAb6CEKAEXsMf--


From nobody Wed May 18 00:02:43 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 5205D12B02B for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 00:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level: 
X-Spam-Status: No, score=-5.727 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.426, 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 2OcMHUYCP17C for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 00:02:37 -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 58AFE12D0D3 for <homenet@ietf.org>; Wed, 18 May 2016 00:02:37 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9CFCDA2; Wed, 18 May 2016 09:02:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1463554953; bh=igCdv84p5VOA24rsdDg65QxFN9gDSqnjYS73Br5PgVE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=UNJytJi5jZARsc9LZlxxdr4EtqGhJEbxBU/RkuldtYJsxwgsKQsdEewypAJpVpGDk eB1HXVeyH6TUJaSgwqutTXzlAW2gI4CM2/HL//cLsb13ZAqu56qG0UnL2MiveQcb+P r1Y4EHyAdJsQqS1HZsyktxQ4gbT0aeP9NuNEg/EA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9126FA1; Wed, 18 May 2016 09:02:33 +0200 (CEST)
Date: Wed, 18 May 2016 09:02:33 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: joel jaeggli <joelja@bogus.com>
In-Reply-To: <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com>
Message-ID: <alpine.DEB.2.02.1605180900490.28372@uplift.swm.pp.se>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk> <573B4BA3.9020709@isi.edu> <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/lYvjOyhx1vD6PjhhIfa7awHwrzY>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 18 May 2016 07:02:41 -0000

On Tue, 17 May 2016, joel jaeggli wrote:

> We use these IPs for production VIPs and testing in a CDN (as /32s) and 
> they are fine.

I have talked to operator colleagues and found several who use .0 and .255 
IPv4 adresses handed out to customers for Internet communication without 
ill effects.

So while this was a problem 10-20 years ago, I'd say it isn't now.

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


From nobody Wed May 18 01:03:07 2016
Return-Path: <otroan@employees.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 50D7A12D176 for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 01:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 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_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 eLz7Kpr5x8Cx for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 01:03:05 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E75D12D14C for <homenet@ietf.org>; Wed, 18 May 2016 01:03:04 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2016 08:03:02 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 08DC89CC7D; Wed, 18 May 2016 01:03:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=0LcY6UKu6x7MNLt94mZYhE35ehw=; b= dlbEDYHmurtvkuTQNy8jBG/EpyHABdwY2BBEVjjObwIJRcb8I4RY0iuKZ8XDQa/c GHlPmyHR2E/V7EwvenafW+qi34brx1M4LUjcAOv5/uhDaAeFFtSRn/ToXBqrODyT XuFwJZb7KKlq0NLCp4wzUCjZR+QQlztCa1rp7BpaXc0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=QdMFmK7hfnABMlBIagyJH1Ajl/ 1GGZEQeWngxtJgpkpo8KJq+QdkP2WNAztZaSdRjVXFduh1gMv3pis8du+17xY9B3 ncBDeJyEIiOmBEheeDhMwwqEfgu1lTribhfC8iynl20/rJwDw1GuLO9lSOXmOF2Z r5wqKDFums7GPRyfE=
Received: from h.hanazo.no (unknown [173.38.220.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B5D759CC4E; Wed, 18 May 2016 01:03:01 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 7E3801692B30; Wed, 18 May 2016 10:03:01 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_1C5F7991-7D86-424F-8E2E-EB27C76128EE"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 18 May 2016 10:02:58 +0200
Message-Id: <DC2842AD-58E0-4E21-AB45-0994C348C201@employees.org>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu> <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fyH93gy9BLYJ-ltk8q9roveiDUw>
Cc: Markus Stenberg <homenet@ietf.org>, "Bless, Roland \(TM\)" <roland.bless@kit.edu>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 18 May 2016 08:03:06 -0000

--Apple-Mail=_1C5F7991-7D86-424F-8E2E-EB27C76128EE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Juliusz,

>> https://tools.ietf.org/html/rfc5453
>> provides an answer w.r.t. IPv6.
>=20
> Do I need to avoid these addresses when assigning a /128 or a /127?

no. if you assign a /128, that is a single address, the length of the =
IID is zero.
the case of /127 is a little trickier, since then one end will get the =
subnet-router anycast address.
as long as both ends of the /127 agree, that's not a problem.

Best regards,
Ole

--Apple-Mail=_1C5F7991-7D86-424F-8E2E-EB27C76128EE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJXPCG1AAoJED4aXnjSQuKWC5MIAKG2JY1LWBeI4BAAivBLlhUy
6vsiP+eK7YnWg9nEQt5gUhEDtf6u2E+RNr0Z7p27fGb4443UWDx8vx+g/QcADi02
MoYk5Ifqf6hVR2uSDz34C1fCfyjVCPbkA5A1F5PpWT8izJtPqSpUzoM9kUyuqDu+
wW90hdaiNnR6QSE87NEky+xoZKO6AzPmP7LOOhojuuQjCXFKrNSEROyS59AKcfyA
Sv05sgAFxdNBzYY66ZtJUJOmAK5l7Qo3aPOTayDtXuEEMRG74Okwe7sNkw065QLu
MIBObPAvFjqOXTr71gmcc+BnCrqkefd7AybsdCeN9W8/LJuuD1Fpj0Dw1jIsAZg=
=83FQ
-----END PGP SIGNATURE-----

--Apple-Mail=_1C5F7991-7D86-424F-8E2E-EB27C76128EE--


From nobody Wed May 18 01:17:01 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 06F8012D190 for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 01:16:50 -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 wjxzR0Q3AgMr for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 01:16:44 -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 B1DFD12D098 for <homenet@ietf.org>; Wed, 18 May 2016 01:16:44 -0700 (PDT)
Received: from [46.227.151.81] (port=58774 helo=rays-mbp.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 1b2weo-0005vc-IT (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Wed, 18 May 2016 09:16:42 +0100
To: homenet@ietf.org
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk> <573B4BA3.9020709@isi.edu> <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com> <alpine.DEB.2.02.1605180900490.28372@uplift.swm.pp.se>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <e988161f-5fcb-cd28-5823-93e2cd84f46e@bellis.me.uk>
Date: Wed, 18 May 2016 09:16:46 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1605180900490.28372@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iV0vv2c989NJqu2P9A_5RzrSwAo>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 18 May 2016 08:16:50 -0000

On 18/05/2016 08:02, Mikael Abrahamsson wrote:

> I have talked to operator colleagues and found several who use .0 and
> .255 IPv4 adresses handed out to customers for Internet communication
> without ill effects.
> 
> So while this was a problem 10-20 years ago, I'd say it isn't now.

I'm glad to hear this!

thanks,

Ray


From nobody Wed May 18 02:03:38 2016
Return-Path: <v6ops@globis.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 8E32612D195 for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 02:03:37 -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, HTML_MESSAGE=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 I12R_M4TRMSL for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 02:03:36 -0700 (PDT)
Received: from globis01.globis.net (092-111-140-212.static.chello.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id 1019F12D17E for <homenet@ietf.org>; Wed, 18 May 2016 02:03:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 7CA2240347; Wed, 18 May 2016 11:03:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ef4TJtvt485; Wed, 18 May 2016 11:03:29 +0200 (CEST)
Received: from Mac-a45e60d143f5.local (dhcp-089-098-157-249.chello.nl [89.98.157.249]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPA id B69BF40344; Wed, 18 May 2016 11:03:29 +0200 (CEST)
Message-ID: <573C2FE0.4080701@globis.net>
Date: Wed, 18 May 2016 11:03:28 +0200
From: "Ray Hunter (v6ops)" <v6ops@globis.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <57333B3F.7000009@globis.net> <CC759790-4F9B-47B8-A42C-A85F78AC9773@jisc.ac.uk> <57335AB6.8060305@globis.net> <87mvnwh81u.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1nu98pXdDzVgZ2yW7xe8mwA=O+zmoGS8XLs_NLbNUaKFQ@mail.gmail.com> <57337274.1040000@globis.net> <CAPt1N1=mVBM-Dyg50eAv4Lz4XK1Hfe1SgHH5osR9fuhJhc0DWQ@mail.gmail.com> <57344249.8070907@globis.net> <874ma3s9pc.wl-jch@pps.univ-paris-diderot.fr> <57348817.1090200@globis.net> <CAPt1N1nWJJx_38Z_G8085w3Kwnd=_6gX3FBLjFMQcDm9sTdFtQ@mail.gmail.com> <5735B02D.8080304@globis.net> <CAPt1N1kAks=pAF-rcHRGWFbWLgWN5qEPZK+-6=c4VeZRi5VHcQ@mail.gmail.com> <CAPt1N1m96gpEz4GXrpr+eA3OjQyhQfbAACyi83noYovE1WSx7Q@mail.gmail.com> <CAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com> <57371F60.6060605@globis.net> <CAPt1N1kMtZ+TKveVxN-Lq5C4tKmBdMNy7n7zRyN0wVyQEZjE+g@mail.gmail.com>
In-Reply-To: <CAPt1N1kMtZ+TKveVxN-Lq5C4tKmBdMNy7n7zRyN0wVyQEZjE+g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070900070008060304010408"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YmBPkGAoC6GvvJNy0cqrLIOrOK0>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]
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, 18 May 2016 09:03:37 -0000

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



> Ted Lemon <mailto:mellon@fugue.com>
> 14 May 2016 15:18
> The only problem with that is that in the homenet ideally we'd like to 
> have local names signed and validatable via DNSSEC, and that requires 
> that the local namespace be global in scope, even if the names 
> published in that namespace are not.
>
Not necessarily.

You only need global scope namespace if trust also needs to extend 
beyond Homenet.

If we're assuming that ULA will be used for on-Homenet communication 
streams (in the event of non-availability of GUA/ ISP uplink), then 
tying local names into the upstream global namespace is not strictly 
necessary.

So IMHO it would be just as acceptable to sign RRs for local names 
related to ULA address space with a locally-generated trust anchor 
(independent of the trust anchors installed on the Internet root servers).

Nodes and new routers would have to learn their local trust-anchor when 
connecting to the Homenet for the first time.

In other words, the local DNSSEC trust anchor identifies a Homenet. Not 
the ULA. Not an arbitrary label.

Otherwise we're going to need a globally-unique time-invariant label to 
identify this Homenet, that is also not based on the actual chosen ULA 
in use, which is not easy to generate.

>
> Ray Hunter (v6ops) <mailto:v6ops@globis.net>
> 14 May 2016 14:51
>
>
> Ted Lemon wrote:
>>
>> If devices publish keys, then you can use those keys to make sure you 
>> are still talking to them. And the dnssec validation of local names 
>> would also work. Graceful renumbering should indeed result in DNS 
>> updates. Bear in mind that this is graceful, so the old and new ULAs 
>> coexist for a while.
>>
>
> Sounds good.
>
> So can we assume
>
> 1) a single ULA namespace for resolving all active ULAs, that will 
> eventually converge to only containing RRs from a single ULA?
>
> 2) And that ULA namespace is disjoint from/completely independent of 
> any GUA namespace?
>
>

-- 
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

--------------070900070008060304010408
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>

</span><br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1kMtZ+TKveVxN-Lq5C4tKmBdMNy7n7zRyN0wVyQEZjE+g@mail.gmail.com"
 type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:mellon@fugue.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ted Lemon</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">14 
May 2016 15:18</span></font></div>    </div></div>
  <div style="color: rgb(136, 136, 136); margin-left: 24px; 
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div 
dir="ltr">The only problem with that is that in the homenet ideally we'd
 like to have local names signed and validatable via DNSSEC, and that 
requires that the local namespace be global in scope, even if the names 
published in that namespace are not.</div><div class="gmail_extra"><br></div></div>
</blockquote>
Not necessarily.<br>
<br>
You only need global scope namespace if trust also needs to extend 
beyond Homenet.<br>
<br>
If we're assuming that ULA will be used for on-Homenet communication 
streams (in the event of non-availability of GUA/ ISP uplink), then 
tying local names into the upstream global namespace is not strictly 
necessary.<br>
<br>
So IMHO it would be just as acceptable to sign RRs for local names 
related to ULA address space with a locally-generated trust anchor 
(independent of the trust anchors installed on the Internet root 
servers). <br>
<br>
Nodes and new routers would have to learn their local trust-anchor when 
connecting to the Homenet for the first time.<br>
<br>
In other words, the local DNSSEC trust anchor identifies a Homenet. Not 
the ULA. Not an arbitrary label.<br>
<br>
Otherwise we're going to need a globally-unique time-invariant label to 
identify this Homenet, that is also not based on the actual chosen ULA 
in use, which is not easy to generate.<br>
<br>
<blockquote style="border: 0px none;" 
cite="mid:CAPt1N1kMtZ+TKveVxN-Lq5C4tKmBdMNy7n7zRyN0wVyQEZjE+g@mail.gmail.com"
 type="cite">
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">
    <div class="gmail_extra"><br></div>


  </div>
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:v6ops@globis.net" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ray Hunter (v6ops)</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">14 
May 2016 14:51</span></font></div>    </div></div>
  <div class="gmail_extra">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<br>
<br>
<span>Ted Lemon wrote:</span><br>
<blockquote type="cite" 
cite="mid:%3CCAPt1N1nkCRG6S2QJ9KqzhTrneN3SpnEQ8vWZO4f4gWwT9g-+dA@mail.gmail.com%3E"><p
 dir="ltr">If devices publish keys, then you can use those keys to 
make sure you are still talking to them. And the dnssec validation of 
local names would also work. Graceful renumbering should indeed result 
in DNS updates. Bear in mind that this is graceful, so the old and new 
ULAs coexist for a while. </p></blockquote>
<br>
Sounds good.<br>
<br>
So can we assume<br>
<br>
1) a single ULA namespace for resolving all active ULAs, that will 
eventually converge to only containing RRs from a single ULA?<br>
<br>
2) And that ULA namespace is disjoint from/completely independent of any
 GUA namespace?<br>
<br><br></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">

  </div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
  </span><a 
href="https://www.postbox-inc.com/?utm_source=email&amp;utm_medium=siglink&amp;utm_campaign=reach"><span
 style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>

--------------070900070008060304010408--


From nobody Wed May 18 12:00:42 2016
Return-Path: <touch@isi.edu>
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 D227712D683 for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 12:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 lMiXqkZNzo7Y for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 12:00:39 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 4D254128B44 for <homenet@ietf.org>; Wed, 18 May 2016 11:50:28 -0700 (PDT)
Received: from [128.9.184.211] ([128.9.184.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u4IInsWO020240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 18 May 2016 11:49:55 -0700 (PDT)
To: otroan@employees.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <573B4076.304@kit.edu> <87eg908mrs.wl-jch@pps.univ-paris-diderot.fr> <DC2842AD-58E0-4E21-AB45-0994C348C201@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <573CB950.7070000@isi.edu>
Date: Wed, 18 May 2016 11:49:52 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <DC2842AD-58E0-4E21-AB45-0994C348C201@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/9XGzUBTQCm0ViXS96q63_B6VFRk>
Cc: Markus Stenberg <homenet@ietf.org>, "Bless, Roland \(TM\)" <roland.bless@kit.edu>
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 18 May 2016 19:00:41 -0000

On 5/18/2016 1:02 AM, otroan@employees.org wrote:
> Juliusz,
>
>>> https://tools.ietf.org/html/rfc5453
>>> provides an answer w.r.t. IPv6.
>> Do I need to avoid these addresses when assigning a /128 or a /127?
> no. if you assign a /128, that is a single address, the length of the IID is zero.

A /128 seems like it indicates that the entire address is the IID.
There's no "network" part left if it refers to a single address.

> The case of /127 is a little trickier, since then one end will get the subnet-router anycast address.
> as long as both ends of the /127 agree, that's not a problem.

See RFC 6164. It's supposed to be standard to allow use for 2 addresses
on a point-to-point link.

Joe



From nobody Wed May 18 12:58: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 315FF12D6A0 for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 12:58:19 -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 lexuh-p8CNwy for <homenet@ietfa.amsl.com>; Wed, 18 May 2016 12:58: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 03137128B44 for <homenet@ietf.org>; Wed, 18 May 2016 12:58:16 -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 u4IJwFBx018771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 May 2016 21:58: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 u4IJwE38018526; Wed, 18 May 2016 21:58: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 6BB1661FA8; Wed, 18 May 2016 21:58: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 OUJlPbDt0uOx; Wed, 18 May 2016 21:58:13 +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 1285D61FA2; Wed, 18 May 2016 21:58:12 +0200 (CEST)
Date: Wed, 18 May 2016 21:58:12 +0200
Message-ID: <87k2ir6svf.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.1605180900490.28372@uplift.swm.pp.se>
References: <87wpms8zvo.wl-jch@pps.univ-paris-diderot.fr> <5ae48799-cb13-2b68-a4cc-a56b6174ae4f@bellis.me.uk> <573B4BA3.9020709@isi.edu> <0714bb3f-3450-2cb2-d685-b3142faf3018@bogus.com> <alpine.DEB.2.02.1605180900490.28372@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 [IPv6:2001:660:3301:8000::1:2]); Wed, 18 May 2016 21:58:15 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 18 May 2016 21:58:15 +0200 (CEST)
X-Miltered: at korolev with ID 573CC957.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 573CC956.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 573CC957.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: 573CC956.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 : 573CC957.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 573CC956.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qhFUFujnHHgFHwZJK5yhV3X1luU>
Cc: homenet@ietf.org
Subject: Re: [homenet] Which IP addresses must be avoided?
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, 18 May 2016 19:58:19 -0000

> I have talked to operator colleagues and found several who use .0 and .255
> IPv4 adresses handed out to customers for Internet communication without
> ill effects.

The customers are probably behind NAT, so I'm not sure how much that says
about the compatibility of client devices.

> So while this was a problem 10-20 years ago, I'd say it isn't now.

Agreed, let's not avoid these addresses.  (Although the point is somewhat
academic in the case of both hnetd and shncpd, which assign /24 by default.)

-- Juliusz

