Re: [ippm] Barry Leiba's Discuss on draft-ietf-ippm-stamp-07: (with DISCUSS)

Henrik Nydell <> Wed, 11 September 2019 08:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F1DB21200B2 for <>; Wed, 11 Sep 2019 01:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qSH5O06i0omu for <>; Wed, 11 Sep 2019 01:42:36 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::a35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 10198120833 for <>; Wed, 11 Sep 2019 01:42:36 -0700 (PDT)
Received: by with SMTP id d126so2086485vkb.1 for <>; Wed, 11 Sep 2019 01:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FXLlikzcOce6ISzttD0uKhkmWP4RPqldDJSRuSSS4Bc=; b=mL5ZZAok/Eru9Be4F/IDQ2Tbz5pJanY1uvpL0uTbl/dCvR7BPBM4QIhuurD76p9po4 UNgIxbbcQe36Z/7KC22Fz6r4J79i713qSz/m8lv4lDz0gqxkwLtQe7XkZjuM6zoS8mz1 lKw8Pxj+GK9ii0FdpXqKi02wvIqyzsaQKLG/4N0Ogb7owVmgZXH1ln54VCvNFc5GlPk1 u4o6FyIo+Fo1SMU7c1hs3csBRGILGMKWGS7+UmznUYwvPLLahYxYe4LFGuz49+lLfl5I LbqW/msLETCs3j1sTwwV2WO/Gk0bzv30h1VPAo/GDd4Dig1FM4Y8AUCLx4WoQGtAXqyN XNig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FXLlikzcOce6ISzttD0uKhkmWP4RPqldDJSRuSSS4Bc=; b=BlawYlMbXvBUmjecoi1i1jMlNUBYnO7l3YWJ+H6mozEdmqjk0kDgEvz6ECFnJ0Bz3z lviaP+H0LQ3qY/JTiJzuuEzqI1wGTiMeM9bod6y2DwZCaGRAe09YQeZ4rUE0zhRDdNl7 yaNOPIdHUuImIaFzoe3+R6983BcDzsBpNyxXl/p5oTVnJ/uVj/ysfAlxJoBRfiVeVTcT gWYSOTcglNfhfLyc9iMm90syXC+UYPdmEVJ0YcgbiDlE0osVsUaHAMBT8gIEC6MitfwU z9N5904pGAD1wA5+7NmBVuiT9tIGtL0k/Yr/fPMZfSoVxrHbyU+jxVG/BZWaJrjZNNT1 HqIw==
X-Gm-Message-State: APjAAAU3AbsHE3RjaAjbDt8QIknJQyX2I9T4sC2eoL9Qzi4+v7bT3Wyi g/YqtE7IQsjurjoaq9I/65OYZ3K/qkEY8HbeyIWys4x1J4Kewvtcs7lXwDVbcii34uceyPx5Rfe zKb6yMM2IQw==
X-Google-Smtp-Source: APXvYqwrcPXWi49U8ntB6Nivq+ukfFyeualVURmg6tsnisDslXkQUI4TzKjcuml2TPpS0EG+mWVriIM7OrIeIKFnRps=
X-Received: by 2002:a1f:2192:: with SMTP id h140mr5527422vkh.92.1568191354976; Wed, 11 Sep 2019 01:42:34 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Henrik Nydell <>
Date: Wed, 11 Sep 2019 10:42:23 +0200
Message-ID: <>
To: Barry Leiba <>
Cc: Greg Mirsky <>, The IESG <>,, Tal Mizrahi <>, IPPM Chairs <>, IETF IPPM WG <>
Content-Type: multipart/alternative; boundary="000000000000a752020592430004"
Archived-At: <>
Subject: Re: [ippm] Barry Leiba's Discuss on draft-ietf-ippm-stamp-07: (with DISCUSS)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Sep 2019 08:42:40 -0000

