wiki/wiki
1
0
Fork 0
mirror of https://git.dn42.dev/wiki/wiki synced 2025-03-14 19:43:32 +00:00
Code Issues Releases Wiki Activity

Updated Frequently-Asked-Questions (markdown)

Browse Source
This commit is contained in:
dn42 wiki 2014-02-24 14:48:12 +01:00
parent fbbd225ccc
commit 67e6016858
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Frequently-Asked-Questions.md
View File

@ -9,7 +9,7 @@ The DN42 registry is stored on multiple monotone servers which sync with each ot
There are some ASes in DN42 that route IPv6 traffic. It is not yet agreed upon what prefixes should be used. The following proposals are the more sane ones: There are some ASes in DN42 that route IPv6 traffic. It is not yet agreed upon what prefixes should be used. The following proposals are the more sane ones:
* Use Site-Local-Addresses (SLAs, also known as Unique Local Addresses, ULAs). This is the *fd00::/8* range. In theory, this would be the obvious winner of this debate. They were standardised for exactly this purpose (not publicly routed networks that still want to use unique prefixes). Sadly, this would require you to announce two prefixes in your LAN if you want to use stateless autoconfiguration and no NAT: The SLA and a globally routed prefix. It is not yet clear if this really works. The relevant RFCs about source address selection demand a behavior that would make this work at the moment (until globally routed addresses from 8000::/1 are used) * Use Unique Local Addresses (ULAs). This is the *fd00::/8* range. In theory, this would be the obvious winner of this debate. They were standardised for exactly this purpose (not publicly routed networks that still want to use unique prefixes). Sadly, this would require you to announce two prefixes in your LAN if you want to use stateless autoconfiguration and no NAT: The ULA and a globally routed prefix. It is not yet known if this really works. [RFC 3484](http://www.rfc-editor.org/rfc/rfc3484.txt) demands a behavior that would make this work at the moment (until globally routed addresses from 8000::/1 are used)
* Use your globally routed PA space. This fixes the LAN-issue, because you only need to announce a single prefix. * Use your globally routed PA space. This fixes the LAN-issue, because you only need to announce a single prefix.
(*TODO*) (*TODO*)