IETF Logo Mail Archive

Re: [quicwg/base-drafts] Auth48: Capitalization and terminology consistency (Issue #4976)

Mike Bishop <notifications@github.com> Tue, 26 April 2022 18:47 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA04EC20D711 for <quic-issues@ietfa.amsl.com>; Tue, 26 Apr 2022 11:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level:
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMlONEBDUYYd for <quic-issues@ietfa.amsl.com>; Tue, 26 Apr 2022 11:47:17 -0700 (PDT)
Received: from smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A79C20D700 for <quic-issues@ietf.org>; Tue, 26 Apr 2022 11:47:17 -0700 (PDT)
Received: from github-lowworker-18092a0.ac4-iad.github.net (github-lowworker-18092a0.ac4-iad.github.net [10.52.123.83]) by smtp.github.com (Postfix) with ESMTP id B004D840F4B for <quic-issues@ietf.org>; Tue, 26 Apr 2022 11:47:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1650998836; bh=JqiexAGgaVVeurMmsl9zy8yS4LklWytiu4/NE0R4OsI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yJ6RPyxD7kqNpsbiTiMBZNAoLWeOVGUB01Zeq8b5VH1l0Wi/v2CnekDngbaAbYesC 6gQ2I1yya3Fn4G+rMuQlCqTUDN0KlM7+kmCjhz/2I2QDd3qWQzzj0NwnUkQqWqWVqC JiypED4W8cXThqWvjjG8kN8FK6uzcdj9bPwxU448=
Date: Tue, 26 Apr 2022 11:47:16 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5UDECYGB3KESKW7QOAOVYLJEVBNHHEMZM6NE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4976/1110134791@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4976@github.com>
References: <quicwg/base-drafts/issues/4976@github.com>
Subject: Re: [quicwg/base-drafts] Auth48: Capitalization and terminology consistency (Issue #4976)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_62683e34a2cb9_14e8d41c6492d0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/vDjoPC-0twSSDAei7BcB_Hx1Ftw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.34
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2022 18:47:19 -0000

"Length" is capitalized in several difference situations in the prose:
- In 4.1.2, defining string literals, "Length" is used interchangeably to refer to the length of the string and the field which contains that value.
- In field names ("Value Length", "Name Length") when representing the length-part of string literals
- In field diagrams, indicating the length of a field whose length was indicated by the previous field ("Length bytes")

It seems to me that the first should be fixed while the second is fine.  The third might benefit from a different means of indicating the size of the field, but it's not as obvious.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4976#issuecomment-1110134791
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4976/1110134791@github.com>

v2.23.0 | Report a Bug | By Email