[dhcwg] Some questions regarding draft-bvtm-dhc-mac-assign-00

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Mon, 05 March 2018 22:57 UTC

Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A32112711E for <dhcwg@ietfa.amsl.com>; Mon, 5 Mar 2018 14:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 63xHHVjEeuAH for <dhcwg@ietfa.amsl.com>; Mon, 5 Mar 2018 14:57:55 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 7F8B712EAB6 for <dhcwg@ietf.org>; Mon, 5 Mar 2018 14:57:41 -0800 (PST)
Received: by mail-lf0-x22b.google.com with SMTP id y19so25662668lfd.4 for <dhcwg@ietf.org>; Mon, 05 Mar 2018 14:57:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=0wpT32UB+bHwNK4AMSOij4tAIMd38qL/R7Pf6shf9v8=; b=YzMY7QGS+roqBhUTP/0IN6Jz86LDLhJl6DlUD/rnQ/0cqnxkncioAnDAn7nIuRzroF cDGLhceWXmqazlIl5o7rRlstlhBKfF4HA0iMQX8DDhnBSMBt5uXANqLLtAHEoKxYdOvT ifOIFQYuxN6G+Ml+cOUxVXf39Q98lNhfceXDeywYZmzTQueiecrc/dbGKtTGHz2mWLpL rgyo48uUT7XdzzE+z0vLKmFkvVhMRijWcz4ATHMjfwOsiCiwgvmEMeJkIfVT2UTW7Ld8 Gi0e99T5e+TYtcNWG9pJnQLl3Pwrs3F0Pq/xFNiVFHpjsGLPvb+9wc5oZ3wRM6JKL4v2 mSNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=0wpT32UB+bHwNK4AMSOij4tAIMd38qL/R7Pf6shf9v8=; b=qzCNIpMZWmQ0KOitPIZ0nWqeZJ2o0G7AoBaM0S9CeQxpiwjG31ff9ZMXmDANEO6GNL Q7J56SeKyy+7rTpoXkB6k0Ce9qgaids727nShw7CDzAYjE5foY5MHup5m4Y0dgstL/pc UDZJ19CXPgD1hG7YDcjhrs3WM8+G6nEQSvFbguqkVeOOpCz3HamgPBUBegrZ0bX8dYBt faLaIbirNIVONAPVhWamKPG3vWdH8Iaiuplojx3hwIVjEhUZV+eb2HLj/oJw+aBHndtV guj+aWJCgKtfR9xag1NHS9TVm98ADEFG0cEg/OuOFxf7MTjC5qKACdn3ibWe6PNQV8+2 gbtA==
X-Gm-Message-State: AElRT7G9bMl1np4XM5hKGGjGnVQbwKyFyPl3VcXsgI8IHLo8yAbHCPFw BhX0tCb8LEYVZtnc1yXvK6XW00tu
X-Google-Smtp-Source: AG47ELs7/vrjaIWUQDWw4cfETHRVaHWy+B4+1bIysE5a+q5MpDQHR7XoBwfg6klAx3zr2JfxP/5k1w==
X-Received: by 10.25.156.210 with SMTP id f201mr10879451lfe.9.1520290659355; Mon, 05 Mar 2018 14:57:39 -0800 (PST)
Received: from [192.168.1.100] (109241079151.gdansk.vectranet.pl. [109.241.79.151]) by smtp.googlemail.com with ESMTPSA id q63sm2904817lje.72.2018.03.05.14.57.37 for <dhcwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 14:57:38 -0800 (PST)
To: dhcwg@ietf.org
References: <03cca537c8164c61a73a14f654f25a9d@XCH-ALN-003.cisco.com>
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Message-ID: <b7dbd8ef-9de4-e797-4724-10a21baaf0aa@gmail.com>
Date: Mon, 05 Mar 2018 23:57:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <03cca537c8164c61a73a14f654f25a9d@XCH-ALN-003.cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/0Y4RiUxk0WrV61MDTqI8PJ2qE5s>
Subject: [dhcwg] Some questions regarding draft-bvtm-dhc-mac-assign-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 22:57:58 -0000

Hi,

Thanks to Bernie for pushing forward, editing and uploading the draft.

This is an initial proposal for a new mechanism in DHCPv6. It looks a
bit odd at first (why would a device request MAC address if it's able to
transmit DHCPv6 packets already), but there are at least two scenarios
where this is justified.

I'd like to encourage people to read the draft. It short - 4 pages of
the actual proposal text (or 7 if you count option format sections).

There are couple questions we'd like to hear your comments on:

1. Does it make sense to reuse DHCPv6 mechanisms to solve this problem?
Several current and former IESG members think so, but we'd like to hear
your opinion on this.

2. Would such a topic be interesting to the WG?

3. Do we want to allow or even mandate Reconfigure here? One of the
objections raised to DHCPv6 protocol in general was that it's not always
possible to change the configuration at moment's notice.

4. We haven't really figured out whether it would be better to have
always one LLADDR per IA_LL or one or more? Arguments can be made both
ways. We're eager to hear what's the preference here.

On a related note, we organized the repo for this work here:
https://github.com/dhcwg/dhcp-mac. Feel free to comment on existing
issues or open new ones. Keep the discussion on dhcwg list, though.

Thanks,

Bernie & Tomek