Hiroaki Harai ([email protected]) Network Research ... · NICT Lab. router HANA GW router ... VLAN XXX VLAN XXX Via APAN XXX.XXX.XXX.XXX/30 ... ‐mobility, multihoming, security become

Development of a Host‐ID/Locator Split & Automatic Locator‐Assigned Network

APAN 33rd Meeting (Chiang Mai)Future Internet TestbedWorking Group Workshop

February 15, 2012Hiroaki Harai ([email protected])

Network Research Headquarters, National Institute of Information and Communications Technology

© National Institute of Information and Communications Technology 2

AgendaMotivationHierarchical & Automatic Number Assignment ‐HANADeployment on JGN‐XHost‐ID/Locator Split Net Architecture – HIMALISSummary

Contributors in NICT• Kenji Fujikawa• Ved P. Kafle• SugangXu• HajimeTazaki

• Yasunaga Kobari• TomojiTomuro


Increasing in Routing Table Size

400K routing entries (cf. 40K ASes)Convergence time

http://bgp.potaroo.net/as2.0/bgp‐active.html

Present

Future

300,000

400,000

Active Ro

uting En

tries

1989 Present

Electric power consumption1.28 W @512K Prefix, 40Gbps lookup

Routing Table Reduction

http://www.ietf.org/

© National Institute of Information and Communications Technology

Some Constraints in the Internet

Current Internet (Routing)

4

Protocol stack

IPAddr1

L5L4L3L2L1

IPAddr2

IPAddr1

Session is associated with using IP addresses

L5L4L3L2L1

Edge Networks

Global Network

Current Internet (Session)

NSP 2

NSP 1

Company,

Office Net

:

Routing EntriesExplosion, Unstable

:

Single RouteNo route In Failure

:

NSP Network Service Provider

Operator Configures Node Locator

Multihome,ID/Loc split


Net Automation Heterogeneity & Mobility

Hierarchical Locators Assign for Route Aggregation: Small size of L3 routing table high availability with energy saving, high‐speed locator lookup, e2e multi‐homing

ID/Locator Split Architecture： No limitation for location of “things”, support mobile communication, multi‐homing, route aggregation, and heterogeneous networking

Transport/Identity/Network Layer Architecture+ automatic assignmentsFor availability enhancement


AKARI Net Design Architecture for NWGN (NewGeneration Network)

6

Net Automation

Heterogeneity & Mobility

Power Saving & Capacity

Life Support (Sensors)


AgendaMotivationHierarchical & Automatic Number Assignment ‐ HANADeployment on JGN‐XHost‐ID/Locator Split Net Architecture – HIMALISSummary


Current Internet (Provider Independent) NWGN (Provider Aggregatable)8

Prefix of Loc

NetName

OutPort

1.2/2 NSP 1 A3.4/2 NSP 2 B5.6.10/3 Home B

Cannot aggregate

Prefix of Loc

NetName

OutPort

1.2/2 NSP 1 A3.4/2 NSP 2 B1.2.10/3 Home A3.4.10/3 Home B

Can aggregate

Net Automation

Assigning Locators Hierarchically and Automatically

Prefix of Loc

NetName

OutPort

1.2/2 NSP 1+ A3.4/2 NSP 2+ B


HANA: Objective & ApproachesImplementing High‐AvailabilityNetworksApproaches

Flexible routing: by providing multiple paths to end sites/hostsStabilizing backbone network: by suppressing the global routing table sizeReducing network management costs: by automatic locator number allocation

Also have high‐speed lookup, green, and high throughput features

HANA: Hierarchical & Automatic Numbering Assignment for Locators

Net Automation

0 n‐1 n m‐1 m N‐1Prefix Midfix Suffix

Prefix length: /nMidfix length: /n‐mSuffix length: /m‐N

Prefix: 1/8, 1.1.1/24Midfix: 0.1/8‐16, 0.0.0.4/24‐32


