Re: [ippm] Barry Leiba's No Objection on draft-ietf-ippm-multipoint-alt-mark-07: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Tue, 10 March 2020 15:20 UTC

Return-Path: <barryleiba@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 320913A10E8; Tue, 10 Mar 2020 08:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.111
X-Spam-Level:
X-Spam-Status: No, score=-3.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.463, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 oQ7Dt6GZhWBe; Tue, 10 Mar 2020 08:20:10 -0700 (PDT)
Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (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 B0CA73A10DC; Tue, 10 Mar 2020 08:20:09 -0700 (PDT)
Received: by mail-io1-f49.google.com with SMTP id v3so7083754iom.13; Tue, 10 Mar 2020 08:20:09 -0700 (PDT)
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:content-transfer-encoding; bh=ndm5XFKE1WYIfLV63Mu8CGKx6aspYDztAIt5HNtRehs=; b=T5mOcbi5dSPg4O52h0G+zgPJX21mxSuT8lyPDV9bNGuni8sna0FrXneTm8+ntCBu0X 07uYWG/T7x8PG2ZooqT7kMm2O9X+qNIky8wfvBgDEgjakSXYYMyfn5+FlyQzRz4JH6eY 9DBcV6eQ+6++ZtU942ywCuUZZhJVLIjpN1LpDSKQ23QeooXYPqsvrFU4u65GtNIse4s6 lmjY7bmoX6I6dKDDQotPAA+0iU16XGnVkBhvieo48ldlT3Pex7LaSAj5jH3yJgIimbUB uQJF+SxlUXidRwEqHvzof7IZcB3LTPQblFTr0cABVFnvY3/+FSTTec8k06zDp3jr8Qa1 pRuw==
X-Gm-Message-State: ANhLgQ1seZuWbVaq9Fk+s9uGgcPqNZnxowpB4563FjSlMVqnsRGqPWsU Ywgkj+Uqe4R+26stO2viVIXBSDbhFOQVwcxygI0=
X-Google-Smtp-Source: ADFU+vsu3nrbrMa8eI+DVC/GYhg1RHAZamUxuHzVFLr3oKjYyYXiGZeLL4jjsEeCDt6F8MqM6tmqXo+8f4aJVTGxt90=
X-Received: by 2002:a5d:9dcb:: with SMTP id 11mr18317284ioo.177.1583853608745; Tue, 10 Mar 2020 08:20:08 -0700 (PDT)
MIME-Version: 1.0
References: <158381589470.5523.1164066942364578999@ietfa.amsl.com> <9d958bb879304d7399819c4c3d73d29e@huawei.com>
In-Reply-To: <9d958bb879304d7399819c4c3d73d29e@huawei.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 10 Mar 2020 11:19:57 -0400
Message-ID: <CALaySJ+42TNw1KgrKGXwU=phL1NH3n8pKOs1cneHmgJNY=DQww@mail.gmail.com>
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-ippm-multipoint-alt-mark@ietf.org" <draft-ietf-ippm-multipoint-alt-mark@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/rNsx8pM7nvVTI8W0mmoDFchjVTg>
Subject: Re: [ippm] Barry Leiba's No Objection on draft-ietf-ippm-multipoint-alt-mark-07: (with COMMENT)
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: Tue, 10 Mar 2020 15:20:14 -0000

Thanks for the quick replies, Giuseppe, and thanks for addressing my comments.

Barry

On Tue, Mar 10, 2020 at 10:16 AM Giuseppe Fioccola
<giuseppe.fioccola@huawei.com> wrote:
>
> Dear Barry,
> Thanks for your comment.
> I have included your suggested changes and capitalized “Alternate Marking” through the document.
>
> Regarding the first paragraph, I can change "explains" with "applies to". It should be better.
>
> Regarding the second paragraph, I can rephrase it as follows: " The Alternate Marking methodology described in RFC 8321 allows the synchronization of the measurements in different points by dividing the packet flow into batches. So it is possible to get coherent counters..."
>
> These changes are addressed in my local version.
>
> I will upload a new revision as soon as I get the additional ballot positions and comments.
>
> Regards,
>
> Giuseppe
>
>
> -----Original Message-----
> From: Barry Leiba via Datatracker [mailto:noreply@ietf.org]
> Sent: Tuesday, March 10, 2020 5:52 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-ippm-multipoint-alt-mark@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org; Tal Mizrahi <tal.mizrahi.phd@gmail.com>; tal.mizrahi.phd@gmail.com
> Subject: Barry Leiba's No Objection on draft-ietf-ippm-multipoint-alt-mark-07: (with COMMENT)
>
> Barry Leiba has entered the following ballot position for
> draft-ietf-ippm-multipoint-alt-mark-07: No Objection
>
> 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-multipoint-alt-mark/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I found this to be a somewhat difficult read, with some awkward wording.
> Because of time constraints I’ll mostly not comment specifically, but leave it to the RPC.  My comments below on Section 1 are examples.
>
> — Abstract —
>
>    This document aims to generalize and expand this
>    methodology
>
> “This document generalizes and expands this methodology”
>
> — Section 1 —
> The “; so” in the first sentence doesn’t follow from what comes before.  It seems that you’ve just glued together two unrelated sentences, and I would unglue them: “point-to-point path.  The extension proposed”
>
> How does the extension explain anything?  Isn’t it the document that does the explaining, but then the extension that does the enabling?
>
> I can’t parse the first sentence of the second paragraph, and I can’t figure out what you’re trying to say.  Can you try re-writing it?
>
> Please check to make sure you are consistent about capitalizing “Alternate Marking” and “Multipoint Alternate Marking” through the document.  It looks like you have it about half and half.
>
>
>