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

[Benoit Claise <[e-mail]>]

Ditto ...

Regards, B.


-------- Forwarded Message --------
Subject: 	[Editorial Errata Reported] RFC6733 (4803)
Date: 	Tue, 13 Sep 2016 14:42:13 -0700
From: 	RFC Errata System <[e-mail]>
To: 	[e-mail], [e-mail], [e-mail], 
[e-mail], [e-mail], [e-mail], 
[e-mail], [e-mail]
CC: 	[e-mail], [e-mail], [e-mail]



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 <[e-mail]>

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

.