RE: [EXTERNAL] Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 25 November 2020 16:34 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 0EFE03A19DF; Wed, 25 Nov 2020 08:34:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 j-l6MBSCd2_C; Wed, 25 Nov 2020 08:34:08 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 DFD8B3A19E4; Wed, 25 Nov 2020 08:34:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0APGY3ev003712; Wed, 25 Nov 2020 11:34:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1606322045; bh=aUBSNh3M1EmPOV7Qtg4U0cud3ys4+q3BET6hUPto8mc=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=cHT8NJjY1JDnl+FghnzXmR1AFeCCJrbnspYlVd6AkpNZ4OleQKJXr8pgNt67UeLw/ mZRhuhcsB52ZmTcBkEmc+zsPxIt+2WXVQgg6JtaUIt4SmbS+7DygEBId++0vxM0E05 LIyj8EfnVF2yVRs7ysq3QddJuFFI6HkCiskAxdNPi+dmgOHL7xaOWY6dHFUpqDfxAe oYRrHsyMfJ06plStn6rDPm2XG2G0InHgxhMc+9Ko9vHKzp3Y0KehlzAb2Z16GyzZHj VFp4VaEZ5nrPie6jvpGjFmPCSpngcui+V3zVMui9BdlzCwswXSr35lYz1cNf9bheh4 3lQrEfHjBAG7Q==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0APGY0TU003658 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 25 Nov 2020 11:34:00 -0500
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; Wed, 25 Nov 2020 08:33:59 -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; Wed, 25 Nov 2020 08:33:59 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
CC: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
Thread-Topic: [EXTERNAL] Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
Thread-Index: AQHWwWyB4Lub7t3bVESvC0PbrYUO2KnWTGYAgABVowCAAGBbAIAAN2WT///PBICAADYay///2c0AgABDFEP//9FPAAAJPo8QAAC5FAAAMUxg3AAA23Tw
Date: Wed, 25 Nov 2020 16:33:58 +0000
Message-ID: <ec0df57a694d473fa98148ba53f1ba1f@boeing.com>
References: <CABNhwV2-dH81CY4wSisV8BU-7H9m5a1xYMqTMecRxhNqZe=ApQ@mail.gmail.com> <CAKD1Yr1xV179LZ7Kxtk5mGruJcJ+BpGb2heBBy4ORtRU7bfvqw@mail.gmail.com> <CAMGpriWqnmL0qo0Hm=b+GbzcdCuXz6PM5aq8owE7-=ty5pDFsw@mail.gmail.com> <1DB65027-BEF2-4C0A-ACF4-C979DA7444C2@employees.org> <m1khXWs-00007wC@stereo.hq.phicoh.net> <47150D97-27D7-4AFD-8418-692D68D09828@employees.org> <m1khXol-0000MEC@stereo.hq.phicoh.net> <BD254B32-FAAE-4433-9CF5-2AF19275CA96@employees.org> <m1khZLr-0000IXC@stereo.hq.phicoh.net> <51F56897-AEE2-43E6-8FCC-BD9412B53675@employees.org> <ad4aa2ca83e743fb8d23026a7ad0649b@huawei.com> <1b284a58699e4fa39b1602b8f3fede28@boeing.com> <m1khbrX-0000J8C@stereo.hq.phicoh.net> <CAKD1Yr2AKRqKWDUhZHYhT+1gOsrCG+JFoFZ=j=W0G7e1i51pRQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr2AKRqKWDUhZHYhT+1gOsrCG+JFoFZ=j=W0G7e1i51pRQ@mail.gmail.com>
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: D4E6C3EBD210C0E3B9FC914DDEC76AA2FF2939855FEA7D987A1CE7A49B2B00882000:8
Content-Type: multipart/alternative; boundary="_000_ec0df57a694d473fa98148ba53f1ba1fboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FPaQfsf7OOjNIR6diU1ON0RkYB8>
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: Wed, 25 Nov 2020 16:34:12 -0000


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Lorenzo Colitti
Sent: Wednesday, November 25, 2020 8:06 AM
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?

On Wed, Nov 25, 2020 at 2:13 AM Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com<mailto:pch-ipv6-ietf-6@u-1.phicoh.com>> wrote:
>https://datatracker.ietf.org/doc/draft-templin-6man-lla-type/

In my opinion it is a quite broken design to put protocol bits in IPv6
addresses when ND already has an option syntax for these types of extensions.

+1, this does seem pretty hacky.
[>]

It is not hacky if it becomes part of the addressing architecture. And, it has
full backwards compatibility in the case that the bits 48-63 are simply 0.