- address-policy-wg - mailman.ripe.net

Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 09 Jan '04

09 Jan '04

>> Google is a business. If they want fault tolerance then they can >Ah, and VeriSign, or VRS, isn't? Or those DNS providers for ORG, INFO, LA, >AG, ...? Most of those registries have signed a Registry Data Escrow Agreement with ICANN and every day they update a copy of the domain registry data that is held by a 3rd party escrow agent. This is because they are operating a service on behalf of ICANN and if they go bakrupt or if they break their ICANN contract then ICANN can take the escrow copy of the data and get someone else to run the TLD registry. Verisign is a business, but the DNS and whois services that they provide are part of the Internet's infrastructure. There is no alternative place to get authoritative mapping of .com domain names to IP addresses or ownership data for a .com domain. In that sense Verisign has no competitors. >> buy it from Akamai or else build their own global infrastructure. >> If Google disappears, we can get similar service from many of their >> competitors. They aren't part of the infrastructure of the Internet. >But part of the economically critical infrastructure. And it's not the RIR's >job to decide whether they better buy the service or provide it themselves. >Sorry, this part of the discussion is heading absolutely nowhere. You're right, I don't know why you headed in that direction. RIPE is concerned with critical Internet infrastructure and not with critical economic infrastructure. --Michael Dillon

2 1

Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>The policy needs to balance everyones needs Yes. >(among that: "little extra routes in the DFZ"). DFZ (default free zone) = global routing table. If someone can implement a solution by announcing a shorter prefix from an existing netblock then there is nothing that RIPE can do to change the number of routes in the global routing table. >The policy does also need very clear-cut criteria to *decide* whether >something meets the policy or not. Applying technical criteria is easy >(easier, at least) than a fuzzy term like "critical infrastructure" >that mean something different to whoever reads it. Yes. And a good policy would start by defining the fuzzy term so that everyone understands the scope of the term when it is used in the policy. >Commenting on your first example: for the USA, something might very >well be a "critical infrastructure", like the US power grid, and *still* >the rest of the world might not care much if it breaks down... - so >the definition of "criticial infrastructure" is very much localized and >fuzzy. Yes. The word "critical" is a value judgement. Critical Internet Infrastructure is different from Critical National Infrastructure. In the USA they are focusing on infrastructure that is critical to their nation. We should look at infrastructure that is critical to the Internet, both globally and in the RIPE region. --Michael Dillon

2 1

Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Hank Nussbacher 08 Jan '04

08 Jan '04

At 11:01 AM 08-01-04 +0000, Michael.Dillon(a)radianz.com wrote: >People seem to be confused about the meaning of "critical infrastructure" >so I decided to see what Google has to say. The first thing it comes up >with is an American government organization called the Department for >Homeland Security. On their question and answer page they say this: >http://www.ciao.gov/publicaffairs/qsandas.htm > >1.) What is a critical infrastructure? > >The USA Patriot Act defines critical infrastructures as those >"systems and assets, whether physical or virtual, so vital to the >United States that the incapacity or destruction of such systems >and assets would have a debilitating impact on security, national >economic security, national public health or safety, or any >combination of those matters." Why should Europe and the RIPE region care about what the US defines as critical infrastructure? > > Es gibt Luegen, verdammte Luegen und RIPE-141(-219)-Netzantraege. > >Translated: There are lies, damned lies and RIPE-141 request forms. It is RIPE-219. RIPE-141 is dead. >--Michael Dillon -Hank

