IPv6 @ Cisco

Ansar Pasha
Patrick Grossetete
Cisco Systems
Cisco Systems
Network Consultant,
Cisco IOS IPv6 Product Manager
Govt & Defense, South
pgrosset@[Link]
ansar@[Link] 1
 Agenda

• IPv6 Business Case

• IPv6 Protocols & Standards
• Integration and Transition
• Cisco IOS IPv6 Roadmap
• IPv6 Deployment scenarios
• References

Presentation_ID 2
 IPv6 - So what’s really changed ?!

• Expanded Address Space

Address length quadrupled to 16 bytes

• Header Format Simplification

Fixed length, optional headers are daisy-chained
IPv6 header is twice as long (40 bytes) as IPv4 header without options (20 bytes)

• No checksumming at the IP network layer

• No hop-by-hop segmentation
Path MTU discovery
• 64 bits aligned
• Authentication and Privacy Capabilities
IPsec is mandated
• No more broadcast

Presentation_ID 3
 IPv4 & IPv6 Header Comparison

IPv4 Header IPv6 Header

Version IHL Type of Service Total Length
Version Traffic Class Flow Label

Fragment
Identification Flags
Offset
Next
Payload Length Hop Limit
Header
Time to Live Protocol Header Checksum

Source Address
Destination Address
Source Address
Options Padding
Legend

- field’s name kept from IPv4 to IPv6

- fields not kept in IPv6 Destination Address
- Name & position changed in IPv6
- New field in IPv6
Presentation_ID 4
 How Was IPv6 Address Size Chosen?

• Some wanted fixed-length, 64-bit addresses

Easily good for 1012 sites, 1015 nodes, at .0001 allocation
efficiency (3 orders of magnitude more than IPv6
requirement)
Minimizes growth of per-packet header overhead
Efficient for software processing

• Some wanted variable-length, up to 160 bits

Compatible with OSI NSAP addressing plans
Big enough for auto-configuration using IEEE 802 addresses
Could start with addresses shorter than 64 bits & grow later

• Settled on fixed-length, 128-bit addresses

(340,282,366,920,938,463,463,374,607,431,768,211,456 in all!)
Presentation_ID 5
 IPv6 Addressing

• IPv6 Addressing rules are covered by multiples RFC’s

Architecture defined by RFC 3513 (obsoletes RFC 2373)

• Address Types are :

Unicast : One to One (Global, Link local, Site local, Compatible)
Anycast : One to Nearest (Allocated from Unicast)
Multicast : One to Many
Reserved

• A single interface may be assigned multiple IPv6

addresses of any type (unicast, anycast, multicast)
No Broadcast Address -> Use Multicast

Presentation_ID 6
 IPv6 Address Representation

• 16-bit fields in case insensitive colon hexadecimal

representation
[Link]
• Leading zeros in a field are optional:
[Link]
• Successive fields of 0 represented as ::, but only once in an
address:
• [Link]
• 2031::130F::9C0:876A:130B
• [Link] => ::1
• [Link] => ::
• IPv4-compatible address representation
• [Link][Link] = ::[Link] = [Link]

Presentation_ID 7
 IPv6 Addressing

• Prefix Format (PF) Allocation

PF = 0000 0000 : Reserved
PF = 001 : Aggregatable Global Unicast Address
PF = 1111 1110 10 : Link Local Use Addresses (FE80::/10)
PF = 1111 1110 11 : Site Local Use Addresses (FEC)::/10)
PF = 1111 1111 : Multicast Addresses (FF00::/8)
Other values are currently Unassigned (approx. 7/8th of total)
• All Prefix Formats have to support EUI-64 bits Interface ID setting
But Multicast

Presentation_ID 8
 Aggregatable Global Unicast Addresses

Provider Site Host

3 45 bits 16 bits 64 bits

Global Routing Prefix SLA Interface ID

001

• Aggregatable Global Unicast addresses are:

Addresses for generic use of IPv6
Structured as a hierarchy to keep the aggregation
• See RFC 3513

