1 Cisco Systems, Inc. All rights reserved. Unified Control Plane & IPv6 Mallik Tatipamula, Product...

1Cisco Systems, Inc. All rights reserved.

Unified Control Plane & IPv6

Mallik Tatipamula, Product Manager

Emerging Technologies, Internet Routing Group

[email protected]

Presentation_ID Cisco Systems, Inc. All rights reserved. 222

Agenda

• Unified Control Plane

• IPv6

• IPv6 services over GMPLS Backbone


Unified Control Plane



[email protected]


Agenda

• Introduction

• Service Provider Requirements

• UCP Definition and Strategy

• Discussion on O-UNI & GMPLS

• Q&A


Technology Trends

Lower Cost, Complexity, and OverheadLower Cost, Complexity, and OverheadLower Cost, Complexity, and Overhead

IPIP

ATMATM

OpticalOptical

B-ISDN IP overATM

IP overSONET/SDH

IPIP

OpticalOptical

IP overOptical

IPIP

SONET/SDHSONET/SDH

OpticalOptical

ATMATM

SONET/SDHSONET/SDH

IPIP

OpticalOptical

Multiplexing, Protection, and Management at Every LayerMultiplexing, Protection, and Management at Every Layer


IP+Optical Network View

Multi-ServiceTransport

Router/SwitchCore Router

DedicatedInternet Access

IP VPN

Frame Relay

TDM Private Line

Optical VPN

Metro Ethernet

Voice

Mobile Wireless

Cable Data

DSL

ATM

DialupInternet Access

Optical Private Line

Optical Core

Transport andMulti-Service Metro

Packet Core

Storage

Storage

Content

Packet Edge

Services

Core PacketTrunks

Metro PacketTrunks

OXC

CATV

Packet ServicesTDM, Wavelength, andFiber Services

Grooming

VoIP


Network Provisioning Problem: Today

• Distinct technology domains—Optical, IP, ATM

• Today integration occurs at the NML and above

• Vision: push network provisioning closer to the network

IP DCNCTMCGM

NMS

NC

UNI

N C

UNI

12000

Internet

DCN DCN

12000

X

W Z

Y

15454

B

A D

C

15454 ONE ONE

ONE

ONE

DCN

Core OTN

1200012000

N C

UNI

NC

UNI


Motivation for Customer Adoption of UCP

• Revenue Growth

New flexible and rapid service delivery

Fast Provisioning of Bandwidth

Bandwidth on Demand

• Operational Efficiency

Optimized/Simplified Architecture

New meshed restoration

Operational Simplification

Coordinated Protection & Restoration

• Cost Reduction

Reduced costs

Improved network efficiency

Reduced % operations overhead

• Enhanced multi-vendor Interoperability

Depreciation31%

G&A7%

Sales and Marketing

13%

OAM&P49%


IP+Optical

Integrated IP+Optical Intelligence: UCP Vision

• GMPLS-Based Standard NNI

• Single MPLS and GMPLS IP+Optical Control Plane

• Concurrent Peer and UNI Overlay Operation

• Topology Visibility for Coordinated Routing and Restoration

• Advanced Optical VPN Services

Client RouterMetro

Multi-ServiceOTN

MetroMulti-Service

OTN

Router Router

UNIUNI-N

NNI NNI

NNINNI

Management Plane

GMPLS Enabled Control Plane


Forwarding Plane

Building on Cisco’s IP Building on Cisco’s IP & MPLS Leadership& MPLS Leadership

Control Planebased on IP routing

IP

ATM

Optical

Services

Network and Service Management

Unified Control Plane

Intern

etwo

rking

Op

erating

S

ystem

Packet Labels/VPI VCI

Packets/Cells

Wavelength Routing

DWDM Transport

SONET/SDHLabels

UCP Definition and Strategy


IP+Optical Network Models

•Peer model IP and optical subnets treated

as a single integrated network

Seamless interconnection of IP and optical networks

OpticalSubnet

Packet services(Retail)

IP Subnet

Wavelength services(Wholesale)

•Overlay model Enables carriers to create

separation between transport and network layers

Control plane runs within each subnet

UNI

Benefits:Benefits:

1. Network simplification: common framework for packets and wavelengths

2. Reduced provisioning costs

3. Increased service velocity

4. Traffic Engineering

5. Coordinated Protection and Restoration

