2012
DOI: 10.1109/mic.2012.98
|View full text |Cite
|
Sign up to set email alerts
|

Designing a Deployable Internet: The Locator/Identifier Separation Protocol

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
35
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 39 publications
(35 citation statements)
references
References 6 publications
0
35
0
Order By: Relevance
“…Routing Locators (RLOCs) assignment is topology-based and is utilized to forward data and route data in the network. On the other hand, Endpoint Identifiers (EIDs) are topology independent and are utilized for numbering [12]. It enhanced routing system scalability by utilizing topologically dependent Routing Locators (RLOCs) [12].…”
Section: Related Protocolsmentioning
confidence: 99%
“…Routing Locators (RLOCs) assignment is topology-based and is utilized to forward data and route data in the network. On the other hand, Endpoint Identifiers (EIDs) are topology independent and are utilized for numbering [12]. It enhanced routing system scalability by utilizing topologically dependent Routing Locators (RLOCs) [12].…”
Section: Related Protocolsmentioning
confidence: 99%
“…LISP [10] is an architectural solution to the Internet's scalability problem, recently generated by the alarming growth of inter-domain routing tables [30]. To this end, LISP's main goal is to split the semantics of IP addresses with the aim of forming two namespaces that unambiguously identify core (locators) and edge (identifiers) network objects.…”
Section: Lisp Backgroundmentioning
confidence: 99%
“…This approach is complementary to existing ALM solutions as it aims to offer overlay management control to network operators in exchange for improved reliability and more efficient network resource use but at the cost of minimal infrastructure support. To achieve our goal, we exploit a unique window of opportunity offered by the development and deployment of the Locator/ID Separation Protocol (LISP) [10], a protocol meant to improve the current routing infrastructure, which we use as support for our proposal. In light of the intrinsic dependency on LISP, we refer to our solution as LISPcasting or shortly, Lcast.…”
Section: Introductionmentioning
confidence: 99%
“…The Locator/IDentifier Separation Protocol (LISP) ( [6], [7] separates the identification and localization roles of IP addresses by introducing two logical addressing spaces: (i) the Routing LOCator space (RLOC), that is globally routable; (ii) the Endpoint IDentifier space (EID), that is only locally routable. With this separation, the Internet core, also known as Default Free Zone (DFZ), handles RLOCs addresses like it is done today, i.e., maintaining routes so that packets can be forwarded between any router within the DFZ.…”
Section: A Lisp Data Planementioning
confidence: 99%
“…. [5]) and those associating locators to routers (e.g., LISP [6], [7]). It is worth to notice that, in the current Internet architecture, end-systems' IP addresses have a dual semantic, being at the same time identifier of communication endpoints and locator of these endpoints in the Internet topology.…”
Section: Introductionmentioning
confidence: 99%