This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[ipv6-wg] Re: [address-policy-wg] Re: 200 customer requirements for IPv6
- Previous message (by thread): [ipv6-wg] Re: [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [ipv6-wg] Re: [address-policy-wg] Re: 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bmanning at vacation.karoshi.com
bmanning at vacation.karoshi.com
Wed Dec 7 23:01:48 CET 2005
On Wed, Dec 07, 2005 at 09:47:24PM +0100, Iljitsch van Beijnum wrote: > On 7-dec-2005, at 13:12, Per Heldal wrote: > > >>Geographical aggregation does not REQUIRE free transit. > > >[Does Fedex deliver goods to everybody in a region if only one > >customer > >in the region pays for their service?] > > That's not the right analogy. The right analogy is: does a Fedex > truck driver in New York have a street map for Berlin? Answer: no. > The NY Fedex driver knows that packages for Berlin should go to > Europe. More specific routing information becomes available as the > package gets closer to its destination. > > So Fedex does aggregate on geography, but only _internally_. Fedex as > a whole still has all the detailed information for the entire world. > (Well, the parts they serve at least.) Interior Gateway Protocols... kind of like OSPFv3 for v6? --bill > > Iljitsch > > -- > I've written another book! http://www.runningipv6.net/ >
- Previous message (by thread): [ipv6-wg] Re: [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [ipv6-wg] Re: [address-policy-wg] Re: 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]