IETF Logo Mail Archive

Re: [dhcwg] DUID+IAID

Ted Lemon <Ted.Lemon@nominum.com> Fri, 30 March 2012 14:58 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 B1ED321F85CC for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 07:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.891
X-Spam-Level:
X-Spam-Status: No, score=-105.891 tagged_above=-999 required=5 tests=[AWL=-0.492, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, 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 UeX-9XwS819c for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 07:58:38 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0603B21F85C6 for <dhcwg@ietf.org>; Fri, 30 Mar 2012 07:58:37 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKT3XKHXGC3GpDQePCjXdeg20tLJPY0xhC@postini.com; Fri, 30 Mar 2012 07:58:38 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 C67581B824D for <dhcwg@ietf.org>; Fri, 30 Mar 2012 07:58:36 -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 A7476190064; Fri, 30 Mar 2012 07:58:36 -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 07:58:36 -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//+VNoI=
Date: Fri, 30 Mar 2012 14:58:36 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D4986@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>
In-Reply-To: <CAAed6vtnoi2fTEsb7kNpVXsnbh7H60mn7wUwcPMu0juVBSMCsw@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 14:58:38 -0000

> In the case where a device only has one interface, then clearly only the DUID
> is needed to provision it, or assign a specific address to it in the case of a
> static-binding/reservation.  If devices have multiple interfaces, then the DUID
> is not enough to uniquely reserve an address for each interface (wired and
> wireless, for example).  In that case, you need the DUID+MAC.

No, that's what IAID is for.   DUID+IAID provides a unique identifier that allows a client to configure multiple interfaces, or multiple network identities, using a consistent DUID.   MAC address is _not_ related to this.   At all.

v2.23.0 | Report a Bug | By Email