Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt

<mohamed.boucadair@orange.com> Wed, 13 August 2014 12:59 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB111A0055 for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 05:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level:
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
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 yMeR3kcos7Vb for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 05:59:54 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F831A0045 for <v6ops@ietf.org>; Wed, 13 Aug 2014 05:59:53 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 7498E3243C9; Wed, 13 Aug 2014 14:59:49 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 4F18D238059; Wed, 13 Aug 2014 14:59:49 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.234]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0195.001; Wed, 13 Aug 2014 14:59:49 +0200
From: mohamed.boucadair@orange.com
To: Ross Chandler <ross@eircom.net>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt
Thread-Index: AQHPturJ1Fq2arzbkkmtZl9xbOFURZvOfpEg
Date: Wed, 13 Aug 2014 12:59:49 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004E181@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140811132108.5976.52069.idtracker@ietfa.amsl.com> <693E53F1-4EA8-4CEF-91AE-D9F8E00DD05A@eircom.net> <787AE7BB302AE849A7480A190F8B933004DF89@OPEXCLILM23.corporate.adroot.infra.ftgroup> <E7F0E006-5196-435A-BA97-E906F0F8F3E4@eircom.net>
In-Reply-To: <E7F0E006-5196-435A-BA97-E906F0F8F3E4@eircom.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004E181OPEXCLILM23corpor_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.6.25.81224
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/c80tsHc8441i0iS_W6hqb8KSLqo
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 13 Aug 2014 12:59:57 -0000

Re-,

I updated my local copy with this NEW text:

   C_REC#12:  The cellular host must be able to be configured to limit
              PDP type(s) for a given APN.  The default mode is to allow
              all supported PDP types.  Note, C_REC#3 discusses the
              default behavior for requesting PDP-Context type(s).

                 This feature is useful to drive the behavior of the UE
                 to be aligned with: (1) service-specific constraints
                 such as the use of IPv6-only for VoLTE (Voice over
                 LTE), (2) network conditions with regards to the
                 support of specific PDP types (e.g., IPv4v6 PDP-Context
                 is not supported), (3) IPv4 sunset objectives, (4)
                 subscription data, etc.

Please let me know if this is OK or more text is needed.

Thank you.

Cheers,
Med

De : Ross Chandler [mailto:ross@eircom.net]
Envoyé : mercredi 13 août 2014 13:28
À : BOUCADAIR Mohamed IMT/OLN
Cc : IPv6 Ops WG
Objet : Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt


Hi Med,

I agree it would be more appropriate to have it as a generalised recommendation, with the text explaining the situation where it might be considered useful to have it.

The reason I worded it like that was modelled on C_REC#12 which has an opening sentence explaining why it is needed, rather than just stating the requirement and having the explanation in the text. I suggested that it be placed after C_REC#12 in recognition that it is a similar type of recommendation.

Generalised this C_REC might also be useful when it comes to sunseting requests for IPv4 from UEs in 3GPP networks.

BR
Ross



On 13 Aug 2014, at 11:53, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:


Hi Ross,

Thank you for the support.

As for your proposed REC, wouldn't be appropriate to generalize the recommendation? e.g.:

   C_REC#x:   The cellular host must be able to be configured to limit
              PDP type(s) for a given APN.  The default mode is to allow
              all supported PDP types.  Note, C_REC#3 discusses the
              default behavior for requesting PDP-Context type(s).

If needed, the text can call out why this is needed (v4v6 not supported, subscriber profile, service-specific constraints (e.g., VoLTE), etc.

BTW, C_REC#12 already hints that PDP types can be limited. I'm particularly referring to this sentence:

"Note, distinct PDP type(s) can
              be configured for home and roaming cases."

Cheers,
Med

De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Ross Chandler
Envoyé : mardi 12 août 2014 16:41
À : IPv6 Ops WG
Objet : Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt


On 11 Aug 2014, at 14:21, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Operations Working Group of the IETF.

       Title           : An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
       Authors         : David Binet
                         Mohamed Boucadair
                         Ales Vizdal
                         Cameron Byrne
                         Gang Chen
          Filename        : draft-ietf-v6ops-mobile-device-profile-08.txt
          Pages           : 18
          Date            : 2014-08-11


Hi All,

I support this useful draft.

An item I'd like to see added to the "Connectivity Recommendations" list after C_REC#12 is.

   C_REC#??:  Because of the potential for separate parallel IPv4 and
              IPv6 PDP/PDN connections when the network or subscriber
              profile does not support IPv4v6 PDP-Contexts, the cellular
                    host must be able to be configured to exclude this type
              from the available options.

For example if the list was just IPv4 or IPv6 (with 464XLAT implied) then the cellular host
would only ever attempt to set-up a single stack connection.

I note that with:
              Android the options are IPv4, IPv6 and IPv4/IPv6.
              Windows Phone 8.1 the options are IPv4, IPv6, IPv4v6 and IPv4v6XLAT


Best regards,
Ross