Re: Deprecating IPv6

Havard Eidnes <he@uninett.no> Mon, 05 June 2017 09:20 UTC

Return-Path: <he@uninett.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C536C126D05; Mon, 5 Jun 2017 02:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YOZG0ASvetWV; Mon, 5 Jun 2017 02:20:50 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [158.38.62.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9E00B124E15; Mon, 5 Jun 2017 02:20:50 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [158.38.62.77]) by smistad.uninett.no (Postfix) with ESMTP id 5F38943E9B9; Mon, 5 Jun 2017 11:20:47 +0200 (CEST)
Date: Mon, 05 Jun 2017 11:20:47 +0200
Message-Id: <20170605.112047.1868975436553913398.he@uninett.no>
To: randy@psg.com
Cc: ipv6@ietf.org, draft-bourbaki-6man-classless-ipv6@ietf.org
Subject: Re: Deprecating IPv6
From: Havard Eidnes <he@uninett.no>
In-Reply-To: <m2lgp6etfi.wl-randy@psg.com>
References: <e892e15f-3479-8099-0d72-41fe18ecabb8@gmail.com> <CAKD1Yr1j5W7YpxVGUYfjfKXGmW=RKd98=2z8m-5TMdhjWRvJYA@mail.gmail.com> <m2lgp6etfi.wl-randy@psg.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FuHq8nw-9ElRdqyL9jULBzhTXdk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 05 Jun 2017 09:20:53 -0000

Hi,

a tangential remark related to the wording in the draft:

>    The length of the Interface Identifier in Stateless Address
>    Autoconfiguration [RFC4862] is a parameter; its length SHOULD be
>    sufficient for effective randomization for privacy reasons.  For
>    example, a /48 might be sufficient.

I think the "a /48 might be sufficient" part is not the best way
to express it.  When you talk about a /48 in IPv6, that's usually
interpreted to correspond to an address space which contains 2^16
/64s.

Suggestions for other ways of expressing what I think is intended
would be "For example, a 48 bit long suffix might be sufficient"
or "For exmple, 48 bits of address space might be sufficient".

Regards,

- Håvard