Optical Service Provider

ISP/iDC

Optical Core


Proposed Industry Models - Overlay Model

• Two Administrative Domains

Optical Transport Network (OTN)

Internet Service Provider (ISP)

• ISP requests circuits via a UNI interface

• OTN uses its own Control Plane for Provisioning

Optical Service Provider

ISP Data Control Plane

(MPLS)

LSREdge-LSR Edge-LSR

LSR

OTN OTN

* ISP . . . Internet Service Provider

UNI UNI


OIF O-UNI 1.0: Key Features

• O-UNI Signaling Actions / Message Types

Connection Creation, Deletion, Status Query

• Control Channel

In-fiber Line/Section DCC, Out-of-fiber signaling (ex: Ethernet)

• Neighbor Discovery (optional)

• Service Discovery (optional)

• Use of RSVP-TE and LMP procedures

• Policy and security considerations


Peer Model

• One Administrative Domain

• LSRs and OXC-LSR are Peers

• Common Control Plane for both L3 and OTN

Common Control Plane(GMPLS)

LSR LSREdge-LSREdge-LSR

OXC-LSR OXC-LSR


GMPLS Key Features

• GMPLS Full Peer model based on IETF drafts Control Channel – IF/IB, OF/OB Link Management –Control Channel Management, Component

Link Verification, Link Property Correlation (Port ID mapping), Link Bundling, Fault Isolation and management

RSVP extensions for GMPLS OSPF/ISIS extensions for GMPLS Route computation with optical constraints (protection, Framing

type, BW etc.,) Support for Packet, TDM (SONET/ SDH), Lambda and Fiber

labels LSP Hierarchy / Forwarding Adjacencies (FA) Support for Bi-directional LSP Support for Unnumbered links


GMPLS Key Features

Feature Name Priority

Border (Augmented) Model

O-UNI Management Agent

GMPLS Management Agent

Path Protection & Restoration

Multi-domain/ Multi-carrier model for GMPLS and O-UNI

Link bundling

MPLS LSR & LMP MIB

Computation of diverse and disjoint paths (SRLG)

O-UNI Client connection acceptance access list

GMPLS Multi-area support

Link Verification and Fault Isolation


Questions?


PS-5422988_05__c1


IPv6



[email protected]


Discussion Topics

• Introduction

• Market Drivers for IPv6

• Deployment architecture

• Addressing support and scale

• Performance

• Operational Deployment

• Feature Combinations

• Q&A


IPv6 @Cisco Systems

• Co-chair of IETF IPv6 WG and Ngtrans

• Well Known Cisco 6Bone router

• ‘Founding Member’ of the IPv6 Forum

• Official CCO IPv6 page is www.cisco.com/ipv6

Cisco IPv6 Statement of Direction published last June

Cisco IOS IPv6 EFT available for free for last 3 years

~around 500 sites running Worldwide

• Ready to deliver a commercial release of Cisco IOS IPv6

• Held IPv6 on TAG sessions in Paris and Tokyo: Sept. 2000


Key IPv6 Markets

• Service providers

Regional ISP, carriers, mobile ISPs, and Greenfield ISPs

• Academic National Research Networks

• Wireless

PDAs, 3G mobile phone networks, automobiles . . .

• Home networking

Set-top box/Cable/xDSL/Ether@Home

Residential Voice over IP gateway

• Gaming industry and consumer PCs

• Enterprises

IPv6 support in operating systems and applications


When

Commercial IPv6 routers available

IPv6 in most OS for developers IPv6 specified for 3G

Many IPv6 apps. available IPv6 Operationally Viable

Operational 3G Systems

IPv4 address exhaustion

IPv6 Timeline:

Time

IPv4

IPv6

Total

Vo

lum

e

2005 20151990

Early Deployments - CY-E-Japan Government Initiatives for IPv6 backbone deploymentsJapanese ISPs/SPs commercial service offeringsNRENs Offerings (Surfnet, SuperSINET etc.,)Mobile Wireless Service Providers trialsGPRS IPv6 based services offerings Source: IPv6 Forum


Market Drivers for IPv6 (1)

• Geographies Japanese Government Sponsored Programs

Commercial Services started in April,

EEC e-Europe document advertised IPv6 as the way to go for Europe

• Internet Ready Devices Cellular Phones, PDAs, Consumer Electronics, Home Networking, Automobile etc.

