[dnssd] [Dnssd] DNS-SD for networking automation (ANIMA etc..)

Toerless Eckert <tte@cs.fau.de> Thu, 15 July 2021 19:35 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B2F23A087D for <dnssd@ietfa.amsl.com>; Thu, 15 Jul 2021 12:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 kmrOgKXUUWyq for <dnssd@ietfa.amsl.com>; Thu, 15 Jul 2021 12:34:58 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C013A0874 for <dnssd@ietf.org>; Thu, 15 Jul 2021 12:34:57 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 86268548015 for <dnssd@ietf.org>; Thu, 15 Jul 2021 21:34:53 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7B8854E7A58; Thu, 15 Jul 2021 21:34:53 +0200 (CEST)
Date: Thu, 15 Jul 2021 21:34:53 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: dnssd@ietf.org
Message-ID: <20210715193453.GC28912@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/cW1DUYKR8nevkjzU7B-5yrBDW3s>
Subject: [dnssd] [Dnssd] DNS-SD for networking automation (ANIMA etc..)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2021 19:35:03 -0000

Dear DNS-SD WG

I wanted to bring this work again up with DNS-SD working group, looking for interest
and collaboration.

I presented this originally in 2017 at IETF100 to DNS-SD WG:
  https://datatracker.ietf.org/meeting/100/materials/slides-100-dnssd-03-toerless-grasp-01.pdf

But then had to let this work sleep because we had a backlog of about 450 pages
worth of ANIMA drafts that wanted to become RFC first, which we finally managed
to get done in May 2021 - RFC{8366,8368,899[012345]}

So, now i refresh this work for IETF111, alrady with additional co-author
and wanted to also refresh interest with DNS-SD:

a) Introducing GRASP protocol as a new transport for "DNS-SD" (beside mDNS, unicast and others).
  https://datatracker.ietf.org/doc/draft-eckert-anima-grasp-dnssd/
b) Leveraging DNS-SD to drive autoconfiguration of decentalized infrastructure services in networks.
  https://datatracker.ietf.org/doc/draft-eckert-anima-services-dns-autoconfig/

The foundational part is really that there are several significant infratructure
services needed in networks including NTP, radius/diameter, DHCP, DNS, syslog, 
netconf/ssh that need to be autoconfigured both for initial bootstrap of devices,
but also during the network lifecycle, and dynamic Service Discovery makes
those services much more flexible to confiure, resilient against server failure
and performant through server load-splitting and/or proximity based server selection.

So, i'll be asking for a slot to present / discuss again at IETF111,
also taking feedback from IETF100 into account!

But please feel free, to also discuss here on the mailin list!

Cheers
    Toerless