Re: [Add] [EXTERNAL] DRDP: response to feed backs provided during the meeting

John Levine <johnl@taugh.com> Fri, 27 March 2020 00:55 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D18433A0C1A for <add@ietfa.amsl.com>; Thu, 26 Mar 2020 17:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=vFNNF1qh; dkim=pass (1536-bit key) header.d=taugh.com header.b=OKRG/Wgf
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 RDeBAKKjUZZq for <add@ietfa.amsl.com>; Thu, 26 Mar 2020 17:55:55 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 DBD3B3A0408 for <add@ietf.org>; Thu, 26 Mar 2020 17:55:54 -0700 (PDT)
Received: (qmail 80874 invoked from network); 27 Mar 2020 00:55:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13be7.5e7d4f19.k2003; bh=E0subA+ZduYP+WgjG2MtJ/xZ7cAeCFzqrOvsIoY0FfY=; b=vFNNF1qh4PsK9zOIQZa2RIRw4xW+8ALVZobTx5NHbgYA8g65CEPp4Z7bvDlUHaGl6lOVYwt8T48VHB0mR1vx8DLLfb2gawrfr9QqZC9C8FI2bgtGNJIHbe9mGIeMt1aoy2iFKwyy6VliZNuSQDQn30ZHlVrQ5rDLNVpglZaIDebLo5TJmd2KMmhAKQY//fUK9zjzjGQDsLshv3+6mAd+B56Y0VKvb+i6cIocHGDwvFPFSL7GCY4BNc3uXIVJFKDD
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13be7.5e7d4f19.k2003; bh=E0subA+ZduYP+WgjG2MtJ/xZ7cAeCFzqrOvsIoY0FfY=; b=OKRG/WgfgglGmbaycxCAW77tyKNsKFxDcOLC3Vpnd8qHvXc0Z0MHxXAtHW60eKRiylRrxcXlAtwHySRwEguiCbSC4+W9vQjF2e8fXH/hUReBI2d+vFLf4bzGOUp/u3DDap3Fztma18Pk1V/CvNymHYo/aXnqZ9YYdJhN/9z5unZNnHhNP9UGUiEkdN9KxS6ju7x5fALzkl83mMrMyNXn1UVXGwOQSz8AJR7ijdEVpuT9CQXuGwNPvXZvBT+SE5y6
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 27 Mar 2020 00:55:52 -0000
Received: by ary.qy (Postfix, from userid 501) id 2AD8F16A81E9; Thu, 26 Mar 2020 20:55:52 -0400 (EDT)
Date: 26 Mar 2020 20:55:52 -0400
Message-Id: <20200327005553.2AD8F16A81E9@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: add@ietf.org
Cc: Glenn.Deen@nbcuni.com
In-Reply-To: <15470670-015C-4C13-9B14-26D74FB87AD2@nbcuni.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/UhuoGRQMKxBZUXv30gfyGk9QNrc>
Subject: Re: [Add] [EXTERNAL] DRDP: response to feed backs provided during the meeting
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2020 00:55:57 -0000

In article <15470670-015C-4C13-9B14-26D74FB87AD2@nbcuni.com> you write:
>Isn’t the DNS itself a global repository of domains?   Could something be signed and published in it?

I think that has a bootstrap problem.  You don't know where to look
unless you know where to look.

If it's at a well-known DNS name, we're back to the single point of failure.

R's,
John