Shared versus separate networks: The impact of reprovisioning

Soumya Sen, Roch Guérin, Kartik Hosanagar

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

As networks improve and new services emerge, questions arise that affect service deployments and network choices. The Internet is arguably a successful example of a network shared by many services. However, combining heterogeneous services on the same network need not always be the right answer, and technologies such as virtualization make deploying new services on separate networks increasingly more viable. So, which is the right option? The question is not unique to networks, and there is a large body of work in the manufacturing systems literature that explores the trade-off between flexible and dedicated plants. This paper highlights an important feature missing from these earlier works, namely, the ability to ''reprovision'' resources in response to changes in demand. It demonstrates that this feature alone can affect the choice of network solutions, and argues for models that incorporate it.

Original languageEnglish (US)
Title of host publicationProceedings of the 2009 ACM Conference on Emerging Networking Experiments and Technologies, CoNEXT'09 - Co-located 2009 Workshop on Re-Architecting the Internet, ReArch'09
Pages73-78
Number of pages6
DOIs
StatePublished - Dec 1 2009
Event2009 Workshop on Re-Architecting the Internet, ReArch'09 - Rome, Italy
Duration: Dec 1 2009Dec 4 2009

Publication series

NameProceedings of the 2009 ACM Conference on Emerging Networking Experiments and Technologies, CoNEXT'09 - Co-located 2009 Workshop on Re-Architecting the Internet, ReArch'09

Other

Other2009 Workshop on Re-Architecting the Internet, ReArch'09
Country/TerritoryItaly
CityRome
Period12/1/0912/4/09

Keywords

  • Network services
  • Resource allocation
  • Virtualization

Fingerprint

Dive into the research topics of 'Shared versus separate networks: The impact of reprovisioning'. Together they form a unique fingerprint.

Cite this