About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

[ipv6-wg@localhost] Re: [lir-wg] IXP networks routing

  • To: < >
    < >
  • From: Arien Vijn < >
  • Date: Mon, 03 Mar 2003 23:28:25 +0100

On 03-03-2003 22:20PM, "Gert Doering" gert@localhost wrote:

>> Come on. Calm down. Think! Ripe is surely educated enough to
>> differentiate between a Enterprise, ISP or IXP.
> 
> Can you *define* what is an IXP?  In a way that an enterprise aiming for
> PI space can't cheat and match that definition?
> 
> I cannot.

Pretty common definition (also in RIPE-256):

"An Internet Exchange Point is defined as a physical network infrastructure
(layer 2) operated by a single entity whose purpose is to facilitate the
exchange of Internet traffic between ISPs. There must be a minimum of three
ISPs connected and there must be a clear and open policy for others to join"

Cheating seems quite a burden too me...

Anyway RIPE-256 just works well. Every IXP in the RIPE region can easily get
a /48 for the peering mesh. In fact it seems easier than requesting IPv4 PI
space (which is good :) )

The issues remains the IPv6 space for services. Yes, I know that this has
been "discussed" before. However it seems that the discussion has not ended.

Arien




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community