[Raw] Roman Danyliw's Discuss on draft-ietf-raw-use-cases-08: (with DISCUSS and COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Thu, 17 November 2022 17:22 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: raw@ietf.org
Delivered-To: raw@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A0DC14F74B; Thu, 17 Nov 2022 09:22:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-raw-use-cases@ietf.org, raw-chairs@ietf.org, raw@ietf.org, corinna.schmitt@unibw.de, corinna.schmitt@unibw.de
X-Test-IDTracker: no
X-IETF-IDTracker: 9.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <166870577081.63597.12770105190077863670@ietfa.amsl.com>
Date: Thu, 17 Nov 2022 09:22:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/t5Uk52QtQVbERnn6XlfGZZT4R04>
Subject: [Raw] Roman Danyliw's Discuss on draft-ietf-raw-use-cases-08: (with DISCUSS and COMMENT)
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.39
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2022 17:22:51 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-raw-use-cases-08: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-raw-use-cases/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 12 states the situation accurately – “Each of the potential RAW
use-cases will have security considerations from both the use-specific
perspective.”  Where are these security and privacy considerations for these
uses cases discussed?  Are these in scope to solve for RAW?  A select list to
review would be:

** Section 3.*. Per the amusement park use case, what are the physical location
tracking and surveillance considerations?

** Section 7.*.  Per the vehicle platooning use case, what are the physical
location tracking privacy considerations?

** Section 8.*. Per the edge robotics use case, what are the privacy
considerations of the video surveillance?

** Section 9.*.  Per the ambulance use case, what are the security
considerations around exchanging health care information over a wireless WAN?

A clearer distinction of what is to be addressed at the protocol level, and
what seems like an application consideration is needed.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

** Section 1.
   Reliable and
   Available Wireless (RAW) is an effort to provide Deterministic
   Networking Mechanisms on a multi-hop path that includes a wireless
   physical layer.

Is this RAW the “RAW WG”?  If so, the WG doesn’t appear to be chartered to
provide the described solution.

** Section 2.5.

   Different safety levels need to be supported, from extremely safety
   critical ones requiring low latency, such as a WAKE warning - a
   warning that two aircraft come dangerously close to each other - and
   high resiliency, to less safety critical ones requiring low-medium
   latency for services such as WXGRAPH - graphical weather data.

I can appreciate the abstract idea of using certain information for safety
critical decision making.  However, can more detail be provided to translate
the “safety levels” to requirements of the data link or the “RAW protocol”? 
Mentioned already seems to be “low” vs. “low-medium” latency; and “high
resiliency” which should be read as guaranteed delivery or ability to use
multiple paths/radio technologies?  Or is “low latency” translated into a
design as the subsequent text suggests of “small packets” and resiliency
primarily about “choosing links”

** Section 2.5.*.  Low latency is stated as a requirement a few times.  Can
this be expressed quantitatively?  Use case owners (and readers) might have
their own subjective idea of what constitutes “low”.

** Section 3.1.
   Such
   deployment is a mix between industrial automation (i.e., Smart
   Factories) and multimedia entertainment applications.

In what way is “industrial automation” and “Smart Factories” the same in this
example?  One seems to connote automation of operational technology (as opposed
to IT).  The other seems to be a marketing term for OT building things – I’m
not sure.

** Section 3.2.
      Some non-time-critical tasks may
      rather use the cloud (predictive maintenance, marketing).

-- Marketing is mentioned as an example of a computational workload appropriate
for the cloud but it isn’t noted as an application in Section 3.1.  Perhaps it
should be made more explicit.

-- If these tasks are “non-time-critical”, why can’t traditional wireless
technologies address them (i.e., why can’t they be solved without RAW)?

** Section 4.2.1
   A rare packet loss is usually admissible, but
   typically 4 losses in a row will cause an emergency halt of the
   production and incur a high cost for the manufacturer.

What is the basis for the “4 losses” (as opposed to say 3 or 5)?  Can this be
cited with a reference?

** Section 6.1.
      But Wi-Fi has an
      especially bad reputation among the gaming community.  The main
      reasons are high latency, lag spikes, and jitter.