• 3GPP/3GPP2 supports IPv6 for 3G Wireless Networks


• Internet Growth (400%/year)

• Mobile Wireless Growth

400 million mobile phone users in 2000, over 1 billion by ; 1/3 of 1B should get connected

• ~1 Billion cars in 2010, 15% should get GPS and Yellow Page services

• Billion of new Internet appliances for Home users

Always-On

Source: Ericsson Radio Systems

Market Drivers for IPv6 (2)Market Drivers for IPv6 (2)

Need for Larger AddressNeed for Larger AddressSpaceSpace


IPv6 Deployment Scenarios

• Many ways to deliver IPv6 services to End Users

End-to-end IPv6 traffic forwarding is the Key feature

Minimize operational upgrade costs

• Service Providers and Enterprises may have different deployment needs

Incremental Upgrade/Deployment

ISP’s differentiate Core and Edge infrastructures upgrade

Enterprise Campus and WAN may have separate upgrade paths

• IPv6 over IPv4 tunnels

• Dedicated Data Link layers for native IPv6

• Dual stack Networks

IPv6 over MPLS or IPv4-IPv6 Dual Stack Routers


IPv6 over IPv4 Tunnels

• Several Tunnelling mechanisms defined by IETF

GRE, Configured Tunnels, Automatic Tunnels using IPv4 compatible IPv6 Address, 6to4

All of the above are supported on Cisco IOS

• Leverages 6Bone experience

• No impact on Core infrastructure

Either IPv4 or MPLS

IPv6 HeaderIPv6 Header Transport Header

Transport Header DataData

IPv6 HeaderIPv6 HeaderIPv4 HeaderIPv4 Header DataDataTransport Header

Transport Header

Service Provider IPv4 Backbone

Service Provider IPv4 Backbone

IPv6 Tunnel

IPv6 Tunnel

IPv6 Tunnel

IPv6 Network


IPv6 over IPv4 Tunnels Case Study

• ISP scenario

Configured Tunnels between IPv6 Core Routers

Configured Tunnels to IPv6 Customers

MP-BGP4 Peering with other 6Bone users

Connection to an IPv6 IX

6to4 tunnels to IPv6 Customers

6to4 relay service

• Enterprise scenario

6to4 tunnels between sites

Configured tunnels between sites or to 6Bone users

Service Service ProviderProvider

IPv4 IPv4 backbonebackbone

IPv6 over IPv4Tunnels

IPv6 Site A

IPv6 Site B

U N I V E R S I T YU N I V E R S I T Y

6Bone

IPv6 IX


IPv6 over MPLS Infrastructure

• Service Providers have already deployed MPLS in their IPv4 backbone for various reasons

MPLS/VPN, MPLS/QoS, MPLS/TE, ATM + IP switching

• Several IPv6 over MPLS scenarios

IPv6 Tunnels configured on CE (no impact on MPLS)IPv6 Tunnels configured on CE (no impact on MPLS)

IPv6 over Circuit_over_MPLS (no impact on IPv6)IPv6 over Circuit_over_MPLS (no impact on IPv6)

IPv6 Provider Edge Router (6PE) over MPLS (no impact on MPLS core)IPv6 Provider Edge Router (6PE) over MPLS (no impact on MPLS core)

Native IPv6 MPLS (require full network upgrade)

• Upgrading software to IPv6 Provider Edge Router (6PE)Low cost and risk as only the required Edge routers are upgraded or installedAllows IPv6 Prefix delegation by ISP


IPv6 Provider Edge Router (6PE) over MPLS

• IPv4 or MPLS Core Infrastructure is IPv6-unaware• PEs are updated to support Dual Stack/6PE • IPv6 reachability exchanged among 6PEs via iBGP (MP-BGP)• IPv6 packets transported from 6PE to 6PE inside MPLS

P P

PP

6PE

Dual StackIPv4-IPv6routers

6PE

v6

v6

v6

v6

v4

v4

v4 IPv4MPLS

CE

CE

CE

CE

MP-iBGP sessions

192.254.10.0

2001:0421::

2001:0420::

192.76.10.0

145.95.0.0

2001:0621::

2001:0620::Dual StackIPv4-IPv6routers

6PE6PE

IPv6 IPv6


Dual Stack IPv4-IPv6 Case Study

• Campus scenario

