<node id="69301">
  <nid>69301</nid>
  <type>news</type>
  <uid>
    <user id="27174"><![CDATA[27174]]></user>
  </uid>
  <created>1313399554</created>
  <changed>1475896195</changed>
  <title><![CDATA[Study Shows How the Internet's Architecture Got its Hourglass Shape]]></title>
  <body><![CDATA[<p>In the natural world, species that share the same ecosystem often 
compete for resources, resulting in the extinction of weaker 
competitors. A new computer model that describes the evolution of the 
Internet's architecture suggests something similar has happened among 
the layers of protocols that have survived -- and become extinct -- on 
the worldwide network.</p>
<p>Understanding this evolutionary process may help computer scientists 
as they develop protocols to help the Internet accommodate new uses and 
protect it from a wide range of threats. But the model suggests that 
unless the new Internet avoids such competition, it will evolve an 
hourglass shape much like today's Internet.
</p>
<p>"To avoid the ossification effects we experience today in the network
 and transport layers of the Internet, architects of the future Internet
 need to increase the number of protocols in these middle layers, rather
 than just push these one- or two-protocol layers to a higher level in 
the architecture," said Constantine Dovrolis, an associate professor in 
the School of Computer Science at the Georgia Institute of Technology. 
</p>
<p>The research will be presented on Aug. 17, 2011 at SIGCOMM, the 
annual conference of the Special Interest Group on Data Communication, a
 special interest group of the Association for Computing Machinery. This
 research was supported by the National Science Foundation.
</p>
<p>From top to bottom, the Internet architecture consists of six layers: 
</p>
<p>• Specific applications, such as Firefox;<br />
• Application protocols, such as Hypertext Transfer Protocol (HTTP);<br />
• Transport protocols, such as Transmission Control Protocol (TCP);<br />
• Network protocols, such as Internet Protocol (IP);<br />
• Data-link protocols, such as Ethernet; and<br />
• Physical layer protocols, such as DSL.
</p>
<p>Layers near the top and bottom contain many items, called protocols, 
while the middle layers do not. The central transport layer contains two
 protocols and the network layer contains only one, creating an 
hourglass architecture.
</p>
<p>Dovrolis and graduate student Saamer Akhshabi created an evolutionary
 model called EvoArch to study the emergence of the Internet's hourglass
 structure. In the model, the architecture of the network changed with 
time as new protocols were created at different layers and existing 
protocols were removed as a result of competition with other protocols 
in the same layer.
</p>
<p>EvoArch showed that even if future Internet architectures are not 
built in the shape of an hourglass initially, they will probably acquire
 that shape as they evolve. Through their simulations, Dovrolis and 
Akhshabi found that while the accuracy of the structure improved with 
time, the basic hourglass shape was always formed -- no matter what 
shape it started in.
</p>
<p>"Even though EvoArch does not capture many practical aspects and 
protocol-specific or layer-specific details of the Internet 
architecture, the few parameters it is based on -- the generality of 
protocols at different layers, the competition between protocols at the 
same layer, and how new protocols are created -- reproduced the observed
 hourglass structure and provided for a robust model," said Dovrolis.
</p>
<p>The model revealed a plausible explanation for the Internet's 
hourglass shape. At the top, protocols are so specialized and selective 
in what underlying building blocks they use that they rarely compete 
with each other. When there is very little competition, the probability 
of extinction for a protocol is close to zero. 
</p>
<p>"In the top layers of the Internet, many new applications and 
application-specific protocols are created over time, but few things 
die, causing the top of the hourglass to get wider over time," said 
Dovrolis.
</p>
<p>In the higher layers, a new protocol can compete and replace an 
incumbent only if they provide very similar services. For example, 
services provided by the File Transfer Protocol (FTP) and HTTP 
overlapped in the application-specific layer. When HTTP became more 
valuable because of its own higher layer products -- applications such 
as web browsers -- FTP became extinct.
</p>
<p>At the bottom, each protocol serves as a general building block and 
shares many products in the layer above. For example, the Ethernet 
protocol in the data-link layer uses the coaxial cable, twisted pair and
 optical fiber technologies in the physical layer. But because the 
bottom layer protocols are used in an abundant way, none of them 
dominate, leading to a low probability of extinction at layers close to 
the bottom. 
</p>
<p>The EvoArch model predicts the emergence of few powerful and old 
protocols in the middle layers, referred to as evolutionary kernels. The
 evolutionary kernels of the Internet architecture include IPv4 in the 
network layer, and TCP and the User Datagram Protocol (UDP) in the 
transport layer. These protocols provide a stable framework through 
which an always-expanding set of physical and data-link layer protocols,
 as well as new applications and services at the higher layers, can 
interoperate and grow. At the same time, however, those three kernel 
protocols have been difficult to replace, or even modify significantly.
</p>
<p>To ensure more diversity in the middle layers, EvoArch suggests 
designing protocols that are largely non-overlapping in terms of 
services and functionality so that they do not compete with each other. 
The model suggests that protocols overlapping more than 70 percent of 
their functions start competing with each other.
</p>

<p>When the researchers extended the EvoArch model to include a protocol
 quality factor -- which can capture protocol performance, extent of 
deployment, reliability or security -- the network grew at a slower 
pace, but continued to exhibit an hourglass shape. In contrast to the 
basic model, the quality factor affected the competition in the bottom 
layers and only high-quality protocols survived there. The model also 
showed that the kernel protocols in the waist of the hourglass were not 
necessarily the highest-quality protocols.</p>
<p>"It is not true that the best protocols always win the competition," 
noted Dovrolis. "Often, the kernels of the architecture are 
lower-quality protocols that were created early and with just the right 
set of connections."</p><p>Researchers are also using the EvoArch model to explore the emergence
 of hourglass architectures in other areas, such as metabolic and gene 
regulatory networks, the organization of the innate immune system, and 
in gene expression during development. 
</p>
<p>"I believe there are similarities between the evolution of Internet 
protocol stacks and the evolution of some biological, technological and 
social systems, and we are currently using EvoArch to explore these 
other hourglass structures," said Dovrolis.
</p>
<p><em>This project is supported by the National Science Foundation 
(NSF) (Award No. 0831848). The content is solely the responsibility of 
the principal investigator and does not necessarily represent the 
official views of the NSF.</em>
</p>
<p><strong>Research News &amp; Publications Office<br />
Georgia Institute of Technology<br />
75 Fifth Street, N.W., Suite 314<br />
Atlanta, Georgia  30308  USA
</strong></p><p><strong>
</strong></p><p><strong>Media Relations Contacts</strong>: John Toon (404-894-6986)(<a href="mailto:jtoon@gatech.edu">jtoon@gatech.edu</a>) or Abby Robinson (404-385-3364)(<a href="mailto:abby@innovate.gatech.edu">abby@innovate.gatech.edu</a>).
</p>
<p><strong>Writer</strong>: Abby Robinson
</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2011-08-15T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>A new computer model designed by Constantine Dovrolis (<em>Computer Science</em>) that describes the evolution of the Internet's architecture suggests a process similar to natural evolution took place to determine which protocols survived and which became extinct. <em>Source: GT Research News</em></p>]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="50659">
            <nid>50659</nid>
            <type>image</type>
            <title><![CDATA[Constantine Dovrolis]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>128787</fid>
                  <filename><![CDATA[constantine-dovrolis.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/images/constantine-dovrolis_1.jpg]]></filepath>
                  <file_full_path><![CDATA[http://www.tlwarc.hg.gatech.edu//sites/default/files/images/constantine-dovrolis_1.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Constantine Dovrolis]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[College of Computing]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>439</tid>
        <value><![CDATA[computer]]></value>
      </item>
          <item>
        <tid>13398</tid>
        <value><![CDATA[Constantine Dovrolis]]></value>
      </item>
          <item>
        <tid>13994</tid>
        <value><![CDATA[Internet architecture]]></value>
      </item>
          <item>
        <tid>1385</tid>
        <value><![CDATA[network]]></value>
      </item>
          <item>
        <tid>13995</tid>
        <value><![CDATA[protocol]]></value>
      </item>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
