[Dime] [Errata Rejected] RFC6733 (6833)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 02 October 2023 13:55 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA5CC15108F; Mon, 2 Oct 2023 06:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 wzVhBFAyeveQ; Mon, 2 Oct 2023 06:55:24 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 5298FC151075; Mon, 2 Oct 2023 06:55:24 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3002EE7292; Mon, 2 Oct 2023 06:55:24 -0700 (PDT)
To: Kshitij.dutt@mindtree.com, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231002135524.3002EE7292@rfcpa.amsl.com>
Date: Mon, 02 Oct 2023 06:55:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/FGAB_8Eu9IleHtZ7fGTXjNOUh7E>
Subject: [Dime] [Errata Rejected] RFC6733 (6833)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2023 13:55:28 -0000

The following errata report has been rejected for RFC6733,
"Diameter Base Protocol".

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

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Kshitij Dutt <Kshitij.dutt@mindtree.com>
Date Reported: 2022-02-03
Rejected by: Rob Wilton (IESG)

Section: 2.4

Original Text
-------------
The following Application Id values are defined:

         Diameter common message       0
         Diameter base accounting      3
         Relay                         0xffffffff

Corrected Text
--------------
The following Application Id values are defined:

         Diameter common message       0
         Diameter base accounting      3
         Relay                         0xffffff

Notes
-----
I presume relay application ID should be 0xffffff decimal equivalent of which is 16777215.
Instead 0xffffffff decimal translates to 4294967295.

This is assumption.
 --VERIFIER NOTES-- 
 The Application-ID field in the Diameter header is 32 bits long, hence the exist Application Id for "Relay" is correct.

--------------------------------------
RFC6733 (draft-ietf-dime-rfc3588bis-33)
--------------------------------------
Title               : Diameter Base Protocol
Publication Date    : October 2012
Author(s)           : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed.
Category            : PROPOSED STANDARD
Source              : Diameter Maintenance and Extensions
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG