IPv6 For Decision MakersThis is an opportunity, not a headache!

Who is Talking?

• Worked on some of the largest IPv6 deployments in the World

• Two Cisco Press IPv6 books• Multiple IPv6 RFCs and patents• IPv6 Forum Fellow, Gold certified trainer

and engineer

2

Afternoon SessionTarget Audience: First Line Managers, Technology Leads and Project Managers

Agenda

Executive Perspective• Why IPv6

• IPv6 Myths and Reality

• Global Market Overview and Adoption Updates

• IPv6 Strategic Opportunities

• IPv6 Risks

• IPv6 Impact on Technology, Processes and People

• Driving IPv6 Integration within the Organization

• Minimizing IPv6 Integration Costs

• Measuring User Experience (UX)

Technology Manager Perspective• IPv6 Protocol Overview

• IPv6 Addressing and Address Planning

• Host Provisioning options

• IPv6 Integration Strategies

• Choosing an IPv6 Integration Strategy

• IPv6 Integration Planning

• IPv6 Integration Execution

• IPv6 Operations Considerations

4

Session Goals

• Become familiar with the key aspects of the technology• Learn the benefits of IPv6 addressing and how to plan it• Understand the deployment and operational considerations• Get the information needed to plan an effective integration

5

IPv6 Protocol OverviewA Review of the Key Concepts

The Fundamentals

• IPv6 upgrades IPv4, the current version of the Internet Protocol• IPv6 is an evolution not a revolution of the Internet Protocol• Developed primarily to deal with IP address space exhaustion• IPv6 incorporates the lessons learned from operating IPv4• IPv6 and IPv4 are not compatible so the transition will require

special approaches

7

History

• Next generation Internet Protocol• Development started in 1993, standardized in 1995, updated in

1998. • Goals of development for the protocol:

- Address issue of IPv4 address exhaustion- Update based upon experience with IPv4- Improve efficiency, streamline, and enhance scalability

IPv6 became an Internet Standard on July 14, 2017.8

IPv6 – IPv4 Comparison

Protocol Aspect

32-bit, Network Address Translation

128-bit, Multiple Scopes

Address Range

IPv4 IPv6

ICMPICMP ICMPv6, PMTU

DHCPProvisioning SLAAC, DHCP-PD, DHCPv6, RDDNS

RIPv2, OSPFv2, ISIS, MP-BGP, EIGRPRouting RIPng, OSPFv3,

ISIS-ST/MT, MP-BGP, EIGRPv6

9

IPv6 – IPv4 Comparison (cont.)

Protocol Aspect

IGMP/PIM/Multicast BGP

MLDP/PIM/Multicast BGP, Scope Identifier

IP Multicast

IPv4 IPv6

Differentiated ServiceIntegrated Service

Quality of Services DiffServ, Integrated Service, Flow

IPSecSecurity Mandated IPSec

Mobile IPMobility MIP + Direct Routing

10

IPv6 Packet

Learning from the experience11

IPv6 Headers

• IPv6 introduces “the Extension Header”• EH allows a packet to carry “meta data”• They are considered payload• You daisy-chain multiple EHs

Extension Headers make IPv6 easier to adapt and extend12

ICMP

• IPv4 uses ICMP for control & troubleshooting• IPv6 uses ICMPv6 for the same functions (NH = 58)

- Echo request, reply

- Time Exceeded & Unreachable messages

- Parameter Problem

- Redirects

• Plus many more:- Packet Too Big (Path MTU Discovery)

- Neighbor and Router Discovery

- Multicast13

ICMP – Provisioning

• StateLess Address AutoConfiguration, heritage of old protocols• It enables devices to autoprovision without having to be too

smart or expensive• The devices can also learn about resources needed for

operation• The mechanism is useful for certain parts of the IT environment

and not for others.

14

DHCP – Provisioning

• Stateful DHCPv6 similar to IPv4• Stateless DHCPv6 complements Stateless Address Auto

