[v6ops] state of IPv4v6/IPv6 roaming in 3GPP networks
<nick.heatley@bt.com> Fri, 03 May 2019 16:24 UTC
Return-Path: <nick.heatley@bt.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039E51200EF for <v6ops@ietfa.amsl.com>; Fri, 3 May 2019 09:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 wLKruBw7i-0n for <v6ops@ietfa.amsl.com>; Fri, 3 May 2019 09:24:45 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 367AA1200E3 for <v6ops@ietf.org>; Fri, 3 May 2019 09:24:45 -0700 (PDT)
Received: from tpw09926dag05h.domain1.systemhost.net (10.9.202.32) by RDW083A011ED67.bt.com (10.187.98.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 3 May 2019 17:28:58 +0100
Received: from tpw09926dag13f.domain1.systemhost.net (10.9.212.21) by tpw09926dag05h.domain1.systemhost.net (10.9.202.32) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 3 May 2019 17:24:42 +0100
Received: from bwp09926084.bt.com (10.36.82.115) by tpw09926dag13f.domain1.systemhost.net (10.9.212.21) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 3 May 2019 17:24:41 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.55) by smtpe1.intersmtp.com (10.36.82.115) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1531.3; Fri, 3 May 2019 17:24:25 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ykB0y27eBDPg0uhT0JoO0tXyHe+8qYTxGR3f8ayLG/4=; b=Kz+gqMk8U3IW0N+GMJwEY45bA47K/pkJ/OjUS23VFx+sm3cAKa23i5AZ6NbeTFlpZjAnw0oWB5UAW4iuT0sfK61z5rfWLZi0Rk7GiLfoVuM1HhCiuMWdh8apfU4sifGAnDQfT4ljwelvcdoLiNqg3h58L2jTdJm2xfWLdNxTgKs=
Received: from CWXP123MB2423.GBRP123.PROD.OUTLOOK.COM (20.179.110.147) by CWXP123MB2568.GBRP123.PROD.OUTLOOK.COM (20.179.111.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.10; Fri, 3 May 2019 16:24:41 +0000
Received: from CWXP123MB2423.GBRP123.PROD.OUTLOOK.COM ([fe80::f0b1:1580:565d:a897]) by CWXP123MB2423.GBRP123.PROD.OUTLOOK.COM ([fe80::f0b1:1580:565d:a897%5]) with mapi id 15.20.1856.012; Fri, 3 May 2019 16:24:41 +0000
From: nick.heatley@bt.com
To: draft-ietf-v6ops-ipv6-roaming-analysis@ietf.org, v6ops@ietf.org
Thread-Topic: state of IPv4v6/IPv6 roaming in 3GPP networks
Thread-Index: AdUBzJC+nlehT8qnTkSqIANfVudR4w==
Date: Fri, 03 May 2019 16:24:41 +0000
Message-ID: <CWXP123MB2423E30FAF89BC30C1D64584EA350@CWXP123MB2423.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nick.heatley@bt.com;
x-originating-ip: [2a00:23c5:311:7100:a1e3:547e:1330:ad09]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7acb3516-00f2-4dbe-1163-08d6cfe3d84a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:CWXP123MB2568;
x-ms-traffictypediagnostic: CWXP123MB2568:
x-antispam-2: 1
x-microsoft-antispam-prvs: <CWXP123MB2568B568948A4717D27AEE57EA350@CWXP123MB2568.GBRP123.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0026334A56
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(136003)(346002)(396003)(366004)(189003)(199004)(186003)(102836004)(52536014)(6116002)(790700001)(46003)(316002)(5024004)(2906002)(450100002)(99286004)(54896002)(476003)(486006)(256004)(14444005)(6306002)(2501003)(6436002)(9686003)(8936002)(68736007)(53936002)(55016002)(7736002)(478600001)(66446008)(71200400001)(5660300002)(76116006)(8676002)(66946007)(73956011)(64756008)(81156014)(66476007)(81166006)(66556008)(71190400001)(25786009)(7696005)(4744005)(110136005)(6506007)(86362001)(14454004)(33656002)(74316002); DIR:OUT; SFP:1101; SCL:1; SRVR:CWXP123MB2568; H:CWXP123MB2423.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: dyS0kubSARhtjP9Lq+OYk2ICkvqdyGABZO2CS36om2be5Y5gq3nJrxqRzsLynsBPjZ15w1xFYnhjFs9L/azInGE5at+1pslFxMimXHS2UqcwagxEyYf352sNC//RLyTj+MeZpj93tYXPvW3LfIlYGdr+dsZ3PA/IR0RcX6wgDZ6q29aQLd2zr5FcHxKCIoao4flYVqjgR0oZeezHieHSp6iNVWaod2YEk5y3sUwXMLK0WZj1p8SInUnbVRRA/47PdgrMlyB4bWazE5cTck680QAEro42gAjjWlWPkrVYiUKrn9AfNDVe7OcXqW5RHKyMPMK9JZXTfNP6lZCCkRfxmSWToB+ujaS8FsJ47b3G5HkwFAkEgWQY4jKHCKY7ytN31qHdLvMTRogYPO9ur+Pri0VCmBgQJ98odCfvR9maOvg=
Content-Type: multipart/alternative; boundary="_000_CWXP123MB2423E30FAF89BC30C1D64584EA350CWXP123MB2423GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7acb3516-00f2-4dbe-1163-08d6cfe3d84a
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 May 2019 16:24:41.1951 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CWXP123MB2568
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gpdfepPBnPL7GnfXcvXMsblbnKA>
Subject: [v6ops] state of IPv4v6/IPv6 roaming in 3GPP networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2019 16:24:48 -0000
Hi there, its been a few years since IPv6 roaming analysis RFC7445 was released. I would appreciate if anyone can comment on if they have found the landscape has changed? I am most interested in problem of section 3: Failure Case in the Network Attachment. Is it still a concern to Operators? Thanks, Nick
- [v6ops] state of IPv4v6/IPv6 roaming in 3GPP netw… nick.heatley