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

Greg Mirsky <gregimirsky@gmail.com> Wed, 11 September 2019 00:34 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 37512120013; Tue, 10 Sep 2019 17:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 N_PKHPFTcKl2; Tue, 10 Sep 2019 17:34:51 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 3E72F12007A; Tue, 10 Sep 2019 17:34:51 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id y23so18221959lje.9; Tue, 10 Sep 2019 17:34:51 -0700 (PDT)
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=X5ZvAWiM86BHwK84UqWQjDGp/riCSFDJCeA9XUK0JJk=; b=YY7aQyQ2oL8TPkteTqcBKIvLgiEqqTxdescM/9MxtYa++l69T1pYwhdnpYdulkE45Q ZWf8dfcPbwz2oGXX9eVBnA5r/Z/zajnkcPMhxkFliYc8pF0GvGs1EKbUxW0muAfhPrd9 l+Zt79791NVZ5WA9YCwNJR1pL+PbUhlJIJGrEGCMh88fGnQkrezsQUVSd/Fr9mlbQpFv +Ghto9Bvp4eBZG6CM1dAOOL9oh9XkEGB68yVXDnzFNFuR9wXgSBH+xooekqkhu9gSb2P oUh64gUqolCd1xOdU2VGbfwN+YgKXJ4wAgVRUzDEY7UPpD4EbP/fe7TUvock5ia8AoC2 rsSw==
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=X5ZvAWiM86BHwK84UqWQjDGp/riCSFDJCeA9XUK0JJk=; b=GbgOY+j9nzbPP4SSlJesGx8zCiguWkUQoI14wA5taMpepSFz3HnlSbJo8c749Y6YTD oAyi97ikLeLXXGsa8y4EIyQO+Z1Cm9gtI/TDWm1rxci3SrpFkiI0i1qug8sb4EefPtLT ATsjf6ifcn3HK7/xm51rNfV8sZnRHAYnbCfxwZcKumsTL0siMujt23T4GgIPvFkpUECq ogAMGBdPni/8Wl4imTcrGG8y3QWWmZLVR8lJhPP+AugrzvlyOrg8mMz+aABNu4rqPr2t 87MreXrB6jCWIDiUaaSYzsdo+fK53MFH6aOkNtLPYAXcHXoz5iL6lf+sO2pJ8VcFcZSO frzw==
X-Gm-Message-State: APjAAAWX5G+hzaHKdeFltbllDZ2kLJt2JLM6g3lOkPTWpxOuCKwu01ix gdlndOVeNwUJbPiuvpOLP83oUG5+Y+9uQb81oWc=
X-Google-Smtp-Source: APXvYqxYu9mcx5nb8H7wTOPnbhzXOXC63yFb9+G81mQ0ayYY2yNhjiVZ6kJXz/t8GrWzkaLrPOhcag7Snwaic2e2nc4=
X-Received: by 2002:a2e:88d4:: with SMTP id a20mr21209370ljk.201.1568162089454; Tue, 10 Sep 2019 17:34:49 -0700 (PDT)
MIME-Version: 1.0
References: <156761599202.22808.13015902618373150935.idtracker@ietfa.amsl.com> <CA+RyBmV4_HaAC2=petia=SCh6wyAu+eRvbHtt5yKTioqn6jJNg@mail.gmail.com> <CALaySJLoUJX+4hA2inmGfG05Lf0kMv0QgsHTpS1_74+N0XzZvg@mail.gmail.com>
In-Reply-To: <CALaySJLoUJX+4hA2inmGfG05Lf0kMv0QgsHTpS1_74+N0XzZvg@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 10 Sep 2019 17:34:37 -0700
Message-ID: <CA+RyBmUsJ3qF8V1B7tFTVc8hd1GUyMFWMn5PXah60H9aYJoXWw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ippm-stamp@ietf.org, Tal Mizrahi <tal.mizrahi.phd@gmail.com>, IPPM Chairs <ippm-chairs@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004aea4405923c30d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/k930uDFpRGcRnM6H0BybFUJppfo>
Subject: Re: [ippm] Barry Leiba's Discuss on draft-ietf-ippm-stamp-07: (with DISCUSS)
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: Wed, 11 Sep 2019 00:34:54 -0000

Hi Barry,
thank you for the clarification. Yes, I agree that a new section can state
it more clearly and give sufficient examples, as you've suggested.
I'll work on it and will share when it is ready.

Regards,
Greg

On Tue, Sep 10, 2019 at 5:15 PM Barry Leiba <barryleiba@computer.org> 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 <gregimirsky@gmail.com> 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 <
> noreply@ietf.org> 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
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-ippm-stamp/
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> DISCUSS:
> >> ----------------------------------------------------------------------
> >>
> >> 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.
>