2005-1: Provider Independent IPv6 Assignments for End-sites

Letzter Rechercheversuch: 26.09.2026

Identität verifiziert: 26.09.2026

Diskussionsbeiträge

7

Erste Aktivität

30.04.2005

Letzte Aktivität

28.04.2006

Erste ausdrückliche Haltung

Unterstützung

Letzte ausdrückliche Haltung

Unterstützung

Haltungswechsel

0

Konsistenz der Position

Keine validierte Konsistenzbewertung

Weitere Richtlinien

9

Erste ausdrückliche Haltung: Unterstützung → Letzte ausdrückliche Haltung: Unterstützung · Haltungswechsel: 0

1. 30.04.2005 · Unbekannt

   [ppml] 2005-1:Business Need for PI Assignments

   Validierte Belege sind nicht verfügbar.

   Quellenbelegte Fakten ↗
2. 18.02.2006 · Unterstützung

   [ppml] Fw: IRS goes IPv6!

   If this sort of game passes muster with ARIN, that means any company with at least 200 locations (or at least a plan to have that many) or that pays a few bucks to create 200 shell companies can get a LIR allocation. This is a very slippery slope, and IMHO we need a true PI policy to put a stop to this nonsense. … I've gotten a few private emails that list dozens of companies and other govt orgs that have supposedly done exactly this; it's apparently the best-known hole in IPv6 address policy. If end users are going to be getting space, though, we should provide a more appropriate policy for them (and assign from a dedicated block).

   Quellenbelegte Fakten ↗
3. 19.02.2006 · Unterstützung

   [ppml] Fw: IRS goes IPv6!

   Hey, ISP guys: the big bad enterprises can already get all the precious routing slots they want today; how about you support 2005-1 or 2006-4 so that we can limit the potential for problems (and segregate them into a different block)?

   Quellenbelegte Fakten ↗
4. 20.04.2006 · Verfahrensbezogen oder neutral

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6Assignments for End Sites - Last Call

   My employer will apply for a prefix as soon as we have at least two carriers that offer (a) native IPv4 and IPv6 on the same pipe, (b) at the same price as IPv4-only connectivity, and (c) agree to accept a PI route.

   Quellenbelegte Fakten ↗
5. 27.04.2006 · Unterstützung

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   IMHO, we're trying to meet a real business need that ARIN members and the … community at large are faced with. I think you're right in a sense that … many folks don't think 2005-1 is the ideal policy, but that's not quite the … same as saying we're doing it for the sake of doing it. … In the real world, one often has to choose the least bad from among many bad … alternatives (and no good ones). Consensus is that 2005-1 is less bad than … having no PIv6 policy at all. … Please define "swamp". If each AS gets a single PIv6 prefix, is that really … a swamp? One of the major problems with v4 was that a single org would get … dozens (or hundreds) of separate blocks; we're definitely not repeating that … mistake. We're also not repeating the mistake of handing out blocks without … any sort of oversight or "renewal" process. … There's no explicit limit on the number of prefixes to be assigned under … this policy, but the intent is that it be no more than the number of ASNs … assigned. At worst, this means PIv6 will present an order of magnitude … fewer routes than PIv4; i.e. as long as v4 is still alive, v6 will not be … the problem. … In short, we may be making a mistake here, but if so it's very different … from the mistakes we made with v4. … If PIv6 space becomes a serious operational concern to folks in the DFZ, … they can simply filter the entire space since it's to be from a distinct … block from LIR allocations. This is another major difference from PIv4, … where ISPs had no way of knowing what was PA and what was PI. … IANAL, but I'm pretty sure that if 2005-1 were repealed, ARIN could refuse … to renew PIv6 assignments and they'd all be gone within a year. There's … even other language in the NRPM that states ARIN can, in extreme cases, … revoke assignments and/or allocations that violate policy, so this isn't … something new.

   Quellenbelegte Fakten ↗
6. 27.04.2006 · Unterstützung

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   We'd prefer a better solution, really, but the IETF has failed to provide us … one. Since multihoming is a fundamental business requirement for … enterprises and PI is the only way to make multihoming work today, either … enterprises get PIv6 or v6 doesn't happen. … Please keep in mind that we don't like this situation any more than you do. … OTOH, one could say that large ISPs don't care about the problems that PA … space causes enterprises. 2005-1 is an attempt to find a compromise that's … acceptable to both sides. … Vendors, like any other business, will solve the problems that result in the … highest profits. It's not surprising, therefore, that the vendor-dominated … IETF has failed to produce a new IDR paradigm that makes routing table … growth (and thus constant upgrades) unnecessary. … That's hardly what we're saying. What we're saying is that the floodgates … are wide, wide open for PIv4 yet there's a paltry ~9650 non-transit ASes in … ARIN-land and multihoming is growing slower than Moore's Law. There is no … rational reason to expect that the number of ASes will increase … significantly solely due to 2005-1 since we're reusing the existing bar; if … there is a rush for ASNs, the v4 table will grow more rapidly than the v6 … table due to the inherent prefix-per-ASN differences. PIv6 will be the … least of ISPs' worries if your fears turn out to be correct. … Now, if we had set the bar for PIv6 lower than for PIv4, I'd agree with you … that there's a serious danger of an overwhelming land rush, but that's not … the case. The bar is the same, and that was deliberate. … OTOH, I don't see any ISPs standing up and saying they did some studies of … what the routing table will look like in five to ten years, and have talked … to our vendors and we _do_ think it will be a problem. [sic] … I'd like to hear why you think you'll need to support 1.3M IPv6 routes in … five years. Particularly, I'd like to hear what you think is wrong with the … pro-PIv6 camp's assertions that we should see 1-2 routes per ASN and that … the growth in ASNs will be at or near historical levels. … If we're wrong, we'd really like to know how and why so that we can find a … better compromise.

   Quellenbelegte Fakten ↗
7. 28.04.2006 · Unterstützung

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   2005-1 effectively requires 512 hosts (and 2 pipes) to get a PIv6 block, so … the expected number of assignments under that policy should be 17k. It's … also reasonable to expect most of those assignments will be minimum-sized, … so ISPs will be able to keep them down to 1 slot/org by filtering anything … longer than /48. … I don't think anyone here is proposing, even as a joke, giving PI space to … orgs with 5-10 employees/hosts. … Ditto, though I come at it from a different angle: no matter how much one … may complain about PIv6, PIv4 is an order of magnitude worse, so as long as … v4 is still natively routed and policies are similar, the IPv6 routing table … size is not going to drive router upgrades -- v4 and VPNs will. … If anything, the cost of constant upgrades to support the bloated v4 table … should be viewed as motivation to get customers moving to IPv6. As much as … one may dislike PIv6, one route/ASN is a lot cheaper to build routers for … than today's nearly 10 routes/ASN.

   Quellenbelegte Fakten ↗

Richtliniennachrichten insgesamt: 19