Re: [Nethistory] Measuring the Internet: When History Means Measurement

Curtis Villamizar <curtis@ietf.occnc.com> Sun, 02 February 2020 01:07 UTC

Return-Path: <curtis@ietf.occnc.com>
X-Original-To: nethistory@ietfa.amsl.com
Delivered-To: nethistory@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44CBE1201C6 for <nethistory@ietfa.amsl.com>; Sat, 1 Feb 2020 17:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf.occnc.com
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 GIoriOL0UJRp for <nethistory@ietfa.amsl.com>; Sat, 1 Feb 2020 17:07:44 -0800 (PST)
Received: from mta1-em1.orleans.occnc.com (mta1-em1.orleans.occnc.com [IPv6:2603:3005:5602:8a00::141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79ED11201AA for <nethistory@ietf.org>; Sat, 1 Feb 2020 17:07:44 -0800 (PST)
Received: from harbor1.v6cc2.occnc.com (harbor1-cc2.v6cc2.occnc.com [IPv6:2603:3005:5602:8af2::1230]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: curtis@occnc.com) by mta1-em1.orleans.occnc.com (Postfix) with ESMTPSA id BC96810789; Sat, 1 Feb 2020 20:07:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ietf.occnc.com; s=curtis-ietf-20180728-193203; t=1580605662; bh=SxsjnkDFJUyQNv9dJDmL8txJVcky9PJQYL8YDXzCQaY=; h=To:cc:Reply-To:From:Subject:In-reply-to:Date; b=gw5T0+olaIPayj/AnpcoKRO+2mlkzl1TvY2nudsLsrF62z5OZ/QVNYBuI2LMs1yZ4 xP4tHwm4mcqj7smOV22ox9wSVmlnCEOUwgWhoKqHqrY1H/wpk+M5RNzwO0cxDJ3kqs oRZBKbDXZVJ3W6IEhXiP2HJ7VDqDxhNGyuDhE1NI6TjH3GrnlFjYbCzayC3+rF0tp/ ruiGoTHa1GrdfzIrjxt9mUBI0Kwbli9pOk9/99uvOpZGAnIdtIiyxDeNHvhMu+L5O6 04TFay9+N787wTXcoS/3+TpoynqbBTiXhOcn5dfw+5Fj7KSUSuuunyORQ2tlPQs3Ie C6+occpAjRaUg==
To: Guntur Wiseno Putra <gsenopu@gmail.com>
cc: nethistory@ietf.org, public-webhistory@w3.org, public-informationarchitecture@w3.org
Reply-To: Curtis Villamizar <curtis@ietf.occnc.com>
From: Curtis Villamizar <curtis@ietf.occnc.com>
In-reply-to: Your message of "Sun, 02 Feb 2020 00:21:15 +0700." <CAKi_AEuZB-ekP+UAiz+f7ZJcGPss5dXFsY0HgccdPyWtVUAgjw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <97649.1580605549.1@harbor1-cc2.v6cc2.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 01 Feb 2020 20:05:49 -0500
Message-Id: <20200202010744.79ED11201AA@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nethistory/fDDrYHNb8Np7ZgIC9aNGvnywc0g>
Subject: Re: [Nethistory] Measuring the Internet: When History Means Measurement
X-BeenThere: nethistory@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Matching net historical materials with institutions that may preserve them <nethistory.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nethistory>, <mailto:nethistory-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nethistory/>
List-Post: <mailto:nethistory@ietf.org>
List-Help: <mailto:nethistory-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nethistory>, <mailto:nethistory-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2020 01:07:46 -0000

Good luck with that.

ISPs have always been notoriously somewhat secretive about their
network topology, even more secretive about the capacity of their
network, and extremely secretive about the actual traffic loads.

Attempts to document all Internet outages (you wrote shutdowns - wrong
word) over time may prove even more difficult.  Small outages are a
constant occurance and not even worth noting.  Routing errors can be
vexing for end customers because they are persistent and can be missed
by ISPs (and can be caused by ISP misconfiguration).  Any such outage
is often attributed to just the organization that reported the outage
or identified the problem even though the impact might have been
widespread.  These days there are also IPv4 vs IPv6 outages (an outage
exists for one but not the other) often due to a routing error.

There was good information collected on the NSFNET when that was a
thing and somewhat central to most of the Internet, but that is now
ancient history (and not a complete look at the Internet even back
then).  Check with Merit for archives and the IMR.  Also check CAIDA
to see what they have.  You may find useful information on routes
going away from the route view servers and possibly archives.  Some of
the regional NOGs or NICs produce route churn graphs and may have
archives.  There are many sources of information and many
methodologies for collecting and analyzing it.

As the number of ISPs grows the difficulty in determining level of
network traffic becomes increasingly intractable.  When routes go away
(or harder to detect blackhole or loop) it is hard to know how much
traffic is affected.  Not all prefix outages are equally important and
the number of addresses within the prefix is a poor estimator (almost
useless for IPv6 with many ISPs freely handing out /48s).

Whenever you talk about outages, you need to quantify the extent of
the outage.  Small outages are a constant.  You have to decide what is
a big enough outage to count as significant and then even harder you
have to decide on a way to measure extent of outages.

Curtis


In message <CAKi_AEuZB-ekP+UAiz+f7ZJcGPss5dXFsY0HgccdPyWtVUAgjw@mail.gmail.com>
Guntur Wiseno Putra writes:
> 
> Dear nethistory,
> public-webhistory &
> public-informationarchitecture
>  
>  
> * Measuring the Internet: When History Means Measurement
>  
> It is about a "reliable place to find answers to questions about the
> current state of the Internet... (but at the same time it is about
> attempting historical values as it is also about a)... single site or tool
> that brings together the multiple measures required to understand the
> Internet=E2=80=99s evolution and health.
>  
> ..... A Web-based dashboard will present these trends and contextualize
> indicators within an overall narrative of Internet evolution and promotion
> of the Internet way of networking...".
>  
>  
> It is part of the 2020 Internet Society Action Plan Projects
>  
> https://www.internetsociety.org/issues/measurement/
>  
>  
> Regard,
> Guntur Wiseno Putra