Embedding LOOPS in Geneve
draft-bormann-loops-geneve-binding-01

Document Type Active Internet-Draft (individual)
Author Carsten Bormann 
Last updated 2020-06-12
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)
loops                                                         C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Standards Track                            12 June 2020
Expires: 14 December 2020

                       Embedding LOOPS in Geneve
                 draft-bormann-loops-geneve-binding-01

Abstract

   LOOPS (Local Optimizations on Path Segments) aims to provide local
   in-network loss recovery.  It can be used with tunneling protocols to
   efficiently recover lost packets on a single segment of an end-to-end
   path instead of leaving recovery to the end-to-end protocol,
   traversing the entire path.

   [I-D.welzl-loops-gen-info] defines the information to be carried
   between LOOPS ingress and egress nodes in a generic way, giving a
   guideline on defining the common elements to embed LOOPS functions in
   various tunnel protocols.  The present document specifies how to
   embed LOOPS in the overlay tunnel protocol chosen for the initial
   LOOPS specification, 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 December 2020.

Copyright Notice

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

Bormann                 Expires 14 December 2020                [Page 1]
Internet-Draft            Embed LOOPS in Geneve                June 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Geneve LOOPS Frame Format . . . . . . . . . . . . . . . . . .   3
     3.1.  Flags and Flag Based Data . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Geneve Option Class . . . . . . . . . . . . . . . . . . .   6
     5.2.  LOOPS Geneve Type Numbers . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   LOOPS (Local Optimizations on Path Segments) aims to provide local
   in-network loss recovery.  The LOOPS problems and opportunities draft
   [I-D.li-tsvwg-loops-problem-opportunities] illustrates some typical
   scenarios where LOOPS are applicable.  One way to use LOOPS is to map
   it onto a tunnel protocol.  The path segment on which LOOPS is
   applied then is a tunnel, which can be an existing one or created on
   purpose.

   LOOPS allows the packet loss recovery to be performed over specific
   segments instead of end-to-end, enabling faster and more reliable
   data delivery.  [I-D.welzl-loops-gen-info] defines the information to
   be carried between LOOPS ingress and egress nodes in a generic way,
   giving a guideline on defining the common elements to embed LOOPS
   functions in various tunnel protocols.

Bormann                 Expires 14 December 2020                [Page 2]
Internet-Draft            Embed LOOPS in Geneve                June 2020

   Geneve [I-D.ietf-nvo3-geneve] is an encapsulation protocol that can
   be used to create overlay tunnels.  It defines an extensible TLV
   structure to carry so-called "tunnel options".  The present document
   employs this flexibility, specifying how to embed LOOPS in Geneve.
   This specification covers the format and Geneve-specific procedures
   only: the actual LOOPS function and procedures are defined in
Show full document text