IP addresses for the RIPE NCC
Dear working Group, Now that we have a new interim policy in place, an important policy question comes up: How can the RIPE NCC get IP addresses for their services ? Either they qualify trough the Interim policy or they need to go to their upstream. Trouble is that as far as I know the RIPE NCC has no upstream provider, as they are multihomed to a substantial number of subscribers. What is the workinggroup opinion on this ? Regards, -hph
On Wed, May 08, 2002 at 09:31:33PM +0200, Hans Petter Holen wrote: | Dear working Group, | Now that we have a new interim policy in place, an important policy question | comes up: How can the RIPE NCC get IP addresses for their services ? | | Either they qualify trough the Interim policy | | or they need to go to their upstream. | | Trouble is that as far as I know the RIPE NCC has no upstream provider, as | they are multihomed to a substantial number of subscribers. | | What is the workinggroup opinion on this ? Please also try to form an opinion on the IPv6 network allocation that the RIPE NCC will be wanting to use for their services. groet, Pim -- __________________ Met vriendelijke groet, /\ ___/ Pim van Pelt /- \ _/ Business Internet Trends BV PBVP1-RIPE /--- \/ __________________
Trouble is that as far as I know the RIPE NCC has no upstream provider, as ^ single they are multihomed to a substantial number of subscribers.
same as lots of small multi-homed sites. this is not new. they can get space from any one of their upstreams. randy
Randy Bush wrote:
Trouble is that as far as I know the RIPE NCC has no upstream provider, as ^ single they are multihomed to a substantial number of subscribers.
same as lots of small multi-homed sites. this is not new. they can get space from any one of their upstreams.
I must say, reluctant as I am usually to agree with Randy :-) I think he is right in this instance. I'm sure that any one of a number of the RIPE NCCs upstreams would be happy to fill out the paperwork for a couple of /24s, which the RIPE NCC could then approve (after appropriate checking of course). Nigel
Hi, just a bit of information. The RIPE NCC has enough IPv4 addresses to support its present and foreseen services and infrastructure. See whois.ripe.net The RIPE NCC, on the other hand, has no IPv6 addresses. I think this matter is one for the LIRs, as main users of RIPE NCC services, to decide on. I shall not try to defend any of the possible options but would definitely request a path forward in order for us to be able to start implementing services over IPv6 transport. Thanks Joao On Wed, 8 May 2002, Nigel Titley wrote:
Randy Bush wrote:
Trouble is that as far as I know the RIPE NCC has no upstream provider, as ^ single they are multihomed to a substantial number of subscribers.
same as lots of small multi-homed sites. this is not new. they can get space from any one of their upstreams.
I must say, reluctant as I am usually to agree with Randy :-) I think he is right in this instance. I'm sure that any one of a number of the RIPE NCCs upstreams would be happy to fill out the paperwork for a couple of /24s, which the RIPE NCC could then approve (after appropriate checking of course).
Nigel
oh, it's ipv6? then you should get a /48 from *each* of your upstreams and your hosts will each choose source and dest v6 addresses appropriately to use the most optimal routing for a packet. and, if you believe that, you'll believe that v6 provides easy rapid and frequent renumbering, reasonable auticonf, and flying pigs. </sarcasm> i suggest you treat v6 just as v4. get a prefix from an upstream and announce it. the reality to smoke ratio on v6 multi-homing is embarrassing. randy
participants (5)
-
Hans Petter Holen -
Joao Luis Silva Damas -
Nigel Titley -
Pim van Pelt -
Randy Bush