| TSVWG | V. Roca |
| Internet-Draft | B. Teibi |
| Intended status: Standards Track | INRIA |
| Expires: April 30, 2018 | October 27, 2017 |
Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME
draft-ietf-tsvwg-rlc-fec-scheme-01
This document describes two fully-specified FEC Schemes for Sliding Window Random Linear Codes (RLC), one for RLC over GF(2) (binary case), a second one for RLC over GF(2^^8), both of them with the possibility of controlling the code density. They are meant to protect arbitrary media streams along the lines defined by FECFRAME extended to sliding window FEC codes. These sliding window FEC codes rely on an encoding window that slides over the source symbols, generating new repair symbols whenever needed. Compared to block FEC codes, these sliding window FEC codes offer key advantages with real-time flows in terms of reduced FEC-related latency while often providing improved erasure recovery capabilities.
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 April 30, 2018.
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 (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 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.
Application-Level Forward Erasure Correction (AL-FEC) codes are a key element of communication systems. They are used to recover from packet losses (or erasures) during content delivery sessions to a large number of receivers (multicast/broadcast transmissions). This is the case with the FLUTE/ALC protocol [RFC6726] in case of reliable file transfers over lossy networks, and the FECFRAME protocol for reliable continuous media transfers over lossy networks.
The present document only focusses on the FECFRAME protocol, used in multicast/broadcast delivery mode, with contents that feature stringent real-time constraints: each source packet has a maximum validity period after which it will not be considered by the destination application.
With FECFRAME, there is a single FEC encoding point (either a end-host/server (source) or a middlebox) and a single FEC decoding point (either a end-host (receiver) or middlebox). In this context, currently standardized AL-FEC codes for FECFRAME like Reed-Solomon [RFC6865], LDPC-Staircase [RFC6816], or Raptor/RaptorQ, are all linear block codes: they require the data flow to be segmented into blocks of a predefined maximum size. The block size is a balance between robustness (in particular in front of long erasure bursts for which there is an incentive to increase the block size) and maximum decoding latency (for which there is an incentive to decrease the block size). Therefore, with a multicast/broadcast session, the block code is dimensioned by considering the worst communication channel one wants to support, and this choice impacts all receivers, no matter their individual channel quality.
This document introduces two fully-specified FEC Schemes that follow a totally different approach: the Sliding Window Random Linear Codes (RLC) over either Finite Field GF(2) or GF(8). These FEC Schemes are used to protect arbitrary media streams along the lines defined by FECFRAME extended to sliding window FEC codes [fecframe-ext]. These FEC Schemes are extremely efficient for instance with media that feature real-time constraints sent within a multicast/broadcast session.
The RLC codes belong to the broad class of sliding window AL-FEC codes (A.K.A. convolutional codes). The encoding process is based on an encoding window that slides over the set of source packets (in fact source symbols as we will see in Section 3.2), and which is either of fixed or variable size (elastic window). Repair packets (symbols) are generated and sent on-the-fly, after computing a random linear combination of the source symbols present in the current encoding window.
At the receiver, a linear system is managed from the set of received source and repair packets. New variables (representing source symbols) and equations (representing the linear combination of each repair symbol received) are added upon receiving new packets. Variables are removed when they are too old with respect to their validity period (real-time constraints), as well as the associated equations they are involved in (Appendix A introduces an optimisation that extends the time a variable is considered in the system). Erased source symbols are then recovered thanks this linear system whenever its rank permits it.
With RLC codes (more generally with sliding window codes), the protection of a multicast/broadcast session also needs to be dimensioned by considering the worst communication channel one wants to support. However the receivers experiencing a good to medium channel quality observe a FEC-related latency close to zero [Roca17] since an isolated erased source packet is quickly recovered by the following repair packet. On the opposite, with a block code, recovering an isolated erased source packet always requires waiting the end of the block for the first repair packet to arrive. Additionally, under certain situations (e.g., with a limited FEC-related latency budget and with constant bit rate transmissions after FECFRAME encoding), sliding window codes achieve more easily a target transmission quality (e.g., measured by the residual loss after FEC decoding) by sending fewer repair packets (i.e., higher code rate) than block codes.
The Sliding Window RLC FEC Scheme is designed so as to reduce the transmission overhead. The main requirement is that each repair packet header must enable a receiver to reconstruct the list of source symbols and the associated random coefficients used during the encoding process. In order to minimize packet overhead, the set of symbols in the encoding window as well as the set of coefficients over GF(2^^m) (where m is 1 or 8, depending on the FEC Scheme) used in the linear combination are not individually listed in the repair packet header. Instead, each FEC repair packet header contains:
Therefore, no matter the number of source symbols present in the encoding window, each FEC repair packet features a fixed 64-bit long header, called Repair FEC Payload ID (Figure 7). Similarly, each FEC source packet features a fixed 32-bit long trailer, called Explicit Source FEC Payload ID (Figure 5), that contains the ESI of the first source symbol (see the ADUI and source symbol mapping, Section 3.2).
This fully-specified FEC Scheme follows the structure required by [RFC6363], section 5.6. "FEC Scheme Requirements", namely:
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 [RFC2119].
This document uses the following definitions and abbreviations:
This section introduces the procedures that are used by this FEC Scheme.
The Sliding Window RLC FEC Scheme relies on several key internal parameters:
In order to comply with the maximum FEC-related latency budget, assuming a constant transmission bitrate at the output of the FECFRAME sender (br_out), encoding symbol size (E), and code rate (cr), we have:
This dw_max_size defines the maximum delay after which an old source symbol may be recovered: after this delay, this old source symbol symbol will be removed from the decoding window.
It is often good practice to choose:
However any value ew_max_size < dw_max_size can be used without impact on the FEC-related latency budget. Finding the optimal value can depend on the erasure channel one wants to support and should be determined after simulations or field trials.
Note that the decoding beyond maximum latency optimisation (Appendix A) enables an old source symbol to be kept in the linear system beyond the FEC-related latency budget, but not delivered to the receiving application. Here we have: ls_size ≥ dw_max_size
An ADU, coming from the application, cannot be mapped to source symbols directly. Indeed, an erased ADU recovered at a receiver must contain enough information to be assigned to the right application flow (UDP port numbers and IP addresses cannot be used to that purpose as they are not protected by FEC encoding). This requires adding the flow identifier to each ADU before doing FEC encoding.
Additionally, since ADUs are of variable size, padding is needed so that each ADU (with its flow identifier) contribute to an integral number of source symbols. This requires adding the original ADU length to each ADU before doing FEC encoding. Because of these requirements, an intermediate format, the ADUI, or ADU Information, is considered [RFC6363].
For each incoming ADU, an ADUI is created as follows. First of all, 3 bytes are prepended: (Figure 1):
Then, zero padding is added to the ADU if needed:
Each ADUI contributes to an integral number of source symbols. The data unit resulting from the ADU and the F, L, and Pad fields is called ADU Information (or ADUI). Since ADUs can be of different size, this is also the case for ADUIs.
symbol length, E E E < ------------------ >< ------------------ >< ------------------ > +-+--+---------------------------------------------+-------------+ |F| L| ADU | Pad | +-+--+---------------------------------------------+-------------+
Figure 1: ADUI Creation example (here 3 source symbols are created for this ADUI).
Note that neither the initial 3 bytes nor the optional padding are sent over the network. However, they are considered during FEC encoding. It means that a receiver who lost a certain FEC source packet (e.g., the UDP datagram containing this FEC source packet) will be able to recover the ADUI if FEC decoding succeeds. Thanks to the initial 3 bytes, this receiver will get rid of the padding (if any) and identify the corresponding ADU flow.
Source symbols and the corresponding ADUs are removed from the encoding window:
Source symbols are added to the sliding encoding window each time a new ADU arrives, once the ADU to ADUI and then to source symbols mapping has been performed (Section 3.2). The current size of the encoding window, ew_size, is updated after adding new source symbols. This process may require to remove old source symbols so that: ew_size ≤ ew_max_size.
Note that a FEC codec may feature practical limits in the number of source symbols in the encoding window (e.g., for computational complexity reasons). This factor may further limit the ew_max_lat value, in addition to the maximum FEC-related latency budget (Section 3.1).
The RLC codes rely on the following Pseudo-Random Number Generator (PRNG), identical to the PRNG used with LDPC-Staircase codes ([RFC5170], section 5.7).
The Park-Miler "minimal standard" PRNG [PM88] MUST be used. It defines a simple multiplicative congruential algorithm: Ij+1 = A * Ij (modulo M), with the following choices: A = 7^^5 = 16807 and M = 2^^31 - 1 = 2147483647. A validation criteria of such a PRNG is the following: if seed = 1, then the 10,000th value returned MUST be equal to 1043618065.
Several implementations of this PRNG are known and discussed in the literature. An optimized implementation of this algorithm, using only 32-bit mathematics, and which does not require any division, can be found in [rand31pmc]. It uses the Park and Miller algorithm [PM88] with the optimization suggested by D. Carta in [CA90]. The history behind this algorithm is detailed in [WI08]. Yet, any other implementation of the PRNG algorithm that matches the above validation criteria, like the ones detailed in [PM88], is appropriate.
This PRNG produces, natively, a 31-bit value between 1 and 0x7FFFFFFE (2^^31-2) inclusive. Since it is desired to scale the pseudo-random number between 0 and maxv-1 inclusive, one must keep the most significant bits of the value returned by the PRNG (the least significant bits are known to be less random, and modulo-based solutions should be avoided [PTVF92]). The following algorithm MUST be used:
Input:
Output:
Algorithm:
In this document, pmms_rand(maxv) denotes the PRNG function that implements the Park-Miller "minimal standard" algorithm, defined above, and that scales the raw value between 0 and maxv-1 inclusive, using the above scaling algorithm.
Additionally, the pmms_srand(seed) function must be provided to enable the initialization of the PRNG with a seed before calling pmms_rand(maxv) the first time. The seed is a 31-bit integer between 1 and 0x7FFFFFFE inclusive. In this specification, the seed is restricted to a value between 1 and 0xFFFF inclusive, as this is the Repair_Key 16-bit field value of the Repair FEC Payload ID (Section 5.1.3).
The coding coefficients, used during the encoding process, are generated at the RLC encoder by the generate_coding_coefficients() function each time a new repair symbol needs to be produced. Note that the fraction of coefficients that are non zero (density) is controlled by a dedicated parameter, DT (Density Threshold). When this parameter equals 15, the maximum value, the function guaranties that all coefficients are non zero (i.e., maximum density). When the parameter is between 0 (minimum value) and strictly inferior to 15, the average probability of having a non zero coefficients equals (DT +1) / 16. The density is reduced in a controlled manner.
These considerations apply both the RLC over GF(2) and RLC over GF(2^^8), the only difference being the value of the m parameter. With the RLC over GF(2) FEC Scheme (Section 4), m MUST be equal to 1. With RLC over GF(2^^8) FEC Scheme (Section 5), m MUST be equal to 8.
<CODE BEGINS>
/*
* Fills in the table of coding coefficients (of the right size)
* provided with the appropriate number of coding coefficients to
* use for the repair symbol key provided.
*
* (in) repair_key key associated to this repair symbol
* (in) cc_tab[] pointer to a table of the right size to store
* coding coefficients. All coefficients are
* stored as bytes, regardless of the m parameter,
* upon return of this function.
* (in) cc_nb[] number of entries in the table. This value is
* equal to the current encoding window size.
* (in) density_threshold value between 0 and 15 (inclusive) that
* controls the density. With value 15, all
* coefficients are guaranteed to be non zero
* (i.e. equal to 1 with GF(2) and equal to a
* value in {1,... 255} with GF(2^^8)), otherwise
* a fraction of them will be 0.
* (in) m Finite Field GF(2^^m) parameter. In this
* version only 1 and 8 are considered.
* (out) returns an error code
*/
int generate_coding_coefficients (UINT16 repair_key,
UINT8 cc_tab[],
UINT16 cc_nb,
UINT8 density_threshold,
UINT8 m)
{
UINT32 i;
if (repair_key == 0 || density_threshold > 15) {
/* bad parameters */
return SOMETHING_WENT_WRONG;
}
pmms_srand(repair_key);
switch (m) {
case 1:
if (density_threshold == 15) {
/* all coefficients are 1 */
memset(cc_tab, 1, cc_nb);
} else {
for (i = 0 ; i < cc_nb ; i++) {
if (pmms_rand(16) <= density_threshold) {
cc_tab[i] = (UINT8) 1;
} else {
cc_tab[i] = (UINT8) 0;
}
}
}
break;
case 8:
if (density_threshold == 15) {
/* coefficient 0 is avoided here in order to include
* all the source symbols */
for (i = 0 ; i < cc_nb ; i++) {
do {
cc_tab[i] = (UINT8) pmms_rand(256);
} while (cc_tab[i] == 0);
}
} else {
/* here a certain fraction of coefficients should be 0 */
for (i = 0 ; i < cc_nb ; i++) {
if (pmms_rand(16) <= density_threshold) {
do {
cc_tab[i] = (UINT8) pmms_rand(256);
} while (cc_tab[i] == 0);
} else {
cc_tab[i] = 0;
}
}
}
break;
default:
/* bad parameter m */
return SOMETHING_WENT_WRONG;
}
return EVERYTHING_IS_OKAY;
}
<CODE ENDS>
Figure 2: Coding Coefficients Generation Function pseudo-code
This fully-specified FEC Scheme defines the Sliding Window Random Linear Codes (RLC) over GF(2) (binary case).
When SDP is used to communicate the FFCI, this FEC Encoding ID is carried in the 'encoding-id' parameter.
All the considerations of Section 5.1.1.2 apply equally here.
All the considerations of Section 5.1.1.2 apply equally here.
All the considerations of Section 5.1.1.2 apply equally here.
All the considerations of Section 5.1.1.2 apply equally here.
This fully-specified FEC Scheme defines the Sliding Window Random Linear Codes (RLC) over GF(2^^8).
The FEC Framework Configuration Information (or FFCI) includes information that MUST be communicated between the sender and receiver(s). More specifically, it enables the synchronization of the FECFRAME sender and receiver instances. It includes both mandatory elements and scheme-specific elements, as detailed below.
When SDP is used to communicate the FFCI, this FEC Encoding ID is carried in the 'encoding-id' parameter.
The FEC Scheme-Specific Information (FSSI) includes elements that are specific to the present FEC Scheme. More precisely:
This element is required both by the sender (RLC encoder) and the receiver(s) (RLC decoder).
When SDP is used to communicate the FFCI, this FEC Scheme-specific information is carried in the 'fssi' parameter in textual representation as specified in [RFC6364]. For instance:
fssi=E:1400
If another mechanism requires the FSSI to be carried as an opaque octet string (for instance, after a Base64 encoding), the encoding format consists of the following 2 octets:
0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Encoding Symbol Length (E) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: FSSI Encoding Format
A FEC source packet MUST contain an Explicit Source FEC Payload ID that is appended to the end of the packet as illustrated in Figure 4.
+--------------------------------+ | IP Header | +--------------------------------+ | Transport Header | +--------------------------------+ | ADU | +--------------------------------+ | Explicit Source FEC Payload ID | +--------------------------------+
Figure 4: Structure of an FEC Source Packet with the Explicit Source FEC Payload ID
More precisely, the Explicit Source FEC Payload ID is composed of the following field (Figure 5):
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Encoding Symbol ID (ESI) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Source FEC Payload ID Encoding Format
A FEC repair packet MUST contain a Repair FEC Payload ID that is prepended to the repair symbol as illustrated in Figure 6. There can be one or more repair symbols per FEC repair packet. When this is the case, the number of repair symbols within this FEC repair packet is easily deduced by comparing the known received FEC repair packet size (equal to the UDP payload size when UDP is the underlying transport protocol) and the symbol size, E, communicated in the FFCI. When this is the case, all the repair symbols MUST have been generated from the same encoding window.
+--------------------------------+ | IP Header | +--------------------------------+ | Transport Header | +--------------------------------+ | Repair FEC Payload ID | +--------------------------------+ | Repair Symbol | +--------------------------------+
Figure 6: Structure of an FEC Repair Packet with the Repair FEC Payload ID
More precisely, the Repair FEC Payload ID is composed of the following fields (Figure 7):
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Repair_Key | DT |NSS (# src symb in ew) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | FSS_ESI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Repair FEC Payload ID Encoding Format
The following procedure applies:
This section provides a high level description of a Sliding Window RLC encoder.
Whenever a new FEC repair packet is needed, the RLC encoder instance first gathers the ew_size source symbols currently in the sliding encoding window. Then it chooses a repair key, which can be a non zero monotonically increasing integer value, incremented for each repair symbol up to a maximum value of 65535 (as it is carried within a 16-bit field) after which it loops back to 1 (indeed, being used as a PRNG seed, value 0 is prohibited). This repair key is communicated to the coefficient generation function (Section Section 3.5) in order to generate ew_size coding coefficients. Finally, the FECFRAME sender computes the repair symbol as a linear combination of the ew_size source symbols using the ew_size coding coefficients. When E is small and when there is an incentive to pack several repair symbols within the same FEC Repair Packet, the appropriate number of repair symbols are computed. The only constraint is to increment by 1 the repair key for each of them, keeping the same ew_size source symbols, since only the first repair key will be carried in the Repair FEC Payload ID. The FEC repair packet can then be sent. The source versus repair FEC packet transmission order is out of scope of this document and several approaches exist that are implementation specific.
This section provides a high level description of a Sliding Window RLC decoder.
A FECFRAME receiver needs to maintain a linear system whose variables are the received and lost source symbols. Upon receiving a FEC repair packet, a receiver first extracts all the repair symbols it contains (in case several repair symbols are packed together). For each repair symbol, when at least one of the corresponding source symbols it protects has been lost, the receiver adds an equation to the linear system (or no equation if this repair packet does not change the linear system rank). This equation of course re-uses the ew_size coding coefficients that are computed by the same coefficient generation function (Section Section 3.5), using the repair key and encoding window descriptions carried in the Repair FEC Payload ID. Whenever possible (i.e., when a sub-system covering one or more lost source symbols is of full rank), decoding is performed in order to recover lost source symbols. Each time an ADUI can be totally recovered, it is assigned to the corresponding application flow (thanks to the Flow ID (F) field of the ADUI) and padding (if any) removed (thanks to the Length (L) field of the ADUI). This ADU is finally passed to the corresponding upper application. Received FEC source packets, containing an ADU, can be passed to the application either immediately or after some time to guaranty an ordered delivery to the application(s). This document does not mandate any approach as this is an operational and management decision.
With real-time flows, a lost ADU that is decoded after the maximum latency (or an ADU received far too late) should not be considered by the application. Instead the associated source symbols should be removed from the linear system maintained by the receiver(s). Appendix A discusses a backward compatible optimization whereby those late source symbols may still be useful to improve the global loss recovery performance.
Editor's notes: RFC Editor, please remove this section motivated by RFC 6982 before publishing the RFC. Thanks.
An implementation of the Sliding Window RLC FEC Scheme for FECFRAME exists:
The FEC Framework document [RFC6363] provides a comprehensive analysis of security considerations applicable to FEC Schemes. Therefore, the present section follows the security considerations section of [RFC6363] and only discusses specific topics.
The Sliding Window RLC FEC Scheme specified in this document does not change the recommendations of [RFC6363]. To summarize, if confidentiality is a concern, it is RECOMMENDED that one of the solutions mentioned in [RFC6363] is used with special considerations to the way this solution is applied (e.g., is encryption applied before or after FEC protection, within the end-system or in a middlebox) to the operational constraints (e.g., performing FEC decoding in a protected environment may be complicated or even impossible) and to the threat model.
The Sliding Window RLC FEC Scheme specified in this document does not change the recommendations of [RFC6363]. To summarize, it is RECOMMENDED that one of the solutions mentioned in [RFC6363] is used on both the FEC Source and Repair Packets.
The FEC Scheme specified in this document defines parameters that can be the basis of attacks. More specifically, the following parameters of the FFCI may be modified by an attacker who only targets receivers (Section 5.1.1.2):
An attacker who only targets a sender will achieve the same results. However if the attacker targets both sender and receivers at the same time (the same wrong piece of information is communicated to everybody), the results will be suboptimal but less severe.
It is therefore RECOMMENDED that security measures are taken to guarantee the FFCI integrity, as specified in [RFC6363]. How to achieve this depends on the way the FFCI is communicated from the sender to the receiver, which is not specified in this document.
Similarly, attacks are possible against the Explicit Source FEC Payload ID and Repair FEC Payload ID: by modifying the Encoding Symbol ID (ESI), or the repair key, NSS or FSS_ESI. It is therefore RECOMMENDED that security measures are taken to guarantee the FEC Source and Repair Packets as stated in [RFC6363].
The Sliding Window RLC FEC Scheme specified in this document does not change the recommendations of [RFC6363].
The Sliding Window RLC FEC Scheme specified in this document does not change the recommendations of [RFC6363] concerning the use of the IPsec/ESP security protocol as a mandatory to implement (but not mandatory to use) security scheme. This is well suited to situations where the only insecure domain is the one over which the FEC Framework operates.
The FEC Framework document [RFC6363] provides a comprehensive analysis of operations and management considerations applicable to FEC Schemes. Therefore, the present section only discusses specific topics.
The present document specifies two FEC Schemes that differ on the associated Finite Field used for the coding coefficients. It is expected that the RLC over GF(2^^8) FEC Scheme will be mostly used since it warrants a high loss protection. Additionally, elements in the finite field are 8 bits long, which makes read/write memory operations aligned on bytes during encoding and decoding.
Finally, in particular when dealing with large encoding windows, an alternative is the RLC over GF(2) FEC Scheme. In that case operations symbols can be directly XORed together which warrants high bitrate encoding and decoding operations.
In addition to the choice of the Finite Field, the two FEC Schemes define a coding coefficient density threshold parameter. This parameter enables a sender to control the code density, i.e., the proportion of coefficients that are non zero on average. With RLC over GF(2^^8), it is recommended that small encoding windows be associated to a density threshold equal to 15, the maximum value, in order to warrant a high loss protection.
On the opposite, with large encoding windows, it it recommened that the density threshold be reduced. With large encoding windows, an alternative can be to use RLC over GF(2) and a density threshold equal to 8 (i.e., an average density equal to 1/2) or smaller.
Note also that using a density threshold equal to 15 with RLC over GF(2) is equivalent to using code that XOR's all the source symbols of the encoding window. In that case it follows that: (1) a single repair symbol can be produced for a given encoding window, and (2) the repair_key parameter is useless (the coding coefficients generation function does not rely on the PRNG).
This document registers two values in the "FEC Framework (FECFRAME) FEC Encoding IDs" registry [RFC6363] as follows:
The authors would like to thank Marie-Jose Montpetit for her valuable feedbacks on this document.
| [fecframe-ext] | Roca, V. and A. Begen, "Forward Error Correction (FEC) Framework Extension to Sliding Window Codes", Transport Area Working Group (TSVWG) draft-roca-tsvwg-fecframev2 (Work in Progress), 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. |
| [RFC6363] | Watson, M., Begen, A. and V. Roca, "Forward Error Correction (FEC) Framework", RFC 6363, DOI 10.17487/RFC6363, October 2011. |
| [RFC6364] | Begen, A., "Session Description Protocol Elements for the Forward Error Correction (FEC) Framework", RFC 6364, DOI 10.17487/RFC6364, October 2011. |
This annex introduces non normative considerations. They are provided as suggestions, without any impact on interoperability. For more information see [Roca16].
It is possible to improve the decoding performance of sliding window codes without impacting maximum latency, at the cost of extra CPU overhead. The optimization consists, for a receiver, to extend the linear system beyond the decoding window:
Usually the following choice is a good trade-off between decoding performance and extra CPU overhead:
ls_max_size
/---------------------------------^-------------------------------\
late source symbols
(pot. decoded but not delivered) dw_max_size
/--------------^-----------------\ /--------------^---------------\
src0 src1 src2 src3 src4 src5 src6 src7 src8 src9 src10 src11 src12
Figure 8: Relationship between parameters to decode beyond maximum latency.
It means that source symbols (and therefore ADUs) may be decoded even if their transport protocol added latency exceeds the maximum value permitted by the application. It follows that these source symbols SHOULD NOT be delivered to the application and SHOULD be dropped once they are no longer needed. However, decoding these late symbols significantly improves the global robustness in bad reception conditions and is therefore recommended for receivers experiencing bad channels[Roca16]. In any case whether or not to use this facility and what exact value to use for the ls_max_size parameter are decisions made by each receiver independently, without any impact on others, neither the other receivers nor the source.