Re: 6MAN Adoption call on draft-gont-6man-deprecate-eui64-based-addresses-00

Tom Taylor <tom.taylor.stds@gmail.com> Sat, 30 November 2013 17:15 UTC

Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C851AE022 for <ipv6@ietfa.amsl.com>; Sat, 30 Nov 2013 09:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IH2SVzD0Xa3Z for <ipv6@ietfa.amsl.com>; Sat, 30 Nov 2013 09:15:48 -0800 (PST)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0DEEA1ADFCD for <ipv6@ietf.org>; Sat, 30 Nov 2013 09:15:47 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id qd12so18311045ieb.17 for <ipv6@ietf.org>; Sat, 30 Nov 2013 09:15:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=V+4GtytRdNYta+Gd7VyeBTVHsHMRBw//i916+2Udnn8=; b=X6Vfbhd/4YP982yx2Q3t4ZMStxurkLhPQCaBc1pSYHh+N7byZjGFhPrv0SoVDDbPRT lM8mbC4FyVsyiJH86GL9hbl9ZYvLmGryZFZajgHXuMFSImjv1toS6YP+iM0lvpvcDubF m7yJp1E5k7EYtskKwO8zzgUK7Rv9YsAppYTe7zDo/jyzCbHONPiGMecYF4DsEoiKnA9m PAzlC0mmEdY1IuwVOjsmpbI7mBjwAbQgsYYWJWsCTTGgouJo6Pmcp2NsK4HtsEEIa9BX i01FrO+GzcykUmP/KQTzNjliU0ELNzfNVicRsOfTisQFj44WnCpT1JA2orD6XT6TNZcN YmQQ==
X-Received: by 10.50.238.196 with SMTP id vm4mr11024541igc.43.1385831746377; Sat, 30 Nov 2013 09:15:46 -0800 (PST)
Received: from [192.168.1.65] ([64.56.250.4]) by mx.google.com with ESMTPSA id i11sm56416068igh.0.2013.11.30.09.15.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 30 Nov 2013 09:15:45 -0800 (PST)
Message-ID: <529A1D3E.2080608@gmail.com>
Date: Sat, 30 Nov 2013 12:15:42 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: 6MAN Adoption call on draft-gont-6man-deprecate-eui64-based-addresses-00
References: <F681E049-43A2-4A61-8692-C59A1BF356A6@employees.org> <5296244E.3080004@gmail.com> <52962629.7020907@innovationslab.net> <529674F6.201@gmail.com> <1385779774.33535.YahooMailNeo@web142505.mail.bf1.yahoo.com>
In-Reply-To: <1385779774.33535.YahooMailNeo@web142505.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Nov 2013 17:15:50 -0000

David Farmer's note the other day made things clearer. To quote:

"Early in our IPv6 adoption we preferred EUI-64 addresses because we 
already tracked ports, MAC and IPv4 address associations for our entire 
network, and when EUI-64 addresses were used we didn't need any 
additional tracking.  We knew were all MAC addresses were We knew we 
needed to add IPv6 address tracking to our management system regardless, 
but we could initially use EUI-64s without any additional tracking."

Tom

On 29/11/2013 9:49 PM, Mark ZZZ Smith wrote:
>
>
>
>
> ----- Original Message -----
>> From: Tom Taylor <tom.taylor.stds@gmail.com>
>> To: Brian Haberman <brian@innovationslab.net>; ipv6@ietf.org
>> Cc:
>> Sent: Thursday, 28 November 2013 9:40 AM
>> Subject: Re: 6MAN Adoption call on draft-gont-6man-deprecate-eui64-based-addresses-00
>>
>> Device tracking, I believe.
>>
>
> Some more detail would be useful.
>
> Windows apparently abandoned EUI-64 based addresses quite a while ago, and my android phone uses temporary IPv6 addresses for outbound connections. So specifically basing some form of device tracking mechanism on the presence of EUI-64 format IIDs for those two common platforms is and has become quite ineffective.
>
> I'm also confused by the comment about IPv4. There probably isn't enough host address space in commonly deployed IPv4 addresses (i.e., /24s or longer) to put any useful amount of an EUI-48 or similar sized layer 2 address in the IPv4 address, unless they're also deploying locally administered layer 2 addresses.
>
>
>
>
>
>> On 27/11/2013 12:04 PM, Brian Haberman wrote:
>>>   Tom,
>>>
>>>   On 11/27/13 11:56 AM, Tom Taylor wrote:
>>>
>>>>   It is clear that
>>>>   some network operators rely on EIU-64-based IPv6 addresses for
>>>>   administrative purposes, as a carry-over from IPv4, and do not at
>>>>   present wish to modify their procedures.
>>>>
>>>
>>>   Could you elaborate on the above?  What procedures are they carrying
>>>   over from IPv4 WRT EUI-64-based addresses?
>>>
>>>   Regards,
>>>   Brian
>>>
>>>
>>>
>>>   --------------------------------------------------------------------
>>>   IETF IPv6 working group mailing list
>>>   ipv6@ietf.org
>>>   Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>
>>>   --------------------------------------------------------------------
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>