IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Thu, 12 July 2012 16:25 UTC

Return-Path: <Ted.Lemon@nominum.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 7C60321F870A for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 09:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level:
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 S6qLyhCtrPED for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 09:25:49 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id AC9D321F86EE for <dhcwg@ietf.org>; Thu, 12 Jul 2012 09:25:43 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKT/76qds2mBaMUh5tTybKgpGDoHOoEmUQ@postini.com; Thu, 12 Jul 2012 09:26:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 77BEF1B82BF for <dhcwg@ietf.org>; Thu, 12 Jul 2012 09:26:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6D60419005C; Thu, 12 Jul 2012 09:26:16 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Thu, 12 Jul 2012 09:26:16 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andre Kostur <akostur@incognito.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt
Thread-Index: AQHNYDkrPoA8vAjQ6kS5Vbap9TjVqZcmSwOA
Date: Thu, 12 Jul 2012 16:26:16 +0000
Message-ID: <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>
In-Reply-To: <CAL10_BqMRGRJhg_nO-8F4GQxZMJusGu9w2Sfg_OWmabBDQm4MA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_C35F21D5C13A4825B4418B737E73F831nominumcom_"
MIME-Version: 1.0
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:25:49 -0000

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.

v2.46.0 | Report a Bug | By Email | System Status