[arch-d] Beyond Best Effort ?! Re: ETSI launches new group on Non-IP Networking addressing 5G new services

Toerless Eckert <tte@cs.fau.de> Thu, 09 April 2020 18:14 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C9B503A011D for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 11:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, PLING_QUERY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 RHdf89Yv_5ZR for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 11:14:35 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80003A010D for <architecture-discuss@ietf.org>; Thu, 9 Apr 2020 11:14:34 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id D3148548048; Thu, 9 Apr 2020 20:14:28 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id CD5DB440040; Thu, 9 Apr 2020 20:14:28 +0200 (CEST)
Date: Thu, 09 Apr 2020 20:14:28 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org
Message-ID: <20200409181428.GG28965@faui48f.informatik.uni-erlangen.de>
References: <60a10451-5fbd-fcec-5389-7a72870dcc84@gmail.com> <6A3A4410-A889-46C7-8FD5-7C5AA85486A1@tzi.org> <20200408054204.GA6005@nic.fr> <6C2A3533-7F75-45B1-9B51-19938597174B@tzi.org> <20200408194154.GJ28965@faui48f.informatik.uni-erlangen.de> <4200C5F8-9F56-4FFF-90F4-7AD76A9F4FC8@eggert.org> <20200409121941.GZ28965@faui48f.informatik.uni-erlangen.de> <C758BDF2-8CD6-4C22-90CA-6ED98DACD740@eggert.org> <C88A918A-CED0-4C7C-8284-7498736931F3@gmail.com> <CACgrgBbV--f9a4QrVZH+-xZpLL=_OBe_q7Usinv26=M6RdcuMQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CACgrgBbV--f9a4QrVZH+-xZpLL=_OBe_q7Usinv26=M6RdcuMQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/1XJHPStXwMEiYCeUtkCWPE3g2rE>
Subject: [arch-d] Beyond Best Effort ?! Re: ETSI launches new group on Non-IP Networking addressing 5G new services
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: Thu, 09 Apr 2020 18:14:37 -0000

This really goes to what i also think is one of the core architectural questions.

There is an important amount of DiffServ in many private networks,
including service provider video to the ome, that users might
consider "Internet". There are IntServ uses for criticial traffic
in Service providers and Enterprises (RSVP-TE), also for higher
resilience (reroute with resource guarantees). TSN has  a lot
of critical manufacturing and othher industrial use cases, and
those all want L3 support (DetNet). 

On the oter hand, we have in IETF not even come up with a better
definition of fairness than don't kill all competing traffic,
we have AFAIK no agreement of what level of aggressiveness of TCP
congestion control should be the fairness standard (maybe L4S will
help here a bit), and we are far from even acknowledging that we
should also have solutions for differentiated dynamic bandwidth,
even though we already have good technology proof points that it
can be done. (Stuck in Net Neutrality ...). See below.

We have recently made a bit of progress in IETF to better
support less than best effort, that could actually make
bits less expensive too.

Aka: I agree that from 50,000 feet you are right, but when you
come closer, you see that the picture is less binary,
but that what you say its true for "Best Effort Internet",
but that is not really sufficient, and its not true for many
private networks. And it is going to become more of an
issue, the more we want to apply Internet technologies
for more critical infrastructure functions IMHO. Or
even for more differentiated services experiences.

I for once think its not a good QoS architecture when
presidents have to call up NetFlix's CEO and ask him
to reduce his companies pressure on the networks, because
networks themselves can not distinguish this entertainment
traffic from more critical traffic. Do you think this
is the right QoS architecture for the Internet ? Are
we going to have an IANA registries for the FAX numbers
of those CEO's ? ;-)) (yeah, sorry, couldn't resist).

Cheers
    Toerless

On Thu, Apr 09, 2020 at 12:40:08PM -0400, Henning Schulzrinne wrote:
> Since we're talking slides, I'll throw in my take:
> 
> http://www.cs.columbia.edu/~hgs/papers/2019/2019%20Internet40%20IIT-RTC.pdf
> 
> Every single failed network architecture has promised QoS by making bits
> more expensive; every successful technology has lowered the total cost of
> deployment and operations and making bits cheaper.
> 
> On Thu, Apr 9, 2020 at 12:26 PM Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> > I wonder if this desire for new non-ip networking architectures, is really
> > a replay of the what I call the packet switching vs. circuit switching
> > debate.   Somewhat more recently Ethernet vs. Token ring.  Basically, can
> > networking architectures provide deterministic service (like circuit
> > switching), or is the Internet best effort OK.
> >
> > It was very common to hear that voice or video couldn???t possibly work over
> > an Internet style packet switching network.   I haven???t heard that in a
> > while, or at least until recently after the 5G hype started gearing up.
> >
> > I attended the lunch speaker session on 5G at the Singapore IETF, slides
> > can be found:
> >
> >
> > https://datatracker.ietf.org/meeting/106/materials/slides-106-edu-sessa-5g-impact-on-networks-edge-cloud-and-slicing-00
> >
> > Seemed to me it was proposing (see slide 13) an end to end 5G
> > network/service.  Lots of words like "Guarantee transport SLAs for each
> > service???, ???Optimize network resources as load conditions change???, etc.   I
> > think arguments proposing a new non-ip networking architecture is back to
> > wanting a more deterministic networking (aka circuit switching).   I
> > suppose it also has something to do with wanting to sell services to very
> > large numbers of devices (vs. the current Internet model a subscription per
> > enterprise or home user).
> >
> > I didn???t understand why all of this couldn???t be built today with the
> > current set of IP wireless and wired technologies.   I was thinking of
> > coming to the mic and ask the speaker if he had heard about the Internet,
> > but decided it wouldn???t be constructive :-)
> >
> > Bob
> >
> >
> > _______________________________________________
> > Architecture-discuss mailing list
> > Architecture-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/architecture-discuss
> >

> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss


-- 
---
tte@cs.fau.de