Re: [EToSat] about LOOPS(Localized Optimization of Path Segments) and etosat

Marie-Jose Montpetit <marie@mjmontpetit.com> Thu, 03 January 2019 18:25 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: etosat@ietfa.amsl.com
Delivered-To: etosat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBD613122F for <etosat@ietfa.amsl.com>; Thu, 3 Jan 2019 10:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 xnsPwFyTY7lr for <etosat@ietfa.amsl.com>; Thu, 3 Jan 2019 10:25:58 -0800 (PST)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 10502131231 for <etosat@ietf.org>; Thu, 3 Jan 2019 10:25:57 -0800 (PST)
Received: by mail-qt1-x833.google.com with SMTP id v11so37884618qtc.2 for <etosat@ietf.org>; Thu, 03 Jan 2019 10:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=GEIXOf5MAbS2t+Xmtzv3rYcI9WKCaM17dP1aLdiOWjA=; b=TRPR8On8D+3njUl9jTt69LAtGmGgiX0uG7CoUuxHqRUYS2r1qQiO95XkftMKUffgdq 07Yafpr3Ur164WwGuSCPZupraBSBFTw7ALW+6JJUehv9IiPpenOxmDP5W+u00EsOkyI5 nkX4lH3kFzZveYvlUXQuEgTaTkeUneiSD2zSOqUHNlf/Qdd+QrdlM7wWN86vJ/0Yiygn t12Sr/4XSeqHcYZ/nifbTISK7scrE3Ow44gcy/ypyQTlQ3D/MsouqOJz1TBX1K4Cv6jo agWxrrGESfK5DswlXFQ4zVO2VMAlk6lcHmiID0OrtSSrLHnBQhgklgwvZiTugpaBir5m Qoig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=GEIXOf5MAbS2t+Xmtzv3rYcI9WKCaM17dP1aLdiOWjA=; b=UFqe391O/tqo9Bx+4nIAbXhkMOgaSLgvN0s9YO1ijWLW/+VZDjvi6+rwT5OvEj4rAp utgm3VAwUWeK0fvt386cm/WBz8qaUxNSoBqnp4J8Kqt8GQyLWt4rocO4La3L8SY8UI/e 2HtpRd5HiQGeN0uFTFwpuEWWiEq5+7g3lOcOfZ+Wp9mEPpMYN+qrtiw99Y2f3gztUgDA Cwk7xxfJwYbxuGr+Eecn5ce9GRtSqODxqf5ipurlNTu5YYFxB/JxUHmxo8l69G2W/wvU 2xvQ3g8Qcf5/el9po3QV+hpPFj1iDNeGZgQhiqT4rjofbGZMjPIpnpskV5qtVgWUXFry yoEg==
X-Gm-Message-State: AA+aEWaHjPQb1eRp53r9UsWmNs/f98okDUvHCfL37v3oxtif0TuyKuV6 uMbhLKCwmljk8R07x2Bcom5tNw==
X-Google-Smtp-Source: ALg8bN6klmw9GeemqXm3/uqi/Xsy8f0n8vD+KoFvKUISVfDR8MkFI+UG+Cmm60GyYp3E2Ety9rDJIA==
X-Received: by 2002:aed:3968:: with SMTP id l95mr47709772qte.344.1546539956907; Thu, 03 Jan 2019 10:25:56 -0800 (PST)
Received: from heidi-lamarr.fios-router.home (pool-173-76-235-112.bstnma.fios.verizon.net. [173.76.235.112]) by smtp.gmail.com with ESMTPSA id u50sm30266828qta.23.2019.01.03.10.25.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Jan 2019 10:25:55 -0800 (PST)
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
Message-Id: <0BEDC18F-3AAA-49BE-9AC8-4ED332625CC5@mjmontpetit.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD6B1692-3C3E-4748-8FA9-983F0C97A184"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 03 Jan 2019 13:25:54 -0500
In-Reply-To: <BL0PR11MB3394C0EE1249C918BC33448C908D0@BL0PR11MB3394.namprd11.prod.outlook.com>
Cc: Carsten Bormann <cabo@tzi.org>, Liyizhou <liyizhou@huawei.com>, "etosat@ietf.org" <etosat@ietf.org>
To: "Border, John" <John.Border@hughes.com>
References: <D408889639FC5E4FADB4E00A3E01FA8FA6D64374@nkgeml513-mbs.china.huawei.com> <BL0PR11MB33944EB404AA6A1E8DABBBD490A80@BL0PR11MB3394.namprd11.prod.outlook.com> <BL0PR11MB33940058189CAC345C51C2C090A80@BL0PR11MB3394.namprd11.prod.outlook.com> <D408889639FC5E4FADB4E00A3E01FA8FA6D64D4D@nkgeml513-mbs.china.huawei.com> <205ADE17-7C94-4AF5-B2F3-87613C6E41DE@tzi.org> <BL0PR11MB3394C0EE1249C918BC33448C908D0@BL0PR11MB3394.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/ec4lbWT6eTMPSNgBK7PVxIB2SQ4>
X-Mailman-Approved-At: Thu, 03 Jan 2019 11:46:36 -0800
Subject: Re: [EToSat] about LOOPS(Localized Optimization of Path Segments) and etosat
X-BeenThere: etosat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The EToSat list is a non-WG mailing list used to discuss performance implications of running encrypted transports such as QUIC over satellite." <etosat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/etosat>, <mailto:etosat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/etosat/>
List-Post: <mailto:etosat@ietf.org>
List-Help: <mailto:etosat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/etosat>, <mailto:etosat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2019 18:26:00 -0000

