Skip to main content

Network coding and satellites
draft-kuhn-nwcrg-network-coding-satellites-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Authors Nicolas Kuhn , Emmanuel Lochin
Last updated 2017-06-30
Replaced by draft-irtf-nwcrg-network-coding-satellites, draft-irtf-nwcrg-network-coding-satellites, draft-irtf-nwcrg-network-coding-satellites, RFC 8975
RFC stream (None)
Formats
Additional resources
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-kuhn-nwcrg-network-coding-satellites-00
Internet Engineering Task Force                             N. Kuhn, Ed.
Internet-Draft                                                      CNES
Intended status: Informational                            E. Lochin, Ed.
Expires: December 31, 2017                                          ISAE
                                                           June 29, 2017

                     Network coding and satellites
             draft-kuhn-nwcrg-network-coding-satellites-00

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 31, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kuhn & Lochin           Expires December 31, 2017               [Page 1]
Internet-Draft        Network coding and satellites            June 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  A note on satellite topology  . . . . . . . . . . . . . . . .   3
     2.1.  Generic description of multi-gateway satellite networks .   3
     2.2.  Focus on satellite gateway description  . . . . . . . . .   3
   3.  Status of network coding in actually deployed satellite
       systems . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Opportunities for more network coding in satellite systems  .   4
   5.  Deployability and related use cases . . . . . . . . . . . . .   4
     5.1.  Network coding and VNF  . . . . . . . . . . . . . . . . .   4
     5.2.  Network coding and PEP  . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   4
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   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:

   o  summing up the current deployment of network coding schemes;

   o  identifying opportunities for further usage of network coding in
      satellite systems.

1.1.  Glossary

   The glossary of this memo is related to the network coding taxonomy
   document [I-D.irtf-nwcrg-network-coding-taxonomy].

   The glossary is extended as follows:

   o  XX: XX

Kuhn & Lochin           Expires December 31, 2017               [Page 2]
Internet-Draft        Network coding and satellites            June 2017

1.2.  Requirements Language

   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 [RFC2119].

2.  A note on satellite topology

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

2.1.  Generic description of multi-gateway satellite networks

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

2.2.  Focus on satellite gateway description

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

3.  Status of network coding in actually deployed satellite systems

   Figure 1 presents the status of the network coding deployment in
   satellite systems.  The information is based on the taxonomy document
   [I-D.irtf-nwcrg-network-coding-taxonomy] 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    |       |         |               |       |
   +------+-------+---------+---------------+-------+

              Figure 1: Network coding and satellite systems

Kuhn & Lochin           Expires December 31, 2017               [Page 3]
Internet-Draft        Network coding and satellites            June 2017

4.  Opportunities for more network coding in satellite systems

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

   .

5.  Deployability and related use cases

   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 Section 4.

5.1.  Network coding and VNF

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

5.2.  Network coding and PEP

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

6.  Acknowledgements

7.  Contributors

   Many thanks to

8.  IANA Considerations

   This memo includes no request to IANA.

9.  Security Considerations

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

10.  References

10.1.  Normative References

Kuhn & Lochin           Expires December 31, 2017               [Page 4]
Internet-Draft        Network coding and satellites            June 2017

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3135]  Border, J., Kojo, M., Griner, J., Montenegro, G., and Z.
              Shelby, "Performance Enhancing Proxies Intended to
              Mitigate Link-Related Degradations", RFC 3135,
              DOI 10.17487/RFC3135, June 2001,
              <http://www.rfc-editor.org/info/rfc3135>.

   [RFC5865]  Baker, F., Polk, J., and M. Dolly, "A Differentiated
              Services Code Point (DSCP) for Capacity-Admitted Traffic",
              RFC 5865, DOI 10.17487/RFC5865, May 2010,
              <http://www.rfc-editor.org/info/rfc5865>.

10.2.  Informative References

   [I-D.irtf-nwcrg-network-coding-taxonomy]
              Adamson, B., Adjih, C., Bilbao, J., Firoiu, V., Fitzek,
              F., samah.ghanem@gmail.com, s., Lochin, E., Masucci, A.,
              Montpetit, M., Pedersen, M., Peralta, G., Roca, V.,
              Saxena, P., and S. Sivakumar, "Network Coding Taxonomy",
              draft-irtf-nwcrg-network-coding-taxonomy-03 (work in
              progress), June 2017.

Authors' Addresses

   Nicolas Kuhn (editor)
   CNES
   18 Avenue Edouard Belin
   Toulouse  31400
   France

   Phone: 0033561273213
   Email: nicolas.kuhn@cnes.fr

   Emmanuel Lochin (editor)
   ISAE
   10 Avenue Edouard Belin
   Toulouse  31400
   France

   Email: emmanuel.lochin@isae.fr

Kuhn & Lochin           Expires December 31, 2017               [Page 5]