Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang
Greg Mirsky <gregimirsky@gmail.com> Sat, 13 August 2022 20:22 UTC
Return-Path: <gregimirsky@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 D099DC157B34 for <ippm@ietfa.amsl.com>; Sat, 13 Aug 2022 13:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_BLOCKED=0.001, 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 9Tuv7ohmo3gW for <ippm@ietfa.amsl.com>; Sat, 13 Aug 2022 13:22:12 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 2E3D4C157902 for <ippm@ietf.org>; Sat, 13 Aug 2022 13:22:12 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id f20so5544356lfc.10 for <ippm@ietf.org>; Sat, 13 Aug 2022 13:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=Z2tfxb634P9j4A0rt/KqxEhTYJrg91VS9wHRRo9T83g=; b=Bbp3o7sWEmLzqQ/SHUUvYPgnHqPtOahCE8tcK+2nMmbyKCcqESIbr15onFwfEWj0CR onUXPQlSd/cOOYFaREb/mquMvl8TAK7mKHd/qZeimLNYa7fQ2ZdSNg8Qsh7ZvRwPYDZ7 WUi2TrAGlH4U96riTqC6k3bLp8kyv6DTjAiZiijkj/U+S8yX4J5KYjWPC1mOMm8B5ZH5 MIMXtum5ygib2Cuw2qRVCU9Qz5F5OELoRldYkHlAyks0cyxn2f3qipopxwtg2txDQt47 9nJjMx0qrgeobRg+3QNngGIdfV4newxRKL81NQRBoDuPeC/Le29ItoJ/RmhMNFOgGwbC AMoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=Z2tfxb634P9j4A0rt/KqxEhTYJrg91VS9wHRRo9T83g=; b=awy4yfuYoH+v+5D6FFmagiLkO4DE1mJ9wLaBTBXhfiTwMdJLAG4Bbl/XeFicbDtveI 3zkwfRn9hMR0iKZcDM6BcYj0GzD6yxgQFZ01jqRaG0YO1aDdRacDZlJ64kkQhA4jUd+R 5qYHPUVs0t7nQ0y5I9ThOGEKpmRFxYPVpxnWnwlJcUGYYOlmVX2wm9/o2WRh8OCH69qu 5MEfW5QBUHEU06WFdqZNUBN93s2sUFsTiIk9D9sDHFKYmeoD3dtdi0/CrBuEy5RBc1Mb 0KDh3chcQPCItdmsGoQ+THWFtX5yZEerKCsnuzIzAI8NvYqeVb1AsB1CUO9uVMMWSQMd iAjQ==
X-Gm-Message-State: ACgBeo1WxOg8ny043qJSjU458Hlc5H8f0JkqCNjZUpazuGZAk5DUxAYu 7SqjnGS8ONSKM85JXtXH9DX0pvo6Gn8temnzWiI=
X-Google-Smtp-Source: AA6agR6U4u+HH7MK9fKiw2ci5LMU5TKqxwG0jrCCIWoKC/JEG6WvDEoUXR+Wv96bMkVNhg+NwKvVKpvfApvt4yE60Ew=
X-Received: by 2002:a05:6512:228c:b0:48c:e97e:1036 with SMTP id f12-20020a056512228c00b0048ce97e1036mr3021583lfu.209.1660422129614; Sat, 13 Aug 2022 13:22:09 -0700 (PDT)
MIME-Version: 1.0
References: <AB392216-E345-4274-9236-B5BEC9DF2BAB@apple.com>
In-Reply-To: <AB392216-E345-4274-9236-B5BEC9DF2BAB@apple.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 13 Aug 2022 13:21:58 -0700
Message-ID: <CA+RyBmXyeXrQBLEQ7rFW1cxkZBYStkWw_Su2qVABgjLvuTFi8g@mail.gmail.com>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000036838105e6252796"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/yIV3Ddy9VtOCggN6V47DuHxJDKA>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang
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: Sat, 13 Aug 2022 20:22:12 -0000
Dear Authors, et al.,
please kindly consider my notes as the WG LC comments on the draft:
- I read the document and left with a general question about the
applicability of this YANG model. Is it to be applied at:
- ingress IOAM node
- ingress and egress IOAM nodes
- ingress, egress, and transit IOAM nodes
- Abstract and the first paragraph of the Introduction section
characterize IOAM as only collecting the operational data and telemetry
information in the data packet. That seems like a contradiction with the
list of IOAM options that include the IOAM Direct Export.
- The first paragraph of the Introduction is likely to benefit from
references to documents that define IOAM encapsulation in IPv6 and NSH.
- The Proof-of-Transit option is listed in the Introduction section. Can
you give an example or reference of an IETF document that describes the
applicability of this trace option?
- It seems like "end to end data" in Section 3.1 should be "edge-to-edge
data".
- Can you explain the behavior of a transit IOAM node that receives IOAM
with Loopback mode/flag? How "the source" is identified in a data packet,
for example, NSH?
- What is "active measurement"? Can you provide an example or reference
to an IETF document that describes active measurements using IOAM?
- I found only two data plane encapsulations - NSH and IPv6. Does that
mean that this model is not intended to support IOAM in an MPLS network?
- Can you point out a part of the YANG model that can be used to control
a transit IOAM node for the IOAM Direct Export trace option?
- Nits:
- s/Edge to Edge/Edge-to--Edge/ per RFC 9197
Regards,
Greg
On Tue, Aug 9, 2022 at 9:15 AM Tommy Pauly <tpauly=
40apple.com@dmarc.ietf.org> wrote:
> Hello IPPM,
>
> This email starts a Working Group Last Call for draft-ietf-ippm-ioam-yang.
>
> https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-yang/
> https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-yang-04.html
>
> Please review this document, and reply to this email to indicate your
> comments, and if you support publishing this document.
>
> The last call will go until *Wednesday, August 31*.
>
> Best,
> Tommy & Marcus
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>
- [ippm] WGLC for draft-ietf-ippm-ioam-yang Tommy Pauly
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang t petch
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang t petch
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang t petch
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- [ippm] FW: WGLC for draft-ietf-ippm-ioam-yang Vengada Prasad Govindan (venggovi)
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Greg Mirsky
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Greg Mirsky
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Greg Mirsky
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Greg Mirsky
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tianran Zhou
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Greg Mirsky
- Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang Tommy Pauly