Rednet Protocol

[ghost]

here I restert the pull request for the rednet prorocol

[viluon]

meta This PR is a fix of the mess at #44.

[oeed]

Just a few formatting fixes @justsomeoneelseagain:

• All the table column and row names need to be capitalised (i.e. 'Transmission Method' not 'transmission method') and the other cells should begin with a capital letter (i.e. 'The target computer...' not 'the target computer...')
• Any number values, variable types and variable names need to have backwards ticks around them so they're formatted like this:65535` Nice work, I see you've actually already done that since I wrote this, maybe just add it around things like table and number too.

Again, I'm not at all knowledgable about Rednet, but can you explain the 'short name' and 'protocol ID'? Are they specified/used by anything particularly?

[ghost]

@oeed protocol ID is invented by me and supposed to be something like a MIME-Type for protocols. The short name is just a short variant of the name and the long is only words e.g. HTTP - Hyper Text Transfer Protocol , but the commonly used Name is HTTP, and the protocol is always referred in programming as http

[Luca0208]

This looks nice :+1:

[oeed]

@justsomeoneelseagain okay, we might need to decide whether they're needed. I can see benefits of having them, but we need to get that communication template #45 going.

[ghost]

@oeed , ok, short and long names are not really needed, but we need something to identify protocols (and it has to be a string)

I´ll work on a Template as soon as this got accepted and then PR some more Protocols

[oeed]

I'd say remove Short Name but keep Protocol ID.

This won't be accepted until a template is made and accepted so we don't need to update it. If you're going to make it, base it heavily off the file format template and only change what's needed.

[lyqyd]

"The data to be transmitted, specified by the protocol"

Should this not be the sender specifying the message? I'm not even sure what you're trying to say here.

This is also not a great naming scheme for this standard, since one would want to create standards for individual protocols intended to be transmitted over rednet, like TRoR. We can call both of them protocols, but we then ought to make distinctions between transmission/transport protocols (like Rednet, GPS, or LyqydNet) and data protocols (like TRoR).

[oeed]

Yes actually that's quite true @lyqyd, this isn't a protocol but a method of transmission. @justsomeoneelseagain I'd just remove any references where you have called this a protocol. This also means removing the protocol ID.

[ghost]

I agree, Rednet isn´t a Protocol, the whole document has to be written new from scratch, I won´t do that.