[Detnet] Moving forward on OAM in DetNet over IP network

Greg Mirsky <gregimirsky@gmail.com> Tue, 19 November 2019 03:52 UTC

Return-Path: <gregimirsky@gmail.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 4A706120048 for <detnet@ietfa.amsl.com>; Mon, 18 Nov 2019 19:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 yhsDJKfJLYCw for <detnet@ietfa.amsl.com>; Mon, 18 Nov 2019 19:52:35 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 799BC120044 for <detnet@ietf.org>; Mon, 18 Nov 2019 19:52:35 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id r7so21599383ljg.2 for <detnet@ietf.org>; Mon, 18 Nov 2019 19:52:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=mQaeXY7/EFbdLQ4bC3LkUqhQRWMvSGiTvf5jYX8ioTg=; b=f1qwvSga1Dvmj02RW6p2tcE5ckPS9xSh4UhWwBmfoMYi8RKHs0pFD9D3e4bTgashzB oAuPc6g0mR5PFSR27mK2/84iSDoJCOvP9mr1db/KFl3izXNI9mr3Tr3WqTXlRXBRldOm fmBnteHnfmI1If0BTirGJgzJk6qfUtufMggNO6zicr8whtdocM43aa2YNA4buS7CrIgn +vg6T4VUZ99QyTCgRydXmvoUh8eCWWMzu9rvdAjT3ab5TnQxyk6danqraQgO685KB2me m3qkU4hdd2p9KeatkHWZ5rwIBvfD6QxPerqSjwQw0d3NZl+Djx0uohmcq42S2Jc4g1+K OKHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=mQaeXY7/EFbdLQ4bC3LkUqhQRWMvSGiTvf5jYX8ioTg=; b=nc48/4r3QljoIrFdRSBlCiQ8P1P9G016Nr0Lf1dtNPp7s6sW4zhXdqduKEpVOTClyB whp1sk0xc/5ashqlpWr4gkL9mqF+oyg7dQSJGmKzMzvNlV348vWYXwvqb599I5gexGJr s/Iodbt/5CuSyyDhQtRfnffOMktx1WYqVK38yiaCyoYVjHJgu9bR6kJKqR8vLjpksLb5 ACfLM08s7D9Ki76R5TMa109SLwv7uWxFQdu0JB9eC1t4iY59A8lCp/MRIg912KTXPjNn 8x95P/TVru5nTLIQX+yoFXCbYryjZo0t0YVnCxdzp/Td15GyBCDCAnzozns971biEnTQ ewTw==
X-Gm-Message-State: APjAAAU+MfUua5SUzNPNy11B59riFdbHtz7ht4aqVnna257kTfnZTJp7 rNLGOVaVcnGWj0AeXhgNB7MVCmudYyXt6OBbGlZp6c+m7VQ=
X-Google-Smtp-Source: APXvYqzAgewyesJxpO70wVUMfd+5DGXAI6XUPEw0BE/czgyKsDzfqflD1SDW99u/EvxSP/m6vfteBMbNgYnosSKMA3o=
X-Received: by 2002:a2e:9097:: with SMTP id l23mr1932975ljg.103.1574135553375; Mon, 18 Nov 2019 19:52:33 -0800 (PST)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 19 Nov 2019 11:52:22 +0800
Message-ID: <CA+RyBmVzsZxymJ1xLqfqAKgzL3MyUrV0Xxt8AfzcEYX4FKKy-w@mail.gmail.com>
To: DetNet WG <detnet@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007cc0f70597aafe92"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/-jOvaLYFUSmY1G-IEGS1xWLWkoE>
Subject: [Detnet] Moving forward on OAM in DetNet over IP network
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: Tue, 19 Nov 2019 03:52:40 -0000

Dear All,
I've had discussions on how to ensure that a test session, monitoring for a
failure or measuring performance, shares the fate, i.e., traverses the same
path and receives the same QoS treatment, with the IP DetNet flow. One of
the options considered was using mapping the flows, likely by using ACLs.
That is possible but requires a lot of coordination with the management
plane.
A possible solution may be based on extending the definition of DetNet flow
ID in an IP network. Section 6 of draft-ietf-detnet-ip
<https://tools.ietf.org/html/draft-ietf-detnet-ip-03#section-6> defines the
set of information that identifies an individual or an aggregated DetNet
flor in the IP network. Because for the OAM flow some of the information
that is used to define the DetNet flow will be different, we propose to
allow that the DetNet flow may be identified by the value calculated using
the set of information identified in Section 6. Then the OAM flow can be
set in the way that the flow ID calculating function generates the same
identifier. (Using the same DetNet IP  Class of Service for OAM is
straightforward.)

I much appreciate your questions, comments, and suggestions.

Regards,
Greg