Re: [ippm] Fwd: New Version Notification for draft-ietf-ippm-stamp-option-tlv-03.txt

Greg Mirsky <gregimirsky@gmail.com> Fri, 28 February 2020 04:13 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 516CB3A0EEC for <ippm@ietfa.amsl.com>; Thu, 27 Feb 2020 20:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IHCJ-Ox8-7kN for <ippm@ietfa.amsl.com>; Thu, 27 Feb 2020 20:13:44 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FF8F3A0EE9 for <ippm@ietf.org>; Thu, 27 Feb 2020 20:13:43 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id 83so1049299lfh.9 for <ippm@ietf.org>; Thu, 27 Feb 2020 20:13:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hPzXquklD5JZqdHd6+QSzgSkeKzcrwxWL3m9qofaF7U=; b=RXrr179KNknj/ukag6jJrgabiO8RK5g5gv/7npmDpk1aCj5+DIkfejRfLt9eSGU2vs qVovwDKzALjiQKzkGEjrtRrIL0s2pAeuEs+CFcSv19V0h1hqSTq0y6nFjUrKHyPTvV2g FKJq0xl3Jrr9Xy9tFTIoTu5X8fd6zk0UZF4q9y+VPgdiMfSQC0av5NV7kzymned2+/JP 6SZk5Y8R23sOeUKAgorPOEqDAYpdmzATCOcWyN5fJnP2KG0+NuOwuSlnykzJXJKs9IK+ BVxoomXHxwa1ywA67xQaouCUxgDztZ6noDKhzmdkm1SDfbr0b9exUZkmaIU7+PBrNcNU Pf0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hPzXquklD5JZqdHd6+QSzgSkeKzcrwxWL3m9qofaF7U=; b=IdLSLDAcKN4V6/X8xLke1ObDKSTRY+cJS2m7NxYwrqypIo3OEqyREajM/MMIQP62pM rJuAjS2KZrLU1BGB1qxvqkPvAybs2xwapd2ez6pN4j/1tf/ifIEc6BeZCxO9a3+IZ+6I mzxO317+NAQKPfa0EfDZV0tnzsVZcIsGVzrIjcnBJpNNUnjCq8qsMVCc6scPqlHcZ09c SENOo8MqUOHSQBcV+Bt3gS4Eu9IXL+hn02jKnbyYDSTDpGI26ZB68NmtVha1QCVdQoZB co3QkhCgOhbV/0Dx9Vps3p4aOb9IRpugFtdMhJaQdEeCSC3rR+ARxiBU4eQ0Edrbycev 3nag==
X-Gm-Message-State: ANhLgQ0HFmOwamKsQ8gL5dH5OOUP7OMXW9wpfeunL9eXwj4fJw9osDxp Dwsq7HNdaCHiO4VC4BS06Xg1TuV3KOVhX38HY9A=
X-Google-Smtp-Source: ADFU+vvysGRS9CIhiSyaAlsRgwkg7qx2zfg59zzTXosA5h0GsNsi4JKia1YAKM7m8oA8aWZaXn54mm1sMXa8b4M70yQ=
X-Received: by 2002:a05:6512:70:: with SMTP id i16mr1395913lfo.93.1582863221819; Thu, 27 Feb 2020 20:13:41 -0800 (PST)
MIME-Version: 1.0
References: <158230107443.29037.14133930624764653909.idtracker@ietfa.amsl.com> <CA+RyBmWChGcvBtjBf2J9788D6Jkjhvg2L3jK5DRNUg-ZLMin_g@mail.gmail.com> <4ABD2C49-D3AC-4E3E-8059-259371085D91@cisco.com>
In-Reply-To: <4ABD2C49-D3AC-4E3E-8059-259371085D91@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 27 Feb 2020 20:13:30 -0800
Message-ID: <CA+RyBmUTh6NL-h-d7BqJG-mL7=sBLw7zn45DRP8SrR4a8dT_PQ@mail.gmail.com>
To: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
Cc: IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000108d56059f9b103a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/EGubm5xvzlU35qi6KRn3O2t7FeM>
Subject: Re: [ippm] Fwd: New Version Notification for draft-ietf-ippm-stamp-option-tlv-03.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 28 Feb 2020 04:13:46 -0000

Hi Rakesh,
thank you for your interest in the update to STAMP extensions. Can you
elaborate on where you see the conflict between STAMP and your proposal? Is
the change you've proposed applicable to STAMP test packet? As far as I
understand, STAMP cannot support your proposal and interwork with a system
that is complaint with draft-gandhi-spring-twamp-srpm. As for STAP
interworking with TWAMP in Unauthenticated mode, SSID doesn't change
anything, as TWAMP Session-Sender will zero the field and Session-Reflector
will ignore it on receipt. So I don't see conflict here at all. I greatly
appreciate your clarification.

Regards,
Greg

On Thu, Feb 27, 2020 at 7:48 PM Rakesh Gandhi (rgandhi) <rgandhi@cisco.com>
wrote:

> Hi Greg,
>
> I noticed that this STAMP TLV draft update is proposing to modify the
> STAMP packet format to contain SSID.
>
>
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |         Error Estimate        |             SSID              |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
> The SRPM draft posted in December had already proposed to use the same
> field for control-code.
>
> https://tools.ietf.org/html/draft-gandhi-spring-twamp-srpm-05
>
>     .                                                               .
>
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>     |         Error Estimate        | Reserved      |  Control Code |
>
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>     .
>
>
>
> Looks like there is a conflict in packet format update proposed that need
> to sort out.
>
>
>
> Thanks,
>
> Rakesh
>
>
>
>
>
> *From: *ippm <ippm-bounces@ietf.org> on behalf of Greg Mirsky <
> gregimirsky@gmail.com>
> *Date: *Friday, February 21, 2020 at 11:07 AM
> *To: *IETF IPPM WG <ippm@ietf.org>
> *Subject: *[ippm] Fwd: New Version Notification for
> draft-ietf-ippm-stamp-option-tlv-03.txt
>
>
>
> Dear All,
>
> the new version includes updates to the Followup Telemetry TLV and
> introduces the new HMAC TLV.
>
> We always welcome and greatly appreciate your comments, questions, and
> suggestions.
>
>
>
> Regards,
>
> Greg
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Fri, Feb 21, 2020 at 8:04 AM
> Subject: New Version Notification for
> draft-ietf-ippm-stamp-option-tlv-03.txt
> To: Henrik Nydell <hnydell@accedian.com <hnydell@accedian..com>>, Min
> Xiao <xiao.min2@zte.com.cn>, Adi Masputra <adi@apple.com>, Ernesto
> Ruffini <eruffini@outsys.org>, Gregory Mirsky <gregimirsky@gmail.com>,
> Richard Foote <footer.foote@nokia.com>
>
>
>
>
> A new version of I-D, draft-ietf-ippm-stamp-option-tlv-03.txt
> has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> Name:           draft-ietf-ippm-stamp-option-tlv
> Revision:       03
> Title:          Simple Two-way Active Measurement Protocol Optional
> Extensions
> Document date:  2020-02-21
> Group:          ippm
> Pages:          25
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-ippm-stamp-option-tlv-03.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-ippm-stamp-option-tlv/
> Htmlized:
> https://tools.ietf.org/html/draft-ietf-ippm-stamp-option-tlv-03
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-ippm-stamp-option-tlv
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ippm-stamp-option-tlv-03
>
> Abstract:
>    This document describes optional extensions to Simple Two-way Active
>    Measurement Protocol (STAMP) which enable measurement performance
>    metrics in addition to ones supported by the STAMP base
>    specification.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>