Re: [Detnet] AD Review of draft-ietf-detnet-ip-oam-09

Greg Mirsky <gregimirsky@gmail.com> Mon, 06 November 2023 09:38 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 441ACC15C2A6 for <detnet@ietfa.amsl.com>; Mon, 6 Nov 2023 01:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_BLOCKED=0.001, 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 pnyfJq4YBQon for <detnet@ietfa.amsl.com>; Mon, 6 Nov 2023 01:38:00 -0800 (PST)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 A3A1DC1519B8 for <detnet@ietf.org>; Mon, 6 Nov 2023 01:36:49 -0800 (PST)
Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-d9c66e70ebdso4272113276.2 for <detnet@ietf.org>; Mon, 06 Nov 2023 01:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699263409; x=1699868209; 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=zDiTo1TIlxfIRKjBFrCHMV+Ub5l9Uq8PggkTq497sg0=; b=UtSvBUtLNfCNDZM2PycWrHpsmkd+RMGEX/4PnLCemSFamr/tjc10zYi0ZqIXzBNomt FivRSXjqiQVYno2LCwL0IeIqnphfMZ9RYL5mSChhFwa6msET9lQumG8Min6yuIOKWSFp UCHUNdxwDfcatv1HjuBk3ONEeu6o4vrpXfD5xGkJnPU2RE1Pb4R3WTkPl+aalOpCk7Ep KfwrJyuDwKjYIsatMTkVKUbg2pgTZze2OChPJGrhCdsYGtWMYbOCyFn+RR+zxqIxl/Sl 6sfrqkNsYjPaGM/BrlRys+jSMOAd9xBFZAKWOTGNcvnSmNK044i0xhQ/LMTdftc3xFW5 rlqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699263409; x=1699868209; 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=zDiTo1TIlxfIRKjBFrCHMV+Ub5l9Uq8PggkTq497sg0=; b=LqrWw7OkQfiSLofqJYfQdrbJjeh4B4+ADUl6w6gs54ekx4qYrAiBxulMyloR7j8iTT t/LG40WO1ZPfgSFqwsRo8z9Xs5NbAEIKU3jPYrwhtHApP2jLwwmEsh32bI67AqZ8Wlcl 2B9KsZjCwBI+yKZyZ8NtYxFly+r2vSFdDR4f9qOo78Yv+oYckcfzQ8T8t982vg7mzSAS WLLTk3izS+X+HtCGyUxXZVPOD1xb/9MkJhlFWrOmW1K8DFAl5qz1h2MkElE1OLxIK5gA phWbDBexY+SUIj/CtZsewIEl8yIpjKGNleG6P1tjtZch4mVbApeI9jdMytdVkdb+Fce3 aHxw==
X-Gm-Message-State: AOJu0YwPg+P2B0+gIA4pioiZgC4lZniw/gjiel/y/IfYi6Yf9tEnjdPR y+IMIzzVX6cfAiybxu2n2FirdoIhzKTVYU3atiIIu+zzIX7rzQ==
X-Google-Smtp-Source: AGHT+IFyzoKUMeezAqYjWMDqr3rvJPhtZ9ZkLL1hy3hSSjy21GVK/uTZkImCWGa8tb/4l2fN79vTvt4HHSgK16AuA9g=
X-Received: by 2002:a5b:d08:0:b0:d9a:c41c:133a with SMTP id y8-20020a5b0d08000000b00d9ac41c133amr25080092ybp.38.1699263408576; Mon, 06 Nov 2023 01:36:48 -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, 06 Nov 2023 10:36:37 +0100
Message-ID: <CA+RyBmUhU0=Z5Kf494Bc8DGE3wmQK4WvJfuivfyj_=UQ=kWp6w@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: "detnet@ietf.org" <detnet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d91ce2060978976a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/GvNOOWKdZRIXMXZnm1S_J_Q-CVE>
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: Mon, 06 Nov 2023 09:38:02 -0000

Hi Roman,
thank you for your thorough review and thoughtful comments. The authors
will work on addressing the comments and answering questions. Will bring
back the proposed updates for the discussion.

Regards,
Greg (on behalf of the authors)

On Tue, Oct 31, 2023 at 7:47 PM 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
>