Re: [ippm] Intdir telechat review of draft-ietf-ippm-stamp-srpm-18

Rakesh Gandhi <rgandhi.ietf@gmail.com> Sat, 07 October 2023 14:29 UTC

Return-Path: <rgandhi.ietf@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 A4536C151095; Sat, 7 Oct 2023 07:29:35 -0700 (PDT)
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_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 lBYL-5EKMWVX; Sat, 7 Oct 2023 07:29:31 -0700 (PDT)
Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (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 AECA1C14F738; Sat, 7 Oct 2023 07:29:26 -0700 (PDT)
Received: by mail-qv1-xf31.google.com with SMTP id 6a1803df08f44-65af7e20f39so18881336d6.2; Sat, 07 Oct 2023 07:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696688965; x=1697293765; 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=a+RPaoayOl/dqNOFu17nkbT1/B4AHCmF0SE0GqI/LSU=; b=hUG4HkTwXkTtKszb4Eheu9FhtMnzrtbi712zEM+Z5VL4+H+a5uocxt7q/kBe/SQaNG /jKU5m6uf/vc6Si2mWs30zQrzSsS1btfZQ4e9KxvcWQx40pDJIRMlYcddv/3RBC0Epym 4d56aDkminozpUfTtam2P9XOIZv0QB5OxD1jXwyyyehPXxH7hJ+aiuiUIESKIztgrNOt xVPk7JRdIy1ZS5g+MXmT0FZQEMxBo3HL1mX3aDyCUqLRuumIk1TwmlksOsEiSCTo5NEe T+q3l4wUZoANn/5+AsCIxm2nuXG/DwIm+FAwRshI2+6SA44M1G5JkQuCbs9YpaG5wnMS P29g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696688965; x=1697293765; 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=a+RPaoayOl/dqNOFu17nkbT1/B4AHCmF0SE0GqI/LSU=; b=NP4LbuKHDrjI1nap1kfXIu7m0fdUOb6Eh6gh1YTbPR5N+4JXOdA1wQzAAJ+8vKbdnh 9gUTYw1rci6FhZmjgv80M7R9pfcI9+KhT2xEnvRkh6IKmYYl2PYsZ/udHbApyDXc82SA SqpFr1BCQ6I3LYWu4pl049aYbfTDWfk95+JqBqkXA28ZMYLVc/MKr2F31CFcotmslF9A QDLyyKW8rdrVHtUIj+18P1dp0poIDqB3AiTDx4v0tJ7xWpnEKhDDiYWzG9q/fL9NJJiG gM5wd0cbcgyf+RJeYTTRT2g+omjhyX8TiNolAkA6BuBAxaJ7/LkppO42J19VwjEM+58M QoWQ==
X-Gm-Message-State: AOJu0YwH3TBdfrR4U8IzlcL7mCzHP5p03qlmiSXLVyDSa3YAcaVNveAs 9YXZxeROcyFCObRQfE8lGKUnKfr5fFT7uXDJaQ==
X-Google-Smtp-Source: AGHT+IGXcPbk5nOiVcsc7v7lhhiteoLmJ9AneNQqHZntshoAA1P0PVLOiG+oxmy09yIsYkrviBNPDcSaOHctQds+9Ec=
X-Received: by 2002:a05:6214:4685:b0:65b:86d:d05f with SMTP id or5-20020a056214468500b0065b086dd05fmr11371523qvb.48.1696688965360; Sat, 07 Oct 2023 07:29:25 -0700 (PDT)
MIME-Version: 1.0
References: <169625727072.58782.5427262828597841652@ietfa.amsl.com> <CA+RyBmU=7tqcdjUOefBf85kdVaucs+NJTm=n75QyxrjtGq0=KQ@mail.gmail.com>
In-Reply-To: <CA+RyBmU=7tqcdjUOefBf85kdVaucs+NJTm=n75QyxrjtGq0=KQ@mail.gmail.com>
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Date: Sat, 07 Oct 2023 10:29:14 -0400
Message-ID: <CAMZsk6em=bSDDwggP77FkJu8FPgAXNHdAFDXZswe2Efx1wN4=Q@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Tim Chown <tim.chown@jisc.ac.uk>, int-dir@ietf.org, draft-ietf-ippm-stamp-srpm.all@ietf.org, ippm@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary="000000000000131e580607212fb2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/cgM98CuJbOnBjjJB13jSG9DU_jc>
Subject: Re: [ippm] Intdir telechat review of draft-ietf-ippm-stamp-srpm-18
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, 07 Oct 2023 14:29:35 -0000

Hi Greg, Tim,

Thank you for your review comments.

Please see replies inline with <RG>...

On Thu, Oct 5, 2023 at 5:37 AM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi, Tim and the Authors,
> I fully agree with the conclusion of the review and have several notes
> that I hope are not too late to consider:
>
>    - It might be that referring to STAMP as Simple TWAMP could be
>    confusing and mistaken as an extension to the TWAMP Lite profile of RFC
>    5357. To avoid the possible confusion, I propose to change the title to
>    "Simple Two-Way Active Measurement Protocol Extensions for Segment Routing
>    Networks", which is consistent with naming other STAMP RFCs, RFC 8762
>    <https://datatracker.ietf.org/doc/rfc8762/> and RFC 8972
>    <https://datatracker.ietf.org/doc/rfc8972/>.
>
>
<RG> Acking.


>
>    - While I agree that enabling co-routing for the reflected STAMP test
>    packet is an important functionality defined in the document, it seems to
>    me that it is not the only one scenario where new STAMP extensions could be
>    used. I imagine that the Return Path TLV in combination with the Return
>    Address sub-TLV could be used to direct the reflected STAMP test packet to
>    an arbitrary host in the domain (or even anywhere in the network).
>
>
<RG> Yes.


>
>    - Furthermore, the ability to control the path of the reflected STAMP
>    test packet can be used beyond making it co-routed with the path of the
>    packet transmitted by the Session-Sender. I feel like the document already
>    identifies these use cases for the new TLVs, just wanted to note them.
>
> <RG> Yes.


> Again, apologies for my notes being so late.
>

Many thanks,
Rakesh




>
> Regards,
> Greg
>
>
> On Mon, Oct 2, 2023 at 4:35 PM Tim Chown via Datatracker <noreply@ietf.org>
> wrote:
>
>> Reviewer: Tim Chown
>> Review result: Ready
>>
>> Hi,
>>
>> I have reviewed this document as part of the Internet Area directorate's
>> ongoing effort to review all IETF documents being processed by the IESG.
>> These
>> comments were written with the intent of improving the operational
>> aspects of
>> the IETF drafts. Comments that are not addressed in last call may be
>> included
>> in AD reviews during the IESG review.  Document editors and WG chairs
>> should
>> treat these comments just like any other last call comments.
>>
>> This document describes an extension to the simple TWAMP protocol to
>> support
>> its use in both MPLS and IPv6 segment routing networks in cases where it
>> is
>> desired that the STAMP packets follow the same path from sender to
>> reflector
>> and back again.
>>
>> The document serves a useful purpose, is well-written, and Ready for
>> publication.
>>
>> Minor comment: the abstract could make it clear that the extension is to
>> enable
>> the same path to be taken out and back between sender and reflector.
>>
>> Tim
>>
>>
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ippm
>>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>