2 1

Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>I believe that your argumentation holds; "critical infrastructure" is >something very personal, and "public"...what's public? Isn't google >a public service, too? Or Yahoo? Or ebay? Or ... People seem to be confused about the meaning of "critical infrastructure" so I decided to see what Google has to say. The first thing it comes up with is an American government organization called the Department for Homeland Security. On their question and answer page they say this: http://www.ciao.gov/publicaffairs/qsandas.htm 1.) What is a critical infrastructure? The USA Patriot Act defines critical infrastructures as those "systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health or safety, or any combination of those matters." That's not something very personal. It is something that is important to a large number of people. Here's another one: http://www.atis.org/tg2k/_critical_infrastructure.html critical infrastructure: 1. Elements of a system that are so vital that disabling any of them would incapacitate the entire system. Disabling .de would make the Internet unusable for millions of people in Germany and would affect millions of German-speaking people around the world. When some part of the infrastructure of the Internet is considered to be critical, the people responsible for it will build it so that it can never fail. They do this by applying fault tolerance techniques. Anycasting DNS is a fault tolerance technique. DENIC is asking for a policy that understands the need for fault tolerance when an organization is managing part of the Internet's critical infrastructure. If this policy focuses on the fault tolerance technique then it is doing the wrong things. Policies are not about technology. RIPE policies are political agreements that balance the needs of everyone in the RIPE community. This policy needs to focus on defining which kinds of "critical infrastructure" are important enough for the whole community to justify special allocations. > Es gibt Luegen, verdammte Luegen und RIPE-141(-219)-Netzantraege. Translated: There are lies, damned lies and RIPE-141 request forms. --Michael Dillon

3 2

Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>> Suggestion... RIPE will allocate /24 blocks from the IPv4 address >> range that was once called "Class C" address space >> for use by services that are part of the Internet's >> critical infrastructure. These blocks are for services >> that will exist for the forseeable future, are used >> freely by many organizations, and are likely to outlive >> the lifetime of the organization currently operating the >> service. >That's not helpful, as it centers around "critical infrastructure". How >is the RIPE NCC supposed to evaluate how "criticial" something is? A workable policy would need to have definitions of "infrastructure" and "critical" that RIPE can use to evaluate any requests. >.de reachability is mostly meaningless for the majority of the >Internet users (as are all other ccTLDs). Reachability of .com and .net is also mostly meaningless for the majority of the Internet users. They only care if they can get to .cn sites because they can only read one language. The Internet has never recognized the tyranny of the majority so I don't think we should be worrying about this today. --Michael Dillon

3 2

Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>In which case I claim that my PC at home is a highly critical infrastructure >as well. When I posted the following suggestion, it included a definition for critical infrastructure and your PC at home doesn't meet it. Suggestion... RIPE will allocate /24 blocks from the IPv4 address range that was once called "Class C" address space for use by services that are part of the Internet's critical infrastructure. These blocks are for services that will exist for the forseeable future, are used freely by many organizations, and are likely to outlive the lifetime of the organization currently operating the service. Your PC at home is not offering a service that will exist for the foreseeable future. I can forsee a future for the Internet into the 22nd century when you and your home PC will be dead. Your home PC is probably not offering a service that is used freely by many organizations. I think this part of the definition needs some work because some people would argue that Google's service meets this criteria but I would argue that part of Google's service are the ads which are not offered freely, i.e. they cost money. Your home PC is not offering any service that would continue to be offered even if you and your home and your company cease to exist. But if DENIC ceases to exist, it is 100% certain that ICANN would find some other organization to continue offering .de nameservice. Maybe this definition should use a name other than critical infrastructure. And my suggestion is nothing more than a first draft. My main point is that a new policy proposal should begin with a first draft of the policy itself so that people can discuss the draft policy instead of spending all the time discussing why it is impossible to write a policy at all. --Michael Dillon

2 1

Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>>People seem to be confused about the meaning of "critical infrastructure" >>so I decided to see what Google has to say. The first thing it comes up >>with is an American government organization called the Department for >>Homeland Security. On their question and answer page they say this: >>http://www.ciao.gov/publicaffairs/qsandas.htm >Why should Europe and the RIPE region care about what the US defines as >critical infrastructure? Two reasons. 1. We were talking about Google and if you use Google to search for "critical infrastructure" that is the first link that comes up. 2. There was confusion about the meaning of the English language phrase "critical infrastructure" and it is useful to study how native speakers of English define this phrase. The U.S.A. contains a large number of native English speakers. If you prefer European sources, here is a PDF booklet from the UK's National Infrastructure Security Co-ordination Centre formed in 1999 before the U.S.A. was putting so much emphasis on homeland security. http://www.niscc.gov.uk/aboutniscc/booklet/NISCC%20Booklet2.pdf And if you want EU sources, then here is a report to the EU Parliament on Scientific and Technological Options Assessment (STOA) that is published in both English and German http://www.europarl.eu.int/workshop/itsecurity/docs/helmbrecht_en.pdf http://www.europarl.eu.int/workshop/itsecurity/docs/helmbrecht_de.pdf The point is that "critical infrastructure" is a term that many people already use in policies and they always find it important to provide a definition for the term within the context that they are discussing. RIPE can do the same. --Michael Dillon (living and working in London)

1 0

Re: Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Sabine Dolderer/Denic 08 Jan '04

08 Jan '04

On 08.01.2004 12:10 Hank Nussbacher <hank(a)att.net.il> wrote: > > At 11:01 AM 08-01-04 +0000, Michael.Dillon(a)radianz.com wrote: > > >People seem to be confused about the meaning of "critical infrastructure" > >so I decided to see what Google has to say. The first thing it comes up > >with is an American government organization called the Department for > >Homeland Security. On their question and answer page they say this: > >http://www.ciao.gov/publicaffairs/qsandas.htm > > > >1.) What is a critical infrastructure? > > > >The USA Patriot Act defines critical infrastructures as those > >"systems and assets, whether physical or virtual, so vital to the > >United States that the incapacity or destruction of such systems > >and assets would have a debilitating impact on security, national > >economic security, national public health or safety, or any > >combination of those matters." > > Why should Europe and the RIPE region care about what the US defines as > critical infrastructure? Because it is not only a US-centric view of the Internet. Most governments (at least the German which I know best and most other Europeans) have started to make their own definitions about what they define as critical to their national infrastructure. And they are asking questions how these infrastructure is protected. But I tend to agree that it is maybe better if we find a more neutral wording. Sabine > > > > > Es gibt Luegen, verdammte Luegen und RIPE-141(-219)-Netzantraege. > > > >Translated: There are lies, damned lies and RIPE-141 request forms. > > It is RIPE-219. RIPE-141 is dead. > > > >--Michael Dillon > > -Hank > > Viele Grüße Sabine Dolderer -- Sabine Dolderer DENIC eG Wiesenhüttenplatz 26 D-60329 Frankfurt eMail: Sabine.Dolderer(a)denic.de Fon: +49 69 27235 0 Fax: +49 69 27235 235

1 0

Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>> Conservation is not an issue regarding IPv6. >...within an address block, this is true. However, what is being >talked about here is "globally routeable chunks of addresses", and >there conservation *is* an issue, since nothing really changes with >respect to routing with IPv6 compared to IPv4. It is best to clarify what resource we want to conserve. I don't think there is any need to conserve IPv4 addresses any more. Exponential growth is a think of the past and we have enough IPv4 addresses to last 10 to 20 years. We also have a replacement protocol, IPv6, that is already commercially deployed in Asia and in Europe. However, we might still want to conserve the number of entries in the global routing table because of the impact on router memory, router CPU and the time required to reload a full view of the Internet when a router is restarted. If we refuse to give DENIC a /24 from the recovered "Class C" swamp space we would be saving a small amount of IPv4 address space but we might not save any global routing table entries... --Michael Dillon

2 1

Re: [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
by Michael.Dillon＠radianz.com 08 Jan '04

08 Jan '04

>That's why I'm in favour to have a policy that permits allocations for >specific, well-defined Anycast services. That allocations would come >from a well-known block, so people would know to not filter /24s from >there (and so on). I agree that there should be a specific and well-defined policy. But I think that this policy does not need to be restricted to anycast services. It is a good thing to allocate only /24s and not any longer prefixes like /32 because there is no shortage of IPv4 address space and no need to conserve this space so severely. And I think that the well-known block used for this type of allocation should come from the old "Class C" swamp space. We have recovered lots of unused addresses from this area and we should begin to allocate them for special purposes which can benefit a large part of the community. --Michael Dillon

2 1