Future Network: Naming and Addressing

advertisement
Joint ITU-T SG 13 and ISO/JTC1/SC 6
Workshop on
“Future Networks Standardization”
(Geneva, Switzerland, 11 June 2012)
Future Network:
Naming and Addressing
Hyun K. Kahng,
ISO/IEC JTC1 SC6
Korea University,
kahng@korea.ac.kr
Geneva, Switzerland, 11 June 2012
Table of contents
Scope
References , Definitions
Challenges, Problems, Gap Analysis,
Requirement
Scenarios to be deployed
Packet Transferring using GA scheme
Geneva, Switzerland, 11 June 2012
2
Scope
Requirements
Problem Statements
Gap analysis
Design Objectives
Technical Challenges
Chronological Scenarios
Geneva, Switzerland, 11 June 2012
3
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
Geneva, Switzerland, 11 June 2012
4
Definitions
Definitions defined in id- LISP-23
Routing locator (RLOC)
End point Identification (EID)
EID-prefix
End-system
Ingress Tunnel Router (ITR)
Egress Tunnel Router (ETR)
xTR
EID-to-RLOC Database
LISP site
Geneva, Switzerland, 11 June 2012
5
Definitions
Definitions defined in ITU-T Y.2015
Locator (LOC)
Node ID
ID/LOC mapping storage function
Definitions defined in ITU-T Y.2091
Address
Identifier
Name
Geneva, Switzerland, 11 June 2012
6
Definitions
Definitions defined in this TR
Geographical Addressing (GA)
Absolute geographical address
Relative geographical address
Geographical Locator (GLOC)
Geographical ID (GID)
End-node/Access-node/Edge network
GA-site
LER
LLER
Locator Edge Router
Local LER
Geneva, Switzerland, 11 June 2012
7
Problem Statement(1)
Analog NAS:
Telecom Network
Geneva, Switzerland, 11 June 2012
Digital NAS: Computer
Network
8
Problem Statement(2)
Diffculty In Network Integration
Different addressing formats
Different naming formats, addressing
searching, transporting and forwarding.
A huge effort to overhaul the existing
network infrastructures
Geneva, Switzerland, 11 June 2012
9
Problem Statement(3)
Technical Limitations
Central
Registration
Authority
Address Space
exhaustion
Address costs
Identifier-locator
separation
Routing Table
Vertical Structure
DNS Translation
Geneva, Switzerland, 11 June 2012
Data Encryption
Category addresses
Lack Geographic
Consideration
No address in
native language
No decimal naming
system
IPv6 Limitations
New demands on
old naming
10
Gap Analysis(1)
The need for a Clean Slate Design
Current IP-based networks
Deficient structural designs.
Inefficiency in NAS.
Inadequate evolutionary approaches i.e.
IPv6
Redesign IPv6
Geneva, Switzerland, 11 June 2012
11
Gap Analysis(2)
The Gaps
On
On
On
On
On
On
On
scalability
security
Quality of Service
Heterogeneity
Robustness
customizability
economic incentives
Geneva, Switzerland, 11 June 2012
12
Requirement(1)
Aspects:
System Requirements
 Special NAS requirements
 Foreseeing mechanism
 Compatibility Requirement
 Others

Geneva, Switzerland, 11 June 2012
13
Requirement(2)
System Technical Requirements
System Integrity Requirement
Intersystem Coherence Requirement
Structural Requirement


A network structure mixing virtual LayerThree circuit switching and Layer-Four
Packet switching
Separation of control layer and data layer
Geneva, Switzerland, 11 June 2012
14
Requirement(3)
New Internet
Reference Model
Seven layer
model
Four layer
model
ISO/OSI Network
Architecture
Four layer
model
Internet Network
Architecture
The corresponding
TCP / IP protocol
Three layer
model
Future network
architecture
TCP/D/IP
protocol
Application
layer
Presentation
Layer
Application
layer
Application
layer
RPC
DNS
SMTP DNS FTP RPC SNMP
Session layer
Transport
Layer
Transport
Layer
Network
layer
Internet layer
IP
(ICMP,ARP,RARP)
Network
Interface
Layer
FDDI,ATM
Fast Ethernet,
Ethernet
Data link
layer
Physical
layer
TCP
SMTP
Trans
port
Layer
UDP
Internet
layer
TCP
Actual
situation of
the circuit
layer
Actual
situation of
the circuit
layer
Network
Interface Layer
Physical
link
H/W
SNMP
UDP
M
IP
FDDI,ATM
Fast Ethernet,
Ethernet
Network
Interface
Layer
Computer
Computer
Application
layer
应用层
Transport
layer
Internet
layer
FTP
IMP
Router
IMP
Router
Internet/M/IP
layer
Internet/M/IP
layer
Network
Interface Layer
Network
Interface Layer
Physical
link
Physical
link
H/W
H/W
Application
layer
应用层
Transport
layer
Internet
layer
Actual
situation of
the circuit
layer
Network
Interface Layer
Physical
link
H/W
Network model for the future
Geneva, Switzerland, 11 June 2012
15
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
Geneva, Switzerland, 11 June 2012
16
Requirements(5)
•
Geographical addressing
Location represented by
absolute address
Geneva, Switzerland, 11 June 2012
Location represented by
relative address
17
Requirements (6)
•
Geographic Address Structure
Code Identifier
Range Info
Distance Info
Location Info
Absolute Location
information
Absolute address
code
Code
Identifier
Field
construction
identifier
Range
Option
Range/
Unit/
Scale
Distance
Option
Distance/
Unit/
Scale
Relative address
code
Alias
Area code
Area code/
country code
Geneva, Switzerland, 11 June 2012
18
Requirements (7)
Geographic Address Structure
Code Identifier
Range Info
code
Field
construction
‘A’
‘X’
Distance Info
Range
(Unit)
option
option
Position Info
Distance
(Unit)
latitu
de
Longi
tude
altitu
de
Position Info
latitude
north/
south
degrees
longitude
min
sec
Code Identifier
east/
west
degrees
Range Info
code
Field
cons.
option
Range
Unit
‘A’
‘C’
1
30
2
Geneva, Switzerland, 11 June 2012
min
altitude
sec
height
Distance Info
Scale
option
U
ni
t
distance
Position Info
Distance
(Unit)
Lati
Long
alti
19
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

