[appsdir] Review request: draft-ietf-tsvwg-circuit-breaker-07.txt
Eliot Lear <lear@cisco.com> Tue, 20 October 2015 13:04 UTC
Return-Path: <lear@cisco.com>
X-Original-To: appsdir@ietfa.amsl.com
Delivered-To: appsdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213B21A039E for <appsdir@ietfa.amsl.com>; Tue, 20 Oct 2015 06:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.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 m-RvzOD1ps6l for <appsdir@ietfa.amsl.com>; Tue, 20 Oct 2015 06:04:13 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 734D61A0064 for <appsdir@ietf.org>; Tue, 20 Oct 2015 06:04:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9646; q=dns/txt; s=iport; t=1445346252; x=1446555852; h=references:subject:to:cc:from:message-id:date: mime-version:in-reply-to; bh=Vnrvy4IjRRuXBmTI8RJl9QTQg3Fummidm1IzQMhGgVM=; b=eF3muwlbZajD1wlkwoXgF8+lAqhYaSpLzifbIJOfI3i82Lg2vMVhxrVm T43szvZrkr3gOs8AaZUfi46Al1xI8Gwqu+fCNWmPHysNw6ohZKmWGZgeU xqGTluGhgc60t6SMoTfQKYiRQd1roz1CJ13MJJBwamq1mHBY3qpx4tbY4 4=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CrBAAWOyZW/xbLJq1ehApvwAchhX0CggwBAQEBAQGBAAuELgEBBCNVARAsFgsCAgkDAgECAUUGDQgBAYgsDbBokxoBAQEBAQEBAQEBAQEBAQEBAQESCYt1hQ0HgmmBRQEEliR6gVSBYWqIBoFYSIN3gwGTCWOEBTw0hWcBAQE
X-IronPort-AV: E=Sophos;i="5.17,707,1437436800"; d="asc'?eml'208?scan'208,208";a="605816487"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Oct 2015 13:04:10 +0000
Received: from [10.61.162.242] ([10.61.162.242]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t9KD4AbG029222; Tue, 20 Oct 2015 13:04:10 GMT
References: <20151019193955.7161.67975.idtracker@ietfa.amsl.com>
To: "appsdir@ietf.org" <appsdir@ietf.org>
From: Eliot Lear <lear@cisco.com>
X-Enigmail-Draft-Status: N1110
X-Forwarded-Message-Id: <20151019193955.7161.67975.idtracker@ietfa.amsl.com>
Message-ID: <56263BC9.5050706@cisco.com>
Date: Tue, 20 Oct 2015 15:04:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151019193955.7161.67975.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="KvmBldNQFuU2TxncxteRTO1kwBgoWSk9i"
Archived-At: <http://mailarchive.ietf.org/arch/msg/appsdir/HyLh0X3uxOIo3EaYcuXN7OiD9dY>
Cc: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, David Black <black_david@emc.com>
Subject: [appsdir] Review request: draft-ietf-tsvwg-circuit-breaker-07.txt
X-BeenThere: appsdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Apps Area Review List <appsdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/appsdir>, <mailto:appsdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/appsdir/>
List-Post: <mailto:appsdir@ietf.org>
List-Help: <mailto:appsdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/appsdir>, <mailto:appsdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 13:04:20 -0000
Hi everyone, The attached draft talks about a "circuit breaker" that could sit at certain points in the network to prevent congestion collapse on otherwise uncontrolled flows. This HAPPENS today and is the normal form of a policing function in a QoS model, and it's great that Gory is documenting it. However, circuit breakers can and do cause applications problems (David can correct me but I think this was part of the impetus of the draft, in fact). A misbehaving circuit breaker in particular might really throw people for a loop. I am seeking a reviewer, and would like to double-team on this draft with that person to get a timely review done for Gory and the TSVWG. Do I have any takers? Please let me know by tomorrow. I'd like to complete work by the end of next week, before people get to Yokohama, if at all possible, and I'm happy to take the first cut (or not). Eliot
--- Begin Message ---
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.
Title : Network Transport Circuit Breakers
Author : Godred Fairhurst
Filename : draft-ietf-tsvwg-circuit-breaker-07.txt
Pages : 23
Date : 2015-10-19
Abstract:
This document explains what is meant by the term "network transport
Circuit Breaker" (CB). It describes the need for circuit breakers
when using network tunnels, and other non-congestion controlled
applications, and explains where circuit breakers are, and are not,
needed. It also defines requirements for building a circuit breaker
and the expected outcomes of using a circuit breaker within the
Internet.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-circuit-breaker/
There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tsvwg-circuit-breaker-07
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-circuit-breaker-07
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
--- End Message ---