IETF Logo Mail Archive

Re: [dhcwg] DUID+IAID

"A. Gregory Rabil" <greg.rabil@jagornet.com> Fri, 30 March 2012 15:03 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 8390D21F869D for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 08:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[AWL=-0.203, 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 712Uu+SrQPow for <dhcwg@ietfa.amsl.com>; Fri, 30 Mar 2012 08:03:12 -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 C4D3A21F8663 for <dhcwg@ietf.org>; Fri, 30 Mar 2012 08:03:11 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so690594bku.31 for <dhcwg@ietf.org>; Fri, 30 Mar 2012 08:03:10 -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=E9Cocr4KeUO8WeHo4ujSWE1FmI15z963HzIM/pMd+LI=; b=U4lpNTVahHjkXFdMxCCtrNzuuOa/N7nC7Dqz6j1UjKYnSjOKAAYAQxxk7EONIGc8LM p9GJmub+ME9x/bQfblHrSjBiMOb75ogdxKpyPoVWgojHNbEWN83vJR6dCrYXayK4eE8u uyONnfquHhrJL4nijRiKpBodNztf6O0+VGe2OJXH+9tRsFI04jrj3uiW0Hbktto4GsJj VK0idil4ciBjXpod1U+vX16YApwoF5rOMiz1VeIAzQHQQJCENQnAAEVBkQaVKrHqVF7E rs479g4a62e1dQ42PatWNCKL5rSk4buUJ/+OW4W9wzp/1V2xTkh57JIMmFEeJ/eZ90w6 7A8g==
MIME-Version: 1.0
Received: by 10.205.137.15 with SMTP id im15mr1117060bkc.54.1333119790331; Fri, 30 Mar 2012 08:03:10 -0700 (PDT)
Received: by 10.204.22.4 with HTTP; Fri, 30 Mar 2012 08:03:10 -0700 (PDT)
In-Reply-To: <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> <8D23D4052ABE7A4490E77B1A012B6307472D4986@mbx-01.win.nominum.com>
Date: Fri, 30 Mar 2012 11:03:10 -0400
Message-ID: <CAAed6vtKw40+BiK4a9KwKxZZ_fZSh3N7kjAMNeyXGUuyASwfvw@mail.gmail.com>
From: "A. Gregory Rabil" <greg.rabil@jagornet.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Gm-Message-State: ALoCoQmn+wr3lnSlOyJsDcFhHp+q4tXup5Dt+UR/Fmbl6DeyOIXV/sN4o7pFyEE/WyPPPuBtSkb3
Content-Type: multipart/alternative; boundary="000e0ce0f68e8bb72204bc772321"
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 15:03:12 -0000

If I want to assign a specific address to the wired interface and a
separate, specific address to the wireless interface, how do I know what
the IAID will be for each of them?

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

> > 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