IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Wed, 13 August 2014 10:53 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 0C4721A0823 for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 03:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 I_auvkXGvPEw for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 03:53:14 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB08E1A081D for <v6ops@ietf.org>; Wed, 13 Aug 2014 03:53:13 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id A2C96C0570; Wed, 13 Aug 2014 12:53:11 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 7810D15804E; Wed, 13 Aug 2014 12:53:11 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.234]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0195.001; Wed, 13 Aug 2014 12:53:11 +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: AQHPtjuTP8ex53zggkS1+QR7dAVhwpvOGpog
Date: Wed, 13 Aug 2014 10:53:10 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004DF89@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20140811132108.5976.52069.idtracker@ietfa.amsl.com> <693E53F1-4EA8-4CEF-91AE-D9F8E00DD05A@eircom.net>
In-Reply-To: <693E53F1-4EA8-4CEF-91AE-D9F8E00DD05A@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_787AE7BB302AE849A7480A190F8B933004DF89OPEXCLILM23corpor_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.8.13.90919
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/5vxw8GFRfPc8vLmwvU_xNfxHKYo
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 10:53:17 -0000

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

v2.23.0 | Report a Bug | By Email