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

"Bernie Volz (volz)" <volz@cisco.com> Tue, 17 April 2018 02:19 UTC

Return-Path: <volz@cisco.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 A96E312D871 for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2018 19:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.508
X-Spam-Level:
X-Spam-Status: No, score=-14.508 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 a70NMvOnZA6B for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2018 19:19:42 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6B4912D86C for <dhcwg@ietf.org>; Mon, 16 Apr 2018 19:19:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19688; q=dns/txt; s=iport; t=1523931581; x=1525141181; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zXo8hsTtLRZcU9zl2bzn5f7v5y7fSegD8XstpJcfSlM=; b=BESArDDKhmGA7QR/N51OUpVFkfJZCWTDKVtRBN6cgqNdqWRiMPsoFzR6 QxEYaT5yyViB6CnEGtHCr6gye/8QZ+ZfwUJRm7ma9fC3TIJ6VftptxWr9 l2KUNN4cqVut+62Lv0mxaDR5YthdMKev3rW4QJ9dAxJPcsySAVzQImede w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DUAQBOWNVa/4oNJK1cGgEBAQEBAgEBAQEIAQEBAYJNdWEXYygKg16IAo0TgXSBD4IWhFCHGIRqgXgLGAEKhEYCGoIqITQYAQIBAQEBAQECbBwMhSIBAQEBAwEBIQpBBQYQAgEIEQQBASgDAgICHwYLFAkIAgQBDQUIE4QOTAMVD6V9ghyHCQ2BK4IgBYgGghOBDgGDC4JPQgEBgUotDxCCSoJUApc5LAgChVeFMjOCdYE7GoYdhGKJLT+GDQIREwGBJAEcOCaBLHAVO4JDhXyFFIU+b41jgRcBAQ
X-IronPort-AV: E=Sophos;i="5.48,461,1517875200"; d="scan'208,217";a="100120582"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2018 02:19:41 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w3H2Jf0L001942 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 Apr 2018 02:19:41 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 16 Apr 2018 21:19:40 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Mon, 16 Apr 2018 21:19:40 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: 何林 <helin1170@gmail.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
CC: dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Some questions regarding draft-bvtm-dhc-mac-assign-00
Thread-Index: AQHT1fKKDM1QMvo14kiG3qDX/EpMaw==
Date: Tue, 17 Apr 2018 02:19:40 +0000
Message-ID: <c0ccb78eef92462084cf6f9efe757f6d@XCH-ALN-003.cisco.com>
References: <03cca537c8164c61a73a14f654f25a9d@XCH-ALN-003.cisco.com> <b7dbd8ef-9de4-e797-4724-10a21baaf0aa@gmail.com> <CABtDdH2P_r5K_J4Vu1XP0EpvcMX83_WGZ91kdEY4Zuerk9Z2_w@mail.gmail.com>
In-Reply-To: <CABtDdH2P_r5K_J4Vu1XP0EpvcMX83_WGZ91kdEY4Zuerk9Z2_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.1.195]
Content-Type: multipart/alternative; boundary="_000_c0ccb78eef92462084cf6f9efe757f6dXCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/pv7MSWpyUSVddpnKBs1a8qc5CDc>
Subject: Re: [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: Tue, 17 Apr 2018 02:19:45 -0000

IPv4, what’s that?

But, seriously, IPv6 link-local is all that is needed if the DHCPv6 server is on the local link and that really isn’t a high bar? Yes, if you need relays you need them to be able to communicate to the servers over IPv6.

My feeling is that we probably don’t want to consider it. But it may be something to consider later when this work is further along, perhaps using DHCPv6 over v4?

Also, IEEE is looking at protocols to do this (that would probably use direct Ethernet layer packets and not IP) and so maybe those environments could use that?


-          Bernie

From: dhcwg <dhcwg-bounces@ietf.org> On Behalf Of ??
Sent: Monday, April 16, 2018 5:54 AM
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some questions regarding draft-bvtm-dhc-mac-assign-00

Another question: should we consider solutions for IPv4-only hypervisors and LoT devices?

2018-03-06 6:57 GMT+08:00 Tomek Mrugalski <tomasz.mrugalski@gmail.com<mailto:tomasz.mrugalski@gmail.com>>:
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


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg



--

    Yours Sincerely,

   Lin He