Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

Ca By <cb.list6@gmail.com> Mon, 09 November 2020 16:17 UTC

Return-Path: <cb.list6@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 2C1EE3A11A1; Mon, 9 Nov 2020 08:17:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 nBxkERMNokjF; Mon, 9 Nov 2020 08:17:56 -0800 (PST)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 6DA393A119E; Mon, 9 Nov 2020 08:17:56 -0800 (PST)
Received: by mail-il1-x133.google.com with SMTP id g15so8804763ilc.9; Mon, 09 Nov 2020 08:17:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gfxmM8BKxZl/FtTeMVI7FWrjzxFtIn2Je77kYNYH+fE=; b=CRaWBSlD/7DkeOd7stw3OGazn0cumAt7GM6/2MvwvbITzXzUxEfMSm3kAum+hEfzv7 kGrZmX1uiJ7uawdudmFalfgna6pMjcIg74ACoY0gWqEzgY65C75/aWH/PPOqjCVwszRy tTUTbkLBHKbAvo7z7ZRK4ek+izsEgPf6l4mVIcx2E4Eyz99QH8X4++M21rZTGLkwsN4/ 4sK2bGZXqKQgwOldTxJthL0tAm1h1Gm0cvF5GiP2fVae/0f/ZqDnkzl0mgm3b4SCSNYu 4y5VjIUn02QoAGm3jKCne7aeHvLQgWOagD9+oCMHitsUoGZCrSzn8VrBKuEJlgxtW7or vxQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gfxmM8BKxZl/FtTeMVI7FWrjzxFtIn2Je77kYNYH+fE=; b=lclL9Z2JwO4seOXayCmo7cVnbnSIymrQRQP6xURl1flVEzPBRZjfYQJN6n3s9AEwBt oXfEP9tdgfbDFG4RCYqgX01QcsbHqERMPRnPv1VJV26zRjbmyEX4orMOcJk3c6F5ANI8 /yul24dUoHCfXxYqO8pfzAAclbntO3wG61ieiGN+tP/F79DsFl0Z1CJSPVaL9kx6w9RT jlTEjvAtkEOmPBQQwCMpHjsfm6LRI21YlcRLusezi9fzs65xcM19DcdsNEF7Zjsb7JB1 IgEPP/aqgLRf9/UMiS6r/2upQQAhSrHnOaE1F4g/wykzAQH3csTGtRU8tezDAYlb3rl1 CpnA==
X-Gm-Message-State: AOAM531WcO0nkK+trlDp10d2ED79DV8hdUwC7y3VYvTjUWNfJNsU2YOF H6V8pHeRZR/CJyDtI+aGu1o1J8U/MUGcS6obr7RsYOU2
X-Google-Smtp-Source: ABdhPJyhLgw7A0KFV2gcKyOnlZB2UZf7oFS1xqeafQOZpQnL1PVuEKZNtIuewFPQrbjQeGvF5pSDGJanMxbKNPgUcWA=
X-Received: by 2002:a92:5e9a:: with SMTP id f26mr10621907ilg.129.1604938675779; Mon, 09 Nov 2020 08:17:55 -0800 (PST)
MIME-Version: 1.0
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CABNhwV13gggo9XfRvrR31bCUptZuAiosK5ebMmnzDdinKqmrBw@mail.gmail.com> <B7B3091C-92E0-482A-8D16-AD6DCFD1E714@isc.org> <CAD6AjGSCnG_fyorW2-tEqzzTfj897Knf55-0QV9DPcDKt45VOA@mail.gmail.com> <F323E4EB-5AAA-4C34-9EA2-06D4A0839308@thehobsons.co.uk>
In-Reply-To: <F323E4EB-5AAA-4C34-9EA2-06D4A0839308@thehobsons.co.uk>
From: Ca By <cb.list6@gmail.com>
Date: Mon, 09 Nov 2020 08:17:44 -0800
Message-ID: <CAD6AjGR-LLQVZ2CQ+SXYnEvJYBVSLPnC3wm71q5XoSzqDWoJnA@mail.gmail.com>
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: Simon Hobson <linux@thehobsons.co.uk>
Cc: 6man <ipv6@ietf.org>, draft-mishra-6man-variable-slaac@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a7ffd305b3aee735"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5jhS1AXora9Ix_HPULqizLuv5AU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Nov 2020 16:17:58 -0000

On Mon, Nov 9, 2020 at 2:07 AM Simon Hobson <linux@thehobsons.co.uk> wrote:

> Ca By <cb.list6@gmail.com> wrote:
>
> >> I think most of this comes down to can I save $18000 per year over a
> customer base of > 16 million.  Penny pinching at its extreme.
>
> > Yet another person missing the point and harkening back to the idea that
> anyone is trying to conserve  ipv6 addresses.
> >
> > Please stop.
>
> Have you heard of the expression "don't shoot the messenger" ?
> People are telling you what they observe. Right or wrong, there **ARE**
> ISPs out there where "bottom line" is the only thing they care about, and
> customer experience come last on the list of priorities.
>
> You'd think that an ISP selling (more or less) only DSL services which
> tend to be "always on" by their nature would achieve no saving by having
> dynamic address allocation vs static - but they still cling to the belief
> that a fixed IP is something that either costs them more, or at the very
> least is something they can screw the customer over.
>
> You keep telling people that this is "not a thing" without presenting any
> evidence whatsoever. We all know that the IPv6 address space is "very big",
> but the evidence is there that some ISPs are not treating it the way you
> claim they all will. You've already been given stats that show that a
> significant number of ISPs are choosing to only supply a /64 when it has
> always been recommended practice to offer a larger allocation. And you've
> also been given evidence that some ISPs would offer a much smaller (even a
> /127) allocation if they could get away with it.
>
> Simon
>

Then let’s leave it at that.

Anti-ipv6 conservation action is not a problem to solve in the ietf.

I am a mobile operator and i want the ietf’s help to provide < /64 prefixes
to my users. I want to give them more ipv6 space. Help me focus the
conversation on how to engineer better methods to deploy larger blocks of
space.



> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>