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

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 07 February 2014 10:23 UTC

Return-Path: <jouni.nospam@gmail.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 BD3811A035D for <dime@ietfa.amsl.com>; Fri, 7 Feb 2014 02:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 iJ9fqgZAB2J2 for <dime@ietfa.amsl.com>; Fri, 7 Feb 2014 02:23:19 -0800 (PST)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 99BA21A05ED for <dime@ietf.org>; Fri, 7 Feb 2014 02:23:18 -0800 (PST)
Received: by mail-la0-f52.google.com with SMTP id c6so2511890lan.11 for <dime@ietf.org>; Fri, 07 Feb 2014 02:23:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YJeIpM+GXO9iKIzVXoJEtXVJ/YwNP2EBxz99oHee4RQ=; b=iODJMso8t8TVGfnL90WjWhpWPRxa05CL1Yql0Jc+SxiNbp5e7qp+JSi4K+Z13a70r+ +kAzcLruJNOeoRfsICo6qYfAfiSG5RFQXGBo0eTWVGJHvMHEHD/Rr5nGgc+jptmw4k3c wgGlkcNChljwObS8CYNnbGwrjjvs5/gUsOwJ2uPe2FJiSmEluWX7EYIOI0m6NvroNWOu j0NR9/INPwfnFk5jKfA/32oQhaAPU+9QG55W/E/oGVamZS3DT1NPkdbrv0IgxkR5fdI/ av7j+F2kK19R70cLBdFxtiJuxE/DWCAJ7yHHkBShn86FXGieVxT4FDaTPYUGiwI/C/gT K+sQ==
X-Received: by 10.112.132.131 with SMTP id ou3mr8906703lbb.29.1391768596616; Fri, 07 Feb 2014 02:23:16 -0800 (PST)
Received: from ?IPv6:2001:6e8:480:60:5cf:580e:21dd:449d? ([2001:6e8:480:60:5cf:580e:21dd:449d]) by mx.google.com with ESMTPSA id y2sm6072123lal.10.2014.02.07.02.23.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 02:23:15 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <26607_1391620178_52F27052_26607_6697_1_6B7134B31289DC4FAF731D844122B36E4876CC@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Date: Fri, 07 Feb 2014 12:23:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E18602D4-2A89-4698-8967-94F950369251@gmail.com>
References: <066.b908ffa610747388ec343de03f526af3@trac.tools.ietf.org> <26607_1391620178_52F27052_26607_6697_1_6B7134B31289DC4FAF731D844122B36E4876CC@PEXCVZYM13.corporate.adroot.infra.ftgroup>
To: lionel.morand@orange.com
X-Mailer: Apple Mail (2.1510)
Cc: "dime@ietf.org" <dime@ietf.org>, "draft-docdt-dime-ovli@tools.ietf.org" <draft-docdt-dime-ovli@tools.ietf.org>
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: Fri, 07 Feb 2014 10:23:20 -0000

Agree.

On Feb 5, 2014, at 7:09 PM, lionel.morand@orange.com wrote:

> 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.
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime