Re: [dhcwg] [v6ops] DHCPv6 Prefix Delegation (DHCPv6 PD) on cellular links - works ok

"Bernie Volz (volz)" <volz@cisco.com> Thu, 30 November 2017 16:43 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DEF1200FC; Thu, 30 Nov 2017 08:43:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 wDvSN1pO4bgx; Thu, 30 Nov 2017 08:43:01 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6778127876; Thu, 30 Nov 2017 08:43:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5729; q=dns/txt; s=iport; t=1512060180; x=1513269780; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=16wtuIoMF7/QQLYa8IocJVofK5fkSEzYjBSxHgDg+j4=; b=HmInbHeWL+/ocZs3M1MfgdNI+SLpvPQr4iV94Gln41sKnOapMk+KwwGn +ZqdTs8cSeORfMq3VBh3g2W5QazHDkAUbCPM1PSeecIdNc/mlYxhRlPTP laRRxJOGIHvXtNsqaItPJhPL0Gxyt5grJSFZmAfYwIA4LIgjZiDrEnRgz Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A6AgAdNCBa/5FdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM8Zm4ng3+ZEopoiECFS4IRChgBCoUYAhqFB0AXAQEBAQEBAQE?= =?us-ascii?q?BayiFIAIEAQEhSwsQAgEIBDsDAgICHwYLFBECBA4FiT5MAxUQpheCJ4c0DYMkA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDQYIJg2iDAoJrhUoxgjIFoh49ApAVhHq?= =?us-ascii?q?TU403iGECERkBgTkBIQE2M4EebxU6KgGBfoJSBReBZ3iKAwEBAQ?=
X-IronPort-AV: E=Sophos; i="5.45,341,1508803200"; d="scan'208,217"; a="38643033"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2017 16:43:00 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id vAUGgxI0012832 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 30 Nov 2017 16:42:59 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 30 Nov 2017 10:42:59 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Thu, 30 Nov 2017 10:42:59 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [v6ops] DHCPv6 Prefix Delegation (DHCPv6 PD) on cellular links - works ok
Thread-Index: AQHTafbnOF1NwEy2cE6/8AeiHgsEYaMtIKEz
Date: Thu, 30 Nov 2017 16:42:59 +0000
Message-ID: <87D21F39-7C1D-4F08-A3EE-39882C8832E6@cisco.com>
References: <7537deef-8f87-5187-1e44-595ac63a16ca@gmail.com>, <6077c7a4-01c8-8b80-588f-0ef4af153487@gmail.com>
In-Reply-To: <6077c7a4-01c8-8b80-588f-0ef4af153487@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_87D21F397C1D4F08A3EE39882C8832E6ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/LMAK8c5JviplKTB-EWV_bMGDiAE>
Subject: Re: [dhcwg] [v6ops] DHCPv6 Prefix Delegation (DHCPv6 PD) on cellular links - works ok
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Nov 2017 16:43:02 -0000

Good new!!

- Bernie (from iPhone)

On Nov 30, 2017, at 11:18 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>> wrote:

v6opsers,

We succeeded in making DHCPv6 PD work natively on a cellular link.
I would claim it to be a first[*].
Packet dump available upon request.

The UE device is a Huawei E392u-12 USB dongle produced in 2011.  It hosts a baseband processor Qualcomm model MDM9600 (or model MDM9200, or an Intel - not sure).  It lets all standard DHCPv6 messaging through. The DHCPv6 client 'odhcpv6' is running on linux laptop.

The mobile operator's PGW assigns a /56 and sets proper forwarding for it.  The PGW runs on a big Cisco platform.

After the successful DHCP exchange the laptop is able to ping google with a src address which is manually derived out of the /56 delegated prefix.

That said,

DHCPv6-PD on cellular links is relevant for a few RFCs and Internet Drafts.  They should be improved because at places these documents are a little bit wrong.

DHCPv6-PD is blocked on other baseband processors, including Qualcomm and Balong versions; they are hosted by many smartphones, USB cellular dongles, mobile personal WiFi hotspots and IoT devices.  A sample list is available upon request.

Last but not least,

[*] earlier DHCPv6 PD on cellular links was shown on tunnel virtual interfaces, like VPN.

Alex

_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops