2011
DOI: 10.1016/j.comnet.2010.12.016
|View full text |Cite
|
Sign up to set email alerts
|

A Dynamic Recursive Unified Internet Design (DRUID)

Abstract: a b s t r a c tThe Dynamic Recursive Unified Internet Design (DRUID) is a future Internet design that unifies overlay networks with conventional layered network architectures. DRUID is based on the fundamental concept of recursion, enabling a simple and direct network architecture that unifies the data, control, management, and security aspects of the current Internet, leading to a more trustworthy network. DRUID's architecture is based on a single recursive block that can adapt to support a variety of communi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(19 citation statements)
references
References 60 publications
(62 reference statements)
0
19
0
Order By: Relevance
“…While this concept of locator-identifier split has the above advantages, its disadvantages are that additional actions are required for every data-plane packet, plus controlplane mapping is required between identifiers and locators. Examples of data-plane overhead include address translations in NPTv6 [9] and DRUID [12], and IP-in-IP tunneling in LISP [5] and shim6 [10]. While the control-plane overhead of mapping from identifiers to locators may seem trivial from a bandwidth perspective, it could add operational costs in troubleshooting misconfigurations.…”
Section: Related Workmentioning
confidence: 99%
“…While this concept of locator-identifier split has the above advantages, its disadvantages are that additional actions are required for every data-plane packet, plus controlplane mapping is required between identifiers and locators. Examples of data-plane overhead include address translations in NPTv6 [9] and DRUID [12], and IP-in-IP tunneling in LISP [5] and shim6 [10]. While the control-plane overhead of mapping from identifiers to locators may seem trivial from a bandwidth perspective, it could add operational costs in troubleshooting misconfigurations.…”
Section: Related Workmentioning
confidence: 99%
“…RNA [118] supports non-layered protocol implementations contrary to [116], [117]. It is a framework wherein protocols may be dynamically composed depending on the context relative to the layers below and above.…”
Section: Figmentioning
confidence: 99%
“…The above frameworks adopt modular building blocks to provide flexibility and some [118], [121] adopt a nonlayered structure that enables cross-layer design. In wireless networks, protocols according to the layered architectures may not always provide good performance due to the highly variable nature of wireless links and the resource nature of (mobile) hosts [122].…”
Section: Cross-layer Designmentioning
confidence: 99%
“…Host identity indirection infrastructure (Hi3) [Gurtov et al, 2008] combines secure-I3 and HIP and introduces better multihoming support by introducing identifier layers for service and hosts. Dynamic Recursive Unified Internet Design (DRUID) [Touch et al, 2011] is an architecture where the data, control, management and security planes are unified, so that different planes can act coordinated in the presence of events (attacks, failures, etc). Another proposal with enhanced security support but with limited multihoming capabilities is the Split Naming/Forwarding (SNF) architecture [Jonsson et al, 2003] Hybrid multihoming proposals can follow a map and encapsulation approach as summarized in Table 2.12.…”
Section: Hybrid Multihomingmentioning
confidence: 99%
“…Proposals like Six/One router [Vogt, 2008] are limited as they only apply to IPv6. DRUID [Touch et al, 2011] presents a unified coordination in the presence of events. Despite following Loc/ID split paradigm, DRUID fails to be a complete specification (e.g.…”
Section: Hybrid Multihomingmentioning
confidence: 99%