IETF Logo Mail Archive

Re: Metadata over IPv6

Brian Haley <haleyb.dev@gmail.com> Thu, 19 December 2019 14:21 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 2940F12083B for <ipv6@ietfa.amsl.com>; Thu, 19 Dec 2019 06:21:46 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 EYswn-I4MOYv for <ipv6@ietfa.amsl.com>; Thu, 19 Dec 2019 06:21:44 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 9939312082F for <ipv6@ietf.org>; Thu, 19 Dec 2019 06:21:44 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id l12so5132837qtq.12 for <ipv6@ietf.org>; Thu, 19 Dec 2019 06:21:44 -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=hGpF3qnpnbNCwaZjycasfUtzmQOBgmV38VI1477s2TU=; b=m03vmySzFNNhL1fzlNraR4OxwFzYo/GaGvGB6gvdIc7+BVK9dKA+6s9OoupP5RKbj/ gm7sVAV50tQV+rRuDpVvpzTbHa5srb/F2Er20IB+bobZX911YzXTdpQbaaG51nxPlqxI 7oRbbHVVwkGjmBtQx4JfJRfMVAyKQGYVEKYALwiO2SNkb80HQRbAoI4ubvdn4t5nE8xg jd4Ukx0LdoRT0QAnIjJAXz4CVfZGfTNWVmOzHe4MACWxdycluIsvM80gP3bV92HfEXMX qn59rlCUY3bn8+qZp8Y/Zrz8gCMeaVc0rNsqXeJW9T5AzoUQ1inCruqD/Rk9Dsk5tAPJ pS2A==
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=hGpF3qnpnbNCwaZjycasfUtzmQOBgmV38VI1477s2TU=; b=bqA8QtwT7DH3O1oSKjNY8fgRhwgFMU5Knho5T3AS/YhCgi9a5IIMRy6C9vgaWGaKv1 zMoPGlJH1DdPtJ1WC4USunfcfZ6xI2Xm/oS/muFXlXTf4pggHCpC8CEkbJJ1r4VjrhKu Woge9wIVF9qPd+OLzEnSG+rwCEgxGSlouULPXF/HYhzw07+aCVkMStpWU2BWKbJMeuGw hedUX0cbhZ9Gmb9O4O85iA3/+ijJkLQlw0Gfgqpsr5vHIiQifNCboV5T/d6YJoaJ0xzq jkxGl0C9igw/ljIbm+T1B8aXTOrty49kaDbjUr1RtcJF3veVCiOxvTsUbJzOGSRh5Dyn eV3A==
X-Gm-Message-State: APjAAAU2maOphMwA3LokrUuv7JcIHdjbYKX1Zhf7w6fzjF9ha6dQPbZp f670P5hHUxxb4S7ootYXm/hzZU3GO/s=
X-Google-Smtp-Source: APXvYqy8Estyn82XHSIIrm2xw3DxyEL5G8bsxJxfJZU1a2a5lfD23Ssy7tKqLCKeLiBGvJQD6jPRpA==
X-Received: by 2002:ac8:30f7:: with SMTP id w52mr7327793qta.380.1576765303404; Thu, 19 Dec 2019 06:21:43 -0800 (PST)
Received: from [10.18.57.43] (nat-pool-bos-t.redhat.com. [66.187.233.206]) by smtp.gmail.com with ESMTPSA id z4sm1728335qkz.62.2019.12.19.06.21.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Dec 2019 06:21:42 -0800 (PST)
Subject: Re: Metadata over IPv6
To: otroan@employees.org
Cc: Fred Baker <fredbaker.ietf@gmail.com>, 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> <0cc715fd-e49c-b6fb-0703-624cefdaf693@gmail.com> <84DC68B2-36D6-4B79-AF72-8B03EDE8DCA4@employees.org> <52d440d7-6416-6ea5-2718-e9c80a2b793a@gmail.com> <8726E39C-62F7-4FFA-B2D4-5201A598FD2D@employees.org>
From: Brian Haley <haleyb.dev@gmail.com>
Message-ID: <8899cf88-2484-eef9-44a1-8d83adfc447b@gmail.com>
Date: Thu, 19 Dec 2019 09:21:41 -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: <8726E39C-62F7-4FFA-B2D4-5201A598FD2D@employees.org>
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/zcDVPN2xLfZgaO22Wk2lhH85i_8>
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: Thu, 19 Dec 2019 14:21:46 -0000

On 12/19/19 8:26 AM, otroan@employees.org wrote:
>>> There are probably 10-15 ways of doing it.
>>> If you do DHCP anyway, why couldn't the URL be passed as an option in DHCP?
>>
>> Yes, there are many ways to do this, it all seems to rely on a well-known link-local address being reachable though.  I'm reluctant to suggest a DHCP option since it will add complexity since more parts will needed to be changed to support it.
> 
> At the top of this email you stated: "...which is right after DHCP completes".

Hi Ole,

Yes, but since this is a different process running, how does it know 
that option was returned and how does it get the value?  The DHCP client 
hopefully put it somewhere I would hope.  I'd have to ask the cloud-init 
developers what they think, I was thinking a well-known IPv6 address 
would be received better.

Thanks!

-Brian

v2.23.0 | Report a Bug | By Email