izaya/OC-Minitel
1
0
Fork 0
mirror of https://github.com/ShadowKatStudios/OC-Minitel.git synced 2024-11-23 10:38:05 +11:00
Code Issues Releases Wiki Activity

Change broadcast address

Browse Source
This commit is contained in:
Skye 2018-02-18 15:53:12 +00:00 committed by GitHub
parent 938c5fce9d
commit 22777cc709
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
protocol-3.md
View File

@ -34,7 +34,7 @@ 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. 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.
### Optional: Broadcast address ### Optional: Broadcast address
Packets addressed to the broadcast address, an adress of an empty string, can optionally be received by all nodes om 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, an adress of just the tilde character, `~`, ASCII 126, can optionally be received by all nodes om 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.
### Optional: Multicast ### Optional: Multicast
A multicast packet has a specially formatted address part. A multicast packet has a specially formatted address part.
@ -78,7 +78,8 @@ Strings in Minitel packets, with the exception of the data portion, have the fol
- ASCII 127 is not allowed - ASCII 127 is not allowed
- ASCII 128 and above (ie unicode) behavior is undefined and should be used with caution. - 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. 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. The data part of the packet can contain any characters.