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

Mark Smith <markzzzsmith@gmail.com> Sat, 19 August 2017 01:06 UTC

Return-Path: <markzzzsmith@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 5ECDA132407 for <v6ops@ietfa.amsl.com>; Fri, 18 Aug 2017 18:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_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 5vgYAF7B2q6U for <v6ops@ietfa.amsl.com>; Fri, 18 Aug 2017 18:06:17 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 2AC3E13203D for <v6ops@ietf.org>; Fri, 18 Aug 2017 18:06:17 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id n29so9097120uai.5 for <v6ops@ietf.org>; Fri, 18 Aug 2017 18:06:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Bl+om7aj6M6q6dpaLVQW08IMUKTV4sGsadvyIRj4eA4=; b=RcIUfxeSZktc6ufDJyMxxVh+UryAoQ/kJVx+tyFyFJXsz9BZBBWJ/udcb+jxG4/bi8 0Dtrwx4OhfeYFGgrsEL1cdoB0lTdmC7AgKBD4E//fVx0yg/nkLE7+OEFeFz7djNAiZTz NC7Hdp9bgHsLLPgB3SRyBQxNR1NIHYehq6ondf0KgzY3NLjZE7D4lPbqoj6AJN/1Wju5 JFjoVAeXN6Jeqi4Cwm6Lc/OMELt88G6B2Auon9QOyy6MSA/U8/TlJZkpCYR2z4MT493+ EvY15pUvyIDpdZCez0EUqdPw1xmCVoMvtgrLdN16KnpjswiSyENVaPOG85owmR9gclLy m8WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Bl+om7aj6M6q6dpaLVQW08IMUKTV4sGsadvyIRj4eA4=; b=MuLnhlZlK9hfa4RsdWREpbd3v7sxQHEWPnxNakIzwhnoDPtnRo4dpiVsMMZXd8ZmrG MespeA+5KnWLsbVSLZ/jssoFrF/HwhRctlh4X7/1XsSTMHdR6DBUrOVq9cizGWOk5Sg4 XpuewMRIw28u129vthtyEcTMZaaC6vyU5sEz0dg5tJ/YsSZQz9Xt/sMvRXToGx+OSe3v Ijwz/RJl+gfpe8UkhrUAor2f+jT1XEfPSUm1B8jWI34MOqy/dIf9YGZ0+rrdsmevRH6D nSNBoESDuT6Gfx1Lt/NZjiK8yPqUAsxwaHTA5OAeZ/xPMuDVqShEQJdyS4CPWYWaHG+e THdg==
X-Gm-Message-State: AHYfb5iYUh4PIQBS/XO7t0gxftUF+JXx5LN3oTpNNAsTEAPkrCcHmr1h 4agciqGZTSomYGucWTNcdqEnipEpBqCI
X-Received: by 10.176.70.145 with SMTP id r17mr7132742uaa.53.1503104776158; Fri, 18 Aug 2017 18:06:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.209 with HTTP; Fri, 18 Aug 2017 18:05:45 -0700 (PDT)
In-Reply-To: <26F2B05C-7697-48D0-8445-5627E22BCAAE@gmail.com>
References: <CAO42Z2wJBCo1yjguWSy-jzSvndeZTPgtN71FfdEhvqrVAUhZUA@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> <DCFE724E-B207-4527-82A1-5A268AC29989@gmail.com> <E673D8E0-7A55-490C-8316-77E178026C58@employees.org> <82CBE1F8-F9A5-463F-8DB1-B92E5A3F6582@gmail.com> <009d739f-f1e3-0212-c105-48f16768e0d0@gmail.com> <85D0C0DD-D09D-4DE9-A8A7-42C04071484B@gmail.com> <CAJE_bqcimqX+L+F9SvZVNYV_Aj9NXVovbs=XzunfS9qDbiJw2A@mail.gmail.com> <CAKD1Yr1Lcp5P2m7rvKTfuYXv=k1k5z_9q4RyJkWCfZzgjG0b9g@mail.gmail.com> <CAJE_bqd31N6bTZtXRcLtamqCfdeDEHjDHRjVonoN6v-tTyf5qA@mail.gmail.com> <7c03f1c5-8930-6930-9f93-ddfb85c8e825@gmail.com> <CAJE_bqcUXF3gfU_tOtO4La1NV6sCHRR1BH7qVA_nt=qtDK342g@mail.gmail.com> <85066e19-4dbc-f408-4a00-c5b6d7b73d20@gmail.com> <26F2B05C-7697-48D0-8445-5627E22BCAAE@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 19 Aug 2017 11:05:45 +1000
Message-ID: <CAO42Z2wGebU=bd41G9p5k5dVDMdxt6eQsPz4PAyyj_3WqgLcKA@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Qv__M2eHEpudVGFjDTt9pYD-ZIA>
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: Sat, 19 Aug 2017 01:06:18 -0000

On 19 August 2017 at 06:05, Fred Baker <fredbaker.ietf@gmail.com> wrote:
> Hat off...
>
> Why not simply say "a prefix"? We are perpetually wrapped around an axle with the prefix length, but reading this 20 years from now (which is the perspective one should take in writing an RFC - what will it mean when it's history?) I don't see why they would worry about the exact length someone wanted to assign within their own boundaries.
>

I think it matters because prefix length is the compliment of IID
size, and we know that the size and value of an IID has privacy and
security implications.

RFC7421, "Analysis of the 64-bit Boundary in IPv6 Addressing",
suggests that an IID of at least 40 bits is necessary for privacy.

If this draft does not take a position on the size of a prefix given
to a host, it should at least highlight that prefix lengths longer
than /88 can have corresponding IID size related privacy implications,
and may want to reference RFC6973, "Privacy Considerations for
Internet Protocols" and RFC7721, "Security and Privacy Considerations
for IPv6 Address Generation Mechanisms" for more specific IPv6
addressing discussion.

Regards,
Mark.