Geneva, Switzerland, 11 June 2012
20
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
Geneva, Switzerland, 11 June 2012
21
Scenarios To be Deployed(1)
Near-future scenario
IPv6,
ID/LOC separation
Unified ID
Mid-term or long-term scenario
Geographical addressing using GPS, or
Satellite
3-dimensional routing
Geneva, Switzerland, 11 June 2012
22
Packet Transferring using GA scheme
Definitions
Geographical ETR (GETR) - ELER
Geographical ITR (GITR) - ILER
Access-node - LLER
EID-to-GID database
EID-to-GLOC database
GA-Site
Geneva, Switzerland, 11 June 2012
23
Packet Transferring using GA scheme
Transferring packets in backbone
network using GA
…
GITR
edge
network
Backbone
network
GETR
AccessNode
End-node
Geneva, Switzerland, 11 June 2012
24
Packet Transferring using GA scheme
Transferring packets in backbone
network using GA
source end-node
E1 with EID1
GITR
backbone network
GETR
GIDE1 Registration
~
~
destination end-node
E2 with EID2
GIDE2 Registration
~
~
~
~
~
~
Query GLOC for EID2
GIDE1, GLOCGITR
EID1, EID2
data
Reply GLOCGETR
for EID2
GLOCGETR GIDE1
EID1, EID2
data
GLOCGITR, GLOCGETR
EID1, EID2
data
Geneva, Switzerland, 11 June 2012
25
Packet Transferring using GA scheme
Transferring packets inside of the
edge network using GA
Registration of EID and GID to GITR
End-node
GITR
Link setup complete
Generate GID
GLOC registration REQ
GID and EID
GLOC registration ACK
GID and EID
Geneva, Switzerland, 11 June 2012
26
Packet Transferring using GA scheme
Transferring packets inside of the
edge network using GA
Operations in the mobile access network
Backbone
network
GETR/
GLOCGETR
Access-Node2/
GIDAN2
edge network
mo
Access-Node1/
ve
GIDAN1
EID2/GID21
Access-Node3/
GIDAN3
EID2/GID23
Geneva, Switzerland, 11 June 2012
27
Packet Transferring using GA scheme
Transferring packets inside of the edge
network using GA
Packet delivery in mobile access
network with sub-access networks
End-node2
Access-node 3
Access-node 1
GETR
Backbone
network
Link setup complete
Generate GID23
GID23 registration
Data packet
(GLOCGETR, GIDAN3)
(EID1, EID2)
Data packet
(GIDAN3, GID23)
(EID1, EID2)
Data packet
(GLOCGITR, GLOCGETR)
(EID1, EID2)
Move to sub-access net 1
Generate new GID21
GID21 registration
Data packet
(GIDAN1, GID21)
(EID1, EID2)
Geneva, Switzerland, 11 June 2012
Data packet
(GLOCGETR, GIDAN1)
(EID1, EID2)
Data packet
(GLOCGITR, GLOCGETR)
(EID1, EID2)
28
Packet Transferring using GA scheme
Transferring packets inside of the edge
network using GA
Operations in ad-hoc mobile network
Backbone
network
Access-Node1/
GIDAN1
Access-Node3/
GIDAN3
GETR/
GLOCGETR
EID2/GID23
EID1/GID11
Geneva, Switzerland, 11 June 2012
29
Packet Transferring using GA scheme
Transferring packets inside of the
edge network using GA
Geneva, Switzerland, 11 June 2012
30
FN-NAS Standardization Plan
MAJOR TASKS IN THE FUTURE
Refine and complete this technical report
Look for and select the best proposal for
a general framework on FN-NAS
Standardize the general framework of
FN-NAS
Make standards of specific schemes
under the general framework of FN-NAS
Geneva, Switzerland, 11 June 2012
31
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
Geneva, Switzerland, 11 June 2012
32
Download