Presentation_ID 9
 Address Allocation Policy
/23 /32 /48 /64

2001 0410 Interface ID

Registry
ISP prefix
Site prefix
Bootstrap process - RFC2450
LAN prefix

• The allocation process is under reviewed by the Registries:

IANA allocates 2001::/16 to registries
Each registry gets a /23 prefix from IANA
Formely, all ISP were getting a /35
With the new policy, Registry allocates a /32 prefix to an IPv6 ISP
Then the ISP allocates a /48 prefix to each customer (or potentially /64)
[Link]
Presentation_ID 10
 Interface IDs

• Lowest-order 64-bit field of unicast address

may be assigned in several different ways:
– auto-configured from a 64-bit EUI-64, or expanded
from a 48-bit MAC address (e.g., Ethernet address)
– auto-generated pseudo-random number
(to address privacy concerns)
– assigned via DHCP
– manually configured

Presentation_ID 11
 IPv6 Address Privacy (RFC 3041)
/23 /32 /48 /64

2001 0410 Interface ID

• Temporary addresses for IPv6 host client application, eg.

Web browser
Inhibit device/user tracking but is also a potential issue
More difficult to scan all IP addresses on a subnet but port
scan is identical when an address is known
Random 64 bit interface ID, run DAD before using it
Rate of change based on local policy
Implemented on Microsoft Windows XP
From RFC 3041: “…interface identifier …facilitates the tracking
of individual devices (and thus potentially users)…”
Presentation_ID 12
 Hierarchical Addressing & Aggregation

Only
Customer announces
no 1 the /32
ISP prefix
[Link]/48
[Link]/32

Customer IPv6 Internet

no 2
2001::/16
[Link]/48

Larger address space enables:

Aggregation of prefixes announced in the global
routing table.
Efficient and scalable routing.
But current Multi-Homing schemes break the model
Presentation_ID 13
 Link-Local & Site-Local Unicast
Addresses

• Link-local addresses for use during auto-configuration and

when no routers are present:

1111 1110 10 0 interface ID

• Site-local addresses for independence from Global

Reachability, similar to IPv4 private address space
RFC3513 specifies 54 bits for SLA field but SL may get deprecated by
IPv6 WG soon

1111 1110 11 SLA* interface ID

Presentation_ID 14
 6to4 and ISATAP Addresses

• 6to4 (RFC 3056) – WAN tunneling

/16 /48 /64

Public IPv4
2002 address SLA Interface ID

•ISATAP (Draft) – Campus tunneling

/23 /32 /48 /64

2001 0410 00 00 5E FE IPv4 Host address

Registry
32 bits
ISP prefix
32 bits
Site prefix
Presentation_ID 15
 Expanded Address Space
Multicast Addresses (RFC 3513)

128 bits

0 Group ID
T=0 a permanent IPv6 Multicast address.
1111 1111
Flags T=1 a transient IPv6 multicast address
Flags =
F F 0 0 0 T scope

8 bits 8 bits 1 = node

2 = link
Scope = 5 = site
8 = organization
E= global

• Multicast is used in the context of one-to-

many.
Presentation_ID 16
 Multicast Address Examples

• All Nodes Addresses:

[Link]
[Link]
• All Routers Addresses:
[Link]
[Link]
[Link]
• OSPv3:
AllSPFRouters : FF02::5
AllDRouters : FF02::6
• Solicited-Node Address:
[Link]XX:XXXX
Concatenation of prefix [Link]/104 with the low-order 24 bits of an
address (unicast or anycast)

Presentation_ID 17
 more on IPv6 Addressing

80 bits 16 bits 32 bits

0000……………………………0000 0000 IPv4 Address

IPv6 Addresses with Embedded IPv4 Addresses

80 bits 16 bits 32 bits

0000……………………………0000 FFFF IPv4 Address

IPv4 mapped IPv6 address

Presentation_ID 18
 IPv6 Addressing Examples

LAN: [Link]/64

