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

"john.zhao" <yuankui.zhao@gmail.com> Mon, 12 March 2018 16:35 UTC

Return-Path: <yuankui.zhao@gmail.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 AE189124C27 for <aaa-doctors@ietfa.amsl.com>; Mon, 12 Mar 2018 09:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 uG7joFSu26kk for <aaa-doctors@ietfa.amsl.com>; Mon, 12 Mar 2018 09:35:48 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7701200E5 for <aaa-doctors@ietf.org>; Mon, 12 Mar 2018 09:35:47 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id x205-v6so5965371lfa.0 for <aaa-doctors@ietf.org>; Mon, 12 Mar 2018 09:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k6TwrCd7MbPAimC4sn0a4VceD+p15NCQD6cHPuwkVE4=; b=t8yiAsPnb+062zxYvEsxxKul6iGQ5PpI3RvS33UobuvN2xzH85NTwOZR6ebHErH4fy qkxBd025r+nvyKD/h2OxlXli22yqIZVmZOC8fiog+hhgXe2OUC6A5kWq9owwUu3sGw8W Arm67+LlCCU3mbUHurfTXed4fG/88WeB4WKlxGr3iDoZUM60fHrqW+Dx8sak2L9Iu2zy e7W870ZELpc9jYMW0rBr8XGbe6t6tl2CnXybbuKmaa/XA8/Qdi5NNHYXsls4VylZJ1fJ DOwMQdIJLnl+NA0cHVMy+1t0/c0ZG9fkT0DIaEuXbw+lfGDMOHYFZavi+0nQi9+bBoRS n4Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k6TwrCd7MbPAimC4sn0a4VceD+p15NCQD6cHPuwkVE4=; b=eh0I6cUThwRSbGlBgn+uPa7A3mTGGz51aO8Td/173G6RbpHhU7mF5GoCQzjsLAGOaX xp300x1ZqZmNSUAj89XHqldrWQDn8ikV/wgwP0wTW9Y+oglLVKrtk1CN7ZEZhs9rTqpA V7fUbmrTZyKAFMkti0gDHMVaxVlhUkDDM5SyDx8HoVPrzFf4FUnu6/Yk3GIwpslQ5K51 5Y7suW1lHea2PtO4PU+ovEy10DFxAkETMWpwsFtYtebF6WLKjkzGnW0bINrqd5cjbGl3 WdOX8xlIpByy8vXsGZXQUBFNP1M3EMruBT/8WTCkckOSdbsogd5OTM3DM9QOUzCW4k/k I4Tg==
X-Gm-Message-State: AElRT7FTcGefeHCbtDAPNE/5XJ9gIvyOMrQt8G8jb4yG8dd1i/5leqlb pTufeCjeJEGzcRFs6quW8KcYbYH8Buz35vJbgDKKNw==
X-Google-Smtp-Source: AG47ELu6pBa5UCIMoNV+Dy6F+srA6zDTmSIiGV8Kz5BjHFL+yvyrBnpBWNE8BDVNRtC3gn7wbYbhZ7jBney+t+I4MNQ=
X-Received: by 10.46.60.22 with SMTP id j22mr5463725lja.27.1520872545890; Mon, 12 Mar 2018 09:35:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:e820:0:0:0:0:0 with HTTP; Mon, 12 Mar 2018 09:35:45 -0700 (PDT)
In-Reply-To: <68c132b6-52de-59d9-1d05-0bab97bb9212@cisco.com>
References: <20180306104750.EF13EB80E97@rfc-editor.org> <68c132b6-52de-59d9-1d05-0bab97bb9212@cisco.com>
From: "john.zhao" <yuankui.zhao@gmail.com>
Date: Tue, 13 Mar 2018 00:35:45 +0800
Message-ID: <CADpucjW=fuxjMRS10Jt3A4No8Li0eVb5Q1S==Z9+yneCvQTFjA@mail.gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Cc: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="f4f5e807453cd8b585056739bba5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/kUq45TT461NzHKXi3W7NrBSnDVw>
Subject: Re: [AAA-DOCTORS] Fwd: [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, 12 Mar 2018 16:35:54 -0000

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>;
> <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>; <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
>
>