Re: [Raw] Proposed RAW charter

Justin Dean <> Tue, 14 January 2020 16:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 068C1120A0C for <>; Tue, 14 Jan 2020 08:47:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UMjLd1jKqDzS for <>; Tue, 14 Jan 2020 08:47:25 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 692491209FC for <>; Tue, 14 Jan 2020 08:47:25 -0800 (PST)
Received: by with SMTP id n8so5951915qvg.11 for <>; Tue, 14 Jan 2020 08:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yCZSjHBRbFSMBLly1pJ86RF97T/oBPt+GzfRIvwKRYc=; b=LKjMw3oPO6fda6pJpGNWDpHnCXKDXPVSW7RWJaS6pRaRSYcOjvVlK+jOKJNYNTKvNN t54K9fXcOyR7w+i0TiqEGjPesk5a9sPCGaniDMINIQ2cAqfKWy691Ty31Ia5o2larMoS LGMno7lWPjuiC6z+elIiZ+sb8lrYoSkUjVZowELLSCgEs6ySOhkpoDum8hwaT5k2jOiK A6sN/+ddC9BSbS8pJj9GcmGOWk8nmw3Blz/RWMSdYAKADc4lYHHbzBN+EzAM1an0Y2n4 qoET4guKPvmdKXU7jmky3LvlIJaBu1c0cIYBVE4jfa/3x1AR6mwUTZORgo0M2wVWYE4F Kw0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yCZSjHBRbFSMBLly1pJ86RF97T/oBPt+GzfRIvwKRYc=; b=J1m72xDuW/ASlRK1AxP5/wi+cYmc8JxaAMDwPzYpsn63K68nbIaActftwLz4BID++J kkAOPHGZNWLkU77tGV+QFjY0+49W2oc3zD45S++kMPJph7gfime5KFss5pMsVN7O5JdC tPSt0IKser19yg+DOnkuVuqV6R6mEVn9aY9dam/Oph1t+TGg2tDs/wnl4J2yOy9X8BCw nW+52aKmN0gXdmcmU41Bsd4PQ1X6392uLaNq2E0mZpdN2njvPo/pOy9hj5AvT8AsU76+ N9ImE3emotXFapfMCMin5n/7qMrg3CwdFiJm1/Id5KmJmUI724NF4b5t6lt/k8Q+P0Gu y+dQ==
X-Gm-Message-State: APjAAAXAxPsYjz5rCyhKiQ91gEPtXpT62dX5ykQxCQh8jDwNRW55wRPo qMnSD+wX4s87GfkHMNBMwnPhn7t9+jI6jRJUHp19lA==
X-Google-Smtp-Source: APXvYqx5SORpBOebDUGpZv/MQ+VM7fzBdQqE4Mu14YrPSIEbl8GRyC799gcOp4zMumajW4fhxaglBKEzKhGTpH0suSw=
X-Received: by 2002:ad4:580b:: with SMTP id dd11mr17492141qvb.242.1579020444243; Tue, 14 Jan 2020 08:47:24 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Justin Dean <>
Date: Tue, 14 Jan 2020 09:47:13 -0700
Message-ID: <>
To: "" <>
Content-Type: multipart/alternative; boundary="000000000000ac1bb7059c1c58e5"
Archived-At: <>
Subject: Re: [Raw] Proposed RAW charter
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Jan 2020 16:47:31 -0000

Comments inline below.
Justin Dean

On Mon, Jan 13, 2020 at 2:14 PM BRUNGARD, DEBORAH A <> wrote:

> Hi RAW,
> Happy New Year!
> As promised, here’s a proposed charter. Please send comments. I’ll be
> submitting it to the IESG for the first step (internal review) by the end
> of the week.
> Note, while the BoF had the most support for doing only use cases and
> requirements, I’ve included here also a gap analysis and an
> architecture/framework document. I think the gap analysis will be the most
> critical. The architecture/framework is intended not to be the typical
> comprehensive protocol architecture, but only architectural aspects of what
> is needed to enable deployment and usage in a wireless network.
> Looking forward to your comments-
> Deborah
> (your supporting AD)
> --
> Reliable and Available Wireless (RAW) provides for high reliability and
> availability for IP connectivity over a wireless medium.

