Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt>(Internet Protocol Version 6 (IPv6) Profile for 3GPP MobileDevices) to Informational RFC

Hi Nick,

A new version of the draft will be edited at least taking into account comments received during this last call process. 
A requirement to guarantee that the device has some IP connectivity in roaming context, like the one you mention, is likely to be integrated in this upcoming version even if the discussions about roaming will continue and will go beyond device capabilities.  

David

> -----Message d'origine-----
> De : Heatley, Nick [mailto:Nick.Heatley@ee.co.uk] 
> Envoyé : mardi 20 août 2013 10:50
> À : v6ops@ietf.org; BINET David IMT/OLN; Byrne, Cameron; 
> phdgang@gmail.com; Vizdal Ales (TMCZ)
> Cc : denghui@chinamobile.com
> Objet : RE: [v6ops] Last Call: 
> <draft-ietf-v6ops-mobile-device-profile-04.txt>(Internet 
> Protocol Version 6 (IPv6) Profile for 3GPP MobileDevices) to 
> Informational RFC
> 
> Given we have been discussing 3GPP IPv6 Roaming, I was 
> thinking of any mobile terminal requirements that come from roaming.
> There seems to be no specifics regarding roaming in this paper.
> 
> One solution appears to be coming into favour to fix one type 
> of operational deficiencies in current roaming: that the 
> terminal can be configured with a home IP profile and a 
> roaming IP profile. This is not so much a compliance 
> requirement, as protecting the subscriber against exceptions 
> when roaming. Should this be included in this paper? Or would 
> this need further debate beyond the scope of this paper?
> What are your thoughts?
> Nick
> 
> 
> > -----Original Message-----
> > From: v6ops-bounces@ietf.org 
> [mailto:v6ops-bounces@ietf.org] On Behalf 
> > Of The IESG
> > Sent: 19 August 2013 14:52
> > To: IETF-Announce
> > Cc: v6ops@ietf.org
> > Subject: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-
> > 04.txt>(Internet Protocol Version 6 (IPv6) Profile for 3GPP
> > MobileDevices) to Informational RFC
> > 
> > 
> > The IESG has received a request from the IPv6 Operations WG 
> (v6ops) to 
> > consider the following document:
> > - 'Internet Protocol Version 6 (IPv6) Profile for 3GPP 
> Mobile Devices'
> >   <draft-ietf-v6ops-mobile-device-profile-04.txt> as 
> Informational RFC
> > 
> > The IESG plans to make a decision in the next few weeks, 
> and solicits 
> > final comments on this action. Please send substantive 
> comments to the 
> > ietf@ietf.org mailing lists by 2013-09-02. Exceptionally, 
> comments may 
> > be sent to iesg@ietf.org instead. In either case, please retain the 
> > beginning of the Subject line to allow automated sorting.
> > 
> > Abstract
> > 
> > 
> >    This document specifies an IPv6 profile for 3GPP mobile 
> devices.  It
> >    lists the set of features a 3GPP mobile device is to be compliant
> >    with to connect to an IPv6-only or dual-stack wireless network
> >    (including 3GPP cellular network and IEEE 802.11 network).
> > 
> >    This document defines a different profile than the one 
> for general
> >    connection to IPv6 cellular networks defined in
> >    [I-D.ietf-v6ops-rfc3316bis].  In particular, this document 
> > identifies
> >    also features to deliver IPv4 connectivity service over 
> an IPv6-only
> >    transport.
> > 
> >    Both hosts and devices with capability to share their 
> WAN (Wide Area
> >    Network) connectivity are in scope.
> > 
> > 
> > 
> > 
> > The file can be obtained via
> > 
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile
> > /
> > 
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-
> > profile/ballot/
> > 
> > 
> > No IPR declarations have been submitted directly on this I-D.
> > 
> > 
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.