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.
\nThe official RFC 4291 — IP Version 6 Addressing Architecture from RFC Editor / Internet Engineering Task Force supports the following bounded statements:
\nThe 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.
\nThis 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.
\nDSE 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.
\nDo 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.
\nA 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.
\nPreserve 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.
\n