izaya/OC-Minitel
1
0
Fork 0
mirror of https://github.com/ShadowKatStudios/OC-Minitel.git synced 2024-12-25 09:58:04 +11:00
Code Issues Releases Wiki Activity

Merge pull request #1 from skyem123/master

Browse Source 
Merge addition of broadcast and multicast to specification
This commit is contained in:
Izaya 2018-02-19 03:02:46 +11:00 committed by GitHub
commit 12432817c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
protocol-3.md
View File

@ -18,6 +18,10 @@ If the packet is, for some reason invalid, simply drop the packet.
### Optional: Meshing
If a message is not addressed to a node, and the node has not seen the packet ID before, the node should repeat it. Whether via the address in the cache or by broadcast, it should be passed on, and the hardware address added to the cache as the sender.
#### Important (Non-Optional) Notes
Broadcast packets MUST NOT be repeated, in order to keep them within the same layer 2 network, unless special precautions are taken.
If a packet is multicast and you don't support multicast, then you SHOULD NOT repeat the packet.
### Optional: Address caching
Each machine should keep a last known route cache. The exact format is up to the implementation, but it will need:
@ -29,9 +33,21 @@ It is recommended to keep the data in the cache for 30 seconds or so, then drop
When sending a message, check the cache for the given destination. If there is a hardware address in the cache for the destination, send the message straight to that address. Otherwise, broadcast the message.
### WIP, Optional: Broadcast address
### Optional: Broadcast address
Packets addressed to the broadcast address, an address of just the tilde character, `~`, ASCII 126, can optionally be received by all nodes of the same layer 2 network. While a node MAY forward a broadcast packet to other nodes, it SHOULD NOT, unless both sides of the forward are prepared to handle such a packet, to avoid it going around the entire layer 3 network.
Packets addressed to the broadcast address (currently undecided) can optionally be received by all nodes.
### Optional: Multicast
A multicast packet has a specially formatted address part.
The address must be a list of valid addresses, seperated by the tilde character, `~`, ASCII 126.
For example, to send to nodes `a` and `b`, the address in the packet would be `a~b`.
Each node should send multicasts as layer 2 broadcasts, unless it is known (using the address cache) that all layer 3 destination addresses have to be sent to or forwarded by one layer 2 address.
When a multicast packet is forwarded, the addresses already seen SHOULD be removed from the packet when possible, using the address cache as a guide.
The same address MUST NOT be repeated in a multicast destination, but the duplicate MAY be ignored and just considered one, but also MAY br dropped as an invalid packet. A duplicate address MUST NOT be considered as two packets with the same contents to the same address.
A multicast packet SHOULD also be able to be broken up into multiple packets with the same contents (but they need different packet IDs!) with different addresses.
### WIP, Optional: Network status packets
@ -62,6 +78,9 @@ Strings in Minitel packets, with the exception of the data portion, have the fol
- ASCII 127 is not allowed
- ASCII 128 and above (ie unicode) behavior is undefined and should be used with caution.
The address part of the packet has a furthur limitatation, the tidle character `~`, ASCII 126, may not be used as an address of a node, but is allowed in the address part as a seperator for multicast.
An address of 0 length (an empty address) MUST be considered invalid and dropped.
The data part of the packet can contain any characters.
### Example exchange: