List of network protocols From Wikipedia, the free encyclopedia Jump to: navigation, search This is an incomplete list

of individual network protocols, categorized by their nearest OSI model layers. Contents [hide]

1 Layer 1 protocols (Physical layer) 2 Layer 2 protocols (Data link layer) 3 Layer 2+3 protocols 4 Layer 3 protocols (Network layer) 5 Layer 3+4 protocols 6 Layer 4 protocols (Transport layer) 7 Layer 5 protocols (Session layer) 8 Layer 7 protocols (Application layer) 9 Protocol description languages 10 Other protocols 11 External links

[edit] Layer 1 protocols (Physical layer)

ISDN Integrated Services Digital Network PDH Plesiochronous Digital Hierarchy o T-carrier (T1, T3, etc.) o E-carrier (E1, E3, etc.) RS-232, a serial line interface originally developed to connect modems and computer terminals SDH Synchronous Digital Hierarchy SONET Synchronous Optical NETworking

over voice telephone lines. [edit] Layer 2 protocols (Data link layer)

ARP Address Resolution Protocol AYIYA Anything In Anything ARCnet CDP Cisco Discovery Protocol DCAP Data Link Switching Client Access Protocol Econet Ethernet FDDI Fiber Distributed Data Interface Frame Relay HDLC High Level Data Link Control LocalTalk L2F Layer 2 Forwarding Protocol L2TP Layer 2 Tunneling Protocol LAPD Link Access Procedures on the D channel LLDP Link Layer Discovery Protocol LLDP-MED Link Layer Discovery Protocol - Media Endpoint Discovery PPP Point-to-Point Protocol PPTP Point-to-Point Tunneling Protocol SLIP Serial Line Internet Protocol (obsolete) StarLan STP Spanning Tree Protocol 1

Token ring VTP VLAN Trunking Protocol

[edit] Layer 2+3 protocols

ATM Asynchronous Transfer Mode Frame relay, a simplified version of X.25 MPLS Multi-protocol label switching Signalling System 7, also called SS7, C7 and CCIS7; a common PSTN control protocol. X.25

[edit] Layer 3 protocols (Network layer)

ARP Address Resolution Protocol BGP Border Gateway Protocol EGP Exterior Gateway Protocol ICMP Internet Control Message Protocol IGMP Internet Group Management Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IPX Internetwork Packet Exchange IS-IS Intermediate system to intermediate system MPLS Multiprotocol Label Switching OSPF Open Shortest Path First RARP Reverse Address Resolution Protocol

[edit] Layer 3+4 protocols

Xerox Network Services (XNS)

[edit] Layer 4 protocols (Transport layer)

IL Originally developed as transport layer for 9P RTP Real-time Transport Protocol SPX Sequenced Packet Exchange SCTP Stream Control Transmission Protocol TCP Transmission Control Protocol UDP User Datagram Protocol Sinec H1 for telecontrol

[edit] Layer 5 protocols (Session layer)

9P Distributed file system protocol developed originally as part of Plan 9 NCP NetWare Core Protocol NFS Network File System SMB Server Message Block (aka CIFS Common Internet FileSystem)

[edit] Layer 7 protocols (Application layer)

AFP Apple Filing Protocol BACnet Building Automation and Control Network protocol BitTorrent, a peer-to-peer file sharing protocol BOOTP Bootstrap Protocol DIAMETER, an authentication, authorization and accounting protocol DICT Dictionary protocol DNS Domain Name Service DHCP Dynamic Host Configuration Protocol FTP File Transfer Protocol Finger, which gives user profile information Gnutella, a peer-to-peer file-swapping protocol Gopher, a precursor of web search engines 2

HTTP HyperText Transfer Protocol, used in the World Wide Web IMAP Internet Message Access Protocol IRC Internet Relay Chat protocol Jabber, an instant-messaging protocol LDAP Lightweight Directory Access Protocol MIME Multipurpose Internet Mail Extensions NNTP News Network Transfer Protocol NTP Network Time Protocol POP3 Post Office Protocol Version 3 RADIUS, an authentication, authorization and accounting protocol Rlogin, a UNIX remote login protocol rsync, a file transfer protocol for backups, copying and mirroring SSH Secure SHell SIP, Session Initiation Protocol, a signalling protocol SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SOAP Simple Object Access Protocol Telnet, a remote terminal access protocol TFTP Trivial File Transfer Protocol, a simple file transfer protocol WebDAV Web Distributed Authoring and Versioning RIP Routing Information Protocol

