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

<lionel.morand@orange.com> Tue, 03 January 2017 11:45 UTC

Return-Path: <lionel.morand@orange.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 D91B01294EB; Tue, 3 Jan 2017 03:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.018
X-Spam-Level:
X-Spam-Status: No, score=-5.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 Uyn_LudljQEN; Tue, 3 Jan 2017 03:45:36 -0800 (PST)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2BE8129435; Tue, 3 Jan 2017 03:45:35 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 5232EC0958; Tue, 3 Jan 2017 12:45:34 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 33016180062; Tue, 3 Jan 2017 12:45:34 +0100 (CET)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0319.002; Tue, 3 Jan 2017 12:45:33 +0100
From: <lionel.morand@orange.com>
To: Benoit Claise <bclaise@cisco.com>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "sec-ads@ietf.org" <sec-ads@ietf.org>
Thread-Topic: [AAA-DOCTORS] Fwd: [Editorial Errata Reported] RFC6733 (4803)
Thread-Index: AQHSWeYdhHq35r8PM0yaMog4/GN22aEmqGdwgAAQ10A=
Date: Tue, 3 Jan 2017 11:45:33 +0000
Message-ID: <17526_1483443934_586B8EDE_17526_11792_1_6B7134B31289DC4FAF731D844122B36E0BFC600A@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <20160913214213.4DBFAB80B89@rfc-editor.org> <372e075c-1564-b36a-1eb3-e62c8717535f@cisco.com> <2069_1483442208_586B8820_2069_7324_1_6B7134B31289DC4FAF731D844122B36E0BFC5E94@OPEXCLILM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <2069_1483442208_586B8820_2069_7324_1_6B7134B31289DC4FAF731D844122B36E0BFC5E94@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E0BFC600AOPEXCLILM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/lspOrdB39dV7avd9INDiUfkSvDc>
Cc: "dime@ietf.org" <dime@ietf.org>, "holger+ietf@freyther.de" <holger+ietf@freyther.de>
Subject: Re: [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: Tue, 03 Jan 2017 11:45:38 -0000

This errata report is correct on the inconsistency regarding the definition of the command header and AVP header and how they are used in the rest of the document in the ABNF description of commands and Grouped AVPs.

For commands, the header is defined as follow:

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

whereas "<Diameter Header:" is used when defining commands.

Same for Grouped AVP. It is defined as follow:

         header           = "<" "AVP-Header:" avpcode [vendor] ">"

whereas "<AVP Header:" is used when defining Grouped AVPs.

Considering that most (if not all) the ABNF descriptions have been copied from the commands and Grouped AVPs defined in the RFC3588 or RFC6733, I would be in favor to correct the specification by modifying the definition of the headers, i.e.

--> In section 3.2.  Command Code Format Specification

OLD:

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

NEW:

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


--> And in section 4.4

OLD:

         header           = "<" "AVP-Header:" avpcode [vendor] ">"

NEW:

         header           = "<" "AVP Header:" avpcode [vendor] ">"

*******************
There are other issues pointed out in this report.

For command-def  = "<" command-name ">" "::=" diameter-message, I would propose to simply correct the example as all the command definitions given in the document are following the command-def definition.
For the grouped-avp-def, I don't know what would be the best approach. We could follow the same approach and require the addition of "<>" but I don't know what would be the impacts on existing Grouped AVPs defined without.

Regards,

Lionel.


-------- 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><mailto:rfc-editor@rfc-editor.org>

To:

vf0213@gmail.com<mailto:vf0213@gmail.com>, jari.arkko@ericsson.com<mailto:jari.arkko@ericsson.com>, john.loughney@nokia.com<mailto:john.loughney@nokia.com>, glenzorn@gmail.com<mailto:glenzorn@gmail.com>, bclaise@cisco.com<mailto:bclaise@cisco.com>, joelja@bogus.com<mailto:joelja@bogus.com>, jouni.nospam@gmail.com<mailto:jouni.nospam@gmail.com>, lionel.morand@orange.com<mailto:lionel.morand@orange.com>

CC:

holger+ietf@freyther.de<mailto:holger+ietf@freyther.de>, dime@ietf.org<mailto:dime@ietf.org>, rfc-editor@rfc-editor.org<mailto: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><mailto: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



.



_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.