Re: [Dime] [dime] #23: DOIC behavior for realm overload
Steve Donovan <srdonovan@usdonovans.com> Wed, 19 February 2014 20:54 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 0DBD51A04F2 for <dime@ietfa.amsl.com>; Wed, 19 Feb 2014 12:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 I-kblkbsPD2X for <dime@ietfa.amsl.com>; Wed, 19 Feb 2014 12:54:22 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA721A0418 for <dime@ietf.org>; Wed, 19 Feb 2014 12:54:22 -0800 (PST)
Received: from 130.sub-70-196-5.myvzw.com ([70.196.5.130]:1057 helo=[192.168.43.20]) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WGE9o-0003xy-2C for dime@ietf.org; Wed, 19 Feb 2014 12:54:18 -0800
Message-ID: <530519F7.1010207@usdonovans.com>
Date: Wed, 19 Feb 2014 14:54:15 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dime@ietf.org
References: <066.bc8b33b812f849d70cc96ca6c7f6d77d@trac.tools.ietf.org>
In-Reply-To: <066.bc8b33b812f849d70cc96ca6c7f6d77d@trac.tools.ietf.org>
Content-Type: multipart/alternative; boundary="------------090104000005040207030900"
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: srdonovan@usdonovans.com
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/lc2wNdhKmSaZ6UD1AgX0enbqGgk
Subject: Re: [Dime] [dime] #23: DOIC behavior for realm overload
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: Wed, 19 Feb 2014 20:54:24 -0000
We've had a lot of discussion of this topic. I believe that we reached agreement that we currently have two types of reports: - Host report that applies to requests sent to a destination-host - Realm report that applies requests routed to a realm that do not have a specified destination-host (realm-routed requests) We also have proposed wording on the interaction between these report types. I propose that the second be renamed to realm-routed reports. A separate ticket has been opened on the need for a third report type that would apply to all request routed to a realm, independent of whether a request contains a destination-host AVP. Steve On 1/21/14 9:24 AM, dime issue tracker wrote: > #23: DOIC behavior for realm overload > > This applies to draft-ietf-dime-ovli-01, which does not show up in the > Component drop down menu. > > The current assumption in the -01 draft is inconsistent in the definition > of behavior of behavior by a reacting node when it receives a realm > overload report. > > Section 4.6 says overload treatment should apply to all request bound for > the overloaded realm. > > Section 5.5.2 is not clear and there have been interpretations that a > realm overload report only applies to requests that contain the realm and > do not contain a destination-host AVP. > > Section 5.5.2 should be updated to be consistent with section 4.6. >
- Re: [Dime] [dime] #23: DOIC behavior for realm ov… Steve Donovan
- Re: [Dime] [dime] #23: DOIC behavior for realm ov… Wiehe, Ulrich (NSN - DE/Munich)
- [Dime] [dime] #23: DOIC behavior for realm overlo… dime issue tracker
- Re: [Dime] [dime] #23: DOIC behavior for realm ov… Ben Campbell
- Re: [Dime] [dime] #23: DOIC behavior for realm ov… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #23: DOIC behavior for realm ov… Steve Donovan
- Re: [Dime] [dime] #23 (draft-ietf-dime-ovli): DOI… dime issue tracker
- Re: [Dime] [dime] #23 (draft-ietf-dime-ovli): DOI… dime issue tracker