Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-device-profile-08.txt
Ross Chandler <ross@eircom.net> Wed, 13 August 2014 11:36 UTC
Return-Path: <ross@eircom.net>
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 315A21A86F7 for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 04:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668] 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 Rmb6aA2NSMsL for <v6ops@ietfa.amsl.com>; Wed, 13 Aug 2014 04:36:14 -0700 (PDT)
Received: from mail11.svc.cra.dublin.eircom.net (mail11.svc.cra.dublin.eircom.net [159.134.118.27]) by ietfa.amsl.com (Postfix) with SMTP id BFB641A085C for <v6ops@ietf.org>; Wed, 13 Aug 2014 04:36:13 -0700 (PDT)
Received: (qmail 26606 messnum 6679486 invoked from network[213.94.190.15/avas03.vendorsvc.cra.dublin.eircom.net]); 13 Aug 2014 11:36:12 -0000
Received: from avas03.vendorsvc.cra.dublin.eircom.net (213.94.190.15) by mail11.svc.cra.dublin.eircom.net (qp 26606) with SMTP; 13 Aug 2014 11:36:12 -0000
Received: from mac1.home.ross.net ([159.134.196.35]) by avas03.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id eBc71o0200mJ9Tz01BcByP; Wed, 13 Aug 2014 12:36:12 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_D1E2C098-E986-4968-AFC5-03D725E4450F"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004DF89@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Date: Wed, 13 Aug 2014 12:28:24 +0100
Message-Id: <E7F0E006-5196-435A-BA97-E906F0F8F3E4@eircom.net>
References: <20140811132108.5976.52069.idtracker@ietfa.amsl.com> <693E53F1-4EA8-4CEF-91AE-D9F8E00DD05A@eircom.net> <787AE7BB302AE849A7480A190F8B933004DF89@OPEXCLILM23.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YMWmGy7ZdBQbX7Aul6FwB6tca2w
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 11:36:17 -0000
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> <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 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
- [v6ops] I-D Action: draft-ietf-v6ops-mobile-devic… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… mohamed.boucadair
- Re: [v6ops] I-D Action: draft-ietf-v6ops-mobile-d… joel jaeggli