Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt

Andre Kostur <akostur@incognito.com> Thu, 12 July 2012 16:38 UTC

Return-Path: <akostur@incognito.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 55DF621F865C for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 09:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level:
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RXPJJxgHFzs for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 09:38:41 -0700 (PDT)
Received: from na3sys010aog104.obsmtp.com (na3sys010aog104.obsmtp.com [74.125.245.76]) by ietfa.amsl.com (Postfix) with SMTP id 5522B21F8656 for <dhcwg@ietf.org>; Thu, 12 Jul 2012 09:38:41 -0700 (PDT)
Received: from mail-lb0-f181.google.com ([209.85.217.181]) (using TLSv1) by na3sys010aob104.postini.com ([74.125.244.12]) with SMTP ID DSNKT/79spSQSZYlxKnjhnzrOQLOtOcuc21y@postini.com; Thu, 12 Jul 2012 09:39:15 PDT
Received: by lbbgk8 with SMTP id gk8so3630990lbb.12 for <dhcwg@ietf.org>; Thu, 12 Jul 2012 09:39:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ojetZqGAwDmF/sfclvV9FrO+P3wh8ZGPYuXE7+QKOHE=; b=laFZrVPXghb8XD/35Rd1cwnd1v7QkyNFt7pVUVC+HUaal8g54ZJODaD0+p5qGwrIUG 96vMCimq4ffiBDa7dCfXxNTSN4antNWvUTYgeWyHZWx1qPRGc3VM4PgXvhjyWiusXr7a dMzfsbmPpfnc7dOEQuSVK9xJKmkEMDn2D7Y4hdeEIhjA+aa7KapPf0QdpTky+WVhXi94 OIs/AWlLpIWZImsAOoAt0gSn2kBDP/awSRXIfPH2CqR/DfOo9kfuBHZ7mQXKW9shoTgP jtNI2T6j3PVDIXE2QHtZsIV70h/cLbRsjc1LhNhlBD/+Ay6c4X83zLsGYTbJfbJllEb7 X2eA==
MIME-Version: 1.0
Received: by 10.112.83.136 with SMTP id q8mr1418731lby.60.1342111153073; Thu, 12 Jul 2012 09:39:13 -0700 (PDT)
Received: by 10.112.40.228 with HTTP; Thu, 12 Jul 2012 09:39:12 -0700 (PDT)
In-Reply-To: <C35F21D5-C13A-4825-B441-8B737E73F831@nominum.com>
References: <CAAed6vuPmGRw7ZVrY_uADTLb+5VZ1i0S8FYU9CiBvw0KjMZM6g@mail.gmail.com> <521202936.30106.1342097834494.JavaMail.root@network1.net> <CAL10_BqMRGRJhg_nO-8F4GQxZMJusGu9w2Sfg_OWmabBDQm4MA@mail.gmail.com> <C35F21D5-C13A-4825-B441-8B737E73F831@nominum.com>
Date: Thu, 12 Jul 2012 09:39:12 -0700
Message-ID: <CAL10_BrTxVVr-d8yOMq+P6Us+xJNwZdmoFrXpZJvbRGD0V_dow@mail.gmail.com>
From: Andre Kostur <akostur@incognito.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQlEFRmFwsvxg5ccV0aY1/u9ybIC7XRhKfAdp5HevOL3amImePRbN1wm98sf5AjnlxSpFfWu
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Jul 2012 16:38:42 -0000

On Thu, Jul 12, 2012 at 9:26 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> On Jul 12, 2012, at 10:18 AM, Andre Kostur wrote:
>
>> Changing gears for a second... if the point behind this draft is to
>> correlate DHCPv4 and DHCPv6 leases, is the MAC address sufficient?
>> Consider the case of any device using the DHCPv4 client identifier to
>> distinguish between multiple leases on the same computer.
>
> This shouldn't be a problem, because even if the client sends a
> client-identifier, it still has to send chaddr.

Yes, you'll likely have a chaddr, but you no longer know which DHCPv4
lease that the DHCPv6 transaction corresponds to.  You may have dozens
of DHCPv4 leases, all with the same CHADDR.


-- 
Andre Kostur