Re: [Detnet] Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 19 December 2018 17:01 UTC

Return-Path: <pthubert@cisco.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 7D221130E70 for <detnet@ietfa.amsl.com>; Wed, 19 Dec 2018 09:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.566
X-Spam-Level:
X-Spam-Status: No, score=-12.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 4Yql8Iw3RO7a for <detnet@ietfa.amsl.com>; Wed, 19 Dec 2018 09:01:08 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 690B5130E6D for <detnet@ietf.org>; Wed, 19 Dec 2018 09:01:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20015; q=dns/txt; s=iport; t=1545238868; x=1546448468; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MuII1oyfcC/+uSs59N7bmzRD+4reI8H+H5kjHZJwudM=; b=BvhNMkW6+0NWF6pViM1D63EgMNlpheFx49VRsuCHMLIlCvVL3NQWbq/Y Rpyf1fNMTn6lG5dvxIyzTHwD1QdnowPYBBBpef408Ettlsn14HLmkEkUm xPIIjCvZb+30Cvjiy1DjCF/aCE6oz8PFhCxIJMGsQB8v66PDce8kloWwD I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAC2eBpc/4kNJK1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ12ZoECJwqMDIt8gg2JFY5IgXsLAQEihEoCgmsiNAkNAQMBAQIBAQJtHAyFPAEBAQEBAi1HBRACAQgRBAEBKAchERQJCAIEDgUIgxuBHUwDFQ+pUx+EDgEDAg4BAg8tAYMFDYIdjD8XgUA/gRGCFFAuglciJQEBAQEBF4EgXQiFIQKLP4QBXoV5imozCQKHDochgykggV5NhFKKXIlIhHmBE4oHAhEUgScfOIFWcBWDJwmBblmDOIUUhT9BMQEBjBiBLoEfAQE
X-IronPort-AV: E=Sophos;i="5.56,373,1539648000"; d="scan'208,217";a="497302238"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2018 17:01:06 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id wBJH16Ep004378 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Dec 2018 17:01:06 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 19 Dec 2018 11:01:05 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Wed, 19 Dec 2018 11:01:05 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: János Farkas <janos.farkas@ericsson.com>, "Grossman, Ethan A." <eagros@dolby.com>
CC: "jouni@gmail.com" <jouni@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "detnet@ietf.org" <detnet@ietf.org>, Balázs Varga A <balazs.a.varga@ericsson.com>, "Maik Seewald (maseewal)" <maseewal@cisco.com>
Thread-Topic: [Detnet] Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M
Thread-Index: AQHUl7WvHqsPXbYGrEq3xUVQ6BqknqWGRPZAgABoMAD//5u4wA==
Date: Wed, 19 Dec 2018 17:00:58 +0000
Deferred-Delivery: Wed, 19 Dec 2018 17:00:29 +0000
Message-ID: <fe360490b91a4fbfb5223e23869904ad@XCH-RCD-001.cisco.com>
References: <CY1PR0601MB1408FD124CDE12A8B4980100C4A30@CY1PR0601MB1408.namprd06.prod.outlook.com> <b6817ea0-869a-75e6-218f-c478f485e1d8@ericsson.com> <DM6PR06MB5659B678012FDCA7001247DFC4BD0@DM6PR06MB5659.namprd06.prod.outlook.com> <b018e8d7-7499-89bb-4f89-70a6640b8bde@ericsson.com> <ffa69772d1ef41538401e5e38e42e08e@XCH-RCD-001.cisco.com> <9fe3ec20-5623-acc6-46a3-22215beca7cb@ericsson.com>
In-Reply-To: <9fe3ec20-5623-acc6-46a3-22215beca7cb@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.4]
Content-Type: multipart/alternative; boundary="_000_fe360490b91a4fbfb5223e23869904adXCHRCD001ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/2hUW2R41lFI3M6RMooTqtBcSJ90>
Subject: Re: [Detnet] Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M
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: Wed, 19 Dec 2018 17:01:13 -0000

Works for me, this is essential.

From: János Farkas <janos.farkas@ericsson.com>
Sent: mercredi 19 décembre 2018 17:58
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Grossman, Ethan A. <eagros@dolby.com>
Cc: jouni@gmail.com; Suresh Krishnan <suresh.krishnan@gmail.com>; detnet@ietf.org; Balázs Varga A <balazs.a.varga@ericsson.com>; Maik Seewald (maseewal) <maseewal@cisco.com>
Subject: Re: [Detnet] Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M

Well, I'd not enter MTBF discussion at this stage.

It is just example in the brackets. What about skipping numbers to get:

"Low packet loss (e.g., limited number of consecutive packets)"

