IETF Logo Mail Archive

Re: [homenet] Updating DNS [was: How many people have installed the homenet code?]

Ted Lemon <mellon@fugue.com> Fri, 13 May 2016 13:40 UTC

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

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>

v2.23.0 | Report a Bug | By Email