[ippm] Question regarding draft-filsfils-spring-path-tracing

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Tue, 07 November 2023 13:13 UTC

Return-Path: <tal.mizrahi.phd@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 1F2BEC17C889; Tue, 7 Nov 2023 05:13:49 -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, 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 QPp--rqpOG4C; Tue, 7 Nov 2023 05:13:48 -0800 (PST)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 7DC49C17060A; Tue, 7 Nov 2023 05:13:45 -0800 (PST)
Received: by mail-il1-x131.google.com with SMTP id e9e14a558f8ab-35950819c97so3692055ab.0; Tue, 07 Nov 2023 05:13:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699362824; x=1699967624; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=C6UtMRwucc7yZprmNF2/e34FOWTp2NOZsF79V18YOEY=; b=CqUZt74MTVRVXFQ69sMI6ieRWwe3MP0RB5TwnSYNBtWTdA/6ktts36pDeexvAOrt6B JAfL8JwhQjsIspalIjrG7DWeth93YjWVDhGTRE5ygdmxE7+b4T9vGihszG/oZwPKL3ip bExoapq3eqMwE82NlaeRKDufJOT7mYcST/aZk4lIM6JRduAL/CqWpZsYKE+J5GFqcxeq 2bEYgzM1mJIm0dfzvg+fRb0a8VQ7Wt3CM4HOsFd1JjvLZcZ6JzGtBc07dRPi2JhxHdQA Ep4oLLr1AIw2jjeStUVkdwDCnciBJw7+dV6y29ig0BgMjg03UP7FHuULXc54TmV85gxN nZjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699362824; x=1699967624; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=C6UtMRwucc7yZprmNF2/e34FOWTp2NOZsF79V18YOEY=; b=kOhMh4x1OxO+XdPK0VDAxlFUF8S7vTs2UinUtYYuivhW3++RsWvaFlBMiA/qomnG8Z 15gAulL9PZIL/+4bEH1DS/5jOBD1JMM96khEpb9+ZzS7kv4L3FJVsiIfqE8hwzXcm5Xf 5ZYJBw0RsRti/zmvQMoL+xuRP3itRfzxygg3H4TRDrLEcNbsU5J6699yp/wrNH/Stn7U g1OSvKwKavQrodTKNETBlVAg0kHOIXI0Uskt6tU6+vsSw4HyXMlYxZT5/wmVsziAWodr 8RXbE7DrilEA2OM/ShBLsa5ymIL97lEl/8Zor0Z8cMSxIdddkOvLtWCAq6K13uBeyvNJ QjEA==
X-Gm-Message-State: AOJu0Yy07q0ezRie5amIBkXPa625ijwHv7BhgXgT1c5b8OJpdZy7k8fH TgcZ4kuHO/R//iVrmjdL24BVd3fL2ELUmsovz3FueGQB3ENIMQ==
X-Google-Smtp-Source: AGHT+IEUzfpVZn70U0seHs3nGfTERaPRjAmRJt+FZAbYbFpWrXgOc3/ZMuvU2v2Qp7BTXbQJcobtgwajGcXXmWfn13o=
X-Received: by 2002:a05:6e02:d4c:b0:359:3fd2:adcc with SMTP id h12-20020a056e020d4c00b003593fd2adccmr17739005ilj.3.1699362824139; Tue, 07 Nov 2023 05:13:44 -0800 (PST)
MIME-Version: 1.0
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Tue, 07 Nov 2023 15:13:32 +0200
Message-ID: <CABUE3XktA=gBt7L8Z7XpRkAv5o+xZrpA_aWfWM7R_bni6W8ZEw@mail.gmail.com>
To: draft-filsfils-spring-path-tracing@ietf.org, ahabdels@cisco.com, IETF IPPM WG <ippm@ietf.org>, SPRING WG List <spring@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/DKYpz4Jq1D3Cjvn-6uNFvaoM6tQ>
Subject: [ippm] Question regarding draft-filsfils-spring-path-tracing
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: Tue, 07 Nov 2023 13:13:49 -0000

Dear authors,

A couple of questions:
1. Why not decouple the IPv6 path tracing option from SRv6? It does
not seem to be strictly SRv6 related. You could potentially define the
relevant SRv6 endpoint behavior in a separate draft.
2. Would it be possible to use the ICMPv6 Loopback message with an SRH
and the path tracing option? That would mean that the ICMPv6 Loopback
reply includes the original SRH of the Loopback message, and also the
path tracing information of the original Loopback message.
In this context "ICMPv6 Loopback" is as defined in
https://datatracker.ietf.org/doc/draft-mcb-intarea-icmpv6-loopback/

Cheers,
Tal.