09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• DDP checksum (long header only)—This 16-bit field is used for<br />

error detection resulting from router-<strong>to</strong>-router transmissions.<br />

The checksum, <strong>to</strong>ge<strong>the</strong>r with <strong>the</strong> datagram at <strong>the</strong> source, is<br />

used by <strong>the</strong> router at arrival <strong>to</strong> verify data integrity.<br />

• Destination <strong>network</strong> address (long header only)—This is a<br />

16-bit <strong>network</strong> address.<br />

• Source <strong>network</strong> address (long header only)—This is a 16-bit<br />

<strong>network</strong> address.<br />

• Destination node ID (long header only)—This is an 8-bit node<br />

address.<br />

• Source node ID (long header only)—This is an 8-bit node<br />

address.<br />

• Destination socket number (short and long header)—This is an<br />

8-bit socket address.<br />

• Source socket number (short and long header)—This is an 8-bit<br />

socket address.<br />

• DDP type (short and long header)—This is an 8-bit field used <strong>to</strong><br />

indicate <strong>the</strong> transport layer pro<strong>to</strong>col.<br />

DDP Broadcasts<br />

Three types of DDP broadcasts exist:<br />

• Network-specific broadcast<br />

• Network-wide broadcast<br />

• Zone-specific broadcast<br />

The way <strong>the</strong> broadcast is interpreted by <strong>the</strong> node is determined by <strong>the</strong><br />

node address field in <strong>the</strong> packet's destination <strong>network</strong> address. If <strong>the</strong><br />

<strong>network</strong> number is any value o<strong>the</strong>r than zero, a datagram with a<br />

destination node ID of $FF (255) is examined by all nodes. However,<br />

<strong>the</strong> datagram is only accepted by nodes with <strong>the</strong> corresponding<br />

<strong>network</strong> number.<br />

If <strong>the</strong> <strong>network</strong> number is zero ($00000000), <strong>the</strong> broadcast is intended<br />

for <strong>the</strong> local <strong>network</strong> segment. If <strong>the</strong> packet is a <strong>network</strong>-wide packet,<br />

<strong>the</strong> <strong>network</strong> address is zero and <strong>the</strong> node address is $FF, and all<br />

nodes on <strong>the</strong> segment accept <strong>the</strong> packet. If <strong>the</strong> packet is intended <strong>to</strong><br />

be a zone-specific broadcast, it has <strong>the</strong> same addressing as a<br />

<strong>network</strong>-wide packet. However, it is up <strong>to</strong> <strong>the</strong> ULP <strong>to</strong> determine if <strong>the</strong><br />

packet is relevant <strong>to</strong> <strong>the</strong> node. Because <strong>the</strong> packet is addressed as a

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!