draft-ietf-v6ops-ent-scenarios-04.txt   draft-ietf-v6ops-ent-scenarios-05.txt 
IPv6 Operations Working Group IPv6 Operations Working Group
Internet Draft Jim Bound (Editor) Internet Draft Jim Bound (Editor)
Document: draft-ietf-v6ops-ent-scenarios-04.txt Hewlett Packard Document: draft-ietf-v6ops-ent-scenarios-05.txt Hewlett Packard
Obsoletes: draft-ietf-v6ops-ent-scenarios-03.txt Obsoletes: draft-ietf-v6ops-ent-scenarios-04.txt
Expires: January 2005 Expires: January 2005
IPv6 Enterprise Network Scenarios IPv6 Enterprise Network Scenarios
<draft-ietf-v6ops-ent-scenarios-04.txt> <draft-ietf-v6ops-ent-scenarios-05.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
This document is an Internet-Draft and is in full conformance patent or other IPR claims of which I am aware have been
with all provisions of Section 10 of RFC2026. disclosed, and any of which I become aware will be disclosed, in
accordance with RFC 3668.
This document is a submission by the Internet Protocol IPv6
Working Group of the Internet Engineering Task Force (IETF).
Comments should be submitted to the ipng@sunroof.eng.sun.com
mailing list.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." 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 January 10, 2005.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document describes the scenarios for IPv6 deployment within This document describes the scenarios for IPv6 deployment within
enterprise networks. It defines a small set of basic enterprise enterprise networks. It defines a small set of basic enterprise
scenarios and includes pertinent questions to allow enterprise scenarios and includes pertinent questions to allow enterprise
administrators to further refine their deployment scenarios. administrators to further refine their deployment scenarios.
Enterprise deployment requirements are discussed in terms of Enterprise deployment requirements are discussed in terms of
coexistence with IPv4 nodes, networks and applications, and in coexistence with IPv4 nodes, networks and applications, and in
terms of basic network infrastructure requirements for IPv6 terms of basic network infrastructure requirements for IPv6
deployment. The scenarios and requirements described in this deployment. The scenarios and requirements described in this
skipping to change at page 2, line 30 skipping to change at page 2, line 30
4.6 Network Management........................................14 4.6 Network Management........................................14
4.7 Address Planning..........................................14 4.7 Address Planning..........................................14
4.8 Multicast..................................................14 4.8 Multicast..................................................14
4.9 Multihoming................................................14 4.9 Multihoming................................................14
5. Security Considerations....................................14 5. Security Considerations....................................14
6. References.................................................14 6. References.................................................14
6.1 Normative References......................................15 6.1 Normative References......................................15
6.2 Non-Normative References..................................15 6.2 Non-Normative References..................................15
Document Acknowledgments.......................................15 Document Acknowledgments.......................................15
Author's Address...............................................16 Author's Address...............................................16
Intellectual Property Statement................................17 Intellectual Property and Copyright Statements.................17
Full Copyright Statement.......................................18
Acknowledgement................................................18
1. Introduction 1. Introduction
This document describes the scenarios for IPv6 deployment within This document describes the scenarios for IPv6 deployment within
enterprise networks. It defines a small set of basic enterprise enterprise networks. It defines a small set of basic enterprise
scenarios and includes pertinent questions to allow enterprise scenarios and includes pertinent questions to allow enterprise
administrators to further refine their deployment scenarios. administrators to further refine their deployment scenarios.
Enterprise deployment requirements are discussed in terms of Enterprise deployment requirements are discussed in terms of
coexistence with IPv4 nodes, networks and applications, and in coexistence with IPv4 nodes, networks and applications, and in
terms of basic network infrastructure requirements for IPv6 terms of basic network infrastructure requirements for IPv6
skipping to change at page 17, line 42 skipping to change at page 17, line 42
Roy Brabson Roy Brabson
IBM IBM
PO BOX 12195 PO BOX 12195
3039 Cornwallis Road 3039 Cornwallis Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Phone: +1 919 254 7332 Phone: +1 919 254 7332
Email: rbrabson@us.ibm.com Email: rbrabson@us.ibm.com
fi fi
Intellectual Property and Copyright Statements
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain Intellectual Property Rights or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; nor does it represent that it has
effort to identify any such rights. Information on the IETF's made any independent effort to identify any such rights. Information
procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such proprietary
rights by implementors or users of this specification can be obtained
from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any Copies of IPR disclosures made to the IETF Secretariat and any
copyrights, patents or patent applications, or other proprietary rights assurances of licenses to be made available, or the result of an
which may cover technology that may be required to practice this attempt made to obtain a general license or permission for the use of
standard. Please address the information to the IETF Executive such proprietary rights by implementers or users of this
Director. specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
Full Copyright Statement The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Copyright (C) The Internet Society (2002). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/