IETF Logo Mail Archive

Re: [homenet] draft-ietf-homenet-front-end-naming-delegation vs. DynDNS

Toke Høiland-Jørgensen <toke@toke.dk> Mon, 23 July 2018 18:50 UTC

Return-Path: <toke@toke.dk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49912130DD9 for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 11:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZewDvJ_XOfE for <homenet@ietfa.amsl.com>; Mon, 23 Jul 2018 11:50:55 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C6312F1A6 for <homenet@ietf.org>; Mon, 23 Jul 2018 11:50:55 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1532371853; bh=Gcdso+Vgu58/4xhUEOlEDVxuAV2UoXsP63YDEVCtvlk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pW2hhAAkCJgKKb5QC6FAJyO/qHyPUbjaN7RD+vrz5ZFZTal6A5WzmzyrzKGRlRxyn lHW5FsYHDw40LcDSjt7xN/KyBVdYpCRNDM9ApJXcV0ybCaZo7T3KiUQPrmymS7V79x Om4aLTk9MOBYnQu13j1hN2YgbHb1a11bsYcvDUWJD9M9WRBWLI9jEOM9YeWs3j3syo JoJ2cBs72n9C32axcaAniq8zchcjzpATGM03dHnQ7b6MlaDo0gNaWsJEH1szn1bbTu kWN3qsarX9Omyik7dK9t09aXBkYh2RdON5WNpbmD/38CefXkqnTimka/F1kL2m9A+x HGJiT7fYgu+1Q==
To: Juliusz Chroboczek <jch@irif.fr>, Elson Oliveira <Elson.Oliveira@cira.ca>
Cc: Homenet <homenet@ietf.org>
In-Reply-To: <87sh496bnb.wl-jch@irif.fr>
References: <87sh4g1bqe.wl-jch@irif.fr> <249918E0-8E8F-44A9-B1ED-0D4F91104B20@isc.org> <877elsovmq.wl-jch@irif.fr> <CAPt1N1msXi1BG9RTDr2sWnn8J6F45CnESJCg4LTP-4jP9mVJxw@mail.gmail.com> <87tvovd0jp.wl-jch@irif.fr> <f70a8ff8-fb99-115d-ec33-d0ffa9ae8f13@cs.tcd.ie> <CAPt1N1=hpR81cBrs1zFKux6JAXQxn6g0==DiSWYVbW0hdSxbww@mail.gmail.com> <87k1prarme.wl-jch@irif.fr> <bc700dd55f654447a02cd93226f6aba5@cira.ca> <87sh496bnb.wl-jch@irif.fr>
Date: Mon, 23 Jul 2018 20:50:50 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87va953hx1.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/5YP9Z1af7qsMsKDZW-dnGdfAI-g>
Subject: Re: [homenet] draft-ietf-homenet-front-end-naming-delegation vs. DynDNS
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2018 18:50:57 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

> Exporting names from the Homenet into the global namespace, on the
> other hand, should be done by the hosts, with no involvement of any
> third party (neither the ISP nor the Homenet itself). This is where I
> argue for some form of end-to-end, secured, dynamic DNS update.

Why? What is wrong with the owner of the network selecting which devices
/ services he/she wants globally reachable without each device/service
having to implement (and be configured for) an external naming provider?

-Toke

v2.23.0 | Report a Bug | By Email