bk99.de entertain the web since 1997

bk99.de
RFC · IPv6Standard explained

RFC 8200: The IPv6 base standard

Summary

RFC 8200 replaces the original IPv6 specification and consolidates the matured base standard. An Internet Standard can become more precise through operational experience without changing its architecture. Deploying IPv6 requires full support in security and monitoring.

Ideas

  • The fixed base header stays leaner than in IPv4.
  • Extension headers carry optional functions.
  • Only endpoints fragment packets.

Facts

  • RFC 8200 replaces RFC 2460.

Remarks

  • RFC 8200 has the status “Internet Standard”; current errata and successor documents should also be checked.

Recommendations

  • Treat IPv6 as regular production traffic.
  • Test MTU, extension headers and ICMPv6 deliberately.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2006

RFC 4291: IPv6 addressing architecture

RFC 4291 organises IPv6 unicast, anycast and multicast addresses as well as prefix notation. Address types map communication scope directly into the architecture. A large address space still requires disciplined planning.

RFC · 1998

RFC 2460: IPv6: A larger address space and a simpler header

RFC 2460 specifies the original IPv6 base with 128-bit addresses, extension headers and a new fragmentation logic. RFC 2460 was superseded by RFC 8200. IPv6 fixes architectural limits without automatically solving all operational problems.

Hostblogger · 2018

Rolling out IPv6 quietly on a web hosting platform

Manuel Schmitt reports on the gradual IPv6 rollout for all existing and new web hosting packages and their domains. Since December 2018, all old and new web hosting packages had been reachable via IPv6. The rollout covered all associated domains.