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

Benoit Claise <bclaise@cisco.com> Mon, 19 December 2016 10:51 UTC

References: <20160922090155.502D3B81064@rfc-editor.org>
To: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "sec-ads@ietf.org" <sec-ads@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <e46d0d2c-d38f-3986-ee54-6cd85cb3bc39@cisco.com>
Date: Mon, 19 Dec 2016 11:49:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <20160922090155.502D3B81064@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------37A999998908DDE5879A77DA"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/2UYIqeP-9x5QD9T8PuI4eij4wHI>
Subject: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC6733 (4808)
Precedence: list

And this one.

Regards, Benoit


-------- Forwarded Message --------
Subject: 	[Technical Errata Reported] RFC6733 (4808)
Date: 	Thu, 22 Sep 2016 02:01:55 -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, joelja@bogus.com, 
jouni.nospam@gmail.com, lionel.morand@orange.com
CC: 	zbigniew.rapnicki@computaris.com, 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_search.php?rfc=6733&eid=4808

--------------------------------------
Type: Technical
Reported by: Zbigniew Rapnicki <zbigniew.rapnicki@computaris.com>

Section: 1.1.3

Original Text
-------------
This document obsoletes RFC 3588 but is fully backward compatible
    with that document.

Corrected Text
--------------
This document obsoletes RFC 3588.

Notes
-----
When comparing the BNF for the answer messages CEA, DPA, DWA, RAA, STA and ASA it can be seen that FAILED-AVP avp is no longer marked with the * which means it can be present only once in the diameter message.
Previous specification (rfc3588) defines multiple FAILED-AVP avp usage in a single diameter message.
Similar case is for Vendor-Specific-Application-Id AVP definition.
Previous specification allows multiple usage of Vendor-Id avp in a single message while the new specification defines it as a single mandatory AVP:
rfc3588:
<Vendor-Specific-Application-Id> ::= < AVP Header: 260 >
                                      1* [ Vendor-Id ]
                                      0*1{ Auth-Application-Id }
                                      0*1{ Acct-Application-Id }

rfc6733:
<Vendor-Specific-Application-Id> ::= < AVP Header: 260 >
                                            { Vendor-Id }
                                            [ Auth-Application-Id ]
                                            [ Acct-Application-Id ]
										
How this facts applies to the sentence about fully backward compatibility in the section 1.1.3?

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 (IESG)
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

.

[AAA-DOCTORS] Fwd: [Technical Errata Reported] RF… Benoit Claise