Difference between revisions of "Project Proposals/GPE VPN"
| Line 4: | Line 4: | ||
== Name == | == Name == | ||
| + | <!-- The name of your project, for example Honeycomb BridgeDomain or NSH Advanced Features etc. --> | ||
| + | |||
Options: Programmable VPN / VPN / GPE-VPN / Overlay Manager | Options: Programmable VPN / VPN / GPE-VPN / Overlay Manager | ||
| Line 15: | Line 17: | ||
== Repository Name == | == Repository Name == | ||
| + | <!-- Project Repository Name, should be: | ||
| + | i. Lower case | ||
| + | ii. Short | ||
| + | iii. Suitable for use as a C identifier | ||
| + | --> | ||
<will be chosen depending on the name choice. "pvpn" for programmable VPN?> | <will be chosen depending on the name choice. "pvpn" for programmable VPN?> | ||
| Line 47: | Line 54: | ||
== Scope == | == Scope == | ||
| + | <!-- Project scope. The project scope should be well defined. It should be possible from the scope to crisply answer whether something belongs or not within the scope of this particular project. Scopes should not be overly broad. A Project scope must also lie within the overall scope set by the board for projects in fd.io: | ||
| + | - IO | ||
| + | – Hardware/vHardware <-> threads/cores | ||
| + | - Processing | ||
| + | - Classify | ||
| + | - Transform | ||
| + | - Prioritize | ||
| + | - Forward | ||
| + | - Terminate | ||
| + | - Management Agents | ||
| + | - Control/Manage IO/Processing | ||
| + | - Supporting Projects | ||
| + | - Testing/Tools/Infrastructure | ||
| + | - Integration with other systems | ||
| + | --> | ||
| + | |||
Project scope includes data plane and control plane functions specified in the project description. This includes implementation of modules/nodes that enable dynamic encapsulation and de-capsulation of data packets starting with the GPE encapsulation format, the map cache, and the LISP control plane protocol for retrieval and update of the mapping and forwarding policies. The scope also includes integration with other components within VPP such as IPSec for encryption and NSH. | Project scope includes data plane and control plane functions specified in the project description. This includes implementation of modules/nodes that enable dynamic encapsulation and de-capsulation of data packets starting with the GPE encapsulation format, the map cache, and the LISP control plane protocol for retrieval and update of the mapping and forwarding policies. The scope also includes integration with other components within VPP such as IPSec for encryption and NSH. | ||
== Initial Committers == | == Initial Committers == | ||
| + | <!-- A list of the name/email/IRC nick of the initial project committers | ||
| + | |||
| + | IMPORTANT: Committers should be people who will actually write code, being a committer is an actual commitment of time. Please also note that committerness is an individual trait. If a committer changes employers, they remain a committer. New committers arise via meritocracy after the project is created, this typically involves some time of establishing history of meritocractic code contribution to the project.. Therefore, it is crucial that a committer is committed to ongoing work on the project in the longer term, not just short term. For more information on how committers are added after project creation see: | ||
| + | https://fd.io/sites/cpstandard/files/pages/files/exhibit_c_-_fd.io_technical_community_charter.pdf section 3.2.2.1. | ||
| + | |||
| + | --> | ||
| + | |||
<Committers list TBD> | <Committers list TBD> | ||
== Vendor Neutral == | == Vendor Neutral == | ||
| + | <!-- | ||
| + | The goal here is to capture the degree of vendor neutrality of the code. | ||
| + | The concerns are two fold: avoiding trademark issues, and maintaining openness. | ||
| + | |||
| + | For this reason, use of vendor names should be purely functional, and only if necessary to | ||
| + | reasonably communicate functional information to the user. | ||
| + | |||
| + | Acceptable Examples: | ||
| + | Indicating the presence of particular hardware | ||
| + | Indicating drivers for particular hardware | ||
| + | Indicating integration with particular technologies. | ||
| + | |||
| + | Unacceptable Examples: | ||
| + | Use of vendor trademarks or product names purely for marketing purposes. | ||
| + | |||
| + | Please describe any such issues here. | ||
| + | --> | ||
This projects is vendor neutral and implements/uses open technologies and protocols such as GPE [1], LISP [2], IPSec, NSH [3]. | This projects is vendor neutral and implements/uses open technologies and protocols such as GPE [1], LISP [2], IPSec, NSH [3]. | ||
Revision as of 05:38, 4 March 2016
Contents
Name
Options: Programmable VPN / VPN / GPE-VPN / Overlay Manager
In the rest of this draft the name "Programmable VPN" is used for the project.
Project Contact Name and Email
Florin Coras <fcoras@cisco.com>
Vina Ermagan <vermagan@cisco.com>
Repository Name
<will be chosen depending on the name choice. "pvpn" for programmable VPN?>
Description
Overview
Programmable VPN is project proposal for VPP to enable programmable Software Defined overlays. The Generic Protocol Encapsulation (GPE) [1] will be used as the main encapsulation format. GPE is effectively merging VXLAN and LISP [2] encapsulations in a single format that supports multi-protocol payloads.
Programmable VPN uses an extended LISP-based map-assisted control plane to dynamically lookup forwarding policies on demand. This includes policies such as connectivity, encryption, traffic engineering and virtual topologies, access control, and service chaining. An external open SDN controller will be used as the mapping system to store and provide the mapping and forwarding policies.
Programmable VPN data plane can be secured with IPsec based encryption.
Overlay tunnels, as well as cryptographic parameters, are provisioned on demand.
Data Plane Operations
Programmable VPN core data plane operations include:
- Determining the location of the destination overlay endpoints, encapsulating data packets to the right destination location, and forwarding these packets onto the underlay network.
- De-capsulating encapsulated packets and forwarding the packets towards their associated destinations in the overlay.
To enable dynamic encapsulation a map cache is used that maps flows in the overlay to the location(s) (IP address in the underlay network) of the next hop, or the destination endpoint, depending on the mapping/forwarding policy defined in the mapping system. The map cache would support generic mappings such that the programmable overlay services can be used by a variety of packets and protocols (e.g. L2, L3, NSH [3]) [4]. Multi-homing and load balancing as well as segmentation based on a VNI/IID will be supported.
The map cache is populated on demand using the LISP[4] map-request/map-reply protocol.
Control Plane Operations
Programmable VPN will use the LISP map-request/map-reply protocol to dynamically lookup the mapping and forwarding policy resulting in the location of the next hop associated with this flow. This mapping information is then cached in the map cache for future use. Changes/updates to the cached mappings are pushed to VPP by the mapping system.
Scope
Project scope includes data plane and control plane functions specified in the project description. This includes implementation of modules/nodes that enable dynamic encapsulation and de-capsulation of data packets starting with the GPE encapsulation format, the map cache, and the LISP control plane protocol for retrieval and update of the mapping and forwarding policies. The scope also includes integration with other components within VPP such as IPSec for encryption and NSH.
Initial Committers
<Committers list TBD>
Vendor Neutral
This projects is vendor neutral and implements/uses open technologies and protocols such as GPE [1], LISP [2], IPSec, NSH [3].
Meets Board Policy (including IPR, being within Board defined Scope etc)
Meets board policy as expressed in Technical Community Charter and IP Policy
