Re: [nwcrg] nwcrg Digest, Vol 52, Issue 4

Janus Heide <janus@steinwurf.com> Tue, 20 February 2018 13:02 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 6CFB6126DEE for <nwcrg@ietfa.amsl.com>; Tue, 20 Feb 2018 05:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=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 TJoRKMWaX_LM for <nwcrg@ietfa.amsl.com>; Tue, 20 Feb 2018 05:02:11 -0800 (PST)
Received: from mailout-taastrup.gigahost.dk (mailout-taastrup.gigahost.dk [46.183.139.199]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308C4127337 for <nwcrg@irtf.org>; Tue, 20 Feb 2018 05:02:10 -0800 (PST)
Received: from mailout.gigahost.dk (mailout.gigahost.dk [89.186.169.112]) by mailout-taastrup.gigahost.dk (Postfix) with ESMTP id 749EB84221D for <nwcrg@irtf.org>; Tue, 20 Feb 2018 13:02:08 +0000 (UTC)
Received: from smtp.gigahost.dk (smtp.gigahost.dk [89.186.169.109]) by mailout.gigahost.dk (Postfix) with ESMTP id 67F5078369B for <nwcrg@irtf.org>; Tue, 20 Feb 2018 13:02:08 +0000 (UTC)
Received: by smtp.gigahost.dk (Postfix, from userid 1000) id 5B8802721CDA; Tue, 20 Feb 2018 13:02:08 +0000 (UTC)
X-Screener-Id: f78902a975ab56d2526c14ad5d4a0b3a5e5edf24
Received: from [10.10.138.128] (unknown [77.243.62.138]) by smtp.gigahost.dk (Postfix) with ESMTPSA id 337472721CD8 for <nwcrg@irtf.org>; Tue, 20 Feb 2018 13:02:08 +0000 (UTC)
To: nwcrg@irtf.org
References: <mailman.30.1518379206.16674.nwcrg@irtf.org>
From: Janus Heide <janus@steinwurf.com>
Message-ID: <e1dfc9a7-458f-e21a-2731-13f99e6c7d00@steinwurf.com>
Date: Tue, 20 Feb 2018 14:02:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <mailman.30.1518379206.16674.nwcrg@irtf.org>
Content-Type: multipart/alternative; boundary="------------5A9FC4C198DAD713E8CE3818"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/mYZcheB-iIAdNo5FaZ9bCR9INbk>
Subject: Re: [nwcrg] nwcrg Digest, Vol 52, Issue 4
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 13:02:13 -0000

Samah,

Thanks for providing suggestions/comments, let me comment / ask a few 
clarifying questions for my understanding.

1. Are there any place in particular in the document where you think 
using those terms would make for a clearer/better read?

3. I am not sure I understand what codes you would like to mix, so it is 
difficult for me to ascertain whether that is or could be support by. 
Could you maybe give an example so we can consider if and how to allow 
for potentially additional flexibility? Thanks.

4. An additional representation type alongside the two that are in the 
document could be added, so far we have not had the use for this feature 
and therefore not added it. Maybe a good approach would be to describe 
such a representation in a new RFC as an extension of the submitted RFC?

Best Janus

On 02/11/18 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. Re: Fwd: New Version Notification for
>        draft-heide-nwcrg-rlnc-00.txt (samah.ghanem@gmail.com)
>
>
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg