draft-ietf-v6ops-addcon-05.txt   draft-ietf-v6ops-addcon-06.txt 
IPv6 Operations G. Van de Velde IPv6 Operations G. Van de Velde
Internet-Draft C. Popoviciu Internet-Draft C. Popoviciu
Intended status: Informational Cisco Systems Intended status: Informational Cisco Systems
Expires: December 24, 2007 T. Chown Expires: April 3, 2008 T. Chown
University of Southampton University of Southampton
O. Bonness O. Bonness
C. Hahn C. Hahn
T-Systems Enterprise Services GmbH T-Systems Enterprise Services GmbH
June 22, 2007 October 1, 2007
IPv6 Unicast Address Assignment Considerations IPv6 Unicast Address Assignment Considerations
<draft-ietf-v6ops-addcon-05.txt> <draft-ietf-v6ops-addcon-06.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 24, 2007. This Internet-Draft will expire on April 3, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
One fundamental aspect of any IP communications infrastructure is its One fundamental aspect of any IP communications infrastructure is its
addressing plan. With its new address architecture and allocation addressing plan. With its new address architecture and allocation
policies, the introduction of IPv6 into a network means that network policies, the introduction of IPv6 into a network means that network
skipping to change at page 3, line 38 skipping to change at page 3, line 38
4.3. Manual/Dynamic Assignment Option . . . . . . . . . . . . . 14 4.3. Manual/Dynamic Assignment Option . . . . . . . . . . . . . 14
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 15 8.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Case Studies . . . . . . . . . . . . . . . . . . . . 17 Appendix A. Case Studies . . . . . . . . . . . . . . . . . . . . 17
A.1. Enterprise Considerations . . . . . . . . . . . . . . . . 17 A.1. Enterprise Considerations . . . . . . . . . . . . . . . . 17
A.1.1. Obtaining general IPv6 network prefixes . . . . . . . 18 A.1.1. Obtaining general IPv6 network prefixes . . . . . . . 18
A.1.2. Forming an address (subnet) allocation plan . . . . . 18 A.1.2. Forming an address (subnet) allocation plan . . . . . 19
A.1.3. Other considerations . . . . . . . . . . . . . . . . . 19 A.1.3. Other considerations . . . . . . . . . . . . . . . . . 19
A.1.4. Node configuration considerations . . . . . . . . . . 20 A.1.4. Node configuration considerations . . . . . . . . . . 20
A.2. Service Provider Considerations . . . . . . . . . . . . . 20 A.2. Service Provider Considerations . . . . . . . . . . . . . 21
A.2.1. Investigation of objective Requirements for an A.2.1. Investigation of objective Requirements for an
IPv6 addressing schema of a Service Provider . . . . 21 IPv6 addressing schema of a Service Provider . . . . 21
A.2.2. Exemplary IPv6 address allocation plan for a A.2.2. Exemplary IPv6 address allocation plan for a
Service Provider . . . . . . . . . . . . . . . . . . . 24 Service Provider . . . . . . . . . . . . . . . . . . . 24
A.2.3. Additional Remarks . . . . . . . . . . . . . . . . . . 28 A.2.3. Additional Remarks . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
Intellectual Property and Copyright Statements . . . . . . . . . . 33 Intellectual Property and Copyright Statements . . . . . . . . . . 33
1. Introduction 1. Introduction
skipping to change at page 17, line 43 skipping to change at page 17, line 43
(http://ops.ietf.org/multi6/draft-list.html )". (http://ops.ietf.org/multi6/draft-list.html )".
Appendix A. Case Studies Appendix A. Case Studies
This appendix contains two case studies for IPv6 addressing schemas This appendix contains two case studies for IPv6 addressing schemas
that have been based on the statements and considerations of this that have been based on the statements and considerations of this
draft. These case studies illustrate how this draft has been used in draft. These case studies illustrate how this draft has been used in
two specific network scenarios. The case studies may serve as basic two specific network scenarios. The case studies may serve as basic
considerations for an administrator who designs the IPv6 addressing considerations for an administrator who designs the IPv6 addressing
schema for an enterprise or ISP network, but are not intended to schema for an enterprise or ISP network, but are not intended to
serve as general design proposal for every kind of IPv6 network. serve as general design proposal for every kind of IPv6 network. All
subnet sizes used in this appendix are for practical visualization
and do not dictate RIR policy.
A.1. Enterprise Considerations A.1. Enterprise Considerations
In this section we consider a case study of a campus network that is In this section we consider a case study of a campus network that is
deploying IPv6 in parallel with existing IPv4 protocols in a dual- deploying IPv6 in parallel with existing IPv4 protocols in a dual-
stack environment. The specific example is the University of stack environment. The specific example is the University of
Southampton (UK), focusing on a large department within that network. Southampton (UK), focusing on a large department within that network.
The deployment currently spans around 1,000 hosts and over 1,500 The deployment currently spans around 1,000 hosts and over 1,500
users. users.
A.1.1. Obtaining general IPv6 network prefixes A.1.1. Obtaining general IPv6 network prefixes
In the case of a campus network, the site will typically take its In the case of a campus network, the site will typically take its
connectivity from its National Research and Education Network (NREN). connectivity from its National Research and Education Network (NREN).
Southampton connects to JANET, the UK academic network, via its local Southampton connects to JANET, the UK academic network, via its local
regional network LeNSE. JANET currently has a /32 allocation from regional network LeNSE. JANET currently has a /32 allocation from
RIPE NCC. The current recommended practice is for sites to receive a RIPE NCC. The current recommended practice is for sites to receive a
 End of changes. 8 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/