[Dime] [Errata Held for Document Update] RFC6733 (5084)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 17 September 2017 23:13 UTC

To: priyatos@cdot.in, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: bclaise@cisco.com, iesg@ietf.org, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170917231239.4CCD6B80CA7@rfc-editor.org>
Date: Sun, 17 Sep 2017 16:12:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/pBQ2uvwVFScmF8ewhCG_8e9c-Ww>
Subject: [Dime] [Errata Held for Document Update] RFC6733 (5084)
Precedence: list

The following errata report has been held for document update
for RFC6733, "Diameter Base Protocol".

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

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Priyatosh Mandal <priyatos@cdot.in>
Date Reported: 2017-08-11
Held by: Benoit Claise (IESG)

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.

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

[Dime] [Errata Held for Document Update] RFC6733 … RFC Errata System