fix(ipam): continue ipv6

Author: RoRoJ

network/ipam/reference-content/ipv6.mdx

@@ -63,7 +63,9 @@ You can attach one or multiple public (flexible) IPv6 addresses to your Elastic
 
 ### Private IPv6 
 
-When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach a reserved IP to a custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address, suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
+When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network.  You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use.
+
+You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
 
 ### Going further
 
@@ -78,16 +80,74 @@ Go further with Elastic Metal and IPv6 in the following documentation:
 
 The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server’s primary IP and also as a failover IP utilizing the concept of a virtual MAC address.
 
-- Dedibox
-- Public Gateways
-- VPC and Private Networks
+Full information on IPv6 with Dedibox can be found in our [dedicated documentation](/dedibox-network/ipv6/).
+
+### Load Balancer and IPv6
+
+Scaleway Load Balancers are compatible with IPv6. 
+
+### Public IPv6 
+
+You can attach a maximum of one (flexible) IPv6 address to your Load Balancer, in addition to a flexible IPv4 address. The Load Balancer cannot have **only** an IPv6 address. Once attached, the IPv6 address cannot be detached or changed for a different one. Each flexible IPv6 address is a `/64` IPv6 subnet.
+
+### Private IPv6 
+
+When you attach a Load Balancer to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use.
+
+### IPv6 at the backend
+
+Load Balancers can also use IPv6 to communicate with their backend servers. When you attach backend servers to a Load Balancer, you can either specify their public IPv6 address, or their private IPv6 address (if the Load Balancer and the backend servers are attached to the same Private Network).
+
+### Going further
+
+Go further with IPv6 and Load Balancers with the following documentation:
+- [How to create and manage flexible IPs](/network/load-balancer/how-to/create-manage-flex-ips/)
+
 
-- Load Balancer
+### VPC, Private Networks and IPv6
 
-## Configuring public IPv6
+VPC and Private Networks are compatible with IPv6. 
+- When you create a Private Network in a VPC, an IPv6 CIDR block is automatically defined for it. This is a `/64` block, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks.
+- All IPv6-compatible resources will automatically receive an IPv6 address when they join a Private Network.
+- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/network/ipam/how-to/reserve-ip/)
+- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/network/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPV4 and IPV6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process.
 
-## Configuring private IPv6
+## Other products and IPv6
+
+Products other than those listed here do not officially support IPv6. These non-compatible products include Managed Databases, Kubernetes Kapsule and Public Gateways. 
+
+Please open or upvote a [feature request](https://feature-request.scaleway.com/) to register your interest in IPv6 for these resources. 
+
+Alternatively, get in touch on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) if you'd like to find out more about IPv6 compatibility of these or other products.
 
 ## Security considerations
 
+Security Concerns with IPv6:
+
+
+
+Default Configuration Risks: Many operating systems enable IPv6 by default, potentially creating unmonitored entry points if not properly configured.
+
+Dual Stack Complexity
+Running both IPv4 and IPv6 ("dual stack") can double the attack vectors if security measures are not equally robust for both protocols.
+Expanded Attack Surface: The enormous address space of IPv6 makes scanning for active hosts challenging, but poorly secured addresses can still be discovered through DNS or other means.
+
+Tips to Mitigate IPv6 Security Risks:
+Implement IPv6-specific Firewalls
+Configure firewalls to handle IPv6 traffic explicitly, ensuring that rules and policies are as robust as those for IPv4.
+
+Disable Unnecessary IPv6 Features
+Turn off IPv6 on interfaces or systems that do not require it to reduce the attack surface.
+
+Monitor IPv6 Traffic
+Ensure that intrusion detection and prevention systems (IDS/IPS) are configured to analyze both IPv4 and IPv6 traffic.
+
+Secure Routing Protocols
+Use routing protocol security mechanisms like authentication and encryption to protect IPv6 routing.
+
+Audit DNS and Address Exposure
+Regularly audit DNS records and public IPv6 addresses to minimize exposure of internal resources.
+
+By addressing these concerns proactively, users can securely adopt IPv6 in their cloud environments while leveraging its benefits.
+
 ## Troubleshooting