Re: [dhcwg] MAC Address Tracking via DHCP6
"Rajiv Asati (rajiva)" <rajiva@cisco.com> Fri, 01 February 2013 15:57 UTC
Return-Path: <rajiva@cisco.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 E533321F8D29; Fri, 1 Feb 2013 07:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level:
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2KEtOYRzvnh; Fri, 1 Feb 2013 07:57:40 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 25DB321F8461; Fri, 1 Feb 2013 07:57:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=946; q=dns/txt; s=iport; t=1359734260; x=1360943860; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=W8VyQmLR2o5IGgC+IXxgS58wZ0KrP3o85PUeaBJ+kCI=; b=go0B9QILDm52YNh5wQaQTAOOO0Mba1UdSQ2dp2R91eQEAQ2W2IIx+8m+ 3CagF0ycXxBJJUnri6F0G4l7mOQ6Rg/W6q0WNM5VnwdAtQvN6v4fnXUFj mrqP0j5ywAs2imX752LQIo25xsi0QEU+Jygv16OjVU1IXcL8wfw0pJENU A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFALfkC1GtJV2b/2dsb2JhbABFDoVzuSsWc4IeAQEBBHkMBgEIEQMBAgEKVh0IAgQBDQUIiAnDGpBtYQOmZ4I+PoIk
X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="168804226"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 01 Feb 2013 15:57:39 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r11FvdSr003141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Feb 2013 15:57:39 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.193]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Fri, 1 Feb 2013 09:57:39 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Chuck Anderson <cra@WPI.EDU>
Thread-Topic: [dhcwg] MAC Address Tracking via DHCP6
Thread-Index: AQHN/9giM3WALPSOxEqXmVcvCQGGwZhkq+IggAB9qoCAAGDQAIAAAdqA//+ujIA=
Date: Fri, 01 Feb 2013 15:57:38 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B114EE410@xmb-rcd-x06.cisco.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630747479218@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.86.115.198]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F6DBE59987666844985070E3C65C6915@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Hamacher <bhamacher@westianet.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Philipp Kern <pkern@debian.org>
Subject: Re: [dhcwg] MAC Address Tracking via DHCP6
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, 01 Feb 2013 15:57:41 -0000
I agree, Ted. -----Original Message----- From: Ted Lemon <Ted.Lemon@nominum.com> Date: Friday, February 1, 2013 10:49 AM To: Chuck Anderson <cra@WPI.EDU> Cc: Rajiv Asati <rajiva@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Hamacher <bhamacher@westianet.com>, Philipp Kern <pkern@debian.org>, "ipv6@ietf.org" <ipv6@ietf.org> Subject: Re: [dhcwg] MAC Address Tracking via DHCP6 >On Feb 1, 2013, at 10:42 AM, Chuck Anderson <cra@WPI.EDU> wrote: >> There is also draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04 >> which handles the case for DHCPv6 clients. That also requires no >> changes to clients--only the DHCPv6 Relay Agent. > >This document doesn't apply to SLAAC or CGA addresses, though‹just >stateful addresses acquired through DHCPv6. Admittedly, we could also >snoop DHCPINFORM traffic, but there's no guarantee that all devices on >the network will do a DHCPINFORM, even if the O bit is set. >
- Re: [dhcwg] MAC Address Tracking via DHCP6 Rajiv Asati (rajiva)
- Re: [dhcwg] MAC Address Tracking via DHCP6 Chuck Anderson
- Re: [dhcwg] MAC Address Tracking via DHCP6 Rajiv Asati (rajiva)
- Re: [dhcwg] MAC Address Tracking via DHCP6 Ted Lemon
- Re: [dhcwg] MAC Address Tracking via DHCP6 Tomek Mrugalski
- Re: [dhcwg] MAC Address Tracking via DHCP6 Rajiv Asati (rajiva)
- Re: [dhcwg] MAC Address Tracking via DHCP6 Ted Lemon
- Re: [dhcwg] MAC Address Tracking via DHCP6 Tim Chown