[AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC6733 (5084)

Benoit Claise <bclaise@cisco.com> Fri, 11 August 2017 09:05 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9043E13255C for <aaa-doctors@ietfa.amsl.com>; Fri, 11 Aug 2017 02:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 TFiEjIRKc5jF for <aaa-doctors@ietfa.amsl.com>; Fri, 11 Aug 2017 02:05:11 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999E4132526 for <aaa-doctors@ietf.org>; Fri, 11 Aug 2017 02:05:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9282; q=dns/txt; s=iport; t=1502442310; x=1503651910; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=IXmtQgtbWvykM+3tyifSwa+Erl5bk2vSJnGppIaOC1Y=; b=T73ZPlyE5BWAuTYTPBgCZB9zHpm+U4mp/9fUBEAgcB9AOLLSLrJFsZud vOh0/Ts4vpF8OFy9uEt/YzLptIPc4mDsn/dV6JNc7Y8QWyNZPFhysouag DBjNBaitGfevRBrw2x9uQa0gaaoiJGa7xJh6rREFTdUTOSaNGsyU2jPFF w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgB3co1Z/xbLJq1cHAEBBAEBCgEBh?= =?us-ascii?q?D6BFI4Qc5EGiDaILIUzghIshRsChTsYAQIBAQEBAQEBayiFGAEDAyNmHAMBAis?= =?us-ascii?q?CAiEsAggGAQwGAgEBihMDFRCrHYImJ4cMDYQhAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBHYMog06BYyuCfIE8gRuBV2WCc4JhBYl4E4hfjQA8j0aEdIIPhV2DV4cRjDF?= =?us-ascii?q?4iGofOIEKMiEIHBUfhU2BdgM+NoonAQEB?=
X-IronPort-AV: E=Sophos;i="5.41,356,1498521600"; d="scan'208,217";a="696431136"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Aug 2017 09:05:06 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v7B955rq019594; Fri, 11 Aug 2017 09:05:05 GMT
References: <20170811040456.E8570B81789@rfc-editor.org>
To: draft-ietf-dime-rfc3588bis@ietf.org, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <20170811040456.E8570B81789@rfc-editor.org>
Message-ID: <4498890f-b043-8dae-a68a-cdf2c3137b9f@cisco.com>
Date: Fri, 11 Aug 2017 11:05:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170811040456.E8570B81789@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------4BAB9D6BB44AD97900F0A21B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/xCfPpHOQ67JOMZJ64G9l3-X7FKE>
Subject: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC6733 (5084)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2017 09:05:13 -0000

What do you guys think of this errata?

Regards, Benoit


-------- Forwarded Message --------
Subject: 	[Technical Errata Reported] RFC6733 (5084)
Date: 	Thu, 10 Aug 2017 21:04:56 -0700
From: 	RFC Errata System <rfc-editor@rfc-editor.org>;
To: 	vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, 
glenzorn@gmail.com, bclaise@cisco.com, warren@kumari.net, 
jouni.nospam@gmail.com, lionel.morand@orange.com
CC: 	priyatos@cdot.in, dime@ietf.org, rfc-editor@rfc-editor.org



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

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

--------------------------------------
Type: Technical
Reported by: Priyatosh Mandal <priyatos@cdot.in>;

Section: 8.16

Original Text
-------------
By including Origin-State-Id in a message, it allows other Diameter
entities to infer that sessions associated with a lower Origin-State-Id
are no longer active.
If an access device does not intend for such inferences to be made, it
MUST either not include Origin-State-Id in any message or set its value
to 0.



Corrected Text
--------------
By including Origin-State-Id in a message, it allows other Diameter
entities to infer that sessions associated with a lower Origin-State-Id
are no longer active.
If an access device does not intend for such inferences to be made, it
MUST either not include Origin-State-Id in any message or set its value
to 0.
As a special case when the value of Origin-State-Id changes from
4294967295 to 0, then also the access device  clear all the sessions.

Notes
-----
Origin-State-Id is defined as Unsigned32 in RFC 6733, Section 8.16. So the maximum
value it can have is 4294967295. If the system restarts many times and the value of
Origin-State-Id reaches the value which is same as its maximum value 4294967295.
Then what will happen for the next restart. At the next restart the value of Origin-State-Id
will be 0 if we try to increase the value of Origin-State-Id.
It is not defined in the RFC 6733, that how the system should behave after 4294967295-th
restart with respect to Origin-State-Id.

Generally when the peer receives an increased value of Origin-State-Id, then it clear all sessions.
If the value of Origin-State-Id reaches its maximum i.e., 4294967295, then after another restart
its value will be 0. For a special case for transition of value of Origin-State-Id from
4294967295 to 0, the peer should clear its session.

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
.