NSP 1

10

HANA OverviewTech 1: Suffix allocation of hosts/routers in each NSP/site → Reduction of Net management costs

NSP 2

Multiple Routes:Improvement of fault tolerance

Prefix:1/8

Prefix:1.1.1/24

Tech 2:Hierarchical automaticprefix distribution

1/8 2/8

Prefix:2/8

Prefix:2.1.2/24

0.0.0.10.0.0.1

0.0.0.2 0.0.0.3

0.0.0.4 0.0.0.5 0.0.0.6

MidfixreqMidfixack

Tech 3:Automatic multiple locator configurationPrefixes: 1.1.1/24, 2.1.2/24, Suffix: 0.0.0.4

→ Locators: 1.1.1.4, 2.1.2.4

Other Techs:‐Auto registration of LOCs to a name resolution sys‐ Cooperation with routing protocols

HANA Server

Prefix:1.1.1/24

Prefix:2.1.2/24

Company/Home

network

The Global Routing Table:Reduced, stable

Net Automation

Cf) Fujikawa, Harai, Ohta,, Asia Workshop on Future Internet Technologies (AWFIT2011), Bangkok.


HANA Overview (Cont’d)R1

R5

R2R3

R4

R13

R10R11

R12

0.0.1/8‐16

R3

0.0.0.3.4/40

0.0.0.3.7/40

0.0.0.3.5/40

0.0.0.3.6/400.0.0.3.2/40

0.0.0.3.3/40

0.0.0.3.1/40

0.0.0.3/24‐32

1.2.6.3/32

1.2.6.3.5/40

1.2.6.3.1/40

1.2.6.3.6/40

Prefix = 1.2.6/24Net Automation


Hierarchical Auto Numbering Assignment for Locators<<Simulation & Visualization>>

12

Cf) Fujikawa, Harai, Ohta, The Basic Procedures of Hierarchical Automatic Locator Number Allocation Protocol HANA, Asia Workshop on Future Internet Technologies (AWFIT2011), Bangkok.

Net Automation


HANA on a Virtualized Network

All the NSPs/site are executed on CoreLab nodes4 nodes have being used for each NSP/SiteEach node has 42 routers/hosts in simulation

Site

NSP1NSP2

TOP NSP

Cf) CoreLab, http://www.corelab.jp/

Net Automation


AgendaMotivationHierarchical & Automatic Number Assignment ‐HANADeployment on JGN‐X

This is a Future Internet TestbedWG WorkshopHost‐ID/Locator Split Net Architecture – HIMALISSummary


Internet Access: HANA‐based Mini‐Data Center in NICT Koganei

Net Automation

15

Internet

(NICT Koganei HQ)

Mini‐Data CenterHANA Multi‐homed Network

(NICT Koganei HQ)

NICT Lab.router

HANAGW router

XXX.XXX.XXX.XXX/30XXXX:XXXX:XXXX::/64Point‐to‐ Point segment

XXX.XXX.XXX.0/24XXXX:XXXX:XXXX::/48

JGN‐Xrouter

HANAGW router

upper IPv4lower IPv6

XXX.XXX.XXX.0/24XXXX:XXX:XXX::/48

VLANXXX

VLANXXX

Via APAN

XXX.XXX.XXX.XXX/30XXXX:XXXX:XXXX::/64Point‐to‐ Point segment


Hierarchical Auto Number Assign

16


Plan: Deploying AKARI Architecture‐basedNet on Nation‐wide Virtual Network

Koganei

A Univ.

B Univ.

ID/Loc split Net

1.2/2

1/1

2/1

3/1 3.1/2

3.2/2

4/1

1.2.3/33.1.2/3

3.2.2/3





Hierarchical Locators Assign for Route Aggregation: Small size of L3 routing table high availability with energy saving, high‐speed locator lookup, e2e multi‐homing

