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

The information below is for an old version of the document
Document Type Active Internet-Draft (spring WG)
Last updated 2019-11-12 (latest revision 2019-10-11)
Replaces draft-voyer-spring-sr-p2mp-policy
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state Candidate for WG Adoption
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: April 13, 2020                                        R. Parekh
                                                     Cisco Systems, Inc.
                                                              H. Bidgoli
                                                                   Nokia
                                                                Z. Zhang
                                                        Juniper Networks
                                                        October 11, 2019

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

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 April 13, 2020.

Voyer, Ed., et al.       Expires April 13, 2020                 [Page 1]
Internet-Draft           SR Replication Segment             October 2019

Copyright Notice

   Copyright (c) 2019 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.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

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 replicates packets directly to each egress node of the
   service, without need for any state in the core of SR domain.
   Multiple Replication segments can be stitched together to build a
   tree in SR domain for Multi-point service; this is outside the scope
   of this document.

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
   node or programmed by a PCE.  Replication segments apply equally to
   both SR-MPLS and SRv6 instantiations of Segment Routing.

Voyer, Ed., et al.       Expires April 13, 2020                 [Page 2]
Internet-Draft           SR Replication Segment             October 2019

   A Replication segment is identified by the tuple <Replication-ID,
   Node-ID>, where:

   o  Replication-ID: An identifier for a Replication segment that is
      unique in context of the Replication node.  This is an unsigned
      32-bit number.

   o  Node-ID: The address of a node at which a Replication segment is
Show full document text