From: Alberto Leiva Popper Date: Fri, 17 May 2024 19:04:22 +0000 (-0600) Subject: Add roadmap to the site X-Git-Tag: 1.6.2~9 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=aa5de49d7f670af26b120ad0b55c4008404d3b42;p=thirdparty%2FFORT-validator.git Add roadmap to the site Still not referenced by the index; needs discussion still. --- diff --git a/docs/css/screen.css b/docs/css/screen.css index bde9bee0..d072983a 100644 --- a/docs/css/screen.css +++ b/docs/css/screen.css @@ -544,4 +544,21 @@ div.highlighter-rouge{ table { margin-bottom: 1rem; -} \ No newline at end of file +} + +.urgency-low { + color: cyan; +} +.urgency-medium { + color: yellow; +} +.urgency-high { + color: orange; +} +.urgency-very-high { + color: red; +} +.urgency-critical { + color: magenta; + font-weight: bold; +} diff --git a/docs/roadmap.md b/docs/roadmap.md new file mode 100644 index 00000000..ba10e040 --- /dev/null +++ b/docs/roadmap.md @@ -0,0 +1,43 @@ +--- +title: Roadmap +--- + +# Roadmap + + + +| Issue | Title | Urgency | Due release | +|-------|-------|---------|-------------| +| [issue122](https://github.com/NICMx/FORT-validator/issues/122) | New invocation mode: Decode and print RPKI file in standard output | Very High | 1.6.2 | +| [issue82](https://github.com/NICMx/FORT-validator/issues/82) | Reach 100% RFC 9286 compliance | Critical | 1.6.3 | +| [issue112](https://github.com/NICMx/FORT-validator/issues/112) | Enforce same origin for RRDP files | High | 1.6.3 | +| [issue113](https://github.com/NICMx/FORT-validator/issues/113) | Detect and properly respond to subtler RRDP session desynchronization | Medium | 1.6.3 | +| [issue50](https://github.com/NICMx/FORT-validator/issues/50) | Provide prometheus endpoint | Very High | - | +| [issue58](https://github.com/NICMx/FORT-validator/issues/58) | Fort's validation produces no router keys | Very High | - | +| [issue74](https://github.com/NICMx/FORT-validator/issues/74) | Kill rsync if a timeout is exceeded | Very High | - | +| [issue114](https://github.com/NICMx/FORT-validator/issues/114) | Support automatic TA key rollover | Very High | - | +| [issue116](https://github.com/NICMx/FORT-validator/issues/116) | SLURM review | High | - | +| [issue118](https://github.com/NICMx/FORT-validator/issues/118) | Implement validation re-reconsidered | High | - | +| [issue119](https://github.com/NICMx/FORT-validator/issues/119) | Review IRIs to file names transition | High | - | +| [issue120](https://github.com/NICMx/FORT-validator/issues/120) | Error messages review | High | - | +| [issue121](https://github.com/NICMx/FORT-validator/issues/121) | Refactor validation and operation logging | High | - | +| [issue72](https://github.com/NICMx/FORT-validator/issues/72) | Encrypt RTR | Medium | - | +| [issue73](https://github.com/NICMx/FORT-validator/issues/73) | Minimize probability of RTR session ID and serial reuse | Medium | - | +| [issue90](https://github.com/NICMx/FORT-validator/issues/90) | Add "metadata" section to json output | Medium | - | +| [issue91](https://github.com/NICMx/FORT-validator/issues/91) | Add "ta" field to ROAs in json output | Medium | - | +| [issue97](https://github.com/NICMx/FORT-validator/issues/97) | Add "incidence" fields for every nonfatal RFC incompliance | Medium | - | +| [issue117](https://github.com/NICMx/FORT-validator/issues/117) | Warn on maxLength defined on SLURM | Medium | - | +| [issue124](https://github.com/NICMx/FORT-validator/issues/124) | Atomize output files (`--output.roa` and `--output.bgpsec`) | Medium | - | +| [issue125](https://github.com/NICMx/FORT-validator/issues/125) | ASN.1 review | Medium | - | +| [issue126](https://github.com/NICMx/FORT-validator/issues/126) | Exhaustive URL validation | Medium | - | +| [issue127](https://github.com/NICMx/FORT-validator/issues/127) | Stream RRDP files | Medium | - | +| [issue128](https://github.com/NICMx/FORT-validator/issues/128) | Reuse TCP connections for HTTP requests to same server | Medium | - | +| [issue129](https://github.com/NICMx/FORT-validator/issues/129) | Rethink the thread pools | Medium | - | +| [issue130](https://github.com/NICMx/FORT-validator/issues/130) | Improve documentation | Medium | - | +| [issue40](https://github.com/NICMx/FORT-validator/issues/40) | failure scenarios, monitoring and glibc recommendations | Low | - | +| [issue42](https://github.com/NICMx/FORT-validator/issues/42) | reload feature: restart validation on SIGHUP | Low | - | +| [issue70](https://github.com/NICMx/FORT-validator/issues/70) | Do a quick temporary offline validation to prevent `No Data Available` | Low | - | +| [issue123](https://github.com/NICMx/FORT-validator/issues/123) | New invocation mode: Validate single file | Low | - | +| [issue131](https://github.com/NICMx/FORT-validator/issues/131) | Implement vCard validation | Low | - | +| [issue132](https://github.com/NICMx/FORT-validator/issues/132) | Implement RTRv2 | Low | - | +