IETF Logo Mail Archive

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

何林 <helin1170@gmail.com> Sun, 15 April 2018 07:52 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 A3AD81275F4 for <dhcwg@ietfa.amsl.com>; Sun, 15 Apr 2018 00:52:57 -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 D9hm0j2Hv0x6 for <dhcwg@ietfa.amsl.com>; Sun, 15 Apr 2018 00:52:55 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 5112E1275AB for <dhcwg@ietf.org>; Sun, 15 Apr 2018 00:52:55 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id d1so17762755wrj.13 for <dhcwg@ietf.org>; Sun, 15 Apr 2018 00:52:55 -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=woueN5GC72IAOBGmWT1ruTcY5rAhcj47sm+tI1k2KAQ=; b=jcOZ4mVEpGs0TuQgWSMpeiIkO0nwwCclWlpJ3kNEuefIwwjJIuZz2b9EjOREUY5fnG kXQHWtCNkMbU0TwLaEQfHtjUQUqIlDTRj246G+oFztsXQNsxACIa0mKl/jO9RocFCuln 4yXPpz1VSpGV7+HvyA5jfwbGw7MCvlhXIK5ehI8i6Cdt8LT4skkiF+S2luZxm2cUeSOr TnR/KiQzQebJrg30kIqJaXRlftg8GyH8HcYwqztCawehOlaRPdM+5Szuynp/YoESFtbz IFRtl5X9yfk7h6AQsLKGn7Ilt8hnxMdIkHnDs38RJMbJgdwLsf+n76EUaQNdy4zIPKoS pH2g==
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=woueN5GC72IAOBGmWT1ruTcY5rAhcj47sm+tI1k2KAQ=; b=dhoYDZB5L//+q0yh/4R5Z2GgxnWkEhrUtTYl589t7h1VrW17ENi9KqGFaii88lMGc3 Cnf/aKGOXTAjmXdDpqQ8UdiwBzxL6AD6jt8WXTlaems4rY49i0O5oGPd1rkIDFPi5/EV Y1Gsy4l+4slt43eYfKzJN67WZ2SCqWdoe99AUHDm76DvmRyQ7+n25KgheE/DiUUuQLVy w1UUA0Tsg6MwA4Y7Vxhx0uPbtslFPuBrxSti+rOePo9fKgxpMpbXp+LYnXmdE/Hq6G1I babyHj0YxQaKVI/GIObt/+nSC9xqtuFrNMc5JiMzcxt0sX18K6eivMQJd2ds4AzrHBVc 6X1g==
X-Gm-Message-State: ALQs6tBFWSI8sFbIg4ZyQV/JRgck7xsM7W1aF86ra2vpublxowtJhunG lESsAsSdGPtFNPlPVvGEn34Ui4D9h92XvhUhx8s=
X-Google-Smtp-Source: AIpwx4+zXNbJYt1w9S8+neRs1eGtU8wDCRMAYmooU+0P2NM4d3GXJNrDjGIDkaEJpbl5aedbHOyc5OBQ0QAl0v3GKpk=
X-Received: by 10.28.192.8 with SMTP id q8mr7144306wmf.103.1523778773895; Sun, 15 Apr 2018 00:52:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.192.131 with HTTP; Sun, 15 Apr 2018 00:52:13 -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: Sun, 15 Apr 2018 15:52:13 +0800
Message-ID: <CABtDdH0To-Db3POs_CeL3qLURghVgvJ3qtkQNbb+yPPXcCydcA@mail.gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="089e0831644088cfb70569de6437"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/SynPx5rJLsVhPwk1-TC2vLAr7ds>
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: Sun, 15 Apr 2018 07:52:58 -0000

Hi:

Few notes inline (LH>) below.

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.
>
> ​LH> Make sense.


> 2. Would such a topic be interesting to the WG?
>
> ​LH> Yes,
​I think it's an interesting topic
.

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.
>
> ​LH> I think it's better to allow any number of LLADDR per IA_LL. Firstly,
this provides flexibility and allows clients to request different types of
link-layer addresses just in one Solicit message (Although I don't know
whether such scenarios exist). Secondly, one LLADDR per IA_LL can be just
considered as a special case.



> 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