From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by huchra.bufferbloat.net (Postfix) with ESMTP id 3CD9C21F19C for ; Mon, 17 Feb 2014 15:01:53 -0800 (PST) Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by MAIL1.WPI.EDU (8.14.8/8.14.7) with ESMTP id s1HN1q5i022437 for ; Mon, 17 Feb 2014 18:01:52 -0500 X-DKIM: Sendmail DKIM Filter v2.8.3 MAIL1.WPI.EDU s1HN1q5i022437 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wpi.edu; s=_dkim; t=1392678112; bh=CxNKCWCkRk89TblivWoGuhRLt4V9krDF67cQF21GRQc=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=tKmTOzyT3T8l0DTIudGznhLORsuH4Ug2BcETGUto3cXgpX9B1W/C//ecvsySC8Uoq /kMp4w1ikZld4JCFgV9q8rcLa3n30tVAaLfG4USpRYH4opN28GyOY4AdyA/9Grf3Ql Z33FgBi6m1foiMTFskc1MOBhGQdkUdMWXiIqkNGM= Received: from SMTP.WPI.EDU (SMTP.WPI.EDU [130.215.36.186]) by MAIL1.WPI.EDU (8.14.8/8.14.8) with ESMTP id s1HN1qNH022432 for ; Mon, 17 Feb 2014 18:01:52 -0500 Received: from angus.ind.WPI.EDU (ANGUS.IND.WPI.EDU [130.215.130.21]) by SMTP.WPI.EDU (8.14.4/8.14.4) with ESMTP id s1HN1pmp030028 for ; Mon, 17 Feb 2014 18:01:51 -0500 (envelope-from cra@WPI.EDU) Received: from angus.ind.WPI.EDU (localhost [127.0.0.1]) by angus.ind.WPI.EDU (8.14.4/8.14.4) with ESMTP id s1HN1orB030210 for ; Mon, 17 Feb 2014 18:01:50 -0500 Received: (from cra@localhost) by angus.ind.WPI.EDU (8.14.4/8.14.4/Submit) id s1HN1ofd030209 for cerowrt-devel@lists.bufferbloat.net; Mon, 17 Feb 2014 18:01:50 -0500 X-Authentication-Warning: angus.ind.WPI.EDU: cra set sender to cra@WPI.EDU using -f Date: Mon, 17 Feb 2014 18:01:50 -0500 From: Chuck Anderson To: cerowrt-devel@lists.bufferbloat.net Message-ID: <20140217230149.GE27322@angus.ind.WPI.EDU> Mail-Followup-To: cerowrt-devel@lists.bufferbloat.net References: <20140215152809.GF26063@angus.ind.WPI.EDU> <20140217101154.GA1958@ens-lyon.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140217101154.GA1958@ens-lyon.fr> User-Agent: Mutt/1.5.20 (2009-12-10) Subject: Re: [Cerowrt-devel] dhcpv4 to slaac naming rfc ready to submit X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 23:01:54 -0000 On Mon, Feb 17, 2014 at 11:11:54AM +0100, Baptiste Jonglez wrote: > On Sat, Feb 15, 2014 at 10:28:10AM -0500, Chuck Anderson wrote: > > At best, this is a partial solution. Using a Modified EUI-64 (RFC4291 > > sec 2.5.1) is not very reliable. Many systems out there, including > > Windows and recent Linux distributions, do Privacy Addressing by > > default, so you will never find their SLAAC address by assuming they > > constructed their address using EUI-64 based on their Link Layer > > Address. Also, they may not respond to ICMPv6 echo requests due to > > firewall settings. > > Privacy extensions define *additional* addresses, while keeping the SLAAC > addresses. RFC4941 does not explicitely state so, but it is hinted at in > Section 2.4, third paragraph. Well, whatever Windows 7 does, it doesn't provide *ANY* EUI-64 address at all, so this won't work with the most popular platform out there.