Optimizing interconnection policies

There are two basic types of interconnection agreements between providers in the Internet: peering and transit. A decision every Internet network service provider (INSP) has to make is which other peering/transit INSPs to connect with. The potential peering/transit partners offer (obviously) differe...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Computer networks (Amsterdam, Netherlands : 1999) Netherlands : 1999), 2004-09, Vol.46 (1), p.19-39
Hauptverfasser: Heckmann, Oliver, Schmitt, Jens, Steinmetz, Ralf
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 39
container_issue 1
container_start_page 19
container_title Computer networks (Amsterdam, Netherlands : 1999)
container_volume 46
creator Heckmann, Oliver
Schmitt, Jens
Steinmetz, Ralf
description There are two basic types of interconnection agreements between providers in the Internet: peering and transit. A decision every Internet network service provider (INSP) has to make is which other peering/transit INSPs to connect with. The potential peering/transit partners offer (obviously) different routes and they may differ quite drastically in the amount and type of charges (line costs, exchange point related costs, settlement costs, administrative costs) they demand as well as in reliability and quality of service. In this article, we discuss and solve problems in this context: the first problem is finding the optimal set of peering and transit partners for one INSP at one point in time, given the routing information and the cost functions of the potential peering/transit partners and the Internet exchange points. Reliability issues (for example enforcing enough spare capacity to absorb the complete failure of one provider) are considered as well as quality of service constraints (e.g., enforcing a certain average AS-hop count). These extended problems are formally described and solved with an optimal algorithm and compared with heuristics. Rates and traffic are in a permanent state of flux, thus an INSP always has to consider whether its current choice of peering/transit partners is still optimal or whether it is worth changing some of its peering/transit agreements. The last part of this article deals with this problem and adapts the algorithm from the first part for this setting.
doi_str_mv 10.1016/j.comnet.2004.03.017
format Article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_57581490</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><els_id>S1389128604000623</els_id><sourcerecordid>679633501</sourcerecordid><originalsourceid>FETCH-LOGICAL-c393t-f79684010e77563add0459d1c119309d4dc0eeb16cf5431a93dae4dc1912d9553</originalsourceid><addsrcrecordid>eNqFkE1LxDAQhoMouK7-Aw-LgrfWTPPVXARZ_IKFveg51CSVlDapSVfQX2-WevKgpxmG5x1mHoTOAZeAgV93pQ6Dt1NZYUxLTEoM4gAtoBZVITCXh7kntSygqvkxOkmpwxmkVb1Al9txcoP7cv5t5fxkow7eWz254Fdj6J12Np2io7bpkz37qUv0cn_3vH4sNtuHp_XtptBEkqloheQ1xYCtEIyTxhhMmTSgASTB0lCjsbWvwHXLKIFGEtPYPAQJlZGMkSW6mveOMbzvbJrU4JK2fd94G3ZJMcFqoBL_C1Y1YZwJmsGLX2AXdtHnJxRIyXm-TGaIzpCOIaVoWzVGNzTxUwFWe7-qU7NftferMFHZb47dzDGblXw4G1XKsry2xsUsUJng_l7wDTPZg9I</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>199661199</pqid></control><display><type>article</type><title>Optimizing interconnection policies</title><source>Access via ScienceDirect (Elsevier)</source><creator>Heckmann, Oliver ; Schmitt, Jens ; Steinmetz, Ralf</creator><creatorcontrib>Heckmann, Oliver ; Schmitt, Jens ; Steinmetz, Ralf</creatorcontrib><description>There are two basic types of interconnection agreements between providers in the Internet: peering and transit. A decision every Internet network service provider (INSP) has to make is which other peering/transit INSPs to connect with. The potential peering/transit partners offer (obviously) different routes and they may differ quite drastically in the amount and type of charges (line costs, exchange point related costs, settlement costs, administrative costs) they demand as well as in reliability and quality of service. In this article, we discuss and solve problems in this context: the first problem is finding the optimal set of peering and transit partners for one INSP at one point in time, given the routing information and the cost functions of the potential peering/transit partners and the Internet exchange points. Reliability issues (for example enforcing enough spare capacity to absorb the complete failure of one provider) are considered as well as quality of service constraints (e.g., enforcing a certain average AS-hop count). These extended problems are formally described and solved with an optimal algorithm and compared with heuristics. Rates and traffic are in a permanent state of flux, thus an INSP always has to consider whether its current choice of peering/transit partners is still optimal or whether it is worth changing some of its peering/transit agreements. The last part of this article deals with this problem and adapts the algorithm from the first part for this setting.</description><identifier>ISSN: 1389-1286</identifier><identifier>EISSN: 1872-7069</identifier><identifier>DOI: 10.1016/j.comnet.2004.03.017</identifier><language>eng</language><publisher>Amsterdam: Elsevier B.V</publisher><subject>Costs ; Interconnect ; Internet ; Internet service providers ; Optimization ; Policy making ; Quality of service ; Routing ; Studies</subject><ispartof>Computer networks (Amsterdam, Netherlands : 1999), 2004-09, Vol.46 (1), p.19-39</ispartof><rights>2004 Elsevier B.V.</rights><rights>Copyright Elsevier Sequoia S.A. Sep 16, 2004</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c393t-f79684010e77563add0459d1c119309d4dc0eeb16cf5431a93dae4dc1912d9553</citedby><cites>FETCH-LOGICAL-c393t-f79684010e77563add0459d1c119309d4dc0eeb16cf5431a93dae4dc1912d9553</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://dx.doi.org/10.1016/j.comnet.2004.03.017$$EHTML$$P50$$Gelsevier$$H</linktohtml><link.rule.ids>314,780,784,3550,27924,27925,45995</link.rule.ids></links><search><creatorcontrib>Heckmann, Oliver</creatorcontrib><creatorcontrib>Schmitt, Jens</creatorcontrib><creatorcontrib>Steinmetz, Ralf</creatorcontrib><title>Optimizing interconnection policies</title><title>Computer networks (Amsterdam, Netherlands : 1999)</title><description>There are two basic types of interconnection agreements between providers in the Internet: peering and transit. A decision every Internet network service provider (INSP) has to make is which other peering/transit INSPs to connect with. The potential peering/transit partners offer (obviously) different routes and they may differ quite drastically in the amount and type of charges (line costs, exchange point related costs, settlement costs, administrative costs) they demand as well as in reliability and quality of service. In this article, we discuss and solve problems in this context: the first problem is finding the optimal set of peering and transit partners for one INSP at one point in time, given the routing information and the cost functions of the potential peering/transit partners and the Internet exchange points. Reliability issues (for example enforcing enough spare capacity to absorb the complete failure of one provider) are considered as well as quality of service constraints (e.g., enforcing a certain average AS-hop count). These extended problems are formally described and solved with an optimal algorithm and compared with heuristics. Rates and traffic are in a permanent state of flux, thus an INSP always has to consider whether its current choice of peering/transit partners is still optimal or whether it is worth changing some of its peering/transit agreements. The last part of this article deals with this problem and adapts the algorithm from the first part for this setting.</description><subject>Costs</subject><subject>Interconnect</subject><subject>Internet</subject><subject>Internet service providers</subject><subject>Optimization</subject><subject>Policy making</subject><subject>Quality of service</subject><subject>Routing</subject><subject>Studies</subject><issn>1389-1286</issn><issn>1872-7069</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2004</creationdate><recordtype>article</recordtype><recordid>eNqFkE1LxDAQhoMouK7-Aw-LgrfWTPPVXARZ_IKFveg51CSVlDapSVfQX2-WevKgpxmG5x1mHoTOAZeAgV93pQ6Dt1NZYUxLTEoM4gAtoBZVITCXh7kntSygqvkxOkmpwxmkVb1Al9txcoP7cv5t5fxkow7eWz254Fdj6J12Np2io7bpkz37qUv0cn_3vH4sNtuHp_XtptBEkqloheQ1xYCtEIyTxhhMmTSgASTB0lCjsbWvwHXLKIFGEtPYPAQJlZGMkSW6mveOMbzvbJrU4JK2fd94G3ZJMcFqoBL_C1Y1YZwJmsGLX2AXdtHnJxRIyXm-TGaIzpCOIaVoWzVGNzTxUwFWe7-qU7NftferMFHZb47dzDGblXw4G1XKsry2xsUsUJng_l7wDTPZg9I</recordid><startdate>20040916</startdate><enddate>20040916</enddate><creator>Heckmann, Oliver</creator><creator>Schmitt, Jens</creator><creator>Steinmetz, Ralf</creator><general>Elsevier B.V</general><general>Elsevier Sequoia S.A</general><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>E3H</scope><scope>F2A</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>20040916</creationdate><title>Optimizing interconnection policies</title><author>Heckmann, Oliver ; Schmitt, Jens ; Steinmetz, Ralf</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c393t-f79684010e77563add0459d1c119309d4dc0eeb16cf5431a93dae4dc1912d9553</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2004</creationdate><topic>Costs</topic><topic>Interconnect</topic><topic>Internet</topic><topic>Internet service providers</topic><topic>Optimization</topic><topic>Policy making</topic><topic>Quality of service</topic><topic>Routing</topic><topic>Studies</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Heckmann, Oliver</creatorcontrib><creatorcontrib>Schmitt, Jens</creatorcontrib><creatorcontrib>Steinmetz, Ralf</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Library &amp; Information Sciences Abstracts (LISA)</collection><collection>Library &amp; Information Science Abstracts (LISA)</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Computer networks (Amsterdam, Netherlands : 1999)</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Heckmann, Oliver</au><au>Schmitt, Jens</au><au>Steinmetz, Ralf</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Optimizing interconnection policies</atitle><jtitle>Computer networks (Amsterdam, Netherlands : 1999)</jtitle><date>2004-09-16</date><risdate>2004</risdate><volume>46</volume><issue>1</issue><spage>19</spage><epage>39</epage><pages>19-39</pages><issn>1389-1286</issn><eissn>1872-7069</eissn><abstract>There are two basic types of interconnection agreements between providers in the Internet: peering and transit. A decision every Internet network service provider (INSP) has to make is which other peering/transit INSPs to connect with. The potential peering/transit partners offer (obviously) different routes and they may differ quite drastically in the amount and type of charges (line costs, exchange point related costs, settlement costs, administrative costs) they demand as well as in reliability and quality of service. In this article, we discuss and solve problems in this context: the first problem is finding the optimal set of peering and transit partners for one INSP at one point in time, given the routing information and the cost functions of the potential peering/transit partners and the Internet exchange points. Reliability issues (for example enforcing enough spare capacity to absorb the complete failure of one provider) are considered as well as quality of service constraints (e.g., enforcing a certain average AS-hop count). These extended problems are formally described and solved with an optimal algorithm and compared with heuristics. Rates and traffic are in a permanent state of flux, thus an INSP always has to consider whether its current choice of peering/transit partners is still optimal or whether it is worth changing some of its peering/transit agreements. The last part of this article deals with this problem and adapts the algorithm from the first part for this setting.</abstract><cop>Amsterdam</cop><pub>Elsevier B.V</pub><doi>10.1016/j.comnet.2004.03.017</doi><tpages>21</tpages></addata></record>
fulltext fulltext
identifier ISSN: 1389-1286
ispartof Computer networks (Amsterdam, Netherlands : 1999), 2004-09, Vol.46 (1), p.19-39
issn 1389-1286
1872-7069
language eng
recordid cdi_proquest_miscellaneous_57581490
source Access via ScienceDirect (Elsevier)
subjects Costs
Interconnect
Internet
Internet service providers
Optimization
Policy making
Quality of service
Routing
Studies
title Optimizing interconnection policies
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-02T22%3A35%3A18IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Optimizing%20interconnection%20policies&rft.jtitle=Computer%20networks%20(Amsterdam,%20Netherlands%20:%201999)&rft.au=Heckmann,%20Oliver&rft.date=2004-09-16&rft.volume=46&rft.issue=1&rft.spage=19&rft.epage=39&rft.pages=19-39&rft.issn=1389-1286&rft.eissn=1872-7069&rft_id=info:doi/10.1016/j.comnet.2004.03.017&rft_dat=%3Cproquest_cross%3E679633501%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=199661199&rft_id=info:pmid/&rft_els_id=S1389128604000623&rfr_iscdi=true