April 2006 - address-policy-wg

Just say *NO* to PI space -- or how to make it less destructive
by Pekka Savola 12 May '06

12 May '06

Hi, I don't support PI space to end-sites. We have to get rid of the notion that a random end-site has any business whatsoever in mucking with the global routing tables, either by making it much larger than need be or by polluting it with needless dynamicity. Example of the latter: deploying inbound traffic engineering adjustment solutions which result in thousands of daily flaps in the advertisements, as shown by Huston's analysis. We have way too much trouble with clueless ISPs to also add (or continue to add) end-sites to the mix... .... Now, from practical point of view, it seems there is strong "need" for PI, and it might be a PI policy of some kind might actually get through. If so, the policy should be such that it minimizes the bad effects of PI and encourages people to use other solutions if those are viable for them (unfortunately, the only way to achieve that appears to be $$$$), in particular (in the rough order of importance): 1. Each assignment must be accompanied by a recurring fee (at least 1000-2000 USD/EUR a year, preferably 5000+). This is peanuts (compared to other costs) to anyone who actually needs this multihoming solution. However, this ensures at least some minimum usage barrier ("those who don't really need this can use different multihoming solutions"), and recovery of the resources back to RIR after the company has gone bankrupt or no longer needs the addresses. If you don't know where to put the extra money, donate it to ISOC or something. 2. one-size-fits-all assignments, period. You get a /48 or /32 (I don't have much preference here), but you must not be able to justify for larger space. This is to avoid the organization from getting a larger block and chopping it into smaller pieces and polluting the global routing table with more specifics which would get past prefix length filters. 3. assignments from a separate address block, set aside for PI. To ease strict "assignment-size only" filtering of these blocks. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

32 86

IPv4-HD-Ratio proposal
by Thor-Henrik Kvandahl 03 May '06

03 May '06

Hi all, here are my *personal* opinion on this proposal. I do not support this proposal, and my reasons for this are: * This proposal increases the rate of consumption of IPv4. * It favourises the large ISPs. * In the presentation on RIPE 52, Tuesday by Filiz Yilmaz, we where told that this proposal was abandoned by ARIN and APNIC, and one representative from LacNIC also stood up and expressed their conserns. I have not heard anything from AfriNIC, but I cannot see why they would want to implement this policy. I feel if will be arrogant of the RIPE community to disregard the other RIRs conserns and implement this policy. And I also have to agree with Gert Doering who said in the address policy WG that there has been very quiet around this proposal, and that the reason for this can be that ETNO claims thay "unanimously support this proposal". -- Thor-Henrik Kvandahl no.telenor

7 11

comments on IP Assignments for anycasting DNS (2005-2)
by Edward Lewis 27 Apr '06

27 Apr '06

Referring to: http://www.ripe.net/ripe/policies/proposals/2005-2.html The author's email address on the page is "@localhost". A few thoughts on the restrictions on this: "gTLD" usually means "generic Top Level Domain". There are also "sTLD" - sponsored TLD. (Check http://en.wikipedia.org/wiki/GTLD, at the bottom of the page there's a box that breaks gTLDs into sTLDs and other categories.) Sometimes "interesting" zones are not the TLD but one under the TLD. E.g., .co.tld. or .com.tld. I think that these should be eligible. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Nothin' more exciting than going to the printer to watch the toner drain...

2 1

AW: [address-policy-wg] Just say *NO* to PI space -- or how to make it less destructive
by Ruchti, Marcus 27 Apr '06

27 Apr '06

Hi Dennis, I don't think flapping routes will increase due to the assignments of PI space, as in the most cases ISP's are requesting those for customers and offers managed multihoming solutions. So announcing these routes into BGP is the responsibility of an ISP. Regards Marcus Ruchti COLT Telecom -----Ursprüngliche Nachricht----- Von: address-policy-wg-admin(a)ripe.net [mailto:address-policy-wg-admin@ripe.net] Im Auftrag von Dennis Lundström Gesendet: Donnerstag, 20. April 2006 16:25 An: Pekka Savola Cc: ppml(a)arin.net; address-policy-wg(a)ripe.net; global-v6(a)lists.apnic.net Betreff: Re: [address-policy-wg] Just say *NO* to PI space -- or how to make it less destructive Hi Pekka. Totally agree with you there. At the moment as we have PI with IPv4, and I'll guess there will be lot's of fuzz dropping It. On the other hand. If PI allocations were no more, then the same people you nag about here would try to become their own ASN:s. And the percentage of peers running on cheap 'o pc-boxes would quite possibly increase. Resulting in that the problem with flapping routes would probably remain, or even get worse. So the problem is really. How do we regulate PI to only be an accepted solution for extreme cases? And still have a fair policy to those who really needs this feature. Best regards. --Dennis Lundström GippNET Pekka Savola wrote: > Hi, > > I don't support PI space to end-sites. We have to get rid of the > notion that a random end-site has any business whatsoever in mucking > with the global routing tables, either by making it much larger than > need be or by polluting it with needless dynamicity. > > Example of the latter: deploying inbound traffic engineering > adjustment solutions which result in thousands of daily flaps in the > advertisements, as shown by Huston's analysis. > > We have way too much trouble with clueless ISPs to also add (or > continue to add) end-sites to the mix... > > .... > > Now, from practical point of view, it seems there is strong "need" for > PI, and it might be a PI policy of some kind might actually get > through. > > If so, the policy should be such that it minimizes the bad effects of > PI and encourages people to use other solutions if those are viable > for them (unfortunately, the only way to achieve that appears to be > $$$$), in particular (in the rough order of importance): > > 1. Each assignment must be accompanied by a recurring fee (at least > 1000-2000 USD/EUR a year, preferably 5000+). This is peanuts > (compared to other costs) to anyone who actually needs this > multihoming solution. However, this ensures at least some minimum > usage barrier ("those who don't really need this can use different > multihoming solutions"), and recovery of the resources back to RIR > after the company has gone bankrupt or no longer needs the addresses. > If you don't know where to put the extra money, donate it to ISOC or > something. > > 2. one-size-fits-all assignments, period. You get a /48 or /32 (I > don't have much preference here), but you must not be able to justify > for larger space. This is to avoid the organization from getting a > larger block and chopping it into smaller pieces and polluting the > global routing table with more specifics which would get past prefix > length filters. > > 3. assignments from a separate address block, set aside for PI. To > ease strict "assignment-size only" filtering of these blocks. > ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security(a)colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

5 4

RE: [address-policy-wg] Renumbering sites (Was: Just say *NO* to PI space -- or how to make it lessdestructive)
by Michel Py 26 Apr '06

26 Apr '06

Gert, >> Michel Py wrote: >> Most of the more experienced network managers out there will >> tell you this: I don't want to go through this again. > But at the same time, most of the more experienced network > managers have been through it a couple of time, and will > understand the necessity... :-) > (We had to change the IP addresses for our recursive DNS servers > 3 times by now, and making sure all customers update their configs > *was* a nightmare Renumbering DNS servers is 1% of renumbering a large enterprise setup. Imagine if you had them change not only DNS, but all of their DHCP scopes, firewall rules, host files, batches, printers, renumber their active directory controllers (ever tried to change the IP address on a windows box that assumes FSMO roles?) etc etc. > - nevertheless, it was the correct thing to do Good for you. In my world, the correct thing to do is the one that has a positive impact on the bottom line. > Jørgen Hovland wrote: > Renumbering is as easy as you want it to be. I love guys like Jørgen. One day they'll find someone fool enough to let them touch a big network, they'll make a mess, and their management will suddenly understand the value of paying me 2k per day so another disaster does not happen. Michel.

