Re: [nwcrg] Traces for packet losses over SATCOM links

<Tomaso.deCola@dlr.de> Sat, 25 May 2019 01:15 UTC

Return-Path: <Tomaso.deCola@dlr.de>
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 3C50612014F for <nwcrg@ietfa.amsl.com>; Fri, 24 May 2019 18:15:47 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 k4zXVGIAkDze for <nwcrg@ietfa.amsl.com>; Fri, 24 May 2019 18:15:44 -0700 (PDT)
Received: from mailin.dlr.de (mailin.dlr.de [194.94.201.12]) (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 2EF4F120089 for <nwcrg@irtf.org>; Fri, 24 May 2019 18:15:43 -0700 (PDT)
IronPort-SDR: f1MZKMQ/zgGHFcntf5j4iI97u61aUtUStaxM/dmlxsOVhWEyDhOiYUXaCJi0dNVFv6jVxzTSIs c18YtikRU0Lw==
IronPort-PHdr: =?us-ascii?q?9a23=3Auv85UBeJI6QXx27B+x+SADz4lGMj4u6mDksu8p?= =?us-ascii?q?Mizoh2WeGdxcS5ZR7h7PlgxGXEQZ/co6odzbaP6ua5ADNLvczJmUtBWaQEbw?= =?us-ascii?q?UCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYdFR?= =?us-ascii?q?rlKAV6OPn+FJLMgMSrzeCy/IDYbxlViDanbr5+MQi6oR/MusULg4ZuJak8xg?= =?us-ascii?q?XUqXZUZupawn9lK0iOlBjm/Mew+5Bj8yVUu/0/8sNLTLv3caclQ7FGFToqK2?= =?us-ascii?q?866tHluhnFVguP+2ATUn4KnRpSAgjK9w/1U5HsuSbnrOV92S2aPcrrTbAoXD?= =?us-ascii?q?mp8qlmRAP0hCoBKjU09nzchM5tg6JBuB+vpwJxzZPIYI+bN/R+cKHScs8VSm?= =?us-ascii?q?daRMldSylBD5mgY4cTEeYMO/tToYnnp1sJqBuzHQ6hCv3oyj9NnHD2xqo63/?= =?us-ascii?q?48Hg7YwgEgGNYOv27PodroMKcSS/q5w7TWwjjaaf5dxDnz6I/Nch87oPGMW6?= =?us-ascii?q?p9ccvLyUkzGQPJlFKQqZbqPz+N0OQCrXSb4uV7Ve21l24rsQZxoiKgxsoql4?= =?us-ascii?q?LHhZoVx0jZ+Sll2oo5ON61RUFhbdK5HpZdtDuWO5ZrTs86Xm1luSI3xqcYtZ?= =?us-ascii?q?O7cyUG0pQqywTbZvCadYWD/wjtW/yLIThigXJoYLe/hxGv/ke+0uD8Tcy00E?= =?us-ascii?q?pSripCj9nMqmgB1xzN5ciDTftw5kmv1zCB2Q7c6u9KIUc6m6ncJZA73rI8i5?= =?us-ascii?q?UdvkXdEyPsmUX2irOWdl8+9eSy9uvnZq/mqoWBOIBqkg3+M6IuldKjAekgLw?= =?us-ascii?q?QCQ3KX9fm/2bDs50H1XbtHg/4snqXErZzWPcEbqbS4Aw9R3IYj8RG/DzK+3d?= =?us-ascii?q?oGmnkHKUhKeAmAj4TzJl7BPu71DfC7g1u2izpk2vTGPqf7DprQMHfPiK3hcq?= =?us-ascii?q?pl605A1AozyshS6YpVCr4dJ/LzXlX+tMfCAhE8Lgy0w+DnBc5h2YMYR22PGb?= =?us-ascii?q?WVMK3IsVWQ/OIgP/GMZJMJuDb6M/Ul4fDvgmMjmV8SZqSp3IEXaGy2Hvh8JE?= =?us-ascii?q?WZe3Xs0Z89FjJemAs1S+jjkxuhTD5VT320Url66CttW6y8CoKWEryqhbWa22?= =?us-ascii?q?G3E7ZRYmluBlSWV3vlIdbXE8wQYT6fd5cy2gcPUqKsHtcs?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GpAQD/luhc/wuKuApLGh4BBgcGgVI?= =?us-ascii?q?ICwGBDoFaEYEshXKBa5ErhASUehSBZwkBAQEBAQEBAQEgAQ4IAQGBBIIFgTc?= =?us-ascii?q?CgmM1CA4BAwEBBQEBAQEEAQECgQUMgjoigVMsDSY+AgEDAQErQQsQAgEIPwc?= =?us-ascii?q?nCxQRAgQOBYMiAYEdfDamX4N1gVKEZAaBNIRniQKBOAwTgh4uPoJIGQEDGFE?= =?us-ascii?q?+Rj+Cb4ImBIsxhziIJI1ABwKBMocQjHqCH4Zlg1SGYIMNk2mLF4VVAV+BLnF?= =?us-ascii?q?PKgGCQRKLAYU/cgGPGQEB?=
X-IronPort-AV: E=Sophos; i="5.60,509,1549926000"; d="scan'208,217"; a="17781373"
From: <Tomaso.deCola@dlr.de>
To: <Nicolas.Kuhn@cnes.fr>
CC: <nwcrg@irtf.org>
Thread-Topic: [nwcrg] Traces for packet losses over SATCOM links
Thread-Index: AQHVEpdVawIxgkHhj0+IEsvuu7+gqg==
Date: Sat, 25 May 2019 01:15:26 +0000
Message-ID: <9D1022E9-D20F-4EB9-9843-CD8DE1223986@dlr.de>
References: <F3B0A07CFD358240926B78A680E166FF1EBF09CE@TW-MBX-P03.cnesnet.ad.cnes.fr>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1EBF09CE@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_9D1022E9D20F4EB99843CD8DE1223986dlrde_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/ya2bnEYICz2BTim5pWt1QJpsTPc>
Subject: Re: [nwcrg] Traces for packet losses over SATCOM links
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: Sat, 25 May 2019 01:15:47 -0000

Dear Nicolas,

Can you please provide some more details about the traces (i.e. central frequency, speed of the train, link budget, etc.)?

Thank you,

Tomaso

Sent from my iPhone

On 24. May 2019, at 23:38, Kuhn Nicolas <Nicolas.Kuhn@cnes.fr<mailto:Nicolas.Kuhn@cnes.fr>> wrote:

Hi,

We have just released some traces that may find suitable for assessing the performance of your codes.
https://wiki.net4sat.org/doku.php?id=opensand:emulated_satcom_features:physical:attenuation:attenuation_example:index<https://wiki.net4sat..org/doku.php?id=opensand:emulated_satcom_features:physical:attenuation:attenuation_example:index>

In short, the CSV you can find on this page show:
#time (s) #attenuation (dB)
0 0
10 40
20 0

When the attenuation is 0 dB, there are no losses.
When the attenuation is 40 dB, packets are lost.

I hope you find it useful.

Cheers,

Nico

_______________________________________________
nwcrg mailing list
nwcrg@irtf.org<mailto:nwcrg@irtf.org>
https://www.irtf.org/mailman/listinfo/nwcrg