Re: draft-bourbaki-6man-classless-ipv6-00

Roger Jørgensen <rogerj@gmail.com> Sun, 04 June 2017 08:56 UTC

Return-Path: <rogerj@gmail.com>
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 9517D1294C8 for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 01:56:02 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 Jvmo2Jur2Uy4 for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 01:56:01 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 156FE1294C7 for <ipv6@ietf.org>; Sun, 4 Jun 2017 01:56:01 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id 4so637450ybl.1 for <ipv6@ietf.org>; Sun, 04 Jun 2017 01:56:01 -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=cXtzOceEL9aJNfTHlqVoG867rJqXi2a6tIQgb1ymMXI=; b=s1kSQFdtiQkJd4ENPz4tts4x9WH4icstgdss4sdEWOUVBKmCAz0lAWNeDNFstaR+Xi 8mGOfJgtlVczyQzvFSJr0KW0O6EZ6fUvvE9ihQLQmopnk2DTLoFl0nw989bkmFJBvvsO 3PlN5igBwT/EegFbJ+HNoyKCWz+hNiHo0tzQWPmThk49fL30Yi80Pv0Y0a+f0s5UcLI+ GXR//hhSEPlWVF9kbYTo4iYUkn6APfrzVU3vlzWkZsyxLREOgItKdvBpMuIUnD+sQmGz G/aqJ4CDY9Jl3UVTq8sc/6U+elsOjeVde7Ym1VRo0tXXBJYxPEefwx67w9iSpe8fAHwq vU4w==
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=cXtzOceEL9aJNfTHlqVoG867rJqXi2a6tIQgb1ymMXI=; b=nSlMMxQVgKPeEBkx+oYOTKyw57ezIcxdJYFx6lBYrs0YHRX7GXZ1iFnutZIGpvwXwq JvRnRwsHaz1ye8z3yAC1JOh/jpZ3A/DfFoxXCFch73lDcAG16Tat5M2SsPhVVeIK8sah 4ijxpdejm6zys2E7pgbWrVRNZ41SZ2/e2GIgqbfeFGnlYEXo20mlWVL3BO3Y+q9hXdx4 EXeV5PIW+8bkSkrHgFIyH9EI2lkWM2qsmbhig9KYGtWLwSSCHOyDEwMx8GM/JKmOHTYz 7lylwVhBFntmDHbJNhZtd0ps5luZXNm6zwYWjxmO1S9fJ8DC9FudkmdlEcmdFtmfoDbq l0tw==
X-Gm-Message-State: AODbwcBxGNWo0M3PRhJBdkJCeiLeAp9hK4MicmMsVKARJ1rK9sZ6Iy73 4sVe8/J6egiSSz31qXgsVZoxSYeLOr5Z
X-Received: by 10.37.56.17 with SMTP id f17mr5467980yba.130.1496566560301; Sun, 04 Jun 2017 01:56:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.246.7 with HTTP; Sun, 4 Jun 2017 01:55:59 -0700 (PDT)
In-Reply-To: <CAKD1Yr3ppM0UF8HoN8PgS7F0iEmK26ebiuJK=tkAdZnuLWpkZg@mail.gmail.com>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <CAKFn1SEdjhsQ3tKPZdbdfF4ArDzw-FZfjQT68gV55Fc-5vzBvw@mail.gmail.com> <CAKD1Yr3ppM0UF8HoN8PgS7F0iEmK26ebiuJK=tkAdZnuLWpkZg@mail.gmail.com>
From: Roger Jørgensen <rogerj@gmail.com>
Date: Sun, 04 Jun 2017 10:55:59 +0200
Message-ID: <CAKFn1SHASt34ihJmGN0iRFQQzLTMspZfxXHgBjBatXXcRYF4cw@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Lorenzo Colitti <lorenzo@google.com>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/271_L9xe4AGXl31HcZLvKWk4yCk>
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: Sun, 04 Jun 2017 08:56:03 -0000

On Sun, Jun 4, 2017 at 3:33 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Sun, Jun 4, 2017 at 2:34 AM, Roger Jørgensen <rogerj@gmail.com> wrote:
>>
>> > Please stop trying to make IPv6 be the same as IPv4. That will take away
>> > our
>> > ability to make the Internet better once IPv4 is gone.
>>
>> oh totaly agree, but it's already lost, the "operators" don't want to
>> move/change.
>
>
> But they *are* changing. For example: almost 20% of Google users these days
> come in over IPv6. Pretty much all of them are connected to networks that
> support SLAAC and use /64 prefixes. That's a huge number now matter how you
> look at it, and it's showing no signs of slowing down.

look into the numbers, I assume there are one huge group missing there,
the enterprises and that's where the money, and damage will be done.



If/when this draft goes through I am pretty sure I in 10-15years time will come
across something like this :

My device provided by the enterprise will have a /122 and when asking why
the security department will say something along the line because there are X
devices allowed on that segment and we provide them all. And since X match
with /122 we just configure them static on each device.
If I am lucky enough that it's global address space, but most likely it will
be ULA with NAT, because NAT provide security......

No real security, just shortsighted missguided assumptions on howto
provide "security."

this draft don't consider the none-technical side where the real damage
is coming. None will bother to look into why they should use a /64,
they will just hear "oh, IPv6 is classless so we can use whatever we
want", and they will go down that road.



-- 

Roger Jorgensen
rogerj@gmail.com / roger@jorgensen.no