Re: [AAA-DOCTORS] [Technical Errata Reported] RFC7683 (5277)

<lionel.morand@orange.com> Mon, 19 March 2018 05:22 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 512D2124F57 for <aaa-doctors@ietfa.amsl.com>; Sun, 18 Mar 2018 22:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level:
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 yQqCR6ErV2wR for <aaa-doctors@ietfa.amsl.com>; Sun, 18 Mar 2018 22:22:25 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 510911201FA for <aaa-doctors@ietf.org>; Sun, 18 Mar 2018 22:22:25 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id A4F50C05E9; Mon, 19 Mar 2018 06:22:23 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.21]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 823F41A0057; Mon, 19 Mar 2018 06:22:23 +0100 (CET)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM6C.corporate.adroot.infra.ftgroup ([fe80::d9f5:9741:7525:a199%18]) with mapi id 14.03.0382.000; Mon, 19 Mar 2018 06:22:23 +0100
From: <lionel.morand@orange.com>
To: Jouni <jouni.nospam@gmail.com>, Benoit Claise <bclaise@cisco.com>
CC: john.zhao <yuankui.zhao@gmail.com>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Thread-Topic: [AAA-DOCTORS] [Technical Errata Reported] RFC7683 (5277)
Thread-Index: AQHTvt27lpKKh8t6EUOYa9Olrz6IBaPXApQw
Date: Mon, 19 Mar 2018 05:22:22 +0000
Message-ID: <26797_1521436943_5AAF490F_26797_483_1_6B7134B31289DC4FAF731D844122B36E2D3715C9@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <20180306104750.EF13EB80E97@rfc-editor.org> <68c132b6-52de-59d9-1d05-0bab97bb9212@cisco.com> <CADpucjW=fuxjMRS10Jt3A4No8Li0eVb5Q1S==Z9+yneCvQTFjA@mail.gmail.com> <e438abb8-66b0-b3da-4a1d-7b69f776c42e@cisco.com> <397_1521105881_5AAA3BD9_397_423_4_6B7134B31289DC4FAF731D844122B36E2D36D97E@OPEXCLILM43.corporate.adroot.infra.ftgroup> <6B3A4576-57D9-4DA4-B397-5EA220238680@gmail.com>
In-Reply-To: <6B3A4576-57D9-4DA4-B397-5EA220238680@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/l920Lz5_yYLbuMbRYX3AZmJXuxo>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC7683 (5277)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.22
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 Mar 2018 05:22:28 -0000

Hi Jouni,

Please see below.

> -----Message d'origine-----
> De : Jouni [mailto:jouni.nospam@gmail.com]
> Envoyé : dimanche 18 mars 2018 18:23
> À : MORAND Lionel IMT/OLN; Benoit Claise
> Cc : john.zhao; aaa-doctors@ietf.org
> Objet : Re: [AAA-DOCTORS] [Technical Errata Reported] RFC7683 (5277)
> 
> Sorry for being a late comer to his discussion. (I am also one of the authors
> but did not participate to the discussion of the errata earlier - shame on me).
> 
> First I do not think the added note in the proposed errata text adds any
> value. The reserved _value_ 0 is reserved. One cannot use/send such in OC-
> Feature-Vector AVP. Also the wording in the note is somewhat confusing
> "The value of zero (0) any DOIC node supports at least the Loss algorithm.”
> Something is missing from that sentence.
> 
[ML] The NOTE is there because the value (0) is not reserved for future use or anything else. This value cannot be sent at all and it is the clarification given in the NOTE (which is only for information).
And obviously, a word is missing in the NOTE. It should be:

       Note: The value of zero (0) BECAUSE any DOIC node supports at least the
                     Loss algorithm. Therefore, the OC-Feature-Vector AVP
                     cannot be sent with no bit set.


> The new added table is OK.. but not necessarily needed. What I think really
> would be useful is the change to Section 9.2. (new IANA registries) that was
> proposed during the initial discussion of the errata but not in the reported
> errata. That changed the “value” to “ assigned bit”, which in my opinion
> makes the use of the assignment very clear.

[ML] change to Section 9.2 is covered in errata report ID 5278, copied hereafter:

Section: 9.2

