[Dime] [Errata Rejected] RFC6733 (4462)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 11 September 2015 12:57 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D6A1B49AE; Fri, 11 Sep 2015 05:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 V34YD4r6Vmyf; Fri, 11 Sep 2015 05:57:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 889891B4950; Fri, 11 Sep 2015 05:57:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DEB82181D1B; Fri, 11 Sep 2015 05:57:27 -0700 (PDT)
To: keshab@smsgt.com, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150911125727.DEB82181D1B@rfc-editor.org>
Date: Fri, 11 Sep 2015 05:57:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/75x-uylrxjvtH6M3yb_RO4CZoUM>
Cc: rfc-editor@rfc-editor.org, dime@ietf.org, iesg@ietf.org
Subject: [Dime] [Errata Rejected] RFC6733 (4462)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 12:57:48 -0000
The following errata report has been rejected for RFC6733, "Diameter Base Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4462 -------------------------------------- Status: Rejected Type: Technical Reported by: Keshab Upadhya <keshab@smsgt.com> Date Reported: 2015-09-01 Rejected by: Stephen Farrell (IESG) Section: 6.1.4 6.1.6 Original Text ------------- 6.1.4. Processing Local Requests A request is known to be for local consumption when one of the following conditions occurs: o The Destination-Host AVP contains the local host's identity; o The Destination-Host AVP is not present, the Destination-Realm AVP contains a realm the server is configured to process locally, and the Diameter application is locally supported; or o Both the Destination-Host and the Destination-Realm are not present. 6.1.6. Request Routing Diameter request message routing is done via realms and Application Ids. A Diameter message that may be forwarded by Diameter agents (proxies, redirect agents, or relay agents) MUST include the target realm in the Destination-Realm AVP. Request routing SHOULD rely on the Destination-Realm AVP and the Application Id present in the request message header to aid in the routing decision. The realm MAY be retrieved from the User-Name AVP, which is in the form of a Network Access Identifier (NAI). The realm portion of the NAI is inserted in the Destination-Realm AVP. Diameter agents MAY have a list of locally supported realms and applications, and they MAY have a list of externally supported realms and applications. When a request is received that includes a realm and/or application that is not locally supported, the message is routed to the peer configured in the routing table (see Section 2.7). Realm names and Application Ids are the minimum supported routing criteria, additional information may be needed to support redirect semantics. Corrected Text -------------- 6.1.6 - When a request is received that includes a realm and/or application that is not locally supported, the message is routed to the peer configured conflicts with 6.1.4 - The Destination-Host AVP is not present, the Destination-Realm AVP contains a realm the server is configured to process locally, and the Diameter application is locally supported Notes ----- please guide if 6.1.4 Local processing - "hostname not present" needs to be amended by "not present in host peer routing table". otherwise it conflicts with 6.1.6. --VERIFIER NOTES-- DIME WG chairs report this is erroneous. -------------------------------------- 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 (4462) RFC Errata System
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… lionel.morand
- [Dime] [Errata Rejected] RFC6733 (4462) RFC Errata System
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Jouni Korhonen
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Jouni
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Jouni Korhonen
- Re: [Dime] [Technical Errata Reported] RFC6733 (4… Keshab Upadhya