SRH Extension for Redundancy Protection
draft-geng-spring-redundancy-protection-srh-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                            X. Geng
Internet-Draft                                                   M. Chen
Intended status: Experimental                                     Huawei
Expires: September 10, 2020                               March 09, 2020

                SRH Extension for Redundancy Protection
             draft-geng-spring-redundancy-protection-srh-00

Abstract

   Redundancy protection is a method of service protection by sending
   copies of the same packets of one flow over multiple paths, which
   includes packet replicaiton, elimination and ordering.  This document
   defines SRv6 header(SRH) extensions to support redundancy protection.

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

Geng & Chen            Expires September 10, 2020               [Page 1]
Internet-Draft              Abbreviated-Title                 March 2020

   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 . . . . . . . . . . . . . . . . .   2
   3.  Redundancy Protection Requirement Analysis  . . . . . . . . .   3
   4.  SRH Extensions for Redundancy Protection  . . . . . . . . . .   3
     4.1.  Option 1: seperated TLVs for flow identification and
           sequence number . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Option 2 unified TLV for flow identification and sequence
           number  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Redundancy protection is a method of providing 1+1 protection by
   sending copies of the same packets of one flow over multiple paths,
   which includes packet replicaiton, elimination and ordering.  This
   document defines SRv6 header(SRH) extensions to support redundancy
   protection.

2.  Terminology and Conventions

   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 [RFC2119].

   Redundancy Node: the start point of redudancy protection, which is a
   network device that could implement packet replication.

   Merging Node: the end point of redudancy protection, which is a
   network node that could implement packet elimination and
   ordering(optionally).

   Editor's Note: Similar mechanism is defined as "Service Protection"
   in the [RFC8655].  In this document, we define a new term "Redundancy
   Protection" to distinguish with other service protection method.
   Some of the terms are the similar as [RFC8655].

Geng & Chen            Expires September 10, 2020               [Page 2]
Internet-Draft              Abbreviated-Title                 March 2020

3.  Redundancy Protection Requirement Analysis

   The figure shows how to provide redundancy protection over SRv6.

                |                                         |
    ----IPv6--->|<---------------SRv6 Domain------------->|<----IPv6---
                |                                         |
Show full document text