One network security related protocol not mentioned in the book is the SSH protocol. This protocol allows encrypted shell sessions and encrypted file transfer sessions between the client and server. One issue in unsecure LANs is that others can sniff your password (and anything sent between the client and server) when you use a plaintext application such as telnet or FTP. SSH provides an encrypted alternative to these applications so that sniffing is not as easy. Note: as with any cryptographic protocol, if someone figures out how to break the underlaying cryptographic algorithms, they can recover the plaintext from the encrypted session.
The two main developers of SSH servers are Tectia (formerly SSH Communications Security) and OpenSSH. The original SSH code was written by Tatu Yl�nen and released freely. Tatu Yl�nen went on to form SSH Communications Security, which is a proprietary company. It changed its name to Tectia Corporation in 2010. OpenSSH was developed from Tatu Yl�nen's free code and is open source. The OpenSSH server is widely used by many Unix/Linux based servers.
There are also many free SSH clients for various platforms, such as the Putty program for Windows. Most Linux distributions use the client software provided by OpenSSH. There are also proprietary SSH clients for a variety of platforms.
Like many network related protocols, SSH was developed first then standardized. IETF formed a working group called secsh to develop the RFCs. The working group has now dissolved. The main RFCs out of that working group are: