IETF Logo Mail Archive

Re: [dhcwg] DUID+IAID

Ted Lemon <Ted.Lemon@nominum.com> Thu, 29 March 2012 14:41 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 C61D121F88EA for <dhcwg@ietfa.amsl.com>; Thu, 29 Mar 2012 07:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.193
X-Spam-Level:
X-Spam-Status: No, score=-106.193 tagged_above=-999 required=5 tests=[AWL=-0.194, 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 XcRlKi1YsvKL for <dhcwg@ietfa.amsl.com>; Thu, 29 Mar 2012 07:41:37 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 30B7421F88C7 for <dhcwg@ietf.org>; Thu, 29 Mar 2012 07:41: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 DSNKT3R0oIqbKRzEevaFJPwy25U34n9R+De4@postini.com; Thu, 29 Mar 2012 07:41:37 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 315621B819B for <dhcwg@ietf.org>; Thu, 29 Mar 2012 07:41: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 28F86190064; Thu, 29 Mar 2012 07:41: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; Thu, 29 Mar 2012 07:41:36 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "A. Gregory Rabil" <greg.rabil@jagornet.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DUID+IAID
Thread-Index: AQHNDbbP4FgtkXLiwESgwgUDJGkpD5aBV/Go
Date: Thu, 29 Mar 2012 14:41:34 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D4438@mbx-01.win.nominum.com>
References: <CAAed6vtfuig6Y1Zqqxd=rQc7MarO7vfkYVDG0HbzeaQrx7GcYw@mail.gmail.com>
In-Reply-To: <CAAed6vtfuig6Y1Zqqxd=rQc7MarO7vfkYVDG0HbzeaQrx7GcYw@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
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: Thu, 29 Mar 2012 14:41:38 -0000

> Ted (don't mean to call you out here, but it is prevalent to my question) wrote this on the ISC DHCP list:
>>DUID+IAID uniquely identifies the interface; DUID uniquely identifies the host.
> My question is can this be guaranteed?

No, I was oversimplifying.   The intent was that there might well be more than one IAID per interface.   In practice, I would expect an IA_NA and an IA_TA to use different IAIDs, for instance.   Similarly for IA_PD.   It was also intended that the client could ask for more than one set of IA_NA addresses per interface if it wanted to present more than one identity to the network.

Even if what I'd said weren't an oversimplification, it wouldn't work to use the MAC address as the IAID, because it's unnecessarily big.   I expect it to be rare that a single DHCP request will require 2^48 IAs.

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