[Dime] [Technical Errata Reported] RFC7683 (5278)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 06 March 2018 10:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55A9127369 for <dime@ietfa.amsl.com>; Tue, 6 Mar 2018 02:56:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5lSgdI1Y9goU for <dime@ietfa.amsl.com>; Tue, 6 Mar 2018 02:56:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA3D6126CF6 for <dime@ietf.org>; Tue, 6 Mar 2018 02:56:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DFABEB81068; Tue, 6 Mar 2018 02:56:01 -0800 (PST)
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
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: lionel.morand@orange.com, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180306105601.DFABEB81068@rfc-editor.org>
Date: Tue, 06 Mar 2018 02:56:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/C3Iwhds2Izw4-5EEosWkEsXg7u4>
X-Mailman-Approved-At: Tue, 06 Mar 2018 02:56:51 -0800
Subject: [Dime] [Technical Errata Reported] RFC7683 (5278)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 10:56:20 -0000
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/eid5278 -------------------------------------- Type: Technical Reported by: Lionel Morand <lionel.morand@orange.com> 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. 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
- [Dime] [Technical Errata Reported] RFC7683 (5278) RFC Errata System