draft-ietf-sunset4-gapanalysis-03.txt   draft-ietf-sunset4-gapanalysis-04.txt 
Network Working Group JP. Dionne Network Working Group S. Perreault
Internet-Draft S. Perreault Internet-Draft Viagenie
Intended status: Informational Viagenie Intended status: Informational T. Tsou
Expires: January 16, 2014 T. Tsou Expires: July 20, 2014 Huawei Technologies (USA)
Huawei Technologies (USA)
C. Zhou C. Zhou
Huawei Technologies Huawei Technologies
July 15, 2013 January 16, 2014
Gap Analysis for IPv4 Sunset Gap Analysis for IPv4 Sunset
draft-ietf-sunset4-gapanalysis-03 draft-ietf-sunset4-gapanalysis-04
Abstract Abstract
Sunsetting IPv4 refers to the process of turning off IPv4 Sunsetting IPv4 refers to the process of turning off IPv4
definitively. It can be seen as the final phase of the migration to definitively. It can be seen as the final phase of the migration to
IPv6. This memo enumerates difficulties arising when sunsetting IPv6. This memo enumerates difficulties arising when sunsetting
IPv4, and identifies the gaps requiring additional work. IPv4, and identifies the gaps requiring additional work.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 36
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 January 16, 2014. This Internet-Draft will expire on July 20, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 18 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Related Work . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Related Work . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Remotely Disabling IPv4 . . . . . . . . . . . . . . . . . . . 3 3. Remotely Disabling IPv4 . . . . . . . . . . . . . . . . . . . 3
3.1. Indicating that IPv4 connectivity is unavailable . . . . 3 3.1. Indicating that IPv4 connectivity is unavailable . . . . 3
3.2. Disabling IPv4 in the LAN . . . . . . . . . . . . . . . . 3 3.2. Disabling IPv4 in the LAN . . . . . . . . . . . . . . . . 3
4. Client Connection Establishment Behavior . . . . . . . . . . 3 4. Client Connection Establishment Behavior . . . . . . . . . . 3
5. Disabling IPv4 in Operating System and Applications . . . . . 4 5. Disabling IPv4 in Operating System and Applications . . . . . 4
6. On-Demand Provisioning of IPv4 Addresses . . . . . . . . . . 4 6. On-Demand Provisioning of IPv4 Addresses . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IPv4 Address Literals . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 9. Security Considerations . . . . . . . . . . . . . . . . . . . 5
10. Informative References . . . . . . . . . . . . . . . . . . . 5 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
11. Informative References . . . . . . . . . . . . . . . . . . . 5
Appendix A. Solution Ideas . . . . . . . . . . . . . . . . . . . 7 Appendix A. Solution Ideas . . . . . . . . . . . . . . . . . . . 7
A.1. Remotely Disabling IPv4 . . . . . . . . . . . . . . . . . 7 A.1. Remotely Disabling IPv4 . . . . . . . . . . . . . . . . . 7
A.1.1. Indicating that IPv4 connectivity is unavailable . . 7 A.1.1. Indicating that IPv4 connectivity is unavailable . . 7
A.1.2. Disabling IPv4 in the LAN . . . . . . . . . . . . . . 7 A.1.2. Disabling IPv4 in the LAN . . . . . . . . . . . . . . 7
A.2. Client Connection Establishment Behavior . . . . . . . . 7 A.2. Client Connection Establishment Behavior . . . . . . . . 8
A.3. Disabling IPv4 in Operating System and Applications . . . 8 A.3. Disabling IPv4 in Operating System and Applications . . . 8
A.4. On-Demand Provisioning of IPv4 Addresses . . . . . . . . 8 A.4. On-Demand Provisioning of IPv4 Addresses . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The final phase of the migration to IPv6 is the sunset of IPv4, that The final phase of the migration to IPv6 is the sunset of IPv4, that
is turning off IPv4 definitively on the attached networks and on the is turning off IPv4 definitively on the attached networks and on the
upstream networks. upstream networks.
skipping to change at page 5, line 19 skipping to change at page 5, line 19
IPv4 address from being released by the home router. IPv4 address from being released by the home router.
PROBLEM 12: Hosts in the LAN have no knowledge that IPv4 is available PROBLEM 12: Hosts in the LAN have no knowledge that IPv4 is available
to them on-demand only. If they had explicit knowledge of this to them on-demand only. If they had explicit knowledge of this
fact, they could tune their behaviour so as to be more fact, they could tune their behaviour so as to be more
conservative in their use of IPv4. conservative in their use of IPv4.
PROBLEM 13: This mechanism is only being proposed for PPP even though PROBLEM 13: This mechanism is only being proposed for PPP even though
it could apply to other provisioning protocols (e.g., DHCP). it could apply to other provisioning protocols (e.g., DHCP).
7. IANA Considerations 7. IPv4 Address Literals
IPv4 addresses are often used as resource locators. For example, it
is common to encounter URLs containing IPv4 address literals on web
sites [I-D.wing-behave-http-ip-address-literals]. IPv4 address
literals may be published on media other than web sites, and may
appear in various forms other than URLs. For the operating systems
which exhibit the behavior described in
[I-D.yourtchenko-ipv6-disable-ipv4-proxyarp], this also means an
increase in the broadcast ARP traffic, which may be undesirable.
PROBLEM 14: IPv6-only hosts are unable to access resources identified
by IPv4 address literals.
8. IANA Considerations
None. None.
8. Security Considerations 9. Security Considerations
It is believed that none of the problems identified in this draft are It is believed that none of the problems identified in this draft are
security issues. security issues.
9. Acknowledgements 10. Acknowledgements
Thanks in particular to Nejc Skoberne and Lee Howard for their Thanks in particular to Andrew Yourtchenko, Lee Howard, Nejc
thorough reviews and comments. Skoberne, and Wes George for their thorough reviews and comments.
Special thanks to Marc Blanchet who was the driving force behind this Special thanks to Marc Blanchet who was the driving force behind this
work. work and to Jean-Philippe Dionne who helped with the initial version
of this document.
10. Informative References 11. Informative References
[BBF.TR242] [BBF.TR242]
Broadband Forum, "TR-242: IPv6 Transition Mechanisms for Broadband Forum, "TR-242: IPv6 Transition Mechanisms for
Broadband Networks", August 2012. Broadband Networks", August 2012.
[Huston2012] [Huston2012]
Huston, G. and G. Michaelson, "RIPE 64: Analysing Dual Huston, G. and G. Michaelson, "RIPE 64: Analysing Dual
Stack Behaviour and IPv6 Quality", April 2012. Stack Behaviour and IPv6 Quality", April 2012.
[I-D.cheshire-dnsext-multicastdns] [I-D.cheshire-dnsext-multicastdns]
Cheshire, S. and M. Krochmal, "Multicast DNS", draft- Cheshire, S. and M. Krochmal, "Multicast DNS", draft-
cheshire-dnsext-multicastdns-15 (work in progress), cheshire-dnsext-multicastdns-15 (work in progress),
December 2011. December 2011.
[I-D.fleischhauer-ipv4-addr-saving] [I-D.fleischhauer-ipv4-addr-saving]
Fleischhauer, K. and O. Bonness, "On demand IPv4 address Fleischhauer, K. and O. Bonness, "On demand IPv4 address
provisioning in Dual-Stack PPP deployment scenarios", provisioning in Dual-Stack PPP deployment scenarios",
draft-fleischhauer-ipv4-addr-saving-03 (work in progress), draft-fleischhauer-ipv4-addr-saving-03 (work in progress),
August 2012. August 2012.
[I-D.wing-behave-http-ip-address-literals]
Wing, D., "Coping with IP Address Literals in HTTP URIs
with IPv6/IPv4 Translators", draft-wing-behave-http-ip-
address-literals-02 (work in progress), March 2010.
[I-D.yourtchenko-ipv6-disable-ipv4-proxyarp] [I-D.yourtchenko-ipv6-disable-ipv4-proxyarp]
Yourtchenko, A. and O. Owen, "Disable "Proxy ARP for Yourtchenko, A. and O. Owen, "Disable "Proxy ARP for
Everything" on IPv4 link-local in the presence of IPv6 Everything" on IPv4 link-local in the presence of IPv6
global address", draft-yourtchenko-ipv6-disable- global address", draft-yourtchenko-ipv6-disable-
ipv4-proxyarp-00 (work in progress), May 2013. ipv4-proxyarp-00 (work in progress), May 2013.
[RFC2563] Troll, R., "DHCP Option to Disable Stateless Auto- [RFC2563] Troll, R., "DHCP Option to Disable Stateless Auto-
Configuration in IPv4 Clients", RFC 2563, May 1999. Configuration in IPv4 Clients", RFC 2563, May 1999.
[RFC3493] Gilligan, R., Thomson, S., Bound, J., McCann, J., and W. [RFC3493] Gilligan, R., Thomson, S., Bound, J., McCann, J., and W.
skipping to change at page 8, line 19 skipping to change at page 8, line 38
existing dependencies, and how to eliminate them. Having programs existing dependencies, and how to eliminate them. Having programs
and operating systems that behave well in an IPv6-only environment is and operating systems that behave well in an IPv6-only environment is
a prerequisite for IPv4 sunsetting. a prerequisite for IPv4 sunsetting.
A.4. On-Demand Provisioning of IPv4 Addresses A.4. On-Demand Provisioning of IPv4 Addresses
No idea. No idea.
Authors' Addresses Authors' Addresses
Jean-Philippe Dionne
Viagenie
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Phone: +1 418 656 9254
Email: jean-philippe.dionne@viagenie.ca
URI: http://viagenie.ca
Simon Perreault Simon Perreault
Viagenie Viagenie
246 Aberdeen 246 Aberdeen
Quebec, QC G1R 2E1 Quebec, QC G1R 2E1
Canada Canada
Phone: +1 418 656 9254 Phone: +1 418 656 9254
Email: simon.perreault@viagenie.ca Email: simon.perreault@viagenie.ca
URI: http://viagenie.ca URI: http://viagenie.ca
Tina Tsou Tina Tsou
Huawei Technologies (USA) Huawei Technologies (USA)
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
Phone: +1 408 330 4424 Phone: +1 408 330 4424
Email: tina.tsou.zouting@huawei.com Email: tina.tsou.zouting@huawei.com
Cathy Zhou Cathy Zhou
Huawei Technologies Huawei Technologies
Huawei Industrial Base Huawei Industrial Base
Bantian, Shenzhen Bantian, Shenzhen
China China
Email: cathy.zhou@huawei.com Email: cathy.zhou@huawei.com
 End of changes. 17 change blocks. 
32 lines changed or deleted 42 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/