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/[email protected]/
[address-policy-wg] Summary of the PI Task Force's recent discussions
- Previous message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
- Next message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon Aug 11 17:03:37 CEST 2003
Hi, On Mon, Aug 11, 2003 at 02:38:47PM +0200, Joao Damas wrote: > On Monday, August 11, 2003, at 02:05 PM, Gert Doering wrote: > > On Mon, Aug 11, 2003 at 01:43:15PM +0200, Christian Rasmussen wrote: > >> I do not see the reason for using PI space if you're an ISP intending > >> to > >> become LIR, this means you will need to renumber when you get your PA > >> allocation no matter if you use PA or PI, so why not just get a PA > >> assignment from your provider until you can justify the /21? > > > > That's what I thought people would do. But they don't. They want to > > be "independent", and so they go for PI, instead for a suballocation > > from one of their upstreams. > > From an end user (enterprise) point of view, what is wrong with trying > to minimise the pain of changing ISPs (renumbering)? I wasn't judging, I was explaining why the mechanisms in the current policy don't work on real-world people - and as such, the policy is flawed in that respect. (Yes, I see a difference between "startup LIR having problems in getting an initial allocation -> fix policy" and "ccTLDs have problems in getting ICANN to change glue records -> fix ICANN"). > On the other hand, it seems a waste of time and resources for all > involved to give out blocks of size less than the minimum observed to > be routed on the Internet. I know the registries can not guarantee > routing of anything on the network but that does not mean the > registries can not follow 'best common practice' as seen on the net, > and I think everyone agrees that any prefix longer than a /24 doesn't > make it past your border routers. People actually do want PI space for other things (like "internal VPN connections that must be numbered unique but need not be routed"). But that's a different issue. > > (And they don't renumber, of course, but just keep the PI) > Well, yes, would anyone return it if it worked for them? No, and that's part of the problem. If it can be avoided in the first place to have people announce multiple prefixes, then we should aim for that. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 56535 (56318) 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] Summary of the PI Task Force's recent discussions
- Next message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]