IETF Logo Mail Archive

Re: Metadata over IPv6

Michael Richardson <mcr@sandelman.ca> Tue, 17 December 2019 19:23 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F53B120072 for <ipv6@ietfa.amsl.com>; Tue, 17 Dec 2019 11:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 fb6zJ9z7BXcy for <ipv6@ietfa.amsl.com>; Tue, 17 Dec 2019 11:23:53 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 586F8120889 for <ipv6@ietf.org>; Tue, 17 Dec 2019 11:23:53 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED35338982; Tue, 17 Dec 2019 14:23:47 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DBEA8D36; Tue, 17 Dec 2019 14:23:50 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian Haley <haleyb.dev@gmail.com>
cc: ipv6@ietf.org
Subject: Re: Metadata over IPv6
In-Reply-To: <eee1ebe3-dd1a-1a5b-21a8-739857995abf@gmail.com>
References: <eee1ebe3-dd1a-1a5b-21a8-739857995abf@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 17 Dec 2019 14:23:50 -0500
Message-ID: <13723.1576610630@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SSiSWuza14YlxPgbRLuluypDAjk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 19:23:56 -0000

Brian Haley <haleyb.dev@gmail.com> wrote:
    > This works fine for dual-stack hosts, but more and more we're seeing
    > IPv6-only networking scenarios that we don't support metadata with, so our
    > community is looking to define an IPv6 address to use for this service.  My
    > question to the list is - do you see a problem with us just defining an IPv6
    > link-local address for this same service?  Or do you think we need to propose
    > a spec for it, in order to get IANA to reserve it?

Well, nobody went to IANA to reserve 169.254.169.254 did they, so why change? :-)

I do think that it should be a link-local address. I don't think you'll get
any push back on that.  How and if to reserve it is a question.
I don't see a good reason to use mDNS to discover it, but others might.

I think that Fred's suggestion to use fe80::ffff:a9fe:a9fe is a good one.
I didn't look at this document to see how they reserved it, but whatever he
did is probably a good idea.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email