Re: DHCPv6-PD is fine

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 09 November 2020 21:45 UTC

Return-Path: <brian.e.carpenter@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 435683A145F for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 13:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 8-hVLeL8Aghr for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 13:45:16 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 53F183A14D2 for <ipv6@ietf.org>; Mon, 9 Nov 2020 13:44:47 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id c20so9418869pfr.8 for <ipv6@ietf.org>; Mon, 09 Nov 2020 13:44:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Mu5Bf+ZUGEHVsa+Z1zU7yYnV7MRDs2jOwvsm4M62KXE=; b=d/afKQloF+rtsYOGOB7Yop3BnB9DOt8oyWpU06H8SD7E1B6h3YGrnjJtAtgz+eLXVF I0ONAOJ7w7lRWFTs69l2Mgo2xbJ+8xPfmbZBM1CL0tTyzLD+NwQSu9GFQfCeIkYDHJZw Xw47M3QIbetvfX8aY4g6o/mGp2B/v9KQx5xNcSLJk+VCPIUlfYhKdUkT7RmdaTJ5+gbv Vyhw6RWb0yJL+s3eTofriKdlAYwMtNt508tJOjlitC4yMkzC+2hu35j89FuZcvYTF+6l LFhNjiS07Q5e65VDtAFT1zHDN/6TtR62If0c50lQzB8jk3vUI+wOlUTRvtZW1yw6a1UG 4g2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Mu5Bf+ZUGEHVsa+Z1zU7yYnV7MRDs2jOwvsm4M62KXE=; b=tr64HtfQ1LZQUiXfSbqvGSkbFgk1g82ezvl/BCdu88PryVxX2CGOo266okleB3Ny0g qMhnL6wtsx2HnYbfy11yudNy6saMmFjp5NYdo+ccRxESXJKyonU1fYeQomzCfK5eBsjx RBh2kD370mTdrhuS0MTY1c6vHPdHiFVDGx/9BnupZxi+EP+qmJ74mzBLxtVsRAYherQd 85x2l6T593sS+IPEC4nEUeW41EnY4zBphQCnIUyHCWf1rdAybdwdH0GRoj2qacZ/9KAu UTgDZ2TAG7ffHzD5M3F1eWn4Nbeh9mzUyOCXcRaszJMD0qWhJIbNIRkNlrLinhtvoqwK 66FA==
X-Gm-Message-State: AOAM530+VeeONQz5JpO75fh13b7Vw3h2HkwlVMvb0Trhk3CmBvcZS7Eu sCvI78JgBj1uWCB5Jct9ygXveWBvy6cwCQ==
X-Google-Smtp-Source: ABdhPJy1kPsVht4Dw9pkrzLQLXKdCNTcbJ1+axE+NcvXal5sfdq08dPrZmWwbm49DQbOoqKqbxP8wA==
X-Received: by 2002:a17:90a:c0f:: with SMTP id 15mr1284616pjs.148.1604958286287; Mon, 09 Nov 2020 13:44:46 -0800 (PST)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id 30sm11654797pgl.45.2020.11.09.13.44.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Nov 2020 13:44:45 -0800 (PST)
Subject: Re: DHCPv6-PD is fine
To: "STARK, BARBARA H" <bs7652@att.com>, 'Simon Hobson' <linux@thehobsons.co.uk>, '6man' <ipv6@ietf.org>
References: <1258a91f37274343a5d6b8f5ebf14708@boeing.com> <350919b2-fe50-a3b8-3f15-4ce32124d495@gmail.com> <3377F3AE-BDFE-4AAC-ACA3-0F3D1A4D8854@thehobsons.co.uk> <SN6PR02MB4512DE7BF31D8758BE15D899C3EA0@SN6PR02MB4512.namprd02.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e2a30777-8800-c2f9-292b-9587d3028561@gmail.com>
Date: Tue, 10 Nov 2020 10:44:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <SN6PR02MB4512DE7BF31D8758BE15D899C3EA0@SN6PR02MB4512.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0ePYEt3Bjk52M1hTgHoDNowWEY8>
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 21:45:17 -0000

Barbara,

On 10-Nov-20 06:38, STARK, BARBARA H wrote:
>>> But in other places, automobiles for example, one must use the existing
>> cellular networks.  DHCPv6-PD is not fine there.  It's not FUD.
>>
>> Just to clarify ...
>> From what I've been reading in this thread, in the mobile world the problem
>> isn't DHCPv6-PD, but the cellular world having not adopted it, or even
>> blocked it (ref discussion of mobile modems blocking DHCP packets).
>>
>> For clarity, is there a problem with DHCPv6-PD, or is there a problem with the
>> mobile world not supporting it for whatever reason ?
>>
>> The reason I ask is that if it's the latter, then the response to "it doesn't work,
>> we need to change something" is that you need to go to the mobile industry
>> and tell them to fix their ****.
>>
>> My 2d worth, Simon
> 
> Please don't take this personally, but, IMO, this is exactly the attitude that has
> brought us to this point. The IETF participants think IETF is in a position to dictate 
> and think they know better how to operate and deploy a network than the
> operators. Availability of equipment that implements features, complexity
> of legacy OSS/BSS systems, and complexity of deploying multiple methods
> of configuration (to make everyone happy) are 100% irrelevant and operators
> should simply spend whatever amount is needed to do exactly what IETF dictates.
> 
> I've suggested engaging and collaborating with other SDOs where operators
> prefer to do their work. But that suggestion clearly has no support here.

The problem there is what it's always been: the underlying motivations of
SDOs with paid-up membership models are different from the IETF's. The IETF
literally doesn't care about the profit margins of operators; it's perhaps
unintentionally slightly oriented towards the profit margins of vendors.
But "make the Internet work better" and "The Internet is for End Users"
are not in the least oriented towards operators' profit margins.

That really does make for a tussle rather than collaboration. It would be
great to achieve collaboration but I'm not sure how it can be done.

If we can show convincingly that /48 to the end user is good for
the operators' profit margins, that would help.

   Brian