Which of the following is not applicable for IP?

To determine which option is not applicable for IP (Internet Protocol), it helps to classify each item by what IP itself defines/does versus what is handled by other parts of the Internet protocol suite. IP is primarily responsible for logical addressing and for carrying datagrams (packet payload + IP header) across an internetwork using routing/forwarding semantics. Key components of IP include the IP header and the datagram model (including fragmentation fields when needed), along with error reporting via ICMP. Meanwhile, “handle addressing conventions” and “datagram format” are directly part of IP’s defined behavior, while “packet handling conventions” is ambiguous—but in typical curricula it refers to conventions for higher-layer or link-layer packet handling rather than the specific IP datagram-processing rules.

A strong way to reason:

• (i) Error reporting: IP commonly uses ICMP for reporting errors related to delivery (e.g., destination unreachable, time exceeded). IP itself defines how such errors are surfaced/triggered via ICMP.
• (ii) Handle addressing conventions: IP defines addressing (IPv4/IPv6) and the source/destination addressing model.
• (iii) Datagram format: IP defines the structure of an IP datagram/header (IPv4 header fields, IPv6 base header fields).
• (iv) Packet handling conventions: In most standard references and exam contexts, IP “packet handling” is better described as datagram forwarding/reassembly/fragmentation behavior (which is specific). But the phrase “packet handling conventions” is not a standard IP-proper term; it usually maps to non-IP conventions (e.g., transport/session behavior or general “packet handling” outside IP’s defined datagram model). Therefore, (iv) is the one typically considered not applicable for IP.

The expected answer is: (iv) Packet handling conventions.

IP responsibilities mapped to the options

keyword primarily defines addressing and how datagrams are forwarded across networks.

1. (i) Error reporting — applicable
   IP itself doesn’t “generate application errors,” but it uses the control-plane mechanism ICMP to report problems encountered during IP packet processing/forwarding (e.g., unreachable destination, TTL expiration).

2. (ii) Handle addressing conventions — applicable
   IPv4/IPv6 specify how endpoints are identified via source and destination addresses in the IP header, and they define addressing semantics used by routers for forwarding.

3. (iii) Datagram format — applicable
   IP defines the datagram header format and fields (for IPv4, such as Version, IHL, Total Length, Identification/Flags/Fragment Offset, TTL, Protocol, Header Checksum; for IPv6, a simplified base header).

4. (iv) Packet handling conventions — not applicable (typical interpretation)
   This option is not a canonical component of IP’s specification phrased this way. IP’s “handling” is more precisely described as forwarding and fragmentation/reassembly behavior for IP datagrams, not generic “packet handling conventions” as a standalone category. In common course/MCQ framing, this makes (iv) the incorrect (not applicable) choice.