a86eb2d4aa045e8e2b9f1762001a973c9b84097d
FAQ.md
... | ... | @@ -1,6 +1,8 @@ |
1 | +# Frequently Asked Questions |
|
2 | + |
|
1 | 3 | [[_TOC_]] |
2 | 4 | |
3 | -## Why are you using monotone for the registry? Why not GIT? |
|
5 | +### Why are you using monotone for the registry? Why not GIT? |
|
4 | 6 | |
5 | 7 | 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. |
6 | 8 | |
... | ... | @@ -20,7 +22,7 @@ There are some ASes in DN42 that route IPv6 traffic. It is not yet agreed upon w |
20 | 22 | At the moment, it is safe to assume 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. |
21 | 23 | |
22 | 24 | |
23 | -## Why are you using ASN in the 76100-76199 range? |
|
25 | +### Why are you using ASN in the 76100-76199 range? |
|
24 | 26 | |
25 | 27 | Yes, we know that this is not private ASN space (rather, it is part of the reserved block 65552-131071, see [IANA](http://www.iana.org/assignments/as-numbers/as-numbers.xhtml)). |
26 | 28 | |
... | ... | @@ -33,7 +35,7 @@ Fortunately, [RFC6996](http://tools.ietf.org/html/rfc6996) defines a new private |
33 | 35 | We now encourage dn42 users to use the newly-allocated ranges in **4242420000-4242429999**. See the [registry page](Services-Whois#AS-numbers) for details. |
34 | 36 | |
35 | 37 | |
36 | -## What BGP daemon should I use? |
|
38 | +### What BGP daemon should I use? |
|
37 | 39 | |
38 | 40 | This is really up to you: that's the magic of open protocols. |
39 | 41 |