[dhcwg] [Technical Errata Reported] RFC7839 (7016)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 07 July 2022 19:11 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4AFC14CF00 for <dhcwg@ietfa.amsl.com>; Thu, 7 Jul 2022 12:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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 FRu9cO5NQB5N for <dhcwg@ietfa.amsl.com>; Thu, 7 Jul 2022 12:11:15 -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 928DDC15790C for <dhcwg@ietf.org>; Thu, 7 Jul 2022 12:11:15 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 630A81D4E; Thu, 7 Jul 2022 12:11:15 -0700 (PDT)
To: shwethab@cisco.com, sgundave@cisco.com, mgrayson@cisco.com, volz@cisco.com, jouni.nospam@gmail.com, ek.ietf@gmail.com, evyncke@cisco.com, tim@qacafe.com, bevolz@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aland@deployingradius.com, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220707191115.630A81D4E@rfcpa.amsl.com>
Date: Thu, 07 Jul 2022 12:11:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Y4yaYwaqxS0B2nWw5f4xER2fSMk>
X-Mailman-Approved-At: Thu, 07 Jul 2022 14:39:27 -0700
Subject: [dhcwg] [Technical Errata Reported] RFC7839 (7016)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2022 19:11:19 -0000

The following errata report has been submitted for RFC7839,
"Access-Network-Identifier Option in DHCP".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7016

--------------------------------------
Type: Technical
Reported by: Alan DeKok <aland@deployingradius.com>

Section: 4.4.1

Original Text
-------------
   Length
      4

   Operator-Identifier
      The Operator-Identifier is a variable-length Private Enterprise
      Number (PEN) ...

Corrected Text
--------------
   Length
      4

   Operator-Identifier
      The Operator-Identifier is a 32-bit Private Enterprise
      Number (PEN) ...

Notes
-----
Either the length is 4, and the contents are 32-bits.  Or the length is >1, and the length is variable.

My guess is that the intention is to have a fixed length.  The variable-length encoding from RFC 6757 is likely not needed here.

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. 

--------------------------------------
RFC7839 (draft-ietf-dhc-access-network-identifier-13)
--------------------------------------
Title               : Access-Network-Identifier Option in DHCP
Publication Date    : June 2016
Author(s)           : S. Bhandari, S. Gundavelli, M. Grayson, B. Volz, J. Korhonen
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG