< draft-roca-nwcrg-rlc-fec-scheme-for-quic-00.txt   draft-roca-nwcrg-rlc-fec-scheme-for-quic-01.txt >
nwcrg V. Roca nwcrg V. Roca
Internet-Draft INRIA Internet-Draft INRIA
Intended status: Informational I. Swett Intended status: Informational I. Swett
Expires: December 23, 2018 Google Expires: August 8, 2019 Google
M-J. Montpetit M-J. Montpetit
Triangle Video Triangle Video
June 21, 2018 February 4, 2019
Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC)
Schemes for QUIC Schemes for QUIC
draft-roca-nwcrg-rlc-fec-scheme-for-quic-00 draft-roca-nwcrg-rlc-fec-scheme-for-quic-01
Abstract Abstract
This document specifies Sliding Window Random Linear Code (RLC) This document specifies Sliding Window Random Linear Code (RLC)
Forward Erasure Correction (FEC) Schemes for the QUIC transport Forward Erasure Correction (FEC) Schemes for the QUIC transport
protocol, in order to recover from packet losses. protocol, in order to recover from packet losses.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 23, 2018. This Internet-Draft will expire on August 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 25 skipping to change at page 2, line 25
4. Sliding Window RLC FEC Scheme over GF(2^^8) when Protecting a 4. Sliding Window RLC FEC Scheme over GF(2^^8) when Protecting a
Single QUIC Stream . . . . . . . . . . . . . . . . . . . . . 4 Single QUIC Stream . . . . . . . . . . . . . . . . . . . . . 4
4.1. Formats and Codes . . . . . . . . . . . . . . . . . . . . 4 4.1. Formats and Codes . . . . . . . . . . . . . . . . . . . . 4
4.1.1. Configuration Information . . . . . . . . . . . . . . 4 4.1.1. Configuration Information . . . . . . . . . . . . . . 4
4.1.2. REPAIR Frame Format . . . . . . . . . . . . . . . . . 5 4.1.2. REPAIR Frame Format . . . . . . . . . . . . . . . . . 5
4.1.3. Additional Procedures . . . . . . . . . . . . . . . . 6 4.1.3. Additional Procedures . . . . . . . . . . . . . . . . 6
4.2. FEC Code Specification . . . . . . . . . . . . . . . . . 6 4.2. FEC Code Specification . . . . . . . . . . . . . . . . . 6
4.2.1. Encoding Side . . . . . . . . . . . . . . . . . . . . 6 4.2.1. Encoding Side . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Decoding Side . . . . . . . . . . . . . . . . . . . . 6 4.2.2. Decoding Side . . . . . . . . . . . . . . . . . . . . 6
5. Sliding Window RLC FEC Scheme over GF(2^^8) when Protecting 5. Sliding Window RLC FEC Scheme over GF(2^^8) when Protecting
Several QUIC Streams . . . . . . . . . . . . . . . . . . . . 6 Several QUIC Streams . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
skipping to change at page 4, line 45 skipping to change at page 4, line 45
stream. stream.
4.1. Formats and Codes 4.1. Formats and Codes
4.1.1. Configuration Information 4.1.1. Configuration Information
This section provides the RLC configuration information that needs to This section provides the RLC configuration information that needs to
be shared during QUIC negotiation between the QUIC sender and be shared during QUIC negotiation between the QUIC sender and
receiver endpoints in order to synchronize them. receiver endpoints in order to synchronize them.
o FEC Encoding ID: the value assigned to this fully specified FEC o FEC Encoding ID (8 bits): the value assigned to this fully
Scheme MUST be XXXX, as assigned by IANA (Section 7). This FEC specified FEC Scheme MUST be XXXX, as assigned by IANA
Encoding ID is used during the QUIC negotiation to uniquely (Section 7). This FEC Encoding ID is used during the QUIC
identify the RLC FEC Scheme for QUIC; negotiation to uniquely identify the RLC FEC Scheme for QUIC;
o Encoding symbol size, E (in bytes): a non-negative integer that o Encoding symbol size, E (in bytes) (16 bits): a non-negative
indicates the size of each source and repair symbol, in bytes. integer that indicates the size of each source and repair symbol,
in bytes. This element is required both by the QUIC sender
endpoint (RLC encoder) and the QUIC receiver endpoint(s) (RLC
decoder).
This element is required both by the QUIC sender endpoint (RLC TODO: specify exact format, with binary encoding, to be carried
encoder) and the QUIC receiver endpoint(s) (RLC decoder). within the opaque 32-bit field during negotiation.
4.1.2. REPAIR Frame Format 4.1.2. REPAIR Frame Format
The RLC FEC Scheme does not use any explicit Source FEC Payload ID, The RLC FEC Scheme does not use any explicit Source FEC Payload ID,
meaning that QUIC STREAM frame format is not modified. meaning that QUIC STREAM frame format is not modified.
On the opposite, the RLC FEC Scheme requires QUIC REPAIR frames to On the opposite, the RLC FEC Scheme requires QUIC REPAIR frames to
convey enough information. This section specifies the REPAIR frame convey enough information. This section specifies the REPAIR frame
format specific to the RLC FEC Scheme and a single QUIC stream. Note format specific to the RLC FEC Scheme and a single QUIC stream. Note
that the notion of REPAIR frame format is equivalent to the notion of that the notion of REPAIR frame format is equivalent to the notion of
skipping to change at page 7, line 35 skipping to change at page 7, line 41
TBD TBD
9. References 9. References
9.1. Normative References 9.1. Normative References
[Coding4QUIC] [Coding4QUIC]
Swett, I., Montpetit, M-J., and V. Roca, "Coding for Swett, I., Montpetit, M-J., and V. Roca, "Coding for
QUIC", Work in Progress, NWCRG draft-swett-nwcrg-coding- QUIC", Work in Progress, NWCRG draft-swett-nwcrg-coding-
for-quic (Work in Progress), June 2018, for-quic (Work in Progress), February 2019,
<https://tools.ietf.org/html/ <https://tools.ietf.org/html/
draft-swett-nwcrg-coding-for-quic>. draft-swett-nwcrg-coding-for-quic>.
[QUIC-transport] [QUIC-transport]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", draft-ietf-quic- Multiplexed and Secure Transport", draft-ietf-quic-
transport-12 (work in progress), May 2018, transport (Work in Progress) (work in progress), January
<https://datatracker.ietf.org/doc/ 2019, <https://datatracker.ietf.org/doc/
draft-ietf-quic-transport/>. draft-ietf-quic-transport/>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RLC] Roca, V., "Sliding Window Random Linear Code (RLC) Forward [RLC] Roca, V. and B. Teibi, "Sliding Window Random Linear Code
Erasure Correction (FEC) Scheme for FECFRAME", Work (RLC) Forward Erasure Correction (FEC) Scheme for
in Progress, Transport Area Working Group (TSVWG) draft- FECFRAME", Work in Progress, Transport Area Working Group
ietf-tsvwg-rlc-fec-scheme (Work in Progress), May 2018, (TSVWG) draft-ietf-tsvwg-rlc-fec-scheme (Work in
<https://tools.ietf.org/html/ Progress), February 2019, <https://tools.ietf.org/html/
draft-ietf-tsvwg-rlc-fec-scheme>. draft-ietf-tsvwg-rlc-fec-scheme>.
9.2. Informative References 9.2. Informative References
[nc-taxonomy] [nc-taxonomy]
Roca et al., V., "Taxonomy of Coding Techniques for Roca (Ed.) et al., V., "Taxonomy of Coding Techniques for
Efficient Network Communications", draft-irtf-nwcrg- Efficient Network Communications", Request For
network-coding-taxonomy (Work in Progress) (work in Comments RFC 8406, June 2018,
progress), June 2018, <https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-irtf-nwcrg-network-coding-taxonomy/>. draft-irtf-nwcrg-network-coding-taxonomy/>.
Authors' Addresses Authors' Addresses
Vincent Roca Vincent Roca
INRIA INRIA
Univ. Grenoble Alpes Univ. Grenoble Alpes
France France
Email: vincent.roca@inria.fr Email: vincent.roca@inria.fr
 End of changes. 13 change blocks. 
26 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/