Which RFC defines NDP Trust Models and Threats?

Which RFC defines NDP Trust Models and Threats?

• A. RFC 3756
• B. RFC 5218
• C. RFC 2460
• D. RFC 4291

Answer: (A)

Understanding how trust and threats are approached in Neighbor Discovery helps you see why certain documents focus on its security. Neighbor Discovery relies on ICMPv6 messages to map addresses to links, find routers, and maintain reachability, and those messages can be spoofed or abused. The RFC that defines how to model trust on a link for NDP and the kinds of threats it faces is RFC 3756. It lays out the trust relationships between hosts and routers and describes threat scenarios such as spoofed advertisements or other ND abuses, framing why additional protections are needed. This context is what leads to secure Neighbor Discovery mechanisms like SEND. The other documents are about broader IPv6 basics or unrelated cryptographic topics, so they aren’t about NDP threat models.

Understanding how trust and threats are approached in Neighbor Discovery helps you see why certain documents focus on its security. Neighbor Discovery relies on ICMPv6 messages to map addresses to links, find routers, and maintain reachability, and those messages can be spoofed or abused. The RFC that defines how to model trust on a link for NDP and the kinds of threats it faces is RFC 3756. It lays out the trust relationships between hosts and routers and describes threat scenarios such as spoofed advertisements or other ND abuses, framing why additional protections are needed. This context is what leads to secure Neighbor Discovery mechanisms like SEND. The other documents are about broader IPv6 basics or unrelated cryptographic topics, so they aren’t about NDP threat models.