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

Fernando Gont <fgont@si6networks.com> Mon, 26 August 2019 05:30 UTC

Return-Path: <fgont@si6networks.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 D874D120826 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 22:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 9bH4q37zbczi for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 22:30:49 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4337A1200A4 for <architecture-discuss@iab.org>; Sun, 25 Aug 2019 22:30:49 -0700 (PDT)
Received: from [192.168.1.2] (ppp-94-69-228-39.home.otenet.gr [94.69.228.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 76B4286418; Mon, 26 Aug 2019 07:30:47 +0200 (CEST)
To: Joe Touch <touch@strayalpha.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: architecture-discuss@iab.org
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>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <22eceb42-70a0-04ad-dc2c-4550f0cf87a5@si6networks.com>
Date: Mon, 26 Aug 2019 08:30:41 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <A0939AF0-2377-427C-8009-1AEE34EF05FA@strayalpha.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/WqqQcHcXPZsebMH6TJ_JNeN1DDA>
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:30:51 -0000

On 26/8/19 07:50, Joe Touch wrote:
> 
> 
>> On Aug 25, 2019, at 12:16 PM, Henning Schulzrinne <hgs@cs.columbia.edu
>> <mailto:hgs@cs.columbia.edu>> wrote:
>>
>> Some of us who worked on the Open Internet (aka network neutrality)
>> saw "protocol neutrality" as very much part of the same spirit and
>> possibly a legal entitlement of customers. And the issue of naming
>> "Internet access" implying some obligations was also part of the
>> discussion. Experience seems to indicate that only legal or regulatory
>> requirements are likely to lead there,
> 
> That hasn’t been the case for SONET, ATM, or Ethernet services.
> 
> If we had a clear definition of “ISOC-certified Internet service”, then:
> a) customers might be willing to seek that
> b) customers who pay for that have a clear legal path if that’s what was
> offered and it isn’t true

If one means to get on that path, I'd start with certified
implementations -- at times, the service is a consequence of this.

One of the most obvious cases is e.g. IPv6 implementations that are
"IPv6 Ready", but then do an extremely lousy job (see "IPv6 Security
Assessment and Benchmarking" at
http://www.ipv6hackers.org/meetings/ipv6-hackers-1).



>> given that many carriers have no economic interest to do this - and
>> carrier-grade NATs make it painful or impossible to move beyond TCP
>> and UDP.
>>
>> Henning
> 
> We could have two versions of service - ISOC-certified true Internet and
> ISOC-certified translated Internet (the latter so we don’t freeze out
> carriers to start). People might pay more for the former.

Without giving this a lot of thought, the problem with "certified
Internet" is that one would expect that to apply to all destinations and
paths.

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?

(I bet many of us, nevertheless, when prompted with the question of
which one we want to buy, would ask the question: what can I do with the
expensive one that I can't with the other? (as opposed to "what one
could *potentially* do).

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492