Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Fri, 07 February 2014 13:08 UTC
Return-Path: <ulrich.wiehe@nsn.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 66CF41A1DE2 for <dime@ietfa.amsl.com>; Fri, 7 Feb 2014 05:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 5t2IBXwxqSiu for <dime@ietfa.amsl.com>; Fri, 7 Feb 2014 05:08:18 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6848E1A16F1 for <dime@ietf.org>; Fri, 7 Feb 2014 05:08:17 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id s17D8Gua026464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 7 Feb 2014 14:08:16 +0100
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s17D8FMB029243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Feb 2014 14:08:16 +0100
Received: from DEMUHTC014.nsn-intra.net (10.159.42.45) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 7 Feb 2014 14:08:15 +0100
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.242]) by DEMUHTC014.nsn-intra.net ([10.159.42.45]) with mapi id 14.03.0123.003; Fri, 7 Feb 2014 14:08:15 +0100
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: ext Jouni Korhonen <jouni.nospam@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
Thread-Index: AQHPI+1LK95DWDMaH0qQEyVc/ebDNpqpv0Fw
Date: Fri, 07 Feb 2014 13:08:15 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D9000668151B259D@DEMUMBX014.nsn-intra.net>
References: <066.b54c2f5aeb31c9b3f88c96008120290d@trac.tools.ietf.org> <CD459A84-E32A-49F9-9F5B-95167F318746@gmail.com>
In-Reply-To: <CD459A84-E32A-49F9-9F5B-95167F318746@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 3345
X-purgate-ID: 151667::1391778496-000025D0-1E8E819B/0-0/0-0
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: Fri, 07 Feb 2014 13:08:21 -0000
Jouni Please see inline. Ulrich -----Original Message----- From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Jouni Korhonen Sent: Friday, February 07, 2014 11:14 AM To: dime@ietf.org Subject: Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP Few comments here. On Feb 4, 2014, at 10:54 AM, dime issue tracker <trac+dime@trac.tools.ietf.org> wrote: > #34: Semantics of OC-Report-Type AVP > > Text in clause 4.6 does not fully explain to which requests overload > treatment of a given report type applies. > Proposal: > > 0 A host report. The overload treatment should apply to requests > for which all of the following conditions are true: > a) The Destination-Host AVP is present in the request and its value > matches the value of the Origin-Host AVP of the received message > that contained the OC-OLR AVP. > b) The value of the Destination-Realm AVP in the request matches the > value of the Origin-Realm AVP of the received message > that contained the OC-OLR AVP. It is perfectly valid to send a request that has Destination-Host AVP but no Destination-Realm AVP. It just means the Diameter nodes must be adjacent peers. <Ulrich> ok, then let's remove b) from 0</Ulrich> > 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> > 1 A realm report. The overload treatment should apply to > requests for which all of the following conditions are true: > a) The Destination-Host AVP is absent in the request. > b) The value of the Destination-Realm AVP in the request matches the > value of the Origin-Realm AVP of the received message > that contained the OC-OLR AVP. > 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. Same not as above. <Ulrich> I understand that this "above" referrs to 0c), not to 0b). Same response as above. </Ulrich> - JOuni > > -- > --------------------------------------+-------------------------- > Reporter: lionel.morand@orange.com | Owner: Ulrich Wiehe > Type: defect | Status: new > Priority: major | Milestone: > Component: draft-docdt-dime-ovli | Version: > Severity: Active WG Document | Keywords: > --------------------------------------+-------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/34> > dime <http://tools.ietf.org/wg/dime/> > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime
- [Dime] [dime] #34: Semantics of OC-Report-Type AVP dime issue tracker
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34 (draft-docdt-dime-ovli): Se… dime issue tracker
- Re: [Dime] [dime] #34 (draft-docdt-dime-ovli): Se… Steve Donovan
- Re: [Dime] [dime] #34 (draft-ietf-dime-ovli): Sem… dime issue tracker