and secure versions of the above (HTTPS, etc.) [edit] Protocol description languages

Abstract syntax notation one (ASN.1)

[edit] Other protocols

Controller Area Network (CAN) Digital Command Control (DCC) DSA Distributed Systems Architecture (Honeywell Bull) FIX protocol Gateway Discovery Protocol GDP is a Cisco protocol similar to IRDP ICMP Router Discovery Protocol Implementation of RFC 1256 IC List of automation protocols modbus SNA Systems Network Architecture (IBM) SOCKS STUN

Physical layer

From Wikipedia, the free encyclopedia Jump to: navigation, search This article or section does not adequately cite its references or sources. Please help improve this article by adding citations to reliable sources. (help, get involved!) This article has been tagged since December 2006. OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer

3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer The physical layer is level one in the seven level OSI model of computer networking as well as in the five layer TCP/IP reference model. It performs services requested by the data link layer. The physical layer is the most basic network layer, providing only the means of transmitting raw bits rather than packets over a physical data link connecting network nodes. No packet headers nor trailers are consequently added to the data by the physical layer. The bit stream may be grouped into code words or symbols, and converted to a physical signal, which is transmitted over a physical transmission medium. The physical layer provides an electrical, mechanical, and procedural interface to the transmission medium. The shapes of the electrical connectors, which frequencies to broadcast on, what modulation scheme to use and similar low-level things are specified here. An analogy of this layer in a physical mail network would be the roads along which the vans carrying the mail drive. The physical layer determines the bit rate in bit/s, also known as channel capacity, digital bandwidth, maximum throughput or connection speed. The major functions and services performed by the physical layer are: Bit-by-bit node-to-node delivery Providing a standardized interface to physical transmission media, including o Mechanical specification of electrical connectors and cables, for example maximum cable length o Electrical specification of transmission line signal level and impedance o Radio interface, including electromagnetic spectrum frequency allocation and specification of signal strength, analog bandwidth, etc. o Specifications for IR over optical fiber or a wireless IR communication link

The five layer TCP/IP model 5. Application layer DHCP DNS FTP HTTP IMAP4 IRC NNTP XMPP MIME POP3 SIP SMTP SNMP SSH TELNET BGP RPC RTP RTCP TLS/SSL SDP SOAP L2TP PPTP 4. Transport layer TCP UDP DCCP SCTP GTP 3. Network layer IP (IPv4 IPv6) ICMP IGMP RSVP IPsec 2. Data link layer ATM DTM Ethernet FDDI Frame Relay GPRS PPP ARP RARP 1. Physical layer

Ethernet physical layer ISDN Modems PLC SONET/SDH G.709 Wi-Fi This box: view talk edit Modulation Line coding Bit synchronization in synchronous serial communication Start-stop signalling and flow control in asynchronous serial communication Circuit mode multiplexing Carrier sense and collision detection utilized by some level 2 multiple access protocols Equalization filtering, training sequences, pulse shaping and other signal processing of physical signals

The physical layer is also concerned with Point-to-point, multipoint or point-to-multipoint line configuration Physical network topology, for example bus, ring, mesh or star network Serial or parallel communication Simplex, half duplex or full duplex transmission mode

[edit] Physical signaling sublayer In a local area network (LAN) or a metropolitan area network (MAN) using open systems interconnection (OSI) architecture, the physical signaling sublayer is the portion of the physical layer that:

interfaces with the medium access control sublayer (MAC) performs character encoding, transmission, reception and decoding performs mandatory isolation functions.