2 1

RE: [address-policy-wg] Renumbering sites (Was: Just say *NO* to PI space -- or how to make it lessdestructive)
by Michel Py 26 Apr '06

26 Apr '06

> Wilfried Woeber wrote: > Why does the laptop store the *addresses* instead of an (FQ)DN? Mine is configured that way because I want to be able to get in remotely in case of a DNS failure so I can fix the DNS :-D Other reason: VPNs based on FQDNs have a tendency to timeout, especially at the first attempt from a remote location (because the FQDN is not cached and has to go up to the root). Also DNS requests go over UDP, which is unreliable. It happens all the time that Joe Blow traveling somewhere reports the next day that he could not check his email or download the sales report because the VPN was not working (because Joe either is not smart enough to retry or finds it a good excuse to go to the bar instead). Next time he goes out the VPN is configured with the hardcoded IP address of the VPN server. In the end, it does not matter why. It's out there, and has to be dealt with. > Jeroen Massar wrote: > Renumbering is *NOT* simple and *CAN't* be automated (no remote > company will allow you full automatic access to change things in > their setup, think firewall rules for instance...) Indeed. Even if they did, it would be logistically impossible. I'm currently configuring an IPSEC tunnel going to a very large corporation. There are thousands of tunnels, configured on every router brand and model man has ever made; each is unique. An automated tool to change this is not in the realm of possible. This leaves the large company with having to deal with thousands of different people with issues such as half of the techs that originally configured the thing are no longer there, nobody remembers the router's password, etc. Renumbering any sizeable organization is _always_ a very costly proposition. It requires allocating valuable resources for weeks to prepare and more to carry. Plus, in any renumbering I have done some issues popped out for weeks after the renumbering. Renumbering generates a steady flow of trouble tickets that require more resources to deal with _and_ make the network guys look like idiots. Only rookies that have never been in the trenches in the real world consider renumbering easy. Most of the more experienced network managers out there will tell you this: I don't want to go through this again. Michel.

8 9

RE: Question
by Bound, Jim 24 Apr '06

24 Apr '06

Tony, Excellent response and educational for sure. It is my belief that the corporate business model today for operating networks may be broken and I think you supported that below? If not my apologies for bad parsing? Their models were fine for an IPv4 world where NAT was required and some even confuse NAT with securing ones network (and some programs in the U.S. Government) and that is simply bad policy and view. In the interim can this be resolved by RIRs creating some kind of additional wording that address reclaim will be done in manner that is negotiable, and do no harm to corporate or government business operations? This would buy us time to work on the issue and stop the FUD around this topic? Also I am willing to sponsor a world wide IPv6 Forum BOF on PI and addressing you can lead as ajunct to one of our regular meetings you can lead for an entire day and we get the right players in the room. So think about that as another option too. But do enjoy the beach this thread does not have to be resolved this week :--) Really want to hear from all of you and discussion Terry D., Latif, Yanick, Dave G. Mike B. etc. Thanks /jim > -----Original Message----- > From: Tony Hain [mailto:alh-ietf@tndh.net] > Sent: Friday, April 07, 2006 7:57 PM > To: 'PPML'; address-policy-wg(a)ripe.net > Cc: 'Richard Jimmerson'; Bound, Jim; 'Latif Ladid ("The New > Internet based on IPv6")'; 'Davis, Terry L'; > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; 'Brig, > Michael P CIV DISA GES-E'; Pouffary, Yanick; 'Green, David B > RDECOM CERDEC STCD SRI' > Subject: RE: Question > > A public answer to a private question as I have been sitting > on a beach for awhile without the laptop and missed some > related conversations ... :) > > > Is the outcome really open for discussion on the PI issue? > It doesn't > > sound like it is. > > In the minds of some the route scaling issue outweighs any > argument for PI. > When taken to its extreme, there is a valid point that a > broken routing system serves no one. At the same time the > dogmatic stance by the ISPs enforcing lock-in is just as > broken both for large organizations with financial or legal > requirements for operational stability, and the individual > consumer/small business with limited budgets looking for true > competition. The hard part is finding the middle ground in a > way that limits the exposure to a potential routing collapse. > > I personally refuse to declare some needs legitimate and > others not, as the only point of such differentiation is to > establish a power broker. When all uses are legitimate, the > problem boils down to the technical approach that can be > scaled as necessary to contain growth in the routing system. > This is the logic that leads me to the bit-interleaved geo > that can be aggregated in varying size pockets as necessary > using existing BGP deployments. We can start flat and > implement aggregation over time when a region becomes too > large to handle. One nice side effect of this geo approach is > that it mitigates the continuing political demands for > sovereign rights to IPv6 space. > > Any aggregation approach will force the business models to > change from current practice. That is not as bad a thing as > the alarmists will make it out to be, because their > accountants are claiming the current model is a broken money > looser as it is (which if so means they will eventually > change anyway). The primary difference is that there will > need to be aggregation intermediaries between the last-mile > and transit providers. The current model eliminates these > middle-men by trading off their routing mitigation service > against a larger routing table (actually they already exist > in the right places but are currently limited to layer2 media > aggregators). The anti-PI bunch is trying to use social > engineering to directly counter the bottom line business > reality that the customer will always win in the end. > Rather than accept this situation and constructively work on > the necessary business model and technology developments, > they effectively stall progress by staunchly claiming there > is no acceptable technical approach that works within the > current business structure. > > Making the RIRs be the police deciding who qualifies for PI > and who does not just adds to their workload and raises > costs. The beneficiaries of this gatekeeper approach are the > ISPs that claim they need full routing knowledge everywhere, > while the cost burden for supporting the waste-of-time > qualification/evaluation work is borne by the applicant. > Given that the most vocal and organized membership in the RIR > community are the ISPs it is easy to understand why it would > seem like the PI issue is already decided as closed. I tend > to believe it will just drag out until enough of the > corporate world becomes aware of the IPv4 exhaustion in light > of their growth needs that they collectively appear at their > RIR and demand an immediate solution. Unfortunately this > 'wait till the last minute' tactic will likely result in a > reactionary quickie with its own set of long term side effects. > > A while back I tried to hold a BOF on geo PI in the IETF, but > was told that > shim6 was the anointed solution. Now that at least nanog has > told the IAB where to put shim6 it might be possible to get > the current IESG to reconsider. In any case the result would > be a technical approach that would still require RIRs to > establish policies around. As long as they are dominated by > the ISPs it will be difficult to get real PI. > > Tony > >

15 25

Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
by Thomas Narten 22 Apr '06

22 Apr '06

"Stephen Sprunk" <stephen(a)sprunk.org> writes: > OTOH, it's ridiculously easy to get PIv4 space today (512 hosts and two > pipes or tunnels), and there's not all that many companies doing it. It's > not growing much either. The doors are already wide open for a land rush > and nobody is taking ARIN up on it. Why does everyone assume it'll happen > with v6 if it's not happening with v4, which _is_ useful today? Because today, people are a lot more network savvy, and they now understand the potential value of getting real PI space. Moreover, anyone who understands history, realizes that getting PI space may become harder in the future, rather than easier. Consequently, it would be a smart business move to get PI space ASAP, in case the rules change down the road. i.e, a rather prudent investment. Thomas

3 2

Re: HD-ratio Proposal - Last Call has ended. Cosensus not reached.
by Hans Petter Holen 20 Apr '06

20 Apr '06

