[core] CoCoA and Aggregate Congestion Control [Fwd: New Version Notification for draft-bormann-core-cocoa-04.txt]
"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Thu, 14 July 2016 16:13 UTC
Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF4112D0AD for <core@ietfa.amsl.com>; Thu, 14 Jul 2016 09:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham 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 PDVqS2Z4M9w3 for <core@ietfa.amsl.com>; Thu, 14 Jul 2016 09:13:40 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE28F12D0E9 for <core@ietf.org>; Thu, 14 Jul 2016 09:13:39 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.1/8.13.1) with ESMTP id u6EGDa0m004238 for <core@ietf.org>; Thu, 14 Jul 2016 18:13:37 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id D763B1D53C1; Thu, 14 Jul 2016 18:13:36 +0200 (CEST)
Received: from 131.111.5.144 by webmail.entel.upc.edu with HTTP; Thu, 14 Jul 2016 18:14:23 +0200
Message-ID: <a104d49b3229d9831305bfdac233b8a6.squirrel@webmail.entel.upc.edu>
Date: Thu, 14 Jul 2016 18:14:23 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: core@ietf.org
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Mail-Scanned: Criba 2.0 + Clamd
X-Greylist: ACL matched, not delayed by milter-greylist-4.4.3 (violet.upc.es [147.83.2.51]); Thu, 14 Jul 2016 18:13:37 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/9wcCNvUiw-vy5h2ArwWW__Pgq90>
Subject: [core] CoCoA and Aggregate Congestion Control [Fwd: New Version Notification for draft-bormann-core-cocoa-04.txt]
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2016 16:13:42 -0000
Dear CoRE WG list members, We submitted revision -04 of draft-bormann-core-cocoa, as you can see below. On Thursday next week, in Berlin, we will present the latest draft updates and results, and will ask for WG adoption of the draft. As the meeting agenda is quite compressed, we would like to achieve some progress already on the list, in particular, regarding Aggregate Congestion Control (ACC). ACC is currently included in the CoCoA draft as an appendix. While CoCoA is intended to be generally applicable, ACC is more interesting on the cloud side, where a single CoAP endpoint may need to talk to thousands of other endpoints and may need to control the burstiness of the resulting aggregate traffic. We would like to ask the WG opinion about which is the best place for ACC: - Is ACC a feature that you would like to see in this draft? - Should ACC be pushed to a new draft? Your comments will be very helpful to make a decision in this regard. Thank you in advance! Cheers, Carles ---------------------------- Original Message ---------------------------- Subject: New Version Notification for draft-bormann-core-cocoa-04.txt From: internet-drafts@ietf.org Date: Fri, July 8, 2016 9:08 pm To: "August Betzler" <august.betzler@entel.upc.edu> "Carsten Bormann" <cabo@tzi.org> "Carles Gomez" <carlesgo@entel.upc.edu> "Dr. Carsten Bormann" <cabo@tzi.org> "Ilker Demirkol" <ilker.demirkol@entel.upc.edu> -------------------------------------------------------------------------- A new version of I-D, draft-bormann-core-cocoa-04.txt has been successfully submitted by Carsten Bormann and posted to the IETF repository. Name: draft-bormann-core-cocoa Revision: 04 Title: CoAP Simple Congestion Control/Advanced Document date: 2016-07-08 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-bormann-core-cocoa-04.txt Status: https://datatracker.ietf.org/doc/draft-bormann-core-cocoa/ Htmlized: https://tools.ietf.org/html/draft-bormann-core-cocoa-04 Diff: https://www.ietf.org/rfcdiff?url2=draft-bormann-core-cocoa-04 Abstract: The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. The CoRE CoAP specification defines basic behavior that exhibits low risk of congestion with minimal implementation requirements. It also leaves room for combining the base specification with advanced congestion control mechanisms with higher performance. This specification defines some simple advanced CoRE Congestion Control mechanisms, Simple CoCoA. It is making use of input from simulations and experiments in real networks. 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. The IETF Secretariat
- [core] CoCoA and Aggregate Congestion Control [Fw… Carles Gomez Montenegro