Power point file is Here

Google doc file is Here

[Note] This is only a place holder for requirement documentation. Current drafting and discussion is done here:

1. The DPACC design must be as high a performing design as possible
2. The DPACC design must proved portability for the applications
3. The DPACC design must be scalability in performance and design
4. All code within the DPACC design must be open sourced with a BSD or MIT like license
   1. The DPACC design must not contain or require proprietary code
   2. The code can not be in binary form and must be in source code form
      1. The only excepted binary form allowed would be firmware that is loaded in the device
5. The DPACC can not use non-upstreamed kernel modules or modifications
   1. The DPACC design can not allow the host kernel to crash by adding a module or kernel modification

1. The API is for the application portability
   1. The applications should not be required to modify the application to follow this API
      1. One example is the current install base of DPDK applications needs to be maintained without require re-writes.
2. Written in a portable language
   1. 'C' is the most common
3. Allow for the best performance of the underlying s-API or Acceleration Core.
   1. Which means to me a very thin layer on top of the s-API to not effect native Acceleration Core performance
4. API must be documented
   1. Do we want Doygen with inline code comments for documenting the API?
5. All code must be open source using a BSD or MIT like license

1. Must follow the standard legacy APIs as close as possible
2. API is for legacy applications portability
3. Written in a port language like C
4. Support a reasonable set of API types sockets, libcrypto, …
5. API must be documented if any differences from the native API
6. All code must be open source using a BSD or MIT like license

1. Need to determine if we need any requirements here