Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt

Nico Schottelius <> Tue, 06 July 2021 18:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 132253A3013 for <>; Tue, 6 Jul 2021 11:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZxaTud4cI21o for <>; Tue, 6 Jul 2021 11:06:39 -0700 (PDT)
Received: from ( [IPv6:2a0a:e5c0:0:2:400:b3ff:fe39:7956]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F2E5E3A3011 for <>; Tue, 6 Jul 2021 11:06:38 -0700 (PDT)
Received: from nb3.localdomain (localhost [IPv6:::1]) by (Postfix) with ESMTP id 4DA4D20106; Tue, 6 Jul 2021 20:06:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=mail; t=1625594791; bh=eFm4OvxZqN8OedXjK5YWjFCGSrrOUgZPsO4zJypyuL8=; h=References:From:To:Cc:Subject:In-reply-to:Date:From; b=YNb9E0f7Bh4Zld2W8+KFtMZOrJJFwbrAynTB+Gj8Oi10la56GU+93u8bxXOtdmyKZ VXlDskiKj9cpAWK6EvJhF4WoGm1rQx/ieuTrTzPlLkUPObsfGOrwYkx/lf0GnbrUty v4DboHhJsmEBoM1d/WV9V5F8j9lp0P8V0kuLM5faav9E///O8tnbShZUopyiZmiddx 4g4YPKxZykR9F2+3Pn53nc38hVtucgFWTflkgBE7Qf4zhyotvjMGITaJ6mHnT/II4o UL8LoPOOqdeuSFPYnXJqWheVl5/W3WGIgsg5mZWuqRraFG1hKNdpqRw9NZeYkoRomJ EUfPTJbTNhpMQ==
Received: by nb3.localdomain (Postfix, from userid 1000) id 890BC14CC251; Tue, 6 Jul 2021 19:53:48 +0200 (CEST)
References: <> <> <> <> <> <> <> <> <> <28125.1625590441@localhost> <>
User-agent: mu4e 1.4.15; emacs 27.2
From: Nico Schottelius <>
To: Jared Mauch <>
Cc: Michael Richardson <>, Andrew Cady <>,
Subject: Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt
In-reply-to: <>
Date: Tue, 06 Jul 2021 19:53:48 +0200
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Jul 2021 18:06:44 -0000

Jared Mauch <> writes:
> I hate to say it but mDNS is likely the way to go for many things, but
> you may not be able to tell the difference between raspberrypi.local
> vs raspberrypi-2.local which can often be a challeng

I don't think mDNS is feasible, as you often don't know the device
name. Let me illustrate a use case that is already there and is indeed
tricky for us at the moment:

We have a "bootstrap network" (layer 2) that contains dozens
or even low hundreds of unconfigured devices. All of these devices can
easily be *found* by using IPv6 multicast ff02::1.

However *some* of them might be broken, have configurations that need to
be repaired via HTTP. The device configuring these devices is usually
some kind of "admin notebook (or desktop)", which we try to configure
"as robust as possible", because there are tons of devices providing
IPv4, IPv6, etc. - it's basically the "device zoo".

Overall, most of these devices can be identified (EUI-64 embedding) and
configured (ssh, dhcp, etc.) automatically. However *some* need manual
care and the trend goes towards requiring an HTTP(s) connection.

What I want to show with this example is that you cannot easily rely on
more complex/upper layer protocols - the only identifier you have is the
link local address, the MAC and the open port list.



Sustainable and modern Infrastructures by