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

"Eustace, Glen" <G.Eustace@massey.ac.nz> Thu, 12 July 2012 20:22 UTC

Return-Path: <G.Eustace@massey.ac.nz>
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 4BE8411E809C for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 13:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 qLjc2qNpb6YI for <dhcwg@ietfa.amsl.com>; Thu, 12 Jul 2012 13:22:53 -0700 (PDT)
Received: from mu-mail3.massey.ac.nz (mu-mail3.massey.ac.nz [130.123.129.187]) by ietfa.amsl.com (Postfix) with ESMTP id 306FC11E8096 for <dhcwg@ietf.org>; Thu, 12 Jul 2012 13:22:52 -0700 (PDT)
Received: from tur-mm5.massey.ac.nz (tur-mm5.massey.ac.nz [130.123.96.133]) by mu-mail3.massey.ac.nz (Postfix) with ESMTP id 5D1571B3182; Fri, 13 Jul 2012 08:23:24 +1200 (NZST)
Received: from tur-exch-cas1.massey.ac.nz (Not Verified[10.100.189.3]) by tur-mm5.massey.ac.nz with MailMarshal id <B4fff323b0000>; Fri, 13 Jul 2012 08:23:23 +1200
Received: from TUR-EXCH-NODE2.massey.ac.nz ([fe80::6d90:b430:e061:20ed]) by tur-exch-cas1.massey.ac.nz ([fe80::590d:38a9:56de:47a4%13]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 08:23:23 +1200
From: "Eustace, Glen" <G.Eustace@massey.ac.nz>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt
Thread-Index: AQHNYGwvIo7YZHxtLUu8zFI5r0fWlA==
Date: Thu, 12 Jul 2012 20:23:23 +0000
Message-ID: <CC2589A3.ADDF%G.Eustace@massey.ac.nz>
In-Reply-To: <BEF0160F-9A8C-4DF3-94FC-9F69BFB09CAF@nominum.com>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.10.0.110310
x-originating-ip: [10.100.189.3]
Content-Type: multipart/alternative; boundary="_000_CC2589A3ADDFGEustacemasseyacnz_"
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <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: Thu, 12 Jul 2012 20:22:54 -0000

As one of these IT departments, I thought that some empirical data might be useful.

We have now got ISC dhcpd running on our main campus and I have just completed adding native IPv6 to the majority of networks.  We do NOT yet have DUIDs stored in our databases but do have the MAC address for the primary NIC for all University owned equipment.

I have the  hardware-ethernet included in each host declaration for both IPv4 and IPv6.  Using the ISC fudge of deconstructing the type 1 DUID, we have 1224 matches out of 1693 active leases.  Whilst not perfect, it is actually better than I expected and for us does add value.

I have not yet attempted to determine why we failed to match the remaining leases, could be a number of reasons

  1.  Private equipment for which we do not have a MAC in the DB
  2.  The DUID generated used a MAC we don't have in the DB
  3.  The MAC we have is wrong.
  4.  etc

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Glen Eustace, Infrastructure Development Engineer (BC/DR)
Information Technology Service, Massey University PN460
Tennent Drive, Palmerston North, New Zealand
Ph: +64-6-3569099 x 81005, Fax: +64-6-3505607, Mob: +64-27-4500321

From: "Ted com>" <Ted.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>
Date: Thu, 12 Jul 2012 19:49:59 +0000
To: Andre Kostur <akostur@incognito.com<mailto:akostur@incognito.com>>
Cc: "<dhcwg@ietf.org<mailto:dhcwg@ietf.org>>" <dhcwg@ietf.org<mailto:dhcwg@ietf.org>>, Marc Perea <marccp@srttel.com<mailto:marccp@srttel.com>>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-00.txt

On Jul 12, 2012, at 3:40 PM, Andre Kostur wrote:
Ok, if we're restricting to ISP environments, why not mandate in such
environments that they should be using the Remote ID (RFC 4649) to
specify the downstream "client".  Note that in DOCSIS environments,
this is already happening.  (Just not in RFC 4649 form... but in an
enterprise-specific option 17).

It's my understanding that the main motivator for this draft is use in corporate IT departments that inventory machines by MAC address.   I guess it would also be useful for ISPs, but that's certainly not the use case that I've heard mentioned most.

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