Re: [saag] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 12 January 2023 05:44 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E36CEC1782AC for <ietf@ietfa.amsl.com>; Wed, 11 Jan 2023 21:44:54 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mh5oSTNgXIyg for <ietf@ietfa.amsl.com>; Wed, 11 Jan 2023 21:44:54 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id EBD63C1763AE for <ietf@ietf.org>; Wed, 11 Jan 2023 21:44:53 -0800 (PST)
Received: (qmail 39353 invoked from network); 12 Jan 2023 05:35:36 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 12 Jan 2023 05:35:36 -0000
Message-ID: <45bae88c-1e03-0b21-9dfc-1be897cc1781@necom830.hpcl.titech.ac.jp>
Date: Thu, 12 Jan 2023 14:44:49 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Subject: Re: [saag] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?
Content-Language: en-US
To: ietf@ietf.org
References: <3c3230f3783b4ec9a8a9e3bb87cc2a8d@huawei.com> <08C49067-DB4C-41AB-A6F3-B96BDBE0A4BC@yahoo.co.uk> <CAKr6gn0tFXEV-h7LH1_Ts5iQRw_mGEi=TqS7hsyK-SqDFmmY-A@mail.gmail.com> <C09B3D18-2871-491F-B76C-630A2DCA439A@gmail.com> <EFCEFAA6-3638-4CE0-91DD-3E38FE00DF29@gmail.com> <1F71EB99-3657-4A20-8B28-2AFB743A9762@gmail.com> <CAMm+LwgCxHJYWtv+4ZQdr0-MbSE3qXg6wrT=DZLS=X9pKqpMSg@mail.gmail.com> <CAJU8_nVWLx9FuP_g=9SXXzGj3HMu9vmuCHh4yRYJ7JGNoW_qsw@mail.gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <CAJU8_nVWLx9FuP_g=9SXXzGj3HMu9vmuCHh4yRYJ7JGNoW_qsw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GgSPD-H5a36JnLafqprHvkmsfSc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2023 05:44:55 -0000

Kyle Rose wrote:

> Unicast delivery is very mature in every way: not just reliable 
> transport, but operations, monitoring, congestion control, 
> authentication, and confidentiality.

Congestion control for multicast is just impossible (what if,
a new user with a 64Kbps link joins a group when 1M users
are enjoying to receive 1Mbps traffic). As such, speed must
be determined by sender side, which can not be TCP friendly.

So, multicast in WAN can be practical only with QoS guarantee
with usage based charging.

In an ISP, it is not so difficult to manually prioritize some
multicast traffic with advance agreements between the ISP and
multicast senders.

> it's the rest of the ecosystem that requires a large lift to
> get multicast delivery to the point where it is viable for
> businesses whose users have high baseline quality expectations.

With best effort, flat rated Internet, end users are not
motivated to be multicast capable and content providers
just use parallel unicast servers.

With QoS guaranteed, usage based charging Internet, paid charge
can be reduced by multicast, which will be the economic incentive
to deploy multicast.

A problem is that best effort speed of the Internet today is
fast enough for most purposes. But, 8K video streaming can
be a candidate.

 > In
 > most cases, technologies for doing those things don't exist except on
 > paper, and even then have not been battle-tested by operators for 40
 > years.

While I designed and implemented fully automated QoS/multicast
signaling protocol with BW and charge based QoS routing, as a
starter, fully manual prioritization is trivially easy with
commercially available technologies.

						Masataka Ohta