Re: [Detnet] OAM terms

Dangjuanna <dangjuanna@huawei.com> Thu, 08 July 2021 02:23 UTC

Return-Path: <dangjuanna@huawei.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 9F9833A08E7; Wed, 7 Jul 2021 19:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 E0YLTuuNqCz5; Wed, 7 Jul 2021 19:23:44 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92853A08DC; Wed, 7 Jul 2021 19:23:43 -0700 (PDT)
Received: from fraeml735-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GL0J21JVRz6K61K; Thu, 8 Jul 2021 10:15:30 +0800 (CST)
Received: from kwepeml100004.china.huawei.com (7.221.188.19) by fraeml735-chm.china.huawei.com (10.206.15.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 8 Jul 2021 04:23:39 +0200
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by kwepeml100004.china.huawei.com (7.221.188.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 8 Jul 2021 10:23:37 +0800
Received: from kwepeml500003.china.huawei.com ([7.221.188.182]) by kwepeml500003.china.huawei.com ([7.221.188.182]) with mapi id 15.01.2176.012; Thu, 8 Jul 2021 10:23:37 +0800
From: Dangjuanna <dangjuanna@huawei.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, "DetNet WG" <detnet@ietf.org>, "raw@ietf.org" <raw@ietf.org>
CC: Fabrice Theoleyre <theoleyre@unistra.fr>, "Black, David" <David.Black@dell.com>, "gregory.mirsky@ztetx.com" <gregory.mirsky@ztetx.com>, =?gb2312?B?QmFsqKJ6cyBWYXJnYSBB?= <balazs.a.varga@ericsson.com>, Janos Farkas <Janos.Farkas@ericsson.com>
Thread-Topic: OAM terms
Thread-Index: Addybr/Aq0dUYoGVQjOseRZv5h1O5gBMBxtQ
Date: Thu, 8 Jul 2021 02:23:37 +0000
Message-ID: <bfd65610fc004061a721da3d819fd07f@huawei.com>
References: <CO1PR11MB4881C3DA1B547BA27DB21C07D81B9@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881C3DA1B547BA27DB21C07D81B9@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.235.250]
Content-Type: multipart/alternative; boundary="_000_bfd65610fc004061a721da3d819fd07fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/bH9gcJyL1ZIwwEDSAkdF4N4Aj-Q>
Subject: Re: [Detnet] OAM terms
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: Thu, 08 Jul 2021 02:23:49 -0000

Hi Pascal,

Please see below.

From: detnet [mailto:detnet-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: 2021年7月6日 22:02
To: DetNet WG <detnet@ietf.org>rg>; raw@ietf.org
Cc: Fabrice Theoleyre <theoleyre@unistra.fr>fr>; Black, David <David.Black@dell.com>om>; gregory.mirsky@ztetx.com; Balázs Varga A <balazs.a.varga@ericsson.com>om>; Janos Farkas <Janos.Farkas@ericsson.com>
Subject: [Detnet] OAM terms

Dear all

There’s a need in the DetNet OAM framework and in the RAW architecture/framework to agree on definitions that can be used on both sides to mean the same thing. At the DetNet OAM call today, we agreed to work on that issue before cut off and publish aligned documents.

As a starting point, please find below the current text in the RAW document, largely based on a mix of RFC 6291 ans Greg’s sentences in the previous thread on this subject; you’ll note the 2 original terms for reverse OAM and Limited OAM that need more refining.

Fire at will!

Pascal


   AOM:  OAM stands for Operations, Administration, and Maintenance, and
      covers the processes, activities, tools, and standards involved
      with operating, administering, managing and maintaining any
      system.  This document uses the terms Operations, Administration,
      and Maintenance, in conformance with the IETF 'Guidelines for the
      Use of the "OAM" Acronym in the IETF' [RFC6291] and the system
      observed by the RAW OAM is the Track.

   Active OAM:  Active OAM uses specially constructed test packets
      crafted to observe a particular Track, subTrack, or Segment of a
      Track.

   In-Band OAM:  An active OAM packet is considered in-band in the
      monitored Track when it traverses the same set of links and
      interfaces receiving the same QoS and PAREO treatment as the data
      flows that are injected in the Track.

   Out-of-Band OAM:  An active OAM packet is out-of-band if its datapath
      is topologically the same as of that of the Track, subTrack or
      Segment being observed, but the QoS or PAREO treatment is
      different (e.g., lower CoS).

[DJ] I am not sure what scenarios this technology will be used in? What role does it play?

   Limited OAM:  An active OAM packet is a Limited OAM packet when it is
      observes the RAW operation over a node, a segment, or a subTrack
      of the Track, though not from Ingress to Egress.  It is injected
      in the datapath and extracted from the datapath around the
      particular function or subnetwork (e.g., around a relay providing
      a service layer replication point) that is being tested.

   Reverse OAM:  A Reverse OAM packet is an Out-of-Band OAM packet that
      traverses the Track from West to East and North-South in one of
      either direction, to capture and report OAM measurements upstream.