Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

"Heatley, Nick" <> Mon, 23 February 2015 16:03 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7C0071A1B85 for <>; Mon, 23 Feb 2015 08:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id h1aeZAClZgHN for <>; Mon, 23 Feb 2015 08:03:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 532D51A1B87 for <>; Mon, 23 Feb 2015 08:03:10 -0800 (PST)
Received: from [] by id AD/99-02804-C3F4BE45; Mon, 23 Feb 2015 16:03:08 +0000
X-Originating-IP: []
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29319 invoked from network); 23 Feb 2015 16:03:08 -0000
Received: from unknown (HELO ( by with DHE-RSA-AES256-SHA encrypted SMTP; 23 Feb 2015 16:03:08 -0000
Received: from EEUKWV0940.EEAD.EEINT.CO.UK (Not Verified[]) by with MailMarshal (v7, 2, 3, 6978) (using TLS: SSLv23) id <B54eb4f320002>; Mon, 23 Feb 2015 16:02:58 +0000
Received: from UK30S005EXS02.EEAD.EEINT.CO.UK (Not Verified[]) by EEUKWV0940.EEAD.EEINT.CO.UK with MailMarshal (v7, 2, 3, 6978) id <B54eb4f3c0000>; Mon, 23 Feb 2015 16:03:08 +0000
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK30S005EXS02.EEAD.EEINT.CO.UK ([2002:62c:2a4f::62c:2a4f]) with mapi id 14.03.0195.001; Mon, 23 Feb 2015 16:03:07 +0000
From: "Heatley, Nick" <>
To: Mikael Abrahamsson <>, Lorenzo Colitti <>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
Date: Mon, 23 Feb 2015 16:03:07 +0000
Message-ID: <6536E263028723489CCD5B6821D4B21303E0B009@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <> <787AE7BB302AE849A7480A190F8B933004912254@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <787AE7BB302AE849A7480A190F8B9330049122B6@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <787AE7BB302AE849A7480A190F8B9330049124F0@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: V6 Ops List <>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Feb 2015 16:03:16 -0000

-----Original Message-----
From: v6ops [] On Behalf Of Mikael Abrahamsson
Sent: 23 February 2015 15:04
To: Lorenzo Colitti
Cc: V6 Ops List
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

My opinion is the following:

We should recommend to run IPv4v6 whereever possible to operators, for the reasons you provide.
[Heatley, Nick] If we want to recommend, then I would suggest we should recommend that the operator's APN design promotes the use of a single PDP/PDN type per subscriber, for the reasons you provide.
The problem for me is that this is design in the operator network and losing focus on the mobile device profile.

We should recommend device manufacturers to follow the 3GPP standards and set up a second PDP context when it receives CC#52.
[Heatley, Nick] I would not be comfortable doing anything but working within the 3GPP standards.

The background is that parallel address version PDPs may exist per subscriber due to:
1.	Legacy handsets (pre-release8 devices on dualstack networks)
2.	OR Roaming situations, e.g. dualstack APN home networks on legacy visited networks
3.	OR Due to an individual operator's APN design.
So even with a recommendation then 2. could exist and result in CC#52.
IMHO the original text just acknowledges the existence of such an outcome.

This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. 

EE Limited
Registered in England and Wales
Company Registered Number: 02382161
Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW.