[address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Tue Jun 22 12:29:06 CEST 2004
Hi, On Tue, Jun 22, 2004 at 11:08:09AM +0100, Carlos Morgado wrote: > > > This doesn't fly. He can't set his own routing policy and he can't > > > multihome. If he changes the single upstream his customers needs to > > > renumber. > > As of today, "more-specific BGP multihoming" works. So he *can* set > > his own routing policy. > > Can you personaly garantee the upstream suplying the space won't aggregate > his prefix ? And if he does, so what? He will loose traffic, as the *other* ISP will make the more specific visible world-wide, and thus no paid-for packets will arrive at the aggregating upstream. Using a more-specific block out of PA space is a well-established technique in IPv4 today. It's not "beautiful", but it works better than other variants. > If you can't this just turned a nice IPv6 space rental setup. Huh? Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 60210 (58081) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]