From 2f6331f83afcc584b1b90c4b9150031adf3d3f06 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 21 Nov 2019 10:45:04 +0100 Subject: [PATCH 1/3] IPv6 compat article --- .../contents.lr | 74 +++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 content/u/blog/draft-for-ipv6-compatibility-check/contents.lr diff --git a/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr new file mode 100644 index 0000000..262468d --- /dev/null +++ b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr @@ -0,0 +1,74 @@ +title: Vendor information for IPv6 compatibility: [draft] +--- +pub_date: 2019-11-21 +--- +author: ungleich +--- +twitter_handle: ungleich +--- +_hidden: no +--- +_discoverable: yes +--- +abstract: +How to make your hardware IPv6 compatible +--- +body: + +Here at [ungleich](https://ungleich.ch) we see many different devices +and software running or not running in IPv6 only networks. This +article summarises some features we see required in IPv6 compatible +devices (including software). + +Devices that don't fully complain with the checklist below will be +removed in the near future from our infrastructure, as their +maintenance cost has become too high. + +The wording is orientated on +[RFC2119](https://tools.ietf.org/html/rfc2119). + +**This document is an early draft** + +## IPv6 autoconfiguration + +All devices must assign themselves an IPv6 address upon receival of a +router advertisement (compare +[RFC4861](https://tools.ietf.org/html/rfc4861). + +## IPv6 listener + +If the device is providing any service, all services **must** bind to +IPv6 sockets (compare [RFC3493](https://tools.ietf.org/html/rfc3493)). + +## Outgoing connections + +All devices **must** support requesting **all** resources via IPv6 +only connections. This does not imply that the vendor resource has to +be reachable by IPv6, as the network operator might provide a NAT64 +service. + + +## Support for IPv6 DNS servers via router advertisements + +All devices **must** read the DNS server and and DNS search path from the +router advertisements and **must** configure the DNS servers and DNS +search path accordingly. + + +## Full NAT64/DNS64 compatibility + +All devices **must** be fully compatible to reach the IPv4 Internet +through the means of NAT64 and DNS64. In particular all outgoing +connections **must** be possible by IPv6 only, even if resources in +the IPv4 Internet are requested. + + +## No hardcoded IPv4 addresses + +IF your device needs to connect to a service (f.i. for updates, +reporting, etc.), it **must not** have any hardcoded IPv4 address. + +## Updates + +IF a device is receiving software updates, it must be able to receive +software updates in IPv6 only networks. From cdd960110686d44ad1e35322136a82a61f2163b7 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 21 Nov 2019 10:48:39 +0100 Subject: [PATCH 2/3] ++fixes --- .../draft-for-ipv6-compatibility-check/contents.lr | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr index 262468d..9741116 100644 --- a/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr +++ b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr @@ -27,26 +27,28 @@ maintenance cost has become too high. The wording is orientated on [RFC2119](https://tools.ietf.org/html/rfc2119). -**This document is an early draft** +**This document is an early draft**. If you have any comments / +improvements, please help us to improve it on the [IPv6 Chat](https://IPv6.chat). ## IPv6 autoconfiguration All devices must assign themselves an IPv6 address upon receival of a router advertisement (compare -[RFC4861](https://tools.ietf.org/html/rfc4861). +[RFC4861](https://tools.ietf.org/html/rfc4861)). ## IPv6 listener If the device is providing any service, all services **must** bind to -IPv6 sockets (compare [RFC3493](https://tools.ietf.org/html/rfc3493)). +IPv6 sockets (compare +[RFC3493](https://tools.ietf.org/html/rfc3493)). Device **may** also +bind to IPv4 sockets. ## Outgoing connections All devices **must** support requesting **all** resources via IPv6 only connections. This does not imply that the vendor resource has to be reachable by IPv6, as the network operator might provide a NAT64 -service. - +service. Devices **may** also try connecting by IPv4. ## Support for IPv6 DNS servers via router advertisements @@ -70,5 +72,5 @@ reporting, etc.), it **must not** have any hardcoded IPv4 address. ## Updates -IF a device is receiving software updates, it must be able to receive +IF a device is receiving software updates, it **must** be able to receive software updates in IPv6 only networks. From 7bcacb5027d4f675486755c0bb758edc736bbbef Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 21 Nov 2019 10:49:21 +0100 Subject: [PATCH 3/3] ++version info --- .../u/blog/draft-for-ipv6-compatibility-check/contents.lr | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr index 9741116..f157537 100644 --- a/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr +++ b/content/u/blog/draft-for-ipv6-compatibility-check/contents.lr @@ -27,8 +27,9 @@ maintenance cost has become too high. The wording is orientated on [RFC2119](https://tools.ietf.org/html/rfc2119). -**This document is an early draft**. If you have any comments / -improvements, please help us to improve it on the [IPv6 Chat](https://IPv6.chat). +**This document is an early draft - version 0.1**. +If you have any comments / improvements, +!please help us to improve it on the [IPv6 Chat](https://IPv6.chat). ## IPv6 autoconfiguration