IETF Logo Mail Archive

Re: Metadata over IPv6

Brian Haley <haleyb.dev@gmail.com> Tue, 17 December 2019 23:06 UTC

Return-Path: <haleyb.dev@gmail.com>
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 93D171200B1 for <ipv6@ietfa.amsl.com>; Tue, 17 Dec 2019 15:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 r5oiur5477jM for <ipv6@ietfa.amsl.com>; Tue, 17 Dec 2019 15:06:38 -0800 (PST)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EEF3120058 for <ipv6@ietf.org>; Tue, 17 Dec 2019 15:06:37 -0800 (PST)
Received: by mail-qv1-xf32.google.com with SMTP id d17so4916563qvs.2 for <ipv6@ietf.org>; Tue, 17 Dec 2019 15:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=WdKJljZ3c9WNjER3HWlMk5znnZ1UONWsuL1smDRVGRg=; b=XP1MZMKHKeIa7zcc6aKu77TkmnUsiFHJehS6HS+JsnQEbUcHUI13vAADqe1HbrJj7J O8dtUXZrxonIZnipcLnQesG/cY4f6xSg4UiWlAhZoi/jlKw4O9RNAF600cPjYSgbsc9R AXOaCB9Ghya8XnbXstWNA6MjQKMHGYnkI96Kvtn+YMkUbtNuwU8sJ+kav5S5iGKtgO7B dQfJMwMqxkm+FYpvOlQi8mkPucHyWIFVXfQ6s4ndujTL9jpB4iu6r793Dc7MeW+44jTc 8uOkopwJ0Zb/gbwD2MRj62MqmOSe0MpFwmoIwwvtJNlzrCh+uYqOwaA46thSUc67PgAu E83g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=WdKJljZ3c9WNjER3HWlMk5znnZ1UONWsuL1smDRVGRg=; b=BjkzuZNvi686RWr2UlDAdV7/QKgiryLTJBLNbEWzS758TkDuDkw2Bvz6nQRMbWwWyQ pLAGNHjAhbHYCOh2KVRBUZMnpjTglUsRYlyJ36Rp2fgH1791IPGM5BVYbICt/DV51CkT lkNl0BJgyfCIPyTqESaSk0wMmNnmOnSADcYlICy8F5GmW5Wz8ET39E2B8OJhweq9hFmn rNsUa5uN5Ko7F+IK2WnHGX0/zSItgPAHL5xA3tvP5rKuxHUV7k8SXH9rJygRBpIctJEn HPKa/72Nun+wTHbTbR8l+CCuQcFz3vYY+IhIe135qTLZOSb7uMo5y+a91aTHp6GSlqu4 Wq0A==
X-Gm-Message-State: APjAAAXyyE6layqiF/hgs25LMCuL1Uc0zSN0Tjpq+Jlxn/ZBUzY7/CJy 5fctmD6mhC2JtmrIEML6NbIVfnWZjI4=
X-Google-Smtp-Source: APXvYqw2iT2lhKZG4ZOjUWDexRUVhifhCMvWiOkmQRvH/Ts9bIBoVu6ERQM6O1dkaKuwHxUbJzhkiA==
X-Received: by 2002:a05:6214:1923:: with SMTP id es3mr194699qvb.49.1576623996280; Tue, 17 Dec 2019 15:06:36 -0800 (PST)
Received: from ?IPv6:2601:18f:700:c12d:f5f0:b1d1:5ddd:d4b8? ([2601:18f:700:c12d:f5f0:b1d1:5ddd:d4b8]) by smtp.gmail.com with ESMTPSA id c184sm22382qke.118.2019.12.17.15.06.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Dec 2019 15:06:35 -0800 (PST)
Subject: Re: Metadata over IPv6
To: Fred Baker <fredbaker.ietf@gmail.com>, otroan@employees.org
Cc: 6man WG <ipv6@ietf.org>
References: <eee1ebe3-dd1a-1a5b-21a8-739857995abf@gmail.com> <32CDF4DD-6AB2-453B-9C62-2DE854BEF764@gmail.com> <6202a23d-0676-acd1-5308-491f6323839d@gmail.com> <4C7D7A5E-AA0C-4089-BDD6-9C6819EF8F55@employees.org> <AFF898F1-2C49-44CC-95BD-BAF5156674C7@gmail.com>
From: Brian Haley <haleyb.dev@gmail.com>
Message-ID: <0cc715fd-e49c-b6fb-0703-624cefdaf693@gmail.com>
Date: Tue, 17 Dec 2019 18:06:34 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <AFF898F1-2C49-44CC-95BD-BAF5156674C7@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/n1K3E4h69qF49z7C_ngO5Z9PLuc>
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 23:06:40 -0000

On 12/17/19 5:23 PM, Fred Baker wrote:
> 
>> On Dec 17, 2019, at 1:54 PM, otroan@employees.org wrote:
>>
>> Is you problem solvable using "service discovery" (e.g. DNS-SD)?

It *might* be, but I can't guarantee DNS will always be present, so it 
would be better to have a well-known address.  Typically this part of 
initialization in a cloud image is done in cloud-init, which is right 
after DHCP completes, and the address it uses is hard-coded in the 
binary itself to make things simple.

That's not to say mDNS couldn't be used, but having to deploy something 
in order to do a single lookup for 'metadata.local' could add a lot of 
overhead since there could be thousands of private networks involved, 
each with it's own daemon.

-Brian

> That would be https://tools.ietf.org/html/rfc6763
> 6763 DNS-Based Service Discovery. S. Cheshire, M. Krochmal. February
>       2013. (Format: TXT, HTML) (Updated by RFC8553) (Status: PROPOSED
>       STANDARD) (DOI: 10.17487/RFC6763)
> 
> Right?
> 
> 8553 changes '_' to '-'.
>

v2.23.0 | Report a Bug | By Email