Geneva, Switzerland, 11 June 2012 Future Network: Naming and Addressing Hyun K. Kahng, ISO/IEC JTC1...

Geneva, Switzerland, 11 June 2012

Future Network: Naming and Addressing

Hyun K. Kahng,ISO/IEC JTC1 SC6Korea University,

[email protected]

Joint ITU-T SG 13 and ISO/JTC1/SC 6 Workshop on

“Future Networks Standardization”

(Geneva, Switzerland, 11 June 2012)

Geneva, Switzerland, 11 June 2012 2

Table of contents

Scope References , DefinitionsChallenges, Problems, Gap Analysis, RequirementScenarios to be deployedPacket Transferring using GA scheme

Scope

RequirementsProblem StatementsGap analysisDesign ObjectivesTechnical ChallengesChronological Scenarios


References

ISO/IEC PDTR 29181-1 ITU-T E.164 (1997)ITU-T Y.1241 (2001)ITU-T Y.2022 (2011)ITU-T Y.2052 (2008)ITU-T Y.2091 (2011)ITU-T Y.2720 (2009)ITU-T Y.3031 (2012)IETF draft-ietf-lisp-23


Definitions

Definitions defined in id- LISP-23Routing locator (RLOC)End point Identification (EID)EID-prefixEnd-systemIngress Tunnel Router (ITR)Egress Tunnel Router (ETR)xTREID-to-RLOC DatabaseLISP site


Definitions

Definitions defined in ITU-T Y.2015Locator (LOC)Node IDID/LOC mapping storage function

Definitions defined in ITU-T Y.2091AddressIdentifierName


Definitions

Definitions defined in this TRGeographical Addressing (GA)Absolute geographical addressRelative geographical addressGeographical Locator (GLOC) Geographical ID (GID)End-node/Access-node/Edge networkGA-site

LER Locator Edge RouterLLER Local LER


Problem Statement(1)

Analog NAS: Telecom Network

Digital NAS: Computer Network


Problem Statement(2)

Diffculty In Network IntegrationDifferent addressing formatsDifferent naming formats, addressing searching, transporting and forwarding. A huge effort to overhaul the existing network infrastructures


Problem Statement(3)Technical Limitations

Central Registration AuthorityAddress Space exhaustionAddress costsIdentifier-locator separationRouting TableVertical StructureDNS Translation

Data EncryptionCategory addressesLack Geographic ConsiderationNo address in native language No decimal naming systemIPv6 Limitations New demands on old naming


Gap Analysis(1)

The need for a Clean Slate DesignCurrent IP-based networksDeficient structural designs.Inefficiency in NAS.Inadequate evolutionary approaches i.e. IPv6Redesign IPv6


Gap Analysis(2)

The GapsOn scalabilityOn securityOn Quality of ServiceOn HeterogeneityOn RobustnessOn customizabilityOn economic incentives


Requirement(1)

Aspects: System RequirementsSpecial NAS requirementsForeseeing mechanismCompatibility RequirementOthers


Requirement(2)

System Technical RequirementsSystem Integrity RequirementIntersystem Coherence RequirementStructural Requirement

A network structure mixing virtual Layer-Three circuit switching and Layer-Four Packet switching

Separation of control layer and data layer


Requirement(3)


Application layer

Presentation Layer

Session layer

Transport Layer

Network layer

Data link layer

Physical layer

Application layer

Transport Layer

Internet layer

Network Interface

Layer

IP（ICMP,ARP,RARP)

FDDI,ATMFast Ethernet，

Ethernet

SMTP DNS FTP RPC SNMP

TCP UDP

Application layer

Network Interface

Layer

FDDI,ATMFast Ethernet，

Ethernet

Network model for the future

New Internet Reference Model

Four layer model

Three layer model

Future network architecture

Transport

Layer

Internet layer

TCP/D/IP protocol

TCP UDP

IP

SMTPDNS

Computer

应用层Application layerTransport

layerInternet

layer

Actual situation of the circuit

layer

Network Interface Layer

Internet/M/IP layer


IMP Router

Internet/M/IP layer


IMPRouter

Computer

应用层Application layerTransport

layerInternet

layer


layer


H/W H/W H/W H/W

M


layer

FTPRPC

SNMP

Four layer model

Seven layer model

The corresponding TCP / IP protocol

Internet Network Architecture

ISO/OSI Network Architecture

Physical link

Physical link

Physical link

Physical link

Requirement(4)

Specific Technical Requirements Addressing Technical Requirements

• Address Format• Separation of ID and Location• Addressing Model • Address Space• Variable Address Length• Address Types

• Direct/Emergency/Verification/Geo• Address Selection


