draft-ietf-v6ops-v6inixp-07.txt   draft-ietf-v6ops-v6inixp-08.txt 
Internet Engineering Task Force R. Gagliano Internet Engineering Task Force R. Gagliano
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational June 4, 2010 Intended status: Informational June 25, 2010
Expires: December 6, 2010 Expires: December 27, 2010
IPv6 Deployment in Internet Exchange Points (IXPs) IPv6 Deployment in Internet Exchange Points (IXPs)
draft-ietf-v6ops-v6inixp-07.txt draft-ietf-v6ops-v6inixp-08.txt
Abstract Abstract
This document provides guidance on IPv6 deployment in Internet This document provides guidance on IPv6 deployment in Internet
Exchange Points (IXP). It includes information regarding the switch Exchange Points (IXP). It includes information regarding the switch
fabric configuration, the addressing plan and general organizational fabric configuration, the addressing plan and general organizational
tasks that need to be performed. IXPs are mainly a layer 2 tasks that need to be performed. IXPs are mainly a layer 2
infrastructure and in many cases the best recommendations suggest infrastructure and in many cases the best recommendations suggest
that the IPv6 data, control and management plane should not be that the IPv6 data, control and management plane should not be
handled differently than in IPv4. handled differently than in IPv4.
skipping to change at page 1, line 36 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 December 6, 2010. This Internet-Draft will expire on December 27, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 4, line 38 skipping to change at page 4, line 38
management tasks. The IPv6 Addressing Architecture [RFC4291] management tasks. The IPv6 Addressing Architecture [RFC4291]
requires that interface identifiers are 64 bits in size for prefixes requires that interface identifiers are 64 bits in size for prefixes
starting with binary 000, resulting in a maximum prefix length of starting with binary 000, resulting in a maximum prefix length of
/64. Longer prefix lengths up to /127 have been used operationally. /64. Longer prefix lengths up to /127 have been used operationally.
If prefix lengths longer than 64 bits are chosen, the implications If prefix lengths longer than 64 bits are chosen, the implications
described in [RFC3627] need to be considered. A /48 prefix allows described in [RFC3627] need to be considered. A /48 prefix allows
the addressing of 65536 /64 LANs. the addressing of 65536 /64 LANs.
When selecting the use of static Interface Identifiers (IIDs), there When selecting the use of static Interface Identifiers (IIDs), there
are different options on how to fill its 64 bits (or 16 hexadecimal are different options on how to fill its 64 bits (or 16 hexadecimal
characters). A non-exhausted list of possible IID selection characters). A non-exhaustive list of possible IID selection
mechanisms is the following: mechanisms is the following:
1. Some IXPs like to include the participants' ASN number decimal 1. Some IXPs like to include the participants' ASN number decimal
encoding inside each IPv6 address. The ASN decimal number is encoding inside each IPv6 address. The ASN decimal number is
used as the BCD (binary code decimal) encoding of the upper part used as the BCD (binary code decimal) encoding of the upper part
of the IID such as shown in this example: of the IID such as shown in this example:
* IXP LAN prefix: 2001:db8::/64 * IXP LAN prefix: 2001:db8::/64
* ASN: 64496 * ASN: 64496
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

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