How do you solve 3GPP issue if neither operator nor handset supports PD?

Gyan Mishra <> Mon, 23 November 2020 07:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D69DB3A1493; Sun, 22 Nov 2020 23:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.841
X-Spam-Status: No, score=0.841 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_20=0.7, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.328, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XSMORkceqLUO; Sun, 22 Nov 2020 23:44:06 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::62d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4D4403A168D; Sun, 22 Nov 2020 23:44:06 -0800 (PST)
Received: by with SMTP id v21so7176269plo.12; Sun, 22 Nov 2020 23:44:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=YHEhHJ5750XlPAl/6ZDvKDzuJzaCDlmfwwLRj+g4Yuo=; b=IJ28//oFjRc6AzGzpqYfCEo0FR16Xiw/szJ9uKyWiA3jsY8uYJD6ePOZqntiCFMjcM IvK0OHD1mDJgSCcEyudW25xv/eq6M7bbCMnkG9NPCYziV+iuB5Nr5/JX+wza/dX5Q/vR SJOYXfysrwSUnGsJMpCc1xr60mRcKInLZv8vwAglAyEpxUm/gtyamQMrGMTR3O0lBtJ4 bn55JMyoLqX2RMNBgAqCqi1pBr32YJPNN4w1+gsfZCqDBvh0Y4hwyDnRtiOzfKZszEkd 4WGWtvJddQomUhY7quXqCFQfUMXDnvm/f8BzzzKWIPIX+eQ0DU/K8HCR3o4Ytr8bQ26U 8YRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=YHEhHJ5750XlPAl/6ZDvKDzuJzaCDlmfwwLRj+g4Yuo=; b=R1vaIMOBz/afn5xclISd2Y+p3Ic2kbosQsW+v09iBPecvgjD8UN7i4vWeUdp73dBG5 u/JWGiNNnm5m+TMiPl+L1vknzrPFcpplnAe2qK690cvo868GjI4cVaA6eiRm1XH4SqPg gjTkKg5msVrV/4u1U6sP68ZUom3/hmBJlRL1FEih/AJwNYFZAHNrFM3CSEU1FtHNGfjj 1ofqRhEfsl0UGw61vVOHJIM71hOTgC7je/N0oi0PzVd8tGzziczoPF6ninLT8EOFHTnn 4Bkcqj2bQukvUuSADCD13F8x1/lNrGIX84/vJ2SKho529MTB43L349socTgnPR/ycyNz U2cw==
X-Gm-Message-State: AOAM533XvppDxVjidHefRM3dJnb4zGBhH8/jr7LRak4uDfmPss3MqZYE U2WQumpi7i0Q0KwlDta6HTmhU0bwh7C+5ROsu+evCxhU+7E=
X-Google-Smtp-Source: ABdhPJw2mcQ0VPBfn6zkHaELCoQI+ccWdS4NpkMsKDqps99tSg0dKQL6MZ5aPzL4wvBm/VN1bEX/uprOvcdCfX2B/cY=
X-Received: by 2002:a17:902:6905:b029:d9:9114:280d with SMTP id j5-20020a1709026905b02900d99114280dmr15492146plk.74.1606117445427; Sun, 22 Nov 2020 23:44:05 -0800 (PST)
MIME-Version: 1.0
From: Gyan Mishra <>
Date: Mon, 23 Nov 2020 02:43:54 -0500
Message-ID: <>
Subject: How do you solve 3GPP issue if neither operator nor handset supports PD?
To: 6MAN <>, Alexandre Petrescu <>, IPv6 Operations <>, "" <>
Content-Type: multipart/alternative; boundary="000000000000cd64c105b4c15bf4"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Nov 2020 07:44:08 -0000

How do we propose to solve this problem if operators don’t support PD even
though the  3GPP standard has supported PD for over 10 years.

Another twist to this puzzle is Android has 90% of the mobile handset
marketplace worldwide and adamantly states they will NOT support DHCPv6 or

I researched Apple which has 10% of the market and they also do not support

Whats the solution now?


*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD