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

DaeYoung KIM <dykim6@gmail.com> Thu, 17 August 2017 06:50 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 4ACFE132457 for <v6ops@ietfa.amsl.com>; Wed, 16 Aug 2017 23:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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] 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 5Pf2wQp7IIEy for <v6ops@ietfa.amsl.com>; Wed, 16 Aug 2017 23:50:00 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (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 E00BF126B7E for <v6ops@ietf.org>; Wed, 16 Aug 2017 23:49:59 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id u185so36641776pgb.1 for <v6ops@ietf.org>; Wed, 16 Aug 2017 23:49:59 -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=zhIKkAh0dbt4DAMmDjgVwNcASgPC+7F1hqBXvoRlaM4=; b=CbuMIjXWmnkLeMnhx7YeTnpzEnQ4XyDeGJgsHAq+cfvtURltAoMp+QE1gUmvFN4pKz f499PXbAGOa7HHZ3DQeCjK6/kwIBDDKUQbOKNoFtQ6AYkrosFEUWClm1qQPPjzJpHUir Pc0QNVIJKkalIEw4vQrgeJ7wuffT1ikKDCQXctpHLyh/qqyL+g8rVtesYpe7BEpKGIII OdbZPZ381jqRHvnlAC9OBZsrLW7TH+AtVka10cN44vOZK8cAyWFuUDdJJNiv3b0DT8SD xD+CZY+2DughBARlsQG67SrqTMiGeHrval3/x8PFE4gG70nAQPTnkXqjJWFjhn5cgHu0 +DIQ==
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=zhIKkAh0dbt4DAMmDjgVwNcASgPC+7F1hqBXvoRlaM4=; b=R4Z3weLVHnASDjMF+GG27HWpV6M2kthyxUcCpEdunYwt+uzCnfJZA/vHlw41LDsXh6 6HM7FNm4GEDCwwZLj0QXrLn0zvhq1tBIZUHrrAT+CEjVySiHEREWadv3VLa0DADlyMn8 3FbhupoJL0iehgmWGzOpzl4g7FyN39teOeof7gJm9C1GORvmQvfKguMpqOoHGNLCM4Ez cmVtUOcB5UGSrlFrhAumTtVDe/cH2/FBmFjCmY38Y/lkh/uYAlYvCP7vRl5696tHVz+b fbcxYeDd2fIKqpUuCXWFSFk91f6XtLcJhq7K7/DDEDLRerdqX/lXfPHjri/xBYjI+SLS mHOA==
X-Gm-Message-State: AHYfb5giSNRtnPQ24a5F7AsxbT9D0umocbhWy37bPP4frKUhMlmQgZa9 tmrOY+8q35M8Kw==
X-Received: by 10.84.215.205 with SMTP id g13mr4705350plj.8.1502952598113; Wed, 16 Aug 2017 23:49:58 -0700 (PDT)
Received: from [100.68.118.228] ([39.7.58.87]) by smtp.gmail.com with ESMTPSA id h14sm5457965pgn.34.2017.08.16.23.49.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Aug 2017 23:49:56 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: DaeYoung KIM <dykim6@gmail.com>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <CAKD1Yr1XfwxkXGN2e7wBgSst2734BDUtZXe=yziYymR0N9hROw@mail.gmail.com>
Date: Thu, 17 Aug 2017 15:49:53 +0900
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>
Content-Transfer-Encoding: quoted-printable
Message-Id: <386BBA22-2896-4AA1-99BD-EAAF11122C5A@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> <85DFAB58-149C-405E-A497-3CBB497828B4@gmail.com> <CAKD1Yr1sCuJdkO8+DyythdxsfZgdYA10oASmn66rtZrQNr-yiQ@mail.gmail.com> <7A6949B4-C49A-4E3A-BA0E-1465AEB61115@gmail.com> <CAKD1Yr2sTsiwrjuWwDTY=6+oL8y83YPmwmdGKAOR45JbfjrUpA@mail.gmail.com> <260A83D9-60ED-40F6-BE41-8E13F466AF9A@gmail.com> <CAKD1Yr1XfwxkXGN2e7wBgSst2734BDUtZXe=yziYymR0N9hROw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AghQRRm7fEZHkVbuF8yvJ-C8LGI>
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 06:50:01 -0000

Sent from my iPhone

> Ah, I see. If you're asking whether you can use this technique to hand out a /96 per host, then the answer is no. You can't use this technique because this technique presumes the use of SLAAC, and SLAAC only works with 64-bit prefixes (except for addresses in ::/3, which aren't routable on the Internet).
> 
> If you're suggesting that SLAAC be changed to support non-64 bit prefixes, that topic is out of scope for this document and this working group

As I know, SLAAC by itself doesn't impose restrictions on the IID length. It's Addr Arch (4291bis) that imposes it.

Then, are all deployed SLLAC software hard-coded to 64 bits? If properly implemented, the IID length should remain a parameter that can be set by an admin.

Should the latter be the case, my life would get easiest.

> If you're willing to use something other than SLAAC, such as DHCPv6, then all you need is one /64 for your whole network and you can number as many devices as you want.

If not for SLAAC, this would certainly be my last option.