NVO3 Requirements Versus Available Protocol Capabilities
draft-chen-nvo3-gap-analysis-00

Abstract

This document matches candidate protocols against the NVO3 requirements. Based on the results, gaps are identified and further protocol work is recommended.

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 http://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 October 13, 2013.

Copyright Notice

Copyright (c) 2013 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 (http://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. Requirements Language
• 1.2. Abbreviations
• 2. Management Requirements
• 3. Control Plane Requirements
• 4. Data Plane Requirements
• 5. Summary and Conclusions
• 6. Acknowledgements
• 7. IANA Considerations
• 8. Security Considerations
• 9. References
• 9.1. Normative References
• 9.2. Informative References
• Authors' Addresses

1. Introduction

The charter of the NVO3 Working Group requires it to identify any gaps between the requirements it has identified and the available protocol solutions as a prerequisite to rechartering or concluding the Working Group if no gaps exist. The present document is intended to provide the required analysis. It provides a tabulation of the candidate protocols' ability to satisfy each requirement identified by the Working Group. Areas where further work is required to ensure that the requirements are met are identified.

Since the Working Group has yet to adopt documents describing requirements for the management and control planes, they are absent from the present version of this document. The data plane requirements are taken from [I_D.dataplane_requirements]. The initial candidate protocols are NVGRE [I_D.NVGRE], VxLAN [I_D.VxLAN], L2VPN [reference?], and L3VPN [reference?].

1.1. 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].

1.2. Abbreviations

This document uses the following abbreviations:

NVO3:

Network virtualization overlays

L2VPN

Layer 2 virtual private network

L3VPN

Layer 3 virtual private network

NVE:

Network virtualization edge

VAP:

Virtual access point

VNI:

Virtual network instance

LAG:

Link aggregation group

ECMP:

Equal cost multi-path

DSCP:

Differentiated services code point

ECN:

Explicit congestion notification [RFC3168]

2. Management Requirements

To come.

3. Control Plane Requirements

To come.

4. Data Plane Requirements

In this section, the numbering of requirement headings is taken from the corresponding section numbers in [I_D.dataplane_requirements].

3.1. Virtual Access Points (VAPs)