datatracker.ietf.org
Sign in
Version 5.6.3.p2, 2014-09-29
Report a bug

Unmanaged Networks IPv6 Transition Scenarios
RFC 3750

Document type: RFC - Informational (April 2004; No errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 3750 (Informational)
Responsible AD: Bert Wijnen
Send notices to: <bob@thefinks.com>, <pekkas@netcore.fi>,<jonne.soininen@nokia.com>

Network Working Group                                         C. Huitema
Request for Comments: 3750                                     Microsoft
Category: Informational                                       R. Austein
                                                                     ISC
                                                             S. Satapati
                                                     Cisco Systems, Inc.
                                                          R. van der Pol
                                                              NLnet Labs
                                                              April 2004

              Unmanaged Networks IPv6 Transition Scenarios

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   This document defines the scenarios in which IPv6 transition
   mechanisms are to be used in unmanaged networks.  In order to
   evaluate the suitability of these mechanisms, we need to define the
   scenarios in which these mechanisms have to be used.  One specific
   scope is the "unmanaged network", which typically corresponds to a
   home or small office network.  The scenarios are specific to a single
   subnet, and are defined in terms of IP connectivity supported by the
   gateway and the Internet Service Provider (ISP).  We first examine
   the generic requirements of four classes of applications: local,
   client, peer to peer and server.  Then, for each scenario, we infer
   transition requirements by analyzing the needs for smooth migration
   of applications from IPv4 to IPv6.

Huitema, et al.              Informational                      [Page 1]
RFC 3750      Unmanaged Networks IPv6 Transition Scenarios    April 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Topology . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Applications . . . . . . . . . . . . . . . . . . . . . . . . .  4
       3.1.  Local Applications . . . . . . . . . . . . . . . . . . .  5
       3.2.  Client Applications. . . . . . . . . . . . . . . . . . .  5
       3.3.  Peer-to-Peer Applications. . . . . . . . . . . . . . . .  5
       3.4.  Server Applications. . . . . . . . . . . . . . . . . . .  5
   4.  Application Requirements of an IPv6 Unmanaged Network. . . . .  6
       4.1.  Requirements of Local Applications . . . . . . . . . . .  6
       4.2.  Requirements of Client Applications. . . . . . . . . . .  7
             4.2.1.  Privacy Requirement of Client Applications . . .  7
       4.3.  Requirements of Peer-to-Peer Applications. . . . . . . .  8
       4.4.  Requirements of Server Applications. . . . . . . . . . .  9
   5.  Stages of IPv6 Deployment. . . . . . . . . . . . . . . . . . .  9
       5.1.  Case A, Host Deployment of IPv6 Applications . . . . . . 10
             5.1.1.  Application Support in Case A. . . . . . . . . . 10
             5.1.2.  Addresses and Connectivity in Case A . . . . . . 11
             5.1.3.  Naming Services in Case A. . . . . . . . . . . . 12
       5.2.  Case B, IPv6 Connectivity with Provider Support. . . . . 12
             5.2.1.  Application Support in Case B. . . . . . . . . . 12
             5.2.2.  Addresses and Connectivity in Case B . . . . . . 13
             5.2.3.  Naming Services in Case B. . . . . . . . . . . . 14
       5.3.  Case C, IPv6 Connectivity without Provider Support . . . 14
             5.3.1.  Application Support in Case C. . . . . . . . . . 15
             5.3.2.  Addresses and Connectivity in Case C . . . . . . 15
             5.3.3.  Naming Services in Case C. . . . . . . . . . . . 15
       5.4.  Case D, ISP Stops Providing Native IPv4 Connectivity . . 15
             5.4.1.  Application Support in Case D. . . . . . . . . . 16
             5.4.2.  Addresses and Connectivity in Case D . . . . . . 16
             5.4.3.  Naming Services in Case D. . . . . . . . . . . . 17
   6.  Security Considerations. . . . . . . . . . . . . . . . . . . . 17
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
       8.1. Normative References. . . . . . . . . . . . . . . . . . . 18
       8.2. Informative References. . . . . . . . . . . . . . . . . . 18
   9.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
   10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 20

Huitema, et al.              Informational                      [Page 2]
RFC 3750      Unmanaged Networks IPv6 Transition Scenarios    April 2004

[include full document text]