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

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 16 January 2015 19:55 UTC

To: lionel.morand@orange.com, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150116195519.0DAA01832B6@rfc-editor.org>
Date: Fri, 16 Jan 2015 11:55:19 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/JF3YBvetQaMaRJ0FF6flEgkQaq4>
Cc: dime@ietf.org, Kathleen.Moriarty@emc.com, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Dime] [Errata Held for Document Update] RFC6733 (4234)
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_search.php?rfc=6733&eid=4234

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

Reported by: Lionel Morand <lionel.morand@orange.com>
Date Reported: 2015-01-16
Held by: Kathleen Moriarty (IESG)

Section: 5.4

Original Text
-------------
In the last sentence of first paragraph odf the section 5.4, it is said:

When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.

Corrected Text
--------------
the sentence should be:

When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnect-Cause AVP
contains the reason the Diameter node issued the Disconnect-Peer-
Request message.

Notes
-----
The correct name of the AVP is "Disconnect-Cause AVP" and not "Disconnection-Reason AVP" that does not exist.

--------------------------------------
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] [Editorial Errata Reported] RFC6733 (4234) RFC Errata System
[Dime] [Errata Held for Document Update] RFC6733 … RFC Errata System