What is the transmission efficiency of a 5,000 byte file is sent in response to a Web request HTTP, TCP TCP/IP (IPv4)

and Ethernet. Assume the file uses a 100 byte HTTP in addition to the 5,000-bype file. Assume the maximum packet size is 1,200. Hint: Remember form Chapter 4 that efficiency = user data/total transmission size.. Necessary phases: 1. The efficiency formula 2. Is packetizing necessary 3. The overhead associated with each layer.

Phase #1 Number of information bits Efficiency (%) = -------------------------------------------------------------------------------------- * 100% Number of information bits + Number of overhead bits

Phase #2 First, recall that each of the layers operate independently. Therefore, our transport (TCP) layer will treat everything from the application layer as data. The application does not care what is below it and therefore will only transmit the HTTP header once. This gives us 5,000 + 100 or 5,100 that must be considered in the packetizing decision. Because 5,100 is greater than 1,200, two or more frames will be necessary (see below).

. . .

In reality, for the Ethernet/IP/TCP combination, each frame can accommodate: 1,492 TCP header IP header (Ethernet header + Ethernet trailer) = 1,492 24 24 = 1,444 (See next page for formats) but use 1,200 as the problem states The number of frames is therefore 5,100/1,200 rounded up or 5 frames to accommodate the original message.

TCP (Total Overhead = 24 bytes)

1 2 3 4 5 6

Source ID Destination ID Sequence number ACK number Header length Unused

16 bits 16 bits 32 bits 32 bits 4 bits 6 bits

7 8 9 10 11

Flags Flow control CRC 16 Urgent pointer Options Total

6 bits 16 bits 16 bits 16 bits 32 bits 192 bits (24 bytes)

IP (Total Overhead = 24 bytes)

1 2 3 4 5 6 7

Version number Header length Type of Service Total length Identifiers Flags Packet offset

4 bits 4 bits 8 bits 16 bits 16 bits 3 bits 13 bits

8 9 10 11 12 13

Hop limit Protocol CRC 16 Source address Destination Address Options Total

8 bits 8 bits 16 bits 32 bits 32 bits 32 bits 192 bits (24 bytes)

Ethernet (Total overhead = 33 bytes as per the text)

Phase #3 Overhead 33 + 24 + 24 + 100 = 181 33 + 24 + 24 33 + 24 + 24 33 + 24 + 24 33 + 24 + 24

Number of information bits Efficiency (%) = -------------------------------------------------------------------------------------- * 100% Number of information bits + Number of overhead bits 5,000 Efficiency (%) = ----------------------------------------------- *100% = 90.8% 5,000+ (181 + 81 + 81 + 81 + 81)

= 81 = 81 = 81 = 81

Resolved Question
Show me another http://answers.yahoo.com/question/index?qid=20080418085647AAySmhP

How long is a 64 byte message in meters?

3 years ago Report Abuse

Additional Details
a. Lets assume that the smallest possible message is 64 bytes (including the 33byte overhead). If we use 10Base-T, how long (in meters) is a 64 byte message? While electricity in the cable travels a bit slower than the speed light, once you include delays in the electrical equipment in transmitting and receiving the signal, the effective speed in only about 40 million meters per second. (Hint: First calculate the number of seconds it would take to transmit the message then calculate the number of meters the signal would travel in that time, and you have the total length of the message.)

3 years ago

G L

Best Answer - Chosen by Voters

Hello! We'll start with a bit of prep research: 1 byte breaks down into 8 bits, so 64 bytes break down into 512 bits Now, let's determine the length of a single bit based on the details provided: Your first given: 10 Base T sends 10 megabits per second. The trick is that 10 megabits per second actually breaks down into 10,485,760 bits per second. So in one second you can transmit 10,485,760 bits some distance. If we follow the hint you offered, our first step is to determine how long it takes to send 512 bits at 10 Base T: In 1 second we can send 10,485,760 bits. Therefore, how long will it take to send 512 bits? 1 second / 10,485,760 bits = ? seconds / 512 bits 1 second * 512 bits / 10,485,760 bits = 4.8828125 10^-5 seconds = .000048828125 seconds Now that we know It takes .000048828125 seconds to send 64 bytes of data, we can apply that information to your second given, that the effective speed is 40,000,000 meters per second. If it only takes .000048828125 seconds to send 64 bytes of data at 10 Base T, and

in a full second the data could travel 40,000,000 meters, then how far will it travel in only .000048828125? 40,000,000 meters per second * .00048828125 seconds = 1,953.125 meters Therefore, your answer is that at 10Base-T assuming 40 million meters per second, A 64 byte message is 1,953.125 meters in length.

Another way to calculate this is to determine how many meters a single bit can travel. If you know a bit can travel at 40,000,000 meters per second, and you can have up to 10,485,760 bits traveling per second, how many meters are traveled per bit? 40,000,000 meters per second / 10,485,760 bits per second = 3.81469727 meters per bit Knowing there are 512 bits per 64 byte message 512 bits * 3.81469727 meters per bit = 1,953.125 meters Again, you find your answer to be that at 10Base-T assuming 40 million meters per second, A 64 byte message is 1,953.125 meters in length. So it looks like the magic is 1,953.125 meters! I hope this has helped. Please read through it so you're sure you understand the math (and to double-check my math), otherwise I'm probably doing more damage than good by sharing the answer.

Q3 IEEE 802.1q (an emerging standard) The main used when a packet needs to go from one switch to another 16-byte VLAN tag inserted into the 802.3 packet by the sending switch or when the IEEE 802.1q packet reaches its destination switch its header (VLAN tag) stripped off and Ethernet packet inside is sent to its destination computer

The IEEE's 802.1Q standard was developed to address the problem of how to break large networks into smaller parts so broadcast and multicast traffic wouldn't grab more bandwidth than necessary. The standard also helps provide a higher level of security between segments of internal networks. The 802.1Q specification establishes a standard method for inserting virtual LAN (VLAN) membership information into Ethernet frames. In a LAN, datalink-layer broadcast and multicast traffic is delivered to all endstations, but this traffic cannot go beyond the LAN boundary. In the past, shared cabling or hubs were the boundaries for LANs.