RIPE NCC Policy Coordinator wrote: > PDP Number: 2005-01 > HD-ratio Proposal > > Dear Hans Petter > > This is to remind you that the "Last Call" period for the proposed > change to RIPE Document ripe-368 has ended. > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2005-1.html > > Please reply to this e-mail to let me know how you would like to proceed. > > * Consensus has been reached. We should publish the policy. > > * Consensus has not been reached. You want to > > * withdraw the policy; > > * return to the review phase (please tell us what duration to set for > the review period); or > The chairs of the Address policy working group have consulted and are divided on the matter of this policy. The outcome of this discussion and consultation with wg-chairs and RIPE Chair in general is that we see a clear consensus in favor of the current proposal. We do see a growing opposition based on the perception of how this will influence future address allocations to emerging regions. I will therefor return the policy to the review phase, for further discussion on the mailing-list and on the upcoming RIPE meeting. As a side note the matter of how RIPE should relate to other organizations in our policy making process I would like to make the following remark; RIPE policy is made by individual contributions to mailing lists and at RIPE meetings. Not by meetings of other organizations. Our discussions should be based on technical arguments in the relevant RIPE fora. Best Regards, Hans Petter Holen Address Policy Chair

2 2

New Document available: RIPE-376
by RIPE NCC Document Announcement Service 20 Apr '06

20 Apr '06

<<< our apologies for duplicate e-mails >>> New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-376 Title: Assigned Numbers Authority (IANA) Policy for Allocation of IPv6 Blocks to Regional Internet Registries Author: AfriNIC APNIC ARIN LACNIC RIPE NCC Date: 19 April 2006 Format: PDF=10551 TXT=4280 Obsoletes: Obsoleted by: Updates: Updated by: Short content description ------------------------- This document describes the policy governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with this policy. Such requirements will be specified by appropriate agreements between ICANN and the NRO. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website at the following URL: http://www.ripe.net/ripe/docs/ripe-376.html The RIPE Document Store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-376.pdf PDF version ftp://ftp.ripe.net/ripe/docs/ripe-376.txt plain text version Kind Regards, Jeroen Bet RIPE NCC Content Webmaster

1 0

2006-01 New Policy Proposal - PI IPv6 Assignments for End User Organisations
by RIPE NCC Policy Coordinator 20 Apr '06

20 Apr '06

PDP Number: 2006-01 Provider Independent (PI) IPv6 Assignments for End User Organisations Dear Colleagues A new RIPE Policy has been proposed and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-01.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 18 May 2006. After this date, we will prepare a draft RIPE Document. We will let you know when this is available. Regards Adrian Bedford RIPE NCC

1 0

HD-ratio Proposal - Review Period Date Correction
by RIPE NCC Policy Coordinator 19 Apr '06

19 Apr '06

PDP Number: 2005-01 HD-ratio Proposal Dear Colleagues The Review Period for RIPE policy proposal 2005-01 has been extended until 17 May 2006. Please ignore the previous mail that gave a date of 10 May 2006. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2005-1.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards Adrian Bedford RIPE NCC

1 0

Proposal Accepted - IANA Policy for Allocation of IPv6 Blocks to RIRs
by RIPE NCC Policy Coordinator 19 Apr '06

19 Apr '06

RIPE PDP Number: 2005-09 Internet Assigned Numbers Authority (IANA) Policy for Allocation of IPv6 Blocks to Regional Internet Registries Dear Colleagues Consensus has been reached, and the proposal described in 2005-09 has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2005-09.html Thank you for your input. Regards Adrian Bedford RIPE NCC

1 0

2005-01 Review Period Extended Until 10 May 2006 (HD-ratio Proposal)
by RIPE NCC Policy Coordinator 19 Apr '06

19 Apr '06

PDP Number: 2005-01 HD-ratio Proposal Dear Colleagues The Review Period for the change to RIPE Document ripe-368 described in proposal 2005-01 has been extended until 10 May 2006 You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2005-1.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards Adrian Bedford RIPE NCC

1 0

Re: [ppml] PI addressing in IPv6 advances in ARIN
by JORDI PALET MARTINEZ 18 Apr '06

18 Apr '06

Hi all, My first idea was submitting a PI IPv6 policy proposal next Monday to RIPE and the rest of the regions, trying to get a consensus for a "global" policy on this, but as this thread is being followed up in several mail exploders, to avoid a long cross-posting, I think it will be better to start some discussion already in a mailing list which is global, and actually I think we have the right one ... global-v6(a)lists.apnic.net So, if you aren't subscribed in the global-v6(a)lists.apnic.net, and you're interested in this thread, please subscribe at http://mailman.apnic.net/mailman/listinfo/global-v6 If you're late because the Eastern, the archives are also available at http://www.apnic.net/mailing-lists/global-v6/ Regards, Jordi > De: JORDI PALET MARTINEZ <jordi.palet(a)consulintel.es> > Responder a: <jordi.palet(a)consulintel.es> > Fecha: Fri, 14 Apr 2006 13:39:07 +0200 > Para: "v6ops(a)ops.ietf.org" <v6ops(a)ops.ietf.org>, "ppml(a)arin.net" > <ppml(a)arin.net>, "shim6(a)psg.com" <shim6(a)psg.com> > Conversación: [ppml] PI addressing in IPv6 advances in ARIN > Asunto: Re: [ppml] PI addressing in IPv6 advances in ARIN > > Hi Owen, > > You said it: If somebody find the good solution, it will be attractive to > the people to go for it. Otherwise, you always have the chance to become an > LIR. My proposal actually is already considering this point and a way to > avoid a need for renumbering if that happens. > > I just want to make sure that we have a way-out if it becomes necessary, but > avoid a showstopper now. I think is it possible. > > I don't have a technical solution yet (and agree with your views on this in > the email below in general), but I'm confident we will have. If it will take > 4 years from now, or just 2, who knows, so my proposal is ensuring that we > have those 4 years+3 for allowing the people either to return the block, or > become an LIR and avoid renumbering an any changes in their network. > > By the way, it may happen, and I'm hoping so, that the technical solution > don't make necessary to return the PI block anymore, and in that case, we > will be even able to remove at that time the "temporarily" point in the > policy (if it becomes accepted). > > Regards, > Jordi > > > > >> De: Owen DeLong <owen(a)delong.com> >> Responder a: <owen(a)delong.com> >> Fecha: Fri, 14 Apr 2006 03:48:34 -0700 >> Para: <jordi.palet(a)consulintel.es>, "v6ops(a)ops.ietf.org" >> <v6ops(a)ops.ietf.org>, >> "ppml(a)arin.net" <ppml(a)arin.net>, "shim6(a)psg.com" <shim6(a)psg.com> >> Asunto: Re: [ppml] PI addressing in IPv6 advances in ARIN >> >> >> >> --On April 14, 2006 12:20:06 PM +0200 JORDI PALET MARTINEZ >> <jordi.palet(a)consulintel.es> wrote: >> >> [snip] >>> However, I want to balance this with the medium-long term implications >>> created in the routing table and with the time needed to build and deploy >>> a better technical solution (or several) which is accepted by the >>> community. >>> >> I think we first need to define what we consider a solution... See below. >> >>> So my proposal basically is about having PI now everywhere (once ARIN >>> adopt it, is unfair not having it in other regions), but those PI >>> allocations for multihoming should be temporary and those address blocks >>> returned to the RIRs some time (lets say 3 years) after the new technical >>> solution is declared as a valid one. >>> >> I would not actually support this idea. The whole point of having PI >> space is to have the addresses for a long-term. Having a timeframe for >> return would simply restore the same barrier to entry that existed >> prior to passing the policy. >> >> Other RIRs are free to implement whatever v6 PI policy they feel is >> appropriate for their region. I would support a globally standardized >> v6 PI policy along the lines of ARIN 2005-1. >> >> However, I would like to argue that if the new technical solution will >> benefit from the return of this address space, it is most likely not >> truly a solution, but, instead, another clever hack piled on top of >> the existing set of hacks. >> >> I suppose if someone found the magic bullet to make geotopological >> addressing really work, that might qualify. However, I have very low >> expectations in that area. >> >> Absent that, any true solution will involve making the size of the routing >> table independent of the number of PI (or even PA) blocks issued by >> the RIRs or will make the size of the routing table practically >> irrelevant. >> >> I know this isn't the easy solution, but, we need to look long and >> hard at the way we do things. I think that solving these problems >> is going to require a significant paradigm shift. Assuming that we >> can use IP addresses for both end system identification and for >> routing topology indicators is how we created this problem. I don't >> see solving it without breaking that assumption, at least at the >> interdomain level. >> >> >>> At this way, on the long-run, we will not have routing table implications, >>> but we allow now the people that want to move ahead only if they have a >>> multihoming solution doing so. >>> >> If you think there is a possible solution (a real solution, not just >> a hack that postpones the inevitable at the expense of usability >> like CIDR did), then I'd like to hear what you are thinking. >> >>> This 3-years time for getting a multihoming network back to the new >>> technical solution (once adopted) is enough time, I think (it could be >>> changed to 5 years if needed, or whatever), so nobody today see the >>> temporarily of the proposal as a showstopper to go for it now. >>> >> I think you underestimate the momentum and requirements of the modern >> enterprise if you believe that to be true. Any capability available >> in v4 that is not available on at least equal or better terms in v6 >> is a deterrent to v6 deployment. >> >> The ability to get permanent addresses which do not have to be returned >> when you switch providers or renumbered on a schedule determined by >> some external organization is a major example of such a capability. >> >> Owen >> >> >> -- >> If it wasn't crypto-signed, it probably didn't come from me. > > > > > ********************************************** > The IPv6 Portal: http://www.ipv6tf.org > > Barcelona 2005 Global IPv6 Summit > Slides available at: > http://www.ipv6-es.com > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the use of the > individual(s) named above. If you are not the intended recipient be aware that > any disclosure, copying, distribution or use of the contents of this > information, including attached files, is prohibited. > > > > > > > ********************************************** > The IPv6 Portal: http://www.ipv6tf.org > > Barcelona 2005 Global IPv6 Summit > Slides available at: > http://www.ipv6-es.com > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the use of the > individual(s) named above. If you are not the intended recipient be aware that > any disclosure, copying, distribution or use of the contents of this > information, including attached files, is prohibited. > > ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

Re: [address-policy-wg] Global IPv6 PI policy proposal
by JORDI PALET MARTINEZ 18 Apr '06

18 Apr '06

Hi Michael, I know is difficult to achieve, but I think is worth to try and at least try to make it as much close as possible if no way to make a single one. I'm in favor of the RIRs process but also in favor of trying to achieve global consensus, avoiding regional shopping, etc. In fact not trying to make it as much global and fair to all as possible, we could say otherwise that there is no reason to set policy by regions, but by country, or estate, etc., which I'm sure you don't agree. We need to understand the very high importance of the PI implications on a global level, which make a good candidate for a global policy, in my opinion. Regards, Jordi > De: <Michael.Dillon(a)btradianz.com> > Responder a: <Michael.Dillon(a)btradianz.com> > Fecha: Tue, 18 Apr 2006 13:09:26 +0100 > Para: <jordi.palet(a)consulintel.es> > CC: "address-policy-wg-admin(a)ripe.net" <address-policy-wg-admin(a)ripe.net>, > "global-v6(a)lists.apnic.net" <global-v6(a)lists.apnic.net> > Asunto: Re: [address-policy-wg] Global IPv6 PI policy proposal > >> Please, use global-v6(a)lists.apnic.net for inputs to this draft policy >> proposal, in order to avoid threads being split across multiple mail >> exploders in different regions. > > I strongly doubt that you will get anywhere with a global > policy proposal. There is a reason that RIRs set their > policies independently. The IPv6 policy was a special case > due to the need to create a new policy for a new type of > address. But from now on, the 5 RIRs are likely to continue > making local changes to policies and it is extremenly unlikely > for any global policy to survive the 5 RIRs intact. > > In fact, the concept of a global policy is in direct > contradiction with the bottom-up nature of the RIRs. > > --Michael Dillon > > ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

IPv6 workshop in Istanbul
by JORDI PALET MARTINEZ 18 Apr '06

18 Apr '06

Hi all, Sponsored by ISOC, there will be an IPv6 workshop next Friday 28th afternoon in Istanbul, right after the RIPE lunch. The workshop is intended for those that don't have IPv6 knowledge. More information and registration: http://www.ipv6tf.org/ipv6_istanbul_isoc.php Please, forward this to your colleagues and other people that may be interested in participating. Thanks ! Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

RE: [narten@us.ibm.com: PI addressing in IPv6 advances in ARIN]
by Bound, Jim 17 Apr '06

17 Apr '06

The IETF has NOTHING to say anymore than any other body about any RIR policy. I want it to remain that way. IETF job is a standards body not a deployment body. /jim > -----Original Message----- > From: owner-shim6(a)psg.com [mailto:owner-shim6@psg.com] On > Behalf Of Iljitsch van Beijnum > Sent: Sunday, April 16, 2006 3:18 AM > To: Patrick W. Gilmore > Cc: shim6-wg; ppml(a)arin.net; global-v6(a)lists.apnic.net; IETF > Discussion; address-policy-wg(a)ripe.net; v6ops(a)ops.ietf.org > Subject: Re: [narten(a)us.ibm.com: PI addressing in IPv6 > advances in ARIN] > > On 16-apr-2006, at 6:09, Patrick W. Gilmore wrote: > > > Wow, Iljitsch, I have never lost so much respect so quickly for > > someone who was not flaming a specific person or using profanity. > > Congratulations. > > Well, that's too bad. But several years of trying to get a > scalable multihoming off the ground (flying to different > meetings on my own > dime) where first my ideas about PI aggregation are rejected > within the IETF mostly without due consideration because it > involves the taboo word "geography" only to see the next best > thing being rejected by people who, as far as I can tell, > lack a view of the big picture, is enough to make me lose my > cool. Just a little. > > > Back on topic, it is not just those 60 people - the "playground" > > appears to overwhelmingly agree with their position. I know I do. > > Don't you think it's strange that the views within ARIN are > so radically different than those within the IETF? Sure, > inside the IETF there are also people who think PI in IPv6 > won't be a problem, but it's not the majority (as far as I > can tell) and certainly not anything close to 90%. Now the > IETF process isn't perfect, as many things depend on whether > people feel like actually doing something. > But many of the best and the brightest in the IETF have been > around for some time in multi6 and really looked at the > problem. Many, if not most, of them concluded that we need > something better than IPv4 practices to make IPv6 last as > long as we need it to last. Do you think all of them were wrong? > > > I am sorry your technical arguments have not persuaded us > in the past. > > But I would urge you to stick to those, > > Stay tuned. > >

3 2

RE: [narten@us.ibm.com: PI addressing in IPv6 advances in ARIN]
by Bound, Jim 17 Apr '06

17 Apr '06

I agree. /jim > -----Original Message----- > From: owner-shim6(a)psg.com [mailto:owner-shim6@psg.com] On > Behalf Of Patrick W. Gilmore > Sent: Sunday, April 16, 2006 12:10 AM > To: Iljitsch van Beijnum > Cc: Patrick W. Gilmore; shim6-wg; ppml(a)arin.net; > global-v6(a)lists.apnic.net; IETF Discussion; > address-policy-wg(a)ripe.net; v6ops(a)ops.ietf.org > Subject: Re: [narten(a)us.ibm.com: PI addressing in IPv6 > advances in ARIN] > > On Apr 14, 2006, at 11:07 AM, Iljitsch van Beijnum wrote: > > > On 14-apr-2006, at 16:57, Scott Leibrand wrote: > > > >> 60 voted in favor of moving forward with PI. 6 voted against. > > > > Wow, 10 to 1. Amazing. > > > > Even more amazing: 60 people who represent nobody but their own > > paycheck get to blow up the internet. > > > > Where is ICANN when you need it? This little experiment in > playground > > democracy has to end before people get hurt. > > Wow, Iljitsch, I have never lost so much respect so quickly for > someone who was not flaming a specific person or using profanity. > Congratulations. > > > Back on topic, it is not just those 60 people - the "playground" > appears to overwhelmingly agree with their position. I know I do. > > I am sorry your technical arguments have not persuaded us in > the past. But I would urge you to stick to those, or at > least consider why we remain unconvinced, rather than devolve > into .. whatever that post was supposed to be. > > -- > TTFN, > patrick > >

1 0

Re: [narten@us.ibm.com: PI addressing in IPv6 advances in ARIN]
by Iljitsch van Beijnum 16 Apr '06

16 Apr '06

On 14-apr-2006, at 16:57, Scott Leibrand wrote: > 60 voted in favor of moving forward with PI. 6 voted against. Wow, 10 to 1. Amazing. Even more amazing: 60 people who represent nobody but their own paycheck get to blow up the internet. Where is ICANN when you need it? This little experiment in playground democracy has to end before people get hurt.

6 7

DRAFT agenda for RIPE 52 address policy WG meeting
by Gert Doering 16 Apr '06

16 Apr '06

Hi APWG folks, here's a first draft of an agenda for the RIPE52 address policy meeting in Istanbul in two weeks. Please send me your comments pretty quickly, as we need to hand in the agenda for printing next Tuesday. Gert Doering -- NetMaster --------------------------- snip ------------------------- A. Administrative Matters - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 51: http://www.ripe.net/ripe/wg/address-policy/r51-minutes.html <has this already been circulated for comments?> B. Policy proposal overview (of address policy WG proposals) - Filiz Yilmaz - 2005-02 IP assignments for anycast DNS (OPEN) - 2005-03 IPv6 initial allocation criteria (Discussion) - 2005-08 Amend IPv6 assignment and utilization requirements (Open) - 2005-12 4-byte AS number policy (Open) - 2005-01 HD-Ratio proposal (concluding) - 2005-09 IPv6 IANA->RIR distribution policy (consensus) C. discussion on existing proposals that are not yet closed D. necessary steps to conclude 2005-09 E. ongoing policy work in other regions * presentation in the plenary * plus discussion time in the WG slot F. IPv6 PI policy - ongoing work in other regions * presentation about the ARIN IPv6 PI policy in the plenary (http://www.arin.net/policy/proposals/2005_1.html= * plus discussion time in the WG slot (Jordi Palet) Z. AOB -- Total number of prefixes smaller than registry allocations: 88685 SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234

1 0

Global IPv6 PI policy proposal
by JORDI PALET MARTINEZ 14 Apr '06

14 Apr '06

Please, use global-v6(a)lists.apnic.net for inputs to this draft policy proposal, in order to avoid threads being split across multiple mail exploders in different regions. 1. Number: (The RIPE NCC will assign this) 2. Policy Proposal Name: Provider-Independent (PI) IPv6 Assignments for End-User-Organizations Note: We can use ³Portable IPv6 Assignments for End-User-Organizations² if that helps some folks to buy-in the proposal. 3. Author: a. name: Jordi Palet Martinez b. e-mail: jordi.palet(a)consulintel.es c. organisation: Consulintel 4. Proposal Version: 1.1 5. Submission Date: 17/4/2006 6. Suggested RIPE Working Group for discussion and publication: Address Policy 7. Proposal type: a. new, modify, or delete. NEW 8. Policy term: a. temporary, permanent, or renewable. TEMPORARY 9. Summary of proposal: This policy is intended to provide a solution for organizations that have a need for provider independent assignments in IPv6. Typically those organizations will require the provider independent assignment in order to be able to become multihomed in a similar fashion as today is done for IPv4, but other reasons are also foreseen. For example some organizations aren¹t multihomed, but still require being globally routable with stable addressing (avoiding renumbering if they change the upstream provider) and in those cases (reasons behind may be administrative, policy, security, etc.) it seems that no other solution than provider independence is feasible, at least by now. Considering the foreseen consequences in the medium/long-term of this policy in the routing tables, this policy proposes an expiry date of 3 years once a technically correct alternative valid and deployable solution becomes accepted by the community. After that sunset period, the assignments done for multihoming purposes should be reclaimed and this policy should be modified to still allow assignments that could be required for purposes different than multhoming. At the sunset, the organizations that want to avoid renumbering and qualify to become an LIR, will be able to opt for that solution and they will get allocated the same prefix. 10. Policy text: a. Current (if modify): b. New: Provider-Independent IPv6 assignment to End-User-Organizations Qualification for an IPv6 Provider-Independent assignment: To qualify for a direct assignment, the organization must not be an IPv6 LIR and must qualify for an IPv4 assignment or allocation from RIPE NCC under the actual IPv4 policy. This is valid regardless of actually having being assigned or allocated such an IPv4 block. Provider-Independent IPv6 assignment size to End-User-Organizations: The minimum size of the assignment is /32. However a larger assignment can be provided if duly documented and justified. Subsequent assignment size to End-User-Organizations: Whenever possible, further assignments will be made from adjacent address blocks, but only if duly documented and justified. Assignment super-block: Those assignments shall be allocated from a separate super-block to allow for LIRs to filter them if required. Expiry for those assignments: In the case of assignments done under this proposal in order to address the multihoming issue, they will need to return the block in a maximum period of 3 years after a technically correct alternative valid and deployable solution becomes accepted by the community. Alternatively, to avoid renumbering, some of the organizations affected by this, could become an LIR, if they qualify for it. 11. Rationale: a. Arguments supporting the proposal In IPv4 there are organizations that qualify for an allocation for being PI, or could opt to be an LIR, either because they need to be multihomed or have other administrative or technical reasons to require a portable addressing block. This is not the case today for IPv6 and it is perceived as a clear barrier for deployment of IPv6 in some organizations, and is being addressed by this proposal by means of providing a direct assignment from RIPE NCC. These organizations are not allowed to make further assignments to other external organizations, but instead only to assign subnets internally within their own facilities. Assigning /32 will make those blocks to behave as other regular LIR-allocated ones and follow the generally accepted routing filtering practices, but at the same time being identifiable belonging to a special super-block. Also, it allows becoming an LIR, if that¹s the case, without requiring a renumbering. By setting up this policy, we avoid creating an unfairness situation among different regions and allow any organization that requires PI to access to it. All the organizations that opt for this PI, will be in the same fair situation once the technical solution is agreed and will have to either move to the new solution or become an LIR if they qualify. Newcomers will be in the same situation. Organizations that don¹t opt to PI with this policy is because they don¹t need it, so they aren¹t put in an unfair situation. Those that don¹t believe in possible alternative solutions and agree in going for a permanent PI policy instead, don¹t have valid reasons to oppose to this proposal, as the sunset will only enter into effect once that solution is agreed, so this proposal is not against their view. Some organizations my qualify to become an LIR now and avoid using this temporary assignment, but if their only reason to become an LIR is to get the PI block, then it seems better, looking in the long-term routing table size conservation, to go for this choice, which is more fair for the overall community. The ³temporarily² of this assignment must be understood as a long-term one, as we may expect those alternative solutions to be available possible in 3-4 years, which means that with the ³transition² period of 3 years, asking for a change in 6-7 years must not be considered as a pain. b. Arguments opposing the proposal The possible effect of this proposal is the grow of the routing tables to figures which, together with the existing (and forecasted) IPv4 routing entries, could create an important trouble to operators before vendors provide products with implement technical solutions, or even if those technical solutions exists, have an important impact in the cost or/and depreciation period for the infrastructure investments. This is the reason why the proposal provides already a fix sunset, but relative to the date where an alternative and technically correct solution is available and accepted as deployable by the community. Regarding the size of the assignment (/32), being a temporal one, should not be considered as a space waste, and instead be seen as an advantage in the sense of not requiring new special filters. Acknowledgments: I will like to acknowledge the inputs received for the first version of this proposal from Marcelo Bagnulo and Lea Roberts. ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