Configuration • DHCPv6 Prefix Delegation is available only for IPv6• The protocol was redesigned from the ground up in a more

clean, scalable way

15

Routing (IGP)

• Many similarities but fundamental differences too• Coexistence is very important• Standards drive towards IPv6 convergence

RIPRIPv2 for IPv4RIPng for IPv6Distinct but similar with RIPng, taking advantage of IPv6 specificities

OSPFOSPFv2 for IPv4OSPFv3 for IPv6Distinct but similar with OSPFv3, cleaner implementation taking advantage of IPv6 specificities

IS-ISExtended to support IPv6Natural fit to some of the IPv6 foundational conceptsSupports Single and Multi Topology operation

EIGRP Extended to support IPv6Some changes reflecting IPv6 characteristics

16

MulticastService IPv4 Solution IPv6 Solution

Addressing Range 32-bit, Class D 128-bit (112-bit Group)

Routing Protocol Independent, All IGPs and MBGP

Protocol Independent, All IGPs and MBGP with v6 mcast SAFI

ForwardingPIM-DM, PIM-SM,

PIM-SSM, PIM-bidir, PIM-BSR

PIM-SM, PIM-SSM, PIM-bidir, PIM-BSR

Group Management IGMPv1, v2, v3 MLDv1, v2

Domain Control Boundary, Border Scope Identifier

Interdomain Solutions MSDP Across Independent PIM Domains

Single RP Within Globally Shared Domains

17

Security

• On average, IPv6 is as secure/unsecure as IPv4• Shortcomings are primarily due to product limitations and lack

of expertise or awareness• New security architecture concepts must be implemented for

IPv6• As an overlay to the existing infrastructure, IPv6 can lower the

security posture of the environment if not properly addressed early on

18

Security (cont.)

• Vulnerabilities similar to IPv4• Vulnerabilities specific to IPv6• Vulnerabilities introduced by the transition process

IPv4 Vulnerabilities IPv6 Vulnerabilities

19

Key Takeaways

• IPv6 is a full Internet Protocol and the plan of record for IT• IPv6 was developed to deal with address shortage • IPv6 was developed based on the experience gained with IPv4• IPv6 is an evolution not a revolution of IP• IPv6 is similar to IPv4 but has many important and subtle

differences

20

IPv6 Addressing and Address PlanningA Lot is Possible with Plenty of Resources

Architecture

• Quantitative dimension – A lot more IP addresses• Qualitative dimension – Addresses have a meaning clearly

represented in their structure• Addresses have two components:

- Prefix ID – the equivalent of Network in IPv4- Interface ID – the equivalent of Host ID in IPv4

• Eliminate broadcast and rely more heavily on Multicast• More prescriptive in defining and using special/reserved addresses• An interface can have multiple addresses

22

Quantitative Perspective

• IPv4 – 32 bits address~4.3 billion addresses (4,294,967,296)

• IPv6 - 128 bits address~340 undecillion addresses(340,282,366,920,938,463,463,374,607,431,768,211,456)

A lot of IP addresses!23

IPv6 Address Format

24

Qualitative Perspective

• IPv6 addresses have a meaning• The address scope identifies the domain to which the packet is

relevant: Link, Organization, Global• IPv6 addresses have three unicast scopes defined

- Link-Local – Relevant only within the directly connected link (FE80::)

- Site-Local Unique-Local – Relevant only within an administrative domain (FD00:: and FC00::)

- Global – Relevant globally (routable across the Internet) and managed by IANA and registries (2000::/3)

• The same three scopes are identified for multicast traffic (FFxy::)25

IPv6 Address Space Allocation

Provider Allocated Provider Independent

26

IPv6 Address ExampleC:\>ipconfig

<snip>Ethernet adapter LAN:

