<?xml version="1.0" encoding="utf-8"?>

<!-- 
     draft-mcfadden-consolidation-taxonomy-04
-->

<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema validation and schema-aware editing -->
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->

<!DOCTYPE rfc [
<!ENTITY nbsp    "&#160;">
<!ENTITY zwsp   "&#8203;">
<!ENTITY nbhy   "&#8209;">
<!ENTITY wj     "&#8288;">
]>

<rfc 
  xmlns:xi="http://www.w3.org/2001/XInclude" 
  category="info" 
  docName="draft-mcfadden-consolidation-taxonomy-04" 
  ipr="trust200902" 
  obsoletes="" 
  updates="" 
  sortRefs="true" 
  submissionType="IETF" 
  xml:lang="en" 
  tocDepth="4" 
  symRefs="true" 
  version="3">

<!-- front matter -->
  <front>
    <title abbrev="Taxonomy of Consolidation">A Taxonomy of Internet Consolidation</title>
    <seriesInfo name="Internet-Draft" value="draft-mcfadden-consolidation-taxonomy-04" />

    <author fullname="Mark McFadden" initials="M." role="editor" surname="McFadden">
      <organization>internet policy advisors, ltd</organization>
      <address>
        <postal>
          <street>6 Bridge Street</street>
          <city>Chepstow</city>
          <code>NP16 5EY</code>
          <country>UK</country>
          <!-- Uses two letter country code -->
        </postal>
        <phone>+1 608 504 7776</phone>
        <email>mark@internetpolicyadvisors.com</email>
      </address>
    </author>
    
    <date year="2024" />
    <area>General</area>
    <workgroup>Internet Engineering Task Force</workgroup>
    <keyword>internet consolidation</keyword>
    
    <abstract>
      <t>This document contributes to the ongoing discussion surrounding Internet consolidation. At recent IETF meetings discussions about Internet consolidation revealed that different perspectives gave completely different views of what consolidation means. While we use the term consolidation to refer to the process of increasing control over Internet infrastructure and services by a small set of organizations, it is clear that that control is expressed through economic, network traffic and protocol concerns. As a contribution to the discussion surrounding consolidation, this document attempts to provide a taxonomy of Internet consolidation with the goal of adding clarity to a complex discussion.</t>
    </abstract>
    
  </front>
<!-- end front matter -->  

