Comparative Analysis of MTU overhead in the context of SPRING
draft-dukes-spring-mtu-overhead-analysis-01

Abstract

This document provides an apples-to-apples comparative analysis of MTU overhead in the context of SPRING.

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 March 18, 2019.

Copyright Notice

Copyright (c) 2018 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
• 1.1. Stateless IPv6 Encapsulation Within a VPN Context
• 1.1.1. Analysis of MTU overhead
• 2. Informative References
• Authors' Addresses

1. Introduction

This document provides an apples-to-apples comparative analysis of MTU overhead in the context of SPRING.

The first version of this document concentrates on stateless IPv6 encapsulation within a VPN context.

1.1. Stateless IPv6 Encapsulation Within a VPN Context

A VPN context provides routing and forwarding isolation at interface granularity on a Provider Edge (PE) node.

Encapsulation between PE nodes is used to forward traffic between the VPN contexts of remote nodes. Typically, this encapsulation encodes the remote node address and VPN context.

Stateless encapsulation requires no additional state be propagated between PE and provider (P) nodes.

1.1.1. Analysis of MTU overhead

VXLAN [RFC7348], LISP [RFC6830], GTP and SRv6 [I-D.filsfils-spring-srv6-network-programming] encapsulations are considered as they provide stateless encapsulation while supporting VPN contexts.

VXLAN, LISP, and GTP encapsulate all add VPN context via UDP.

• VXLAN: 56 bytes : IPv6(40) + UDP(8) + VXLAN(8)
• LISP: 56 bytes : IPv6(40) + UDP(8) + LISP(8)
• GTP: 56 bytes : IPv6(40) + UDP(8) + GTP(8)

SRv6 encapsulates and includes the VPN context with the destination SID.

• SRv6: 40 bytes : IPv6(40)

The SRv6 VPN SID encodes location and VPN context so IPv6 encapsulation is all that's required for the SRv6 case, i.e. there is no Segment Routing Extension Header (SRH) [I-D.ietf-6man-segment-routing-header] required.

SRv6 results in a lower overhead than VXLAN, LISP, and GTP for stateless encapsulation within a VPN context.

2. Informative References

Authors' Addresses