Connection-specific DNS Suffix . : lanIPv6 Address: 2001:55c:62da:a1f4:910b:3654:666e:3945 <- Global UnicastTemporary IPv6 Address: 2001:55c:62da:a1f4:aca1:cb:96f2:81e <- “Temporary”Link-local IPv6 Address: fe80::910b:3654:666e:3945%1 <- Link LocalIPv4 Address. . . . . . . . . . . : 192.168.1.123Subnet Mask . . . . . . . . . . . : 255.255.255.0Default Gateway . . . . . . . . . : 192.168.1.1

C:\>netsh inter ipv6 show join<snip>

Interface 10: LANScope References Last Address---------- ---------- ---- ---------------------------------0 0 Yes ff01::10 0 Yes ff02::1 <- All-nodes Mcast0 3 Yes ff02::c0 1 Yes ff02::1:30 2 Yes ff02::1:ff6e:3945 <- SNMA0 1 Yes ff02::1:fff2:81e <- SNMA

27

Implications of a Large IP Address Space

• A cleaner address architecture• Address plans are focused on network addresses not host

addresses• Address plans simpler, more scalable• The room to embed information in address leading to easier

policies and operations• Multicast is easier to deploy

Take full advantage of the large address space!28

Slicing and Dicing an IPv6 Address

2001:0DB8:0000:0000:0085:0802:0000:0004

Interface Identifier (IID)Prefix

• Your address plan deals primarily with the Prefix bits• Acquire as much address space as your environment needs to

build meaningful prefixes• Establish the rules for the IID

29

Two Competing Views for Your Address Plan

:0DB8:0000:0000:

Prefix

Policy Network ArchitectSecurity Architect

Location Network EngineerOperations Engineer

High Order Bits

What is easier to manage, policies or routes?30

IPv6 Address Plan Design

• How important is readability? Nibble boundaries• Is consistency important? Worry less about wastage • Leave room for growth? Sparse allocation• Can there be too much of a good thing? Watch out for too much

slicing, particularly for high order bits

31

IPv6 Address Planning Best Practices

• Start early because you need to build YOUR address plan• Take the opportunity to get input from various teams• Create a core team and a broad team to work on addressing• Start with the address plan and then acquire the space that fits• Be bold and think outside the IPv4 constraints• Drive simplicity rather than conservation• Expect at least 2-3 iterations

32

Key Takeaways

• IPv6’s most apparent and impactful benefit is the availability of plenty IP addresses

• IPv6 address architecture has both a quantitative and a qualitative dimension

• IPv6 addresses carry a lot of information, use this feature• Start early building your IPv6 address plan and iterate• Take advantage of this opportunity to create a new foundation

for your network

33

Host Provisioning OptionsIP Address, Gateway and DNS

IP Host Provisioning

• Definition: Becoming a reachable and responsive end-point in an IP network

• Key elements for IP host provisioning:- Network and Host IP address- Network Gateway - Domain Name Server

35

IPv4 Host Provisioning Mechanisms

DHCP

Function Options + -

IP AddressManual Configuration

DHCPv4

Control

Device mgmt

Not scalable

Maintain state

GatewayManual Configuration

DHCPv4

Control

Device mgmt

Not scalable

DNS DNS Service

36

IPv6 Host Provisioning Mechanisms

Function Options + -

IP Address

Manual Configuration

Statefull DHCPv6

SLAAC

Control

Device mgmt

Simpler stacks

Not scalable

Maintain state

Other integration

Gateway

Manual Configuration

Stateful DHCPv6

SLAAC

Control

Device mgmt

Simpler stacks

Not scalable

Maintain state

DNS

DNS Service

Stateless DHCPv6

RDNSS Inconsistency 37

SLAAC (RFC 4862)

Type = 133 (RA) Code = 0 Checksum

Reachable Time

IPv6 Base Header (40 bytes) (NH = 58 = ICMPv6)

Router Lifetime

Options (Example = Source Link-Layer Address)

Cur Hop Limit M O Reserved

Retrans Time

Type = 3 (PIO) Length = 4

Valid Lifetime

Prefix

Preferred Lifetime

Prefix Len L A Reserved

Reserved

38

DHCPv6 (RFC 8415)