Ethernet0

interface Ethernet0
ipv6 address [Link]/64 eui-64
MAC address: 0060.3e47.1530

router# show ipv6 interface Ethernet0

Ethernet0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::260:3EFF:FE47:1530
Global unicast address(es):
[Link], subnet is [Link]/64
Joined group address(es):
FF02::1:FF47:1530
FF02::1
FF02::2
MTU is 1500 bytes

Presentation_ID 19
 6BONE

• The 6bone is an IPv6 testbed setup to assist in the

evolution and deployment of IPv6 in the Internet.
The 6bone is a virtual network layered on top of portions of the
physical IPv4-based Internet to support routing of IPv6 packets,
as that function has not yet been integrated into many
production routers. The network is composed of islands that
can directly support IPv6 packets, linked by virtual point-to-
point links called "tunnels". The tunnel endpoints are typically
workstation-class machines having operating system support
for Ipv6.

• Over 50 countries are currently involved

• Registry, maps and other information may be found on
[Link]

Presentation_ID 20
 6Bone Addressing

/28 /48 /64

3ffe Interface ID

pTLA prefix
site prefix
LAN prefix

• 6Bone address space defined in RFC2471 uses 3FFE::/16

A pTLA receives a /28 prefix
A site receives a /48 prefix
A LAN receives a /64 prefix
• Guidelines for routing on 6bone - RFC2772

Presentation_ID 21
 6Bone Topology

BGP
Site Peering
Site
Site Site
pTLA Site
Site
Provider
pTL
pTL
Site pTLA ApTLA
A

Site
Site pTLA
Provider
Site
• 6Bone is a test bed network with hundreds of sites from 50 countries
• The 6Bone topology is a hierarchy of providers
• First-level nodes are backbone nodes called pseudo Top-Level
Aggregator (pTLA)
Presentation_ID 22
 IPv6 Header Options (RFC 2460)

IPv6 Header
Next Header TCP Header
= TCP + Data

IPv6 Header
Next Header Routing Header TCP Header
= Routing Next Header = TCP + Data

IPv6 Header Routing Header Fragment of

Next Header Next Header = Fragment Header TCP Header
= Routing Fragment Next Header = TCP + Data

• Processed only by node identified in IPv6 Destination Address field => much lower
overhead than IPv4 options
exception: Hop-by-Hop Options header
• Eliminated IPv4’s 40-octet limit on options
in IPv6, limit is total packet size, or Path MTU in some cases
Presentation_ID 23
 IPv6 Header Options (RFC2460)

• Currently defined Headers should appear in the following order

IPv6 header
Hop-by-Hop Options header
Destination Options header
Routing header
Fragment header
Authentication header (RFC 1826)
Encapsulating Security Payload header (RFC 1827)
Destination Options header
upper-layer header

Presentation_ID 24
 IPv6 and Path MTU Discovery

• Definitions:
link MTU a link’s maximum transmission unit,
path MTU the minimum MTU of all the links in a
path between a source and a destination
• Minimum link MTU for IPv6 is 1280 octets (68 octets for IPv4)
On links with MTU < 1280, link-specific fragmentation and reassembly must be used
• Implementations are expected to perform path MTU discovery to send packets
bigger than 1280 octets:
for each dest., start by assuming MTU of first-hop link
if a packet reaches a link in which it cannot fit, will invoke ICMP “packet too big” message to
source, reporting the link’s MTU; MTU is cached by source for specific destination
• Minimal implementation can omit path MTU discovery as long as all packets kept ≤
1280 octets – e.g., in a boot ROM

Presentation_ID 25
 Neighbor Discovery (RFC 2461)

• Protocol built on top of ICMPv6 (RFC 2463)

Combination of IPv4 protocols (ARP, ICMP,…)
• Neighbor Discovery:
Determines the link-layer address of a neighbor on the same link,
Duplicate Address Detection
Finds neighbor routers, Keeps track of neighbors
• Defines 5 ICMPv6 packet types
Router Solicitation / Router Advertisements
Neighbor Solicitation / Neighbor Advertisements
Redirect

