IETF Logo Mail Archive

Re: [dhcwg] DUID+IAID

Ted Lemon <Ted.Lemon@nominum.com> Fri, 30 March 2012 19:10 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 8E45C21F866B for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 12:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.185
X-Spam-Level:
X-Spam-Status: No, score=-106.185 tagged_above=-999 required=5 tests=[AWL=-0.186, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, 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 94MCSHKETjbk for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 12:10:11 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id B118521F866A for <dhcwg@ietf.org>; Fri, 30 Mar 2012 12:10:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKT3YFEjydtFcnD388+C8lra0GK9sCx80x@postini.com; Fri, 30 Mar 2012 12:10:10 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 E8B0B1B80BA for <dhcwg@ietf.org>; Fri, 30 Mar 2012 12:10:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 DD4C4190064; Fri, 30 Mar 2012 12:10:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Fri, 30 Mar 2012 12:10:10 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "A. Gregory Rabil" <greg.rabil@jagornet.com>
Thread-Topic: [dhcwg] DUID+IAID
Thread-Index: AQHNDk7f4FgtkXLiwESgwgUDJGkpD5aCkfCbgADC4wD//4tAkoAAeMQA//+VNoKAAHcfAP//jNrqABW23oD//5QDew==
Date: Fri, 30 Mar 2012 19:10:08 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D5A6E@mbx-01.win.nominum.com>
References: <CAAed6vsuc5AoJ-pmdu-CYLzJ4jEtSUkxYy1aLTJbkoRiEjUQ9A@mail.gmail.com> <201203300826.q2U8Qx51078004@givry.fdupont.fr> <8D23D4052ABE7A4490E77B1A012B6307472D478A@mbx-01.win.nominum.com> <CAAed6vv6gDkjnHO1YujFbTm=fhJVZHi_25u6=PRgTiDrO6uR4g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D4946@mbx-01.win.nominum.com> <CAAed6vtnoi2fTEsb7kNpVXsnbh7H60mn7wUwcPMu0juVBSMCsw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D4986@mbx-01.win.nominum.com> <CAAed6vtKw40+BiK4a9KwKxZZ_fZSh3N7kjAMNeyXGUuyASwfvw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D49C0@mbx-01.win.nominum.com>, <CAAed6vtD+KKqLRzJdEF9ymtGM0VtXcz6-Htqdu1wgb-jerVo_A@mail.gmail.com>
In-Reply-To: <CAAed6vtD+KKqLRzJdEF9ymtGM0VtXcz6-Htqdu1wgb-jerVo_A@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] DUID+IAID
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: Fri, 30 Mar 2012 19:10:11 -0000

Greg, this is getting exhausting.   The MAC is not a unique identifier, even for an individual client.   Every request that comes out of an interface will have the same MAC address under this proposal.   This is true even if more than one IAID is presented per interface.   So identifying host interfaces this way won't work.

>From an administrative standpoint, you can use the mac to associate with the client in your administrative database or UI.   You can use the mac to associate DHCPv4 clients with a DHCPv6 client (notice the many-to-one mapping here: a dual-stack device with two interfaces will appear to be two clients to the DHCPv4 server).

So the MAC address is useful, but it does not fit into the box you are trying to shoehorn it into here.

v2.23.0 | Report a Bug | By Email