The American standard for DS0 is 64 Kbs, the European standard is 32 Kbs. The Americans pushed for an ATM payload of 64 Bytes while the Europeans pushed for 32 Bytes. To come to a compromise, the committee added 64 + 32 = 96. They then divided this sum by 2 for a result of 48. A 5 Byte header was added for a total of 53 Bytes.
When the CCITT was standardizing ATM, parties from the United States wanted a 64-byte payload because this was felt to be a good compromise between larger payloads optimized for data transmission and shorter payloads optimized for real-time applications like voice; parties from Europe wanted 32-byte payloads because the small size (and therefore short transmission times) simplify voice applications with respect to echo cancellation. Most of the European parties eventually came around to the arguments made by the Americans, but France and a few others held out for a shorter cell length. With 32 bytes, France would have been able to implement an ATM-based voice network with calls from one end of France to the other requiring no echo cancellation. 48 bytes (plus 5 header bytes = 53) was chosen as a compromise between the two sides. 5-byte headers were chosen because it was thought that 10% of the payload was the maximum price to pay for routing information.
From: http://en.wikipedia.org/wiki/Asynchronous_transfer_mode
53 bytes
ATM as well as frame relay are switched WANs. Frame relay protocol was designed to replace X.25 . ATM is advantageous as it is a cell network and a cell network uses the cell as a basic unit of data exchange and are small and fixed size block of information .
.53 MB (which is MegaBytes, or millions of bytes) equates to 542.7199707031 KiloBytes (which is thousands of bytes.)
Port 53
DNS primarily uses the User Datagram Protocol (UDP) on port number 53 to serve requests. DNS queries consist of a single UDP request from the client followed by a single UDP reply from the server. When the length of the answer exceeds 512 bytes and both client and server support EDNS, larger UDP packets are used.
53 bytes
53 bytes long
53 bytes
ATM as well as frame relay are switched WANs. Frame relay protocol was designed to replace X.25 . ATM is advantageous as it is a cell network and a cell network uses the cell as a basic unit of data exchange and are small and fixed size block of information .
ATM has (i) Fixed cell size, (ii) Implemented to meet the transport requirements for LAN,MAN and WAN applications, (iii) Connection-oriented, (iV) Cell size is fixed and is of 53 bytes 5 for header and 48 for payload, (V) Packet switching on private network that operate on data link layer on OSI. Whereas IP has (i) Variable cell size, (ii) Allow voice, data, fax and video signals to share a common networking infrastructure, (iii) Connection less, (iV) Cell size is upto 65535 bytes,and (V) Network addressing that operate on network layer on OSI frame relay.
I'm assuming you mean Asynchronous Transfer Mode, not Automatic Teller Machine. It's used by Telcos, often as part of the SONET optical fibre system. Its main features are its 53-byte cell size and its circuit-oriented design which suits the needs of Telecommunications. Although ATM was "very fast" when first introduced, it's been overtaken by Ethernet over fibre in its various forms. Ethernet can now reliably work at tens of gigabits, and ATM is often "packaged" into Ethernet frames for transport.
ATM
.53 MB (which is MegaBytes, or millions of bytes) equates to 542.7199707031 KiloBytes (which is thousands of bytes.)
TCP 53
Packet forwarding in simple terms is the forwarding of packets from one node to another from networking point of view. For example, a router or a switch. These networking devices make routing devices with the help of their routing tables and then select an outgoing interface. After that they make some changes in the packet header and push (forward) the packet to the selected interface. In case you don't know the meaning of packet. Packer is the smallest unit of size in networking. Different networks has different packet size. For example, in ATM Networks the packet size is of 53 Bytes.
A PTR record is essentially the opposite of an A record. A records resolve names to IP addresses. PTR records resolve IP addresses to names. A record = give me a name I'll give you an IP PTR record = give me an IP I'll give you a name Try it out in windows: ping "www.yahoo.com" Here is what I got: ------------------------------------------------------------------------------------- F:\>ping www.yahoo.com Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data: Reply from 69.147.76.15: bytes=32 time=14ms TTL=53 Reply from 69.147.76.15: bytes=32 time=11ms TTL=53 Reply from 69.147.76.15: bytes=32 time=65ms TTL=53 Reply from 69.147.76.15: bytes=32 time=12ms TTL=53 --------------------------------------------------------------------------------------- now do a "ping -a IP-ADDRESS" which will spit you back the name attached to that IP ---------------------------------------------------------------------------------------- F:\>ping -a 69.147.76.15 Pinging f1.www.vip.re1.yahoo.com [69.147.76.15] with 32 bytes of data: Reply from 69.147.76.15: bytes=32 time=19ms TTL=53 Reply from 69.147.76.15: bytes=32 time=88ms TTL=53 Reply from 69.147.76.15: bytes=32 time=12ms TTL=53 Reply from 69.147.76.15: bytes=32 time=46ms TTL=53 Ping statistics for 69.147.76.15: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 88ms, Average = 41ms ------------------------------------------------------------------------------------------- Your accessing PTR records to do this. ... and just so you beileve me try a "ping 69.147.76.15" and check the results FYI: if your doing a ping -a to an intranet host you need to configure reverse lookup for it to work properly.
53 Kilobyte's isn't very much but can be the equivelant of 53,000 bytes, 1000 KB is required to take it up to the next level of 1 MB.