This statement is suggestion a subjective assessment of the user experience. 
Is it technically accurate?

** Section 6.1.  The use cases seem to overlap:

-- Can one do “real-time mobile gaming” on a “wireless console”?

-- Are “cloud gaming” and “wireless console” mutually exclusive categories? 
Can’t an Xbox use Wi-Fi 5 to use the “Xbox Cloud Gaming” service?

** Section 7.1

the Spanish traffic control has recently introduced
   a fleet of drones for quicker reactions upon traffic congestion
   related events

Could a reference please be provided.

** Section 8.2.  What is “very low latency” in this context?

** Section 9.1.  I don’t have any insight into how a network infrastructure is
built on an ambulance.  Are these systems all really on the same LAN in
practice now?  Is the navigation systems connected to the vital signs sensor? 
Don’t these discrete functions all function as their own WWAN?

** Section 9.1.  What is a “radio-WAN”?  Is this the same as a wireless WAN?

** Section 9.4.  What is “high availability” in this context?

Editorial
** Section 1.  Editorial.  “Deterministic Networking in the IP world …” uses
colloquial, consider rephrasing.

** Section 1.  Editorial
So far, Open Standards for Deterministic Networking ...

Why is “Open Standards for Deterministic Networking …” capitalized?  Which of
these are proper nouns?

** Section 2.3.  Typo. s/accomodate/accommodate/

** Section 2.4.  Editorial.
Thus, making use of wireless
   technologies is a must

Consider alternative language to this colloquial syntax.

** Section 3.1.  Editorial
   *  Emergency: safety has to be preserved, and must stop the
      attraction when a failure is detected.

Consider being clearer on safety for whom – is it the attraction operator and
visitor/rider/bystander?

** Section 3.3.  Editorial.
   Wireless also increases the
   reconfigurability, enabling to update an attraction at a lower cost.
   The frequent renewal helps to increase the customer loyalty.

This first sentence doesn’t parse for me.  As such, I don’t follow the link to
customer loyalty in the second sentence.  Is the idea here that wireless allows
the attractions to be swapped or adapted more frequently than if a wired
network was used? In turn, this variability of offerings in the amusement park,
attracts repeat visits by customers.

** Section 4.2.1.  Editorial.
   Finally, some industries exhibit
   hybrid behaviors, like canned soup that will start as a process
   industry while mixing the food and then operate as a discrete
   manufacturing when putting the final product in cans and shipping
   them.

The discrete steps of “process industry”, “discrete manufacturing” aren’t
explained; and don’t link to the previous narrative of “process control”,
“factory automation” or “motion control”.

** Section 4.2.2.  Editorial.  Consider replacing the colloquial phrases:
--  “Holy Grail of the Industrial Internet of Things”.

-- “carpeted floor over IP”

** Section 4.3.  Editorial. s/a few thousands of flexions/a few thousand
flexions/

** Section 4.4.  Editorial.
  RAW mechanisms should be
   able to setup a Track
 Should “Track” be capitalized?

** Section 5.3.

   Deployed announcement speakers, for instance along the platforms of
   the train stations, need the wireless communication to forward the
   audio traffic in real time.

Why do train stations needed wireless communication (as opposed to wired being
acceptable)?

** Section 6.1.  Is “Real-Time Mobile Gaming” assuming that the connected
players and game servers are using the Internet to connect them?  How can RAW
help then?

** Section 6.1.  Editorial.
*  Wireless Console Gaming: Playing online on a console has 2 types
      of internet connectivity, which is either wired or Wi-Fi.

Isn’t the definition of “wireless console gaming” that a wireless connection is
used?  The distinction to wired doesn’t make sense to me.

** Section 6.4.  Typo. s/importan/important.

** Section 9.  Editorial. Is an “Instrumented emergency vehicle” only scoped to
“emergency medical vehicles”?  If so, I recommend renaming the section.

** Section 9.4.  Editorial. Can “radio footprint” be more precisely defined. 
Does this mean a seamless hand-off approach is needed between multiple
base-stations of some kind to keep the radio connected?