Re: [nwcrg] nwcrg @ ietf106 minutes

"" <> Tue, 26 November 2019 00:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 019B3120FCC for <>; Mon, 25 Nov 2019 16:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id B1GAbpTRW4bT for <>; Mon, 25 Nov 2019 16:43:05 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 78AB91200CE for <>; Mon, 25 Nov 2019 16:43:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s2048; t=1574728981; bh=+RiyMBduziQdGSWAwal9w4KYlIgVQVOrsi4EJvInHBg=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From:Subject; b=NPnZjwiooXKOh7FT7VgaJHCETnxFboedM5fg+k6Wb2lw/IrTzqD366AL+Vjx3aPSbnrpFOrQcO9aAPnaFgy1nzIS8iJZnztogwTJZHapaeCqnPCKdlCDLIDNANjTGl7HK7BHqBnZN5EeDsTpu9Pn++wIcWvViuIQ/ywuKSzxOrpPDf4mXpqkJUMfIbyUfBRbALC263smCEcr0gkfDzv2pOa+PAiWrJRTmGC2G3wNHS28A+5RBSqKZ7Oty5h33Cv8+JSXOD3rwzMyEk3aVSJUZzxFtc/3d2Vx3jakify8m9C1/+t6MTajOa+SN3XffahUsYUMhbY/P02TZR/mTY+NYw==
X-YMail-OSG: STMtHZ4VM1ngBgox5fCajIolwpgfu1leM.kB6q4sBOXIltWAy0FHGSP7_aCtVxl NluhMaSTsTSY017by4cBg8pvx3BiIbslpPhmG.BxwW.l3I.UHSelA63YtCZ.ullZWxp_3bGlKR5f ngAGOwFwU8qQb2Sjx_8SJRNR44PExbEyQd6Awhrwjpbzbw_pOL44IieVVrWgNbRK9r9n2GAKTMRK wwiJro9UcUUCuAnhZHLP0mQv0aXh7RyMePwa8wJ9fMi2EGEpO8PKrCRk_TSEqUVScCF38JKtc.oe 0ClcdaIXfMaqxzMTGi19THvB2L_T7R9fP1ppWbJMtbN1QkzpaEOpVHMis5UQuIM9RMuYE96zjs1e WU8K.Tqbk5O3RygXSroDIFRDngMQJV_aXs3o9Wba24Hm409Zwk1CnwQ1H8unKIdRFCdEZTN91CXv TTgACoc3xXGxBskuLNxVq_T4Zz6YPH0ab.fsTvE6_jtPevuMK8til6Pfxqrb1wIc3wPk1Kp0amQj yNbE.3E8SbbQy4k5xHuNlUwJ6OQPkeQpNDKyKOkkp38g5cJEpVZTh3yMmd2Oh4LYl5XpeW6K50Rl .TuGkM9hDztuJpQgvJVy0A._YrNISqXAmc1LH_L19vbYV01b.Vj0O4ia.haTi6Ky7KkV8COpOTHO jTcKMDeYofaR4mM8rX27ALzYZVJ4C57ZsPxnP6igOAVe5uq65txRm1._q7SRDKKoSKIy7ajthsEw PlyFYLqbSLpsHPkZibebBRpee6JL44hVIkoWr0AWRxNN44cU7RsuYYrOcP40UUu8gfOd0Gkbtq2G 7x_H6yHNMGr6P7vbUiPSOw7BbFPaoSqSqu3.eRVU3LO4fdU.krANsEkCt73C4IFYNttX6AFQiSNH Hw7uqnzemWb.CWigHYyhfGGSUcy9Xlrgw48irVcHdNXhpzjo6B7pSPl4Gsb7GCj539KitlYU3Tt6 AsnmT4ao9nmZ163cpD4b0n2xphm7gyXSN0ArdxYeZ4DG0qHWQkcF8zylHRXz0830uuw6fpIANQix Qmn9cvJKHtHnbXSpIwhRdlL59nQGaDPQcr03SIDoZQaOl72kPSa01JIJM._vzfbeyHhaYW7S6mmT ibTpH6ESpCfJYolNy6pqvcwHZ_IwxtkMR1JikozAlVzNERUazZFw72GbPi64pVkiwPNp_JtGasPa P1RcN2ncJ5k2XJIgX2bkWSBM6PCeeBxySSh9jbxmOHxZnRvX6xlfcN1ixg4aWj_su3SKYFI6.L5A 3JtX1If5qCZlSAkkHeOuqIVNjcmeB4Rtf65DCXS3Sg1G5vuZT1HENl8lqhnhMxMpcsnZ3R0DOaoL KSwKqDkmVhT42uW4IUZ2Q7kwCWU7mJG4gYjDYnOdHkq4K
Received: from by with HTTP; Tue, 26 Nov 2019 00:43:01 +0000
Date: Tue, 26 Nov 2019 00:42:56 +0000 (UTC)
From: "" <>
To:, Vincent Roca <>
Cc: Marie-Jose Montpetit <>
Message-ID: <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_38470_1747561566.1574728976549"
X-Mailer: WebService/1.1.14822 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Archived-At: <>
Subject: Re: [nwcrg] nwcrg @ ietf106 minutes
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 26 Nov 2019 00:43:07 -0000

> All the comments from Lloyd Wood and Vincent Roca have been answered
> (see details in github I-D repository for Lloyd’s comments).

Well, this is news to me. If something is brought up on the list,
I'd expect it to be answered on the list, as the primary place
where work is discussed. Where is this? Thanks.

> Some satellite vocabulary (satellite "payload" and "FECFRAME"
> in the satellite context) may create confusion at IETF and these
> terms have been removed.
I can see satellite payload/packet vs frame payload causingconfusion if no context is provided, and there is little needto refer to the satellite platform/payload distinction when everythingis going through the communications payload. However, there is aglossary in the draft where the term and its use can be explicitlycalled out. A glossary is to clear up confusion about vocabulary;that is why it is there.

FECFRAME is integral to DVB-S and S2, which the draft relieson heavily. That an IETF group chose the same name, what, adecade later is merely a coincidence. And there is a glossaryin the draft where the term and its use(s) can be explicitly calledout.

Really, discussing DVB-S without not even saying why you'renot addressing the key FECFRAME component of DVB-S isinsufficient, or not clarifying error correction vs erasurecorrection in some detail particularly where terminology (FEC)overlaps, is not enough in my view.

noted on the draft:

   Physical and link layers coding protection is
   usually sufficient to guarranty Quasi-Error Free, with a negligeableshould be
Physical- and link-layer coding protection are usuallysufficient to guarantee Quasi-Error-Free communications,with a negligible...

Please run a spellcheck before asking for anotherlast call.

thanks and regards

Lloyd Wood 

    On Tuesday, 26 November 2019, 01:08:12 GMT+11, Vincent Roca <> wrote:  
 Dear all,

We have uploaded the preliminary meeting minutes in the datatracker:
Please tell us if you have comments.

NB: you will also find them in the github repository in IMHO a more readable format
    along with all the slides presented:

We’d like to warmly thank Nicolas, Cédric and Oumaima for taking notes.


 Marie-Jose and Vincent

nwcrg mailing list