[Dime] [Technical Errata Reported] RFC7155 (6119)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 24 April 2020 06:21 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 EC6973A0CF5 for <dime@ietfa.amsl.com>; Thu, 23 Apr 2020 23:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 qWTs0rC1nu92 for <dime@ietfa.amsl.com>; Thu, 23 Apr 2020 23:21:56 -0700 (PDT)
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 8664C3A0CEE for <dime@ietf.org>; Thu, 23 Apr 2020 23:21:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2C5A9F406D3; Thu, 23 Apr 2020 23:21:43 -0700 (PDT)
To: glenzorn@gmail.com, warren@kumari.net, rwilton@cisco.com, 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: luke@mewburn.net, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200424062143.2C5A9F406D3@rfc-editor.org>
Date: Thu, 23 Apr 2020 23:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/SIlKcvFlvIvkcnt45Dc8jdTUkLw>
Subject: [Dime] [Technical Errata Reported] RFC7155 (6119)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 24 Apr 2020 06:22:00 -0000
The following errata report has been submitted for RFC7155, "Diameter Network Access Server Application". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6119 -------------------------------------- Type: Technical Reported by: Luke Mewburn <luke@mewburn.net> Section: GLOBAL Original Text ------------- [Missing sections when RFC 4005 was obsoleted by RFC 7155] Corrected Text -------------- 4.7 AVPs Used Only for Compatibility The AVPs defined in this section SHOULD only be used for backwards compatibility when a Diameter/RADIUS translation function is invoked and are not typically originated by Diameter systems during normal operations. +----------+ | AVP Flag | | Rules | |----+-----| |MUST| MUST| Attribute Name Section Defined | | NOT| -----------------------------------------|----+-----| Origin-AAA-Protocol 4.7.1 | M | V | -----------------------------------------|----+-----| 4.7.1. Origin-AAA-Protocol The Origin-AAA-Protocol AVP (AVP Code 408) is of the type Enumerated and should be inserted in a Diameter message translated by a gateway system from another AAA protocol, such as RADIUS. It identifies the source protocol of the message to the Diameter system receiving the message. The supported values are: 1 RADIUS Notes ----- The description of Origin-AAA-Protocol (AVP Code 408) is missing from RFC 7155. The AVP is documented in RFC 4005 section 9.3.6. The proposed corrected text contains RFC 4005 section 9.3 as RFC 7155 section 4.7, and RFC 4005 section 9.3.6 as RFC 7155 section 4.7.1. All other AVPs in RFC 4005 section 9.3.x are not listed because they are documented in their relevant standards already. RFC 7155 is listed as the Reference for Origin-AAA-Protocol in multiple locations in https://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml It appears that there may be an accidental omission of Origin-AAA-Protocol when RFC 7155 obsoleted RFC 4005. The Origin-AAA-Protocol AVP is referenced in other sections in RFC 7155: - 3.1. AA-Request (AAR) Command - 3.2. AA-Answer (AAA) Command - 3.3. Re-Auth-Request (RAR) Command - 3.4. Re-Auth-Answer (RAA) Command - 3.5. Session-Termination-Request (STR) Command - 3.6. Session-Termination-Answer (STA) Command - 3.7. Abort-Session-Request (ASR) Command - 3.8. Abort-Session-Answer (ASA) Command - 3.9. Accounting-Request (ACR) Command - 3.10. Accounting-Answer (ACA) Command - 5.1. AA-Request / AA-Answer AVP Table - 5.2.1. Framed Access Accounting AVP Table - 5.2.2. Non-Framed Access Accounting AVP Table 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. -------------------------------------- RFC7155 (draft-ietf-dime-rfc4005bis-14) -------------------------------------- Title : Diameter Network Access Server Application Publication Date : April 2014 Author(s) : G. Zorn, Ed. Category : PROPOSED STANDARD Source : Diameter Maintenance and Extensions Area : Operations and Management Stream : IETF Verifying Party : IESG
- [Dime] [Technical Errata Reported] RFC7155 (6119) RFC Errata System
- Re: [Dime] [Technical Errata Reported] RFC7155 (6… Rob Wilton (rwilton)