network layer

Note: This feedback goes to your product's documentation team and does not include a response. Issues that require a response should go through IBM support. Note: This feedback goes to your product's documentation team and does not include a response. Issues that require a response should go through IBM support. Note: This feedback goes to your product's documentation team and does not include a response. Issues that require a response should go through IBM support. There has been an error sending your feedback to the team. Your comment was saved locally, if not in an incognito browser, and will be available when attempting to submit feedback again. No networking information would be complete without discussing the fact that IP networks (and SNA networks, too) are implemented as layers. Each layer has certain capabilities (in the form of protocols) that it is required to uphold. For example, the IP layer does not include reliability of delivery, while the TCP layer does not concern itself with routing details. For example, when you write a check, you conform to various requirements of the check writing protocol: you must include the amount, the payee, the date and a signature on each check. When it comes to delivery of that check, you put it in an envelope and follow the postal mail protocol to ensure you have a destination address, zip code, return address and, of course, correct postage. The postal service doesn't care what protocol (the check writing protocol, in this case) is being encapsulated within the envelope. The content (payload) of a letter is not the concern of the mail protocol. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence, for the sake of maintaining user understanding, are sometimes required. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.