Re: [Detnet] AD Review of draft-ietf-detnet-ip-oam-09
Greg Mirsky <gregimirsky@gmail.com> Tue, 05 December 2023 00:36 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 EB6D6C14CF1F for <detnet@ietfa.amsl.com>; Mon, 4 Dec 2023 16:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQqKuWkZuup5 for <detnet@ietfa.amsl.com>; Mon, 4 Dec 2023 16:36:44 -0800 (PST)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21BEBC14F5F6 for <detnet@ietf.org>; Mon, 4 Dec 2023 16:36:44 -0800 (PST)
Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-db548cd1c45so3122495276.2 for <detnet@ietf.org>; Mon, 04 Dec 2023 16:36:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701736603; x=1702341403; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PGXI8nFqJNtsc5cw9QkPpJ08LB4wu+qCq2JBILyaMSk=; b=NJZuBWPHe8VYP2nmpHU15m2XeLJkR8YDttczwI0DIXc3mBx4T/kEKo//Om6/Grcn7o 023v0vuSJFzOGWsFNcluf/LXrxatFGvGHzvlRMh/0oUI1UbL6NH21n9EYpiB9J3liM40 pcF6vt1Ae+RnTPX7BHSnxNGK6VOV0B31UGWRVh04uD+8exaItgkJVBYu0nnghxE4u+27 9uEsIfRw8TQ4IawKzDD2CRfcIRjXVN3kG5mpqW1CZg/oatxrwpVGatlmVKZJBUgWxnI3 dTdoZOolaXRYpxdDkeozxL7UOSEJ3cfKEsAWKfgZCZaV+6h59MAmhyOiv4Uoh6pHj81S 22Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701736603; x=1702341403; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PGXI8nFqJNtsc5cw9QkPpJ08LB4wu+qCq2JBILyaMSk=; b=k/N1o2bnn9eZyZ1Kx4D4E4ZPKC9JKhS9vXGpAJDffkQ7d1W/YSxAQz1DiPR+qp5Vyi LWNvHyQD5A5CwsrgB90fgTYqZA2/e2RWl+K6SNTfmI70YVPZVIlKOlvwznlSOoZlDs9E u8MhoD8R51URXgVmTvNxjVmD4Pw+x2JGgPn2XdVELAi6Y4PiHtsS1IB085LKZTstcLgk nlkentXWqMOjMo7Vmh8EkOC/uRKuWPYS0nG5YHXTMlGTurr8DfGsSWkIEbgbH9pJLYDF 66OaIBiixUm7au/dG/KlCp3cNBTkUQskWpHZIgTzChyeV9s31qIztzRlEgsj6uJMvNFV XONQ==
X-Gm-Message-State: AOJu0YxHH5eD0Ofv/yQhPwNOWGxGW3W4LaxR6xFEKsHt7qZrM9oRXox5 Q8J/PriXmE+58C9OmUQyoksR4570kzvq+hWwOdnDKAGlrxWkAw==
X-Google-Smtp-Source: AGHT+IEnVMJ2hxVw4zoSHXJ6PtbVjQ6cuFAH7mL/netgHq9X+0QFZOCQzWJfw4pXo2ahtR7iOnp/S7KQ4Yhb5zdFjJE=
X-Received: by 2002:a25:9d88:0:b0:db5:447c:1a87 with SMTP id v8-20020a259d88000000b00db5447c1a87mr1423727ybp.62.1701736603022; Mon, 04 Dec 2023 16:36:43 -0800 (PST)
MIME-Version: 1.0
References: <BN2P110MB110719BF117AD8A21A0CFA6ADCA0A@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BN2P110MB110719BF117AD8A21A0CFA6ADCA0A@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 04 Dec 2023 16:36:32 -0800
Message-ID: <CA+RyBmW-CmfifUgp+n1L8pYhGwNhNhYBir-qijN=Kudc4Cjyyg@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: "detnet@ietf.org" <detnet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b97aa3060bb86d57"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/U62dMaQlzwueVDJjDJ4NrhvQ7Ss>
Subject: Re: [Detnet] AD Review of draft-ietf-detnet-ip-oam-09
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
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, 05 Dec 2023 00:36:48 -0000
Hi Roman, I've uploaded the new version with updates to address your comments and suggestions: URL: https://www.ietf.org/archive/id/draft-ietf-detnet-ip-oam-10.txt Status: https://datatracker.ietf.org/doc/draft-ietf-detnet-ip-oam/ HTML: https://www.ietf.org/archive/id/draft-ietf-detnet-ip-oam-10.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-detnet-ip-oam Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-detnet-ip-oam-10 Please let the authors know if you have any further questions or concerns. Regards, Greg On Tue, Oct 31, 2023 at 11:47 AM Roman Danyliw <rdd@cert.org> wrote: > Hi! > > I performed an AD Review of draft-ietf-detnet-ip-oam-09 and will be taking > over as the responsible AD on this document to help load-balance work in > RTG. Thanks for this document. My feedback is as follows. > > ** Section 3.1 > When the UDP destination port number used by the OAM > protocol is one of the assigned by IANA, then the UDP source port can > be used to achieve co-routedness of OAM, > > Typo? What is “co-routedness”? > > ** Section 3.1 > That correlation between the particular IP OAM > protocol session and the monitored IP DetNet flow can be achieved > using the DetNet YANG model [I-D.ietf-detnet-yang]. > > Is this correlation possible by processing the provisioning information > codified in the YANG? Is not such a correlation possible by processing > _any_ provisioning information regardless of the data representation? I’m > wondering if this isn’t as simple as “That correlation between the > particular IP OAM session and the monitored IP DetNet flow can be achieved > by using DetNet provisioning information (e.g., [I-D.ietf-detnet-yang]). > > ** Section 3.2. Typo. s/IP active OAM/active IP OAM/? > > ** Section 3.2. > The amount of operational work mapping IP > OAM protocols to the monitored DetNet flow can be reduced by using an > IP/UDP tunnel to carry IP test packets. Then, to ensure that OAM > packets traverse the same set of nodes and links, the IP/UDP tunnel > must be mapped to the monitored DetNet flow. > > -- Using “IP/UDP” tunnel is referenced without citation. > > -- Isn’t this suggesting the opposite of what is said in other places – > that the measurement and the DetNet packet need to get the same > treatment/path? > > ** Section 3.2 > [I-D.ietf-detnet-mpls-over-ip-preof] describes how DetNet with MPLS > over UDP/IP data plane [RFC9025] can be used to support Packet > Replication, Elimination, and Ordering Functions to potentially lower > packet loss, improve the probability of on-time packet delivery and > ensure in-order packet delivery in IP DetNet's service sub-layer. > > -- I don’t understand the link to this PREOF draft and OAM. What am I > missing? > > -- I didn’t see a formal treatment of these topics in > [I-D.ietf-detnet-mpls-over-ip-preof]. > > ** Section 6. > This document describes the applicability of the existing Fault > Management and Performance Monitoring IP OAM protocols, and does not > raise any security concerns or issues in addition to ones common to > networking or already documented for the referenced DetNet and OAM > protocols. > > Please provide references to these key DetNet and OAM-related document > covering the relevant security considerations. > > Thanks, > Roman > _______________________________________________ > detnet mailing list > detnet@ietf.org > https://www.ietf.org/mailman/listinfo/detnet >
- [Detnet] AD Review of draft-ietf-detnet-ip-oam-09 Roman Danyliw
- Re: [Detnet] AD Review of draft-ietf-detnet-ip-oa… Lou Berger
- Re: [Detnet] AD Review of draft-ietf-detnet-ip-oa… Greg Mirsky
- Re: [Detnet] AD Review of draft-ietf-detnet-ip-oa… Greg Mirsky
- Re: [Detnet] AD Review of draft-ietf-detnet-ip-oa… Greg Mirsky