BATS Coding Scheme for Multi-hop Data Transport
draft-yang-nwcrg-bats-03
Internet Engineering Task Force S. Yang
Internet-Draft CUHK(SZ)
Intended status: Informational X. Huang
Expires: November 26, 2020 R.W. Yeung
CUHK
J.K. Zao
NCTU
May 25, 2020
BATS Coding Scheme for Multi-hop Data Transport
draft-yang-nwcrg-bats-03
Abstract
This document describes a BATS coding scheme for communication
through multi-hop networks. BATS code is a class of efficient linear
network coding scheme with a matrix generalization of fountain codes
as the outer code, and batch-based linear network coding as the inner
code.
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 https://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 November 26, 2020.
Copyright Notice
Copyright (c) 2020 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
(https://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
Yang, et al. Expires November 26, 2020 [Page 1]
Internet-Draft BATS Code May 2020
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Data Delivery Procedures . . . . . . . . . . . . . . . . 4
2.2.1. Source Node Data Partitioning and Padding . . . . . . 5
2.2.2. Source Node Outer Code Encoding Procedure . . . . . . 5
2.2.3. Recoding Procedures . . . . . . . . . . . . . . . . . 7
2.2.4. Destination Node Procedures . . . . . . . . . . . . . 7
2.3. Recommendation for the Parameters . . . . . . . . . . . . 8
2.4. Example DDP Packet Format . . . . . . . . . . . . . . . . 8
2.4.1. Packet Header . . . . . . . . . . . . . . . . . . . . 8
2.4.2. Packet Payload . . . . . . . . . . . . . . . . . . . 9
2.4.3. Packet Footer . . . . . . . . . . . . . . . . . . . . 10
3. BATS Code Specification . . . . . . . . . . . . . . . . . . . 10
3.1. Common Parts . . . . . . . . . . . . . . . . . . . . . . 10
3.2. Outer Code Encoder . . . . . . . . . . . . . . . . . . . 11
3.3. Inner Code Encoder (Recoder) . . . . . . . . . . . . . . 12
3.4. Belief Propagation Decoder . . . . . . . . . . . . . . . 13
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5.1. Provision of Confidentiality Protection . . . . . . . . . 14
5.2. Countermeasures against Pollution Attacks . . . . . . . . 14
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1. Normative References . . . . . . . . . . . . . . . . . . 15
6.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
This document specifies a BATS code [BATS] scheme for data delivery
in multi-hop networks. The BATS code described here includes an
outer code and an inner code. The outer code is a matrix
generalization of fountain codes (see also the RapterQ code described
in RFC 6330 [RFC6330]), which inherits the advantages of reliability
Show full document text