RE: [address-policy-wg] RE: Question
by Bound, Jim 14 Apr '06

14 Apr '06

Ray, Thanks for the response. IPv6 Forum does not have an organizational opinion at this time, we have evolved to a technical in depth body and try to avoid such positions unless it interferes with IPv6 deployment. I will take your response as an indirect NO the IETF does not have input to RIRs as a body either. My assumption, which I did not state previously, that the IETF is given any special treatment regarding your policy, was an invalid assumption on my part. So thanks for clearing that up. We have taken this discussion offline to persons who want to continue the analysis discussion. Thank You, /jim > -----Original Message----- > From: Ray Plzak [mailto:plzak@arin.net] > Sent: Thursday, April 13, 2006 8:46 AM > To: Bound, Jim; 'Latif Ladid ("The New Internet based on > IPv6")'; 'Tony Hain'; 'PPML'; address-policy-wg(a)ripe.net > Cc: 'Richard Jimmerson'; 'Davis, Terry L'; > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; 'Brig, > Michael P CIV DISA GES-E'; Pouffary, Yanick; 'Green, David B > RDECOM CERDEC STCD SRI' > Subject: RE: [address-policy-wg] RE: Question > > Jim, > > Regarding direction, ARIN staff implements policies that have > reached community consensus as determined by the ARIN > Advisory Council and as ratified by the Board of Trustees. In > one sense, ARIN works like the IETF in that it is individuals > who contribute to the discussion. An organization is one > voice and is not viewed as representative of its members from > the standpoint of numbers. You are correct. This does not > preclude someone representative of the IPv6 Forum from making > a statement on either the ppml or at a meeting on behalf of > the Forum. One last point, if the Forum feels that the > community is developing policy that is harmful then the Forum > should certainly make a statement, more importantly, its > individual members should become active voices in the > discussion. There are a lot of voices in the IPv6 discussions > but the discussion could be much more robust if those of the > Forum were included. > > Ray > > > -----Original Message----- > > From: Bound, Jim [mailto:Jim.Bound@hp.com] > > Sent: Tuesday, April 11, 2006 9:30 AM > > To: Ray Plzak; Latif Ladid ("The New Internet based on IPv6"); Tony > > Hain; PPML; address-policy-wg(a)ripe.net > > Cc: Richard Jimmerson; Davis, Terry L; > ollivier.robert(a)eurocontrol.fr; > > narten(a)us.ibm.com; Brig, Michael P CIV DISA GES-E; > Pouffary, Yanick; > > Green, David B RDECOM CERDEC STCD SRI; Bound, Jim > > Subject: RE: [address-policy-wg] RE: Question > > > > Ray, So you don't take IETF direction but only from > individuals in the > > IETF? Just want this to be clarified very clearly. This also does > > not preclude the IPv6 Forum stating a public position on the issue > > whether RIRs react to it or not. Not that will happen but > it could if > > the pain is strong enough to prohibit IPv6 deployment. > > > > Thanks > > /jim > > > > > -----Original Message----- > > > From: Ray Plzak [mailto:plzak@arin.net] > > > Sent: Monday, April 10, 2006 6:56 AM > > > To: 'Latif Ladid ("The New Internet based on IPv6")'; Bound, Jim; > > > 'Tony Hain'; 'PPML'; address-policy-wg(a)ripe.net > > > Cc: 'Richard Jimmerson'; 'Davis, Terry L'; > > > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; 'Brig, > Michael P > > > CIV DISA GES-E'; Pouffary, Yanick; 'Green, David B RDECOM CERDEC > > > STCD SRI' > > > Subject: RE: [address-policy-wg] RE: Question > > > > > > The NAv6TF is in the ARIN region. If individuals > associated with it > > > think that ARIN should adopt a policy or change an > existing policy > > > they should not only say so they should propose such a policy. > > > Remember policies in the ARIN region, like in all of the RIRs is > > > made not by the RIR organization staff and board but by the > > > community in the region. ARIN staff will be more than > happy to help > > > anyone through the process, which by the way, while an > orderly and > > > formal process is not onerous, but one designed to provide for an > > > open and honest discussion of any policy proposal before it is > > > adopted. If you are interested in pursuing this, please > contact me > > > and I will get a staff member to assist you. > > > > > > Ray > > > > > > > -----Original Message----- > > > > From: address-policy-wg-admin(a)ripe.net > [mailto:address-policy-wg- > > > > admin(a)ripe.net] On Behalf Of Latif Ladid ("The New > Internet based > > > > on > > > > IPv6") > > > > Sent: Saturday, April 08, 2006 9:53 AM > > > > To: 'Bound, Jim'; 'Tony Hain'; 'PPML'; > address-policy-wg(a)ripe.net > > > > Cc: 'Richard Jimmerson'; 'Davis, Terry L'; > > > > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; > 'Brig, Michael > > > > P CIV DISA GES-E'; 'Pouffary, Yanick'; 'Green, David B RDECOM > > > CERDEC STCD SRI' > > > > Subject: [address-policy-wg] RE: Question > > > > > > > > > > > > > > > > The technical community should fix this one before the ITU > > > sees this > > > > as another chance to have a political say on the IPv6 > addressing. > > > > These things leak fast. My advice is that ARIN should seriously > > > > own this issue before the ITU turns it to a sovereignty issue, > > > which they > > > > could for sure win this time. I know one of their noodles > > > is sizzling > > > > at it. > > > > > > > > Cheers > > > > Latif > > > > > > > > -----Original Message----- > > > > From: Bound, Jim [mailto:Jim.Bound@hp.com] > > > > Sent: 08 April 2006 14:52 > > > > To: Tony Hain; PPML; address-policy-wg(a)ripe.net > > > > Cc: Richard Jimmerson; Latif Ladid ("The New Internet based > > > on IPv6"); > > > > Davis, Terry L; ollivier.robert(a)eurocontrol.fr; > narten(a)us.ibm.com; > > > > Brig, Michael P CIV DISA GES-E; Pouffary, Yanick; > Green, David B > > > > RDECOM CERDEC STCD SRI; Bound, Jim > > > > Subject: RE: Question > > > > > > > > Tony, > > > > > > > > Excellent response and educational for sure. It is my > > > belief that the > > > > corporate business model today for operating networks may be > > > > broken and I think you supported that below? If not my > apologies > > > for bad parsing? > > > > > > > > > > > > Their models were fine for an IPv4 world where NAT was required > > > > and some even confuse NAT with securing ones network (and some > > > programs in the U.S. > > > > Government) and that is simply bad policy and view. > > > > > > > > In the interim can this be resolved by RIRs creating > some kind of > > > > additional wording that address reclaim will be done in > > > manner that is > > > > negotiable, and do no harm to corporate or government business > > > > operations? This would buy us time to work on the issue > > > and stop the > > > > FUD around this topic? > > > > > > > > Also I am willing to sponsor a world wide IPv6 Forum > BOF on PI and > > > > addressing you can lead as ajunct to one of our regular > > > meetings you > > > > can lead for an entire day and we get the right players in > > > the room. > > > > So think about that as another option too. > > > > > > > > But do enjoy the beach this thread does not have to be > > > resolved this > > > > week > > > > :--) > > > > > > > > Really want to hear from all of you and discussion Terry D., > > > > Latif, Yanick, Dave G. Mike B. etc. > > > > > > > > Thanks > > > > /jim > > > > > > > > > -----Original Message----- > > > > > From: Tony Hain [mailto:alh-ietf@tndh.net] > > > > > Sent: Friday, April 07, 2006 7:57 PM > > > > > To: 'PPML'; address-policy-wg(a)ripe.net > > > > > Cc: 'Richard Jimmerson'; Bound, Jim; 'Latif Ladid ("The > > > New Internet > > > > > based on IPv6")'; 'Davis, Terry L'; > > > ollivier.robert(a)eurocontrol.fr; > > > > > narten(a)us.ibm.com; 'Brig, Michael P CIV DISA GES-E'; > Pouffary, > > > > > Yanick; 'Green, David B RDECOM CERDEC STCD SRI' > > > > > Subject: RE: Question > > > > > > > > > > A public answer to a private question as I have been > sitting on > > > > > a beach for awhile without the laptop and missed some related > > > > > conversations ... :) > > > > > > > > > > > Is the outcome really open for discussion on the PI issue? > > > > > It doesn't > > > > > > sound like it is. > > > > > > > > > > In the minds of some the route scaling issue outweighs > > > any argument > > > > > for PI. > > > > > When taken to its extreme, there is a valid point > that a broken > > > > > routing system serves no one. At the same time the > > > dogmatic stance > > > > > by the ISPs enforcing lock-in is just as broken both > for large > > > > > organizations with financial or legal requirements for > > > operational > > > > > stability, and the individual consumer/small business > > > with limited > > > > > budgets looking for true competition. The hard part is > > > finding the > > > > > middle ground in a way that limits the exposure to a > potential > > > > > routing collapse. > > > > > > > > > > I personally refuse to declare some needs legitimate and > > > others not, > > > > > as the only point of such differentiation is to establish a > > > > > power broker. When all uses are legitimate, the problem boils > > > down to the > > > > > technical approach that can be scaled as necessary to > > > contain growth > > > > > in the routing system. > > > > > This is the logic that leads me to the bit-interleaved > > > geo that can > > > > > be aggregated in varying size pockets as necessary using > > > > > existing BGP deployments. We can start flat and implement > > > > > aggregation over time when a region becomes too large > to handle. > > > > > One nice > > > side effect > > > > > of this geo approach is that it mitigates the continuing > > > political > > > > > demands for sovereign rights to IPv6 space. > > > > > > > > > > Any aggregation approach will force the business models to > > > > > change from current practice. That is not as bad a > thing as the > > > alarmists > > > > > will make it out to be, because their accountants are > > > claiming the > > > > > current model is a broken money looser as it is (which if > > > so means > > > > > they will eventually change anyway). The primary > > > difference is that > > > > > there will need to be aggregation intermediaries between the > > > > > last-mile and transit providers. The current model > > > eliminates these > > > > > middle-men by trading off their routing mitigation > > > service against a > > > > > larger routing table (actually they already exist in > the right > > > > > places but are currently limited to layer2 media > > > aggregators). The > > > > > anti-PI bunch is trying to use social engineering to directly > > > > > counter the bottom line business reality that the > > > customer will always win in the end. > > > > > Rather than accept this situation and constructively > work on the > > > > > necessary business model and technology developments, they > > > > > effectively stall progress by staunchly claiming there is no > > > > > acceptable technical approach that works within the > > > current business structure. > > > > > > > > > > Making the RIRs be the police deciding who qualifies for > > > PI and who > > > > > does not just adds to their workload and raises costs. The > > > > > beneficiaries of this gatekeeper approach are the ISPs that > > > > > claim they need full routing knowledge everywhere, while the > > > cost burden > > > > > for supporting the waste-of-time > qualification/evaluation work > > > > > is borne by the applicant. > > > > > Given that the most vocal and organized membership in the RIR > > > > > community are the ISPs it is easy to understand why it would > > > > > seem like the PI issue is already decided as closed. I tend to > > > believe it > > > > > will just drag out until enough of the corporate world > > > becomes aware > > > > > of the > > > > > IPv4 exhaustion in light of their growth needs that they > > > > > collectively appear at their RIR and demand an immediate > > > solution. > > > > > Unfortunately this 'wait till the last minute' tactic will > > > > > likely result in a reactionary quickie with its own > set of long > > > term side effects. > > > > > > > > > > A while back I tried to hold a BOF on geo PI in the IETF, but > > > > > was told that > > > > > shim6 was the anointed solution. Now that at least nanog has > > > > > told the IAB where to put shim6 it might be possible to get > > > the current > > > > > IESG to reconsider. In any case the result would be a > technical > > > > > approach that would still require RIRs to establish > > > policies around. > > > > > As long as they are dominated by the ISPs it will be > > > difficult to get real PI. > > > > > > > > > > Tony > > > > > > > > > > > > > > > > > >