Upgrade all layer 3 devices to allow IPv6 hosts deployment anywhere, similar to IPX/IP environment

• ISP

Access technologies may have IPv4 dependencies, eg. Cable for network management

Transparent IPv4-IPv6 access services

Core may not go dual-stack before sometimes to avoid a full upgrade

Cable

Leased Line

Dial, ADSL, FTTH

Enterprise

SOHOResidential

ENT/SOHOResidential

Dual Stack Paths


Deployment Architectures

• Several different architectures are identified below. Which is your company pursuing ?

(1) IPv6 tunnel through IPv4 backbone

Configured, Automatic or 6to4

(2) IPv6 over MPLS backbone

(3) Dual IPv4 - IPv6 protocol stacks


Deployment Architectures

• Which customer services are being targeted for , , … ?- wireless phones, personal organizers, etc.

• Which IGP will be used in the backbone ?

- I/IS-ISv6, OSPFv3, RIPv6

• How many customers per area/domain ?

• Is the backbone a ring or mesh topology?

- SONET/SDH over lay ?


Performance

• Which line cards/interfaces are required in ? Which in ?

- STM 4 /16 / 64, channelized, FE, GE, SRP/DPT

• What data forwarding rate/volumes are expected at the edge and backbone ?

-with ACLs / without ACLs

- over time: , , and beyond

• What is the expectation of network convergence given a failure?


Addressing and Scale

• Will your customers be using IPv6 addresses?

• Will your customers be using IPv4 addresses?

• Will you be providing access to the Internet?


Addressing and Scale

• What is the expected customer deployment through , , ?

- # of nodes, # of addresses/node/network

• Is there a desire to support VPNs ?- partitioning, number of customers per VPN


Engineering Issues

• How large do you expect your IPv6 routing table to be?

• How will you partition your address space?

• Is there a requirement for /56 addresses?


Operational Deployment

• What tools need to be developed to support a wide deployment ?

- debug, show ipv6, 3rd party analyzer, GUI


Feature Combinations

• Which features require IPv6 to be ‘enabled’ in the time frame ?

• Which features will coexist simultaneously to provide the services?

- Access Control Lists (ACL), Extended ACLs

- IPsec

- Committed Access Rate (CAR)

- QoS

- others ...


ACLs

• Do you expect to use IPv6 ACLs?

• For which applications will you be using ACLs?

• Will ACLs be deployed with IPsec ?

• Which fields are most important to include in ACLs?

• Do you require full 128 bit address in ACLs? Would 64 bits be sufficient?


NetFlow

• Is Netflow support required ?

• How are you planning to do accounting or billing .. based on what stats ?

• Which fields would be required to report on ?


IPv6 MIBs

• Do you need support for RFC 2465 & 2466?

• Would you prefer Enterprise MIBs for interim versions of Fenner Drafts?

• What Network Management Systems do you plan to use for IPv6?


Mobile IP

• What percentage of your traffic will be Mobile IP traffic?

• What does your Mobile IP traffic look like? (IPSec, Routing Header, Binding Updates, etc.)


IPv6 Multicast

• What are your requirements for IPv6 Multicast functionality?

• What are your performance requirements for IPv6 Multicast?

• What is the timeframe for Multicast deployment?


IPv6 services over GMPLS Backbone



[email protected]


IPv6 Provider Edge Router (6PE) over GMPLS Backbone

• IPv4 or GMPLS Core Infrastructure is IPv6-unaware• PEs are updated to support Dual Stack/6PE • IPv6 reachability exchanged among 6PEs via iBGP (MP-BGP)• IPv6 packets transported from 6PE to 6PE inside GMPLS

P P

PP

6PE

Dual StackIPv4-IPv6routers

6PE

v6

v6

v6

v6

v4

v4

v4 IPv4GMPLS

CE

CE

CE

CE

MP-iBGP sessions

192.254.10.0

2001:0421::

2001:0420::

192.76.10.0

145.95.0.0

2001:0621::

2001:0620::Dual StackIPv4-IPv6routers

6PE6PE

IPv6 IPv6


6PE Forwarding

6PE-1

P2

2001:0421::

2001:0420::

IPv6 packetto 2001:0421::

192.72.170.13

LDP/IGPv4 label1 to 6PE-2


IPv6 packet

To 2001:421::

IPv6 packet