<!-- Main Draft Text -->

  <middle>
    <section numbered="true" toc="default">
      <!-- This is the start of Section 1 -->
      <name>Introduction - Why a Taxonomy?</name>
      <t>Internet consolidation has been under discussion for the last several years. The 2019 Internet Society's "Global Internet Report: Consolidation and the Internet Economy" highlighted issues on this topic and kicked started a series of discussions and publications around consolidation.  The DINRG Workshop on Centralization took place in June of 2021 and was reported on at IETF 114<xref target="DINRG"/>. Furthermore, a draft for the Internet Architecture Board (IAB) discussed issues of economic and technical consolidation<xref target="IABwrkshp"/>.  Despite community interest, the draft expired without further work or publication.</t>
      <t>Several other contributions have focused on responses to consolidation. However, the report from the DINRG Workshop makes clear that there are different "categories of centralization." This draft does not attempt to propose responses to centralization, instead it attempts to build upon the Workshop's summary of "categories of centralization" with a goal of supporting future work and discussion.</t>
      <!-- This is the end of Section 1 -->
    </section>
    
    <section numbered="true" toc="default">
      <!-- This is the start of Section 2 -->
      <name>Toward a Definition of Consolidation</name>
      <t>There's a reason that concerns have been expressed about the "definition" of centralization. Centralization has seen many attempts to define "centralization." In a now expired Internet-Draft, one definition was "the process of increasing control over internet infrastructure and services by a small set of organizations." <xref target="Arrko1"/> A more recent RFC uses the following definition: "centralization" is the state of affairs where a single entity or a small group of them can observe, capture, control, or extract rent from the operation or use of an Internet function exclusively."<xref target="RFC9518"/></t>
      <t>This is not simply a recent trend. Dmytri Kleiner views the situation as primarily economic and notes that the dot com boom "was characterized by a rush to own infrastructure, to consolidate independent internet service providers and take control of the network." He describes the environment in the early 2000s as a sort of economic land rush where investors tried to replace the smaller service vendors with larger ones on every scale, from low level telecommunications infrastructure to high level services such as news aggregation, e-mail and video.<xref target="Kleiner"/></t>
      <t>Taking as a starting point the centralization of DNS services, there have also been studies of what centralization means in the context of key Internet services. For instance, one academic study found that about 12,000 name servers used by websites in the Alexa top 1 million used exactly the same third-party infrastructure.<xref target="DNSmeasure"/> This finding led to the proposal of a metric for measuring the market share of organizations that provide DNS resolvers.<xref target="Entropy"/> In this case, the authors implicitly provide definitions of "centralization" based on external metrics.</t>
      <t>A completely different approach to the definition of consolidation can be seen by looking at research that focuses on the consolidation of data instead of economic measures.<xref target="DataConsolidation"/> In one study the authors state, "as users get used to using their services, the users' generated content and the data about their online behaviors are concentrated in such companies. This phenomenon, called "data consolidation", has become a serious problem, which makes the Internet society seek to decentralize the current Internet. The decentralized Internet aims to prevent the concentration of user data in a few giant companies."<xref target="ISOCconsolidation"/> This approach to centralization isn't an isolated research activity. Another study surveys the ongoing research activities on "data centralization" from the Internet Society, EU Horizon-2020, and Decentralized web.</t>
      <t>The key problem is that "centralization" means different things in different contexts. Research takes on various topics including economic, network and data centralization. As a result the guidance from the DINRG workshop seems to have an important message for those who would like to see a single definition of centralization: there are "categories" of centralization, each with its own definition.<xref target="DINRG"/></t>
      <t>Note that this draft does not attempt to define the concept of intermediation.<xref target="RFC3724"/> In general, an intermediary is a communications participant that is not the primary initiator of communications or the intended recipient of that communication. Intermediation is familiar from the examples of search engines: a search engine is a important tool in helping to scale the Internet by helping users find and identify relevant content in an ever-growing ocean of information. As an intermediary, the search engine places itself between the user and the rest of the Internet. Unfortunately, the intermediary can be accessed directly by the user, or embedded structurally - for instance through algorithims that sift, filter or rate content on behalf of the user. Obviously, such intermediation gives power to those who operate it - with content and information flowing from both sides of the connection. It is possible to argue that today's Internet is impossible without intermediaries (for instance, proxies in HTTP or SIP).<xref target="RFC8517"/> However, controlling the level of participation and access that intermediaries have is a fundamental security issue. Lack of propoer controls on intermediatires in ptotocols is the source of significant security problems.
      </t>
      <t>It is also important to note that metrics for intermediation and centralization show that, while there is a high degree of variability globally for centralization, research suggests a highly concentrated market of third-party providers: three providers, globally, serve an average of 92 percent of all websites, and Google, by itself, serves an average of 70 percent of recently surveyed websites.<xref target="Pace"/>
      </t>
      <!-- This is the end of Section 2 -->
    </section>
    
    <section numbered="true" toc="default">
      <!-- This is the start of Section 3 -->
      
      <name>Background to Consolidation Issues</name>
      <t>Internet consolidation is defined in one setting as "the process of increasing control over internet infrastructure and services by a small set of organizations." <xref target="RFC8890"/>  Economy of scale is the driving force behind consolidation because markets naturally consolidate when economies of scale come into play.</t>
      <t>The DINRG Workshop Report notes that:</t>
      <ul>
      <li>the economy of scale enables one to generate the same service outcome with far lower production costs, and consume fewer resources for each instance of the service transaction.</li>
      <li>a large user pool produces big data which helps improve service customization for each user, letting bigger companies gain an edge over smaller competitors.</li>
      <li>centralized application developments reduce the number of platforms, hence substantially reduce the cost in development and maintenance, and circumvent interoperability issues. Consolidated development and operational efforts also help mitigate technical expertise shortages.</li>
      <li>most of all, monopoly players can dictate to the market the terms of the service and the service price bought to the market, which causes longer term stagnation of the market and increased inefficiency within the market, which acts as a drag on further innovation.</li>
      </ul>
      <t>The current consolidation and centralization of control and operation of Internet infrastructure and services was not an original design goal. In fact, RFC1958 says:</t>
      <ul><li>
      "This allows for uniform and relatively seamless operations in a competitive, multi-vendor, multi-provider public network."
      </li></ul>
      <t>and later,</t>
      <ul><li>
      "Heterogeneity is inevitable and must be supported by design."<xref target="RFC1958"/>
      </li></ul>
      <t>In fact RFC8280<xref target="RFC8280"/> explicitly asks key questions about centralization of protocols in the context of human rights:
      </t>
      <ul>
      <li>Can your protocol be implemented without one single point of control?</li>
      <li>If applicable, can your protocol be deployed in a federated manner?</li>
      <li>What is the potential for discrimination against users of your protocol?</li>
      <li>Can your protocol be used to negatively implicate users (e.g., incrimination, accusation)?</li>
      <li>Does your protocol create additional centralized points of
      control?</li>
      </ul>
      <t>The notion of centrality is essential to a consideration of any potential taxonomy. In the realm of graph theory and network analysis, centrality indicators are pivotal tools that quantitatively assess the importance of nodes within a graph based on their position in the network. These indicators assign numerical values or rankings to nodes, facilitating the identification of influential entities across diverse applications. Examples include pinpointing key figures in social networks, critical nodes in infrastructural networks in urban systems, pivotal individuals in disease transmission dynamics, and nodes crucial to understanding brain network functionality. A similar notion of centrality for the Internet can be formulated based on the quantitative analysis of particular intermediaries in Internet sessions.
      </t>
      <t>Much of the discussion surrounding consolidation focuses on Internet services, applications and data. However, contributions to the discussion of consolidation have also addressed economic, traffic and architectural consolidation. The concentration of Internet traffic, infrastructure, services, and users on a handful of providers is a growing concern because of the economic, political, and reliability implications of these consolidation trends. In recognition of this, a taxonomy with four main categories is proposed:</t>
      <ul>
      <li>Economic Consolidation</li>
      <li>Traffic and Infrastructure Consolidation</li>
      <li>Architectural Consolidation</li>
      <li>Service and Application Consolidation</li>
      </ul>
      
      <!-- This is the end of Section 3 -->
    </section>
    
    <section numbered="true" toc="default">
      <name>Economic Consolidation</name>
      <!-- This is the start of Section 4 -->
      <t>The Internet Society Report on Internet Consolidation suggests that the Internet's economy is defined as the economic activities that either support the Internet or are fundamentally dependent on the Internet's existence.<xref target="ISOCconsolidation"/></t>
      <t>As a result, economic consolidation on the Internet refers to the effects of market consolidation on competition and the economic power of a small set of companies that dominate economic activity in the Internet. There are two aspects to economic consolidation on the Internet.</t>
      <t>Economic consolidation means that a small number of companies dominate the marketplace and hence, the revenues gathered from the use of the Internet.</t>
      <t>Economic consolidation also means that a small number of companies control the flow of capital among enterprises that provide services on the Internet.</t>
      <t>The Internet Society also argues that there are two views of market consolidation in the Internet. In the first the metric is the concentration of providers in a given marketplace. In the second, it is the jusridiction of providers in a given market. It uses a pair of metrics ( the GINI coefficient and the Herfindahl=Hirschman Index (HHI) ) to measure market consolidation. 
      </t>
      <section numbered="true" toc="default">
        <!-- This is the start of Section 4.1 -->
        <name>4.1. Economic Revenue Consolidation</name>
        <t>One of the two aspects of economic consolidation is the generation of revenue by a small number of enterprises. As an example, Amazon accounts for more than 45% of all online retail spending in the United States. Alibaba is estimated to have 60% or the electronic commerce market in China. Meta - including Facebook, Messenger, WhatsApp and Instagram - dominates social media and messaging holding four of the world's top six social media platforms.</t>
        <t>In each of these cases, a very small number of companies operate extremely popular services, concentrating revenue generation into those companies. In fact, the popularity of these services is so great that value is created by adding other, complementary services onto the base they provide. The dominant services thus control the foundation upon which other revenue streams are built.,xref target="EmpiricalView"/></t>
        <t>The impact of revenue consolidation is enhanced by the presence of network effects in digital media and services. A network effect is market feature where the benefit to the user or consumer of a product or service increases as the number of other users increases. First-mover advantages play a role in defining the marketplace, but as a product or service gains traction and sees its market grow, the user base becomes the foundation for future growth.</t>
        <t>An example of this would be the dominance of the portable document format, originally introduced by Adobe. As the number of users grew, it became the dominant format for the exchange of documents readable on a variety of devices. While the network effect does not imply immediate or inevitable market dominance, it does seem to be tightly correlated with market leaders in digital, Internet-based services.</t>
      </section>
      <section numbered="true" toc="default">
        <!-- This is the start of Section 4.2 -->
        <name>4.2. Economic Flow Consolidation</name>
        <t>In addition to revenue generation, the very large application layer companies (Alphabet, Amazon, Tencent, Meta and Alibaba) control how money and capital moves through enterprises providing services on the Internet.</t>
        <t>We have seen that embedded intermediaries that have substantial power can implement platforms that provide services to downstream consumers as well as upstream sources of content and applications. As the controlling intermediary for those services and applications, these large companies are also able to dictate how economic flows move between consumers and providers of applications and services.</t>
        <t>Regulators and policy makers often are concerned about the enormous market power that these huge intermediaries have, but refrain from imposing controls or sanctions on the grounds that consumers get significant benefits when platform operators use upstream revenues to subsidize downstream services.</t>
        <t>That control is often influenced by the fact that an enormous amount of the economic flow related to the Internet occurs largely out of public sight. Advertising is a critical part of the economic flow of the Internet. Advertisers want their message to reach the broadest community of potential consumers possible. As a result, advertising platforms need to be built to provide services to the greatest number of potential advertisers. The greater the reach of the advertising platform, the greater the value to the advertiser. The result, on the Internet, is a trend to collect the advertising tools in a consolidated group of global, dominant enterprises.</t>
        <t>The end user sees free tools, services and information. However, the cost of those services is paid for, largely, by advertising revenue that makes up a vast proportion of the economic flow of the Internet.</t>
      </section>
      
      <!-- This is the end of Section 4 -->
    </section>
    
    <section numbered="true" toc="default">
      <!-- This is the start of Section 5 -->
      
      <name>Traffic and Infrastructure Consolidation</name>
      <t>A significant majority of the Internet's traffic is delivered from very large content services including Google, Amazon and Facebook. These companies naturally attempt to provide the best possible service for their customers - including perceived speed of content delivery - these content services seek to establish connections directly with the companies providing access to the network. The result is a "flattening" of the Internet's traditional topology.</t>
      <t>In fact, a recent study shows that these large services can reach more than 76% of the Internet without having to traverse traditional Tier 1 and Tier 2 ISPs. Besides bringing benefits of low latency and higher security to their users, these large-scale networks are also able to implement improvements and innovations in protocol design by having far greater control over the elements of the infrastructure being used to deliver services.</t>
      <t>An empirical view of this consolidation in February of 2022 shows that the number of webpages that are hosted on these networks has increased from 2015 to 2020 at a rate exceeding 80%. In looking at data sources including TLD datasets and Alexa Top 1M datasets only a small number of content delivery networks host the vast majority of landing pages.</t>
      <t>Centralization of this sort makes traffic filtering easier since forcing a content network to block specific content (or worse, blocking the content network entirely) would make a large amount of the content unavailable. As these networks begin to migrate other services to HTTP (for instance, DNS over HTTP), more than the web is affected by the impacts of filtering by centralized content services. In fact, blocking a content network entirely would block all the content of the network, not just the content that was the target of the filtering.</t>
      <t>This happens at all layers. As an example at the application layer, in 2021 Google and Apple were forced to remove applications created by the Russian political opposition from their stores. The ability of a government to influence the content network means that centralization can lead to a reduction in the diversity of information or services on the Internet.</t>
      <t>As the content networks grow in scale, the networks themselves grow to support the required network capacity. This sets up a feedback look that drives market concentration toward the infrastructure provided by the content networks. As these networks grow larger, it becomes difficult for smaller networks and infrastructure providers to compete with the economies of scale from which the large networks benefit. </t>
      
      <!-- This is the end of Section 5 -->
    </section>
    
    <section numbered="true" toc="default">
    
      <!-- This is the start of Section 6 -->
      
      <name>Architectural Consolidation</name>
      <t>A third category of consolidation is the evolution of the Internet's architecture to meet contemporary use cases and requirements. Early descriptions of the Internet's architecture described heterogeneous endpoints connected by neutral transports. The end-to-end principle suggested that the transport of data between endpoints was provided without much intervention. <xref target="RFC1958"/></t>
      <t>Two developments have led to architectural consolidation: the emergence of intermediary services and the movement of transport related code to the application layer.</t>
      <section numbered="true" toc="default">
        <!-- This is the start of Section 6.1 -->
        <name>The Rise of Intermediaries</name>
        <t>In the first case, technologies like CDNs are built into the network for the efficient delivery of content and services. The consumer is largely unaware that the service or application is being hosted by an organization other than they one they think they contacted. Instead, content delivery is pushed as close to the consumer as possible to ensure that the end-user experience is as optimal as possible.</t>
        <t>The result is a series of security, economic and policy concerns associated with the small number of very large providers of these intermediary services. However, in this section we only want to consider the architectural issues specific to the use of intermediaries.</t>
      </section>
      <section numbered="true" toc="default">
        <!-- This is the start of Section 6.2 -->
        <name>Vertical Architectural Consolidation</name>
        <t>The second case is vertical architectural consolidation. This is where the companies that control the applications attempt to control all aspects of the communication. For instance, the provider of the browser may be the organization that the browser connects to. The advantage of this kind of architectural consolidation is that it allows the largest players to introduce technological innovation more quickly than if multiple layers of the stack required innovation in parallel.</t>
        <t>With tools like DNS over HTTPS, we see applications taking control of the infrastructure of transport in addition to providing an application or service. Applications essentially provide their own ecosystem (from centralized control of DNS services all the way to the end-user experience).</t>
      </section>
      <section numbered="true" toc="default">
      <!-- This is the start of Section 6.3 -->
      <name>Standards Development</name>
      <t>Others have rightly observed that, in the current environment, development of protocols and standards for the Internet is largely confined to a small number of participants from a small number of organizations. One trend is that the giant enterprises on the Internet also dominate the development of protocols.</t>
      <t>Having a small number of organizations controlling the infrastructure of the Internet also means that innovative technologies can be implemented quickly and at large-scale. In 2022, a study in the ACM Transactions on Internet Technology found that Google accounting for 60% of all TLS 1.3 secured resources. Some other, large CDNs use TLS 1.3 almost exclusively. QUIC is also an example of a new technology that profits from consolidation. Large scale intermediaries can facilitate the deployment and adoption of new standards because the decision for the adoption is propagated across the infrastructure instead of through user adoption or feature updates.</t>
      </section>
      
      <!-- This is the end of Section 6 -->
    </section>
    
    <section numbered="true" toc="default">
    
      <!-- This is the start of Section 7 -->
      
      <name>Service and Application Consolidation</name>
      <t>Services and applications are those tools that users see when they interact with the Internet. They take advantage of the infrastructure (and, access) parts of the Internet's ecosystem. According to the Internet Society's report on consolidation, "a small number of companies operating some of the Internet's most popular services dominate this market. Many of these companies act as multi-sided markets or platforms, meaning they offer a base upon which other applications, processes or technologies can be developed."</t>
      <t>By itself, Google holds 90% of the global search market, the number one mobile operating system (Android), the top-user-generated video platform and has more than 1.5 billion active users of its Gmail email service. Google also has a map service, a public DNS resolver service, a cloud service and a document store.</t>
      <t>While twenty years ago, an application would simply rely on the underlying operating system to provide its communications and transport services, now applications and services do this for themselves. This is a case of the intermediary or platform providing the application integrating all the necessary components for providing a service on the Internet.</t>
      <!-- This is the end of Section 7 -->
      
    </section> 
    
    <section numbered="true" toc="default">
    
      <!-- This is the start of Section 8 -->
      
      <name>Other Considerations</name>
      <t>Some extremely useful research (from a variety of academic institutions including the University of Illinois, the Unversity of California at Berkeley, the Oxford Internet Institute and the London School of Economics)has documented that there is extreme centralization in the area of Internet jurisdiction.</t>
      <t>In the first case, numerous national laws are designed to have extraterritorial impact, extending their reach to individuals or corporations beyond the enacting state's borders. This practice has a long history predating the Internet, but its implications are amplified by the inherently cross-border nature of digital networks. Additionally, some nations are increasingly motivated to assert control over the Internet, further intensifying these effects. The intersection of global connectivity and national regulatory ambitions creates a complex legal landscape, where the extraterritorial application of laws can lead to significant jurisdictional challenges and conflicts. As countries strive to enforce their legal frameworks in the digital realm, the tension between national sovereignty and the borderless nature of the Internet becomes more pronounced, highlighting the need for international cooperation and dialogue to navigate these issues effectively. </t>
      <t>In the second case, the landscape for jurisdiction for dispute resolution is often dictated by the provider of the service. Research shows that, despite the desire of many governments to pursue national soveriegnty, jurisdiction for dispute resolution is dominated by a single nation. Rather than have the jurisdiction be in the country of the consumer of the service, the jurisdiction is determined by the provider.</t>
      <t>In both of these cases, the risk is that policy makers will use this inequity as a reason to impose rules that spill over on to the Internet elsewhere, with potential unintended effects</t>
      <t>It has also been observed that there is a paradox concerning the physical infrastructure of the Internet. The physical infrastructure of the Internet has never been more diverse: the kinds and numbers of devices connected continues to grow at exponential rates. However, the network management infrastructure of the Internet continues to be significantly centralized. This paradox is, perhaps, a feature of architectural consolidation discussed above.</t>
      
      <t>Finally, and separately from protocol related consolidation, there is the concept of data centralization: the idea that information is captured and stored by large organizations - possibly without the consent of the indivudals or organizations that have generated the data. There is evidence of a growing body of concern related to data centralization and the public policy implications of that centralization. However, that concern is beyond the scope of this draft.</t>
      
      <!-- This is the end of Section 8 -->
    </section>
    
    <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
    
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>While this document does not describe a specific protocol, it does discuss the evolving architecture of the Internet. Changes to the Internet's architecture have direct and indirect implications for the Internet's threat model. Specifically, the changes to the end-to-end model (see section 6 above) have inserted new interfaces which must be reflected in security considerations for new protocols.</t>
    </section>
    
    <section numbered="true" toc="default">
      <name>Conclusions</name>
      <t>This document seeks to rekindle and restart the discussion on consolidation. As argued above, Internet consolidation is happening at different places and different layers of the Internet. Though there has been interest in the Internet consolidation in the past, now is the time to start the discussions again.</t>
      <t>The author is particularly grateful for comments received on this draft in the wake of a presentation at IETF 118.</t>
    </section>
    
  <!-- End of the Main Draft Text -->
    
  </middle>
  
  <back>
    <references>
      <name>References</name>
      
      <references>
        <name>Informative References</name>
        
        <reference anchor="Arrko1" target="https://datatracker.ietf.org/doc/html/draft-arkko-arch-infrastructure-centralisation-00">
          <front>
            <title>Considerations on Internet Consolidation and the Internet Architecture </title>
            <author initials="J." surname="Arrko">
              <organization />
            </author>
            <date year="2019" />
          </front>
        </reference> 
        
        <reference anchor="RFC9518" target="https://www.rfc-editor.org/info/rfc9518">
        <front>
            <title>Centralization, Decentralization, and Internet Standards</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="December" year="2023"/>
            <abstract>
                <t>This document discusses aspects of centralization that relate to Internet standards efforts. It argues that, while standards bodies have a limited ability to prevent many forms of centralization, they can still make contributions that assist in the decentralization of the Internet.</t>
            </abstract>
        </front>
        <seriesInfo name="RFC" value="9518"/>
        <seriesInfo name="DOI" value="10.17487/RFC9518"/>
        </reference>
        
        <reference anchor="Kleiner">
	  <front>
	    <title>The Telekommunist Manifesto</title>
	    <author initials="D." surname="Kleiner">
            <organization />
	    </author>
	    <date year="2022" />
	  </front>
	</reference>
	
        <reference anchor="DNSmeasure">
	  <front>
	    <title>Measuring Centralization of the DNS Infrastructure in the Wild</title>
	    <author initials="L." surname="Zembruzki">
            <organization />
	    </author>
	    <author initials="A. S." surname="Jacobs">
            <organization />
	    </author>
	    <author initials="G. S." surname="Granville">
            <organization />
	    </author>
	    <author initials="G,C,M." surname="Moura">
            <organization />
	    </author>
	    <date year="2022" />
	  </front>
	</reference>
	
        <reference anchor="Entropy">
	  <front>
	    <title>Evidence of Decreeasing Internet Entropy;: The Lack of Redundancy in DNS Resolution by Major Websites</title>
	    <author initials="S." surname="Bates">
            <organization />
	    </author>
	    <author initials="J." surname="Bowers">
            <organization />
	    </author>
	    <author initials="S." surname="Greenstein">
            <organization />
	    </author>
	    <author initials="J." surname="Weinstock">
            <organization />
	    </author>
	    <author initials="Y." surname="Xu">
            <organization />
	    </author>
	    <author initials="J." surname="Zittrain">
            <organization />
	    </author>
	    <date year="2022" />
	  </front>
	</reference>
	
        <reference anchor="DataConsolidation">
	  <front>
	    <title>How To Centralize the Internet: A Focus on Data Consolidation and User Privacy</title>
	    <author initials="T." surname="Kwon">
            <organization />
	    </author>
	    <author initials="J." surname="Song">
            <organization />
	    </author>
	    <author initials="H." surname="Jung">
            <organization />
	    </author>
	    <author initials="S." surname="Chun">
            <organization />
	    </author>
	    <author initials="H." surname="Lee">
            <organization />
	    </author>
	    <author initials="M." surname="Kang">
            <organization />
	    </author>
	    <author initials="M." surname="Park">
            <organization />
	    </author>
	    <author initials="E." surname="Cho">
            <organization />
	    </author>
	    <date year="2022" />
	  </front>
	</reference>
	
        <reference anchor="ISOCconsolidation" target="https://future.internetsociety.org/2019/consolidation-in-the-internet-economy">
          <front>
            <title>Considerations on Internet Consolidation and the Internet Architecture [draft-arkko-iab-internet-consolidation-02] (Expired)</title>
            <author>
              <organization>Internet Society</organization>
            </author>
            <date year="2019" />
          </front>
        </reference> 
        
        <reference anchor="Pace" target="https://dl.acm.org/doi/10.1145/3579437">
          <front>
            <title>Each at its Own Pace: Third-Party Dependency and Centralization Around the World</title>
            <author initials="R." surname="Kumar">
	       <organization />
            </author>
            <author initials="S." surname="Asif">
	       <organization />
            </author>
            <author initials="E." surname="Lee">
	       <organization />
            </author>
            <author initials="F." surname="Bustamante">
	       <organization />
            </author>
            <date year="2023" month="March" />
          <abstract><t>We describe the results of a large-scale study of third-party dependencies around the world based on regional top-500 popular websites accessed from vantage points in 50 countries, together covering all inhabited continents. This broad perspective shows that dependencies on a third-party DNS, CDN or CA provider vary widely around the world, ranging from 19 percent to as much as 76 percent of websites, across all countries. The critical dependencies of websites -- where the site depends on a single third-party provider -- are equally spread ranging from 5 percent to 60 percent (CDN in Costa Rica and DNS in China, respectively). Interestingly, despite this high variability, our results suggest a highly concentrated market of third-party providers: three providers across all countries serve an average of 92 percent and Google, by itself, serves an average of 70 percent of the surveyed websites. Even more concerning, these differences persist a year later with increasing dependencies, particularly for DNS and CDNs. We briefly explore various factors that may help explain the differences and similarities in degrees of third-party dependency across countries, including economic conditions, Internet development, economic trading partners, categories, home countries, and traffic skewness of the country's top-500 sites.</t>
          </abstract>
          </front>
        <seriesInfo name="DOI" value="10.1145/3579437"/>
        </reference> 
        
        <reference anchor="DINRG" target="https://datatracker.ietf.org/meeting/114/materials/slides-114-dinrg-draft-report-of-dinrg-workshop-on-centralization-in-the-internet-01.pdf">
          <front>
            <title>Draft Report of DINRG Workshop on Centralization in the Internet</title>
            <author>
              <organization>Internet Engineering Research Group: DINRG</organization>
            </author>
            <date year="2021" />
          </front>
        </reference> 
        
        <reference anchor="IABwrkshp" target="https://www.iab.org/activities/workshops/dedr-workshop/position-papers/">
          <front>
            <title>Design Expectations vs. Deployment Reality in Protocol Development Workshop 2019</title>
            <author>
              <organization>Internet Architecture Board</organization>
            </author>
            <date year="2019" />
          </front>
        </reference>  
        
        <reference anchor="ISOCpaper" target="https://future.internetsociety.org/2019/consolidation-in-the-internet-economy">
          <front>
            <title>Consolidation In the Internet Economy</title>
            <author>
              <organization>The Internet Society</organization>
            </author>
            <date year="2019" />
          </front>
        </reference>
        
        <reference anchor="JCP" target="https://www.tandfonline.com/toc/rcyb20/5/1">
          <front>
            <title>Consolidation of the Internet</title>
            <author>
              <organization>Journal of Cyber Policy</organization>
            </author>
            <date year="2020" />
          </front>
        </reference>
        
        <reference anchor="EmpiricalView" target="https://vaibhavbajpai.com/documents/papers/proceedings/web-consolidation-toit-2022.pdf">
          <front>
            <title>An Empirical View on Consolidation of the Web</title>
            <author initials="T." surname="Viet Doan">
              <organization />
            </author>
            <author initials="R." surname="Rijswijk-Deij">
              <organization />
            </author>
            <author initials="O." surname="Hohlfeld">
              <organization />
            </author>
            <author initials="V." surname="Bajpai">
              <organization />
            </author>
            <date year="2022" />
          </front>
        </reference>  
        
        <reference anchor="RFC1958" target="https://www.rfc-editor.org/info/rfc1958">
          <!-- Manually added reference -->
          <front>
            <title>Architectural Principles of the Internet</title>
            <author initials="B." surname="Carpenter" fullname="B. Carpenter">
              <organization />
            </author>
            <date year="1996" month="June" />
            <abstract>
              <t>The Internet and its architecture have grown in evolutionary fashion from modest beginnings, rather than from a Grand Plan. While this process of evolution is one of the main reasons for the technology's success, it nevertheless seems useful to record a snapshot of the current principles of the Internet architecture. This is intended for general guidance and general interest, and is in no way intended to be a formal or invariant reference model. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1958" />
          <seriesInfo name="DOI" value="10.17487/RFC1958" />
        </reference>
        
        <reference anchor="RFC3724" target="https://www.rfc-editor.org/info/rfc3724">
          <!-- Manually added reference -->
          <front>
            <title>The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture</title>
            <author initials="J." surname="Kempf" fullname="J. Kempf">
              <organization />
            </author>
            <author initials="R." surname="Austein" fullname="R. Austein">
              <organization />
            </author>
            <date year="2004" month="March" />
            <abstract>
              <t>The end-to-end principle is the core architectural guideline of the Internet.  In this document, we briefly examine the development of the end-to-end principle as it has been applied to the Internet architecture over the years.  We discuss current trends in the evolution of the Internet architecture in relation to the end-to-end principle, and try to draw some conclusion about the evolution of the end-to-end principle, and thus for the Internet architecture which it supports, in light of these current trends.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3724" />
          <seriesInfo name="DOI" value="10.17487/RFC3724" />
        </reference>
        
        <reference anchor="RFC8280" target="https://www.rfc-editor.org/info/rfc8280">
        <front>
           <title>Research into Human Rights Protocol Considerations</title>
           <author fullname="N. ten Oever" initials="N." surname="ten Oever"/>
           <author fullname="C. Cath" initials="C." surname="Cath"/>
           <date month="October" year="2017"/>
           <abstract>
           <t>This document aims to propose guidelines for human rights considerations, similar to the work done on the guidelines for privacy considerations (RFC 6973). The other parts of this document explain the background of the guidelines and how they were developed.
           This document is the first milestone in a longer-term research effort. It has been reviewed by the Human Rights Protocol Considerations (HRPC) Research Group and also by individuals from outside the research group.</t>
           </abstract>
        </front>
        <seriesInfo name="RFC" value="8280"/>
        <seriesInfo name="DOI" value="10.17487/RFC8280"/>
        </reference>
        
        <reference anchor="RFC8517" target="https://www.rfc-editor.org/info/rfc8517">
        <front>
            <title>An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective</title>
            <author fullname="D. Dolson" initials="D." role="editor" surname="Dolson"/>
            <author fullname="J. Snellman" initials="J." surname="Snellman"/>
            <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/>
            <author fullname="C. Jacquenet" initials="C." surname="Jacquenet"/>
            <date month="February" year="2019"/>
            <abstract>
                <t>This document summarizes an operator's perception of the benefits that may be provided by intermediary devices that execute functions beyond normal IP forwarding. Such intermediary devices are often called "middleboxes".
                RFC 3234 defines a taxonomy of middleboxes and issues in the Internet. Most of those middleboxes utilize or modify application- layer data. This document primarily focuses on devices that observe and act on information carried in the transport layer, and especially information carried in TCP packets.</t>
            </abstract>
            </front>
        <seriesInfo name="RFC" value="8517"/>
        <seriesInfo name="DOI" value="10.17487/RFC8517"/>
        </reference>
        
        <reference anchor="RFC8890" target="https://www.rfc-editor.org/info/rfc8890">
          <!-- Manually added reference -->
          <front>
            <title>The Internet is for End Users</title>
            <author initials="M." surname="Nottingham" fullname="M. Nottingham">
              <organization />
            </author>
            <date year="2020" month="August" />
            <abstract>
              <t>This document explains why the IAB believes that, when there is a conflict between the interests of end users of the Internet and other parties, IETF decisions should favor end users. It also explores how the IETF can more effectively achieve this.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8890" />
          <seriesInfo name="DOI" value="10.17487/RFC8990" />
        </reference>
        
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false">
      <name>Acknowledgements</name>
      <t>Many thanks to all who discussed this with us in DINRG in 2021, 2022, 2023, and 2024.</t>
    </section>
  </back>
</rfc>