| draft-ietf-v6ops-mobile-device-profile-12.txt | draft-ietf-v6ops-mobile-device-profile-13.txt | |||
|---|---|---|---|---|
| V6OPS Working Group D. Binet | V6OPS Working Group D. Binet | |||
| Internet-Draft M. Boucadair | Internet-Draft M. Boucadair | |||
| Intended status: Informational France Telecom | Intended status: Informational France Telecom | |||
| Expires: March 21, 2015 A. Vizdal | Expires: March 30, 2015 A. Vizdal | |||
| Deutsche Telekom AG | Deutsche Telekom AG | |||
| G. Chen | G. Chen | |||
| China Mobile | China Mobile | |||
| N. Heatley | N. Heatley | |||
| EE | EE | |||
| R. Chandler | R. Chandler | |||
| eircom | meteor | eircom | meteor | |||
| September 17, 2014 | September 26, 2014 | |||
| An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices | An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices | |||
| draft-ietf-v6ops-mobile-device-profile-12 | draft-ietf-v6ops-mobile-device-profile-13 | |||
| Abstract | Abstract | |||
| This document defines an IPv6 profile that a number of operators | This document defines an IPv6 profile that a number of operators | |||
| recommend in order to connect 3GPP mobile devices to an IPv6-only or | recommend in order to connect 3GPP mobile devices to an IPv6-only or | |||
| dual-stack wireless network (including 3GPP cellular network and IEEE | dual-stack wireless network (including 3GPP cellular network and IEEE | |||
| 802.11 network). | 802.11 network). | |||
| This document defines a different profile than the one for general | This document defines a different profile than the one for general | |||
| connection to IPv6 cellular networks defined in the IPv6 for Third | connection to IPv6 cellular networks defined in the IPv6 for Third | |||
| skipping to change at page 2, line 4 | skipping to change at page 2, line 4 | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on March 21, 2015. | This Internet-Draft will expire on March 30, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 8, line 14 | skipping to change at page 8, line 14 | |||
| LTE), (2) network conditions with regards to the | LTE), (2) network conditions with regards to the | |||
| support of specific PDP types (e.g., IPv4v6 PDP-Context | support of specific PDP types (e.g., IPv4v6 PDP-Context | |||
| is not supported), (3) IPv4 sunset objectives, (4) | is not supported), (3) IPv4 sunset objectives, (4) | |||
| subscription data, etc. | subscription data, etc. | |||
| C_REC#13: Because of potential operational deficiencies to be | C_REC#13: Because of potential operational deficiencies to be | |||
| experienced in some roaming situations, the cellular host | experienced in some roaming situations, the cellular host | |||
| must be able to be configured with a home IP profile and a | must be able to be configured with a home IP profile and a | |||
| roaming IP profile. The aim of the roaming profile is to | roaming IP profile. The aim of the roaming profile is to | |||
| limit the PDP type(s) requested by the cellular host when | limit the PDP type(s) requested by the cellular host when | |||
| out of the home network. Note, distinct PDP type(s) can | out of the home network. Note that distinct PDP type(s) | |||
| be configured for home and roaming cases. | and APN(s) can be configured for home and roaming cases. | |||
| C_REC#14: In order to ensure IPv4 service continuity in an IPv6-only | C_REC#14: In order to ensure IPv4 service continuity in an IPv6-only | |||
| deployment context, the cellular host should support a | deployment context, the cellular host should support a | |||
| method to locally construct IPv4-embedded IPv6 addresses | method to locally construct IPv4-embedded IPv6 addresses | |||
| [RFC6052]. A method to learn PREFIX64 should be supported | [RFC6052]. A method to learn PREFIX64 should be supported | |||
| by the cellular host. | by the cellular host. | |||
| This solves the issue when applications use IPv4 | This solves the issue when applications use IPv4 | |||
| referrals on IPv6-only access networks. | referrals on IPv6-only access networks. | |||
| skipping to change at page 15, line 13 | skipping to change at page 15, line 13 | |||
| Address privacy considerations are discussed in [RFC4941] [RFC7217]. | Address privacy considerations are discussed in [RFC4941] [RFC7217]. | |||
| 7. IANA Considerations | 7. IANA Considerations | |||
| This document does not require any action from IANA. | This document does not require any action from IANA. | |||
| 8. Acknowledgements | 8. Acknowledgements | |||
| Many thanks to C. Byrne, H. Soliman, H. Singh, L. Colliti, T. | Many thanks to C. Byrne, H. Soliman, H. Singh, L. Colliti, T. | |||
| Lemon, B. Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. | Lemon, B. Sarikaya, M. Mawatari, M. Abrahamsson, P. Vickers, V. | |||
| Kuarsingh, E. Kline, S. Josefsson, A. Baryun, and J. Woodyatt for | Kuarsingh, E. Kline, S. Josefsson, A. Baryun, J. Woodyatt, and T. | |||
| the discussion in the v6ops mailing list. | Kossut for the discussion in the v6ops mailing list. | |||
| Special thanks to T. Savolainen, J. Korhonen, and J. Jaeggli for | Special thanks to T. Savolainen, J. Korhonen, and J. Jaeggli for | |||
| their detailed reviews and comments. | their detailed reviews and comments. | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [IR92] GSMA, "IR.92.V4.0 - IMS Profile for Voice and SMS", March | [IR92] GSMA, "IR.92.V4.0 - IMS Profile for Voice and SMS", March | |||
| 2011, <http://www.gsma.com/newsroom/ | 2011, <http://www.gsma.com/newsroom/ | |||
| End of changes. 6 change blocks. | ||||
| 8 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||