Re: [Raw] I-D Action: draft-ietf-raw-oam-support-03.txt

Greg Mirsky <gregimirsky@gmail.com> Wed, 23 February 2022 03:02 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEC613A0E05 for <raw@ietfa.amsl.com>; Tue, 22 Feb 2022 19:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 hxHzlQNHv7i3 for <raw@ietfa.amsl.com>; Tue, 22 Feb 2022 19:02:52 -0800 (PST)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 73B613A0E03 for <raw@ietf.org>; Tue, 22 Feb 2022 19:02:52 -0800 (PST)
Received: by mail-ed1-x530.google.com with SMTP id i11so39947263eda.9 for <raw@ietf.org>; Tue, 22 Feb 2022 19:02:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oqe+cyJOVhtp51eO0fR3MgQ2SyJF9thA0nA1pIh+5dU=; b=BITX2PuuW7vaaTV2V//wqncuRrugSM5CUjE3VqoEpw9IBDGi0tclqwaToKAMgVYQ0Z 7teB9OTJtqmCfdZN8gLhTFJm2zTrVgdGxXIA/L5dVbis5sywNPtyWGma2Us0ER4kNXkz zW8iQHGpQQ4t6BCGzjp3qqC84bt+jHZ5vRAjOHOR9Rm+g6LVQKfMvUXgG5Ybiyqo64nh X3glH07ac0ZgLpIsTihtUwa0pgak2PtFHVTn04isCkQviGdGLjHTmI2f4+lwkqwcWbYX RC/1eeaCU6i4Gtv+twjuQoZgxx1UUUVyhwN9A6PWVzlGJNeYHHqO/0igpEcmutetRoGG qCUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oqe+cyJOVhtp51eO0fR3MgQ2SyJF9thA0nA1pIh+5dU=; b=5B0TiEFHxt3DfSEft0vfWiViRrGZgVLmaCK/mGOLArVlSUUEcN1DQEOFsisetz7EDG n/9tGd1wuClw2Sn78STlUiVHlqVwvqm6moQxA7pKEAd6VjToulcYHp76ZCCZ0D0rFNdT yjHPznN1vHeyhD5G6pQx2oFnh/9W9Bj8BCaqaLU+axWm+SYNDnQPoHMVS/1CE8fJy3DL 18SwHtDORTarLX6L4gZ79+upxu9KUxbiDHva5c25zLbUlovbwWigFa2vEUaCm5T8+JUV uzy5chnX9rqF5MfqI431Lz+fZnSd2k2a8PlyIEcUqMtOsthCv2e1picycwQuAH6fdO/k fT2Q==
X-Gm-Message-State: AOAM532jmCdO37aSDbxB3DbSmAki+lM9DS3PVpUOv0oU3KfgPKf+2dVt 3cVfGRDm5K3msCoJNgwIPZMEoCiLOI+eiltLXIaGrJzQ1+4=
X-Google-Smtp-Source: ABdhPJwUaS9og53RyBIRK0RBfdDGIpl7TUdG+i+0VBvmTD6/wp0Lz7BQ4+OUD3I3R7Eya6GSzgjC9j2A7LSMSq91/PM=
X-Received: by 2002:a50:bf0f:0:b0:410:c512:cb6f with SMTP id f15-20020a50bf0f000000b00410c512cb6fmr29126331edk.262.1645585370335; Tue, 22 Feb 2022 19:02:50 -0800 (PST)
MIME-Version: 1.0
References: <164240876858.16324.3818187102115260103@ietfa.amsl.com> <F9AF1612-C73F-4B28-A2A1-BCBFD9D28AF4@cnrs.fr> <378D7E5C-BBE1-4AE1-B2F4-754806300F89@cnrs.fr>
In-Reply-To: <378D7E5C-BBE1-4AE1-B2F4-754806300F89@cnrs.fr>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 22 Feb 2022 19:02:38 -0800
Message-ID: <CA+RyBmUQGRP62jnkUpj5CixZruPqNkyG2CEgO6wofd7gxM-6Dg@mail.gmail.com>
To: Fabrice Theoleyre <fabrice.theoleyre@cnrs.fr>
Cc: raw@ietf.org
Content-Type: multipart/alternative; boundary="000000000000724e4e05d8a6b349"
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/pUBUP6JjXRjqIVzMlQF428rxSws>
Subject: Re: [Raw] I-D Action: draft-ietf-raw-oam-support-03.txt
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Wed, 23 Feb 2022 03:02:57 -0000