Presentation_ID 26
 IPv6 Auto-Configuration

• Stateless (RFC2462) SUBNET PREFIX +

RA indicates MAC ADDRESS
Host autonomously configures its own Link-Local
address SUBNET
Router solicitation are sent by booting nodes to request PREFIX
RAs for configuring the interfaces.

• Stateful
DHCPv6 (under definition at IETF)

• Renumbering
Hosts renumbering is done by modifying the RA to
announce the old prefix with a short lifetime and the new
prefix. SUBNET PREFIX +
MAC ADDRESS
Router renumbering protocol (RFC 2894), to allow domain- At boot time, an IPv6 host
interior routers to learn of prefix introduction / withdrawal
build a Link-Local address,
then its global IPv6
address(es) from RA

Presentation_ID 27
 Stateless Autoconfiguration

1. RS 2. RA 2. RA

1 - ICMP Type = 133 (RS)

2 - ICMP Type = 134 (RA)
Src = ::
Src = Router Link-local Address
Dst = All-Routers multicast Address
Dst = All-nodes multicast address
query= please send RA
Data= options, prefix, lifetime,
autoconfig flag

Router solicitations are sent by booting nodes to

request RAs for configuring the interfaces.
Presentation_ID 28
 Duplicate Address Detection

A B

ICMP type = 135

Src = 0 (::)
Dst = Solicited-node multicast of A
Data = link-layer address of A
Query = what is your
link address?

Duplicate Address Detection (DAD) uses neighbor

solicitation to verify the existence of an address to be
configured.

Presentation_ID 29
 Routing in IPv6

• As in IPv4, IPv6 has 2 families of routing protocols: IGP and EGP,

and still uses the longest-prefix match routing algorithm
• IGP
RIPng (RFC 2080)
Cisco EIGRP for IPv6
OSPFv3 (RFC 2740)
Integrated IS-ISv6 (draft-ietf-isis-ipv6-02)
• EGP : MP-BGP4 (RFC 2858 and RFC 2545)
• Cisco IOS supports all of them
Pick one meeting your objectives

Presentation_ID 30
 OSPFv3 overview

• OSPFv3 is OSPF for IPv6 (RFC 2740)

• Based on OSPFv2, with enhancements
• Distributes IPv6 prefixes
• Runs directly over IPv6
• Ships-in-the-night with OSPFv2

Presentation_ID 31
 Differences from OSPFv2

• Runs over a link, not a subnet

• Multiple instances per link

• Topology not IPv6-specific

– Router ID
– Link ID

• Standard authentication mechanisms

• Uses link local addresses
• Generalized flooding scope
• Two new LSA types
Presentation_ID 32
 OSPFv3 configuration example

Router1#
Area 0
interface Ethernet0
ipv6 address [Link]/64 Router2
ipv6 ospf 1 area 0

interface Ethernet1
LAN1: [Link]/64
ipv6 address [Link]/64
ipv6 ospf 1 area 1
Eth0

ipv6 router ospf 1

Router1
router-id [Link]
Eth1
area 1 range [Link]/48

LAN2: [Link]/64

Area 1

Presentation_ID 33
 IS-IS Standards

• IETF IS-IS for IP Internets WG

[Link]
• ISO 10589 specifies OSI IS-IS routing protocol for CLNS traffic
Tag/Length/Value (TLV) options to enhance the protocol
A Link State protocol with a 2 level hierarchical architecture.
• RFC 1195 added IP support, also known as Integrated IS-IS (I/IS-IS)
I/IS-IS runs on top of the Data Link Layer
Requires CLNP to be configured
• Draft RFC defines how to add IPv6 address family support to IS-IS
[Link]
• Draft RFC introduces Multi-Topology concept for IS-IS
[Link]

Presentation_ID 34
 IS-IS for IPv6

• 2 Tag/Length/Values added to introduce IPv6 routing

