I decided I would remake the internet and make it a better, more kid-friendly place. This probably will never be implemented, but I did it anyways.

[All commands, responses, state info, etc are in binary format]
Internet Protocols -
flag objects-
server:
users[];
  user.state  
     states: 0 = disconnected, 1 = connected, 10 = afk, 11 = connected-banned, 100 = connected-suspended;
  user.access
     access-types: 0 = banned, 1 = General User, 10 = Operator, 11 = Administrator, 100 = Bot, 101 = Owner;
  user.permissions[]
     permissions: 0 = no permissions, 1 = Generic Permit, 10 = Operator Permit, 11 = Administrator Permit, 100 = Bot Permit, 101 = Full Access;
  user.protocol
     protocols: 0 = CP, 1 = DTP, 10 = OTP, 11 = HTTP, 100 = HTTPS;

global emergency cancel protocol byte: 1111 // like dialing 911
//the GECP is a protocol to terminate the current task due to an error, user action, or anything else.

server.state
    states: 0 = offline, 1 = online, 10 = one or more connections;
Connection Protocol-
commands and responses:
1, request connect;
10, reply connect;
11, allow connect;
100, deny connect;

byte sequence:
client: send 1;
server: send 10;
server: (process if allow or deny, then) send 11 or send 100;


Data Transfer Protocol-
commands and responses: 
1, data request;
10, confirm request;
11, allow request;
100, deny request;
101, get data;
110, send data;
111, accept data;
1000, reject data;

byte sequence:

--scenario: client get from server
client: send 1;
server: send 10;
server: (process if allow or deny, then) send 11 or send 100;
client: send 101;
client: send <address>;
server: (process, then) send 111 or send 1000;

--scenario: client get from server
client: send 1;
server: send 10;
server: send 11;
client: send 101;
client: send <address>;
server: (process, then) send 111;
server: send 110;

--scenario: client send to server
client: send 1;
server: send 10;
server: (processes...) send 11;
client: send 110;
server: send 11;
client: send <address>;
server: (processes...) send 10;

Termination Protocol:
commands and responses:
1, request terminate; // request a termination
10, reply terminate; // request received
11, allow terminate; // allow termination
100, deny terminate; // deny termination (thread waiting on external client object perhaps)
101, terminate; // ends connection after 10, and 11.
110, cancel terminate; // cancels the termination procedure
111, force terminate;
1000, override terminate;

byte sequence:

--scenario: allow terminate (server)
client: send 1;
server: send 10;
server: send 11;
client: send 101;
server: send 101;

--scenario: deny terminate (server)
client: send 1;
server: send 10;
server: send 100;
client: send 111;
server: send 100;
client: send 1000;
client: send 101;

Script Transfer Protocol-

HTTP ~
HTTPS ~

Opcode Transfer Protocol:
commands and responses:
1, request opcode command; // send request for opcode operation
10, confirm confirm opcode command; // confirms response was recieved
11, allow opcode command; // allows request
100, deny opcode command; // denies request
101, send opcode; // sends an opcode
110, get opcode; // checks opcode
111, unknown opcode; // unrecognized operation
1000, opcode executed; // opcode executed
1001, require value; // received opcode, give value

client: send 1;
server: send 10;
server: send 11;
client: send 101;
client: send <opcode>;
server: send 1000;
client:...;
....;

/////////////////////////////////////End of explanation////////////////////////////////////////

I honestly believe the internet and networks in general would be more secure using these protocols