NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98
Aaron Falk <firstname.lastname@example.org>
Transport Area Director(s):
Scott Bradner <email@example.com>
Vern Paxson <firstname.lastname@example.org>
Transport Area Advisor:
Vern Paxson <email@example.com>
To Subscribe: firstname.lastname@example.org
In Body: subscribe tcpsat your_email_address
Description of Working Group:
Satellites are being used to extend the Global Internet geographically and will be more ubiquitous in the next decade with the deployment of several proposed services capable of providing greater than T1 access to individual users anywhere in the world.
Yet, satellite links have a unique combination of characteristics that can affect the throughput of TCP traffic. Because of the high-bandwidth delay product, slow start and congestion control algorithms behave much differently when the path includes a satellite link than exclusively terrestrial ones.
The TCP over Satellite Working Group shall produce an informational RFC which describes the issues affecting TCP throughput over satellite links. It identifies the domains in which each issue applies, including network topology, satellite orbit (LEO, MEO, GEO), and link rates; fixes, both protocol and implementation, that ameliorate reduced throughput; and areas for further research. The purpose of including this information is to direct the research community to the areas in which show promise, not to perform the research or even advocate the results.
The scope of this working group will include consideration of the following for inclusion in the Informational RFC:
o Transport layer issues affecting TCP over satellite links o Existing TCP options o Compliant implementations which have some known improved performance over satellite links o Recommendation of well understood protocol changes o Identification of protocol changes that are potentially promising but require more further investigation in order to be well understood
The working group will consider in depth security issues that are relevant, describing risks and indicating how they may be addressed.
Goals and Milestones:
Post first Internet-Draft.
Meet at Munich IETF to review Internet-Draft.
Meet at DC IETF tyo achieve consensus on final version of Internet-Draft.
Submit Internet-Draft to IESG for consideration as an Informational RFC.
No Request For Comments
Report By: Jim Griner (email@example.com)
The TCP over Satellite group met on December 8th at 1PM. Aaron Falk, WG chair presented the WG status, showing the following:
(1) The Internet Draft "Enhancing TCP Over Satellite Channels using Standard Mechanisms" has been forwarded to the RFC Editor by the IESG for publication as a BCP.
(2) The Internet-Draft "Ongoing TCP Research Related to Satellites" is now on revision number five, with nearly all sections completed. The schedule is to send it to the IESG in February 99.
(3) This was the last meeting of TCPSAT. All discussions concerning TCP over satellites is being moved to the performance implications of link characteristics (pilc) mailing list. The website for pilc is http://pilc.lerc.nasa.gov/pilc. All discussions on TCP spoofing and splitting connections are being moved to the tcppep mailing list. The website for tcppep is http://tcppep.lerc.nasa.gov/tcppep. However, the TCPSAT mailing list will remain active.
Mark Allman, document editor, presented a brief summary of new sections added to the research issues draft. No new sections are being solicited for the draft. Plans are to have all editing done in mid-January, and submission to the IESG in mid-February.
Jim Griner, NASA Lewis, announced an Internet-Draft is available, which defined terminology used in discussions about TCP performance enhancing proxies. draft-griner-tcppep-term-00.txt
Rohit Goyal, Ohio State University, presented an overview of the Internet-Draft Optimizing TCP over Satellite ATM Networks, draft-goyal-tcpsat-tcpatm-00.txt. Aaron raised the question as to whether the TCPSAT group wanted to request a charter change that would allow the TCP over ATM over satellite work to be completed in the WG. Many think technical articles should be written about this issue, but that it is not within the IETF scope. There did not seem to be consensus or WG energy to take on this additional document.