IETF Logo Mail Archive

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

何林 <helin1170@gmail.com> Mon, 16 April 2018 09:54 UTC

Return-Path: <helin1170@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 56BD51275F4 for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2018 02:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.77
X-Spam-Level:
X-Spam-Status: No, score=-0.77 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 JTZ3k7rgkwFw for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2018 02:54:51 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (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 5360D126B6E for <dhcwg@ietf.org>; Mon, 16 Apr 2018 02:54:51 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id d19so24187805wre.1 for <dhcwg@ietf.org>; Mon, 16 Apr 2018 02:54:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+5nZuWWW5gSYHvBPD5y4uOMBUqG17FUqpLTVHBzojXo=; b=vQLRtoNPZpSzfRk3C0IF03Pp6n0GPEzgUqucZmCH1Z4xcAEPoiknvsVZ+HThXptO3t mbZsKngBUEutrIJE4xM/bmzBG478hlw6QB7dsjQ6nIIjQVGPNfktXk3e5MQwjNpICHBP sqIPI/zdDB78mOOWwNqOaw2kfDlTvFSj1mScT9LNYTPALIFJXfotuMKkFdks9fABArLi qB2HOFoHC/6v+2yZ8eD6QFV0RFYBS4qlashyJXlvtw+oK6TX2Fi++YQpAI59bhX0TbCE G970OVek8FhqQxytyZ0onYma7nLrUeaJIIMKKcxZIF0QnHq0cdMZXwYUREEKTPEpIWw2 Ts8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+5nZuWWW5gSYHvBPD5y4uOMBUqG17FUqpLTVHBzojXo=; b=pVIEh/KA8744++joSfHs9qhZ7Ca+8ixVF7cOzX0GivtWDs2bCOcWuEvjD+DqogkyN6 N/L5inPEOnf9vpQdIJUx8y6SYwL6CbgRTyHPaGHtNK0rYtwTvuoB2FSEm1+/J9hBtg/h h+eX6ktZYC+Owqf1ZoqOBR/KDNG2T2R4p3AvFj/kQNP27NKGt5pEO6msCl27saq+oug1 Z9zgpdGJzAEkVUZqR+7K9Td78G1dtnQmSxL/AAU0h6BW59GVPpMJ2+0z3TTEt5t5NUIC GeLy2Tdw7ycdk4lt8/JMBWhaZA6mP5uVH/ePJ7gtT1aLku4YYs7wZeWM38sqEsnY+biN aFBQ==
X-Gm-Message-State: ALQs6tCPGYF5pniI8FNS29+3jMUG9UcplhISHGsjcd6Fs4jNs1cF5DoB keV/70GOwK4JDPm1oxS2WFeiqCyKOcmN4pvgkPE=
X-Google-Smtp-Source: AIpwx4/0ZVtXOWvFafpEncL09waPJGYVXZ8rVtIDX+ozh4YcM0rR1Yx1p9jiGwWOBCHhsVzNwIq/V01JTt3jdWd4OAI=
X-Received: by 10.28.18.206 with SMTP id 197mr9136610wms.22.1523872489843; Mon, 16 Apr 2018 02:54:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.192.131 with HTTP; Mon, 16 Apr 2018 02:54:09 -0700 (PDT)
In-Reply-To: <b7dbd8ef-9de4-e797-4724-10a21baaf0aa@gmail.com>
References: <03cca537c8164c61a73a14f654f25a9d@XCH-ALN-003.cisco.com> <b7dbd8ef-9de4-e797-4724-10a21baaf0aa@gmail.com>
From: 何林 <helin1170@gmail.com>
Date: Mon, 16 Apr 2018 17:54:09 +0800
Message-ID: <CABtDdH2P_r5K_J4Vu1XP0EpvcMX83_WGZ91kdEY4Zuerk9Z2_w@mail.gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a11497ffa70b0390569f436f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/UoFTUj4zV-4LevNr2vb8D7g8ul4>
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: Mon, 16 Apr 2018 09:54:53 -0000

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>:

> 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
> https://www.ietf.org/mailman/listinfo/dhcwg
>



-- 

    Yours Sincerely,

*   Lin He*

v2.23.0 | Report a Bug | By Email