draft-ietf-ipv6-prefix-delegation-requirement-02.txt   draft-ietf-ipv6-prefix-delegation-requirement-03.txt 
Network Working Group S. Miyakawa Network Working Group S. Miyakawa
Internet-Draft NTT Communications Corporation Internet-Draft NTT Communications Corporation
Expires: December 28, 2003 R. Droms Expires: February 21, 2004 R. Droms
Cisco Cisco
June 29, 2003 August 23, 2003
Requirements for IPv6 prefix delegation Requirements for IPv6 prefix delegation
draft-ietf-ipv6-prefix-delegation-requirement-02.txt draft-ietf-ipv6-prefix-delegation-requirement-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
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."
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 28, 2003. This Internet-Draft will expire on February 21, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document describes requirements for how IPv6 address prefixes This document describes requirements for how IPv6 address prefixes
should be delegated to an IPv6 subscriber's network (or "site"). should be delegated to an IPv6 subscriber's network (or "site").
1. Introduction 1. Introduction
With the deployment of IPv6 [1], several Internet Service Providers With the deployment of IPv6 [1], several Internet Service Providers
are ready to offer IPv6 access to the public. In conjunction with are ready to offer IPv6 access to the public. In conjunction with
widely deployed "always on" media such as ADSL and the expectation widely deployed "always on" media such as ADSL and the expectation
that cusomters will be assigned a /48 IPv6 unicast address prefix that customers will be assigned a /48 IPv6 unicast address prefix
(see RFC3513 [2] and section 3 of RFC3177 [3]), an efficient (see RFC3513 [2] and section 3 of RFC3177 [3]), an efficient
mechanism for delegating address prefixes to the customers sites is mechanism for delegating address prefixes to the customers sites is
needed. The delegation mechanism will be intended to automate the needed. The delegation mechanism will be intended to automate the
process of informing the customer's networking equipment of the process of informing the customer's networking equipment of the
prefixes to be used at the customer's site. prefixes to be used at the customer's site.
This document clarifies the requirements for IPv6 address prefix This document clarifies the requirements for IPv6 address prefix
delegation from the ISP to the site. delegation from the ISP to the site.
2. Scenario and terminology 2. Scenario and terminology
skipping to change at page 3, line 12 skipping to change at page 3, line 10
The prefix delegation mechanism should allow for delegation of The prefix delegation mechanism should allow for delegation of
prefixes of lengths between /48 and /64, inclusively. Other lengths prefixes of lengths between /48 and /64, inclusively. Other lengths
may be supported. The mechanism should allow for delegation of more may be supported. The mechanism should allow for delegation of more
than one prefix to the customer. than one prefix to the customer.
3.2 Use of Delegated Prefixes in Customer Network 3.2 Use of Delegated Prefixes in Customer Network
The prefix delegation mechanism must not prohibit or inhibit the The prefix delegation mechanism must not prohibit or inhibit the
assignment of longer prefixes, created from the delegated prefixes, assignment of longer prefixes, created from the delegated prefixes,
to links within the customer network. It is not a requirement that to links within the customer network. The prefix delegation mechanism
the prefix delegation mechanism provide for the reporting of prefix is not required to report any prefix delegations within the
delegation within the customer network back to the ISP. customer's network back to the ISP.
3.3 Static and Dynamic Assignment 3.3 Static and Dynamic Assignment
The prefix delegation mechanism should allow for long-lived static The prefix delegation mechanism should allow for long-lived static
pre-assignment of prefixes and for automated, possibly short-lived pre-assignment of prefixes and for automated, possibly short-lived
on-demand dynamic assignment of prefixes to a customer. on-demand dynamic assignment of prefixes to a customer.
3.4 Policy-based Assignment 3.4 Policy-based Assignment
The prefix delegation mechanism should allow for the use of policy in The prefix delegation mechanism should allow for the use of policy in
skipping to change at page 3, line 47 skipping to change at page 3, line 45
3.6 Accounting 3.6 Accounting
The prefix delegation mechanism must allow for the ISP to provide The prefix delegation mechanism must allow for the ISP to provide
accounting information about delegated prefixes. accounting information about delegated prefixes.
3.7 Hardware technology Considerations 3.7 Hardware technology Considerations
The prefix delegation mechanism should work on any hardware The prefix delegation mechanism should work on any hardware
technology and should be hardware technology independent. The technology and should be hardware technology independent. The
mechanism must work on shared links. The mechanism should work with mechanism must work on shared links. The mechanism should work with
all hardware technologies either with authentication mechanism or all hardware technologies either with an authentication mechanism or
without, but ISPs would like to take advantage of hardware without, but ISPs would like to take advantage of the hardware
technology's authentication mechanism if it exits. technology's authentication mechanism if it exists.
4. IANA Considerations 4. IANA Considerations
There are no IANA considerations in this document. There are no IANA considerations in this document.
5. Security considerations 5. Security considerations
Section 3.5 specifies security requirements for the prefix delegation Section 3.5 specifies security requirements for the prefix delegation
mechanism. For point to point links, where one trusts that there is mechanism. For point to point links, where one trusts that there is
no man in the middle, or one trusts layer two authentication, no man in the middle, or one trusts layer two authentication,
authentication may not be necessary. authentication may not be necessary.
A rogue delegating router can issue bogus prefixes to a requesting A rogue delegating router can issue bogus prefixes to a requesting
router. This may cause denial of service due to unreachability. router. This may cause denial of service due to unreachability.
An intruder requesting router may be able to mount a denial of A rogue requesting router (CPE) may be able to mount a denial of
service attack by repeated requests for delegated prefixes that service attack by repeated requests for delegated prefixes that
exhaust the delegating router's available prefixes. exhaust the delegating router's available prefixes.
6. Acknowledgments
The authors would like to express our thanks to Pekka Savola, Dave
Thaler, Micheal Py and other members of the IPv6 working group for
their review and constructive comnents and to the people in the IPv6
operation group of the Internet Association of Japan and NTT
Communications IPv6 project, especially Toshi Yamasaki and Yasuhiro
Shirasaki for their original discussion and suggestions.
Informative References Informative References
[1] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) [1] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998. Specification", RFC 2460, December 1998.
[2] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) [2] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
Addressing Architecture", RFC 2460, December 1998. Addressing Architecture", RFC 2460, December 1998.
[3] IESG, IAB,., "IAB/IESG Recommendations on IPv6 Address", RFC [3] IAB/IESG, "IAB/IESG Recommendations on IPv6 Address", RFC
3177, September 2001. 3177, September 2001.
Authors' Addresses Authors' Addresses
Shin Miyakawa Shin Miyakawa
Innovative IP Architecture Center, NTT Communications Corporation NTT Communications Corporation
Tokyo Tokyo
Japan Japan
Phone: +81-3-6800-3262 Phone: +81-3-6800-3262
EMail: miyakawa@nttv6.jp EMail: miyakawa@nttv6.jp
Ralph Droms Ralph Droms
Cisco Cisco
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978.936.1674 Phone: +1 978.936.1674
EMail: rdroms@cisco.com EMail: rdroms@cisco.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
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
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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/