[nfsv4] [Technical Errata Reported] RFC4506 (7101)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 21 August 2022 19:06 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17ED0C1522B6 for <nfsv4@ietfa.amsl.com>; Sun, 21 Aug 2022 12:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 6SUfac8iwmQR for <nfsv4@ietfa.amsl.com>; Sun, 21 Aug 2022 12:06:13 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49699C14F72C for <nfsv4@ietf.org>; Sun, 21 Aug 2022 12:06:13 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C364AAE9F; Sun, 21 Aug 2022 12:06:12 -0700 (PDT)
To: email2mre-rfc4506@yahoo.com, martin.h.duke@gmail.com, Zaheduzzaman.Sarker@ericsson.com, davenoveck@gmail.com, beepee@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dylan@allbee.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220821190612.C364AAE9F@rfcpa.amsl.com>
Date: Sun, 21 Aug 2022 12:06:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Hmv05h_s5RP1mmU0A1FP5welA_U>
Subject: [nfsv4] [Technical Errata Reported] RFC4506 (7101)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2022 19:06:17 -0000
The following errata report has been submitted for RFC4506, "XDR: External Data Representation Standard". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7101 -------------------------------------- Type: Technical Reported by: Dylan Allbee <dylan@allbee.org> Section: 4.3, Original Text ------------- Enumerations have the same representation as signed integers. Enumerations are handy for describing subsets of the integers. Enumerated data is declared as follows: enum { name-identifier = constant, ... } identifier; For example, the three colors red, yellow, and blue could be described by an enumerated type: enum { RED = 2, YELLOW = 3, BLUE = 5 } colors; Corrected Text -------------- ... enum identifier { name-identifier = constant, ... } ; ^^^^^^^^^^ ... enum colors { RED = 2, YELLOW = 3, BLUE = 5 } ; ^^^^^^ Notes ----- The grammar for this definition, as specified in 6.3, is: type-def: "typedef" declaration ";" | "enum" identifier enum-body ";" | "struct" identifier struct-body ";" | "union" identifier union-body ";" It is unclear whether the original intent was for identifies to precede or succeed the definition bodies. The example in section 7 shows: enum filekind { ... } And several RFCs which depend on 4506 have also followed that pattern, such as this example from RFC 5531, section 8.2: enum auth_flavor { ... } Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC4506 (draft-ietf-nfsv4-rfc1832bis-06) -------------------------------------- Title : XDR: External Data Representation Standard Publication Date : May 2006 Author(s) : M. Eisler, Ed. Category : INTERNET STANDARD Source : Network File System Version 4 Area : Transport Stream : IETF Verifying Party : IESG
- [nfsv4] [Technical Errata Reported] RFC4506 (7101) RFC Errata System