Sources:
RFC 349:
Socket Assignment
1 [Old] Telnet
3 [Old] File Transfer
5 Remote Job Entry
7 Echo
9 Discard
The act of trying to connect an even socket to another even socket, or an odd socket to another odd socket, was considered a "peculiar error" called "homosocketuality", which was strictly forbidden by internet protocols, and mandatory "heterosocketuality" was called the "Anita Bryant feature" [2].
http://www.saildart.org/IMPSER.DOC[SS,SYS]
When the error code is zero, the next 8 bit byte is the Stanford peculiar error code, followed by 72 bits of the ailing command returned. Here are the Stanford error codes. [...]
IGN 3 Illegal Gender (Anita Bryant feature--sockets must be heterosocketual, ie. odd to even and even to odd) [...]
Illegal gender in RFC, host hhh/iii, link 0
The host is trying to engage us in homosocketuality. Since this is against the laws of God and ARPA, we naturally refuse to consent to it.
http://www.saildart.org/FTP.NCP[S,NET]
; Try to initiate connection
loginj:
init log,17
sixbit /IMP/
0
jrst noinit
setzm conecb
setom conecb+lsloc
move ac3,hostno
movem ac3,conecb+hloc
setom conecb+wfloc
movei ac3,40
movem ac3,conecb+bsloc
move ac3,consck
trnn ac3,1
jrst gayskt ; only heterosocketuals can win!
movem ac3,conecb+fsloc
mtape log,[
=15
byte (6) 2,24,0,7,7
] ; Time out CLS, RFNM, RFC, and INPut
[...]
gayskt: outstr [asciz/Homosocketuality is prohibited (the Anita Bryant feature)
/]
ife rsexec,<jrst rstart;>exit 1,
I don't know why he uses two accounts!
Whenever I plagiarize myself, I try to check the links and refine the text to keep it relevant.
Just posting a link to an old article requires less effort for me, but more effort for other people to switch context, navigate and read. And a server's disk space and bandwidth aren't as precious as a reader's time and effort.
It was not my intention to trigger mdekkers into having fits about SJWs, or shocking paxcoder who is not a gay supporter.
I suggest however that when you do, you add a line to the bottom that says something along the line "This comment was based on an earlier comment I made X days ago using another account." when you do just to keep people from accusing you of plagiarizing others.
HTTP Streaming e.g. is only there to artificially keep traffic numbers up by factor 3 but has not much technical justification, other than fix a broken RTSP negotiation.
For example if you telephone with somebody over SIP you will be assigned two UDP numbers (RTP is UDP), you at an even number and the return stream on the next odd number. You don't care if each and every audio frame is ACK'ed. That's why sometimes someone can hear you, but you cannot hear them. No ack for the return stream.