David,
Michel Py wrote: There is no such thing as a default-free zone for IPv6 anyway. Not in the v4 sense, and there is no definition for IPv6 DFZ. I presented this at the 6bone meeting in Minneapolis, might want to have a look at it. http://arneill-py.sacramento.ca.us/ipv6mh/ietf53.ppt
David Kessens Wrote: You can present whatever you want, but I don't have a 'default route' that points to any of my ipv6 peers.
Me neither, but it does not make me nor you part of the DFZ. This is called a defaultless setup. Unless there is a document that gives a definition of "DFZ" specific to IPv6 (I am not aware of it, please point me to it) this is the way it works in v4: - The DFZ and the DFZ's routing table are two different things. The DFZ's routing table expands outside the DFZ itself. - There is no relation in running a defaultless setup and being part of the DFZ. A defaultless setup does get the DFZ's routing table, though. - There is no relation in having a global prefix and being part of the DFZ either. What is the DFZ: It is where tier-1s peer together. In other words, in order to be part of a DFZ, you need to be a tier-1, which means you do not get transit from anybody. If you are a multihomed tier-2, you might run defaultless but you can always dump the traffic on one of your tier-1 transit providers (after all that's why you are paying them); a floating static default route might be useful for tier-2s in case of routing snafus. One of the requirements of the DFZ is that all tier-1s must be fully meshed. Since they do not have transit, they need to know all the routes, and since they announce only their own routes to other tier-1 peers, they get only the connected peer's own routes as well, which means they need to be fully meshed. As of today, the situation we have in IPv6 is that everyone peers nicely together without much filtering, resulting in people actually providing transit to their peers, which exists very little in v4. In v4, the only routes you advertise to your peers are your own, not in v6 today. So, it can be one of three things: 1. There is a specification of "DFZ" specific to IPv6 (I am not aware of it, please send link). 2. The Big Eight have actually completed their full v6 mesh (I am not aware of this, did I miss something?). 3. There is not such thing as an IPv6 DFZ. Michel.