IETF Logo Mail Archive

Re: [DNSOP] Publishing Information for Entities Identified by Domain Names

Martin Hoffmann <martin@opennetlabs.com> Mon, 27 January 2020 09:51 UTC

Return-Path: <martin@opennetlabs.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B5512012E for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2020 01:51:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 yBFRuaeo6odn for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2020 01:51:45 -0800 (PST)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (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 B06D512001B for <dnsop@ietf.org>; Mon, 27 Jan 2020 01:51:45 -0800 (PST)
Received: from glaurung.nlnetlabs.nl (unknown [IPv6:2a04:b904::a2c5:89ff:feb5:e311]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 0D9A723CB8; Mon, 27 Jan 2020 10:51:43 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none (p=none dis=none) header.from=opennetlabs.com
Authentication-Results: dicht.nlnetlabs.nl; spf=none smtp.mailfrom=martin@opennetlabs.com
Date: Mon, 27 Jan 2020 10:51:42 +0100
From: Martin Hoffmann <martin@opennetlabs.com>
To: John Levine <johnl@taugh.com>
Cc: dnsop@ietf.org
Message-ID: <20200127105142.33542706@glaurung.nlnetlabs.nl>
In-Reply-To: <20200125224121.48FE81336ABA@ary.qy>
References: <20200122151155.65e52c77@glaurung.nlnetlabs.nl> <20200125224121.48FE81336ABA@ary.qy>
Organization: Open Netlabs
X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-3I_mVemMf7wvqqnc1w-T1C8nlY>
Subject: Re: [DNSOP] Publishing Information for Entities Identified by Domain Names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2020 09:51:47 -0000

John Levine wrote:
> In article <20200122151155.65e52c77@glaurung.nlnetlabs.nl> you write:
> >
> >for a project we’ve been working[0] we needed to discover the
> >location of documents describing certain entities. We decided to
> >pick domain names as the identifiers and then use the DNS for
> >publication of those locations. It turned out there isn’t currently
> >a mechanism to actually do that (other than possibly NAPTR but that
> >seemed overly complex).  
> 
> You might take a look at RFCs 8552 and 8553.  There is a long history
> of publishing stuff in the DNS with scoped identifiers.

All the uses mentioned defined so far are about service discovery. This
draft essentially adds a means for information discovery to it. I
didn’t want to pollute the global scope namespace, though, so I
proposed to add one global node name to it and then take it from there.

Kind regards,
Martin

v2.23.0 | Report a Bug | By Email