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/
[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 ]
Carlos Morgado
chbm at cprm.net
Tue Jun 22 12:08:09 CEST 2004
On Tue, Jun 22, 2004 at 08:45:29AM +0200, Gert Doering wrote: > Hi, > > On Tue, Jun 22, 2004 at 07:44:23AM +0200, Kurt Erik Lindqvist wrote: > > > If you estimate that you will continue to be very small, you could use > > > a /40 or such from one of your upstream ISPs (which is a problem > > > *today*, > > > as there are not enough upstream ISPs, indeed). > > > > 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 ? If you can't this just turned a nice IPv6 space rental setup. -- Carlos Morgado <chbm at cprm.net> - Internet Engineering - Phone +351 214146594 GPG key: 0x75E451E2 FP: B98B 222B F276 18C0 266B 599D 93A1 A3FB 75E4 51E2 The views expressed above do not bind my employer.
- 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 ]