Re: [core] [Gen-art] [Last-Call] Genart last call review of draft-ietf-core-new-block-10

Pete Resnick <resnick@episteme.net> Sat, 24 April 2021 23:34 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1568C3A2532; Sat, 24 Apr 2021 16:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 40YvlAj6DNmk; Sat, 24 Apr 2021 16:34:37 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1510A3A2530; Sat, 24 Apr 2021 16:34:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 8B74DE295DA1; Sat, 24 Apr 2021 18:34:35 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BqZb2x3STR2U; Sat, 24 Apr 2021 18:34:11 -0500 (CDT)
Received: from [172.16.1.27] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 72C30E295D63; Sat, 24 Apr 2021 18:34:05 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: John C Klensin <john-ietf@jck.com>
Cc: gen-art@ietf.org, last-call@ietf.org, draft-ietf-core-new-block.all@ietf.org, core@ietf.org
Date: Sat, 24 Apr 2021 18:33:35 -0500
X-Mailer: MailMate (1.14r5795)
Message-ID: <D9D030B7-3144-4A06-9533-8F504F8C25B7@episteme.net>
In-Reply-To: <3D267D4121127EA65D3C3A7D@PSB>
References: <161930002269.19583.4502578348808948027@ietfa.amsl.com> <3D267D4121127EA65D3C3A7D@PSB>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_01D1DCF0-A731-4C8F-8FA3-A208A71FB356_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/oDSUecsiDsJ1K4OEzG3lx9rspHA>
Subject: Re: [core] [Gen-art] [Last-Call] Genart last call review of draft-ietf-core-new-block-10
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Apr 2021 23:34:42 -0000

On 24 Apr 2021, at 17:38, John C Klensin wrote:

> --On Saturday, April 24, 2021 14:33 -0700 Pete Resnick via
> Datatracker <noreply@ietf.org> wrote:
>
>> Reviewer: Pete Resnick
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft. The General
>> Area Review Team (Gen-ART) reviews all IETF documents being
>> processed by the IESG for the IETF Chair.  Please treat these
>> comments just like any other last call comments.
>> ...
>
>> Nits/editorial comments:
>>
>> In section 4.3:
>>
>> In several response code definitions:
>>
>>    The token used MUST be any token that was received in a
>> request using    the same Request-Tag.
>>
>> That doesn't really parse well. I think you either mean "The
>> token used MUST be a token" or you mean "The token used can be
>> any token".
>
> If the first meaning is intended, isn't that tautologically
> true?  If the token used is not a token, what would it be?

You need to put it in the context of the example give. It could be:

     The token used MUST be a token that was received in a
     request using the same Request-Tag.

which means it can't be a token with a different Request-Tag, or it 
could be:

     The token used can be any token that was received in a
     request using the same Request-Tag.

which means that there might be different tokens that use the same 
Request-Tag, but you can use any of them.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best