Re: [nwcrg] nwcrg Digest, Vol 69, Issue 6

Janus Heide <janus@steinwurf.com> Mon, 29 July 2019 10:50 UTC

Return-Path: <janus@steinwurf.com>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89391200FF for <nwcrg@ietfa.amsl.com>; Mon, 29 Jul 2019 03:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 VlW7A8uDe9an for <nwcrg@ietfa.amsl.com>; Mon, 29 Jul 2019 03:50:25 -0700 (PDT)
Received: from mailout-taastrup.gigahost.dk (mailout-taastrup.gigahost.dk [46.183.139.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36762120018 for <nwcrg@irtf.org>; Mon, 29 Jul 2019 03:50:24 -0700 (PDT)
Received: from mailout.gigahost.dk (mailout.gigahost.dk [89.186.169.112]) by mailout-taastrup.gigahost.dk (Postfix) with ESMTP id 1AD7F189271B for <nwcrg@irtf.org>; Mon, 29 Jul 2019 10:50:13 +0000 (UTC)
Received: from smtp.gigahost.dk (smtp.gigahost.dk [89.186.169.109]) by mailout.gigahost.dk (Postfix) with ESMTP id 2FCE6782B5A for <nwcrg@irtf.org>; Mon, 29 Jul 2019 10:50:22 +0000 (UTC)
Received: by smtp.gigahost.dk (Postfix, from userid 1000) id E2F392721A9A; Mon, 29 Jul 2019 10:50:12 +0000 (UTC)
X-Screener-Id: f78902a975ab56d2526c14ad5d4a0b3a5e5edf24
Received: from [192.168.1.127] (ip-5-186-112-232.cgn.fibianet.dk [5.186.112.232]) by smtp.gigahost.dk (Postfix) with ESMTPSA id B8A312721AC1 for <nwcrg@irtf.org>; Mon, 29 Jul 2019 10:50:12 +0000 (UTC)
To: nwcrg@irtf.org
References: <mailman.70.1562871613.13006.nwcrg@irtf.org>
From: Janus Heide <janus@steinwurf.com>
Message-ID: <93fbbce0-0ee8-4ea9-696a-90908aaba637@steinwurf.com>
Date: Mon, 29 Jul 2019 12:50:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <mailman.70.1562871613.13006.nwcrg@irtf.org>
Content-Type: multipart/alternative; boundary="------------9DF78831D1E68423E3D27734"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/lJTvj0haZ4JFK7z7ff34rmrmGjY>
Subject: Re: [nwcrg] nwcrg Digest, Vol 69, Issue 6
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2019 10:50:28 -0000

Hi Salvatore,

Good question.

Let me expand a bit on that from memory. We where working with a use 
case where we identified a symbols size of approximately 100 bytes and a 
total packet size from 1200 bytes and down. From these parameters, up to 
15 symbols permitted the sufficient flexibility in terms of packet size 
e.g. allowing for packets of sizes 100, 200, ..., 1500 bytes (of 
variable packet size) to be changed on the fly.

Of course for some other application this choice might be to limiting, 
but in this case it is possible to include multiple representations into 
a single packet. This would come at the cost of additional overhead (if 
you include 2 representations you get twice the overhead) but to be fair 
I think it will be quiet uncommon to go beyond a few symbols per packet. 
Coupled with the fact that allocating more than 4 bytes would start to 
be problematic for other fields this seemed a good trade-off.

If you can come up with some use cases where this choice would pose a 
problem, I would be interested to know it.

Best Janus

On 11.07.2019 21.00, nwcrg-request@irtf.org wrote:
> Send nwcrg mailing list submissions to
> 	nwcrg@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.irtf.org/mailman/listinfo/nwcrg
> or, via email, send a message with subject or body 'help' to
> 	nwcrg-request@irtf.org
>
> You can reach the person managing the list at
> 	nwcrg-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of nwcrg digest..."
>
> Today's Topics:
>
>     1. about the symbols field in draft-heide-nwcrg-rlnc-02
>        (Salvatore Signorello)
>     2. Symbol representation draft updated (Janus Heide)
>
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg