| < draft-ietf-nvo3-encap-02.txt | draft-ietf-nvo3-encap-03.txt > | |||
|---|---|---|---|---|
| INTERNET-DRAFT Sami Boutros(Ed.) | INTERNET-DRAFT Sami Boutros(Ed.) | |||
| Intended Status: Informational VMware | Intended Status: Informational VMware | |||
| Expires: March 18, 2019 September 14, 2018 | Expires: January 2, 2020 July 1, 2019 | |||
| NVO3 Encapsulation Considerations | NVO3 Encapsulation Considerations | |||
| draft-ietf-nvo3-encap-02 | draft-ietf-nvo3-encap-03 | |||
| Abstract | Abstract | |||
| As communicated by WG Chairs, the IETF NVO3 chairs and Routing Area | As communicated by WG Chairs, the IETF NVO3 chairs and Routing Area | |||
| director have chartered a design team to take forward the | director have chartered a design team to take forward the | |||
| encapsulation discussion and see if there is potential to design a | encapsulation discussion and see if there is potential to design a | |||
| common encapsulation that addresses the various technical concerns. | common encapsulation that addresses the various technical concerns. | |||
| There are implications of different encapsulations in real | There are implications of different encapsulations in real | |||
| environments consisting of both software and hardware implementations | environments consisting of both software and hardware implementations | |||
| skipping to change at page 2, line 4 ¶ | skipping to change at page 1, line 44 ¶ | |||
| other groups may also distribute working documents as | other groups may also distribute working documents as | |||
| Internet-Drafts. | Internet-Drafts. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/1id-abstracts.html | http://www.ietf.org/1id-abstracts.html | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html | http://www.ietf.org/shadow.html | |||
| Copyright and License Notice | Copyright and License Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2019 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 3, line 15 ¶ | skipping to change at page 3, line 11 ¶ | |||
| 10.2 Informative References . . . . . . . . . . . . . . . . . . 15 | 10.2 Informative References . . . . . . . . . . . . . . . . . . 15 | |||
| 11. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 15 | 11. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 11.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 15 | 11.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 11.2. Extensibility . . . . . . . . . . . . . . . . . . . . . . 15 | 11.2. Extensibility . . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 11.2.1. Native Extensibility Support . . . . . . . . . . . . 15 | 11.2.1. Native Extensibility Support . . . . . . . . . . . . 15 | |||
| 11.2.2. Extension Parsing . . . . . . . . . . . . . . . . . . 15 | 11.2.2. Extension Parsing . . . . . . . . . . . . . . . . . . 15 | |||
| 11.2.3. Critical Extensions . . . . . . . . . . . . . . . . . 16 | 11.2.3. Critical Extensions . . . . . . . . . . . . . . . . . 16 | |||
| 11.2.4. Maximal Header Length . . . . . . . . . . . . . . . . 16 | 11.2.4. Maximal Header Length . . . . . . . . . . . . . . . . 16 | |||
| 11.3. Encapsulation Header . . . . . . . . . . . . . . . . . . 16 | 11.3. Encapsulation Header . . . . . . . . . . . . . . . . . . 16 | |||
| 11.3.1. Virtual Network Identifier (VNI) . . . . . . . . . . 16 | 11.3.1. Virtual Network Identifier (VNI) . . . . . . . . . . 16 | |||
| 11.3.2. Next Protocol . . . . . . . . . . . . . . . . . . . . 17 | 11.3.2. Next Protocol . . . . . . . . . . . . . . . . . . . . 16 | |||
| 11.3.3. Other Header Fields . . . . . . . . . . . . . . . . . 17 | 11.3.3. Other Header Fields . . . . . . . . . . . . . . . . . 17 | |||
| 11.4. Comparison Summary . . . . . . . . . . . . . . . . . . . 17 | 11.4. Comparison Summary . . . . . . . . . . . . . . . . . . . 17 | |||
| Authors' Addresses (In alphabetical order) . . . . . . . . . . . . 18 | Authors' Addresses (In alphabetical order) . . . . . . . . . . . . 18 | |||
| 1. Problem Statement | 1. Problem Statement | |||
| As communicated by WG Chairs, the NVO3 WG charter states that it may | As communicated by WG Chairs, the NVO3 WG charter states that it may | |||
| produce requirements for network virtualization data planes based on | produce requirements for network virtualization data planes based on | |||
| encapsulation of virtual network traffic over an IP-based underlay | encapsulation of virtual network traffic over an IP-based underlay | |||
| data plane. Such requirements should consider OAM and security. Based | data plane. Such requirements should consider OAM and security. Based | |||
| skipping to change at page 18, line 46 ¶ | skipping to change at page 18, line 43 ¶ | |||
| +----------------+----------------+----------------+----------------+ | +----------------+----------------+----------------+----------------+ | |||
| | Reserved bits | 14 bits | - | 27 bits | | | Reserved bits | 14 bits | - | 27 bits | | |||
| +----------------+----------------+----------------+----------------+ | +----------------+----------------+----------------+----------------+ | |||
| Figure 1: NVO3 Encapsulation Comparison | Figure 1: NVO3 Encapsulation Comparison | |||
| Authors' Addresses (In alphabetical order) | Authors' Addresses (In alphabetical order) | |||
| Sami Boutros | Sami Boutros | |||
| VMware | VMware | |||
| Email: sboutros@vmware.com | Email: boutross@vmware.com | |||
| Ilango Ganga | Ilango Ganga | |||
| Intel | Intel | |||
| Email: ilango.s.ganga@intel.com | Email: ilango.s.ganga@intel.com | |||
| Pankaj Garg | Pankaj Garg | |||
| Microsoft | Microsoft | |||
| Email: pankajg@microsoft.com | Email: pankajg@microsoft.com | |||
| Rajeev Manur | Rajeev Manur | |||
| Broadcom | Broadcom | |||
| Email: rajeev.manur@broadcom.com | Email: rajeev.manur@broadcom.com | |||
| Tal Mizrahi | Tal Mizrahi | |||
| Marvell | Marvell | |||
| End of changes. 7 change blocks. | ||||
| 5 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||