Analysis Framework For Extensions of SRv6 Encapsulation
draft-filsfils-spring-analysis-fmwk-ext-srv6-encap-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                        C. Filsfils
Internet-Draft                                             D. Dukes, Ed.
Intended status: Informational                       Cisco Systems, Inc.
Expires: July 20, 2020                                          K. Patel
                                                            Arrcus, Inc.
                                                        January 17, 2020

        Analysis Framework For Extensions of SRv6 Encapsulation
         draft-filsfils-spring-analysis-fmwk-ext-srv6-encap-00

Abstract

   This document provides a framework for analysis of multiple proposals
   to extend SRv6 encapsulation with the objective of minimizing
   encapsulation size or leveraging legacy equipment.  It defines
   relevant metrics to evaluate each proposal.

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 July 20, 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

Filsfils, et al.          Expires July 20, 2020                 [Page 1]
Internet-Draft         SRv6 Encapsulation Analysis          January 2020

   (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.  Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Compliance  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Data Plane Efficiency . . . . . . . . . . . . . . . . . .   4
     2.3.  State Efficiency  . . . . . . . . . . . . . . . . . . . .   4
     2.4.  Encapsulation Size  . . . . . . . . . . . . . . . . . . .   4
   3.  Variables For Metrics . . . . . . . . . . . . . . . . . . . .   4
   4.  Analysis of Proposals . . . . . . . . . . . . . . . . . . . .   5
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Traffic traversing an SR domain is encapsulated in an outer IPv6
   header with an optional Segment Routing Header (SRH) for its journey
   through the SR domain [I-D.ietf-6man-segment-routing-header].

   This document provides a framework for analysis of multiple proposals
   to extend SRv6 encapsulation with the objective of minimizing
   encapsulation size or leveraging legacy equipment.  It defines
   relevant metrics to evaluate each proposal.

   Future revisions will evaluate and document the metrics for each
   proposal, compare them and draw conclusions.

2.  Metrics

   Metrics are identified as metric:score.  Metric is the abbreviation
   of the metric name, and score is an integer reporting its evaluation.
   A proposal with a metric (M) and score of zero is represented as M:0.

   A score may vary based on the number and type of instructions in a
   segment list.  Three types of segments are considered: T for
   topological, S for service, and V for VPN.

   A proposal with a metric (M), computed for a segment list of 5
   topological segments followed by 1 VPN segment, with a score of 10 is
   represented as M(5T.1V):10.

Filsfils, et al.          Expires July 20, 2020                 [Page 2]
Internet-Draft         SRv6 Encapsulation Analysis          January 2020

   A score may vary based on node parameters.  Three parameters are
   considered: N the number of nodes in the network, I the number of IGP
   algorithms [I-D.ietf-lsr-flex-algo] configured at the node, and A the
   number of adjacency SIDs configured at the node.

   A proposal with metric (M), computed for a node in a network of 100