[Dime] [Technical Errata Reported] RFC6733 (6171)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 13 May 2020 13:27 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 E67483A0B33 for <dime@ietfa.amsl.com>; Wed, 13 May 2020 06:27:23 -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 Gk7nCzOl-33p for <dime@ietfa.amsl.com>; Wed, 13 May 2020 06:27:22 -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 0F3C13A08A7 for <dime@ietf.org>; Wed, 13 May 2020 06:27:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 87B82F40729; Wed, 13 May 2020 06:27:05 -0700 (PDT)
To: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, 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: v@pharos-avantgard.com, dime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200513132705.87B82F40729@rfc-editor.org>
Date: Wed, 13 May 2020 06:27:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/3MbUvqQHsQBOMMf1HCFyQbbf4yo>
X-Mailman-Approved-At: Wed, 13 May 2020 07:43:54 -0700
Subject: [Dime] [Technical Errata Reported] RFC6733 (6171)
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: Wed, 13 May 2020 13:27:24 -0000
The following errata report has been submitted for RFC6733, "Diameter Base Protocol". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6171 -------------------------------------- Type: Technical Reported by: Valentin Micic <v@pharos-avantgard.com> Section: 6.1.3 Original Text ------------- A relay or proxy agent MUST check for forwarding loops when receiving requests. A loop is detected if the server finds its own identity in a Route-Record AVP. When such an event occurs, the agent MUST answer with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. Corrected Text -------------- A relay or proxy agent MUST check for forwarding loops when receiving requests. A loop is detected if a relay or proxy agent finds its own identity in a Route-Record AVP. When such an event occurs, the agent MUST answer with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. Notes ----- The term "server" used to identify party which is to detect its own identity as a part of Route-Record AVP is semantically too close to the term Diameter Server. If "relay or proxy agent MUST check", the question is what would be the consequence of such action if the (Diameter) "server" is to do the "detecting"? 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. -------------------------------------- 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
- [Dime] [Technical Errata Reported] RFC6733 (6171) RFC Errata System