• Cleaner version of DHCP• New functionality for IPv6• Modes of operation:

- Stateful- Stateless- DHCP-PD

39

RDNSS (RFC 8106)

Type Length Reserved

Lifetime

Addresses of IPv6 Recursive DNS Servers

Type Length Reserved

Lifetime

Domain Names of DNS Search List

Recursive DNS Server Option

DNS Search List Option

40

Signaling

Flags Operation

M=0, O=0, A=1 IPv6 address from router using SLAAC

M=0, O=1, A=1 IPv6 address from router using SLAAC and optional info from DHCPv6 server using DHCPv6 Stateless

M=1, O=0 IPv6 address and optional info from DHCPv6 server using DHCPv6 Stateful

M=1, O=1, A=1 IPv6 address and optional info from DHCPv6 server using DHCPv6 Stateful and address from router if available

41

IPv6 Host Provisioning Debate

• A matter of principle• A matter of vision• A matter of “I can do that”

42

Key Takeaways

• With IPv6 you get more provisioning options• Can simplify operations or implement new provisioning

processes for specific services• OS support of all options is mostly consistent with one

exception• The debate continues!

43

IPv6 Integration StrategiesFrom Proof Of Concept to Trial to Production

Tool Box

• These mechanisms are useful/necessary because IPv6 and IPv4 are not interoperable

• Three general mechanisms for providing access to IPv6 hosts have been defined:- Native IPv6 access in dual-stack mode- Tunneled access between insular hosts or domains- Translation to IPv6 or IPv4 only hosts

• All these mechanisms generate operational overheadThe right transition mechanism must be used for the right part of

the environment and at the right time during the integration.45

Dual-Stack

• The same interface of a host has both IPv4 and IPv6 stacks operating at the same time

• Native connectivity over IPv6• Deployed in parallel with IPv4, the two protocols operate as

ships in the night• Protocols are selected based on available reachability

information• IPv6 is preferred over IPv4 by standardization but the OS or

application is ultimately making the decisionThis is the preferred deployment tool.

46

Tunneling

• IPv6 is inside an IPv4 packet or an MPLS frame• Interconnects IPv6 islands or a disperse population of hosts

over an IPv4 or MPLS infrastructure• There are several tunnel types such as:

- Manual (GRE, Protocol 41, UDP)- Dynamic (ISATAP, Teredo, 6rd, 6to4, DMVPN)- MPLS (6PE, 6VPE)

• Others have been defined but fell out of use

Generates significant overlays, adds complexity.47

Translation

• Traffic is translated between IPv4 and IPv6 stacks• Sits between IPv4 and IPv6 domains• There are two general approaches:

- Translate the IP packets - Proxy between the two stacks, the payload is processed above layer three and sent over the other stack

• Performance taxing and scalability constraining

Valuable tool if not overused.48

Pros and Cons

Right tool for the right problem at the right time

Tools Pros Cons

Dual-Stack Optimal approach with full control on delivery, performance and operations

All elements involved must support IPv6 at production level

Tunneling

An option for staging the enablement and managing the process of infrastructure refreshGood option for IPv6 over MPLS

Impact on performanceImpact on scalabilityComplicates operations

Translation

Easy solution for enabling web based applicationsGood for managing legacyWorkaround for product gaps

Impact on performanceImpact on scalabilityComplicates operations

49

Key Takeaways

• Lack of backwards compatibility is both good and bad• Multiple tools available to address various scenarios during the

enablement, integration and transition process• The preferred approach is dual-stack, then translation and

finally tunneling• The operational complexity of the network will increase during

the enablement and integration of IPv6• Many organizations consider going to IPv6 only asap.

50

Choosing an IPv6 Integration Strategy Always Aligned with the Organization Specific Needs, Environment and Timeline

The success and effectiveness of the IPv6 integration is mostly dependent on driving good, consistent habits.

Integration Strategy

Discovery:• Vision & Strategy• Opportunities & Risks• Drivers & Priorities• Timeline & Metrics

