Difference between revisions of "Project Proposals/uDPI"

From fd.io
Jump to: navigation, search
(→‎Name)
(→‎Scope)
Line 41: Line 41:
 
         - Integration with other systems
 
         - Integration with other systems
 
-->
 
-->
−
uDPI's main responsibility is to enable communication between its northbound interfaces and VPP's management APIs, performing all necessary translations in the background. It is important to note that many features and utilities will be reused from open source projects and tools (e.g. netopeer2, goahead and openSSL) and will not be a direct part of Sweetcomb. This section is splitted into 2 sections: in-scope and out-of-scope to clearly define what is developed as part of Sweetcomb project and what will be just reused from other projects (or where Sweetcomb relies on other projects).
+
uDPI's main responsibility is to provide a reference framework for Deep Packet Inspection. It will cover below key components:
 +
* Flow classification
 +
** HW flow offloading leveraging rte_flow on DPDK
 +
** SW flow classification
 +
** Supports both ipv4 and ipv6 flows
 +
** Supports Tunnel Traffic Classification
 +
** BD-aware and VRF-aware
 +
** Bi-directional traffic maps to one flow.
  
 +
* Flow expiration
 +
** Timer-based expiration mechanism
 +
** TCP session aware expiration mechanism
  
 +
* TCP segments reassembly
 +
** TCP connection track
 +
** TCP segments reorder
 +
** TCP segments overlap process
 +
 +
* Application Database
 +
** Default static Application Database
 +
** Add new Application rules dynamically
 +
 +
* Application Detection
 +
** Leverage Hyperscan Stream Mode
 +
** Reassembly TCP segments on the fly
 +
 +
* Supported protocols:
 +
** TLS/HTTPS
 +
** HTTP
 +
** DNS
 +
** QUIC
 +
......
  
 
== Initial Committers ==
 
== Initial Committers ==

Revision as of 07:47, 10 July 2019


Name

uDPI

Project Contact Name and Email

Repository Name

udpi

Description

uDPI (Universal Deep Packet Inspection) is a reference framework to provide a high performance solution for Deep Packet Inspection.

We are planning to contribute existing code, and initial code is contributed by Intel.

Scope

uDPI's main responsibility is to provide a reference framework for Deep Packet Inspection. It will cover below key components:

  • Flow classification
    • HW flow offloading leveraging rte_flow on DPDK
    • SW flow classification
    • Supports both ipv4 and ipv6 flows
    • Supports Tunnel Traffic Classification
    • BD-aware and VRF-aware
    • Bi-directional traffic maps to one flow.
  • Flow expiration
    • Timer-based expiration mechanism
    • TCP session aware expiration mechanism
  • TCP segments reassembly
    • TCP connection track
    • TCP segments reorder
    • TCP segments overlap process
  • Application Database
    • Default static Application Database
    • Add new Application rules dynamically
  • Application Detection
    • Leverage Hyperscan Stream Mode
    • Reassembly TCP segments on the fly
  • Supported protocols:
    • TLS/HTTPS
    • HTTP
    • DNS
    • QUIC

......

Initial Committers

Vendor Neutral

No current or expected issues with vendor neutrality.

Meets Board Policy (including IPR, being within Board defined Scope etc)

Meets board policy as expressed in Technical Community Charter and IP Policy

Administrata

  • Request for Project proposal consideration
    • Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
    • Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)
Retrieved from "https://wiki.fd.io/index.php?title=Project_Proposals/uDPI&oldid=9669"