1 0

RE: [address-policy-wg] RE: Question
by Bound, Jim 13 Apr '06

13 Apr '06

Ray, So you don't take IETF direction but only from individuals in the IETF? Just want this to be clarified very clearly. This also does not preclude the IPv6 Forum stating a public position on the issue whether RIRs react to it or not. Not that will happen but it could if the pain is strong enough to prohibit IPv6 deployment. Thanks /jim > -----Original Message----- > From: Ray Plzak [mailto:plzak@arin.net] > Sent: Monday, April 10, 2006 6:56 AM > To: 'Latif Ladid ("The New Internet based on IPv6")'; Bound, > Jim; 'Tony Hain'; 'PPML'; address-policy-wg(a)ripe.net > Cc: 'Richard Jimmerson'; 'Davis, Terry L'; > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; 'Brig, > Michael P CIV DISA GES-E'; Pouffary, Yanick; 'Green, David B > RDECOM CERDEC STCD SRI' > Subject: RE: [address-policy-wg] RE: Question > > The NAv6TF is in the ARIN region. If individuals associated > with it think that ARIN should adopt a policy or change an > existing policy they should not only say so they should > propose such a policy. Remember policies in the ARIN region, > like in all of the RIRs is made not by the RIR organization > staff and board but by the community in the region. ARIN > staff will be more than happy to help anyone through the > process, which by the way, while an orderly and formal > process is not onerous, but one designed to provide for an > open and honest discussion of any policy proposal before it > is adopted. If you are interested in pursuing this, please > contact me and I will get a staff member to assist you. > > Ray > > > -----Original Message----- > > From: address-policy-wg-admin(a)ripe.net [mailto:address-policy-wg- > > admin(a)ripe.net] On Behalf Of Latif Ladid ("The New Internet based on > > IPv6") > > Sent: Saturday, April 08, 2006 9:53 AM > > To: 'Bound, Jim'; 'Tony Hain'; 'PPML'; address-policy-wg(a)ripe.net > > Cc: 'Richard Jimmerson'; 'Davis, Terry L'; > > ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; 'Brig, Michael P > > CIV DISA GES-E'; 'Pouffary, Yanick'; 'Green, David B RDECOM > CERDEC STCD SRI' > > Subject: [address-policy-wg] RE: Question > > > > > > > > The technical community should fix this one before the ITU > sees this > > as another chance to have a political say on the IPv6 addressing. > > These things leak fast. My advice is that ARIN should seriously own > > this issue before the ITU turns it to a sovereignty issue, > which they > > could for sure win this time. I know one of their noodles > is sizzling > > at it. > > > > Cheers > > Latif > > > > -----Original Message----- > > From: Bound, Jim [mailto:Jim.Bound@hp.com] > > Sent: 08 April 2006 14:52 > > To: Tony Hain; PPML; address-policy-wg(a)ripe.net > > Cc: Richard Jimmerson; Latif Ladid ("The New Internet based > on IPv6"); > > Davis, Terry L; ollivier.robert(a)eurocontrol.fr; narten(a)us.ibm.com; > > Brig, Michael P CIV DISA GES-E; Pouffary, Yanick; Green, David B > > RDECOM CERDEC STCD SRI; Bound, Jim > > Subject: RE: Question > > > > Tony, > > > > Excellent response and educational for sure. It is my > belief that the > > corporate business model today for operating networks may be broken > > and I think you supported that below? If not my apologies > for bad parsing? > > > > > > Their models were fine for an IPv4 world where NAT was required and > > some even confuse NAT with securing ones network (and some > programs in the U.S. > > Government) and that is simply bad policy and view. > > > > In the interim can this be resolved by RIRs creating some kind of > > additional wording that address reclaim will be done in > manner that is > > negotiable, and do no harm to corporate or government business > > operations? This would buy us time to work on the issue > and stop the > > FUD around this topic? > > > > Also I am willing to sponsor a world wide IPv6 Forum BOF on PI and > > addressing you can lead as ajunct to one of our regular > meetings you > > can lead for an entire day and we get the right players in > the room. > > So think about that as another option too. > > > > But do enjoy the beach this thread does not have to be > resolved this > > week > > :--) > > > > Really want to hear from all of you and discussion Terry D., Latif, > > Yanick, Dave G. Mike B. etc. > > > > Thanks > > /jim > > > > > -----Original Message----- > > > From: Tony Hain [mailto:alh-ietf@tndh.net] > > > Sent: Friday, April 07, 2006 7:57 PM > > > To: 'PPML'; address-policy-wg(a)ripe.net > > > Cc: 'Richard Jimmerson'; Bound, Jim; 'Latif Ladid ("The > New Internet > > > based on IPv6")'; 'Davis, Terry L'; > ollivier.robert(a)eurocontrol.fr; > > > narten(a)us.ibm.com; 'Brig, Michael P CIV DISA GES-E'; Pouffary, > > > Yanick; 'Green, David B RDECOM CERDEC STCD SRI' > > > Subject: RE: Question > > > > > > A public answer to a private question as I have been sitting on a > > > beach for awhile without the laptop and missed some related > > > conversations ... :) > > > > > > > Is the outcome really open for discussion on the PI issue? > > > It doesn't > > > > sound like it is. > > > > > > In the minds of some the route scaling issue outweighs > any argument > > > for PI. > > > When taken to its extreme, there is a valid point that a broken > > > routing system serves no one. At the same time the > dogmatic stance > > > by the ISPs enforcing lock-in is just as broken both for large > > > organizations with financial or legal requirements for > operational > > > stability, and the individual consumer/small business > with limited > > > budgets looking for true competition. The hard part is > finding the > > > middle ground in a way that limits the exposure to a potential > > > routing collapse. > > > > > > I personally refuse to declare some needs legitimate and > others not, > > > as the only point of such differentiation is to establish a power > > > broker. When all uses are legitimate, the problem boils > down to the > > > technical approach that can be scaled as necessary to > contain growth > > > in the routing system. > > > This is the logic that leads me to the bit-interleaved > geo that can > > > be aggregated in varying size pockets as necessary using existing > > > BGP deployments. We can start flat and implement aggregation over > > > time when a region becomes too large to handle. One nice > side effect > > > of this geo approach is that it mitigates the continuing > political > > > demands for sovereign rights to IPv6 space. > > > > > > Any aggregation approach will force the business models to change > > > from current practice. That is not as bad a thing as the > alarmists > > > will make it out to be, because their accountants are > claiming the > > > current model is a broken money looser as it is (which if > so means > > > they will eventually change anyway). The primary > difference is that > > > there will need to be aggregation intermediaries between the > > > last-mile and transit providers. The current model > eliminates these > > > middle-men by trading off their routing mitigation > service against a > > > larger routing table (actually they already exist in the right > > > places but are currently limited to layer2 media > aggregators). The > > > anti-PI bunch is trying to use social engineering to directly > > > counter the bottom line business reality that the > customer will always win in the end. > > > Rather than accept this situation and constructively work on the > > > necessary business model and technology developments, they > > > effectively stall progress by staunchly claiming there is no > > > acceptable technical approach that works within the > current business structure. > > > > > > Making the RIRs be the police deciding who qualifies for > PI and who > > > does not just adds to their workload and raises costs. The > > > beneficiaries of this gatekeeper approach are the ISPs that claim > > > they need full routing knowledge everywhere, while the > cost burden > > > for supporting the waste-of-time qualification/evaluation work is > > > borne by the applicant. > > > Given that the most vocal and organized membership in the RIR > > > community are the ISPs it is easy to understand why it would seem > > > like the PI issue is already decided as closed. I tend to > believe it > > > will just drag out until enough of the corporate world > becomes aware > > > of the > > > IPv4 exhaustion in light of their growth needs that they > > > collectively appear at their RIR and demand an immediate > solution. > > > Unfortunately this 'wait till the last minute' tactic will likely > > > result in a reactionary quickie with its own set of long > term side effects. > > > > > > A while back I tried to hold a BOF on geo PI in the IETF, but was > > > told that > > > shim6 was the anointed solution. Now that at least nanog has told > > > the IAB where to put shim6 it might be possible to get > the current > > > IESG to reconsider. In any case the result would be a technical > > > approach that would still require RIRs to establish > policies around. > > > As long as they are dominated by the ISPs it will be > difficult to get real PI. > > > > > > Tony > > > > > > > >

3 2

Re: Question - Aviation
by Thomas Narten 12 Apr '06

12 Apr '06

"Davis, Terry L" <terry.l.davis(a)boeing.com> writes: > PSS: Back to "critical infrastructure" networks a moment, I'd say that > any network that wanted to declare itself "critical infrastructure" > could obtain PI space, Note: in my mind "PI" space is closely associated with the notion of "being routed within the DFZ of the public internet". > BUT to me this type of network should always be run as a "closed > network" with exchanges to the Internet only through "mediation > gateways" operating at the application level, not at the routing > level. So, this type of network isn't connected directly to the internet and is thus not really part of the public internet (which makes sense to me). Thus, it is unclear to me that PI space is really needed for this. Seems to me, that all you really need is globally unique, unrouted (on the public internet) space. Would RFC 4193 "unique local addresses" satisify the need? And if your answer is "they are not unique enough", would centrally assigned ones, ala (expired) draft-ietf-ipv6-ula-central-00.txt meet your needs? (It would be ironic if you answered yes, because the topic of resurrecting this document came up during the discussion of http://www.arin.net/policy/proposals/2006_2.html at Tuesday's ARIN meeting). Thomas

2 1