doc:rfc_start
This is an old revision of the document!
Table of Contents
Specifications (OOBD-RFCs)
To enable inter-connectivity between the different functionalities of the OOBD tool set, all relevant mechanisms and data structures shall be discussed and then specified as OOBD- RFCs. As RFCs proved them-self in the last decades as well working principle, OOBD-RFC should follow the same rules as described in RFC 2223 in regards of structure, layout and content. Only all item regarding page layout will not be applied, as the OOBD-RFCs will normally be web documents, but no single page printouts.
Release Process
- According to the original RFCs, OOBD-RFCs will follow the same states of discussion and implementation (releasing)
- Informational / Experimental: Hint, idea, message to the community / experimental implementation; first level of a potential standard
- Proposed Standard: Definition finished, waiting for agreement from the OOBD community
- Draft Standard: Implementation phase, final tuning
- Standard: Implemented, content frozen
- Historic – not used anymore
OOBD-RFCs
| Nr | Title | Status |
|---|---|---|
| 1 | The OOBD Development Process | Informational |
| 2 | Firmware Command Syntax | Standard |
| 3 | Embedding multiple files in one | Informational |
| 4 | Encrypting sensible data with PGP | Draft Standard |
| 5 | Lock the OOBD Dongle with a software key against unauthorized use (steal protection) | informational |
| 6 | RTD (Real Time Data) Protocol for the OOBD Firmware | Draft Standard |
| 7 | CANraw Mode Protocol for the OOBD firmware | Draft Standard |
doc/rfc_start.1393650039.txt.gz · Last modified: 2014/03/01 06:00 by admin