Changes in fbbd225: Created faq (markdown)

				Frequently-Asked-Questions.md
			
          @@ -0,0 +1,17 @@

          +## Why are you using monotone for the registry? Why not GIT?

          +

          +There is an important difference between the data model of monotone and GIT: In GIT branches *are* HEADs, while in monotone, branches are a list of HEADs. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In GIT, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.

          +

          +The DN42 registry is stored on multiple monotone servers which sync with each other. This is not possible in GIT, because the GIT servers don't know how to handle merge conflicts. In monotone, the servers just sync the conflict.

          +

          +

          +## What about IPv6 in DN42?

          +

          +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 your globally routed PA space. This fixes the LAN-issue, because you only need to announce a single prefix.

          +

          +(*TODO*)

          +

          +At the moment, it is probably save to say that everyone doing IPv6 routing accepts at least prefixes from fd00::/8 with prefix lengths between 48 and 64 bits (inclusive) if they are part of the registry.

...	...	@@ -0,0 +1,17 @@
	1	+## Why are you using monotone for the registry? Why not GIT?
	2	+
	3	+There is an important difference between the data model of monotone and GIT: In GIT branches are HEADs, while in monotone, branches are a list of HEADs. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In GIT, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.
	4	+
	5	+The DN42 registry is stored on multiple monotone servers which sync with each other. This is not possible in GIT, because the GIT servers don't know how to handle merge conflicts. In monotone, the servers just sync the conflict.
	6	+
	7	+
	8	+## What about IPv6 in DN42?
	9	+
	10	+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:
	11	+
	12	+* 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)
	13	+* Use your globally routed PA space. This fixes the LAN-issue, because you only need to announce a single prefix.
	14	+
	15	+(TODO)
	16	+
	17	+At the moment, it is probably save to say that everyone doing IPv6 routing accepts at least prefixes from fd00::/8 with prefix lengths between 48 and 64 bits (inclusive) if they are part of the registry.