[tsvwg] Fwd: Re: New Version Notification for draft-jones-tsvwg-transport-for-satellite-00.txt
Tom Jones <tom@erg.abdn.ac.uk> Mon, 22 February 2021 18:18 UTC
Return-Path: <tom@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAB63A223F for <tsvwg@ietfa.amsl.com>; Mon, 22 Feb 2021 10:18:39 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 eWdiRGLtL5TQ for <tsvwg@ietfa.amsl.com>; Mon, 22 Feb 2021 10:18:36 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB6C3A1F9F for <tsvwg@ietf.org>; Mon, 22 Feb 2021 10:17:31 -0800 (PST)
Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 04D321B00257 for <tsvwg@ietf.org>; Mon, 22 Feb 2021 18:17:29 +0000 (GMT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id F2F4F27C0054 for <tsvwg@ietf.org>; Mon, 22 Feb 2021 13:17:28 -0500 (EST)
Received: from imap38 ([10.202.2.88]) by compute3.internal (MEProxy); Mon, 22 Feb 2021 13:17:28 -0500
X-ME-Sender: <xms:OPUzYFxSL55N6WzUoP0bEdDzPhQyUPRzwYVymtSr47IV98JIVICCQw> <xme:OPUzYFTV6trglP9p19oR4N2vVXKc9tEXp4WTZEon2NdSc-41w_LSx0ljeFVa9ZmEd n0hzWYjtXWY_nLpqQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeefgdduuddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd erreejnecuhfhrohhmpedfvfhomhculfhonhgvshdfuceothhomhesvghrghdrrggsughn rdgrtgdruhhkqeenucggtffrrghtthgvrhhnpeehvdetfffhuddtgfdvgffgleeikeeuke fgtddvffdtjeeivdektdfgheelgeejteenucffohhmrghinhepihgvthhfrdhorhhgpdhg ihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsohhmvgdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqgeeh geehtddujedtqdduheehgedvgeehkedqthhomheppegvrhhgrdgrsggunhdrrggtrdhukh esfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:OPUzYPWkdqrGxzMEYWTsNfH3HKNV5z0OPFqjn6usvrN9o3wjlSsQCA> <xmx:OPUzYHjGd_kqkpuVJDgki--nTFW2pc9LePYViL69zXrUIPriwsyS7g> <xmx:OPUzYHAVMxfVvVbdYFlG5uzuddVIQTN5NIl1LOZ0TBhk1iWL9ejIiQ> <xmx:OPUzYKMs3V8GyCCx5WC9i4K4L7muoR9LmrgGvXU0_UhgwuKImhtyUQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6AF14CA005D; Mon, 22 Feb 2021 13:17:28 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
x-forwarded-message-id: <20210222172029.GD98769@tom-desk.erg.abdn.ac.uk>
Message-Id: <cfed8de0-05af-410f-83ec-e401a5ee8d49@www.fastmail.com>
Date: Mon, 22 Feb 2021 18:17:06 +0000
From: Tom Jones <tom@erg.abdn.ac.uk>
To: tsvwg@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XXk7ZJEMud3w95y2tCSXE42OLT0>
Subject: [tsvwg] Fwd: Re: New Version Notification for draft-jones-tsvwg-transport-for-satellite-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 18:18:44 -0000
----- Original message ----- From: Tom Jones <tom@erg.abdn.ac.uk> Cc: Emile Stephan <emile.stephan@orange.com>, Godred Fairhurst <gorry@erg.abdn.ac.uk>, John Border <border@hns.com>, Nicolas Kuhn <nicolas.kuhn@cnes.fr> Subject: Re: New Version Notification for draft-jones-tsvwg-transport-for-satellite-00.txt Date: Monday, February 22, 2021 17:20 On Mon, Feb 22, 2021 at 09:11:46AM -0800, internet-drafts@ietf.org wrote: > > A new version of I-D, draft-jones-tsvwg-transport-for-satellite-00.txt > has been successfully submitted by Tom Jones and posted to the > IETF repository. > > Name: draft-jones-tsvwg-transport-for-satellite > Revision: 00 > Title: Enhancing Transport Protocols over Satellite Networks > Document date: 2021-02-22 > Group: Individual Submission > Pages: 27 > URL: https://www.ietf.org/archive/id/draft-jones-tsvwg-transport-for-satellite-00.txt > Status: https://datatracker.ietf.org/doc/draft-jones-tsvwg-transport-for-satellite/ > Html: https://www.ietf.org/archive/id/draft-jones-tsvwg-transport-for-satellite-00.html > Htmlized: https://tools.ietf.org/html/draft-jones-tsvwg-transport-for-satellite-00 > > > Abstract: > IETF transport protocols such as TCP, SCTP and QUIC are designed to > function correctly over any network path. This includes networks > paths that utilise a satellite link or network. While transport > protocols function, the characteristics of satellite networks can > impact performance when using the defaults in standard mechanisms, > due to the specific characteristics of these paths. > > RFC 2488 and RFC 3135 describe mechanisms that enable TCP to more > effectively utilize the available capacity of a network path that > includes a satellite system. Since publication, both application and > transport layers and satellite systems have evolved. Indeed, the > development of encrypted protocols such as QUIC challenges currently > deployed solutions, for satellite systems the capacity has increased > and commercial systems are now available that use a range of > satellite orbital positions. > > This document describes the current characterises of common satellite > paths and describes considerations when implementing and deploying > reliable transport protocols that are intended to work efficiently > over paths that include a satellite system. It discusses available > network mitigations and offers advice to designers of protocols and > operators of satellite networks. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > Hello TSVWG, We have published a new document on transport protocol considerations in satellite networks and we would love to hear comments from the working group. This document is an expansion of the work in draft-kuhn-quic-4-sat by Nicolas, Emile, John and Gorry. Our intention with this document is to increase the scope of the protocols to consider transports more generally from just quic in quic-4-sat. We see this as a logical update of RFC 2488 (and to some extent RFC 2760) to include advancements in both transport protocol design and satellite networks. We look forward to hearing any feedback the working group has on this document and any contributions you might be able to make to fill out some of the thinner sections. We are happy to take comments on this mailing list, directly by email or as pull requests or issues on the documents github repository. https://github.com/uoaerg/draft-jones-transport-for-satellite - Tom