Re: [Detnet] Congestion Protection name change (was: Re: Tsvart last call review of draft-ietf-detnet-architecture-08)

"Andrew G. Malis" <agmalis@gmail.com> Mon, 10 December 2018 15:28 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D330F130E3C; Mon, 10 Dec 2018 07:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 W7d72SeYqZKi; Mon, 10 Dec 2018 07:28:29 -0800 (PST)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F1F9124C04; Mon, 10 Dec 2018 07:28:29 -0800 (PST)
Received: by mail-qk1-x735.google.com with SMTP id y78so6653549qka.12; Mon, 10 Dec 2018 07:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fZeGavJ9DNoEc+V5p8px/EgHjC0CC7b93ZY6SwQjlxk=; b=IlHaTB4gz+CLN5SHTkuBOnkJFsRD3/eMbsYT3B8PMMUHS03Hb5ZvqUwIlZG7WmK/Mc XK3OSuvSrNGyPMxiFAKeUhboaziBulM4bmvx3qSzS8U5Ot1jbT1t+zfP1aWGL9Zmfisa IZ1EH2MAHgIUuHr7zJhLne7K0M/dUFKCkWGkg78KfeNDxXMZek7lliIUFApIO6N6k/Ci X2GSQL2tJaUU7p3hTHKe/r3LAQRtboQCmJcjc00PZkUIR2dweZiTdoGHi0mqIrfSSHWS 8LwipQ9BHMWfYU2C7Z061Gt+9XdgfV7Z17BcnP1rKdqR4w042PgPuwmhf03VKDWnMaJi Fdug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fZeGavJ9DNoEc+V5p8px/EgHjC0CC7b93ZY6SwQjlxk=; b=nU6uRc2ItJUQnh7gzxk4EHWuKMPDXfKi7nSBF+YtxoizEy3iZBKegguiOhw1TAFXAE jIuQNjxW2UEnNvtyuoHa4kPWd7U+9nyqPj9lDGEUqFLcxgyEi6/J34Il6wyAdOeZQaa7 UVXiYOA5dQkllBb6kW/vZUAMHc5HnXLBeahXX74S/T11TXVZZVJ3NAbBIbAEeMv/ycNr sf2RC6HKDQBPF3YyJDsZMXEtlZovtDfa4KMpuDyGedP/sIUycLJPCDJ6v4e0bp+mNeee m3IXH9Vx9sg2TeK4658MzLC0eZwpWEjzdGyDmN3Isu/0P2TGKZrmT6Ni9S6y15vHUbz6 laPA==
X-Gm-Message-State: AA+aEWa88Jx+hcOQ0hhgVmVqT4BpG+e/KIuAWAP7iozN6mnIDQUF8T3n 3XJKehaqs3kp4euhWrEq8rfksKQg/cUEDiLCjZYUFQ==
X-Google-Smtp-Source: AFSGD/XHoSryglczoYvXUqpKuv86rnc/c5luJXKo+KNZfnIBKX4laQs1semf8VurU868WKNBv6UsYA7gEXV1AzGhnUI=
X-Received: by 2002:a37:4651:: with SMTP id t78mr11161993qka.210.1544455708329; Mon, 10 Dec 2018 07:28:28 -0800 (PST)
MIME-Version: 1.0
References: <153817345967.27205.135001179751151278@ietfa.amsl.com> <fdf872d6-08a6-2c33-de21-9dd1506c1d21@labn.net> <6EC6417807D9754DA64F3087E2E2E03E2D16A4D3@rznt8114.rznt.rzdir.fht-esslingen.de> <e38ab4d6-0924-ab60-b1dc-4ac26600044c@labn.net> <090ae5ba-e44c-f8fa-7259-5ab1b01fb23c@ericsson.com> <a26edd340da7432d8c5d17cd9726b8c4@XCH-RCD-001.cisco.com>
In-Reply-To: <a26edd340da7432d8c5d17cd9726b8c4@XCH-RCD-001.cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 10 Dec 2018 10:28:16 -0500
Message-ID: <CAA=duU29DEYo1_QfQTKdcSE3sdNYXtbJYdSuQ38iLFUN34HUtA@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: János Farkas <janos.farkas@ericsson.com>, Lou Berger <lberger@labn.net>, Michael.Scharf@hs-esslingen.de, Transport Area Review Team <tsv-art@ietf.org>, detnet WG <detnet@ietf.org>, draft-ietf-detnet-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ddcaa9057cac9d1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/t_hQhe9b7GA5YEpNZkdooVsE-cY>
Subject: Re: [Detnet] Congestion Protection name change (was: Re: Tsvart last call review of draft-ietf-detnet-architecture-08)
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2018 15:28:32 -0000

Since we're guaranteeing a particular level of service as generally used in
SLAs, I would prefer the term "service level guarantee", which includes
bounds on packet delay and packet loss.

If we want, we can extend the definition to include examples of the
mechanisms used to provide the guarantee, such as queue management, link
and node resource management, shaping, preemption, scheduling, and so on,
but we don't have to.

Cheers,
Andy

On Mon, Dec 10, 2018 at 9:48 AM Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> The problem János is that we do not only avoid loss. We also control
> latency. So "queuing loss" is too limitation.
> We are protecting the resources that are necessary, or providing
> guarantees that they are available. To provide the service.
> Maybe "service guarantees" could be good?
> Pascal
>
> > -----Original Message-----
> > From: János Farkas <janos.farkas@ericsson.com>
> > Sent: lundi 10 décembre 2018 18:30
> > To: Lou Berger <lberger@labn.net>; Scharf, Michael <Michael.Scharf@hs-
> > esslingen.de>
> > Cc: tsv-art@ietf.org; detnet@ietf.org; draft-ietf-detnet-
> > architecture.all@ietf.org
> > Subject: Congestion Protection name change (was: Re: [Detnet] Tsvart
> last call
> > review of draft-ietf-detnet-architecture-08)
> >
> > Hi,
> >
> > As I understand, there is confusion around two DetNet terms.
> > We are removing "transport".
> >
> > The other one is "congestion" and "congestion protection".
> >
> > Brief description of congestion protection in Section 3.1:
> >
> >     Congestion protection operates by allocating resources along the path
> >     of a DetNet flow, e.g., buffer space or link bandwidth. Congestion
> >     protection greatly reduces, or even eliminates entirely, packet loss
> >     due to output packet congestion within the network, but it can only
> >     be supplied to a DetNet flow that is limited at the source to a
> >     maximum packet size and transmission rate.  Note that congestion
> >     protection provided via congestion detection and notification is
> >     explicitly excluded from consideration in DetNet, as it serves a
> >     different set of applications.
> >
> >     Congestion protection addresses two of the DetNet QoS requirements:
> >     latency and packet loss.  Given that DetNet nodes have a finite
> >     amount of buffer space, congestion protection necessarily results in
> >     a maximum end-to-end latency.  It also addresses the largest
> >     contribution to packet loss, which is buffer congestion.
> >
> > Detailed description is in Section 3.2.1.
> >
> > We wanted to have a brief collective term for the mechanisms used to
> avoid
> > queuing related packet loss (including buffer overflow etc.).
> >
> > Based on the discussions, we should have a term that does not include
> > "congestion".
> > ("Service Protection" is another DetNet term, hence we may consider a
> term
> > without "protection" to minimize confusion.)
> >
> > I suggest to replace "congestion protection" with "queuing loss
> avoidance".
> >
> > After agreeing in the terminology cahnge (if any), the text has to be
> updated
> > accordingly.
> >
> > What do you think?
> >
> > Best regards,
> > Janos
>
>