Hi Fabrice,
thank you for the timely reminder. I believe that the draft is stronger
now. I have several questions that we might discuss:

   - It is not clear what we are saying in the Terminology section with the
   following:

The data plane takes the individual decision.

Can you help me by giving an example?


   - Further, in the same section, active measurement methods are
   discussed. I agree with the text but have a question about the following:

      Active methods may implement

      one of these two strategies:

      -  In-band: control information follows the same path as the data

         packets.  In other words, a failure in the data plane may

         prevent the control information from reaching the destination

         (e.g., end-device or controller).


      -  out-of-band: control information is sent separately from the

         data packets.  Thus, the behavior of control vs. data packets

         may differ;

For an active measurement method, what is the control information? Active
OAM is differentiated from other measurement methods by its reliance on
generated test packets. As stressed in the text, test packets must be
in-band with the monitored data flow. I wonder if that text is useful for a
reader.


   - The following text seems to indicate that "control" is being used as
   another term for "test":

      piggybacking vs. dedicated control packets: control information

      may be encapsulated in specific (dedicated) control packets.

Though if I apply that assumption the result is not clear to me either:
      piggybacking vs. dedicated test packets: test information
      may be encapsulated in specific (dedicated) test packets.

Am I missing something?


I hope my notes make sense.

Regards,
Greg

On Tue, Feb 22, 2022 at 12:59 AM Fabrice Theoleyre <
fabrice.theoleyre@cnrs.fr> wrote:

> Dear colleagues,
>
> We plan to present this novel version during the next IETF meeting. If
> some of you could have a look at the draft before the next meeting, it
> would be fantastic!
>
> Best regards,
> Fabrice
>
>
>
> > Le 17 janv. 2022 à 09:41, Fabrice Theoleyre <fabrice.theoleyre@cnrs.fr>
> a écrit :
> >
> > Dear all,
> >
> > We have updated the draft (novel requirements section, consistency with
> the other RAW drafts, editorial modifications, etc.)
> >
> > We would be grateful if you have any feedback for us.
> >
> > Best regards,
> > Fabrice
> >
> >
> >
> >
> >> Le 17 janv. 2022 à 09:39, internet-drafts@ietf.org a écrit :
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >> This draft is a work item of the Reliable and Available Wireless WG of
> the IETF.
> >>
> >>       Title           : Operations, Administration and Maintenance
> (OAM) features for RAW
> >>       Authors         : Fabrice Theoleyre
> >>                         Georgios Z. Papadopoulos
> >>                         Greg Mirsky
> >>                         Carlos J. Bernardos
> >>      Filename        : draft-ietf-raw-oam-support-03.txt
> >>      Pages           : 16
> >>      Date            : 2022-01-17
> >>
> >> Abstract:
> >>  Some critical applications may use a wireless infrastructure.
> >>  However, wireless networks exhibit a bandwidth of several orders of
> >>  magnitude lower than wired networks.  Besides, wireless transmissions
> >>  are lossy by nature; the probability that a packet cannot be decoded
> >>  correctly by the receiver may be quite high.  In these conditions,
> >>  providing high reliability and a low delay is challenging.  This
> >>  document lists the requirements of the Operation, Administration, and
> >>  Maintenance (OAM) features are recommended to construct a predictable
> >>  communication infrastructure on top of a collection of wireless
> >>  segments.  This document describes the benefits, problems, and trade-
> >>  offs for using OAM in wireless networks to achieve Service Level
> >>  Objectives (SLO).
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-raw-oam-support/
> >>
> >> There is also an HTML version available at:
> >> https://www.ietf.org/archive/id/draft-ietf-raw-oam-support-03.html
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-raw-oam-support-03
> >>
> >>
> >> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
> >>
> >>
> >> --
> >> RAW mailing list
> >> RAW@ietf.org
> >> https://www.ietf.org/mailman/listinfo/raw
> >
>
> --
> RAW mailing list
> RAW@ietf.org
> https://www.ietf.org/mailman/listinfo/raw
>