IPv6 Project

Resources

Goals

Timeline

53

Terminology

• IPv6 Prepared: I could support IPv6• IPv6 Ready: I can turn IPv6 on any time• IPv6 Enabled: I turned IPv6 on

You will achieve these stages at various points during execution.

54

Integration Strategy

55

Integration Strategy (cont.)

1. Prepare the organization for IPv62. Drive IPv6 readiness to facilitate deployment according to

timeline3. Enable IPv6 according to priorities

56

Integration Strategy (cont.)

In the absence of a flag day you must organize integration around priorities and metrics

Infrastructure Domains Services Users

• Access

• Backbone

• DC

• Internet Edge

• External Web

• SaaS Apps

• Internal Apps

• Partner

• External

• Researchers

• Students

• Staff57

Domain Pros Cons

Internet EdgeConfined domainEasy to implementEasy to show progress

Tempting to just do translation and not progress

Access WiFiA good way to start trials within SSIDsA good way to learn about running full stack services

BYOD impacts current choicesDual-stack is the only optionTunneling or separate transport over backbone

Access WiredA good way to start trials within VLANsA good way to learn about running full stack services

BYOD impacts current choicesAccess managementTunneling or separate transport over backbone

Insular Domain Fully controlledRequires less operational readiness

Requires select staff to support the domain

BackboneIn full control of the domainNot gated by infrastructure servicesGood way to trial operations

Failures have significant impact

Infrastructure Domains

58

Services

Domain Pros Cons

Outbound Services Easy to implementEasy to show progress Failures are very visible

SaaS ServicesShow how things will workFocus only on transportPractice dual-stack access

Requires access all the way to end usersRequires operational readiness including Internet Access

Contained ServicesEasier to manage and controlGood way to practice operationsCan be deployed IPv6 only proper support

Requires full IPv6 support by the infrastructure and operations

Internal Services Does not Internet facing security enforcement

Requires full, operational IPv6 enablement and support

59

Users

Domain Pros Cons

External Brand managementEasier to implement Failure can be very visible

SpecializedFully controlledLimited scope and requirementsSmall impact to the overall environment

Requires dedicated staff and resourcesHigh visibility domains are a risk

Internal ContainedFully controlledGood way to practice operationsCan be deployed IPv6 only proper support

High priority service failure are highly visible

60

Steps

Test Trial Stage Production

61

Key Takeaways

• The IPv6 integration strategy is organization specific• Understand the opportunities and risk as aligned with the Next

Generation Networks• Prepare for IPv6, drive IPv6 readiness and start enabling• Combine the approach and tools combinations that fit your

environment, show progress, minimizes negative impact and helps the organization increase readiness.

62

IPv6 Integration PlanningPlans are Made to be Changed

IPv6 and You

IPv6 is an organization specific value proposition

That means:• Specific drivers• Specific priorities• Specific timeline

64

IPv6 Deployment – Methodology

Plan for the Next Generation environment, not for IPv6.65

IPv6 Deployment – Alignment

Align strategies, leverage and protect investments.66

IPv6 Deployment – Environment

Address all aspects of the IT environment impacted by IPv6.67

IPv6 Deployment – Ecosystem

Manage the entire ecosystem.68

High-Level Roadmap

H1 2019

H2 2019

H1 2020

H2 2020

69

Planning

• Have an organization level IPv6 plan encompassing all tracks driven through independent projects

• Leverage all existing lifecycles and partner management processes to drive IPv6 readiness of products, service and partners

• Drive readiness through every project which typically means at most an additional cost of 5% per project

• Update all operational processes to support IPv6 and maintain consistency of IPv6 support

• Expect and plan for an iterative process.70

Planning (cont.)

• Start early to give your organization time to learn, align and save money

• Create an IPv6 Enablement office• Build clear targets and metrics• Implement gates to ensure IPv6 progress across all projects• Provide continuous messaging upwards and downwards on the

progress of the project.

71