To 2001:421::

MP-BGP labelTo 2001:420::


6PE-2

MPLS Label Pop and IPv6 Forwarding :

•6PE-2 receives an MPLS packet

•Lookup is done on Label

•Result is:

Pop the label & do IPv6 lookup on IPv6 destination

IPv6 packet

To 2001:421::

IPv6 packet

To 2001:421::

P1



IPv6 packet

To 2001:421::

IPv6 packet

To 2001:421::



IPv6-UNaware MPLS Label Switching:

•P1 receives an MPLS packet

•Lookup is done on Label1

•Result is Label2

192.254.10.17

IPv6 packet

To 2001:421::

IPv6 packet

To 2001:421::



IPv6-UNaware MPLS Label Switching:

•P2 receives an MPLS packet

•Lookup is done on Label2

•Result includes Pop label (PHP)

IPv6 Forwarding and Label Imposition:

•6PE-1 receives an IPv6 packet

•Lookup is done on IPv6 prefix

•Result is:

Labelz binded by MP-BGP to 2001:0421::

Label1 binded by LDP/IGPv4 to the IPv4 address of BGP Next Hop (6PE-2)

GMPLS Backbone


Backup slides


O-UNI versus GMPLS Comparison

Link Management, verification, neighbor discovery, etc

LMP LMP

Function MPS/GMPLS O-UNI

Routing Protocol IGP TE extensions N/A

Drafts as of June

SignalingATM

ForumRSVP/CR-LDP

extensionsRSVP/CR-LDP

extensions

Model Peer/Overlay Overlay to Peer

Standards Body Peer/IETF OIF

PeerOverlay

Overlay is a subset of the peer model

• Support UCP protocols including O-UNI and GMPLS in IOS

• Drive innovation and standards through active participation in IETF and OIF

• Deliver UCP technology on Cisco’s key metro optical and router platforms

• Use software services leadership to increase value of transport service offerings

• Support UCP protocols including O-UNI and GMPLS in IOS

• Drive innovation and standards through active participation in IETF and OIF

• Deliver UCP technology on Cisco’s key metro optical and router platforms

• Use software services leadership to increase value of transport service offerings


Milestones QFT2 QFT3/FCS Radar

Dates 02/02 11/02 v1.1

Dev. platform HFR/ENA on GSR HFR H/W with LC HFR H/W with LC

Features O-UNI based on OIF UNI 1.0

UNI

Client core (connection establishment, acceptance, deletion, status for bearer channel of SONET/ SDH framing type, IPv4 support)

Network Services (required to enable demonstration of UNI-C)

Line protocol state control HA Path Restoration (local)

OLM

Core (control channel management OF/OB, neighbor configuration, label resource mapping)

HA

RSVP

Extensions for O-UNI + OF/OB support HA With refresh reduction on shared media

O-UNI based on OIF UNI 1.0

UNI Client (IPv6 and NSAP support) SONET alarm control OLM / LMP (multiple active channels, IF/IB,

hellos, switchover, auto-discovery, link verification, fault isolation)

RSVP in IP-in-IP or GRE tunnel RSVP and LMP State Recovery Procedures Path Protection (through UNI service level

or diversity object)

GMPLS based on latest IETF drafts

Link Management - OLM/LMP RSVP extensions for GMPLS OSPF/ISIS ext. + OF/OB support MPLS-TE Control & TE Link ext. + all

GMPLS labels support Route computation with constraints LSP Hierarchy (FA-LSP) Support for Bi-directional LSP Support of unnumbered links

Border model O-UNI Management Agent GMPLS Management Agent

+ MPLS LSR & LMP MIB Path Protection (protected

segment or segment exclusion) & Restoration (re-route)

Native IPv6 support Multi-domain Peer model Link bundling Computation of diverse and

disjoint paths (SRLG) Optical VPN O-UNI Lambda/ Fiber labels O-UNI Client connection

acceptance access list LSP Joining / Linking GMPLS Multi-area support DWDM transponders on

HFR PLIM

HFR UCP Roadmap


Benefits of UCP

Service Opportunities • Traffic Management and QOS within optical network.• Enables emerging new services such as bandwidth on demand and Optical VPN services.• Enables new services yet to be conceived.