Original Text
-------------
9.2.  New Registries

   Two new registries have been created in the "AVP Specific Values"
   sub-registry under the "Authentication, Authorization, and Accounting
   (AAA) Parameters" registry.

   A new "OC-Feature-Vector AVP Values (code 622)" registry has been
   created.  This registry contains the following:

      Feature Vector Value Name

      Feature Vector Value

      Specification defining the new value

   See Section 7.2 for the initial Feature Vector Value in the registry.
   This specification defines the value.  New values can be added to the
   registry using the Specification Required policy [RFC5226].

   A new "OC-Report-Type AVP Values (code 626)" registry has been
   created.  This registry contains the following:

      Report Type Value Name

      Report Type Value

      Specification defining the new value

   See Section 7.6 for the initial assignment in the registry.  New
   types can be added using the Specification Required policy [RFC5226].

Corrected Text
--------------
9.2.  New Registries

   Two new registries have been created in the "AVP Specific Values"
   sub-registry under the "Authentication, Authorization, and Accounting
   (AAA) Parameters" registry.

   A new "OC-Feature-Vector AVP Values (code 622)" registry has been
   created.  This registry contains the following:

      Assigned Bit

      Feature Name

      Specification defining the new capability

   See Section 7.2 for the initial assigned bit in the registry.
   This specification defines the capbility announced by the setting of 
   this bit.  New values can be added to the registry using the 
   Specification Required policy [RFC5226].

   A new "OC-Report-Type AVP Values (code 626)" registry has been
   created.  This registry contains the following:

      Report Type Value Name

      Report Type Value

      Specification defining the new value

   See Section 7.6 for the initial assignment in the registry.  New
   types can be added using the Specification Required policy [RFC5226].

Notes
-----
This errata report is linked to the following errata report: Errata ID: 5277 The IANA registry created for the OC-Feature-Vector AVP Values (code 622) should only describe the use of the bit assigned to a given feature. There is no AVP value assigned to a given feature. The associated IANA registry should provide a table describing the setting of the bit assigned to a given feature/capability.


Regards,

