[mpls] Re: WG last call: draft-ietf-mpls-rfc6374-sr

Rakesh Gandhi <rgandhi.ietf@gmail.com> Tue, 14 May 2024 22:07 UTC

Return-Path: <rgandhi.ietf@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73FA4C14CF18 for <mpls@ietfa.amsl.com>; Tue, 14 May 2024 15:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, 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 n8wmrzLnENX9 for <mpls@ietfa.amsl.com>; Tue, 14 May 2024 15:07:23 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 9713EC14F700 for <mpls@ietf.org>; Tue, 14 May 2024 15:07:23 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-6a05f376effso50086646d6.0 for <mpls@ietf.org>; Tue, 14 May 2024 15:07:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715724442; x=1716329242; 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=Y7oxeTwnAScCTFEtpzF/9wVFNV6XwttJI3pukhav8aI=; b=aRyuvUHsCDpyWu/CvE6ghjl8O2Mq8OpjHeNvnt9XKzTmDlc48BtsmQRpiPY2EIYlkX X4W12Nn6XM9ZKH1m9DPOX3yX/D6CQlmIzOWqeki5lpPEiWUZ00oj9F1dUu7oIqWak9rw 4unhukndRUXU+uCPU2Y3Ym9RAo3wnHGXZrPOfxp6K/qxnOXTgLgIU4IbCBrLrb4zFQDY +RF0+8XPpRepT7YIgwpCT4ZwHr5Jyii3dKU+PFt4kc0lll4/soE5/L7GJOad8Qx9cx6J FtP+DP3B3ruHLt1P5TICuwQp/dFn/oJGbWtoNZI7XKWUSCPZGrW8c+lRDQuxtQRmKCeC BAcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715724442; x=1716329242; 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=Y7oxeTwnAScCTFEtpzF/9wVFNV6XwttJI3pukhav8aI=; b=LE+pP4kj/FuUb42Dxkld5rjw3Myn+KWeL+D41iL5KGzZWs3qM5YK1T+k6LH1nVjrdC YKAk3EVwZNW+xAvKOrUa8qThCw6Nwi5r+3WNKGWT93GHsgKugod9YfISmx6YwPb7ukc4 ekBVhRSeRmf2HXmCYvzQ8jikJ6tid0k6e55oVGp1NtruIogaUbfyVaAzJ11AsGwWnrvv prxj2ZbOkVgnQI7ASXeD59iXfbNFaH4DkmhvEiA1sySRE4eTfnGnNNwkE1G4c0xEpK5/ TI7NJxoT21r5AJsrmS2fV3Hh4ONbF1jqqLGYDDfiVyt3T7C3Ua9k3WoXi6HPV3U/TqZV NpYQ==
X-Forwarded-Encrypted: i=1; AJvYcCU76pcGlNqhb8mMr2YjnvPoiJYNOFpjestUvPA4hKYaGcxVz1mpY6Icw0+2meBHQ0Lr3TpOjLIJ9oZcGdx4
X-Gm-Message-State: AOJu0YyXjSdeEDQntxtu6TwFAyzduVApX9gV991DG8j7IfEgT06uSGmc 8nia3SDeHlDpBMlLqpEBQDr3+tPwxXewuiyFicaSWNjQabmRLHg9A1DekzHHAhXR4h+w9yjB2G5 gPh9UCJGBcKvgAi6PJlSihDcWdw==
X-Google-Smtp-Source: AGHT+IFAw0qhTQIUZ8Z/jz5M14gXgNyzPV+Zn/o0D0iMo5GjBK6/QiaNmkmIWkZkx1Mn01tIy/HLWUzxgsgxuFDKp2I=
X-Received: by 2002:a05:6214:4487:b0:69b:5889:8eff with SMTP id 6a1803df08f44-6a168212cfemr164739046d6.43.1715724442241; Tue, 14 May 2024 15:07:22 -0700 (PDT)
MIME-Version: 1.0
References: <0B3D008A-6DCF-414A-9BD4-C6F1F192B171@tony.li> <20240507162307532l71Ge0kniVo4vAQ8VHhF7@zte.com.cn>
In-Reply-To: <20240507162307532l71Ge0kniVo4vAQ8VHhF7@zte.com.cn>
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Date: Tue, 14 May 2024 18:07:11 -0400
Message-ID: <CAMZsk6eQO47mgpscD_hHFW-6m0HAbrABV56CEKH8KTo1_ysnoQ@mail.gmail.com>
To: xiao.min2@zte.com.cn
Content-Type: multipart/alternative; boundary="000000000000e994270618713966"
Message-ID-Hash: GWFVMWONJLJY4X575E4VTPNURIQWYM6J
X-Message-ID-Hash: GWFVMWONJLJY4X575E4VTPNURIQWYM6J
X-MailFrom: rgandhi.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: WG last call: draft-ietf-mpls-rfc6374-sr
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/XliISMiZzMwIxKh8EoK-H_FlLa0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Hi Xiao Min,

Thank you for the review comments.

Please see replies inline with <RG>...

On Tue, May 7, 2024 at 4:24 AM <xiao.min2@zte.com.cn> wrote:

> Hi all,
>
>
> I've read the latest version of the draft, which introduces two new TLVs -
> Return Path TLV and Block Number TLV.
>
> With regard to the Return Path TLV, its usage is clear to me, RFC 9503
> defines a similar STAMP TLV extension.
>
> However, to the Block Number TLV, its usage is not clear to me. The first
> paragraph of section 7.2 seems to combine this TLV with Alternate-Marking
> Method defined in RFC 9341, though I can't figure out how they're combined.
>

<RG> RFC 9341, Section 3.1, first paragraph defines packet loss measurement
using block number (copied text below).

   "The basic idea is to virtually split traffic flows into consecutive
   blocks: each block represents a measurable entity unambiguously
   recognizable by all network devices along the path.  By counting the
   number of packets in each block and comparing the values measured by
   different network devices along the path, it is possible to measure
   if packet loss occurred in any single block between any two points."


<RG> This draft defines Block number TLV to carry the above block number
associated with the traffic counters.

   "The packet loss measurement using Alternate-Marking Method defined in
   [RFC9341] MAY use Block Number (BN) for data correlation for the data
   traffic flow under measurement.  To be able to correlate the transmit
   and receive traffic counters of the matching Block Number, the Block
   Number of the traffic counters is carried in the LM query and
   response messages."


*<RG> How about updating the text as follows?*



* "The packet loss measurement using Alternate-Marking Method defined in
   [RFC9341] is based on dividing the traffic flow into consecutive
blocks and   counting the number of packets in each block. A block
number is used to *


*   identify the transmit and receive counters in each block and
compare for measuring loss.*


*   The LM query and response messages carry the transmit and receive
counters along with the  *


*   block number when using the AMM defined in [RFC9341] for loss measurement."*

Thanks,

Rakesh



> Best Regards,
>
> Xiao Min
> Original
> *From: *TonyLi <tony.li@tony.li>
> *To: *mpls <mpls@ietf.org>;
> *Date: *2024年04月30日 23:52
> *Subject: **[mpls] WG last call: draft-ietf-mpls-rfc6374-sr*
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
> [WG chair hat: on]
>
> Hi all,
>
> This starts a 2 week working group last call on
> draft-ietf-mpls-rfc6374-sr.
>
> This last call ends at 12:01PM PDT, Tues. May 14th.
>
> Please send all comments to the mailing list.
>
> Thanks,
> Tony
>
>
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org
>