IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt

perl-list <perl-list@network1.net> Mon, 16 July 2012 12:52 UTC

Return-Path: <dankney@network1.net>
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 897C721F8814 for <dhcwg@ietfa.amsl.com>; Mon, 16 Jul 2012 05:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XvRH577QNr8B for <dhcwg@ietfa.amsl.com>; Mon, 16 Jul 2012 05:52:40 -0700 (PDT)
Received: from zimbra.network1.net (zimbra.network1.net [74.115.181.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8AC21F8813 for <dhcwg@ietf.org>; Mon, 16 Jul 2012 05:52:40 -0700 (PDT)
Received: from zimbra.network1.net (localhost [127.0.0.1]) by zimbra.network1.net (Postfix) with ESMTP id B3A9A5410F0; Mon, 16 Jul 2012 08:53:23 -0400 (EDT)
Date: Mon, 16 Jul 2012 08:53:23 -0400
From: perl-list <perl-list@network1.net>
To: Glen Eustace <G.Eustace@massey.ac.nz>
Message-ID: <1979796211.37016.1342443203647.JavaMail.root@network1.net>
In-Reply-To: <CC298347.AE7B%G.Eustace@massey.ac.nz>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_37015_2069659810.1342443203646"
X-Originating-IP: [74.115.182.5]
X-Mailer: Zimbra 7.2.0_GA_2669 (ZimbraWebClient - GC20 (Mac)/7.2.0_GA_2669)
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt
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: Mon, 16 Jul 2012 12:52:41 -0000

I can't remember which, but it is either Mac OS or windows 7 that use a random mac to generate the link local address and in turn use the link local to generate the DUID (or the reverse - in any case, it wasn't the mac of the interface). D-Link routers use no mac at all and just randomly generate the DUID. Neither of those device's macs can be gotten from the DUID. 

----- Original Message -----

> From: "Glen Eustace" <G.Eustace@massey.ac.nz>
> To: "dhcwg" <dhcwg@ietf.org>
> Sent: Sunday, July 15, 2012 4:45:02 PM
> Subject: Re: [dhcwg] I-D Action:
> draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt

> > Some equipment doesn't use any mac at all to generate the DUID
> > which is perfectly acceptable in the related RFC.
> > If the DUID always used the mac, then we wouldn't need this draft
> > at all.

> Correct but in an Enterprise environment like ours, the majority of
> clients do. I haven't seen any that don't yet. I just thought it
> might be interesting to see in how many cases the MAC used for IPv4
> actually was successful in identifying the client (for back office
> purposes)

> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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