ID/Locator Split Architecture： No limitation for location of “things”, support mobile communication, multi‐homing, route aggregation, and heterogeneous networking

Transport/Identity/Network Layer Architecture+ automatic assignmentsFor availability enhancement

again


ID/locator Split Internetworking Architecture (1/2)Background: current Internet problems

mobility and multihomingsupporting heterogeneous network layer protocols and locatorsscalable routing, traffic engineering

IP address as both host ID and Locator

Imposes limitations on

Physical

Data link

Network

Transport

Application

Physical

Data link

Network

Physical

Data link

Network

Transport

Application

Host Router HostLinkLink

Use IP addr as Locator

Use IP addr as ID

ID/locator split architecture

PhysicalData link

Network

Host Border Router

Host

LinkLink

Use Locator

Use ID

Transport

Application

Identity

Map ID to Locator

PhysicalData link

Network

Transport

Application

PhysicalData link

NetworkIdentity Identity

Global Hostname

IDPrefix Scope Version Hash Value

Local Hostname # Domain Name

ParameterHash function

LocatorsLocator 2 … Locator N

Mobility MultihomingDynamic mapping

New ID space introduced

Locator 1

cf) V. P. Kafle, et al., IEEE Com. Mag., Feb 2010.



ID/locator Split Internetworking Architecture (2/2)‐mobility, multihoming, security become easier

Edge Networks

Current Internet:mobility/multihomingnot supported natively

Protocol stack

IPAddr1

L5L4L3L2L1

IPAddr1

Core Network

Edge Networks

New Generation Network：mobility/multihoming natively supported

Protocol stack

Loc 1

L5L4L3L2L1

L5L4L3L2L1

ID

Core Network

ID

Security association is between IP addrs Security association is between IDs

L5L4L3L2L1

Mobility Mobility

20

Loc2IPAddr2


HIMALIS Architecture Stack & Identity Layer Functions

map IDs to locators (or L3 protocol) by searching in ID tables (for ID/locator bindings)translate locators (or L3 protocols) in data packetsexchange signaling messages to build or update ID tables

Transit Network

Host

Edge Network A Edge Network B

Edge Router (GW)

Core Routers

Edge Router

NETIdentity

Transport

LinkPHY

Application

Identity

Transport

Application

NETIdentity

LinkPHY

NET

LinkPHY

NetworkLinkPHY

LinkPHY

NET

Identity

LinkPHY

NETLinkPHY

NETLinkPHY

NETLinkPHY

LinkPHY

Host

HIMALIS (Heterogeneity Inclusion for Mobility Adaption through Locator ID Separation)


Edge Network

Global Transit Network

GWGW

Edge Network

HostHost

Host Name Registry (HNR)

RoutersDomain Name Registry

(DNR)

PHYLinkNetwork

TransportApplication

Identity

PHYLinkNetwork

TransportApplication

Identity

PHYLinkNetworkIdentity

PHYLinkNetwork

PHYLinkNetworkIdentity

HNR

HIMALIS Architectural Entities

(Perform L3 protocols/locators translation)

(Retrieve hostname to ID/locator mappings, implement ID/locator split protocol stack)

Edge networks with heterogeneous L3 protocols/locator spaces

(Store and provide mappings between various parameters, e.g., ID/locator mappings)


22cf) V. P. Kafle, et al., IEEE Com. Mag., Feb 2010.


DNR and HNR provide hostname to host ID/locator bindings

To communicate with Host 2, Host 1 sends (1) Hostname resolution request to LNS, which resolves the (2) Domain name to HNR B’s ID and locator from DNR, and then the (3) Hostname to host ID/locator from HNR B and Host 2.

Domain name resolution

GW

Host 1

LNS

Hostname resolution request

(1)

kafle-pc#idloc.org:

GW

Host 2

(3)

(2)

(5)

(4)

Hostname resolution request

kafle-pc#mydomain.org

sen01#yourcompany.com

DNR

