Re: [i2rs] draft-ietf-i2rs-ephemeral-state-09, Ephemeral-REQ-05
"Susan Hares" <shares@ndzh.com> Wed, 01 June 2016 16:04 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8B812D11B for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 09:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no autolearn_force=no
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 ImJQbXbpuYQp for <i2rs@ietfa.amsl.com>; Wed, 1 Jun 2016 09:04:33 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BE3212B057 for <i2rs@ietf.org>; Wed, 1 Jun 2016 09:04:33 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.63;
From: Susan Hares <shares@ndzh.com>
To: 'Jeffrey Haas' <jhaas@pfrc.org>, i2rs@ietf.org
References: <20160601160450.GR17462@pfrc.org>
In-Reply-To: <20160601160450.GR17462@pfrc.org>
Date: Wed, 01 Jun 2016 12:04:28 -0400
Message-ID: <006f01d1bc1f$47014a50$d503def0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ9ndGW8PQQ92Z4NRJPX3Z02Pog4559Ajbg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/kRIi5Tll_Wf_pdxcfinyMj0LMic>
Subject: Re: [i2rs] draft-ietf-i2rs-ephemeral-state-09, Ephemeral-REQ-05
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 16:04:39 -0000
I2RS WG: Two replacements for Ephemeral-REQ-05: Option 1: I2RS pub-sub, logging, RPC or other mechanisms may lead to undesirable or unsustainable resource consumption on a system implementing an I2RS Agent. It is RECOMMENDED that mechanisms be made available to permit prioritization of I2RS operations, when appropriate, to permit implementations to shed work load when operating under constrained resources. An example of such a work shedding mechanism is rate-limiting. Option 2: Ephemeral state handling, notifications, and OAM could increase the data flow rates across transport, or the rate of publication of data in a subscription, or logging needed for traceability. It is RECOMMENDED that the I2RS Agent should have the ability to limit, prioritize or split data flows in the I2RS protocol. Any feedback? Sue -----Original Message----- From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Jeffrey Haas Sent: Wednesday, June 01, 2016 12:05 PM To: i2rs@ietf.org Subject: [i2rs] draft-ietf-i2rs-ephemeral-state-09, Ephemeral-REQ-05 As per the interim, here is some suggested text changes: Existing text: Ephemeral-REQ-05: Ephemeral state handling and notifications could increase need for CPU processing, data flow rates across a transport, or the rate of publication of data in a subscription or the logging for traceability. The I2RS Agent SHOULD have the ability to constraints for OAM functions operating to limit CPU processing, data rate across a transport, the rate of publication of data in a subscription, and logging rates; and the I2RS Agent SHOULD have the ability to prioritize some of the management data flows between the I2RS Agent and I2RS Client. In order to constrain resources needed, the I2RS Agent MAY also schedule data flows or split data flows unto multiple data flow streams. Suggested new text: I2RS pub-sub, logging, RPC or other mechanisms may lead to undesirable or unsustainable resource consumption on a system implementing an I2RS Agent. It is RECOMMENDED that mechanisms be made available to permit prioritization of I2RS operations, when appropriate, to permit implementations to shed work load when operating under constrained resources. An example of such a work shedding mechanism is rate-limiting. ----- Note that Subscription QoS in the pub-sub requirements provides for this type of behavior in that context. -- Jeff _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
- [i2rs] draft-ietf-i2rs-ephemeral-state-09, Epheme… Jeffrey Haas
- Re: [i2rs] draft-ietf-i2rs-ephemeral-state-09, Ep… Susan Hares
- Re: [i2rs] draft-ietf-i2rs-ephemeral-state-09, Ep… Eric Voit (evoit)