Capability and Operational Savings • De-laying and Common control for Multi-technology network• Enabler for Mesh networking (efficiency)• Enhanced traffic engineering (More intelligent use of bandwidth)• Unified network management• Auto Discovery: topology, resources, services• Integrated/coordinated recovery across multiple levels• Fast protection and restoration (classes)• Rapid rule (policy) based provisioning (faster time-to-service)• Rapid network reconfiguration (responsiveness)• Scales to network size and complexity (extensible)• Standards interoperability

Cisco Proprietary & Confidential, please do not distribute Cisco Systems, Inc.,


Border Peer: A Sweet Spot

The “Border model” is a hybrid between the full Peer and Overlay models.

Border Routers receive routing information from the optical devices as well as routers.

Border router keeps the optical and router domain topology information in separate routing tables.

No routing information from the router region is carried in the optical region.

Optical NNI

OpticalNNI

Optical NNI

BorderRouter

MPLS

GMPLS

R1

R2

OXC/ TDMR2A

R1B

R1A

HFR

HFR

Optical Topology

Router Topology

Edge Router


Advantages of the Border Peer Model

• Takes the strengths of the peer model, while respecting the administrative domains.

Efficient use of resources/ consistent path selection in a heterogeneous network of routers and optical nodes/ devices.

Simplifies fault handing in a router+optical network.

Respects domains boundaries.

• Allows for incremental deployment of the optical regions with minimum-to-no reconfiguration of the existing router region.


Multi-domain Multi-carrier Model

UCP

OTN

UCP

UCP

UCP

UCP

BGP for GMPLS/ O-UNI

IP_2

IP_3

IP_1


UCP


BGP Extensions for G-MPLS and O-UNI• Employ inter-domain routing protocol (BGP) to exchange topology info across domain

boundaries.• Why BGP?

• Extensible, supports multiple address families, many existing policy routing “knobs”,• Independent of IGP,• Consistent with the use and acceptance of BGP.

• Clearly addresses short-coming of a peer peer model, stated earlier. New Service Provider’s Applications

• Create Optical VPN. • Carrier of Carrier Bandwidth Brokering. • Multi-provider restoration and path diversity. • Automatic path restoration following circuit failure over multiple domains .

BGP Extensions for G-MPLS and O-UNI• Employ inter-domain routing protocol (BGP) to exchange topology info across domain

boundaries.• Why BGP?

• Extensible, supports multiple address families, many existing policy routing “knobs”,• Independent of IGP,• Consistent with the use and acceptance of BGP.

• Clearly addresses short-coming of a peer peer model, stated earlier. New Service Provider’s Applications

• Create Optical VPN. • Carrier of Carrier Bandwidth Brokering. • Multi-provider restoration and path diversity. • Automatic path restoration following circuit failure over multiple domains .


UCP Enabler Technology

Key Attributes of MPLS:• Separation of Control and forwarding planes• A Label is a Label !

Generalized MPLS (GMPLS)• MPLS control plane extended for circuits, lambdas, fiber and ports.

Bundle Fiber Lambdas

TDM Channels

Labeled packets

Bundle Fiber Lambdas Labeled Packets

TDM Channels

GMPLS is the UCP enabler technology


LMP Functionality: TE Link Property Correlation

1

32

6

27

TE Link

• LinkSummary message is used for this purpose. • LinkSummaryAck for agreement.• LinkSummaryNack for disagreement.

Lin

kS

um

mar

y

Lin

kS

um

mar

yA

ck/ N

ack

• Synchronizes link state:• Component Interface Id mapping.• Link properties, e.g., link mux type.


OCC: Optical Connection Controller

UNI: User Network Interface

CCI: Connection Control Interface

NNI: ASON control Node Node Interface

IrDI : Inter Domain Interface

Proposed Standards in G.ason

Switch SwitchSwitchClients:IP, ATM,TDM, etc.

OCCOCC OCC

CCI

NNI

UNIUserSignaling

IrDI_NNI

IrDI

OCCASON control plane

Optical Transport Network

Clients:IP, ATM,TDM, etc.

UNI – OIF/IETF

NNI – IETF - GMPLS

NNI

CCICCI – IETF GSMP

1 Cisco Systems, Inc. All rights reserved. Unified Control Plane & IPv6 Mallik Tatipamula, Product...

Documents

Transcript of 1 Cisco Systems, Inc. All rights reserved. Unified Control Plane & IPv6 Mallik Tatipamula, Product...