[Dime] Issue #23 - Proposed resolution

Steve Donovan <srdonovan@usdonovans.com> Tue, 29 July 2014 19:22 UTC

Return-Path: <srdonovan@usdonovans.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 B98671A02D8 for <dime@ietfa.amsl.com>; Tue, 29 Jul 2014 12:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.579
X-Spam-Level: *
X-Spam-Status: No, score=1.579 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_NEUTRAL=0.779] 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 N4-GX9ZLbAIF for <dime@ietfa.amsl.com>; Tue, 29 Jul 2014 12:22:25 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [66.117.4.208]) (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 1A0AA1A01CB for <dime@ietf.org>; Tue, 29 Jul 2014 12:22:25 -0700 (PDT)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:65069 helo=Steves-MacBook-Air-2.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1XCCyd-0004tM-0N for dime@ietf.org; Tue, 29 Jul 2014 12:22:23 -0700
Message-ID: <53D7F470.3090500@usdonovans.com>
Date: Tue, 29 Jul 2014 14:22:24 -0500
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "dime@ietf.org" <dime@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srd+usdonovans.com/only user confirmed/virtual account not confirmed
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/jnUHKgIYzZGp9UwUp5yqIct19eE
Subject: [Dime] Issue #23 - Proposed resolution
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: <http://www.ietf.org/mail-archive/web/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, 29 Jul 2014 19:22:25 -0000

Issue @23 points out that there are two interpretations of the realm 
overload report in the current text.  One implies that a realm report 
applies to all requests sent to the realm, the other implies that it 
only applies to requests sent to the realm that does not contain a 
destination-host AVP.

I believe we have consensus to use the second definition.

There was also a proposal, made by me, to change the name of the report 
to something like "realm-routed-request" to be more accurate in defining 
what the scope of the overload report.  I no longer think this is 
necessary and am happy with the "realm" name for the report.

If we have agreement on the direction then I will identify the text that 
needs to be changed to remove the conflicting definitions of the report 
type.  I will send it to the list for review before incorporating it 
into the -04 version of the draft and closing the issue.

Please let me know if there are issues with this proposal.

Regards,

Steve