?

The special aspect brought in really is the aspect of consecutive packets.

Regards,
Janos
On 12/19/2018 5:50 PM, Pascal Thubert (pthubert) wrote:
Hello  János

I agree to change the sentence. Zero is not reasonable in the real world, even in wired space : ) What about

"Low packet loss (e.g.,  one in a million, one in a billion, min time between losses, min packets between losses, strictly bounded number of consecutive losses)"
Maybe that's too many examples but when you look up the (old) art of "reliability " you end up with terms such as MTBF...
All the best

Pascal

From: detnet <detnet-bounces@ietf.org><mailto:detnet-bounces@ietf.org> On Behalf Of János Farkas
Sent: mercredi 19 décembre 2018 17:13
To: Grossman, Ethan A. <eagros@dolby.com><mailto:eagros@dolby.com>
Cc: jouni@gmail.com<mailto:jouni@gmail.com>; Suresh Krishnan <suresh.krishnan@gmail.com><mailto:suresh.krishnan@gmail.com>; detnet@ietf.org<mailto:detnet@ietf.org>; Balázs Varga A <balazs.a.varga@ericsson.com><mailto:balazs.a.varga@ericsson.com>; Maik Seewald (maseewal) <maseewal@cisco.com><mailto:maseewal@cisco.com>
Subject: Re: [Detnet] Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M

I just tried to resolve the concern around burstless.

Actually, the numbers may not be right.

Checking IEC/IEEE 60802 contributions
https://1.ieee802.org/tsn/iec-ieee-60802-tsn-profile-for-industrial-automation/

Use Cases: http://www.ieee802.org/1/files/public/docs2018/60802-industrial-use-cases-0918-v13.pdf
and traffic type characterization: http://www.ieee802.org/1/files/public/docs2018/60802-ademaj-traffic-type-characterization-1118-v01.pdf
indicate that the most stringent requirement is zero loss.
The next one is how many consecutive packets may be lost
There are more relaxed cases.

This section is: 7.4.  Industrial M2M Asks

Maybe we should focus on the stringent cases.

What about updating the bullet to:

"Low packet loss (e.g., zero, limited number of consecutive packets)"

?

Regards,
Janos


On 12/18/2018 8:31 PM, Grossman, Ethan A. wrote:
Thanks Janos,
Doesn't 0.1-1% sound like an awful lot of packet loss?
Do I understand correctly that you mean:
"Low packet loss (0.1-1 % of packets can be lost, but only a bounded number of consecutive packets can be lost)"

I guess I still don't exactly understand the intent, can you please clarify?
Thanks, and sorry for being dense here.
Ethan.

From: János Farkas <janos.farkas@ericsson.com><mailto:janos.farkas@ericsson.com>
Sent: Tuesday, December 18, 2018 8:21 AM
To: Grossman, Ethan A. <eagros@dolby.com><mailto:eagros@dolby.com>
Cc: jouni@gmail.com<mailto:jouni@gmail.com>; Maik Seewald (maseewal) <maseewal@cisco.com><mailto:maseewal@cisco.com>; Balázs Varga A <balazs.a.varga@ericsson.com><mailto:balazs.a.varga@ericsson.com>; detnet@ietf.org<mailto:detnet@ietf.org>; Suresh Krishnan <suresh.krishnan@gmail.com><mailto:suresh.krishnan@gmail.com>
Subject: Re: Resolving the remaining Use Cases Draft Comments - Cellular Radio and Industrial M2M

Hi Ethan,

Maybe it is not a god phrase, but the intention with the phrase that the loss should be burstless was that consecutive packets should not be lost.
Perhaps the maximum consecutive loss tolerance parameter describes it better in https://tools.ietf.org/html/draft-ietf-detnet-flow-information-model-02<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Ddetnet-2Dflow-2Dinformation-2Dmodel-2D02&d=DwMD-g&c=lI8Zb6TzM3d1tX4iEu7bpg&r=ZcHC6wX_gDwPDcfMaFNZiQ&m=0W0EQyafQ7HdKxGYDUDOn91m44yUJHQre2QdC0Pq5rI&s=xtlwetwJuYWGjTBmpNfLC8CvvhDk4x1YkRjNDTE0rws&e=>. It is the "maximum    number of consecutive packets whose loss can be tolerated"

Maybe updating the bullet in the use cases draft to:

"Low packet loss (0.1-1 %, limited number of consecutive packets)"

?

Regards,
Janos
On 12/16/2018 6:03 AM, Grossman, Ethan A. wrote:
Balazs, Janos:
* Section 7.4

What does burstless mean (especially in the context of low packet loss)?