Network Architecture with Recursive Addressing

1. NARA:
Network Architecture with
Recursive Addressing
DaeYoung KIM
dykim@cnu.kr
Wednesday, February 25, 15

2. Key Words
• Scalable
• recursive; inwards & outwards
• Local
• to a given autonomous site
• Orthogonal
• interior opaque to exterior
Wednesday, February 25, 15

3. Architecture
• Internet: a network of autonomous sites
• Site: a collection of nodes
• Site named by a global site address
• Node named by a local node address
• Exterior routing on site addresses
• Interior routing on node addresses
Wednesday, February 25, 15

4. Global Network = {sites}
1
4
3
2
25
15
41
37
22
11
11
Wednesday, February 25, 15

5. Global Network = {sites}
1
4
3
2
25
15
41
37
22
11
11
Wednesday, February 25, 15

6. site = {nodes} = {subnets}
1 2
3
4
5
6
91
94
97
101
96
Wednesday, February 25, 15

7. Scope
subnet
site site
mac addr subnet
subnet subnet subnet
node name
global
site addr
subnet addr
node addr site
Wednesday, February 25, 15

8. APP
TP/IP
NameS
Site
Site-b
Site-c
{node, site}
name
G
G
nodenode
name
1
2
3
6
6’
7
Site-a
iAS6’’
4
5
{node, site}
Operational Overview
Wednesday, February 25, 15

9. Routing
• Interior & Exterior routings orthogonal
• Interior routing on node address
• Exterior routing on site address
• Sites equivalent to network nodes
• Any routing protocols possible
Wednesday, February 25, 15

10. Flat Interior Routing
1 2
3
4
5
6
91
94
97
101
96
1
1
12
2
91
91
94
97
97
-
96
96
94
-
1
2
3
4
5
6 94 94
1
2
3
4
5
91
91
94
97
97 97
-
6 94 -
91
91
94
97
97
96
-
-
94
96
1
2
3
4
5
6 94 94
91
97
91
Wednesday, February 25, 15

11. Flat Interior Routing
1 2
3
4
5
6
91
94
97
101
96
1
1
12
2
91
91
94
97
97
-
96
96
94
-
1
2
3
4
5
6 94 94
1
2
3
4
5
91
91
94
97
97 97
-
6 94 -
91
91
94
97
97
96
-
-
94
96
1
2
3
4
5
6 94 94
91
97
91
Wednesday, February 25, 15

12. 91
91
94
97
97
96
-
-
94
96
1
2
3
4
5
6 94 94
91
91
94
97
97
-
96
96
94
-
1
2
3
4
5
6 94 94
1
2
3
4
5
91
91
94
97
97
97
97
-
91
6 94 -
91
Flat Interior Routing
1 2
3
4
5
91
94
97
101
96
1
1
12
2
6
{94:-6} {94:-6}
{91:+6}
{91:+6}
Wednesday, February 25, 15

13. Flat Interior Routing
1 2
3
4
5
91
94
97
101
96
1
1
12
2
6
91
91
94
97
97
-
96
96
94
-
1
2
3
4
5
6 91 -
91
91
94
97
97
97
97
-
91
1
2
3
4
5
6 91 91
91
91
91
94
97
97
96
-
-
94
96
1
2
3
4
5
6 91 96
Wednesday, February 25, 15

14. Mapped Interior Routing
1 2
3
4
5
6
91
94
97
101
96
1
1
12
2
1
2
3
4
5
91
91
94
97
97
6 94
mapper
{node, subnet}
= {node, router}
Wednesday, February 25, 15

15. Mapped Interior Routing
1 2
3
4
5
6
91
94
97
101
96
1
1
12
2
1
2
3
4
5
91
91
94
97
97
6 94
mapper
{node, subnet}
= {node, router}
Wednesday, February 25, 15

16. 3
4
5
6
1 2
3
4
5
91
94
97
101
96
1
1
12
2
6
{94:-6}
{91:+6}
1
2
3
4
5
91
91
94
97
97
6 94
mapper
{node, subnet}
= {node, router}
Mapped Interior Routing
Wednesday, February 25, 15

17. 1 2
3
4
5
91
94
97
101
96
1
1
12
2
6
1
2
3
4
5
6
mapper 91
91
94
97
97
91
{node, subnet}
= {node, router}
Mapped Interior Routing
Wednesday, February 25, 15

18. Exterior Routing
1
2
3
4
Wednesday, February 25, 15

19. Flat Exterior Routing
1
3
4
2
25
15
41
37
22
11
37
25
15
22
1
3
2
1
1
11
41 3
dst:41
2
2
1
11
11
Wednesday, February 25, 15

20. Mapped Exterior Routing
1
4
3
2
25
15
41
37
22
11
11
11 12
13
21 41
42
Wednesday, February 25, 15

21. Implementation
Choices
• IPv4 (or IPv6 address) for node address
• AS# for site address
• DNS extended for NameS
• IS-IS+ or OSPF+ for interior routing
• BGP4+ for exterior routing
Wednesday, February 25, 15

22. Consequences
• Recursively scalable without bound
• No address depletion, No governance
• No routing table explosion
• Inherent fast host / nw mobility by routers
• Effortless ISP migration and multi-homing
• No ID/Loc Separation
Wednesday, February 25, 15

23. Others
• LISP ;local & PA address
• ILNP ;global ID & Loc
• ENCAP ;domain address
• hIPv4 ;edge/core locators
Wednesday, February 25, 15

24. Conclusions
• Scalable Internet
• by local addressing & orthogonal routing
• feasible and deployable
• Further works for proof of concept
Wednesday, February 25, 15

25. Acknowledgements
• Work done during a stay at ACCMS, Kyoto
University with their support.
• Profound thanks to Prof.Yasuo OKABE.
Wednesday, February 25, 15

26. References
• RFC 1498, On the Naming and Binding of
Network Destinations, J. Saltzer, 1993.
• RFC 1955, ENCAPS, B. Hinden, 1996.
• John Day, Patterns in Network Architecture,
Prentice-Hall, 2008.
• Discussions at IRTF/RRG.
Wednesday, February 25, 15

27. Appendix
Wednesday, February 25, 15

28. Inter-Net
link
relay-node
= router
leaf-node
= host
Wednesday, February 25, 15

29. N & A Classics
• Name: identifier of an object (node)
• Address: locator of an object
• The two are different and distinct
• Need both to locate/identify an object
• “There’s no identifying an object without
locating it, and vice-versa” - Jerry Saltzer
Wednesday, February 25, 15

30. ID/Loc Separation?
Node ID
MAC address
Locator
LAN
Naming
the same thing
twice!
Wednesday, February 25, 15

31. Fallacy of IP Address
BobAlice
?
?
x
To: I1
I1
I2
Name the node,
not the interface!
Wednesday, February 25, 15

32. ID == Address !
• Need only ID
• ID points to a node, not an interface.
• ID should be routable in inter-net.
• So, ID is a node address.
• Address is the right term, not ID!
Wednesday, February 25, 15

33. Address == Name !
iPAD-dy.kr
168.188.68.120
00:25:00:21:e4:a9
name
address name
address
DNS
ARP
APP
inter-net
network
iPAD
-dy
PoA
Wednesday, February 25, 15

34. Global Name & Local Address
Why bother keeping both global?
192.168.2.100 192.168.2.100
iPAD-dy.kr NameS iPAD-dy.jp
ASk ASj
{IPx} {IPy}
{x,y} = {4, 6}
Wednesday, February 25, 15