Re: [arch-d] FYI: closure of the IAB Stack Evolution program

Joe Touch <touch@strayalpha.com> Mon, 26 August 2019 05:41 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9255F1200A1 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 22:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 i_GjEKRJHkNh for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 22:41:03 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 19C95120025 for <architecture-discuss@iab.org>; Sun, 25 Aug 2019 22:41:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=CaetCTWAX5CYeElUgId2yl83fbVEJLJogGjKeVoBHXM=; b=Gix7EGYFmVMqXYRKjOR04Zo/2 yVt70yo1KoGqPg4ft4ugBOOJ6+2VFeqZAKi4ziOZK9U+1wrch+gZD5nrbb4njJV738tqGj6YlymOh 4wiOr2ZETkq1UC3y3mEaFvThSXzLPA7YybjJOQZ5Zk0BrHh090ciYp0W9e72UYzoSCSZR/e6VQ91s /1HpLg4PrkwH7xpa32czElgfQ71wxyWNPebO97nLlC2TvMvFyCj2VCuOhD36T7wJk+AFfvLKO/gJ6 kvdKW4U+AgcZGULE3ExDf8p4vq9gVPmbBB94atP5GRs5cnnBpBuhJ30WbcsXW9O3jzaqks94T1ust WskptzTRA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:62333 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1i27kQ-0010p4-85; Mon, 26 Aug 2019 01:41:02 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_D2C8A540-9B28-46E1-9EDD-3BE732AF5634"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <22eceb42-70a0-04ad-dc2c-4550f0cf87a5@si6networks.com>
Date: Sun, 25 Aug 2019 22:40:57 -0700
Cc: Henning Schulzrinne <hgs@cs.columbia.edu>, architecture-discuss@iab.org
Message-Id: <276F8587-603C-499A-A89F-3387589D6E6B@strayalpha.com>
References: <B5A0F4E0-D437-4DF9-9918-C35627A8CADC@trammell.ch> <d5009253-4884-9f1f-66e7-1159e85524b9@si6networks.com> <770822F2-688F-44EA-A6A1-7E7EDBFAA989@trammell.ch> <cece8133-6b69-a677-52fc-a7fb4c7d5136@si6networks.com> <64E3A59C-8709-41E0-B74F-C036E4481AE4@apple.com> <f3645e11-d823-4308-3f51-6f2da5e33180@si6networks.com> <87imqnvhui.wl-morrowc@ops-netman.net> <CA+9kkMDWk3kmYOZ8Zz+BjUZG0+sshQJjR9pYt-NgL8umqpMtWQ@mail.gmail.com> <eb2bc35f-ea95-69b9-5163-baded0c47478@si6networks.com> <20190825164839.GA77144@verdi> <715FF08E-9DD1-4052-BE1D-3C3AA614B560@strayalpha.com> <CACgrgBZrfaQTHneNV7JSSq6YB98-qUa7FnAgGFffX9ztyc2oAg@mail.gmail.com> <A0939AF0-2377-427C-8009-1AEE34EF05FA@strayalpha.com> <22eceb42-70a0-04ad-dc2c-4550f0cf87a5@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - iab.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/kfW-5g_Hb7cs_8YyHYC4bvR-DUg>
Subject: Re: [arch-d] FYI: closure of the IAB Stack Evolution program
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2019 05:41:05 -0000


> On Aug 25, 2019, at 10:30 PM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> When should my ISP start billing me for the "true Internet" service?
> When it works with Google, or with everyone? If the former: Does it
> matter? If the latter: would it ever happen?

1. provide endpoint services that use certified implementations
2. give me real Internet service, per below

No, this won’t fix everything. But it’s the set of steps we need to take first.

The next step is to highlight where these rules don’t work as not working. Not endorse them as “de facto changes to the baseline”.

Joe

Bill of Internet Access Rights


Joe Touch
USC/ISI
June 21, 2006 
(this is an update of a set of rules originally presented at "Preventing the Internet Meltdown", Los Angeles CA 2004; the original is also presented below) 

Internet is an association of communicating parties. This necessarily results in a number of rights which are required for consenting parties to communicate. Consenting parties should be able to communicate in an unrestricted fashion, insofar as they do not impinge on the corresponding rights of other parties. The following is a list of specific rights to that end:

1. REAL IP: Users have the right to obtain a real IP address, routable from anywhere on the Internet.

2. REAL DNS (& REVERSE-DNS): Users have the right to obtain a valid reverse DNS name for that IP address, and the forward lookup of that name should match the same address.

3. RECEIVE ANY: Users have the right to receive any valid IP packet, using any valid transport protocol on any valid port (if applicable), up to the limits of your local resources and network connection.

4. SEND ANY: Users have the right to send any valid IP packet to any valid real IP address, using any transport protocol, on any valid port (if applicable), provided it uses an inconsequential amount of resources of the network and potential receiver until mutual consent is established.

5. ENFORCEMENT: Users have the right to know the ISP responsible for traffic from any valid IP address, sufficient to register a complaint regarding violations of any of these rules.