.comorgmydomain.org:

=> HNR A’s ID&GLOC…

DNR Recordyourcompany.com:

…=> HNR B’s ID&GLOC

DNR Record

HNR A

kafle-pc#mydomain.org:=> Host1’s ID&GLOC

HNR Record

HNR B

sen01#yourcompany.com:=> Host2’s ID&GLOC

HNR Record

Hostname resolution response

LNS


GWs translate L3 protocols (locators) using ID tables

After hostname resolution, LNS provides ID/locator binding to GW, which caches it in ID table. GW translates L3 protocols (locators) in packet headers by using bindings from ID tables.

GW 1

Host 1

GW2

Host 2

=>{Host2’s ID&GLOC}

ID TableHost1’s ID&LLoc ID Table

H = Host G = GW

data

=>{Host1’s ID&GLOC}Host2’s ID&LLoc

Headerdata

Header

data

Src loc: G2’s LLocDest loc: H2’s LLocSrc ID: H1’s IDDest ID: H2’s ID

Src loc: H1’s LLocDest loc: G1’s LLocSrc ID: H1’s IDDest ID: H2’s ID

Src loc: H1’s GLocDest loc: H2’s GLocSrc ID: H1’s IDDest ID: H2’s ID

Header

L3 Protocols (Locators) Translation


HIMALIS System ImplementationWe have validated the feasibility of the HIMALIS network functions by implementing them on PCsWe have been optimizing them based on the performance results.


Hosts Display: network status

Gateways

DNR, HNR

In local network or in Internet (PlanetLab)

Edge Networks

Display: session status


HIMALIS System Operation VerificationHeterogeneity & Mobility




Summary Heterogeneity & Mobility

HIMALIS: Host‐ID/Locator SplitNet Automation

HANA: Hierarchical Auto Numbering AssignmentProof‐of‐concept prototyping, protocol designNext steps (on going)

HANA Full Internet‐scale VerificationName Regisitry Integration (Automatic Registration/Update)HIMALIS Kernel ImplementationNet‐Layer Independent Application SupportBuilding the HIMALIS/HANA on R&D Testbed

New Generation Network Infrastructure as a ServicePlease visit NICT booth at Interop Tokyo 2012 in June.

28


Design a network of the future from clean slateDevelop novel technologies before 2015To envision a new ICT infrastructure for the next 2‐3 decades

AKARI Architecture Design Project‐ a small light in the dark pointing to the future ‐Design & Building towards NWGN supporting Future Society

Design Principles for Net Architecture

Approach to NWGN

Sustainable Network Architecture (over 50 years)

1. Crystal Synthesis• Select, Integrate, Simplification• Common Layer• End-to-End

Diversity Inclusion

3.Sustainable & Evolutionary• Self-organizing, Emergent• Scalable Distributed Control• Openness

2.Reality Connection• Physical Logical Separation• Bi-directional Authentication• Traceability

Reliable Network Space Social Potentiality Promotion

29Cf. Harai et al., IEICE Trans. Commun., Mar 2010.


R&D Milestone

30

Goal: Design of New‐Generation Network in 2015 and Establish Its Component Technologies2006 20112007 2008 2009 2010 2012 2013 2014 2015

NWGNBlue print

JGN2plus

Conceptual Design

JGN2 JGN‐X, StarBED

ImplementingNWGN

Functions & NWGN

Redesigned blueprint

Testbed Design

Adding Automation, Virtualization,

Integrated Net, …

Connecting, Incorporating to Testbed

Detail Protocol Design

Overlay Net, Net Virtualization

Detail Design

Test implementation & Evaluation

Implementation & Evaluation

Done/Plan

Available Facilities

Documents

Hiroaki Harai ([email protected]) Network Research ... · NICT Lab. router HANA GW router ... VLAN XXX VLAN XXX Via APAN XXX.XXX.XXX.XXX/30 ... ‐mobility, multihoming, security become