Re: [Dime] [Technical Errata Reported] RFC6733 (5084)

Dave Dolson <ddolson@sandvine.com> Mon, 14 August 2017 10:51 UTC

Return-Path: <ddolson@sandvine.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 D6DA2132196 for <dime@ietfa.amsl.com>; Mon, 14 Aug 2017 03:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 B1fl0AsxNFf9 for <dime@ietfa.amsl.com>; Mon, 14 Aug 2017 03:51:29 -0700 (PDT)
Received: from mail1.sandvine.com (mail1.sandvine.com [64.7.137.165]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09CD7132192 for <dime@ietf.org>; Mon, 14 Aug 2017 03:51:29 -0700 (PDT)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by WTL-EXCHP-3.sandvine.com ([fe80::3c39:d305:d721:f00a%15]) with mapi id 14.03.0319.002; Mon, 14 Aug 2017 06:51:26 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: Priyatosh Mandal <priyatos@cdot.in>, RFC Errata System <rfc-editor@rfc-editor.org>, "vf0213@gmail.com" <vf0213@gmail.com>, "jari.arkko@ericsson.com" <jari.arkko@ericsson.com>, "john.loughney@nokia.com" <john.loughney@nokia.com>, "glenzorn@gmail.com" <glenzorn@gmail.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "warren@kumari.net" <warren@kumari.net>, "jouni.nospam@gmail.com" <jouni.nospam@gmail.com>, "lionel.morand@orange.com" <lionel.morand@orange.com>
CC: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] [Technical Errata Reported] RFC6733 (5084)
Thread-Index: AQHTE68YeM6TpIqW/EGeAHwz10SRjKKDg/CAgAArP98=
Date: Mon, 14 Aug 2017 10:51:25 +0000
Message-ID: <20170814105124.5115986.90299.28199@sandvine.com>
References: <20170811040456.E8570B81789@rfc-editor.org>, <20170814041602.M44812@cdot.in>
In-Reply-To: <20170814041602.M44812@cdot.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_2017081410512451159869029928199sandvinecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/9Er9qQRIUUFZQ3eEsDySy1iC1Gg>
X-Mailman-Approved-At: Mon, 14 Aug 2017 05:54:38 -0700
Subject: Re: [Dime] [Technical Errata Reported] RFC6733 (5084)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Aug 2017 10:51:32 -0000

In my opinion, the change should not be accepted.
In your roll-over special case, the device should skip over the value 0, using 1 or some other value instead of zero.


David Dolson
Sandvine
From: Priyatosh Mandal
Sent: Monday, August 14, 2017 12:57 AM
To: RFC Errata System; 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: dime@ietf.org
Subject: Re: [Dime] [Technical Errata Reported] RFC6733 (5084)


Dear All,
Kindly verify this.

Regards,
Priyatosh Mandal

On Thu, 10 Aug 2017 21:04:56 -0700 (PDT), RFC Errata System wrote
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


Priyatosh
Ext: 8517
Mob: 9810480266
--------------------------------------------------------------------------------
::Disclaimer::
--------------------------------------------------------------------------------
The contents of this email and any attachment(s) are confidential and intended
for the named recipient(s) only. It shall not attach any liability on C-DOT.
Any views or opinions presented in this email are solely those of the author
and  may  not  necessarily  reflect  the   opinions