[AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC6733 (4808)
Benoit Claise <bclaise@cisco.com> Mon, 19 December 2016 10:51 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 3CC4F12999F; Mon, 19 Dec 2016 02:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.621
X-Spam-Level:
X-Spam-Status: No, score=-17.621 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 fvdztLxnOzsL; Mon, 19 Dec 2016 02:50:57 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92E9A129961; Mon, 19 Dec 2016 02:49:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8708; q=dns/txt; s=iport; t=1482144549; x=1483354149; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=AbT6XiElolgkSDR4sEs6yqh5rJjcUktxswwYXy2hfIc=; b=RdTEi+ocCl4YT0/Zw95ZCmnqEwebRXImWAgOdMPwCRjOR1qMQiPP26In WrgJmNFq9whvRM8gGy3NlGLZ+D79JdlDbvyRckbxY9Lbg8d0N1ub0mzWl Loh/j+vcAak+oIMaPUfhzck3ChFK5lSCPw/FjwxXep+rA6ccLIjQI1GkQ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AACguVdY/xbLJq1DGhkBAQEBAQEBAQEBAQcBAQEBAYM3AQEBAQF5gQaNT3OVZId2h3OFJYIKKoV4AoJUFAECAQEBAQEBAWIohGgBAgQSdxwDAQIvISwCCAYBDAYCAQEeiC8DFw4unhkBkB4vhngNg1cBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhjaBfQiCVIE9gQs7gQRZhUEFiFsHEYdQhECFODWNQoNygXSFA4Mnhi+JYlKDZYQPHzeBAhUOFoNyDQ+BXj00AROISAEBAQ
X-IronPort-AV: E=Sophos;i="5.33,373,1477958400"; d="scan'208,217";a="648001932"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2016 10:49:07 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id uBJAn7OX015989; Mon, 19 Dec 2016 10:49:07 GMT
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>
X-Forwarded-Message-Id: <20160922090155.502D3B81064@rfc-editor.org>
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)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 19 Dec 2016 10:51:07 -0000
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