Proceedings of the ACM SIGCOMM Workshop on Information-Centric Networking 2011
DOI: 10.1145/2018584.2018595
|View full text |Cite
|
Sign up to set email alerts
|

Routing policies in named data networking

Abstract: Modern inter-domain routing with BGP is based on policies rather than finding shortest paths. Network operators devise and implement policies affecting route selection and export independently of others. These policies are realized by tuning a variety of parameters, or knobs, present in BGP. Similarly, NDN, a information-centric future Internet architecture, will utilize a policy-based routing protocol such as BGP. However, NDN allows a finer granularity of policies (content names rather than hosts) and more t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
26
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
6
2
2

Relationship

0
10

Authors

Journals

citations
Cited by 51 publications
(26 citation statements)
references
References 11 publications
0
26
0
Order By: Relevance
“…[15]). Having hundreds of millions of routers implementing routing policies naturally raises scalability concerns; the proposals on content-centric networking with routers implementing policies per content [17] will only aggravate the problem.…”
Section: Related Workmentioning
confidence: 99%
“…[15]). Having hundreds of millions of routers implementing routing policies naturally raises scalability concerns; the proposals on content-centric networking with routers implementing policies per content [17] will only aggravate the problem.…”
Section: Related Workmentioning
confidence: 99%
“…This policy was also adopted in several studies (e.g. [6], [9]), and it mainly aims to minimize the network traffic that crosses other domains because the transit cost is commonly charged according to the traffic volume [19]. In the following, we describe how the CC implements the aforementioned two decisions accordingly:…”
Section: A Caching-related Decisionsmentioning
confidence: 99%
“…One obvious origin of non-aggregatable prefixes is the Internet backbone routing table advertised in CCNcapable BGP [10], because many contents are published under provider-independent prefixes. According to a rough estimate, a full routing table of BGP includes 620 million prefixes, which is the number of web server hostnames as of December 2012 [11].…”
Section: Problems Of Non-aggregatable Prefixesmentioning
confidence: 99%