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.
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. 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 correctly.
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.
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.
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.
Yes, we know that this is not private ASN space (rather, it is part of the reserved block 65552-131071, see IANA).
We used to assign ASN in the 64600-64855 range, where you would get ASN 64600+X if you had 172.22.X.0/24. Since we are now assigning /25 by default, and we have extended the address range to include 172.23.0.0/16, this is legacy.
Another issue with the private ASN range 64512-65534: other projects are also using it (for instance, Freifunk, Anonet, etc), which can lead to conflicts.
Fortunately, RFC6996 defines a new private ASN range: 4200000000-4294967294. Given the size of this range, there is little chance of running into a conflict.
We now encourage dn42 users to use the newly-allocated ranges in 4242420000-4242429999. See the registry page for details.
This is really up to you: that's the magic of open protocols.
As of 2014, most people seem to use either Quagga or Bird (with a growing preference for Bird). You may also encounter users of OpenBGPd. Even more occasionally, people use hardware BGP routers in dn42, for instance Extreme Networks hardware.
Yes, but only when connecting to this site via dn42 over SSL.
Last edited by dn42 wiki, 2017-10-16 08:27:16