Bug 589 - NLnet top-level gigabit crypto router 2021-02-052
Summary: NLnet top-level gigabit crypto router 2021-02-052
Status: CONFIRMED
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Milestones (show other bugs)
Version: unspecified
Hardware: PC Linux
: --- enhancement
Assignee: Luke Kenneth Casson Leighton
URL: https://libre-soc.org/crypto_router_a...
Depends on: 770 771 772 773 774 775 776 817
Blocks:
  Show dependency treegraph
 
Reported: 2021-02-06 14:32 GMT by Luke Kenneth Casson Leighton
Modified: 2022-04-21 22:30 BST (History)
4 users (show)

See Also:
NLnet milestone: NLnet.2021.02A.CryptoRouter
total budget (EUR) for completion of task and all subtasks: 50000
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation: 770 771 772 773 774 775 776
The table of payments (in EUR) for this task; TOML format:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Kenneth Casson Leighton 2021-02-06 14:32:23 GMT
APPROVED. Awaiting final review of task list and signing MOU...

We need to first define what one actually want to test and who does what.
Test only functional through JTAG patterns provided to me or full test on ethernet and USB functionality ?
Will there be PCB needed with ethernet PHY and/or USB PHY ?
So budget needed may go from 1000EUR to 5000EUR I would say.

Task list:

# Discussion and Finalisation of Which Cryptographic Primitives to Implement

Discuss and decide on what cryptographic or other primitives are the most beneficial,
simple, or otherwise well-suited for us to implement, since there are too
many in existence for us to implement them all.

Budget: 2000 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=770

# Creation of Cryptographic-Primitive OpenPower ISA Pseudo-code and Associated Unit-Tests

Creation of the pseudo-code for the new instructions we will be creating, as well as
modification of existing pseudo-code, where warranted, for the
purposes of usage as a reference for simulation of the new/modified instructions for
testing purposes, as well as potential submission as one or more proposals
to the OpenPower Foundation as the de-jure reference for how those proposed
new instructions should function. Also, creation/improvement of the unit-tests for the above
referenced pseudo-code.

Budget: 8000 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=771

# Creation of the HDL Code for the Instructions and Associated Unit-Tests

Creation of the HDL code for the instructions used to implement the Cryptographic
Primitives. This may include modification of the implementation of already
existing instructions if needed, in order to improve performance, security,
or other desired qualities. Also, creation of the unit-tests for the
new/changed HDL code, or other related HDL code that needs testing.

Budget: 15000 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=772

# High-Level Demos of Cryptographic and Other Relevant Algorithms

Creation of demonstrations of cryptographic and other relevant
algorithms using our new and/or modified instructions to attempt
to demonstrate improved performance, simplicity, security, and/or
other benefits of our additions and/or modifications.

Budget: 5500 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=773

# Equipment needed, such as FPGA boards and Ethernet PMODs

Purchase of equipment needed for development of the router and related
projects, as well as possible minor development of equipment needed.
Examples of what would be purchased include relatively entry-level FPGA boards and Ethernet PMODs.

Budget: 4000 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=774

# Project Management

Management, and other misc. costs such as maintaining our financial records systems.

Budget: 7500 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=775

# Documentation of designs, code, processes, and other relevant things as needed

In order to make it more likely for our project to be understandable and useful,
documentation of designs, code, processes, and other relevant things is necessary.

Budget: 8000 EUR
URL: https://bugs.libre-soc.org/show_bug.cgi?id=776
Comment 2 Staf Verhaegen 2021-04-24 11:53:19 BST

    
Comment 3 Luke Kenneth Casson Leighton 2021-09-13 15:34:04 BST
Draft instructions partially designed:
https://libre-soc.org/openpower/sv/bitmanip/
Comment 4 Luke Kenneth Casson Leighton 2021-10-22 13:08:38 BST
i've added a TODO/preliminary top-level milestone for documentation
of sky130 and coriolis2, amount TBD.  fortunately as this is
an "approved" task, work can go ahead even though the exact
MoU has not been agreed yet, and budget will be available once
tasks are agreed.
Comment 5 Jacob Lifshay 2022-02-11 23:25:54 GMT
I filled out the description and guessed budgets for the tasks here. Appended to the end of the top comment:
https://bugs.libre-soc.org/show_bug.cgi?id=589#c0

The task list is shorter than I expected (half of the original tasks were apparently moved to NGI POINTER assuming I'm guessing correctly), so imho the budgets may end up somewhat inflated as a result of trying to split 50000 between them...particularly the algorithm demos one...though I could be wrong.
Comment 6 Luke Kenneth Casson Leighton 2022-02-12 13:36:58 GMT
(In reply to Jacob Lifshay from comment #5)
> I filled out the description and guessed budgets for the tasks here.
> Appended to the end of the top comment:
> https://bugs.libre-soc.org/show_bug.cgi?id=589#c0

brilliant. i took off the moved tasks
 
> The task list is shorter than I expected (half of the original tasks were
> apparently moved to NGI POINTER assuming I'm guessing correctly),

yes.

> so imho
> the budgets may end up somewhat inflated as a result of trying to split
> 50000 between them...particularly the algorithm demos one...though I could
> be wrong.

we can compensate by adding 3 new tasks, FPGAs Management and Documentation.
should do the trick.
Comment 7 Jacob Lifshay 2022-02-15 02:46:11 GMT
added the suggested tasks, and rebalanced the budgets. looks good?
Comment 8 Jacob Lifshay 2022-02-15 02:49:26 GMT
(In reply to Luke Kenneth Casson Leighton from comment #6)
> brilliant. i took off the moved tasks

the moved tasks need to be removed from this bug's Depends On list.
Comment 9 Luke Kenneth Casson Leighton 2022-02-15 05:40:12 GMT
hilariousness. all good except "useless" bit :) both Michiel and
EU Auditors will be reading the milestones, try rewording with
a positive spin even if it's blindingly obvious amd bordering
on "filler" words. length is fine, positive or neutral is best
Comment 10 Jacob Lifshay 2022-02-15 05:50:10 GMT
(In reply to Luke Kenneth Casson Leighton from comment #9)
> hilariousness. all good except "useless" bit :)

rephrased:
# Documentation of designs, code, processes, and other relevant things as needed

In order to make it more likely for our project to be understandable and useful,
documentation of designs, code, processes, and other relevant things is necessary.
Comment 11 Jacob Lifshay 2022-02-15 05:55:34 GMT
moved subtasks (that were moved to ngi pointer) to See Also, rather than Depends On list.
Comment 12 Luke Kenneth Casson Leighton 2022-02-15 06:15:29 GMT
(In reply to Jacob Lifshay from comment #10)

> In order to make it more likely for our project to be understandable and
> useful,
> documentation of designs, code, processes, and other relevant things is
> necessary.

perfect. extra bonus points for including bureaucratic phrases like
"promoting outcomes" although that would need conferences or press releases
and blogs and blech realistically it is a new milestone and i think we're
good.

next part literally cutpaste create bugreports, 1st line in title, para
as comment0, then edit *this* comment 0 to include full URL.
full because the text will be dropped verbatim as Schedule A into MoU
Comment 13 Jacob Lifshay 2022-02-15 06:55:40 GMT
(In reply to Luke Kenneth Casson Leighton from comment #12)
> next part literally cutpaste create bugreports, 1st line in title, para
> as comment0, then edit *this* comment 0 to include full URL.
> full because the text will be dropped verbatim as Schedule A into MoU

submitted all the bugs and added links.