Classify IPv6 unicast, anycast, and multicast addresses before policy

Treat this document as a focused evidence review: Classify IPv6 unicast, anycast, and multicast addresses before policy. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 4291 — IP Version 6 Addressing Architecture from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An IPv6 unicast address identifies one interface, and traffic sent to it is delivered to that interface. The research record locates this support at Section 2 (IPv6 Addressing), Unicast definition.
• An IPv6 anycast address identifies multiple interfaces and delivers a packet to the nearest one according to routing distance. The research record locates this support at Sections 2 (IPv6 Addressing) and 2.6 (Anycast Addresses).
• An IPv6 multicast address delivers to every interface in its group, and multicast replaces IPv6 broadcast addressing. The research record locates this support at Section 2 (IPv6 Addressing), Multicast definition.

The source support ends with the statements listed above. Use them to examine address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains in the applicable environment, not to imply a wider guarantee.

What the source does not establish

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Section 2 (IPv6 Addressing), Unicast definition, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections 2 (IPv6 Addressing) and 2.6 (Anycast Addresses), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 2 (IPv6 Addressing), Multicast definition, which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

A reviewer should be able to retrace the decision from Section 2 (IPv6 Addressing), Unicast definition; Sections 2 (IPv6 Addressing) and 2.6 (Anycast Addresses); Section 2 (IPv6 Addressing), Multicast definition through configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Record what was collected, where, when, by whom, and which system or role it represents.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• RFC 4291 — IP Version 6 Addressing Architecture — RFC Editor / Internet Engineering Task Force