IETF Logo Mail Archive

Re: [dhcwg] DUID+IAID

"A. Gregory Rabil" <greg.rabil@jagornet.com> Fri, 30 March 2012 14:19 UTC

Return-Path: <greg.rabil@jagornet.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 4DDC921F86D1 for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 07:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
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 wjTVJIQvhdHm for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 07:19:03 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 94D2B21F86C6 for <dhcwg@ietf.org>; Fri, 30 Mar 2012 07:19:03 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so636598bku.31 for <dhcwg@ietf.org>; Fri, 30 Mar 2012 07:19:02 -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:x-gm-message-state:content-type; bh=y8gyJiNLbc3oCpmI3hlO2hOoNhtYOQ2L4LDfn1NkxHw=; b=Oi/C9oa96MJOpHvlmTu4THcVoIiW23URTiQJfPqi/RHcK9YugEU51vP1ZvuS+eqj9d 4oOTwGgkasZah/2x3cHkZ3NE5RCvOVf7xierJFc5zfScviG3bGIhEs6Zf/y2gL9GUUMH vQTQJqnUh4R3051aDxDDqWtb41unvsCm2Jm/NFa0nqNBkqgD/Q8S3pguXKK4YJe3H13Q ppUhzTWCdVu9GUeyIlKXXV36YEqpRpIHQHB5xSdJoJENMr7pK3vTFx8KYfwG6PlrfNrt UTMXs6Q/UKhm256Lc2RMhgALE2oSMufHXeSmxPRbU0rwg4MbxFF7MCgI8GTIunVqcbb2 HyRw==
MIME-Version: 1.0
Received: by 10.204.150.78 with SMTP id x14mr1024470bkv.114.1333117142570; Fri, 30 Mar 2012 07:19:02 -0700 (PDT)
Received: by 10.204.22.4 with HTTP; Fri, 30 Mar 2012 07:19:02 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307472D4946@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>
Date: Fri, 30 Mar 2012 10:19:02 -0400
Message-ID: <CAAed6vtnoi2fTEsb7kNpVXsnbh7H60mn7wUwcPMu0juVBSMCsw@mail.gmail.com>
From: "A. Gregory Rabil" <greg.rabil@jagornet.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Gm-Message-State: ALoCoQn74qpuXxPxoh/sf2yHKHUhEMkHgx3GGrNxGfOH1BFEHMSnMENpxPjr0dCYoQcbE+k7u8ej
Content-Type: multipart/alternative; boundary="0015175df040ba16e404bc7685fd"
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:19:04 -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.

Greg

On Fri, Mar 30, 2012 at 10:07 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > Okay, so given that the MAC address is not unique, then in order to
> "provision"
> > devices (aka static binding, reservation, or manual dhcp), the
> administrator must
> > know both the DUID and the MAC of the device to be provisioned, correct?
>
> If you "provision" you mean "connect to a back-office database that only
> has the MAC as a key" then yes.   Otherwise no.
>

v2.23.0 | Report a Bug | By Email