Difference between revisions of "Project Proposals/mmb"
From fd.io
(→Initial Committers) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
== Description == | == Description == | ||
| − | + | mmb is a plugin that intents to implement middlebox policies that can be configured using generic CLI commands. It performs stateless packet matching based on any combination of constraints on network or transport protocol fields, stateful TCP and UDP flow matching, packet rewrite, packet dropping, bidirectionnal mapping. | |
== Scope == | == Scope == | ||
| Line 36: | Line 36: | ||
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: | 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. | https://fd.io/sites/cpstandard/files/pages/files/exhibit_c_-_fd.io_technical_community_charter.pdf section 3.2.2.1. | ||
| − | |||
--> | --> | ||
| + | |||
| + | * [mailto:korian.edeline@uliege.be Korian Edeline] (LF ID: ekorian) | ||
| + | * [mailto:justin.iurman@uliege.be Justin Iurman] | ||
== Vendor Neutral == | == Vendor Neutral == | ||
| Line 57: | Line 59: | ||
Please describe any such issues here. | Please describe any such issues here. | ||
--> | --> | ||
| + | |||
| + | No current or expected issues with vendor neutrality. | ||
| + | |||
== Meets Board Policy (including IPR, being within Board defined Scope etc) == | == Meets Board Policy (including IPR, being within Board defined Scope etc) == | ||
Latest revision as of 10:27, 23 October 2018
Contents
Name
Modular MiddleBox
Project Contact Name and Email
Korian Edeline - korian.edeline@uliege.be
Repository Name
mmb
Description
mmb is a plugin that intents to implement middlebox policies that can be configured using generic CLI commands. It performs stateless packet matching based on any combination of constraints on network or transport protocol fields, stateful TCP and UDP flow matching, packet rewrite, packet dropping, bidirectionnal mapping.
Scope
Initial Committers
- Korian Edeline (LF ID: ekorian)
- Justin Iurman
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)
