Re: [Maprg] [EToSat] [IETF112] Recommendations on using VPN over SATCOM

Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com> Sun, 14 November 2021 15:38 UTC

Return-Path: <nicolas.kuhn.ietf@gmail.com>
X-Original-To: maprg@ietfa.amsl.com
Delivered-To: maprg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC5A33A0C4E for <maprg@ietfa.amsl.com>; Sun, 14 Nov 2021 07:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aZ1dlr4Mw_vj for <maprg@ietfa.amsl.com>; Sun, 14 Nov 2021 07:38:36 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC573A0C4C for <maprg@irtf.org>; Sun, 14 Nov 2021 07:38:35 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id i9so14173992qki.3 for <maprg@irtf.org>; Sun, 14 Nov 2021 07:38:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/tD7Q1Lkp4nSRfZPnYvTK4krLkNNA758B9nFH91CSsI=; b=cQq9WF/GhmlSkCsn+Umwt1G/zIA7yx7PbxtiJlPbD4jnYTEWDLpV/YZ/iP/QSPdLWi 7ONMBlXnFUKAcZkKgxXU2Vb/9FEZpGe0JjXC1apABPUNmgiT6Cio19hs9WAd0iVzKhrm k4hGccc1MNH6yq3QFUx4l/kXsEOReBF9/WqIQPrORzrznUOm7arxhnlWdhug9cHeQ3IM mJCE2g4pVe9dZLVlzhcFflGQj22nSKndIaB9wjgxSqJPze2CJN80LLKOstAF4CxvHYf1 nd0NlHVaQCiDyfBk6G8avHNfrXa8OX8BPRjpKKH3FN6xaRzMKzbtVqh+VJGeX2WaWBuk byWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/tD7Q1Lkp4nSRfZPnYvTK4krLkNNA758B9nFH91CSsI=; b=uIkmQQQ2Eq4QcBOEYcFQSTppYbYDZ3srEWp4TYIj8VMbJ4s5wzuWOUGY4Gb0BD+e6b bjVm1+P4Dkri0VtuJNUWJQ601M75KfQdNZFuxkwgzPOYbOntSIXs97ji4xlXktI5V0Ze rx1pUlOXDR7TQB+5lUhMlgvtsHX/cLlJUskUmsdEl31yPbP1d38AGyLb3CaMWzVBZUUl kPLKSCBmaL+c2Y82t17clmDtongYzIwDCj0cM6FZDmT5DbFMZUm7+7pXMUixza3YUkvt R2Vl7+F1dF27Iw+rlr5WE7s15gatsy4AG136dzlnz1Xh5nUhlLT4U7Rwyz9VxnXwk6EG XA1g==
X-Gm-Message-State: AOAM5309ZgasCjhtVY9R3dWFJcHVCUiwEKN0f42If6twV8QtH+PZPXb/ GFmLrge+nuUAuFt+BxNEjlAljsnKk//kf3AMfRw=
X-Google-Smtp-Source: ABdhPJwH7Ph9IVJP7qItx2YPMISt7EvvObFza8N2J5ENsQrOUA0vl77NrVxCYngtVv+2Nok3dE9YjeR0cUFdAc/ev5w=
X-Received: by 2002:a37:a617:: with SMTP id p23mr25085341qke.466.1636904314555; Sun, 14 Nov 2021 07:38:34 -0800 (PST)
MIME-Version: 1.0
References: <CAL0D2oRNxS1Qid153Ead5Ntk-BdRJLnN1OdZhPiyQQHK+0NTjQ@mail.gmail.com> <f274aa24-48fb-00df-9ea6-e44720a6254b@fau.de>
In-Reply-To: <f274aa24-48fb-00df-9ea6-e44720a6254b@fau.de>
From: Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>
Date: Sun, 14 Nov 2021 16:38:23 +0100
Message-ID: <CAL0D2oSx681sCHOfpUudYyGhoD89qUDq4criG4kfnDAudLHtAA@mail.gmail.com>
To: Joerg Deutschmann <joerg.deutschmann@fau.de>
Cc: maprg@irtf.org, etosat@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003350d205d0c17c3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/maprg/R7wqusfXwIwr-bhCVAbUc4hF3N4>
Subject: Re: [Maprg] [EToSat] [IETF112] Recommendations on using VPN over SATCOM
X-BeenThere: maprg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Measurement and Analysis for Protocols \(MAP\) \(Proposed\) RG mailing list" <maprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/maprg>, <mailto:maprg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/maprg/>
List-Post: <mailto:maprg@irtf.org>
List-Help: <mailto:maprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/maprg>, <mailto:maprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Nov 2021 15:38:42 -0000

Hello everyone,

Thanks for the pointer, Joerg !

More inline.

On Wed, Nov 10, 2021 at 10:06 PM Joerg Deutschmann <joerg.deutschmann@fau.de>
wrote:

> Dear Nicolas,
>
> thanks a lot! We did similar measurements earlier this year considering
> - no VPN, OpenVPN (UDP only), Wireguard
> - single/multiple TCP flows
> - different applications
> - different access technologies and operators (4x GEO, LEO Starlink,
> LTE, DSL)
>
> The results are available here:
>
> https://www.cs7.tf.fau.eu/research/quality-of-service/qos-research-projects/sat-internet-performance/
> Executive summary and presentation is available in English language;
> unfortunately the full report is only available in German language right
> now, but I'll translate it upon request.
>
> One comment and a few questions:
> - In order to see how close the performance comes to the bottleneck link
> rate, I've calculated corresponding goodput values in this spreadsheet:
>
> https://docs.google.com/spreadsheets/d/12OUg6B60X9OA3WS8XvWrdFj5Ln6CJAV38k6DWviIg6k/edit?usp=sharing
> - Which PEP did you use, was it PEPsal?
>
[NK] Yes

> - What is the motivation of testing different CCs on the end hosts and
> on the PEP (Section IV-A)? Unless there are delays and/or packet losses
> on the local network and/or Enterprise network, I'd assume that the
> performance is determined by the satellite link (and the
> local/enterprise network has negligible performance impact)?
>
[NK] There are some cases of deployments where the operator / box provider
can tune the CC.
As a result, there were discussions on whether using BBR was performing
better than CUBIC.
This is the main motivation.

> - The poor performance of "Loss LEO" with CUBIC is a bit surprising to
> me. Which loss rate and which "variable RTT" was used? In our VPN
> measurements, the Starlink LEO megaconstellation performed quite well
> despite some packet loss.
>
[NK] The RTT was around 60ms but most importantly the loss rate was 1%.
This huge packet loss may be the reason for the poor performance of CUBIC.

>
> Thanks and best regards,
> Joerg
>
>
> On 09.11.21 09:56, Nicolas Kuhn wrote:
> > Dear MAPRG, ETOSAT,
> >
> > Later today, we will present some results on exploring the mixed usage
> > of VPN and congestion controls over emulated SATCOM systems.
> >
> > We have published a short technical report on the topic :
> > https://arxiv.org/pdf/2111.04586.pdf <
> https://arxiv.org/pdf/2111.04586.pdf>
> >
> > See you later,
> > Kind regards,
> >
> > Nicolas - on the behalf of my co-authors
>