Segment Routing for Redundancy Protection
draft-geng-spring-sr-redundancy-protection-00

Document Type Active Internet-Draft (individual)
Authors Xuesong Geng  , Mach Chen  , Fan Yang 
Last updated 2020-11-02
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)
SPRING Working Group                                             X. Geng
Internet-Draft                                                   M. Chen
Intended status: Standards Track                                 F. Yang
Expires: May 6, 2021                                 Huawei Technologies
                                                        November 2, 2020

               Segment Routing for Redundancy Protection
             draft-geng-spring-sr-redundancy-protection-00

Abstract

   Redundancy protection is one of the mechanisms to achieve service
   protection, following the principle of PREOF (Packet Replication/
   Elimination/Ordering Function).  To empower the Segment Routing with
   the capability of redundancy protection, two types of Segment
   including Redundancy Segment and Merging Segment are introduced.  The
   instantiation of Redundancy and Merging Segments can be applied to
   both segment routing over MPLS (SR-MPLS) and segment routing over
   IPv6 (SRv6).

Requirements Language

   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 .

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 May 6, 2021.

Geng, et al.               Expires May 6, 2021                  [Page 1]
Internet-Draft                                             November 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 and Conventions . . . . . . . . . . . . . . . . .   3
   3.  Redundancy Protection in Segment Routing Scenario . . . . . .   3
   4.  Segment to Support Redundancy Protection  . . . . . . . . . .   4
     4.1.  Redundancy Segment  . . . . . . . . . . . . . . . . . . .   5
     4.2.  Merging Segment . . . . . . . . . . . . . . . . . . . . .   5
   5.  Meta Information to Support Redundancy Protection . . . . . .   6
   6.  Segment Routing Policy to Support Redundancy Protection . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Service protection defined in [RFC8655] is initially required from
   the use cases in a variety of industries described in [RFC8578].
   Together with other two techniques Resource allocation and Explicit
   routes, targets to provide the deterministic flow transmission.
   Meanwhile, with the emerge of Cloud VR, Cloud Game, HDV (high-
   definition video) applications running in the Internet, SLA (Service
   Level Agreement) guarantee becomes an important issue which requires
   new technologies and solutions for network.

   Redundancy Protection is one of the mechanisms to achieve service
   protection, following the principle of PREOF (Packet Replication/
   Elimination/Ordering Function) defined in [RFC8655].  Specifically,
   replicates the packets of flows into two or more copies, transports

Geng, et al.               Expires May 6, 2021                  [Page 2]
Internet-Draft                                             November 2020

   different copies through different path in parallel, eliminates and
   orders the packets at end to provide redundancy protection.
Show full document text