IETF Logo Mail Archive

Re: [homenet] A TOFU approach to naming things in the homenet (with code!)

Juliusz Chroboczek <jch@irif.fr> Fri, 14 April 2017 13:51 UTC

Return-Path: <jch@irif.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 EE361120454 for <homenet@ietfa.amsl.com>; Fri, 14 Apr 2017 06:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, 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 AECkQHCVFXgY for <homenet@ietfa.amsl.com>; Fri, 14 Apr 2017 06:51:40 -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 16ACC128CD5 for <homenet@ietf.org>; Fri, 14 Apr 2017 06:51:39 -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 v3EDpcx8010403; Fri, 14 Apr 2017 15:51:38 +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 6768CD79B2; Fri, 14 Apr 2017 15:51:38 +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 8-6rX9jCJs6O; Fri, 14 Apr 2017 15:51:37 +0200 (CEST)
Received: from trurl.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6DAA1D79D8; Fri, 14 Apr 2017 15:51:37 +0200 (CEST)
Date: Fri, 14 Apr 2017 15:51:42 +0200
Message-ID: <87r30v3xn5.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Toke Høiland-Jørgensen <toke@toke.dk>
Cc: homenet@ietf.org
In-Reply-To: <87r30vomax.fsf@alrua-x1>
References: <87r30vomax.fsf@alrua-x1>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 14 Apr 2017 15:51:38 +0200 (CEST)
X-Miltered: at korolev with ID 58F0D3EA.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 58F0D3EA.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 58F0D3EA.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/42UJ1GBBhmLJYhw--3vaiq0o6v0>
Subject: Re: [homenet] A TOFU approach to naming things in the homenet (with code!)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Apr 2017 13:51:42 -0000

Simple and elegant, solves a real problem without too much ideology.

> This daemon will allow a client to claim a name on a Trust On First Use
> (TOFU) basis

Cool.

> If the name in a claim is not already taken by another nclient, the
> client's claim will be successful and the daemon will cache the public
> key and use it to verify subsequent update requests.

Does this imply there's a single daemon in the Homenet?  How does the
network elect it in case there are multiple claimants?  How does the
client learn the address of the daemon?

-- Juliusz

v2.23.0 | Report a Bug | By Email