[icnrg] Fwd: I-D Action: draft-oran-icnrg-flowbalance-02.txt

"David R. Oran" <daveoran@orandom.net> Mon, 03 February 2020 16:44 UTC

Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D238120B4C for <icnrg@ietfa.amsl.com>; Mon, 3 Feb 2020 08:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 u7DbeSG5tzWZ for <icnrg@ietfa.amsl.com>; Mon, 3 Feb 2020 08:44:45 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66DCA120B61 for <icnrg@irtf.org>; Mon, 3 Feb 2020 08:44:32 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:f5cc:3b5a:8c50:b1e3]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 013GiOHG018653 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Mon, 3 Feb 2020 08:44:26 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Mon, 03 Feb 2020 11:44:19 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <982C793A-D96B-424D-83C5-69564027461A@orandom.net>
References: <158074807780.28637.13088164580374058154@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/i00GSUzzThMQVVv_YUq4Ygcjfcg>
Subject: [icnrg] Fwd: I-D Action: draft-oran-icnrg-flowbalance-02.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2020 16:44:56 -0000

This is a simple refresh with just a conversion to V3 of the xml2rfc 
grammar and a few cosmetics.

As noted in the earlier message form the chairs, this has not gotten any 
review yet, so that author would very much appreciate review by ICNRG 
participants.

Thanks!

DaveO

Forwarded message:

> From: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-oran-icnrg-flowbalance-02.txt
> Date: Mon, 03 Feb 2020 08:41:17 -0800
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>
>
>         Title           : Maintaining CCNx or NDN flow balance with 
> highly variable data object sizes
>         Author          : Dave Oran
> 	Filename        : draft-oran-icnrg-flowbalance-02.txt
> 	Pages           : 15
> 	Date            : 2020-02-03
>
> Abstract:
>    Deeply embedded in some ICN architectures, especially Named Data
>    Networking (NDN) and Content-Centric Networking (CCNx) is the 
> notion
>    of flow balance.  This captures the idea that there is a one-to-one
>    correspondence between requests for data, carried in Interest
>    messages, and the responses with the requested data object, carried
>    in Data messages.  This has a number of highly beneficial 
> properties
>    for flow and congestion control in networks, as well as some
>    desirable security properties.  For example, neither legitimate 
> users
>    nor attackers are able to inject large amounts of un-requested data
>    into the network.
>
>    Existing congestion control approaches however cannot deal
>    effectively with a widely varying MTU of ICN data messages, since 
> the
>    protocols allow a dynamic range of 1-64K bytes.  Since Interest
>    messages are used to allocate the reverse link bandwidth for
>    returning Data, there is large uncertainty in how to allocate that
>    bandwidth.  Unfortunately, current congestion control schemes in 
> CCNx
>    and NDN only count Interest messages and have no idea how much data
>    is involved that could congest the inverse link.  This document
>    proposes a method to maintain flow balance by accommodating the 
> wide
>    dynamic range in Data message MTU.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-oran-icnrg-flowbalance/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-oran-icnrg-flowbalance-02
> https://datatracker.ietf.org/doc/html/draft-oran-icnrg-flowbalance-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-oran-icnrg-flowbalance-02
>
>
> 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/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt