© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v2.09-1 Deployment of IPv6 Examining IPv6 Address Allocation.

Презентация:



Advertisements
Похожие презентации
© 2005 Cisco Systems, Inc. All rights reserved. BGP v Route Selection Using Policy Controls Using Multihomed BGP Networks.
Advertisements

© 2005 Cisco Systems, Inc. All rights reserved. BGP v Customer-to-Provider Connectivity with BGP Understanding Customer-to-Provider Connectivity.
© 2005 Cisco Systems, Inc. All rights reserved.INTRO v Constructing Network Addresses Classifying Network Addressing.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v Customer-to-Provider Connectivity with BGP Connecting a Multihomed Customer to Multiple Service.
© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Security Issues in IPv6 Discussing Security Issues in an IPv6 Transition Environment.
© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Examining Mobility Examining Mobile IPv4.
© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Examining Mobility Examining Mobile IPv6.
© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Deployment of IPv6 Understanding the IPv6 Multihoming Issues.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Integrating Internet Access with MPLS VPNs Implementing Internet Access as a Separate VPN.
© 2006 Cisco Systems, Inc. All rights reserved. BSCI v Implementing IPv6 Using IPv6 with IPv4.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Implementation Configuring Small-Scale Routing Protocols Between PE and CE Routers.
© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Deployment of Cisco Unified CallManager Release 5.0 Endpoints Configuring Cisco Unified CallManager.
© 2006 Cisco Systems, Inc. All rights reserved. BSCI v Implementing IPv6 Defining IPv6 Addressing.
© 2006 Cisco Systems, Inc. All rights reserved.ISCW v IPsec VPNs Implementing the Cisco VPN Client.
© 2006 Cisco Systems, Inc. All rights reserved. ICND v Determining IP Routes Implementing Variable-Length Subnet Masks.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v BGP Overview Processing BGP Routes.
© 2005 Cisco Systems, Inc. All rights reserved.INTRO v Managing Your Network Environment Managing Cisco Devices.
© 2006 Cisco Systems, Inc. All rights reserved. IP6FD v IPv6-Enabled Routing Protocols Examining Integrated IS/IS.
© 2006 Cisco Systems, Inc. All rights reserved. HIPS v Configuring Groups and Policies Configuring Policies.
© 2007 Cisco Systems, Inc. All rights reserved.SNRS v Secured Connectivity Examining Cisco IOS VPNs.
Транксрипт:

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Deployment of IPv6 Examining IPv6 Address Allocation

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v The Early IPv6 Internet: The 6bone The early IPv6 Internet was an experimental collection of IPv6 nodes and networks collectively known as the 6bone. Mostly tunneled traffic at first Served as a testbed for address allocation methods and standards testing Provided experimental address prefixes for users (3FFE::/16) Ceased allocating address blocks in June 2004 and was officially closed on June 6, 2006

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Deployment of the Production IPv6 Internet IPv6 address space must be available to build the production IPv6 Internet. The 6bone used test addresses. Regional registries allocate IPv6 production prefixes to ISPs based on a common policy.

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v IPv6 Address Registries As in IPv4, the IPv6 address space is managed by the regional registries: –Asia Pacific Network Information Center (APNIC) –American Registry for Internet Numbers (ARIN) –Latin American and Caribbean Network Information Center (LACNIC) –Réseaux IP Européennes: Network Coordination Centre (RIPE-NCC) –African Network Information Center (AfriNIC) Registries are based on geographical location.

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Definitions IANA RIR NIR LIR/ISP EU EU(ISP) Regional Internet Registries (APNIC, ARIN, RIPE, LACNIC, plus future) National Internet Registries (Asia Pacific region) Local Internet Registries (ISPs) End Users Internet Assigned Numbers Authority

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v IPv6 Address Allocation Policy Registries, allocation policy: Allocation policy is identical among registries, but prices and management can be different. It was reviewed by IETF and by a public consultation process. Addresses are only given to ISPs, not to enterprises. Address allocation started in July Policy was adopted in July 2002.

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Current IPv6 Address Allocation Policy Current address allocation policy: Initial allocation criteria: –Be an LIR (ISP), not end site –Plan to provide IPv6 connectivity to organizations –Plan for at least 200 /48 assignments within two years

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Current IPv6 Address Allocation Policy (Cont.) Current address allocation policy: Minimum prefix length initially assigned to ISP is /32. –More space is available if justified. –Current /35 holders, under old policy, are automatically entitled to receive a /32. Subsequent allocation is based on utilization of /48 assignments.

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Changing IPv6 Allocation Policy Pressure for provider-independent IPv6 addressing is generating change Many large organizations are rejecting requirement to only obtain IPv6 addresses from ISP –ARIN proposal makes provisions for provider- independent allocations –LIRs will have to determine policy for minimum block size to advertise and accept

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Assignment of IPv6 addresses to organizations: /48 the general case –Actual allocations can vary depending upon organizational requirements /64 when it is known that one and only one subnet is needed /128 when it is absolutely known that one and only one device is connecting IPv6 Address Allocation to Organizations

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v IPv6 Address Allocation Process The IPv6 address allocation process: IANA allocates from 2000::/3 to registries. Each registry receives a /12 prefix from IANA. Registry allocates a /32 prefix to an IPv6 ISP. ISP allocates a /48 prefix to each customer. 2A56 00A1 ISP Prefix Site Prefix LAN Prefix /32 /48/64 Registry /12

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v :: FFFF:: 2000::/3 4000::/3 Whole Allocated Address Space Current IANA Allocated Space for Registries One Registry Space 2A50:: /23 2A60:: /23 One Provider Space 2A56: 00A1: : /32 2A56: 00A2: : /32 One Customer Space 2A56: 00A1: D98E: :/48 2A56: 00A1: D98F: :/48 Partition of Allocated IPv6 Address Space

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v One LAN One host: 2A56:00A1:D98E:0001:290:27ff:fe3a:9e9a One Customer Space 2A56: 00A1: D98E: :/48 2A56: 00A1: D98F: :/48 2A56: 00A1: D98E: 0001: :/64 LAN prefix (64 bits)Host (64 bits) Partition of Allocated IPv6 Address Space (Cont.)

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Connecting to an ISP Network An IPv6 ISP must peer with other ISPs, get a prefix from the registry, and provide connectivity and addresses to customers. IPv6 ISP Peering Customer Allocates prefix Regional Registry

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Network Access Points Tier 1 providers exchange traffic in NAPs: No default route is propagated or announced. NAPs may have route servers. ISP NAP

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Connecting an Enterprise Network To connect an enterprise network to the IPv6 Internet, perform the following steps: Connect the enterprise network to an IPv6 ISP. Obtain an end site prefix from the ISP. IPv6 Internet IPv6 Network IPv6 ISP Default Route /48 Prefix Enterprise

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Steps (Cont.): Design an address plan for the enterprise network: –RFC 3531 describes an efficient method for address plans. Allocate /64 prefixes to each LAN. Default Route /48 prefix 2001: DB8: 0001: :/48 to ISP IPv6 Network Ethernet LAN /64 prefix 2001:DB8: 0001:0001: :/64 /64 prefix 2001:DB8:0001: 0003: :/64 /64 prefix 2001:DB8:0001: 0002: :/64 Connecting an Enterprise Network (Cont.)

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Typical Configuration: Addressing 2001:0DB8:0002::/ :0DB8:0001::/ :0418:0001::/48 Allocate /48 to customers Customer 2 Customer 3 Customer 1 ISP :0DB8::/32 ISP :0418::/32 IPv6 Internet 2000::/3

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Customer 2 Customer 3 Customer 1 ISP :0DB8::/32 ISP :0418::/32 Typical Configuration: Routing IPv6 Internet 2001::/ :0DB8:0002:/ :0DB8:0001:/ :0DB80001:/48 Only announce the /32 prefix Configure a default route to ISP

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v A tunnel server can be used to connect a single host or small network over the IPv4 Internet. IPv4 Internet IPv6 over IPv4 Tunnel Tunnel Server IPv6 Network Connecting As a Host Using a Tunnel Server IPv6 Internet

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v IPv4 Internet Connecting As a Host Using 6to4 The 6to4 tunneling mechanism can be used to connect a single host or network over the IPv4 Internet. IPv6 over IPv4 Tunnel 6to4 Router 6to4 Host 6to4 Router IPv6 Internet IPv6 Network

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v Summary The IPv6 Internet, like the IPv4 Internet, is made up of interconnected IPv6 nodes and networks. The IPv6 Internet started with the 6bone, but now consists entirely of nodes and networks numbered from the production IPv6 address block, 2000::/3. Allocations are made from IANA to regional registries, which in turn provide address space to large ISPs residing in that region, which in turn allocate address space to end sites. There are several of requirements for ISPs to obtain address space, including establishing that they are in the business of providing Internet connectivity and that their business plan includes a way to make assignments in the near term. There are many ways to connect a network to the IPv6 Internet, including obtaining native connectivity through an ISP or obtaining services via a manual or automatic tunnel.

© 2006 Cisco Systems, Inc. All rights reserved.IP6FD v