IETF Logo Mail Archive

RE: [EXTERNAL] Re: DHCPv6-PD is fine

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 09 November 2020 17:30 UTC

Return-Path: <Fred.L.Templin@boeing.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 2EC6F3A126E for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=boeing.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 nMWeiK6_bcMd for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:30:16 -0800 (PST)
Received: from ewa-mbsout-02.mbs.boeing.net (ewa-mbsout-02.mbs.boeing.net [130.76.20.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C143A1276 for <ipv6@ietf.org>; Mon, 9 Nov 2020 09:30:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0A9HUDBU001137; Mon, 9 Nov 2020 09:30:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1604943014; bh=W0HYQSd21zHQ4KRtUJfIdA+JIzJVXcNs/CojEP3x4eE=; h=From:To:Subject:Date:References:In-Reply-To:From; b=MnTTncHEVpWj+QAuksAqHCzfc8SZ+RHWJa+WsEiVYLybVQKdhvqOPccU6qSjrx0WJ fXB22rkZiwLxKA9n8+x6kD2mrLHb82A0r8p3nBHzzoDA+GXwpKczrGRgECE71D/+51 BS5u0Y3Goqs63d6i2CNNGqVwW4HeX9Y8WsRgsj+g9gUfEnWN2QrsqnGyTeepB2tCvL LeM2EXI3HbWd1taTyBZWRaCnRRx2gxg2dU82TIOrMfQJvRm4Zod6IHTrw4JOujdrWo 3tM8R566RDa9TXVPvkx2l6BA2p36pBlbAUG0Gkl0QW5z4icoVRanTHL6Vueq0BduVb I87aYDw4G9+sA==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by ewa-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0A9HTwUZ065480 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 9 Nov 2020 09:30:00 -0800
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 9 Nov 2020 09:29:57 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Mon, 9 Nov 2020 09:29:57 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Simon Hobson <linux@thehobsons.co.uk>, 6man <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: DHCPv6-PD is fine
Thread-Topic: [EXTERNAL] Re: DHCPv6-PD is fine
Thread-Index: Ada2tKxSlCA25DTCRH2QjN3TcGyuSwAB1Nb7AABI9VA=
Date: Mon, 09 Nov 2020 17:29:57 +0000
Message-ID: <6d0f351df5f04cf598d055c624e9f17c@boeing.com>
References: <1258a91f37274343a5d6b8f5ebf14708@boeing.com> <350919b2-fe50-a3b8-3f15-4ce32124d495@gmail.com> <3377F3AE-BDFE-4AAC-ACA3-0F3D1A4D8854@thehobsons.co.uk>
In-Reply-To: <3377F3AE-BDFE-4AAC-ACA3-0F3D1A4D8854@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 9830F2B0F96983508AD61AF0414D7A43AABF2F2FFE31A9A1DC346B9BFE0FEBC92000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/buN8DzUtzR-Do3djPa5SyrteWxg>
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 17:30:18 -0000

Simon, if it would interest you please have a look at the DHCPv6-PD method
outlined in the OMNI draft. It is more accurately called "proxy-DHCPv6" in that
the mobile (aka Client) does not issue traditional DHCPv6 Solicit, etc. but rather
only issues RS. The access router that receives the RS then acts as a "proxy" to
speak to the DHCPv6 server on the Client's behalf, then returns prefix info in
a responsive RA message.

Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Simon Hobson
> Sent: Monday, November 09, 2020 9:15 AM
> To: 6man <ipv6@ietf.org>
> Subject: Re: DHCPv6-PD is fine
> 
> Alexandre Petrescu <alexandre.petrescu@gmail.com> 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
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email