]> CNES

18 Avenue Edouard Belin Toulouse 31400 France 0033561273213 nicolas.kuhn@cnes.fr

ISAE

10 Avenue Edouard Belin Toulouse 31400 France emmanuel.lochin@isae.fr

Transport Internet Engineering Task Force template This memo presents the current deployment of network coding in some satellite telecommunications systems along with a discussion on the multiple opportunities to introduce these technics at a wider scale.

Network coding schemes are inherent part of the satellite systems, since the challenging physical layer require specific robustness to guarantee an efficient usage of the expensive radio resource. Further exploiting these schemes is an opportunity for a better end user experience along with a better exploitation of the scarce resource. In this context, this memo aims at: summing up the current deployment of network coding schemes; identifying opportunities for further usage of network coding in satellite systems.

The glossary of this memo is related to the network coding taxonomy document . The glossary is extended as follows: XX: XX

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

The objective of this section of to provide a generic description of the components composing a generic satellite system and their interaction.

This subsection presents a high level description of a multi-gateway satellite network.

This subsection focuses on the description of the functions that take place in a generic satellite gateway.

presents the status of the network coding deployment in satellite systems. The information is based on the taxonomy document and the notations are the following: End-to-End Coding (E2E), Network Coding (NC), Intra-Flow Coding (IntraF), Inter-Flow Coding (InterF), Single-Path Coding (SP) and Multi-Path Coding (MP).

+------+-------+---------+---------------+-------+ + | Upper | Middle | Communication layers | + | Appl. | ware | | + +-------+---------+---------------+-------+ | |Source | Network | Packetization | PHY | | |coding | AL-FEC | UDP/IP | layer | +------+-------+---------+---------------+-------+ |E2E | x | | | | |NC | | | | x | |IntraF| | | | | |InterF| | | | | |SP | | | | | |MP | | | | | +------+-------+---------+---------------+-------+

This section extends by presenting the opportunities for more network coding in satellite systems. .

This section details use-cases where the usage of network coding schemes could improve the overall system and the deployability of the opportunities that are provided in .

Related to the foreseen virtualized network infrastructure, the network coding schemes could be proposed as VNF and their deployability enhanced.

Related to the impact and integration of network coding in Proxy-Enhanced-Proxy RFC 3135 architecture. In particular how network coding can be integrated inside a PEP with QoS scheduler as defined, for instance, in RFC 5865.

Many thanks to

This memo includes no request to IANA.

This document, by itself, presents no new privacy nor security issues.

&RFC2119;