[Anima] services-dns-autoconfig
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 16 November 2021 12:53 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE33F3A08CD for <anima@ietfa.amsl.com>; Tue, 16 Nov 2021 04:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 6IxjqPX0Mb8c for <anima@ietfa.amsl.com>; Tue, 16 Nov 2021 04:53:49 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::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 444FC3A08CB for <anima@ietf.org>; Tue, 16 Nov 2021 04:53:48 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [142.169.78.56]) by relay.sandelman.ca (Postfix) with ESMTPS id 2E7D91F456 for <anima@ietf.org>; Tue, 16 Nov 2021 12:53:45 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 263DB1A0536; Tue, 16 Nov 2021 07:52:21 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="==-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 16 Nov 2021 07:52:21 -0500
Message-ID: <101059.1637067141@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8DWCQ006KQO2gPZCRmc5S1NJx3U>
Subject: [Anima] services-dns-autoconfig
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Nov 2021 12:53:54 -0000
I tried to read https://datatracker.ietf.org/doc/html/draft-eckert-anima-services-dns-autoconfig-00 this afternoon between other appointments. I think that the Introduction needs to tell me a lot more about the problem space. The Day-0/Day-1 stuff, I sort of understood, but not really. Is it relevant how the device got onto the ACP, if it wasn't BRSKI? I'm really unclear what the first sentence means: This document defines to support the autoconfiguration of Autonomic Control Plane (ACP, [RFC8994]) nodes for fundamental decentralized network services via DNS-SD GRASP, utilizing a new proposal mapping of DNS-SD ([RFC6763]) onto GRASP as its hop-by-hop multicast transport and encoding of messages. I don't know what "DNS-SD GRASP" is, and I think I should know all the words in the first sentence :-) I'm not sure if this is document is providing for autoconfiguration *OF* the ACP in nodes, or autoconfiguration of the nodes, once the ACP is configured. I think that the goal of this document is to somehow gateway DNS-SD requests/replies into GRASP M_FLOOD messages. But, I'm having to reverse engineer that. A comment on: }2.3. DNS for operations } } Availability of DNS names for network operations/troubleshooting is } today mostly an convenience in network operations, but with IPv6 } evolving the need to use DNS names even in CLI based network } diagnostics is raising - because IPv6 addresses often are more } difficult to memorize by operators. More and more network features } also support configurtion that instead of addresses include domain } names or URLs, and ultimately, any non-fully autoconfigured functions } should rather rely on domain-names and URLs instead of just addresses } for greater flexibility and relilability in the face of address } changes. I think that there are three major reason why even CLI tools need to use names: 1) because SSH, PKIX and other identities of the remote nodes are bound to the name. 2) because there are a multitude of IPv{4,6} addresses available for the destination, and the tools need to try them all. 3) because picking a source address (and protocol) is going to become more and more difficult as we get into new overlays, and MIF. Where you get the name->IP mapping will affect what source is really allowed. We lack the right APIs... getaddrinfo(3) isn't enough.
-- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Anima] services-dns-autoconfig Michael Richardson
- Re: [Anima] services-dns-autoconfig Brian E Carpenter