Centralised Architectures in Internet Infrastructure
draft-arkko-arch-infrastructure-centralisation-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           J. Arkko
Internet-Draft                                                  Ericsson
Intended status: Informational                         November 05, 2019
Expires: May 8, 2020

          Centralised Architectures in Internet Infrastructure
           draft-arkko-arch-infrastructure-centralisation-00

Abstract

   Centralised deployment models for Internet services and Internet
   business consolidation are well-known Internet trends, at least when
   it comes to popular and user-visible service.  This memo discusses
   the impacts of similar trends within the Internet infrastructure, on
   functions such as DNS resolution.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 8, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Arkko                      Expires May 8, 2020                  [Page 1]
Internet-Draft          Centralised Architectures          November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Context . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Issues with Centralisation  . . . . . . . . . . . . . . . . .   3
     3.1.  Single point of failure . . . . . . . . . . . . . . . . .   3
     3.2.  Surveillance  . . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  Concentration of information  . . . . . . . . . . . . . .   4
     3.4.  Effect scope  . . . . . . . . . . . . . . . . . . . . . .   4
     3.5.  Interaction with other issues . . . . . . . . . . . . . .   4
     3.6.  The effect of differing expectations and jurisdictions  .   5
   4.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Centralised deployment models for Internet services and Internet
   business consolidation are well-known Internet trends, at least when
   it comes to popular and user-visible service [ISOC]
   [I-D.arkko-iab-internet-consolidation] [I-D.arkko-arch-dedr-report].
   This memo discusses the impacts of similar trends within the Internet
   infrastructure, on functions such as DNS resolution.

   This memo has been inspired by recent attempts to move DNS resolution
   from large number of local servers to a more centralized
   arrangements, but the principles outlined in this document apply more
   generally to other basic Internet services.

   Section 2 introduces the context of the memo, Section 3 discusses
   some potential issues, and Section 4 makes a recommendation.

2.  Context

   For the purposes of this discussion, "Internet Infrastructure" is
   defined as those parts of the technical Internet infrastructure that
   are needed to form a communication substrate for applications to run
   on.  Applications are not a part of the infrastructure, they run on
   it.  But packet forwarding, routing, naming as well as higher level
   functions such as certificate authorities are included; anything that
   is needed to establish an end-to-end HTTPS connection between host is
   part of the infrastructure.  This also includes all Internet
   technology that is needed for these part to work.

   The DNS [RFC1035] is a complex system with many different security
   issues, challenges, deployment models and usage patterns.  While
   there are many parts of the DNS system and they are all part of the

Arkko                      Expires May 8, 2020                  [Page 2]
Internet-Draft          Centralised Architectures          November 2019
Show full document text