David,

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.

This is by choice and not by necessity, because you could have one if you wanted to. Here are a few definitions I glanced in what we are currently working on: 1. At the top level, the `default-free zone', it's not possible to define a default route. BGP speakers in the default-free zone really do need to have a route for every possible Internet destination. 2. The core of the Internet is also called the default-free zone (DFZ) because backbone service providers must maintain a complete map of all globally visible network prefixes reachable throughout the Internet: no default routes are allowed. 3. The Default-Free Zone (DFZ) of the Public Internet is where routers MUST maintain routing entries for all reachable destinations. In short: A router in the DFZ can NOT have a default route. These are tier-1 transit providers. Opposed to tier-2, where you CAN configure a default route to one or more of your transit providers; it actually is common practice for tier-2 to have a floating static default route as backup in case of BGP snafus. As of today, I have not seen a single IPv6 router where you could not configure a default route, as filtering (or the lack thereof) makes almost every peer a transit provider. The ipv6mh mailing list had this discussion a while ago and here is the definition we currently use: DFZ: the subset of routers that do not have a default route and do not receive a full routing table from a single peer. Michel.