IETF Logo Mail Archive

[Add] Draft on deployment models for Internet infrastructure

Jari Arkko <jari.arkko@piuha.net> Sun, 17 November 2019 03:20 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEF6120833 for <add@ietfa.amsl.com>; Sat, 16 Nov 2019 19:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIksUCiFv1kv for <add@ietfa.amsl.com>; Sat, 16 Nov 2019 19:20:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3A419120046 for <add@ietf.org>; Sat, 16 Nov 2019 19:20:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 997C46601B3 for <add@ietf.org>; Sun, 17 Nov 2019 05:20:04 +0200 (EET)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHZv1hSg5Bta for <add@ietf.org>; Sun, 17 Nov 2019 05:20:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id EA60E6600DE for <add@ietf.org>; Sun, 17 Nov 2019 05:20:02 +0200 (EET)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <BFE6C273-41BF-4A4A-B25A-2F92DBA29357@piuha.net>
Date: Sun, 17 Nov 2019 11:20:00 +0800
To: ADD Mailing list <add@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/k0ZwYfQoniekXqmkUYfoNKl_h_Q>
Subject: [Add] Draft on deployment models for Internet infrastructure
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2019 03:20:07 -0000

I also wanted to point people to a draft that talks about centralised and 
other deployment models. This draft is about a broader topic than the
DNS, more generally about anything in the Internet infrastructure. But 
it is also applicable for DNS. Comments and other observations are 
again appreciated.

https://tools.ietf.org/html/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.

Jari

v2.23.0 | Report a Bug | By Email