IETF Logo Mail Archive

Re: [Dime] [dime] #28: Report type support in capabilities?

<lionel.morand@orange.com> Wed, 05 February 2014 17:09 UTC

Return-Path: <lionel.morand@orange.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 0AEE61A00F7 for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 09:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 rGbB7aZryhO1 for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 09:09:40 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id E539C1A0122 for <dime@ietf.org>; Wed, 5 Feb 2014 09:09:39 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 76A6A22C3EB; Wed, 5 Feb 2014 18:09:38 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 5AC684C07C; Wed, 5 Feb 2014 18:09:38 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0174.001; Wed, 5 Feb 2014 18:09:38 +0100
From: lionel.morand@orange.com
To: "dime@ietf.org" <dime@ietf.org>, "draft-docdt-dime-ovli@tools.ietf.org" <draft-docdt-dime-ovli@tools.ietf.org>, "srdonovan@usdonovans.com" <srdonovan@usdonovans.com>
Thread-Topic: [Dime] [dime] #28: Report type support in capabilities?
Thread-Index: AQHPHtINDyLLtzyX8k6tlE6/3O5WMZqm5Qaw
Date: Wed, 05 Feb 2014 17:09:37 +0000
Message-ID: <26607_1391620178_52F27052_26607_6697_1_6B7134B31289DC4FAF731D844122B36E4876CC@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <066.b908ffa610747388ec343de03f526af3@trac.tools.ietf.org>
In-Reply-To: <066.b908ffa610747388ec343de03f526af3@trac.tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.2.5.114814
Subject: Re: [Dime] [dime] #28: Report type support in capabilities?
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, 05 Feb 2014 17:09:42 -0000

The default mechanism implies that a client will be able to manage both types of report. Therefore there is no need at this stage IMHO.

In future, if there is a need to explicitly indicate which report type a node support, it may be a hint for defining different capabilities/algos. And this new capability will be described a new companion document.

Lionel

-----Message d'origine-----
De : DiME [mailto:dime-bounces@ietf.org] De la part de dime issue tracker
Envoyé : vendredi 31 janvier 2014 23:16
À : draft-docdt-dime-ovli@tools.ietf.org; srdonovan@usdonovans.com
Cc : dime@ietf.org
Objet : [Dime] [dime] #28: Report type support in capabilities?

#28: Report type support in capabilities?

 This applies to draft-ietf-dime-ovli

 This is more of a question than an issue.

 We currently only include the abatement algorithm in the OC-Feature-Vector
 AVP.  The question is whether we should expand it to include support for
 the host(server) report and realm report.

 The reason for the question is that the agent overload extension will
 likely include an indicator in the OC-Feature-Vector of support for the
 peer report type.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-docdt-dime-
  srdonovan@usdonovans.com           |  ovli@tools.ietf.org
     Type:  defect                   |     Status:  new
 Priority:  minor                    |  Milestone:
Component:  draft-docdt-dime-ovli    |    Version:
 Severity:  Submitted WG Document    |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/28>
dime <http://tools.ietf.org/wg/dime/>

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

v2.23.0 | Report a Bug | By Email