[AAA-DOCTORS] Fwd: [Editorial Errata Reported] RFC6733 (4803)

Benoit Claise <bclaise@cisco.com> Mon, 19 December 2016 10:53 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 6C59D1296C3; Mon, 19 Dec 2016 02:53:16 -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 770myfYI6Ld0; Mon, 19 Dec 2016 02:53:13 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B931912988C; Mon, 19 Dec 2016 02:51:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8295; q=dns/txt; s=iport; t=1482144711; x=1483354311; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=D+b+g0e4OknYxz6MeWBnML+LFbGhXzHBAV9sOjkHo4w=; b=clTWJiF96iZztl8SgG757PxyRHKe5Ivy2eNM7zMz9IEmiPLawm0VeXaV d63XeCfbTtQYCZ2UAJ1W45yS2HJlgMjH+XNEriiaSlPPhFjyiV5TmUJ2G ySIUXaJ7k9D1NbkS3RVfZU4OoZwudBBDq/jTrZ+0jBN8Xej6RQ1V5y6tz c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D+AAARu1dY/xbLJq1DGhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM3AQEBAQF5gQaNT3OVZYd2h3OFJYIKKoV4AoJUFAECAQEBAQE?= =?us-ascii?q?BAWIohGgBAgQSdxwDAQIvISwCCAYBDAYCAQEeiC8DFw4unhgBkB4vhngNg1cBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAR6GNoF9CIFMgQiBPYELO4EEWYVBBYhiEYYOgUK?= =?us-ascii?q?JeDWNQoNygXSFA4Mnhi+HcIFyUoNlhA8fN4ECFQ4Wg3IND4FePTQBE4hIAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,373,1477958400"; d="scan'208,217";a="650842403"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2016 10:51:48 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id uBJApmTI007136; Mon, 19 Dec 2016 10:51:48 GMT
References: <20160913214213.4DBFAB80B89@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: <20160913214213.4DBFAB80B89@rfc-editor.org>
Message-ID: <372e075c-1564-b36a-1eb3-e62c8717535f@cisco.com>
Date: Mon, 19 Dec 2016 11:51:48 +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: <20160913214213.4DBFAB80B89@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------C2DEE3D569B809790FCB533C"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/u_rYl9i49BswVlXa2xxRktbyVW4>
Subject: [AAA-DOCTORS] Fwd: [Editorial Errata Reported] RFC6733 (4803)
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:53:16 -0000

Ditto ...

Regards, B.


-------- Forwarded Message --------
Subject: 	[Editorial Errata Reported] RFC6733 (4803)
Date: 	Tue, 13 Sep 2016 14:42:13 -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: 	holger+ietf@freyther.de, 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=4803

--------------------------------------
Type: Editorial
Reported by: Holger Freyther <holger+ietf@freyther.de>;

Section: 3.2

Original Text
-------------
    Example-Request ::= < Diameter Header: 9999999, REQ, PXY >
                        { User-Name }
                     1* { Origin-Host }
                      * [ AVP ]



Corrected Text
--------------
    <Example-Request> ::= < Diameter-Header: 9999999, REQ, PXY >
                        { User-Name }
                     1* { Origin-Host }
                      * [ AVP ]



Notes
-----
I converted the BNF into a PetitParser parser in Smalltalk/Pharo and noticed that example and grammar do not match. The first issue is with the example following the grammar but most definitions do not follow the BNF so maybe it is best to update the BNF.

   header           = "<Diameter-Header:" command-id
                          [r-bit] [p-bit] [e-bit] [application-id]">"

But "Diameter-Header:" is not used throughout the text so maybe it is better to update the grammar to "Diameter Header:".


  command-def      = "<" command-name ">" "::=" diameter-message

but the example is not using <> for the command-name ("Example-Request"). For the grouped-avp-def application is sometimes used with "<" name ">" and sometimes just name.

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

.