Future standardization of PEPs discussed at workshop
In general, the Internet transport protocol (namely TCP, the Transport Control Protocol) exhibits suboptimal performance due to the following satellite characteristics: long feedback loops, large bandwidth*delay product, asymmetric capacity. One solution is implementing a TCP PEP. This usually consists in splitting the connection in order to apply more adequate flow and congestion control techniques over the satellite link.
In addition to TCP PEPs, there are other complementary solutions such as application layer PEPs, which implement techniques such as data and header compression algorithms; HTTP acceleration (with caching and web page objects prefetching) and DNS caching techniques. All these PEP techniques are now more and more widespread in satellite communications and were discussed at the workshop.
Delegates from ETSI, ESA and industry took part in lively discussions on current and future standardisation issues such as:
• Capacity management/Quality of Service interface between PEPs, satellite terminals and gateways, including cross-layer techniques.
• Management aspects of PEPs (standard Management Information Bases), configuration and monitoring.
• Multicast PEPs including multicast optimisation and replication.
• Separation of A-PEP (application) and T-PEP (transport) with standard interface.
• Future On-Board Processing satellites with PEPs.