[Dime] [Technical Errata Reported] RFC6733 (6833)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 03 February 2022 14:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 AC7933A1BD0 for <dime@ietfa.amsl.com>; Thu, 3 Feb 2022 06:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 zFp-rSpFgGKO for <dime@ietfa.amsl.com>; Thu, 3 Feb 2022 06:37:45 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 947503A1C24 for <dime@ietf.org>; Thu, 3 Feb 2022 06:37:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 81E6F13310F; Thu, 3 Feb 2022 06:37:38 -0800 (PST)
To: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com, warren@kumari.net, rwilton@cisco.com, jouni.nospam@gmail.com, lionel.morand@orange.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Kshitij.dutt@mindtree.com, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220203143738.81E6F13310F@rfc-editor.org>
Date: Thu, 03 Feb 2022 06:37:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/DdyQYOXGjqqPbtFOiNG6txSvoQQ>
X-Mailman-Approved-At: Thu, 03 Feb 2022 06:46:04 -0800
Subject: [Dime] [Technical Errata Reported] RFC6733 (6833)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Feb 2022 14:37:50 -0000

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

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

--------------------------------------
Type: Technical
Reported by: Kshitij Dutt <Kshitij.dutt@mindtree.com>

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.

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. 

--------------------------------------
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