Re: [apps-discuss] [Editorial Errata Reported] RFC7601 (4671)

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 18 April 2016 17:47 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B0512D7A0 for <apps-discuss@ietfa.amsl.com>; Mon, 18 Apr 2016 10:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 DNmEY8IYDaJA for <apps-discuss@ietfa.amsl.com>; Mon, 18 Apr 2016 10:47:37 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 9A23412E13F for <apps-discuss@ietf.org>; Mon, 18 Apr 2016 10:47:37 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id c4so229336240vkb.3 for <apps-discuss@ietf.org>; Mon, 18 Apr 2016 10:47:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=0oiQgKH5zaIxPO8aeay5Q4XAMs3+sRe3jdlQOtSsTmw=; b=FlF+BySpDljM91gB1smt4DxKT2vDC68SshlHUoM8SEevHn/NkyUBzleYwma2va+V9P eeDTXBB20dWA4MlpY3PTrEcg3sAPEeEFIilISkkERY+MWuf8aZzcxToXnYvaSRBcIdzH izRI5vLldpCkJ9RMGA6l67EmOlpr5FUo5K0m3LFJ3RUW6JxY+5iZpQD8EosKKxoeMPtK ryIHp0xsxb56rvHdPSHLTx5wG6R3Y6IYBv/ZiE4GKucZzSNVIxPfcov0eL6jqzp0vcI1 67VRDBL+zLPYyuIHSbb/DCuoh2HCf7BVx7ha24pEAIPqNbLx8mGLc5joPg9YbTsObp0X S7Qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=0oiQgKH5zaIxPO8aeay5Q4XAMs3+sRe3jdlQOtSsTmw=; b=dhWEltN9mNh2OPYUCQxkmKDAB5pbnQJTFtpg8qs0VT6UxeDPiJWf5iOpN/jBD3tv9Z S3PpELqBw2OOGmqFJaSMXmux9s+AvRuEf7ulzX865nDzD0A91Vwl0rJ0qY0X68AQds8C mxYfnNyOLBsyOmKp2LEXEOJ5RrPysBX9e9kGUmA19btAowWNd+d1q4GZY6m5LIucPGa7 paYerBUtDUUJDZr2klqltxmds5rygkr53Nc4OQn7+JZck7scrhBPjXoB2bBsSOct6RHR ji58Poh5ALenKtvYcL40R79Z8ZmUNKtMjSZ5RRIJXLZWFRjH0DOTuy0eN1hoPcslJ9bU 8SVg==
X-Gm-Message-State: AOPr4FUYu44u1Y4NvzjHkHirK/hOzk8bdCym566kEsDvofHgt1Ju6y33lPjsTcg+fMhjmK/OKyzjCNhGPHo04w==
MIME-Version: 1.0
X-Received: by 10.176.0.106 with SMTP id 97mr2605014uai.113.1461001656695; Mon, 18 Apr 2016 10:47:36 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Mon, 18 Apr 2016 10:47:36 -0700 (PDT)
In-Reply-To: <20160418160554.AAE0318000F@rfc-editor.org>
References: <20160418160554.AAE0318000F@rfc-editor.org>
Date: Mon, 18 Apr 2016 10:47:36 -0700
Message-ID: <CAL0qLwbA6bxdYYL0kAeMVTP4uU9FaDe6JKSOOcc4meNxzaZWMA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary=001a113e4d9cc3803f0530c5f495
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/VrP8QCH8qN0K1ELsgFGMWS62kQs>
Cc: Ben Campbell <ben@nostrum.com>, Alessandro Vesely <vesely@tana.it>, IETF Apps Discuss <apps-discuss@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [apps-discuss] [Editorial Errata Reported] RFC7601 (4671)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 17:47:38 -0000

On Mon, Apr 18, 2016 at 9:05 AM, RFC Errata System <
rfc-editor@rfc-editor.org> wrote:

> Corrected Text
> --------------
>    The "ptype" in the ABNF above indicates the general type of property
>    being described by the value being reported, upon which the reported
>    result was based.  Coupled with the "property", which is more
>    specific, they indicate from which particular part of the message the
>    reported "pvalue"s were extracted.
>
>
>
> Notes
> -----
> The original text can be understood in multiple ways, depending on the
> meaning attributed to the term "result".  The corrected text I submit is
> one of the possible interpretations.  Note that if the first appearance of
> the term is assumed to be the ABNF "result", then ptype becomes an
> attribute of method, thereby setting a limit of one ptype per resinfo, as
> coincidentally it actually is.
>

Though it would be nice if there was some more obvious way to disambiguate
other than renaming the tokens into non-words, I note that the quoted
strings in both the original and corrected versions refer to ABNF tokens,
however "result" is not quoted, and doesn't refer to the ABNF.

As for the correction, to be more grammatically correct, I would use:

-- BEGIN --
The "ptype" in the ABNF above indicates the general type of property being
described by the value being reported, upon which the reported result was
based.  Coupled with the "property", which is more specific, it indicates
from which particular part of the message the "pvalue" was extracted.
-- END --

Otherwise, the suggestion seems fine to me, though I disagree with the
characterization that there's a limit of one ptype per resinfo.  There's
nothing precluding the existence of a method that bases its result on two
distinct ptype/properties, or chooses to report none, for example.

-MSK