LOOPS Generic Information Set
draft-welzl-loops-gen-info-04

Document Type Active Internet-Draft (individual)
Authors Michael Welzl  , Carsten Bormann 
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TSVWG                                                           M. Welzl
Internet-Draft                                        University of Oslo
Intended status: Standards Track                         C. Bormann, Ed.
Expires: 14 January 2021                          Universit├Ąt Bremen TZI
                                                            13 July 2020

                     LOOPS Generic Information Set
                     draft-welzl-loops-gen-info-04

Abstract

   LOOPS (Local Optimizations on Path Segments) aims to provide local
   (not end-to-end but in-network) recovery of lost packets to achieve
   better data delivery in the presence of losses.
   [I-D.li-tsvwg-loops-problem-opportunities] provides an overview over
   the problems and optimization opportunities that LOOPS could address.

   The present document is a strawman for the set of information that
   would be interchanged in a LOOPS protocol, without already defining a
   specific data packet format.

   The generic information set needs to be mapped to a specific
   encapsulation protocol to actually run the LOOPS optimizations.  A
   companion document contains a sketch of a binding to the tunnel
   encapsulation protocol Geneve [I-D.ietf-nvo3-geneve].

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 14 January 2021.

Copyright Notice

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

Welzl & Bormann          Expires 14 January 2021                [Page 1]
Internet-Draft                    LOOPS                        July 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Challenges  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  No Access to End-to-End Transport Information . . . . . .   6
     2.2.  Path Asymmetry  . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Reordering vs. Spurious Retransmission  . . . . . . . . .   6
     2.4.  Informing the End-to-End Transport  . . . . . . . . . . .   7
   3.  Simplifying assumptions . . . . . . . . . . . . . . . . . . .   8
   4.  LOOPS Architecture  . . . . . . . . . . . . . . . . . . . . .   9
   5.  LOOPS Generic Information Set . . . . . . . . . . . . . . . .  10
     5.1.  Setup Information . . . . . . . . . . . . . . . . . . . .  10
     5.2.  Forward Information . . . . . . . . . . . . . . . . . . .  10
     5.3.  Reverse Information . . . . . . . . . . . . . . . . . . .  11
   6.  LOOPS General Operation . . . . . . . . . . . . . . . . . . .  12
     6.1.  Initial Packet Sequence Number  . . . . . . . . . . . . .  12
       6.1.1.  Minimizing collisions . . . . . . . . . . . . . . . .  12
       6.1.2.  Optional Initial PSN procedure  . . . . . . . . . . .  12
     6.2.  Acknowledgement Generation  . . . . . . . . . . . . . . .  13
     6.3.  Measurement . . . . . . . . . . . . . . . . . . . . . . .  14
       6.3.1.  Ingress-relative timestamps . . . . . . . . . . . . .  14
       6.3.2.  ACK generation  . . . . . . . . . . . . . . . . . . .  15
     6.4.  Loss detection and Recovery . . . . . . . . . . . . . . .  15
       6.4.1.  Local Retransmission  . . . . . . . . . . . . . . . .  15
       6.4.2.  FEC . . . . . . . . . . . . . . . . . . . . . . . . .  16
     6.5.  Discussion  . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Sketches of Bindings to Tunnel Protocols  . . . . . . . . . .  16
     7.1.  Embedding LOOPS in Geneve . . . . . . . . . . . . . . . .  17
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
     9.1.  Threat model  . . . . . . . . . . . . . . . . . . . . . .  17
Show full document text