IPv6 Enablement Office

72

Planning – First Activities

1. Develop the initial roadmap aligned with the strategic goals of the organization and the metrics agreed on with the leadership

2. Develop the education plan and start education as soon as possible

3. Initial update of procurement and vendor management policies4. Initiate project assessment5. Perform a security policies review6. Start the Address Plan development process.

73

Planning – Roadmap

74

Planning – Education & Guidance

75

Program Introduction

Program Introduction

Education Education & Guidance Deployment & Integration

Leadership

Implementors

Operations

IT Leadership Class

IPv6 Network Technical Training

IPv6 Host OS Technical Training

IPv6 Host OS Technical Training

IPv6 Help Desk Training

IPv6 Address Planning

IPv6 Support Activities

Assessment Meetings

Assessment Meetings

Product Specific Training

Platform Specific Training

IPv6 Support Activities

Planning – Processes

76

Planning – Suppliers

77

Planning – Project Assessment

78

Key Takeaways

• You should create a plan as soon as possible and expect it to change

• A transition office is critical to orchestrating all projects• It is very important to agree upon metrics, track and report on

them regularly• Start training and processes updates as soon as possible.

79

IPv6 Integration ExecutionA Continuous Process Aligned with the Plans of the Organization

Considerations

• Typically no or very limited funding• Management will expect results and progress but will be likely

to de-prioritize IPv6 if it is raised as a slowdown factor• Requires significant collaboration and coordination• IPv6 will be blamed for ANY issue that pops up

81

M3

Minimize Negative Impact•Security•Performance

Maximize Benefits•Good IP Address Plan•Good Target Architecture

Minimize Cost•IT Project Readiness•Vendor and Partner Management

82

Metrics

• You cannot manage something you do not measure• The nature of the IPv6 project makes metrics particularly

important• Metrics and KPIs must be agreed upon with the leadership• Metrics reporting is essential to maintaining project support

and execution consistency• Metrics and KPIs must apply to all stages: Prepare, Ready,

Enable.

83

Metrics ExamplesMetric Description

Percentage of Infrastructure Track the percentage of the infrastructure (prepared, ready, enabled). Shows progress of the enablement

Number of Users Number and types of users enabled for IPv6. Shows impact

Number of Services Number, types and priority of services enabled for IPv6. Shows impact

Projects Special projects enabled by or for IPv6. Shows expertise

Performance Performance (such as response times) over IPv6 vs IPv4. Shows quality of integration

Issues Number and priority of IPv6 related issues vs IPv4. Shows quality of integration and readiness of operations

84

Assessment – Everyone Says They Are Ready

• Equipment and Tools: Use industry standards but build your own profiles based on your target architecture. Do not assume it is consistent through subsequent releases

• Services and Providers: Secure explicit support statements for capabilities, processes and support. Test claims

• Security: Avoid generic assessment, evaluate against the specific needs of your organization

• Performance: Baseline!

85

Assessment – Standards

Functional Requirements

IPv6 Standards Profile

IETF Standards

• Organization Strategy

• Industry Best Practices

• Protocol Evolution

86

Baselining

Similar to any major technology integration or service deployment, it is critical to understand the value delivered and the business impact

The reasonable approach is:• Baseline the key metrics with IPv4• Monitor the IPv4 baseline while enabling IPv6• Baseline the key metrics with IPv6

The truly meaningful metric for IPv6 deployment is UX.87

Integration

Test Trial Stage Production

Testing is less necessaryTrials are important

Depends on organization

Remember you can always count on IPv4 for backup88

Messaging

• The IPv6 project easily falls out of sight and out sight and out of mind leading to gaps in execution and diminished management support

• The success of the project depends on continued, consistent and metric based communication with the leadership and all those involved

• The commitment of the organization to IPv6 must be constantly reinforced by management until most processes are updated to support the IPv6 integration and IPv6 based operations.

89

Messaging (cont.)

CEO

CIO

Executive Sponsor

Projects Leads

Grass Roots IPv6

