Re: [Dime] [Technical Errata Reported] RFC6733 (4462)
"Keshab Upadhya" <keshab@smsgt.com> Thu, 10 September 2015 03:26 UTC
Return-Path: <keshab@smsgt.com>
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 D611F1A1B4C for <dime@ietfa.amsl.com>; Wed, 9 Sep 2015 20:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.427
X-Spam-Level:
X-Spam-Status: No, score=-1.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URG_BIZ=0.573] autolearn=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 RxlRSd0Hny75 for <dime@ietfa.amsl.com>; Wed, 9 Sep 2015 20:26:28 -0700 (PDT)
Received: from gateway34.websitewelcome.com (gateway34.websitewelcome.com [192.185.149.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 518721A8AAC for <dime@ietf.org>; Wed, 9 Sep 2015 20:26:28 -0700 (PDT)
Received: by gateway34.websitewelcome.com (Postfix, from userid 500) id B7DB83C3DB743; Wed, 9 Sep 2015 22:26:27 -0500 (CDT)
Received: from cm5.websitewelcome.com (cm5.websitewelcome.com [192.185.178.233]) by gateway34.websitewelcome.com (Postfix) with ESMTP id B56803C3DB727 for <dime@ietf.org>; Wed, 9 Sep 2015 22:26:27 -0500 (CDT)
Received: from gator4074.hostgator.com ([192.185.4.85]) by cm5.websitewelcome.com with id FFSS1r00a1q3akG01FSTRH; Wed, 09 Sep 2015 22:26:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smsgt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=pW+1v8+UnNv4iCLf5nbvgY+f2yHtBN7yQpSMwO7Sz68=; b=Mf/Met06CkqOFedrgGrKkc/idbjW8g1Kse83nmRpuZfweI72VlApfRiHmeRh0oiGXude/++jW+GeaVPodDkRc6ly+sIMaJyolmQnej7A/SWC+UzBhdbY9irq/m6SycpBB+VR9oMp3LzV6Tw15OXErNAB148uAl0Pi66T5JH9L9M=;
Received: from [121.58.195.226] (port=50440 helo=Keshab) by gator4074.hostgator.com with smtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from <keshab@smsgt.com>) id 1ZZsVF-000ASa-Df; Wed, 09 Sep 2015 22:26:25 -0500
From: Keshab Upadhya <keshab@smsgt.com>
To: 'RFC Errata System' <rfc-editor@rfc-editor.org>, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com
References: <20150902010923.059A2180474@rfc-editor.org>
In-Reply-To: <20150902010923.059A2180474@rfc-editor.org>
Date: Thu, 10 Sep 2015 11:25:53 +0800
Message-ID: <00fc01d0eb78$69cdeb10$3d69c130$@smsgt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJjReiBNFWUJ68CiMoyGb3CJoxo450QZBKw
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator4074.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smsgt.com
X-BWhitelist: no
X-Source-IP: 121.58.195.226
X-Exim-ID: 1ZZsVF-000ASa-Df
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (Keshab) [121.58.195.226]:50440
X-Source-Auth: allan
X-Email-Count: 124
X-Source-Cap: YWxsYW47YWxsYW47Z2F0b3I0MDc0Lmhvc3RnYXRvci5jb20=
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/_9jsMwgfQy72WNep1khB98LnK0A>
X-Mailman-Approved-At: Thu, 10 Sep 2015 08:16:40 -0700
Cc: dime@ietf.org
Subject: Re: [Dime] [Technical Errata Reported] 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: Thu, 10 Sep 2015 03:28:27 -0000
Hi All, Good day! Could you please help on below request raised as conflict in RFC-6733? Kindly consider this as an urgent request. Thank you, Regards, Keshab. -----Original Message----- From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] Sent: Wednesday, September 2, 2015 9:09 AM To: vf0213@gmail.com; jari.arkko@ericsson.com; john.loughney@nokia.com; glenzorn@gmail.com; bclaise@cisco.com; joelja@bogus.com; jouni.nospam@gmail.com; lionel.morand@orange.com Cc: keshab@smsgt.com; dime@ietf.org; rfc-editor@rfc-editor.org Subject: [Technical Errata Reported] RFC6733 (4462) The following errata report has been submitted 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 -------------------------------------- Type: Technical Reported by: Keshab Upadhya <keshab@smsgt.com> 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. 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 (IESG) 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 (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