IETF Logo Mail Archive

Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP

Steve Donovan <srdonovan@usdonovans.com> Mon, 10 February 2014 14:43 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 9A5FF1A0814 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 06:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 IjByEpbPKk76 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 06:43:52 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [66.117.0.129]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB3A1A02E1 for <dime@ietf.org>; Mon, 10 Feb 2014 06:43:52 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:57396 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WCs4K-0004oq-DE for dime@ietf.org; Mon, 10 Feb 2014 06:42:45 -0800
Message-ID: <52F8E5A7.6030902@usdonovans.com>
Date: Mon, 10 Feb 2014 08:43:51 -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.b54c2f5aeb31c9b3f88c96008120290d@trac.tools.ietf.org> <CD459A84-E32A-49F9-9F5B-95167F318746@gmail.com> <5BCBA1FC2B7F0B4C9D935572D9000668151B259D@DEMUMBX014.nsn-intra.net>
In-Reply-To: <5BCBA1FC2B7F0B4C9D935572D9000668151B259D@DEMUMBX014.nsn-intra.net>
Content-Type: text/plain; charset="ISO-8859-1"
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: srdonovan@usdonovans.com
Subject: Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
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: Mon, 10 Feb 2014 14:43:53 -0000

>>       c) The value of the Application-ID in the Diameter Header of the
>>          request matches the value of the Application-ID of the Diameter
>>          Header of the received message that contained the OC-OLR AVP.
> No need for this since we agreed that DOIC implicitly always refers 
> to the application on which the DOIC AVPs are carried in.
> <Ulrich>yes, we agreed on that, so c) is correct and it does not harm to keep c)</Ulrich>
SRD> I don't see the reason for including this statement.  By
definition, an overload report
applies to the application ID in the answer message.  There is no way
for the application-id
in the answer message to be different than the application-id in the
request message without
breaking Diameter.

v2.23.0 | Report a Bug | By Email