Re: [v6ops] Implementation Status of PREF64

Mark Smith <markzzzsmith@gmail.com> Wed, 13 October 2021 21:16 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 8DD373A0C4E for <v6ops@ietfa.amsl.com>; Wed, 13 Oct 2021 14:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.597
X-Spam-Level:
X-Spam-Status: No, score=-0.597 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_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0k_T88z9GcFZ for <v6ops@ietfa.amsl.com>; Wed, 13 Oct 2021 14:16:39 -0700 (PDT)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 95E903A0C67 for <v6ops@ietf.org>; Wed, 13 Oct 2021 14:16:39 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id f15so1206677ilu.7 for <v6ops@ietf.org>; Wed, 13 Oct 2021 14:16:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q8uVXoLzXp0Wdx33q0FgtwFUHxQfYiaU+ivRW1Ub/EY=; b=Yod3OyLqwvN8FvrFCs1FvniJSi1sVWZjVRwzJPSfgUnbZmgGNvxjbZAxjybELDyEH7 8efZTfWGwIrUFUvxkU32ZNYI8uZOti0CoQ9NtPxX8/ZOQenSeL54Z/OIakzme/tz3goV L4P3nJpZ8S98XGpZHUquW6Y7kokPn+07CRSFaWvPnqwSxzBpO91QrVjqUrBxCkArGnbc G54IS3YLUYbvIJJASSl+UqgzkyNo0MQTUXAQUFxD8tOoZIphnAj2sGavxVFkicyuuYkd e65fIIVw3caOrGm0llorQMsftACqSyz61FH+xyL/BCKRyDNgmkKRZgDznJ0VB031kV6T EyLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q8uVXoLzXp0Wdx33q0FgtwFUHxQfYiaU+ivRW1Ub/EY=; b=vw7PF0Tp4jt5rN+Opi/6CKKc+ZcF4u7oDjOec3oaEjGPW6SpZchL8ZWZ9fMSrTtUdI Ri1Ut8C1aTj6pdVLlwlnTAiVrbLoY0pNdxzAI6ArCmn9UI2U2VBOv3ASSQuK2P/UCLi9 F1CGLIr0ta0tSQ7LrGJs+GxotmVDToBfIV3M+RJIp/5LLfrBnqOknn93FHY58kp2QpMj Obkwi4xzm6Knagr4TjQfcgo8UK+qlT4ZktEmf4wF5NP0NF8uz0gqGTQ4JcPr/qwKz3IY NASRaHJ6gqEeBv3gChkbuGAMLhAdGwAsPJqTAXBOTyS3l2Va8b+s5aQCuwl8Elf6aOBB SmTg==
X-Gm-Message-State: AOAM532ytiT452GBIIQaqyxUPHWC6Ar/fLH4NmjkbyqWhWw+J11CyXUo 9qQyukbggWQ/YObkfhpZQkZ9778gaymKpCuUwEOWGAXg
X-Google-Smtp-Source: ABdhPJxn2eThCdBIJpwIj6w40M/jAc8yNbEv8hrtWpCz/oMXD0Ufu5JzUBS7069Tr3FLX8VbNQIzO/9pprNGpxcgU98=
X-Received: by 2002:a05:6e02:198d:: with SMTP id g13mr1065037ilf.300.1634159798030; Wed, 13 Oct 2021 14:16:38 -0700 (PDT)
MIME-Version: 1.0
References: <EFC78F4B-873B-42EE-8DC5-04C29758B0D0@consulintel.es> <YVNhdioAbeO9p2/G@Space.Net> <CAKD1Yr2+Y59v81mPBn4Y3u0LRX7TzahbnaF1hVUZ+NSf0Jj_4g@mail.gmail.com> <20210930.082006.177771395.sthaug@nethelp.no> <d0c441c6-68fa-52ef-7c60-e8f0cff80ba0@gmail.com> <64E83A09-C4DC-428C-88D1-79FAD6AAB72E@delong.com> <d1e5aa61-c61b-6e5f-9c6f-50f88d7a28a2@gmail.com> <F4F2E2BA-C07C-457C-A244-8A3220B32226@delong.com> <C34C198D-51F5-4189-8913-305733B6AA90@thehobsons.co.uk>
In-Reply-To: <C34C198D-51F5-4189-8913-305733B6AA90@thehobsons.co.uk>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 14 Oct 2021 08:16:26 +1100
Message-ID: <CAO42Z2wAKoyC0pssr9To+cAHavCMEZGh9FHb+yG7x8rWw5cU5g@mail.gmail.com>
To: Simon <linux@thehobsons.co.uk>
Cc: v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000044939105ce427a4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vqoyuxXv4FdZRQG4p0bFsotJcCo>
Subject: Re: [v6ops] Implementation Status of PREF64
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Oct 2021 21:16:44 -0000

On Thu, 14 Oct 2021, 07:04 Simon, <linux@thehobsons.co.uk> wrote:

> Owen DeLong <owen=40delong.com@dmarc.ietf.org> wrote:
>
> >> An enterprise network might deploy its own DHCPv6 .apk's into
> employee's Android smartphones, for that particular enterprise network.
> >
> > Most enterprises expect this feature to be built into the OS.
>
> Indeed, the days of having to install pieces of software to get BASIC
> network functions is so ... last century. Brings back not so fond memories
> of having to pick an IP implementation (actually, pick a protocol and
> implementation), and then juggle with your load order to maximise hi-mem in
> DOS, and all that stuff.
>
> How long is it now since anything without IPv4 built in would be
> considered “broken” - and yet we’re still considering (or at least, some
> people are suggesting) that IPv6 should be held back to how networking was
> several decades ago !
>
> Not to put too fine a point on it, but I have seen no argument against
> Android including standards compliance


DHCPv6 is not required. See BCP 220.




 and a working DHCPv6 client other than : “it’s not how we want people to
> be using the devices they have bought AND SUPPOSEDLY OWN and we’re big
> enough to force our rules on the world”.
>
> Sorry Lorenzo, but basically the arguments put forward against allowing
> DHCPv6 client on Android come down to “but we want people to use them THIS
> way regardless of how they actually want to use it”. Dressed up a bit in
> the name of “protecting users” which is rich given that Google’s primary
> business is in amassing and profitting from people’s personal information -
> so perhaps it’s a more a case of “can’t have others abusing users’ privacy
> - that’s our job”.
>
> Just saying how it looks.
>
> Simon
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>