Re: [arch-d] Fwd: A Public Option for the Core

Toerless Eckert <tte@cs.fau.de> Mon, 17 August 2020 13:23 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 A4C853A153F for <architecture-discuss@ietfa.amsl.com>; Mon, 17 Aug 2020 06:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 BR8IhCA9rjJL for <architecture-discuss@ietfa.amsl.com>; Mon, 17 Aug 2020 06:23:37 -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 3FE7D3A0C06 for <architecture-discuss@ietf.org>; Mon, 17 Aug 2020 06:23:36 -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 91ABB54802F; Mon, 17 Aug 2020 15:23:31 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 86251440059; Mon, 17 Aug 2020 15:23:31 +0200 (CEST)
Date: Mon, 17 Aug 2020 15:23:31 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John Day <jeanjour@comcast.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Joe Touch <touch@strayalpha.com>, architecture-discuss@ietf.org
Message-ID: <20200817132331.GX62842@faui48f.informatik.uni-erlangen.de>
References: <754DE168-DF3B-4471-A145-39C6143E538A@comcast.net> <FB381338-A278-45B2-A40B-3A065E3A3ED1@strayalpha.com> <1fd2ed7d-d4bc-c5b7-9a4a-7966d5e60513@gmail.com> <20200817074637.GW62842@faui48f.informatik.uni-erlangen.de> <BC83D497-4EC6-48A8-9289-433B8A896B47@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BC83D497-4EC6-48A8-9289-433B8A896B47@comcast.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/iclpXroRqFAGn-V84LzCDo37MCA>
Subject: Re: [arch-d] Fwd: A Public Option for the Core
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, 17 Aug 2020 13:23:40 -0000

On Mon, Aug 17, 2020 at 07:42:36AM -0400, John Day wrote:
> 
> 
> > On Aug 17, 2020, at 03:46, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > John, Joe, Brian:
> > 
> > All great discussion points, but i am not sure if JohnD's starting
> > point of "no deductive adaptation of behavior" is really mandatory
> > and/or sufficient for *I* net neutrality. Aka: Do we even have
> > an approved and complete *I* "net neutrality" definition ? If so, where ?
> 
> Really? I said that?  Interesting. I wonder, when and even more, why?

Didn't say you said. Was referring to this, from Joe:

>>>> On 16/08/2020 02:48, Joseph Touch wrote:                                                                                
>>>> *I* want apps to be able to get different service from the network and to pay differently for them if needed, but       
+*never* to have the network infer or enforce that mapping.   

> > Btw, IMHO: Having an application tell the network exactly what it
> > wants from the network is quite a challenging task for applications.
> > When i worked with enterprise application developers, they wouldn't
> > even want to bother to understand what differences in service from the
> > network would best help the application.
> > 
> > Hence we thought of a framework where the application would instead
> > attribute traffic as to what it is, e.g.: application FOO, wihthin FOO floX,
> > e.g.: X = audio/video/...  Aka: Whatever the application developer was able/
> > willing to tell.
> > 
> > Then one can have a trusted layer that would map this information to
> > actual network service requirements/advisory information.
> > 
> > In classical enterprise environments, this trusted mapping layer
> > could typically be a nework device (given how applications in enterprise
> > are subject to a lot of control by the enterprise operator anyhow).
> > In typical residential environment, the trusted mapping would likely
> > best be the browser, given how that performs all type of control
> > operations against applications anyhow.
> 
> Interesting conjecture. O, well.

That second part was just my view of how beyond best effort service differentiation
would likely best be embodied into prevailing architectures in different  market
segments. Opinions welcome.

Cheers
    Toerless

> John
> 
> > 
> > Cheers
> >    Toerless
> > 
> > On Mon, Aug 17, 2020 at 08:24:06AM +1200, Brian E Carpenter wrote:
> >> On 17-Aug-20 03:01, Joe Touch wrote:
> >>> And the second is that service level implies connection. It only requires the network understands a label *I* control, rather than trying to infer one from the packet contents.
> >> 
> >> However, it does need some kind of flow state (whether flows are individual or aggregated) in the forwarding queues. Not that this is a new argument; we had it in the diffserv WG many years ago and it continues to this day in TSVWG.
> >> 
> >> I don't think this really affects the basic arguments for a "public core". It just indicates that transit networks don't need to be strictly best effort and stateless in order to be neutral.
> >> 
> >>   Brian
> >>  
> >>> 
> >>> Joe
> >>> 
> >>>> On Aug 16, 2020, at 3:19 AM, John Day <jeanjour@comcast.net> wrote:
> >>>> 
> >>>> ???
> >>>> 
> >>>>> Begin forwarded message:
> >>>>> 
> >>>>> *From: *John Day <jeanjour@comcast.net <mailto:jeanjour@comcast.net>>
> >>>>> *Subject: **Re: [arch-d] A Public Option for the Core*
> >>>>> *Date: *August 16, 2020 at 06:18:04 EDT
> >>>>> *To: *John Grant <j@ninetiles.com <mailto:j@ninetiles.com>>
> >>>>> 
> >>>>> No, that is not true.  Your first mistake is that there is a control plane.
> >>>>> 
> >>>>> John
> >>>>> 
> >>>>>> On Aug 16, 2020, at 06:02, John Grant <j@ninetiles.com <mailto:j@ninetiles.com>> wrote:
> >>>>>> 
> >>>>>> On 16/08/2020 02:48, Joseph Touch wrote:
> >>>>>>> *I* want apps to be able to get different service from the network and to pay differently for them if needed, but *never* to have the network infer or enforce that mapping.
> >>>>>> Of course, if you're going to do that -- have the application negotiate a particular kind of service rather than have the network "inspect" the packets and guess what service is needed -- you need a control plane protocol (let's call it "signalling") to do the negotiation, and you no longer have the connectionless/stateless paradigm on which IP is founded.
> >>>>>> 
> >>>>>> -- 
> >>>>>> John Grant
> >>>>>> Nine Tiles, Cambridge, England
> >>>>>> +44 1223 862599 and +44 1223 511455
> >>>>>> http://www.ninetiles.com
> >>>>>> 
> >>>>>> _______________________________________________
> >>>>>> 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
> >>> 
> >>> _______________________________________________
> >>> 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

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