Re: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step

Martin Duke <martin.h.duke@gmail.com> Thu, 21 September 2023 20:45 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FDEC1519BD for <ippm@ietfa.amsl.com>; Thu, 21 Sep 2023 13:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, 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=unavailable 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 9xCwJZ7h9VSL for <ippm@ietfa.amsl.com>; Thu, 21 Sep 2023 13:45:26 -0700 (PDT)
Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (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 48373C1519BE for <ippm@ietf.org>; Thu, 21 Sep 2023 13:45:26 -0700 (PDT)
Received: by mail-ua1-x92b.google.com with SMTP id a1e0cc1a2514c-7a52a27fe03so633180241.0 for <ippm@ietf.org>; Thu, 21 Sep 2023 13:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695329125; x=1695933925; 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=C1LQPC/cNXJXzPHS7Zt4DvE09ml7iyX658GEWOi1w1o=; b=gr3AqjrEUayawgDFnBCXbGgxb6k9tH1BO05/PWzN2TwUQHyB/H43pHRwvSz8yh0j9y itOebkuIKE3Ivx/iT2ketogM1rJQkAIZLvnItyB5Cbg/h8KWLIJg3dZSBekGRMjdp1W9 02joDpi3+DJEJwbQpHXJb2EQzLH9jknf3ZUvMaAkF8T1ZC8ZDEU9J6bDPgrIQm8MQ865 VpXz2zLiwS5OkRJz4C86T3L0PXLLSHsBxbI0rE7K1PTBitDglVBMFgh4p0YGaAK/G6ms TAPScq9eHdLEUDmTILb7i7FZUY6vtGYEHQKcVMU9CyAs4klxuxIf5WS8RsN/2de6LfqH Cc7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695329125; x=1695933925; 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=C1LQPC/cNXJXzPHS7Zt4DvE09ml7iyX658GEWOi1w1o=; b=pTyxQgzWblrlTMbVrBdSSDMJegsRh3tsIJVObWpxTfsIsVKauTSkPGFAoYS7FY6nLL MnsAWE+ksMyVyBe4xXgBCYKMJb5Vaxp2fHDSWVYmo2wwQ35f55zPKT8BW/UWF8NqDCuY VgpgXtuKQ0o11nrmVCRABzGKckHrTIyJGZW8VaGWqbKE6bxGGCr3gCVVickXOmLGHdo3 jhAgRZLgUM3yvEkxNEFRLJcrLzMeHUWrvrgeNGpvSYUPGAhffQeQLGSCrgeQpAhlkKge nOM3IweZeCsagZu4KbmK/PztiXI4RwGZxAIMHa+SMl9b6bSlVmrug0ChW1GFOMnTHQNq n8wA==
X-Gm-Message-State: AOJu0YzAV+6P+okUZfnR2roWmMC1rPCujrMV+LrwuxzpO65zy74IvHuQ EvXrHT7K1Yz4aQJa4o71iH9euJO3ghlkg9njw7zeMjc4
X-Google-Smtp-Source: AGHT+IHN5sTHhmGIMF0TUm/A3wgLDkBIo9VN+f2wddJ8t5xqwaA4XyyfaYq7IDdh9vEOcSqpvvsf2MxZ6+v2zqtHYwY=
X-Received: by 2002:a67:e284:0:b0:452:88da:2e1f with SMTP id g4-20020a67e284000000b0045288da2e1fmr7572121vsf.21.1695329124970; Thu, 21 Sep 2023 13:45:24 -0700 (PDT)
MIME-Version: 1.0
References: <148C83FD-7102-405E-85AF-C29D0A265EB2@apple.com> <BY3PR13MB478715F8E6E77838AB513A0C9AFAA@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB478715F8E6E77838AB513A0C9AFAA@BY3PR13MB4787.namprd13.prod.outlook.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 21 Sep 2023 13:45:12 -0700
Message-ID: <CAM4esxR2qL5Eb1XMaOHzuU8Ro-KJfvrx2Dwy7pzMDyECSt_2Jw@mail.gmail.com>
To: Haoyu Song <haoyu.song@futurewei.com>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004575ad0605e4922b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Rc7yPpkjtbQD4WiLn9i5nCrxuP4>
Subject: Re: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2023 20:45:27 -0000

I agree that this type of work is in-charter.

I can't speak to whether this answers a big need or anyone would deploy it,
but I don't see a fundamental problem with adoption, assuming there are
satisfactory answers to the questions below.

I can see how something like this could go haywire, with followon packets
getting misrouted, reordered, or lost, and wonder if we have enough
experience with it to be a standard, or if we should instead aim for
experimental.

Some more minor comments:

I found the motivation in the introduction to be a bit hard to understand,
and the abstract could use a sentence or two explaining what this protocol
specifically does.

IIUC since the last major presentation @IETF 113, the model seems to have
evolved from each intermediate node generating its own followon packet,
instead the ingress node generates one and each intermediate node appends
to the followup. I hope that's right?

It's also disturbing to me that there doesn't seem to be strong wire-image
synchronization between the trigger packet and followon packet via a common
sequence number or something else. This could lead to confusion at the
egress.

What assurances are there that the followon packet followed the same path
from ingress to egress as the trigger packet? What are the consequences of
this not happening and remaining undetected?

This is not very important, but I find "hybrid two-step" to be a
nondescriptive name, and might prefer something like "IOAM Followon".

Martin


On Tue, Sep 19, 2023 at 11:28 AM Haoyu Song <haoyu.song@futurewei.com>
wrote:

> IPPM WG,
>
>
>
> As a coauthor, I support the adoption of the draft as the WG document. The
> hybrid approach complements with the other IOAM approaches well and has its
> own merits.  Thanks!
>
>
>
> Best,
>
> Haoyu
>
>
>
> *From:* ippm <ippm-bounces@ietf.org> *On Behalf Of * Tommy Pauly
> *Sent:* Wednesday, September 13, 2023 9:22 AM
> *To:* IETF IPPM WG <ippm@ietf.org>
> *Subject:* [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step
>
>
>
> Hello IPPM,
>
>
>
> This email starts a call for adoption for
> draft-mirsky-ippm-hybrid-two-step. This draft has been around for a while
> and discussed several times on list and in WG meetings.
>
>
>
> https://datatracker.ietf.org/doc/draft-mirsky-ippm-hybrid-two-step/
>
> https://www.ietf.org/archive/id/draft-mirsky-ippm-hybrid-two-step-15.html
>
>
>
> Please review the document and email the list with your comments, and if
> you think IPPM should adopt this work.
>
>
>
> This call for adoption will last three weeks and end on *October 4th*.
>
>
>
> Best,
>
> Tommy
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>