• IPv6 Reachability TLV (0xEC)
External bit
Equivalent to IP Internal/External Reachability TLV’s
• IPv6 Interface Address TLV (0xE8)
For Hello PDUs, must contain the Link-Local address
For LSP, must only contain the non-Link Local address
• IPv6 NLPID (0x8E) is advertised by IPv6 enabled routers

Presentation_ID 35
 Cisco IOS IS-IS dual IP configuration

Router1#
interface ethernet-1
ip address [Link] [Link]
LAN1: [Link]/64 ipv6 address [Link]/64
ip router isis
Ethernet-1
ipv6 router isis
Router1 interface ethernet-2
Ethernet-2 ip address [Link] [Link]
ipv6 address [Link]/64
LAN2: [Link]/64 ip router isis
ipv6 router isis

router isis
address-family ipv6
redistribute static
Dual IPv4/IPv6 configuration. exit-address-family
net 42.0001.0000.0000.072c.00
Redistributing both IPv6 static routes redistribute static
and IPv4 static routes.
Presentation_ID 36
 Multi-Topology IS-IS extensions

• New TLVs attributes for Multi-Topology extensions.

Multi-topology TLV: contains one or more multi-topology ID in which the router participates. It is theoretically
possible to advertise an infinite number of topologies. This TLV is included in IIH and the first fragment of a
LSP.
MT Intermediate Systems TLV: this TLV appears as many times as the number of topologies a node supports. A
MT ID is added to the extended IS reachability TLV type 22.
Multi-Topology Reachable IPv4 Prefixes TLV: this TLV appears as many times as the number of IPv4 announced
by an IS for a give n MT ID. Its structure is aligned with the extended IS Reachability TLV Type 236 and add a MT
ID.
Multi-Topology Reachable IPv6 Prefixes TLV: this TLV appears as many times as the number of IPv6 announced
by an IS for a given MT ID. Its structure is aligned with the extended IS Reachability TLV Type 236 and add a MT
ID.

• Multi-Topology ID Values
Multi-Topology ID (MT ID) standardized and in use in Cisco IOS:
MT ID #0 – “standard” topology for IPv4/CLNS
MT ID #2 – IPv6 Routing Topology.

Presentation_ID 37
 Cisco IOS Multi-Topology IS-IS
configuration example

Router1#
Area B interface ethernet-1
ip address [Link] [Link]
ipv6 address [Link]/64
ip router isis
ipv6 router isis
isis ipv6 metric 20
LAN1: [Link]/64
Ethernet-1 interface ethernet-2
ip address [Link] [Link]
Router1 ipv6 address [Link]/64
ip router isis
Ethernet-2
ipv6 router isis
isis ipv6 metric 20
LAN2: [Link]/64
• The optional keyword transition may router isis
be used for transitioning existing IS- net 49.0000.0100.0000.0000.0500
metric-style wide
IS IPv6 single SPF mode to MT IS-IS. !
• Wide metric is mandated for Multi- address-family ipv6
multi-topology
Topology to work. exit-address-family

Presentation_ID 38
 Multi-Protocol BGP for IPv6 – RFC2545

• IPv6 specific extensions:

Scoped addresses: Next-hop contains a global IPv6 address and/or potentially a link-local address
NEXT_HOP and NLRI are expressed as IPv6 addresses and prefix.
Address Family Information (AFI) = 2 (IPv6)

Sub-AFI = 1 (NLRI is used for unicast)

Sub-AFI = 2 (NLRI is used for multicast
RPF check)
Sub-AFI = 3 (NLRI is used for both unicast and multicast RPF check)
Sub-AFI = 4 (label)

Presentation_ID 39
 A Simple MP-BGP Session
Router2
Router1

AS 65001 AS 65002
[Link] [Link]

Router1#
interface Ethernet0
ipv6 address [Link]/64
!
router bgp 65001
bgp router-id [Link]
no bgp default ipv4-unicast
neighbor [Link] remote-as 65002
address-family ipv6
neighbor [Link] activate
neighbor [Link] prefix-list bgp65002in in
neighbor [Link] prefix-list bgp65002out out
exit-address-family