Requirements(5)

• Geographical addressing


Location represented by absolute address

Location represented by relative address

Requirements (6)

• Geographic Address Structure


Code Identifier Range Info Distance Info Location Info

Code Identifier

Field construction

identifier

RangeOption

Range/Unit/Scale

DistanceOption

Distance/Unit/Scale

Absolute Location

information

Absolute address

code

Relative address

code

Alias

Area code

Area code/

country code

Requirements (7)

Geographic Address Structure


Code Identifier Range Info Distance Info

Position Info

codeField

constructionoption

Range(Unit)

optionDistance

(Unit)

‘A’ ‘X’ latitu

deLongitude

altitude

Position Info

latitude longitude altitude

north/ south

degrees min seceast/west

degrees min sec height distanceUnit

Code Identifier Range Info Distance Info Position Info

codeField cons.

option Range Unit Scale optionDistance

(Unit)

‘A’ ‘C’ 1 30 2 Lati Long alti

Requirement (8)

• Address Selection• Fields in Addressing

Addressing type Mobile/Fixed node flag Backbone/local flag Bandwidth Processor information VC flag/region/lable Service type EID/GID LOC/GLOC


Requirement (9)

Complementary Technical Requirements Security Technical Requirement

• New Communications Rules To Supplement New NAS

• Address Allocation Encryption• Header• Emergency Routing

EXTENSION TECHNICAL REQUIREMENT EVALUATION AND TEST REQUIREMENT


Scenarios To be Deployed(1)

Near-future scenarioIPv6,ID/LOC separationUnified ID

Mid-term or long-term scenarioGeographical addressing using GPS, or Satellite3-dimensional routing


Packet Transferring using GA scheme

DefinitionsGeographical ETR (GETR) - ELERGeographical ITR (GITR) - ILERAccess-node - LLEREID-to-GID databaseEID-to-GLOC databaseGA-Site



Transferring packets in backbone network using GA


…Backbone network

edgenetwork

GITR GETR

Access-Node

End-node


Transferring packets in backbone network using GA


source end-nodeE1 with EID1

GIDE1 Registration

GITR backbone network GETRdestination end-node

E2 with EID2GIDE2 Registration

Query GLOC for EID2

Reply GLOCGETR

for EID2

~~ ~~~~~~~~ ~~~~~~ ~~

GIDE1, GLOCGITR

EID1, EID2

data GLOCGETR GIDE1

EID1, EID2

data

GLOCGITR, GLOCGETR

EID1, EID2

data


Transferring packets inside of the edge network using GA

Registration of EID and GID to GITR


End-node GITR

Generate GID

GLOC registration REQGID and EID

GLOC registration ACKGID and EID

Link setup complete



Operations in the mobile access network


GETR/GLOCGETR

Backbone network

edge network

EID2/GID21Access-Node3/

GIDAN3

EID2/GID23

Access-Node2/GIDAN2

Access-Node1/GIDAN1



Packet delivery in mobile access network with sub-access networks


End-node2

GID23 registration

Access-node 3 Access-node 1 GETRBackbone network

GID21 registrationGenerate new GID21

Generate GID23

Link setup complete

Move to sub-access net 1

Data packet(GLOCGITR, GLOCGETR)

(EID1, EID2)Data packet

(GLOCGETR, GIDAN3)(EID1, EID2)

Data packet(GIDAN3, GID23)

(EID1, EID2)

Data packet(GLOCGITR, GLOCGETR)

(EID1, EID2)Data packet

(GLOCGETR, GIDAN1)(EID1, EID2)

Data packet(GIDAN1, GID21)

(EID1, EID2)



Operations in ad-hoc mobile network


GETR/GLOCGETR

Backbone network

EID1/GID11

EID2/GID23

Access-Node3/GIDAN3

Access-Node1/GIDAN1




FN-NAS Standardization Plan

MAJOR TASKS IN THE FUTURERefine and complete this technical reportLook for and select the best proposal for a general framework on FN-NASStandardize the general framework of FN-NASMake standards of specific schemes under the general framework of FN-NAS


FN-NAS Standardization Plan

MAJOR TASKS IN THE FUTURE Make complementary standards or

imbedding FN-NAS into Future Network system

Provide NAS assistance to study of Future Network applications

Start work on registration and distribution of numbers and addresses for Future Network

Make a plan for address resources management policies


Date post:	27-Mar-2015
Category:	Documents
Upload:	sophia-moss
View:	212 times
Download:	0 times

Geneva, Switzerland, 11 June 2012 Future Network: Naming and Addressing Hyun K. Kahng, ISO/IEC JTC1...

Documents