The STAMP test (As for RFC5357 TWAMP and for example Cisco IP-SLA , Huawei
U.2520, Juniper RPM and other in-line test functions) is indeed intended to
be used on production networks to enable the operator to assess service
level agreements based on delay, jitter and loss. So the rephrasing needs
to be done keeping that in mind, and I see no implications on using it over
the Internet either. The agreement on UDP ports to use needs to be done
between the session-sender and the session-reflector only. Intermediate
nodes or other users of the network need not be aware of the STAMP test or
the ports it uses. It is in fact desirable that the STAMP packets are not
distinguishable from other traffic on the network, but are treated just
like any user traffic in the class of service they are transmitted.


On Wed, Sep 11, 2019 at 2:15 AM Barry Leiba <> wrote:

> Hi, Greg, and thanks for the response.
> I think a minor rephrasing of the requirement isn't enough, really.
> As I understand it now, after other discussion, it's not that you need
> agreement from the users, but that you should put a paragraph (or
> maybe a separate section, to highlight the point) that says that this
> is not intended for use on the open Internet nor on production
> networks, and gives examples of what it *is* intended for... perhaps
> test networks, production networks during advertised maintenance
> windows, that sort of thing.  And then you don't need to say that the
> network's users need to agree, but simply that they need to be aware
> that performance testing will be happening during period X, and that
> disruptions to normal network operation are possible.  You'd need to
> come up with text that the working group agrees with, of course, but I
> think that if you do it will address my concern as well as some of the
> others that were raised.
> Does that make sense?
> Barry
> On Tue, Sep 10, 2019 at 5:01 PM Greg Mirsky <> wrote:
> >
> > Hi Barry,
> > thank you for your pointed question. Please find my explanation and the
> proposed updated below under the GIM>> tag.
> >
> > Regards,
> > Greg
> >
> > On Wed, Sep 4, 2019 at 9:53 AM Barry Leiba via Datatracker <
>> wrote:
> >>
> >> Barry Leiba has entered the following ballot position for
> >> draft-ietf-ippm-stamp-07: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut this
> >> introductory paragraph, however.)
> >>
> >>
> >> Please refer to
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >>
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> ----------------------------------------------------------------------
> >>
> >> I'm sure this will be easy to either explain to me or re-phrase:
> >>
> >> Sections 4 and 6 both say something like "MUST be agreed by all users
> of the
> >> network".  What does that really mean?  How is it remotely possible to
> get
> >> agreement from all users of your network?  How is it remotely possible
> that
> >> they could understand what you're asking them to agree to?
> >
> >
> > GIM>> Yes, looking at the bigger picture, at the Internet rather than
> only at the domain where the test will be performed makes such condition
> unattainable. Would s/network/network domain where the test is planned/  so
> that it reads as:
> >
> > ... MUST be agreed by all users on the network domain where the test is
> planned ...
> >
> > make it clearer and the number of parties involved reasonable, practical?
> > As for what the could be the question users will be asked, I think that
> it should verify whether the application that has the port number assigned
> is active as the same number will be used as the destination port number in
> the STAMP test.


*Henrik Nydell*
*Sr Product Manager*
<>  <>
* <>*


Avis de confidentialité

 informations contenues dans le présent 
message et dans toute pièce qui 
lui est jointe sont confidentielles et 
peuvent être protégées par le 
secret professionnel. Ces informations sont 
à l’usage exclusif de son ou
 de ses destinataires. Si vous recevez ce 
message par erreur, veuillez 
s’il vous plait communiquer immédiatement 
avec l’expéditeur et en 
détruire tout exemplaire. De plus, il vous est 
strictement interdit de 
le divulguer, de le distribuer ou de le reproduire 
sans l’autorisation 
de l’expéditeur. Merci.

Confidentiality notice


 e-mail message and any attachment hereto contain confidential 
which may be privileged and which is intended for the 
exclusive use of its 
addressee(s). If you receive this message in error,
 please inform sender 
immediately and destroy any copy thereof. 
Furthermore, any disclosure, 
distribution or copying of this message 
and/or any attachment hereto 
without the consent of the sender is 
strictly prohibited. Thank you.