Supporting Dynamic Inter-Domain Network Composition: Domain discovery

Vitor Jesus*, Rui L. Aguiar, Peter Steenkiste

*Corresponding author for this work

Research output: Chapter in Book/Published conference outputConference publication

1 Citation (Scopus)

Abstract

When two administratively independent domains need to engage in cooperation of some kind, some initial common known point of contact must exist, both in terms of the application topological position (i.e., IP address, transport protocol and port) and in terms of the interface technology (e.g., the protocol suite of the interaction). In a world of many domains of many types (not necessarily Autonomous Systems in the sense of interdomain routing), manual or single-directory-based operations are not practical (or even feasible); hence, some form of autonomic discovery and handshaking of domains is needed. We propose and evaluate several strategies to allow autonomic bootstrapping of inter-domain operations, all fit to be deployed as BGP extensions. We show the time/message overhead tradeoff: it's possible to obtain the absolute minimum message complexity of O(N) but at the cost of central administrative burden or, for fully distributed schemes, a tradeoff (message/time complexity) of O(N 2)/O(N) or O(N2)/O(log2N).

Original languageEnglish
Title of host publicationProceedings - 2009 IEEE International Conference on Communications
Number of pages6
DOIs
Publication statusPublished - 2009
Event2009 IEEE International Conference on Communications, ICC 2009 - Dresden, Germany
Duration: 14 Jun 200918 Jun 2009

Publication series

Name
ISSN (Print)1550-3607
ISSN (Electronic)1938-1883

Conference

Conference2009 IEEE International Conference on Communications, ICC 2009
Country/TerritoryGermany
CityDresden
Period14/06/0918/06/09

Keywords

  • Autonomic networks
  • Inter-domain
  • Inter-domain service discovery

Fingerprint

Dive into the research topics of 'Supporting Dynamic Inter-Domain Network Composition: Domain discovery'. Together they form a unique fingerprint.

Cite this