This very first sentence seems off to me as later in the charter it's
mentioned that no solutions are going to be directly in scope so will the
work actually provide this or just outline the challenges and point towards
solutions in DetNet/Manet/other WGs?  If no solutions will be in scope then
I suggest leading with the next 1-2 sentences mixed with the first as way
of introduction to RAW.

> The wireless medium presents significant challenges to achieve
> deterministic properties such as low packet error rate, bounded consecutive
> losses, and bounded latency. RAW extends the DetNet Working Group concepts
> to provide for high reliability and availability for an IP network
> utilizing scheduled wireless segments and other media, e.g.,
> frequency/time-sharing physical media resources with stochastic traffic:
> IEEE Std. 802.15.4 timeslotted channel hopping (TSCH), 3GPP 5G
> ultra-reliable low latency communications (URLLC), IEEE 802.11ax/be, and
> L-band Digital Aeronautical Communications System (LDACS).
and etc. is needed here unless this his is exhaustive.

> Similar to DetNet, RAW will stay abstract to the radio layers underneath,
> addressing the Layer 3 aspects in support of applications requiring high
> reliability and availability.
> While DetNet solutions apply to both wireless and wired, there has been
> recent industry interest for wireless applications which were not initially
> included in the DetNet use cases. One critical application is Aeronautical
> Data Communications. The Aeronautical standards work on a physical layer
> and data link layer for data communications is reaching maturity and there
> is significant interest in developing an IP connectivity solution.
(using wireless links?)

> In the interests of providing timely solutions for these newly identified
> industry applications, RAW’s focus will be on identifying use cases and
> requirements for these new applications. RAW will solicit input on
> deployment plans, requirements, and operational practices (including
> security and privacy aspects) for these newer industrial applications.
> RAW’s primary focus is on identifying areas where the DetNet adaptation to
> wireless networks requires additional supporting mechanisms. The RAW
> Working Group will also examine the applicability of other existing IETF
> work, e.g.., DLEP.  The RAW Working Group will provide input to the DetNet
> Working Group, MANET Working Group, and other IETF Working Groups, and
> cooperate in reviewing solutions to RAW’s identified deployment problems.
> RAW is not chartered to work on a solution, if solution work is needed in
> addition to the DetNet solution work or other existing solution work in the
> IETF, it will be coordinated on where the work will be done.
In terms of presentation of information the critical bit of info that RAW
will NOT work on solutions seems a bit buried here and this should be moved
towards the top.

> The RAW Working Group is planned to be a short timeframe (12-18 months)
> Working Group to quickly address these newer industry applications. The
> initial milestones will be comprised of Informational documents. The
> documents may exist individually or on a git repository.
Unnecessary suggest cutting previous sentence.

> The use case document may consist of one or more documents to allow
> users/operators the opportunity to provide comprehensive deployment plans
> for these new (to IETF) technologies. The group will closely coordinate
> with the DetNet and MANET Working Groups. The work produced by this group
> may be of interest to other SDOs, 3GPP, IEEE, and the Aeronautical
> industry. No formal co-ordination is anticipated with these groups at this
> time.
"these groups" meaning "these non-IETF groups"?

> Milestones
> Draft for “Use Cases” adopted by WG
> Draft for “Problem Statement and Requirements” adopted by WG
> Draft for “Architectural/Framework aspects to enable deployment and usage
> in a wireless network” adopted by WG
> Draft for “Evaluation of Existing IETF Tools and Gap Analysis” adopted by
> WG
> Draft for “Use Cases” submit for publication
> Draft for “Problem Statement and Requirements” submit for publication
> Draft for “Architectural/Framework aspects to enable deployment and usage
> in a wireless network” submit for publication
> Draft for “Evaluation of Existing IETF Tools and Gap Analysis” submit for
> publication

> --
> Raw mailing list