SR Replication Segment for Multi-point Service Delivery
draft-voyer-spring-sr-replication-segment-03

The information below is for an old version of the document
Document Type Active Internet-Draft (candidate for spring WG)
Authors Daniel Voyer  , Clarence Filsfils  , Rishabh Parekh  , Hooman Bidgoli  , Zhaohui Zhang 
Last updated 2020-06-22 (latest revision 2020-06-01)
Replaces draft-voyer-spring-sr-p2mp-policy
Replaced by draft-ietf-spring-sr-replication-segment
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      D. Voyer, Ed.
Internet-Draft                                               Bell Canada
Intended status: Standards Track                             C. Filsfils
Expires: December 3, 2020                                      R. Parekh
                                                     Cisco Systems, Inc.
                                                              H. Bidgoli
                                                                   Nokia
                                                                Z. Zhang
                                                        Juniper Networks
                                                            June 1, 2020

        SR Replication Segment for Multi-point Service Delivery
              draft-voyer-spring-sr-replication-segment-03

Abstract

   This document describes the SR Replication segment for Multi-point
   service delivery.  A SR Replication segment allows a packet to be
   replicated from a replication node to downstream nodes.

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

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 December 3, 2020.

Voyer, Ed., et al.      Expires December 3, 2020                [Page 1]
Internet-Draft           SR Replication Segment                June 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.  Replication Segment . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   We define a new type of segment for Segment Routing [RFC8402], called
   Replication segment, which allows a node (henceforth called as
   Replication Node) to replicate packets to a set of other nodes
   (called Downstream Nodes) in a Segment Routing Domain.  Replication
   segments provide building blocks for Point-to-Multi-point Service
   delivery.  A Replication segment at ingress node of Multi-point
   service could replicates packets directly to each egress node of the
   service (without need for any state on the internal routers), or it
   could be stitched to other Replication segments to build a tree in SR
   domain for Multi-point service.  The latter is outside the scope of
   this document but specified in [I-D.voyer-pim-sr-p2mp-policy].

2.  Replication Segment

   In a Segment Routing Domain, a Replication segment is a logical
   segment which connects a Replication Node to a set of Downstream
   Nodes.  A Replication segment can be either provisioned locally on a

Voyer, Ed., et al.      Expires December 3, 2020                [Page 2]
Internet-Draft           SR Replication Segment                June 2020

   node or programmed by a PCE.  Replication segments apply equally to
   both SR-MPLS and SRv6 instantiations of Segment Routing.
Show full document text