Embedding LOOPS in SRv6
draft-wang-loops-srv6-binding-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text 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                                                            J. Wang
Internet-Draft                                                    S. Nie
Intended status: Informational                                    B. Lei
Expires: September 10, 2020                                China Telecom
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                          March 09, 2020

                        Embedding LOOPS in SRv6
                    draft-wang-loops-srv6-binding-00

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.

   Segment Routing (SR) leverages the source routing mechanisms and
   steers the packets through an policy instantiated as an ordered list
   of instructions called segments.  LOOPS can be embedded in an SR
   segment to improve the packet recovery. draft-welzl-loops-gen-info
   defines the generic information model, without binding that to any
   specific protocols, to be carried between LOOPS ingress and egress
   nodes, which can be SR segment endpoints.  This document specifies
   the concrete mechanisms to embed LOOPS in SRv6 segment.

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 September 10, 2020.

Wang, et al.           Expires September 10, 2020               [Page 1]
Internet-Draft                LOOPS in SRv6                   March 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
   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.  LOOPS TLV in SRv6 . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Flags and Flag Based Data . . . . . . . . . . . . . . . .   5
   4.  Embedding LOOPS in SRv6 . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   LOOPS (Local Optimizations on Path Segments) aims to provide local
   in-network loss recovery.  [I-D.li-tsvwg-loops-problem-opportunities]
   shows an overview on the problems that LOOPS could address and some
   use cases where LOOPS can be employed to improve the performance.
   When an end-to-end path contains one or more LOOPS segments, packet
   loss recovery can be performed over such a segment.  Such in-network
   recovery is faster than the end-to-end packet recovery in most cases,
   especially when the LOOPS enabled segment is a small part of the
   entire path in terms of latency, or when it occasionally suffers
   microburst losses.  In addition, with the increasing deployment of
   encrypted transport layer like QUIC, the traditional performance
   enhancing proxies (PEPs, [RFC3135]) are no longer applicable.  LOOPS
   enabled on a network segment can work with no dependency on transport
   layer or higher information.  Thus it can improve performance over a
   path with segments of varying quality.
Show full document text