From nobody Thu Feb 3 06:46:06 2022 Return-Path: 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 68C513A1A7A for ; Thu, 3 Feb 2022 06:33:05 -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 tQEC0tP6J-Kf for ; Thu, 3 Feb 2022 06:33:01 -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 49B293A1A8A for ; Thu, 3 Feb 2022 06:32:59 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 499) id 1D5F4EB6C3; Thu, 3 Feb 2022 06:32:59 -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 Cc: Kshitij.dutt@mindtree.com, dime@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20220203143259.1D5F4EB6C3@rfc-editor.org> Date: Thu, 3 Feb 2022 06:32:59 -0800 (PST) Archived-At: X-Mailman-Approved-At: Thu, 03 Feb 2022 06:46:04 -0800 Subject: [Dime] [Technical Errata Reported] RFC6733 (6832) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 14:33:06 -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/eid6832 -------------------------------------- Type: Technical Reported by: Kshitij Dutt Section: 7.1.4 Original Text ------------- DIAMETER_OUT_OF_SPACE 4002 A Diameter node received the accounting request but was unable to commit it to stable storage due to a temporary lack of space. Corrected Text -------------- DIAMETER_OUT_OF_SPACE 4002 A Diameter node received the request but was unable to commit it to stable storage due to a temporary lack of space. Notes ----- Original text signifies accounting application explicitly. It can be any of Accounting or Authorization. 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 From nobody Thu Feb 3 06:46:11 2022 Return-Path: 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 ; 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 ; 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 ; 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 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, 3 Feb 2022 06:37:38 -0800 (PST) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 From nobody Fri Feb 4 02:42:21 2022 Return-Path: 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 6C2E03A0EDD for ; Thu, 3 Feb 2022 13:53:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 BWN6hsBnYkWU for ; Thu, 3 Feb 2022 13:53:09 -0800 (PST) Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A01E3A0E88 for ; Thu, 3 Feb 2022 13:53:08 -0800 (PST) Received: by mail-io1-xd34.google.com with SMTP id n17so5077856iod.4 for ; Thu, 03 Feb 2022 13:53:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UK63seBgklvFjmTSLfbAkElkBH/PV4IQu3SxnTnAZ0k=; b=L8fppkDluFcIog9AUKOky6+r9owORyoq0t9A8N1C4M00rHscuBC2gPF+fMVf3l4F3G aUpbMwHnZ3EM2RuMoO2DFiN9Ts5VhkEkMA5zErkPc+LDpPt4qcEC/+5p+HDpGHkeSVkd nQnLYCvF7/4ry6JYtwq0iJVI2Bjz4Vy5+Nac/vsIoApWBcSLmKE0KlYOM8/2BxBN2cuC KG6B6Zc5HLDx1z5/iIZaHkLbPyOOZAyspEV81j34MGfpSSe0SePvkRDBqjVVrmsWPlLD LEyT5RN84dX8HTTHvzx3eusS+YBau1G2gM1/Ob/FwHS5hEFl2bnbY41dINfhOUwPIoTq 9vMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UK63seBgklvFjmTSLfbAkElkBH/PV4IQu3SxnTnAZ0k=; b=OwJKTzLrZIlAhrN/kbqsvvD+V17MMB5q1gM+9+AGDfwUlpqND4OnpNrjoBIry63SME jIxm/eRhjF7Eo4DISUQpiUWjJqJB3hvep9CrJ1TOuJ4xEkJJjwzwPPVvRkpTSHbC0jOq 90X22uMMjMmi4gy1ugeYH+wSsSsbb6tv418iW5JymbeDs1mjDgevabbzYf90Sw0/pDxn Q98f0pC3CeJwsOOCWDGoQZ0SPq2InvRC70GxbsAMRT1i2nFUpT1RVtZzsBdb7bUoGy9/ /fSjtTNdCcMglwF3ZOb0wLo58fsLdKOxhGIkMwMkt/YAW66V1rs5VvLGvNAubZ/aEwk6 or1w== X-Gm-Message-State: AOAM5317GBS0z/Muga/OzOHjzhm540t6/sYhDJ/vewi8COeTGnRjGX2H xuejELNMikE+NlBVwGzJ5oiH4qihPbAfeTRaPEI= X-Google-Smtp-Source: ABdhPJwMkrlwxHYpsoIOkSePftM9fXKyjqZP9j2/ODMT8KqMah0M16i+HtfaYGc5CN+w7N43kTZ5ysOXPM/oTKoft7g= X-Received: by 2002:a05:6638:38a0:: with SMTP id b32mr9860jav.228.1643925187057; Thu, 03 Feb 2022 13:53:07 -0800 (PST) MIME-Version: 1.0 References: <20220203143259.1D5F4EB6C3@rfc-editor.org> In-Reply-To: <20220203143259.1D5F4EB6C3@rfc-editor.org> From: Glen Zorn Date: Thu, 3 Feb 2022 13:52:58 -0800 Message-ID: To: RFC Errata System Cc: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, Warren Kumari , rwilton@cisco.com, jouni.nospam@gmail.com, lionel.morand@orange.com, Kshitij.dutt@mindtree.com, dime@ietf.org Content-Type: multipart/alternative; boundary="000000000000cfdad105d7242803" Archived-At: X-Mailman-Approved-At: Fri, 04 Feb 2022 02:42:19 -0800 Subject: Re: [Dime] [Technical Errata Reported] RFC6733 (6832) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 21:53:17 -0000 --000000000000cfdad105d7242803 Content-Type: text/plain; charset="UTF-8" I think that this change needs a little more justification to be accepted. For example, under what circumstances would a Diameter auth server be writing to stable storage? IIRC, Diameter auth was designed to be stateless... On Thu, Feb 3, 2022, 06:32 RFC Errata System wrote: > 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/eid6832 > > -------------------------------------- > Type: Technical > Reported by: Kshitij Dutt > > Section: 7.1.4 > > Original Text > ------------- > DIAMETER_OUT_OF_SPACE 4002 > > A Diameter node received the accounting request but was unable to > commit it to stable storage due to a temporary lack of space. > > Corrected Text > -------------- > DIAMETER_OUT_OF_SPACE 4002 > > A Diameter node received the request but was unable to > commit it to stable storage due to a temporary lack of space. > > Notes > ----- > Original text signifies accounting application explicitly. It can be any > of Accounting or Authorization. > > 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 > --000000000000cfdad105d7242803 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think that this change needs a little more justificatio= n to be accepted. For example, under what circumstances would a Diameter au= th server be writing to stable storage? IIRC, Diameter auth was designed to= be stateless...

