FAQ.md
... ...
@@ -13,7 +13,7 @@ The DN42 registry is stored on multiple monotone servers which sync with each ot
13 13
14 14
There are some ASes in dn42 that route IPv6 traffic. They generally use the "Unique Local Address" range (ULA, *fd00::/8*) defined by [RFC 4193](https://tools.ietf.org/html/rfc4193). A minor disadvantage of using ULAs is that you need to announce two prefixes in your LAN if you want to use stateless autoconfiguration and no NAT: The ULA and a globally routed prefix. Usually, this works fine, but it may cause issues with legacy clients which don't implement [RFC 6172](https://tools.ietf.org/html/rfc6172) correctly.
15 15
16
-To get your own ULA range, simply pick a *random* prefix of the form fdXX:XXXX:XXXX/48 and enter it into the dn42 registry to make sure there are no collisions.
16
+To get your own ULA range, simply pick a **random** prefix of the form fdXX:XXXX:XXXX/48 and enter it into the dn42 registry to make sure there are no collisions.
17 17
18 18
In theory, globally routable IPv6 networks could also be used inside dn42. However, this would complicate prefix filtering for everybody, and might lead to strange routing patterns, where packets are routed partially on dn42 and partially through the Internet. Most dn42 ASes filter such IPv6 prefixes, which means you'd have a hard time making them reachable in dn42.
19 19