Source: from Federal Standard 1037CNote: Physical layer Associated with transmission of unstructured bit streams over a physical link. Responsible for the mechanical, electrical and procedural characteristics that establish, maintain and deactivate the physical link. Data link layer

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer The data link layer is layer two of the seven-layer OSI model as well as of the five-layer TCP/IP reference model. It responds to service requests from the network layer and issues service requests to the physical layer. This is the layer which transfers data between adjacent network nodes in a wide area network or between nodes on the same local area network segment. The data link layer provides the functional and procedural means to transfer data between network entities and might provide the means to detect and possibly correct errors that may occur in the Physical layer. Examples of data link protocols are Ethernet for local area networks and PPP, HDLC and ADCCP for point-to-point connections. The data link is all about getting information from one place to a selection of other places. At this layer one does not need to be able to go everywhere, just able to go somewhere else. It is analogous to social interaction in that one needs to know at least one other person, but not necessarily know Fred, Bob, or James. The data link provides data transfer across the physical link. That transfer might or might not be reliable; many data link protocols do not have acknowledgments of successful frame reception and acceptance, and some data link protocols might not even have any form of checksum to check for transmission errors. In those cases, higher-level protocols must provide flow control, error checking, and acknowledgments and retransmission. In some networks, such as IEEE 802 local area networks, the data link layer is split into MAC and LLC sublayers; this means that the IEEE 802.2 LLC protocol can be used with all of the IEEE 802 MAC layers, such as Ethernet, token ring, IEEE 802.11, etc., as well as with some non-802 MAC layers such as FDDI. Other data link layer protocols, such as HDLC, are specified to include both sublayers, although some other protocols, such as Cisco HDLC, use HDLC's low-level framing as a MAC layer in combination with a different LLC layer Contents [hide]

1 Logical Link Control Sublayer 2 Media Access Control Sublayer 3 Examples 4 Interfaces

[edit] Logical Link Control Sublayer The uppermost sublayer is Logical Link Control (LLC). This sublayer multiplexes protocols running atop the data link layer, and optionally provides flow control, acknowledgment, and error recovery. PPP and HDLC protocols works in Logical Link Control Sub Layer. [edit] Media Access Control Sublayer The sublayer below it is Media Access Control (MAC). Sometimes this refers to the sublayer that determines who is allowed to access the media at any one time (usually CSMA/CD). Other times it refers to a frame structure with MAC addresses inside. There are generally two forms of media access control: distributed and centralized. Both of these may be compared to communication between people: In a network made up of people speaking, i.e. a conversation, we look for clues from our fellow talkers to see if any of them appear to be about to

speak. If two people speak at the same time, they will back off and begin a long and elaborate game of saying "no, you first". The Media Access Control sublayer also determines where one frame of data ends and the next one starts. In a snail-mail network, each letter is one frame of data, and one can tell where it begins and ends because it is inside an envelope. One might also specify that a letter will begin with a phrase like "Dear Sir", and ends with a phrase like "Yours Sincerely". [edit] Interfaces The data link layer is often implemented in software as a "network card driver". The operating system will have a defined software interface between the data link and the network transport stack above. This interface is not a layer itself, but rather a definition for interfacing between layers. Examples include: ODI NDIS SANA II - Standard Amiga Networking Architecture, version 2

Retrieved from "http://en.wikipedia.org/wiki/Data_link_layer" Network layer

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer The network layer is level three of the seven level OSI model as well as of the five layer TCP/IP model. In the four layer TCP/IP reference model it is called Internet layer, which is the second layer from below. It responds to service requests from the transport layer and issues service requests to the data link layer. In essence, the network layer is responsible for end to end (source to destination) packet delivery, whereas the data link layer is responsible for node to node (hop to hop) packet delivery. The network layer provides the functional and procedural means of transferring variable length data sequences from a source to a destination via one or more networks while maintaining the quality of service requested by the transport layer. The Network layer

performs network routing, flow control, network segmentation/desegmentation, and error control functions. The network layer deals with transmitting information all the way from its source to its destination - transmitting from anywhere, to anywhere. Here are some things that the network layer needs to address: Is the network connection-oriented or connectionless?