On Thu, Feb 3, 2022, 06:32 RFC Errata System <rfc-editor@rfc-editor.org> wrote:=
The following errata report has be= en submitted for RFC6733,
"Diameter Base Protocol".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6832
--------------------------------------
Type: Technical
Reported by: Kshitij Dutt <Kshitij.dutt@mindtree.com>

Section: 7.1.4

Original Text
-------------
DIAMETER_OUT_OF_SPACE 4002

=C2=A0 =C2=A0 =C2=A0 A Diameter node received the accounting request but wa= s unable to
=C2=A0 =C2=A0 =C2=A0 commit it to stable storage due to a temporary lack of= space.

Corrected Text
--------------
DIAMETER_OUT_OF_SPACE 4002

=C2=A0 =C2=A0 =C2=A0 A Diameter node received the request but was unable to=
=C2=A0 =C2=A0 =C2=A0 commit it to stable storage due to a temporary lack of= space.

Notes
-----
Original text signifies accounting application explicitly. It can be any of= Accounting or Authorization.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, ple= ase
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party=C2=A0
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC6733 (draft-ietf-dime-rfc3588bis-33)
--------------------------------------
Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Diameter Base= Protocol
Publication Date=C2=A0 =C2=A0 : October 2012
Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: V. Fajardo, Ed., J. Ark= ko, J. Loughney, G. Zorn, Ed.
Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD
Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Diameter Maintenan= ce and Extensions
Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Operations an= d Management
Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF
Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG
--000000000000cfdad105d7242803-- From nobody Fri Feb 4 02:42:31 2022 Return-Path: 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 43CEF3A0EBF for ; Thu, 3 Feb 2022 13:56:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 dNVPDjnj4jjE for ; Thu, 3 Feb 2022 13:56:22 -0800 (PST) Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73ABC3A0EBD for ; Thu, 3 Feb 2022 13:56:22 -0800 (PST) Received: by mail-io1-xd2a.google.com with SMTP id s18so5032548ioa.12 for ; Thu, 03 Feb 2022 13:56:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PdpxzbFTSOs0UH1R4sTsvsTtTS25uLPpf2PflsYC9HI=; b=MY8ruVkRz5uDqZoThC9xHUTOCqbn9fg2DbD02qNOjkALB7y3djwv7pg+/dRr1Cn1es wveDMMDF/g2BCIYaUJfOTrl1kl/axrnVtIIn5Ha+P4pLQHHlGJTIPMNz5oFERuLmlm/J +/+azrF5lcPOdnrnByOVJeLFdPDFGCk8bi3s6aWGe/w6pA6jmjWQrvnc9HHmFE8sqnd/ qEqsP1ML5gAGm7eVeMnceMUg45EhJ4N+ladeT2IeWjoELptFdyMWH6tg193HvkAvs4Q8 acuxxW7iRy7Xj3WinOjm/gjlMVi7Zwc+KicqGZdM7VzVeidNaL5zxWaJly8F0ku9fgLC 8Cnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PdpxzbFTSOs0UH1R4sTsvsTtTS25uLPpf2PflsYC9HI=; b=VAGQ6/0BStca8lWlQ++8+APtzSjORU2QnOw/mCCkHPmmF8bmCATGjKNFuZWUHBDZKN T1BV3n8HUcm6acZkEXCK7q57VBHoUP5YfQhK2fhnGmr3cyvMZkQ6rAX+1P4psDm5SEoW BwCOxFTxzTZVCw/CQrkVADY0rjxZr0bYO1PJcEXnbLRj4jQslmDjQ90GvYLG6awui17c ybQZENCM/ZfHRXw/KQ4dFBtuwBwkKdYd7v2CA5rBujeIqSX51nPOIjIFHTVdWrZpXfAg xpEf5pPufdi8smQ490LiNA4lNrrqw2Ro0ujr30GSZwLsXuVqAvEVevszPuGuRZ5/AsEI Pb4A== X-Gm-Message-State: AOAM531gHpR1m49uktGVoH6OWvhdufKwbnFw6HKmi2m6DaCqKPYC8SAA Ec+APy0H6m0qqvOSY/BL5UjSsTtkgVVkgix4Ckw= X-Google-Smtp-Source: ABdhPJyPYlKbEhrO1p1AViNHsdu7vrY/D5YASmSQZnNLBNIycvkcltq3S52lGfkFvpHD1URMB8xmD9zjQOAzR3AWyuQ= X-Received: by 2002:a02:cd0a:: with SMTP id g10mr1645jaq.223.1643925379728; Thu, 03 Feb 2022 13:56:19 -0800 (PST) MIME-Version: 1.0 References: <20220203143738.81E6F13310F@rfc-editor.org> In-Reply-To: <20220203143738.81E6F13310F@rfc-editor.org> From: Glen Zorn Date: Thu, 3 Feb 2022 13:56:10 -0800 Message-ID: To: RFC Errata System Cc: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, Warren Kumari , rwilton@cisco.com, jouni.nospam@gmail.com, lionel.morand@orange.com, Kshitij.dutt@mindtree.com, dime@ietf.org Content-Type: multipart/alternative; boundary="0000000000004bcaf505d724340b" Archived-At: X-Mailman-Approved-At: Fri, 04 Feb 2022 02:42:19 -0800 Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2022 21:56:27 -0000 --0000000000004bcaf505d724340b Content-Type: text/plain; charset="UTF-8" REJECT The Application-ID field in the Diameter header is 32 bits long. On Thu, Feb 3, 2022, 06:37 RFC Errata System wrote: > 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 > > 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 > --0000000000004bcaf505d724340b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
REJECT
The Application-ID field in the D= iameter header is 32 bits long.=C2=A0

On Thu, Feb 3, 2022, 06:37 RFC E= rrata System <rfc-editor@rf= c-editor.org> wrote:
The fol= lowing 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:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Diameter common message=C2=A0 =C2=A0 =C2= =A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Diameter base accounting=C2=A0 =C2=A0 =C2= =A0 3
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Relay=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00xffffffff

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

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Diameter common message=C2=A0 =C2=A0 =C2= =A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Diameter base accounting=C2=A0 =C2=A0 =C2= =A0 3
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Relay=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00xffffff

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

This is assumption.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, ple= ase
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party=C2=A0
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC6733 (draft-ietf-dime-rfc3588bis-33)
--------------------------------------
Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Diameter Base= Protocol
Publication Date=C2=A0 =C2=A0 : October 2012
Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: V. Fajardo, Ed., J. Ark= ko, J. Loughney, G. Zorn, Ed.
Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD
Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Diameter Maintenan= ce and Extensions
Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Operations an= d Management
Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF
Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG
--0000000000004bcaf505d724340b--