Presentation_ID 40
 IPv4 versus IPv6 Multicast

IP Service IPv4 Solution IPv6 Solution

Address Range 32-bit, class D 128-bit

Protocol Independent
Protocol Independent
Routing All IGPs,and BGP4+
All IGPs,and BGP4+
with v6 mcast SAFI

Forwarding PIM-DM, PIM-SM, PIM-SM, PIM-SSM,

PIM-SSM, PIM-bidir PIM-bidir
Group
IGMPv1, v2, v3 MLDv1, v2
Management

Boundary/Border Scope Identifier

Domain Control

MSDP across Single RP within

Interdomain Independent PIM Globally Shared
Solutions Domains Domains
Presentation_ID 41
 Multicast Listener Discover – MLD

• MLD is equivalent to IGMP in IPv4

• MLD messages are transported over ICMPv6
• Version number confusion:
MLDv1 corresponds to IGMPv2
RFC 2710
MLDv2 corresponds to IGMPv3, needed for SSM
[Link]
• MLD snooping
[Link]
• CGMP for v6 under consideration

Presentation_ID 42
 IP Routing for Multicast

• RPF based on reachability to v6 source same as

with v4 multicast
• RPF still protocol independent:
Static routes, mroutes
Unicast RIB: BGP, ISIS, OSPF, EIGRP, RIP, etc
Multi-protocol BGP (mBGP)
- support for v6 mcast sub-address family
- provide translate function for non-supporting peers

Presentation_ID 43
 IP Routing for Multicast

RPF Route Selction Rules:

I. look up the longest mask route from the available route sources:
1. static mroutes.
2. MBGP RIB,
3. unicast RIB,

[Link] more than one of these three sources returns a route with the same
longest mask then select amongst these routes the one with the lowest
(= best) distance.

III. If the distance is equal on multiple entries:

Select static mroute over MBGP over unicast RIB

Presentation_ID 44
 IPv6 Multicast Forwarding

• PIM-Sparse Mode (PIM-SM)

[Link],
• PIM-Source Specific Mode (PIM-SSM)
[Link] (v6 SSM needs MLDv2)
unicast prefix based multicast addresses ff30::/12
-> SSM range is ff3X::/32
-> current allocation is from ff3X::/96
• PIM-bidirectional Mode (PIM-bidir)
[Link]

Presentation_ID 45
 RP mapping mechanisms for PIM-SM

• Static RP assignment
• BSR
• Auto-RP – no current draft

Presentation_ID 46
 Domain Control

• Definitions:
–A PIM domain is topology served by common RP for all
sources and receivers of same group.
–A routing domain is consistent with AS.

• Its necessary to constrain the PIM messages, rp-

mappings, and data for groups within the PIM
domain:
–In IPv4 we used multicast boundary/ BSR border
–In IPv6 we use scopes and zones

Presentation_ID 47
 IPv6 Scoping support

• Scopes: [Link]
Example scopes:
link-local (2)
site-local (5)
global (E or 14)
• Zone is a connected region of topology of a given scope
• Initial implementation similar to v4 boundaries:
– Can configure interface with zone and scope
ipv6 zone <zoneid> scope <2-15> CAUTION: This is
still being worked.
– PIM messages and data traffic within that scope are ignored on that interface
– Initially a zone can only contain one interface

Presentation_ID 48
 IPv6 Multicast Inter-domain Options
SSM, no RPs

R S
DR

ASM across multiple separate PIM domains, each with RP, MSDP peering

R S
DR RP RP RP

ASM across single shared PIM domain, one RP

R S
DR CE1

Presentation_ID 49
 Configuring Cisco IOS IPv6 Multicast

Group mode determines how to forward, compared to

interface mode in v4.
By default all interfaces are PIM enabled unless
explicitly disabled.
Config for PIM-SSM: Config for PIM-SM:
! !
ipv6 multicast-routing ipv6 multicast-routing
! ipv6 pim rp-address <v6_address>
!