Maintaining Support

Messaging Internally

Messaging Externally

90

Baselining (cont.)

Instrument Environment

Baseline Services and Network over IPv4

Monitor IPv4 during IPv6 deployment

Baseline Services and Network over IPv6 Monitor Optimize

Continuously Report on IPv6 Metrics

Metrics:

User Experience

APDEX

Uptime, Latency, Drops, etc

91

Key Takeaways

• Maximize the opportunity, Minimize Impact, Minimize Cost• Define, track and report clear metrics and KPIs• Baseline the environment prior, during and after integration• Communicate extensively with decision makers and

stakeholders.

92

IPv6 Operations ConsiderationsDuring the Enablement and Post Enablement

Operations Considerations

• Operations will possibly get involved at all stages of the IPv6 project

• IPv6 integration will add complexity to the environment• Due to the fact that users and applications now have access

options (IPv4/IPv6) they are not aware off there are more possible causes of issues

• IPv6 expertise is not readily available across domains.

94

It Gets Harder Before it Gets Easier

Credit @Network World95

Readiness

• Do not make IPv6 operational readiness an afterthought of the integration process

• Create IPv6 leads within the operations teams• Align IPv6 education process with the integration milestones to

make sure the right level and amount of expertise is available within the operations team

• Involve the IPv6 operations leads in trials and special projects in order to gain experience and improve operational processes

• Leverage the community, it is the best and least expensive way to get ready.

96

Key Takeaways

• IPv6 adds complexity to all aspects of IT operations: People, Technology, Process

• Plan for increased operational costs during the deployment and co-existence stages of the IPv6 integration

• Gradually develop the expertise and experience of the operations team, do not throw them in the deep-end of the pool overnight

• This is a great opportunity to learn with and from others. Leverage the Merit community.

97

Session Takeaways

• IPv6 is an evolution of the Internet Protocol• IPv6 deployment touches every aspect of IT: People,

Technology, Process• IPv6 enablement is a once in a career opportunity to build the

next generation IT infrastructure• IPv6 enablement does not have to be expensive but it has to

start early and driven as an organization wide effort• Metrics, metrics, metrics• Start planning today with the help of the Merit IPv6 Program!

98

The IPv6 Program

chip@nephos6.com

Glossary• 6PE – IPv6 Provider Edge

• 6rd – IPv6 Rapid Deployment

• 6VPE – IPv6 VPN Provider Edge

• BGP – Border Gateway Protocol

• BYOD – Bring Your Own Device

• DC – Data Center

• DHCP – Dynamic Host Configuration Protocol

• DDI – DHCP, DNS, IPAM

• DMVPN – Dynamic Multipoint VPN

• DNS – Domain Name Service

• EA – Enterprise Architect

• IANA – Internet Assigned Numbers Authority

• ICMP – Internet Control Message Protocol

• IID – Interface Identifier

• IETF – Internet Engineering Task Force 101

• IPv4 – Internet Protocol version 4

• IPv6 – Internet Protocol version 6

• IoT – Internet of Things

• ISIS – Intermediate System to IS

• ISP – Internet Service Provider

• IT – Information Technology

• KPI – Key Performance Indicator

• NAT – Network Address Translation

• NH – Next Header

• NFV – Network Functions Virtualization

• PMTU – Path Max Transmission Unit

• OSPF – Open Shortest Path First

• POR – Plan of Record

• TCP – Transport Control Protocol

• RDNS – Recursive DNS

• RDNSS – Recursive DNS Server

• RIP – Routing Information Protocol

• RIR – Regional Internet Registry

• SDN – Software Defined Networks

• SLAAC – StateLess Address Auto Configuration

• SP – Service Provider

• SSID – Service Set Identifier

• UDP – User Datagram Protocol

• UX – User Experience

• ToS – type of Service

• TLS – Type Length Value

• TTL – Time To Live

• VLAN – Virtual Local Area Network

• VPN – Virtual Private Network

Expertise and Experience