For example, snail mail is connectionless, because you can send a letter to someone without them doing anything and they will receive the letter. On the other hand, the telephone system is connection-oriented, because the other party is required to pick up the phone before communication can be established. The OSI Network Layer protocol can be either connection-oriented, or connectionless. The TCP/IP Internet Layer (equivalent to OSI's Network Layer) supports only the connectionless Internet Protocol (IP). What are the Global Addresses?

Everybody in the network needs to have a unique address which determines who they are. This address will normally be hierarchical, so you can be "Fred Murphy" to Dubliners, or "Fred Murphy, Dublin" to people in Ireland, or "Fred Murphy, Dublin, Ireland" to people anywhere in the world. On the internet, these addresses are known as IP Addresses. How do you forward a message?

This is of particular interest to mobile applications, where a user may rapidly move from place to place, and it must be arranged that his messages follow him. Version 4 of the Internet Protocol (IPv4) doesn't really allow for this, though it has been hacked somewhat since its inception. Fortunately, the forthcoming IPv6 has a much better designed solution, which should make this type of application much smoother. In the traditional postage system (commonly referred to as snail mail) this role is provided by the postman (to some extent). [edit] Examples
o o o o o o o o

IP/IPv6, Internet Protocol DVMRP, Distance Vector Multicast Routing Protocol ICMP, Internet Control Message Protocol IGMP, Internet Group Multicast Protocol PIM-SM, Protocol Independent Multicast Sparse Mode PIM-DM, Protocol Independent Multicast Dense Mode IPSec, Internet Protocol Security IPX, Internetwork Packet Exchange RIP, Routing Information Protocol NLSP, NetWare Link State Protocol X.25, Packet Level Protocol X.75, Packet Switched Signaling Between Public Networks DDP, Datagram Delivery Protocol

Transport layer

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer

In computing and telecommunications, the transport layer is the second highest layer in the four and five layer TCP/IP reference models, where it responds to service requests from the application layer and issues service requests to the network layer. It is also the name of layer four of the seven layer OSI model, where it responds to service requests from the session layer and issues service requests to the network layer. The definitions of the transport layer are slightly different in these two models. The following text primarily refers to the TCP/IP model. The transport layer provides transparent transfer of data between hosts. It is usually responsible for end-to-end connection, error recovery, flow control, and ensuring complete data transfer. In the Internet protocol suite this function is most commonly achieved by the connection oriented Transmission Control Protocol (TCP). The datagram-type transport, User Datagram Protocol (UDP), provides neither error recovery nor flow control, leaving these to the application. The purpose of the Transport layer is to provide transparent transfer of data between end users, thus relieving the upper layers from any concern with providing reliable and cost-effective data transfer. The transport layer usually turns the unreliable and very basic service provided by the Network layer into a more powerful one. There is a long list of services that can be optionally provided at this level. None of them are compulsory, because not all applications want all the services available. Some can be wasted overhead, or even counterproductive in some cases. Connection-oriented This is normally easier to deal with than connection-less models, so where the Network layer only provides a connection-less service, often a connectionoriented service is built on top of that in the Transport layer. Same Order Delivery The Network layer doesn't generally guarantee that packets of data will arrive in the same order that they were sent, but often this is a desirable feature, so the Transport layer provides it. The simplest way of doing this is to give each packet a number, and allow the receiver to reorder the packets. Reliable Data Packets may be lost in routers, switches, bridges and hosts due to network congestion, when the packet queues are filled and the network nodes have to delete packets. Packets may be lost or corrupted in for example Ethernet due to interference and noise, since Ethernet does not retransmit corrupt packets. Packets may be delivered in the wrong order by an underlying network. Some transport layer protocols, for example TCP, can fix this. By means of an error detection code, for example a checksum, the transport protocol may check that 9

the data is not corrupted, and verify that by sending an ACK message to the sender. Automatic repeat request schemes may be used to retransmit lost or corrupted data. By introducing segment numbering in the transport layer packet headers, the packets can be sorted in order. Of course, error free is impossible, but it is possible to substantially reduce the numbers of undetected errors. Flow Control The amount of memory on a computer is limited, and without flow control a larger computer might flood a computer with so much information that it can't hold it all before dealing with it. Nowadays, this is not a big issue, as memory is cheap while bandwidth is comparatively expensive, but in earlier times it was more important. Flow control allows the receiver to say "Whoa!" before it is overwhelmed. Sometimes this is already provided by the network, but where it is not, the Transport layer may add it on. Congestion avoidance Network congestion occurs when a queue buffer of a network node is full and starts to drop packets. Automatic repeat request may keep the network in a congested state. This situation can be avoided by adding congestion avoidace to the flow control, including slow-start. This keeps the bandwidth consumption at a low level in the beginning of the transmission, or after packet retransmission. Byte orientation Rather than dealing with things on a packet-by-packet basis, the Transport layer may add the ability to view communication just as a stream of bytes. This is nicer to deal with than random packet sizes, however, it rarely matches the communication model which will normally be a sequence of messages of user defined sizes. Ports (Part of the transport layer in the TCP/IP model, but of the session layer in the OSI model) Ports are essentially ways to address multiple entities in the same location. For example, the first line of a postal address is a kind of port, and distinguishes between different occupants of the same house. Computer applications will each listen for information on their own ports, which is why you can use more than one network-based application at the same time. On the Internet there are a variety of Transport services, but the two most common are TCP and UDP. TCP is the more complicated, providing a connection and byte oriented stream which is almost error free, with flow control, multiple ports, and same order delivery. UDP is a very simple 'datagram' service, which provides limited error reduction and multiple ports. TCP stands for Transmission Control Protocol, while UDP stands for User Datagram Protocol. Other options are the Datagram Congestion Control Protocol (DCCP) and Stream Control Transmission Protocol (SCTP). Some things, such as connection orientation can be implemented at either Transport or Network layer. The idea is that the Network layer implements whatever set of options is easiest: for some underlying networks it is easiest to implement connectionless communication, while for others it is easiest to implement connection oriented communication. The Transport layer uses this simplest set of options to implement whatever combinations of options are actually desired. [edit] Transport protocol comparison table TCP Packet header size Packet entity Error checking UDP SCTP

20 Bytes 8 Bytes Segment Datagram Yes Yes Yes

10

Port numbering Connection oriented

Yes Yes

Yes No No No No No

Yes Yes

Automatic repeat request (ARQ) Yes Segment numbering Flow control Congestion avoidance Session layer Yes Yes Yes

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer The session layer is level five of the seven level OSI model. It responds to service requests from the presentation layer and issues service requests to the transport layer. The Session layer provides the mechanism for managing the dialogue between enduser application processes. It provides for either full duplex or half-duplex operation and establishes checkpointing, adjournment, termination, and restart procedures. The Session layer is typically completely unused, but it does have a few places where it is useful. The idea is to allow information on different streams, perhaps originating from different sources, to be properly combined. In particular, it deals with synchronization issues, and ensuring nobody ever sees inconsistent versions of data, and similar things. One application which is fairly intuitively clear is web conferencing. Here, we want to make sure that the streams of audio and video match up - or in other words, that we do not have lipsync problems. We may also want to do "floor control" - ensuring that the person displayed on screen and whose words are relayed is the one selected by the speaker, or by some other criteria.

11

Another big application is in live TV programs, where streams of audio and video need to be seamlessly merged from one to the other so that we do not have half a second of blank airtime, or half a second when we transmit two pictures simultaneously. In brief: the session layer establishes, manages and terminates connections (sessions) among cooperating applications. It also adds traffic flow information. Presentation layer

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer

The presentation layer is the sixth level of the seven layer OSI model. It responds to service requests from the application layer and issues service requests to the session layer. The presentation layer is responsible for the delivery and formatting of information to the application layer for further processing or display. It relieves the application layer of concern regarding syntactical differences in data representation within the end-user systems. Note: An example of a presentation service would be the conversion of an EBCDIC-coded text file to an ASCII-coded file. The presentation layer is the first one where people start to care about what they are sending at a more advanced level than just a bunch of ones and zeros. This layer deals with issues like how strings are represented - whether they use the Pascal method ("\x0Dthisisastring") or the C/C++ method ("thisisastring\0"). The idea is that the application layer should be able to point at the data to be moved, and the Presentation layer will deal with the rest. Encryption is typically done at this level too, though it can be done at the application, session, transport, or network layer; each having its own advantages and disadvantages. Another example is representing structure, which is normally standardised at this level, often by using XML. As well as simple pieces of data, like strings, more complicated things are standardised in this layer. Two common examples are 'objects' in object-oriented programming, and the exact way that streaming video is transmitted. In many widely used applications and protocols, no distinction is made between the presentation and application layers. For example, HTTP, generally regarded as an application layer protocol, has presentation layer aspects such as the ability to identify character encodings for proper conversion, which is then done in the application layer.

12

Retrieved from "http://en.wikipedia.org/wiki/Presentation_layer"

Retrieved from "http://en.wikipedia.org/wiki/Session_layer" Application layer

From Wikipedia, the free encyclopedia Jump to: navigation, search OSI Model 7 Application layer 6 Presentation layer 5 Session layer 4 Transport layer 3 Network layer 2 Data link layer

LLC sublayer MAC sublayer

1 Physical layer The application layer is the seventh level of the seven-layer OSI model. It interfaces directly to and performs common application services for the application processes; it also issues requests to the presentation layer. The common application layer services provide semantic conversion between associated application processes. Note: Examples of common application services of general interest include the virtual file, virtual terminal, and job transfer and manipulation protocols. The application layer of the four layer and five layer TCP/IP models corresponds to the application layer, the presentation layer and session layer in the seven layer OSI model.

[edit] Examples The five layer TCP/IP model 5. Application layer DHCP DNS FTP HTTP IMAP4 IRC NNTP XMPP MIME POP3 SIP SMTP SNMP SSH TELNET BGP RPC RTP RTCP TLS/SSL SDP SOAP L2TP PPTP 4. Transport layer TCP UDP DCCP SCTP GTP 3. Network layer IP (IPv4 IPv6) ICMP IGMP RSVP IPsec 13

 2. Data link layer ATM DTM Ethernet FDDI Frame Relay GPRS PPP ARP RARP 1. Physical layer Ethernet physical layer ISDN Modems PLC SONET/SDH G.709 Wi-Fi This box: view talk edit Network architecture From Wikipedia, the free encyclopedia Jump to: navigation, search In computing, network architecture is the design of a computer network. In telecommunication, the term network architecture has the following meanings: 1. The design principles, physical configuration, functional organization, operational procedures, and data formats used as the bases for the design, construction, modification, and operation of a communications network. 2. The structure of an existing communications network, including the physical configuration, facilities, operational structure, operational procedures, and the data formats in use. With the development of distributed computing, the term network architecture has also come to denote classifications and implementations of distributed computing architectures. For example the applications architecture of the telephone network PSTN has been termed the Advanced Intelligent Network. There are any number of specific classifications but all lie on a continuum between the dumb network (e.g. Internet) and the intelligent computer network (e.g. the telephone network PSTN). Other networks contain various elements of these two classical types to make them suitable for various types of applications. Recently the context aware network which is a synthesis of the two has gained much interest with its ability to combine the best elements of both. The Internet Protocol (IP) is a data-oriented protocol used for communicating data across a packet-switched internetwork. IP is a network layer protocol in the internet protocol suite and is encapsulated in a data link layer protocol (e.g., Ethernet). As a lower layer protocol, IP provides the service of communicable unique global addressing amongst computers. This implies that the data link layer need not provide this service. Ethernet provides globally unique addresses except it is not globally communicable (i.e., two arbitrarily chosen Ethernet devices will only be able to communicate if they are on the same bus). The difference is that IP is concerned with the final destination of data packets. Ethernet is concerned with only the next device (computer, router, etc.) in the chain. The final destination and next device could be one and the same (if they are on the same bus) but the final destination could be on the other side of the world. Contents [hide]

1 Packetization 2 Services provided by IP 3 Reliability 4 IP addressing and routing 5 Version history 6 See also 14

7 External links 8 References

[edit] Packetization Data from an upper layer protocol is Encapsulation of user data in a UDP datagram inside an IP packet encapsulated inside one or more packets/datagrams (the terms are basically synonymous in IP). No circuit setup is needed before a host tries to send packets to a host it has previously not communicated with (this is the point of a An example IP header as captured by ethereal packet-switched network), thus IP is a connectionless protocol. This is quite unlike Public Switched Telephone Networks that require the setup of a circuit before a phone call may go through (a connection-oriented protocol). [edit] Services provided by IP Because of the abstraction provided by encapsulation, IP can be used over a heterogeneous network (i.e., a network connecting two computers can be any mix of Ethernet, ATM, FDDI, Wi-fi, token ring, etc.) and it makes no difference to the upper layer protocols. Each data link layer can (and does) have its own method of addressing (or possibly the complete lack of it), with a corresponding need to resolve IP addresses to data link addresses. This address resolution is handled by the Address Resolution Protocol (ARP). [edit] Reliability IP provides an unreliable service (i.e., best effort delivery). This means that the network makes no guarantees about the packet and none, some, or all of the following may apply:

data corruption out of order (packet A may be sent before packet B, but B can arrive before A) duplicate arrival lost or dropped/discarded

In terms of reliability the only thing IP does is ensure the IP packet's header is error-free through the use of a checksum. This has the side-effect of discarding packets with bad headers on the spot, and with no required notification to either end (though an ICMP message may be sent). To address any of these reliability issues, an upper layer protocol must handle it. For example, to ensure in-order delivery the upper layer may have to cache data until it can be passed up in order. If the upper layer protocol does not self-police its own size by first looking at the Layer 2 MTU size, and sends the IP layer too much data, IP is forced to fragment the original datagram into smaller fragments for transmission. IP does provide re-ordering of any 15

fragments that arrive out of order by using the fragmentation flags and offset.[1] TCP is a good example of a protocol that will adjust its segment size to be smaller than the MTU. UDP and ICMP are examples of protocols that disregard MTU size thereby forcing IP to fragment oversized datagrams.[2] The primary reason for the lack of reliability is to reduce the complexity of routers. While this does give routers carte blanche to do as they please with packets, anything less than best effort yields a poorer experience for the user. So, even though no guarantees are made, the better the effort made by the network, the better the experience for the user. [edit] IP addressing and routing Perhaps the most complex aspects of IP are IP addressing and routing. Addressing refers to how end hosts become assigned IP addresses and how subnetworks of IP host addresses are divided and grouped together. IP routing is performed by all hosts, but most importantly by internetwork routers, which typically use either interior gateway protocols (IGPs) or external gateway protocols (EGPs) to help make IP datagram forwarding decisions across IP connected networks. [edit] Version history IP is the common element found in today's public Internet. The current and most popular network layer protocol in use today is IPv4; this version of the protocol is assigned version 4. IPv4 was adopted by the United States Department of Defense as MIL-STD-1778. IPv6 is the proposed successor to IPv4 whose most prominent change is the addressing. IPv4 uses 32-bit addresses (~4 billion addresses) while IPv6 uses 128-bit addresses (~3.41038 addresses). Although adoption of IPv6 has been slow, as of 2008, all United States government systems must support IPv6.[3] Versions 0 through 3 were either reserved or unused; version 5 was used for an experimental stream protocol. Other version numbers have been assigned, usually for experimental protocols, but have not been widely used. [edit] See also

Connectionless protocol IANA Internet protocol suite IPv4 IPv5 IPv6 IP address IP packet TCP and UDP port numbers Transmission Control Protocol ip - the ip structure for the C programming language

Address Classes In the original Internet routing scheme developed in the 1970s, sites were assigned addresses from one of three classes: Class A, Class B and Class C. The address classes differ in size and number. Class A addresses are the largest, but there are few of them. Class Cs are the smallest, but they are numerous. Classes D and E are also defined, but not used in normal operation. To say that class-based IP addressing in still used would be true only in the loosest sense. Many addressing designs are still class-based, but an increasing number can only be explained using the more general concept of CIDR, which is backwards compatible with address classes. 16

Suffice it to say that at one point in time, you could request the Internet NIC to assign you a class A, B or C address. To get the larger class B addresses, you might have to supply some justification, but only the class A was really tough to get. In any case, NIC would set the network bits, or n-bits, to some unique value and inform the local network engineer. It would then be up to the engineer to assign each of his hosts an IP address starting with the assigned n-bits, followed by host bits, or h-bits, to make the address unique. Internet routing used to work like this: A router receiving an IP packet extracted its Destination Address, which was classified (literally) by examining its first one to four bits. Once the address's class had been determined, it was broken down into network and host bits. Routers ignored the host bits, and only needed to match the network bits to find a route to the network. Once a packet reached its target network, its host field was examined for final delivery. Summary of IP Address Classes Class A - 0nnnnnnn hhhhhhhh hhhhhhhh hhhhhhhh

First bit 0; 7 network bits; 24 host bits Initial byte: 0 - 127 126 Class As exist (0 and 127 are reserved) 16,777,214 hosts on each Class A

Class B - 10nnnnnn nnnnnnnn hhhhhhhh hhhhhhhh

First two bits 10; 14 network bits; 16 host bits Initial byte: 128 - 191 16,384 Class Bs exist 65,532 hosts on each Class B

Class C - 110nnnnn nnnnnnnn nnnnnnnn hhhhhhhh

First three bits 110; 21 network bits; 8 host bits Initial byte: 192 - 223 2,097,152 Class Cs exist 254 hosts on each Class C

Class D - 1110mmmm mmmmmmmm mmmmmmmm mmmmmmmm

First four bits 1110; 28 multicast address bits Initial byte: 224 - 247 Class Ds are multicast addresses - see RFC 1112

Class E - 1111rrrr rrrrrrrr rrrrrrrr rrrrrrrr

First four bits 1111; 28 reserved address bits Initial byte: 248 - 255 Reserved for experimental use

17