Lionel
> 
> Regards,
> 	Jouni
> 
> 
> 
> > On 15 Mar 2018, at 11:24, lionel.morand@orange.com wrote:
> >
> > This errata report has been discussed with authors (including Ben
> Campbell) and is triggered after the review of another diameter draft that
> want to define a new feature.
> > The conclusion was that the clarification was needed. The only issue was
> about IANA impacts and if the proposed erratum was enough to trigger an
> update of the IANA registry.
> >
> > Regards,
> >
> > Lionel
> >
> > De : AAA-DOCTORS [mailto:aaa-doctors-bounces@ietf.org] De la part de
> > Benoit Claise Envoyé : mercredi 14 mars 2018 21:45 À : john.zhao Cc :
> > aaa-doctors@ietf.org Objet : Re: [AAA-DOCTORS] Fwd: [Technical Errata
> > Reported] RFC7683 (5277)
> >
> > Dear all,
> >
> > Any other views on the last two errata?
> >
> > Regards, B.
> > Hi Benoit,
> >
> >         The last word of "abatment" should be "abatement". In side of the
> 'description' column, the "OLR_DEFAULT_ALGO"could be set but as 1 always
> should be stated. As any other features could be set but 0 or 1 in the future.
> >
> >         Just FYI.
> >
> >         Thanks,
> > BR//John Zhao
> >
> > 2018-03-06 19:21 GMT+08:00 Benoit Claise <bclaise@cisco.com>;:
> > Feedback on this one?
> >
> > Regards, B.
> >
> >
> > -------- Forwarded Message --------
> > Subject:
> > [Technical Errata Reported] RFC7683 (5277)
> > Date:
> > Tue, 6 Mar 2018 02:47:50 -0800
> > From:
> > RFC Errata System <rfc-editor@rfc-editor.org>;
> > To:
> > jouni.nospam@gmail.com, srdonovan@usdonovans.com,
> ben@nostrum.com,
> > lionel.morand@orange.com, bclaise@cisco.com, warren@kumari.net,
> > jouni.nospam@gmail.com, lionel.morand@orange.com
> > CC:
> > lionel.morand@orange.com, dime@ietf.org, rfc-editor@rfc-editor.org
> >
> >
> > The following errata report has been submitted for RFC7683, "Diameter
> > Overload Indication Conveyance".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata/eid5277
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Lionel Morand <lionel.morand@orange.com>;
> >
> > Section: 7.2
> >
> > Original Text
> > -------------
> > 7.2.  OC-Feature-Vector AVP
> >
> >    The OC-Feature-Vector AVP (AVP Code 622) is of type Unsigned64 and
> >    contains a 64-bit flags field of announced capabilities of a DOIC
> >    node.  The value of zero (0) is reserved.
> >
> >    The OC-Feature-Vector sub-AVP is used to announce the DOIC features
> >    supported by the DOIC node, in the form of a flag-bits field in which
> >    each bit announces one feature or capability supported by the node.
> >    The absence of the OC-Feature-Vector AVP in request messages
> >    indicates that only the default traffic abatement algorithm described
> >    in this specification is supported.  The absence of the OC-Feature-
> >    Vector AVP in answer messages indicates that the default traffic
> >    abatement algorithm described in this specification is selected
> >    (while other traffic abatement algorithms may be supported), and no
> >    features other than abatement algorithms are supported.
> >
> >
> >    The following capability is defined in this document:
> >
> >    OLR_DEFAULT_ALGO (0x0000000000000001)
> >
> >       When this flag is set by the a DOIC reacting node, it means that
> >       the default traffic abatement (loss) algorithm is supported.  When
> >       this flag is set by a DOIC reporting node, it means that the loss
> >       algorithm will be used for requested overload abatement.
> >
> > Corrected Text
> > --------------
> > 7.2.  OC-Feature-Vector AVP
> >
> >    The OC-Feature-Vector AVP (AVP Code 622) is of type Unsigned64 and
> >    contains a 64-bit flags field of announced capabilities of a DOIC
> >    node.  The value of zero (0) is reserved.
> >
> >       Note: The value of zero (0) any DOIC node supports at least the
> >             Loss algorithm. Therefore, the OC-Feature-Vector AVP
> >             cannot be sent with no bit set.
> >
> >    The OC-Feature-Vector sub-AVP is used to announce the DOIC features
> >    supported by the DOIC node, in the form of a flag-bits field in which
> >    each bit announces one feature or capability supported by the node.
> >    The absence of the OC-Feature-Vector AVP in request messages
> >    indicates that only the default traffic abatement algorithm described
> >    in this specification is supported.  The absence of the OC-Feature-
> >    Vector AVP in answer messages indicates that the default traffic
> >    abatement algorithm described in this specification is selected
> >    (while other traffic abatement algorithms may be supported), and no
> >    features other than abatement algorithms are supported.
> >
> >    The following capability is defined in this document:
> >
> > +---+------------------+----------------------------------------------+
> > |bit|  Feature Name    |  Description                                 |
> > +---+------------------+----------------------------------------------+
> > | 0 | OLR_DEFAULT_ALGO |When set by a DOIC reacting node, it means    |
> > |   |                  |that the default traffic abatement (loss)     |
> > |   |                  |algorithm is supported. When set by a DOIC    |
> > |   |                  |reporting node, it means that the loss        |
> > |   |                  |algorithm will be used for requested overload |
> > |   |                  |abatment.                                     |
> > +---+------------------+----------------------------------------------+
> >
> >
> > Notes
> > -----
> > The OC-Feature-Vector AVP is a 64-bit flag field and not a set of values (one
> per feature). Using the hexadecimal notation, it gives the feeling that there is
> a unique value for the OC-Feature-Vector AVP per supported capability, hich
> is incorrect. It is only required to define the use of each bit. This errata report
> has an impact on the associated IANA regisrty.
> >
> > 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 can log in to change
> > the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC7683 (draft-ietf-dime-ovli-10)
> > --------------------------------------
> > Title               : Diameter Overload Indication Conveyance
> > Publication Date    : October 2015
> > Author(s)           : J. Korhonen, Ed., S. Donovan, Ed., B. Campbell, L. Morand
> > Category            : PROPOSED STANDARD
> > Source              : Diameter Maintenance and Extensions
> > Area                : Operations and Management
> > Stream              : IETF
> > Verifying Party     : IESG
> > .
> >
> >
> > _______________________________________________
> > AAA-DOCTORS mailing list
> > AAA-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/aaa-doctors
> >
> >
> >
> >
> __________________________________________________________
> ____________
> > ___________________________________________________
> >
> > 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.
> >
> > _______________________________________________
> > AAA-DOCTORS mailing list
> > AAA-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/aaa-doctors


_________________________________________________________________________________________________________________________

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.