The files also refer to the nwcrg on-going work. It is a common practice to run coded (FEC) sessions over tunnels to isolate the effects of coding across paths. And we have work on nw coding over satellite also. Would this group be open for me to send this thread over to our list?

Also in the COIN proposed RG we are also looking at per hop optimization but in the context of in-network computing (and that includes FEC, transcoding, pre-fetching, data decompostion etc.) which I can see are also related. So I could copy there too.

Thanks for copying me.

mjm


Marie-Jose Montpetit, Ph.D.
mariejo@mit.edu
marie@mjmontpetit.com
+1-781-526-2661
@SocialTVMIT



> On Jan 3, 2019, at 12:48 PM, Border, John <John.Border@hughes.com> wrote:
> 
> 
> 
> Clearly LOOPS should not focus only on satellite.  But, I think LOOPS is directly relevant to ETOSAT.  Techniques like LOOPS are likely to be a key part of the solution to the performance over satellite problem.
> 
> I will be sending out an email to ETOSAT in the next couple of days to try to kickstart discussion overall.
> 
> 
> John
> 
> 
> 
> -----Original Message-----
> From: Carsten Bormann <cabo@tzi.org> 
> Sent: Friday, December 07, 2018 5:59 PM
> To: Border, John <John.Border@hughes.com>
> Cc: Liyizhou <liyizhou@huawei.com>
> Subject: Re: about LOOPS(Localized Optimization of Path Segments) and etosat
> 
> WARNING: The sender of this email could not be validated and may not match the person in the "From" field.
> 
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
> WARNING: The sender of this email could not be validated and may not match the person in the "From" field.
> 
> Hi John,
> 
>> On Dec 7, 2018, at 10:37, Liyizhou <liyizhou@huawei.com> wrote:
>> 
>> I copied to Carsten who was leading the side meeting. He might provide more information.
> 
> As Yizhou said, there are no formal minutes of this side meeting, but I did record my impressions in the attached short summary.  I have also attached the slides that we used, as the summary may not be comprehensible without those.
> 
> Given that Spencer specifically asked us to discuss this in the context of etosat, it would certainly help to know what the intentions were in creating this list and to speculate a bit how a potential etosat activity might cross-pollinate with LOOPS.
> 
> Grüße, Carsten
> <Summary of the IETF103 LOOPS side meeting, 2018-11-06.pdf><LOOPS.pdf>