Re: [P2PSIP] [VIPR] Quotas

Cullen Jennings <fluffy@cisco.com> Thu, 09 June 2011 15:27 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8132F11E80FD; Thu, 9 Jun 2011 08:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01U5T53luHMz; Thu, 9 Jun 2011 08:27:10 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id B2EA711E80DD; Thu, 9 Jun 2011 08:27:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=3081; q=dns/txt; s=iport; t=1307633230; x=1308842830; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=n+ZBe5DyuLrUjgA5N2VL5JncwrVDtgKWROBpU1V9lLY=; b=TNqZe8KeYpsvyYMX2wAaMzrxISWLlV59BatqcPLfH7IE6ZQNDZrJlnzV lfiZgfWjpMt5pTjFkjqH0z3wGQTLOUFgjcHcSYKy6xXFKv0TQx0IdU6bj hYhOghsoBKz2bP/3h5OoxBWZejL/xW9a5keC080kqjAZbLS6Sg9FvE9z6 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOfl8E2rRDoI/2dsb2JhbABTpjt3qheeH4MdgwYEhwiKIoRNiyQ
X-IronPort-AV: E=Sophos;i="4.65,341,1304294400"; d="scan'208";a="462702680"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-1.cisco.com with ESMTP; 09 Jun 2011 15:26:33 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p59FQWbA027977; Thu, 9 Jun 2011 15:26:32 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4DED7F87.2090305@acm.org>
Date: Thu, 09 Jun 2011 09:26:32 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B9C94BB-EA37-4BD3-A4CA-267FC86B4277@cisco.com>
References: <4DED7F87.2090305@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
Cc: "vipr@ietf.org" <vipr@ietf.org>, P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] [VIPR] Quotas
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 15:27:12 -0000

I can't put my finger on why, but I get very nervous about suing downloadable scripts to enforce critical system constraints such as security and quotas. It just seems like a disaster waiting to happen. That said, I can't come up with any specific problem of why it would not work but it makes me feel very uneasy. 

It does seems reasonable to make this type of quota a general purpose extension to reload that could be used by things beyond vipr WG stuff. 

On Jun 6, 2011, at 7:31 PM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Now that version -15 of RELOAD is out, I am able to restart editing
> draft-petithuguenin-vipr-reload-usage which is, as its name indicates, a RELOAD
> usage for VIPR.  Most of it can now be implemented with standard RELOAD,
> excepted for one thing, the quota algorithm.
> 
> The quota algorithm in VIPR is interesting because it looks like it can be
> applied to other resources than the one handled by VIPR.  This quota works by
> using a variable that limits, at a responsible peer, the number of resources
> that can be stored by one storing peer.  More precisely, the number of unique
> resource (of one kind) that a storing node can store in one responsible peer is
> the quota value divided by the fraction of resources this peer is responsible
> for (adjusted for the number of replicas and other parameters, but let's forget
> this for now).  The two standard quota parameters in RELOAD only limit the
> absolute number and or size of the resources that can be stored.
> 
> The ideal would be to add the VIPR quota inside the RELOAD base spec. Having
> stuff in base is good because in this case any RELOAD implementation could be
> used for VIPR (or any other overlay), and - in my opinion - having multiple
> implementations of RELOAD inside one overlay is what will help an overlay to
> survive a programmer error.
> 
> Now I would agree that we should stop adding stuff to base, to have a chance to
> see it published as an RFC one day, so perhaps an alternative idea is to do the
> same thing for quotas that I did for access control policy:  Use a script in the
> configuration file to express the quota algorithm associated to a specific Kind-ID.
> 
> Is there any opinions or questions or comments on this?
> 
> Note that this email is cross posted with the VIPR working group, but please
> follow up only in P2PSIP.
> 
> Thanks.
> 
> - -- 
> Marc Petit-Huguenin
> Personal email: marc@petit-huguenin.org
> Professional email: petithug@acm.org
> Blog: http://blog.marc.petit-huguenin.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> 
> iEYEARECAAYFAk3tf4UACgkQ9RoMZyVa61f0LwCgm4OkWYDf46pZ7GjfPfu93BBJ
> NcUAnAtLP1kTvzZ51F9jTucTUcTp6f9Y
> =kM4T
> -----END PGP SIGNATURE-----
> _______________________________________________
> VIPR mailing list
> VIPR@ietf.org
> https://www.ietf.org/mailman/listinfo/vipr