IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

DY Kim <dykim6@gmail.com> Thu, 17 August 2017 08:54 UTC

Return-Path: <dykim6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52ED81321A8 for <v6ops@ietfa.amsl.com>; Thu, 17 Aug 2017 01:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zZtb3JfX6zHB for <v6ops@ietfa.amsl.com>; Thu, 17 Aug 2017 01:54:01 -0700 (PDT)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB71F132420 for <v6ops@ietf.org>; Thu, 17 Aug 2017 01:54:01 -0700 (PDT)
Received: by mail-pg0-x243.google.com with SMTP id t80so2694696pgb.2 for <v6ops@ietf.org>; Thu, 17 Aug 2017 01:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IlN8bA1An+e2Tdwfie8FgbdJ8B/b5x1CEo6j4J8i+ns=; b=Z+4jJWx6Dn3b42WHqxOEoKH8uktqTg+bAyom8vqIo4Ytb8Q9DDHOTXO511UmRkSQ2G CtOGG7AV1DKEGt6a3bzdksna7tkFhTHEpNj5kFcB2V1dEuELSEbxyMRfULZIzf0YEn0z hnKX9ZzXtz620iMywdvQcbK1QbXRS9uU49SsXIHa7DXcNjMLuu+uEE0qzvuP85mBrd6z kxX9KDxFe/djthPdgnCPssxcDarAs2IcGRboIa/4kImgN3877LQpQzB6pYeaHhV5cI4k Ppqz69/k2/f48FKkWrX8MOHlp0lCf9Iy/6rhI0UXQegKbEGcnaWz5LISufdqS5opIHyn 4EoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IlN8bA1An+e2Tdwfie8FgbdJ8B/b5x1CEo6j4J8i+ns=; b=bbR8HmZjaEGNXPV9s9AHj0xiF6kmZnsE6iuUmqrtCJf0TQUBM+amttjCpAEmIcEcuG wz75CCia6o34S+fiAXZFLihbQd7xhOtNlO9HLSE2FEtjbYMjb4FSUgs7W75GsW87TDHs RFoBxm577puYtU6bjyBZwxLuJbfSGG8NEo9q5NPqvAnlzNoc00Dsw6TC0K3wvHiFgHby HtJEkc6Tc6tgpChaAPqpMlUpYu3WG4y87qpAZC0jvHF8iMZwYK1YsKRzb5VUrxEy4UTB rsy4c91j1QMUqzFN380ttbqYi6ooh87I7THwDbsNQydFBQD3Xc5MKO+40xAvgfHDkz/q l0mQ==
X-Gm-Message-State: AHYfb5jQTuF1dv6qzxOXICnF8wlOt9fb9y9iFCn0bdfJSaadJmJw9GUN bH/CTth4UCbQNg==
X-Received: by 10.99.154.26 with SMTP id o26mr4272707pge.136.1502960041495; Thu, 17 Aug 2017 01:54:01 -0700 (PDT)
Received: from [222.113.135.33] ([222.113.135.33]) by smtp.gmail.com with ESMTPSA id l2sm4868845pgc.27.2017.08.17.01.53.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Aug 2017 01:53:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: DY Kim <dykim6@gmail.com>
In-Reply-To: <7CB3B027-714C-4F18-8AD9-E76060137891@employees.org>
Date: Thu, 17 Aug 2017 17:53:56 +0900
Cc: Simon Hobson <linux@thehobsons.co.uk>, v6ops list <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCFE724E-B207-4527-82A1-5A268AC29989@gmail.com>
References: <CAO42Z2wJBCo1yjguWSy-jzSvndeZTPgtN71FfdEhvqrVAUhZUA@mail.gmail.com> <9bd9f886-f53b-109f-d998-1d4c7adaf3b1@gmail.com> <B6A257C9-7E8A-452D-9C0F-0B10A31990CB@thehobsons.co.uk> <796A0ED0-0F58-43FA-9F81-D4D736A35F3B@steffann.nl> <BD3B4153-2EEF-4BFB-832D-D126A75AEC11@thehobsons.co.uk> <CAN-Dau2jzbQPuE5diEz-XzfRBHY=O1znE8hfy8P-Eee=MVwC_w@mail.gmail.com> <7C6C4FCC-26B9-493D-9992-4663DE6EB9CE@jisc.ac.uk> <3A69468C-98E4-4631-A52F-3D8772646EEE@consulintel.es> <20170807110746.GG45648@Space.Net> <CAO42Z2xXXjKUZ8qQY+b1NgDagX2ZJkqL5gieD+_js59ucp0EMw@mail.gmail.com> <20170810055819.GQ45648@Space.Net> <CAO42Z2xtfsYbw+Wf=ZjyFCmnDbhL17QCkWWRJ7F1+BgGCRiipg@mail.gmail.com> <51268C23-40F4-4476-9025-A1DD3BA37BC3@thehobsons.co.uk> <CAKD1Yr0uBU-LczaZJ5SdNpb_FpB0qfZJ0kNnr=gEviD+F3DTZw@mail.gmail.com> <B13F6A0A-BF0A-404B-A332-5A228F4AFC07@thehobsons.co.uk> <7CB3B027-714C-4F18-8AD9-E76060137891@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hfwJWyiyQso_CY1vNtyJHdNxdCw>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Aug 2017 08:54:04 -0000

I’d hope I’m not bothering busy people too much, but let me recall the history as I remember:

 o 128 bits decided for the IPv6 address length, part of which being prefix, part IID.

 o The next question arose about how to configure the addresses.

 o People noticed that 128 bits are large enough to hold the whole 802 MAC addresses.

 o Soon, they also realized the length of the 802 MAC addresses are going to be extended to 64 bits.

 o Each host interface would be associated with, typically, a 802 MAC, so it should be the most convenient choice to identify an interface.

 o This then led to the possibility that the address can be auto-configured once the hosts are given subnet prefixes, i.e., 64-bit subnet prefix and 64-bit IID.

 o The practice has been over 20 years.

 o By now, IIDs are not to be configured with MAC addresses anymore, but with (hashed) random numbers to provide privacy.

 o Hence, the historical link of the IID to the MAC address is now broken, and so its link to 64 bits. Apparently, IID is now free from 64 bits.

 o And yet, people would now pick the fallen broken branch of 64 bits, and try to graft it back to the trunk IID.

 o As the history started out 20 years ago, the IID would be the master and the 64-bit would be the slave. Now, the history is about to go upside down so that the roles are overturned; the 64-bit is now the master and the IID would be the slave.

This flow of history looks a bit funny to me, I’m afraid.

---
DY


> On 17 Aug 2017, at 16:36, Ole Troan <otroan@employees.org> wrote:
> 
> That's not quite correct, at least not in a historical context.

v2.23.0 | Report a Bug | By Email