Config for PIM-bidir: Disable PIM on an interface

! !
ipv6 multicast-routing interface ethernet 0
ipv6 pim rp-address <v6-address> bidir no ipv6 pim
! !
Presentation_ID 50
 Overview of Mobile IPv6 Functionality

CN

4. 3.

HA

1. 2.
MN
• 1. MN obtains Local IP address using stateless or stateful
autoconfiguration – Neighbor Discovery
• 2. MN registers with HA by sending a Binding Update
• 3. HA intercepts traffic for registered MN and tunnels
packets from CN to MN
• 4. MN sends packets from CN directly or via HA using Tunnel
Presentation_ID 51
 Route Optimization
Correspondent
Home Host
Agent

CN to MN

Mobile
Node

• Traffic is routed directly from the CN to the MN

• Binding Update SHOULD be part of every IPv6 node
implementation
• IPv4 also has route optimization but CN needs enhanced IP
stack and Key management is a problem
• Security Issues –
Shared Key or PKI Problem and We need a Scalable Solution
Presentation_ID 52
 Cisco IOS Mobile IPv6 Home Agent
Technology Preview
• MIPv6 Home Agent Technology Preview release built on
MP3 client IETF MIPv6 draft 20
• Initial release was ID-13
AP2
• Available on Cisco 2600, 3600, 3700 and 7200 series
• Adding DAD and DHAD
• IPsec support planned for a later stage
• waiting for IETF MIPv6 WG completion
Ethernet-2 • Binding update can be filtered by source address
using ACL
• Only available for testing and experiment
Ethernet-1 Tested with BSD, Linux and Windows MIPv6 client

Router1# ipv6 unicast-routing

Router1# ipv6 mobile
Router1# interface ethernet-1
ipv6 address [Link]/64
AP1 ipv6 mobile home-agent enable
Router1# interface ethernet-2
ipv6 address [Link]/64
ipv6 mobile home-agent enable

Presentation_ID 53
 IPv6 Security

• IPsec standards apply to both IPv4 and IPv6

• All implementations required to support authentication and
encryption headers (“IPsec”)
• Authentication separate from encryption for use
in situations where encryption is prohibited or prohibitively
expensive
• Key distribution protocols are not yet defined (independent
of IP v4/v6)
• Support for manual key configuration required

Presentation_ID 54
 IP Quality of Service Reminder

Two basic approaches developed by IETF:

• “Integrated Service” (int-serv)
fine-grain (per-flow), quantitative promises (e.g., x bits per second),
uses RSVP signaling
• “Differentiated Service” (diff-serv)
coarse-grain (per-class), qualitative promises (e.g., higher priority), no
explicit signaling
Signaled diff-serv (RFC 2998)
– uses RSVP for signaling with course-grained qualitative aggregate markings
– allows for policy control without requiring per-router state overhead

Presentation_ID 55
 IPv6 Support for Int-Serv

• 20-bit Flow Label field to identify specific flows

needing special QoS
– each source chooses its own Flow Label values; routers
use Source Addr + Flow Label to identify distinct flows
– Flow Label value of 0 used when no special QoS requested
(the common case today)
• This part of IPv6 is not standardized yet, and may well
change semantics in the future
[Link]
[Link]

Presentation_ID 56
 IPv6 Support for Diff-Serv

• 8-bit Traffic Class field to identify specific

classes of packets needing special QoS
– same as new definition of IPv4 Type-of-
Service byte
– may be initialized by source or by router
enroute; may be rewritten by routers enroute
– traffic Class value of 0 used when no special
QoS requested (the common case today)

Presentation_ID 57
 IPv6 and DNS

IPv4 IPv6

Hostname to A record: AAAA record:

IP address [Link]. A [Link] [Link] AAAA [Link]

PTR record: PTR record:

IP address to [Link].[Link]. PTR [Link].[Link].[Link].[Link].[Link].8.1.c.0.
hostname [Link]. [Link] PTR [Link].

Presentation_ID 58
 IPv6 Technology Scope

IP Service IPv4 Solution IPv6 Solution

32-bit, Network 128-bit, Multiple
Addressing Range
Address Translation Scopes
Serverless,
Autoconfiguration DHCP
Reconfiguration, DHCP

Security IPSec IPSec Mandated,

works End-to-End

Mobility Mobile IP Mobile IP with Direct

Routing
Differentiated Service, Differentiated Service,
Quality-of-Service
Integrated Service Integrated Service

IP Multicast IGMP/PIM/Multicast MLD/PIM/Multicast

BGP BGP,Scope Identifier

Presentation_ID 59
 IPv6 Standards

• Core IPv6 specifications are IETF Draft Standards =>

well-tested & stable
currently have 5 Draft Standards, 32 Proposed
started to compile an IPv6 Node Requirements spec
• Some important auxilliary standards are less mature
e.g., mobile IPv6, MIBS, scoped addressing,…
for an up-to-date status: [Link]/ipv6
• 3GPP UMTS Rel. 5 cellular wireless standards
mandate IPv6; also being considered by 3GPP2

Presentation_ID 60
 IPv6 Current Status - Standardisation

• Several key components now on Standards Track:

Specification (RFC2460) Neighbour Discovery (RFC2461)
ICMPv6 (RFC2463) IPv6 Addresses (RFC2373/4/5)
RIP (RFC2080) BGP (RFC2545)
IGMPv6 (RFC2710) OSPF (RFC2740)
Router Alert (RFC2711) Jumbograms (RFC2675)
Autoconfiguration (RFC2462)

IPv6 over: PPP (RFC2023) Ethernet (RFC2464)

FDDI (RFC2467) Token Ring (RFC2470)
NBMA(RFC2491) ATM (RFC2492)
Frame Relay (RFC2590) ARCnet (RFC2549)
Presentation_ID 61
 Prioritizing IETF IPv6 WG Work

(1) Finishing work-in-progress:

Default address selection
Address architecture
Basic & advanced APIs
ICMPv6 update
Router preferences
Cellular hosts requirements
Node information queries
DAD fixes to privacy address, autoconf and/or
address architecture
(2) Important and urgent for deployment:
DNS discovery
Prefix delegation
IPv6 MIBs

Presentation_ID 62
 Prioritizing IPv6 WG Work (cont.)

(3) Important but not quite so urgent:

Flow label specification
Scoped address architecture
IPv6-over-3GPP-PDP-contexts spec
IPv6 node requirements
(4) important but perhaps better handled in other WGs:
secure, robust plug-and-play
multi-link subnet specification
anycast architecture
routing protocol updates to handle IPv6 scoping
(5) important and already handled in other WGs:
site multihoming
IPv4 coexistence / interoperability / transition
DHCPv6
mobile IPv6

Presentation_ID 63
 Status of Other IPv6-Related WG in the IETF

• NGtrans (Next Generation Transition)

Major reorganization, moving from “tool development” to “IPv6
network operation”
• v6Ops
• DHCP (dynamic host configuration)
DHCPv6 spec very close to Proposed Standard (at last!)
• Multi6 (multihoming for IPv6)
Little progress
• Mobile IP
Binding-update authentication issue of mobile IPv6 resolved;
expect Proposed Standard soon(?)

Presentation_ID 64
 Questions?

Presentation_ID 65
 More Information

• CCO IPv6 - [Link]

• The ABC of IPv6
[Link]
[Link]
• IPv6 e-Learning [requires CCO username/password]
[Link]
• IPv6 Access Services :
[Link]
• ICMPv6 Packet Types and Codes TechNote:
[Link]
• Cisco IOS IPv6 Product Manager – pgrosset@[Link]

Presentation_ID 66
Presentation_ID © 1999, Cisco Systems, Inc. [Link] 67
© 2001, Cisco Systems, Inc. 68