Basic Structure of the Internet

by George Alende.

Share
|
Homepage | Submit your article | Contact | TOS
More articles on protocols  

You are here: Categories » Electronics and communication » Protocols

The best view of the Internet comes with following a packet from your PC. When you log into a web site, you actually send a command to a distant server telling it to download a page of data to your PC. Your web browser packages that command into a packet labeled with the address of the server storing the page that you want. Your PC sends the packet to your modem (or terminal adapter), which transmits it across your telephone or other connection to your Internet Service Provider or ISP.

The ISP actually operates as a message forwarder. At the ISP, your message gets combined with those from other PCs and sent through a higher speed connection (at least you should hope it is a high speed connection) to yet another concentrator that eventually sends your packet to one of five regional centers (located in New York, Chicago, San Francisco, Los Angeles, and Maryland). There the major Internet carriers exchange signals, routing the packets from your modem to the carrier that haul them to their destination based on their Internet address.

One of the weaknesses of today's Internet is its addressing. All of the Internet addresses are global. From the address itself, neither you nor a computer can tell where that address is or, more importantly, how to connect to it. The routers in the Internet regional centers maintain tables to help quickly send packets to the proper address. Without such guidance, packets wander throughout the world looking for the right address. Worse, the current Internet naming convention which assigns 32-bit addresses, doesn't have the breadth necessary to accommodate all future applications of the Internet. Some experts believe that the Internet will simply run out of available addresses sometime around the turn of the century-whether the shortfall occurs before or after the millennium depends on how pessimistic an expert you ask.

Internet addresses are separate and distinct from the domain names used as Uniform Resource Locators (URLs) through which you specify Web pages. The domain names give you a handle with a natural-language look. Internet addresses are, like everything in computing, binary codes.

Even domain names are running short. Finding a clever and meaningful name for a web site is a challenge that's ever increasing. Believing that one of the problems in the shortage of URLs has been the relatively few suffixes available, one of the coordinating agencies for Internet names, the International Ad Hoc Committee, proposed seven additional suffixes in addition to the six already in use in the U.S. and the national suffixes used around the world (.US for United States, .CA for Canada, and so on).

Leave a comment or ask a question
Total comments: 0

Protocols Disclaimer

  • The e-articles directory is not responsible for any and all copyright infringements by writers and authors. If you suspect the information contained by this page for any copyright infringements, please contact us to investigate the issue
DNS risks and security - DNS is the Domain Name System. It's a UDP- and TCP-based protocol that listens on port 53. TCP connections are commonly used for zone transfers. The DNS matches IP addresses to hostname (more...)
FTP with IPv6 - FTP has been designed to work over IPv4 supporting 32-bit addresses. With RFC 2428, "FTP Extensions for IPv6 and NATs," a specification was made that allows FTP to work over IPv4 and IPv6. Duri (more...)
DNS in the IPv6 world - DNS is used in the IPv4 world to do name-to-address mappings and vice versa. This is not changing in the IPv6 world. The need for DNS is actually much greater because of the length of IPv6 addr (more...)
RADIUS Vulnerabilities - RADIUS is known to have a set of weaknesses that are either presented in the protocol itself or caused by poor client implementation. The stateless UDP protocol itself allows easier packet forg (more...)
DHCP with IPv6 - DHCP is widely used to configure hosts with their IPv4 addresses and additional information. If you have an IPv6 network, you do not need DHCP to configure your hosts with address information. (more...)
IPSec Protocols Operations and Modes Overview - IPSec was designed by a dedicated working group of the Internet Engineering Task Force (IETF). The goal behind IPSec creation was the development of a single standard providing high-quality, in (more...)
REXEC - REXEC is often confused with the other r services. However, it bears no relationship to them. REXEC runs on TCP port 512. UNIX distributions often ship without an REXEC client program (more...)
Network File System NFS - The Network File System (NFS) protocol defines a way for co-operating systems to share filesystems. Today, everyone seems to refer to NFS mounts as shares. NFS is based on the RPC (Remote (more...)
SMTP - SMTP is the Simple Mail Transfer Protocol (defined in RFC 821). Among other tasks, its job is to receive mail by accepting connections on TCP port 25 from remote mail servers. By default, UNIX (more...)
MNP: Microcom Networking Protocol Standards - Microcom Networking Protocol is an entire hierarchy of standards, starting with MNP Class 1, an out of date error correction protocol to MNP Class 10, Adverse Channel Enhancements, which is desi (more...)

 
free content
    Copyright © 2006 - 2012 e-articles.info.
The texts, articles and tutorials in the directory are property of their respective owners and authors.