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 >>>

Re: Interim Policy proposal for IPv6 Address Assignment Policy forInternet Exchange Points

  • To: < >
    < >
    < >
    < >
  • From: Dave Pratt < >
  • Date: Fri, 31 Aug 2001 15:30:39 +0200 (CEST)

Hiya all,

Unfortunately, I must respond against the proposal as it stands with use of a
/64 allocation.

Allocations of /64 for the peering LAN can be obtained already from a separate
block (I forget the details - but I think from a US based ISP only block
managed by David Huberman). I fail to see therefore what this proposal helps
with.

This does not solve the problem as I see it, which is how to reliably, and
independently of a particular ISP, multihome the infrastructure associated
with the exchange point. From which range do the addresses for www.IXP.net or
lg.IXP.net or term-serv.IXP.net come from ?

For this I propose globaly routable allocations be made, with a size of at
least /48. The IXP can then decide whether to use part of that for the
exchange LAN, or whether to get a separate /64.

Cheers
Dave

On Fri, 31 Aug 2001, Fearghas McKay wrote:

->Since the address space does not need to be routable globally and an
->IXP is expected to only have one subnet, a /64 (64 bits of address
->space) will be assigned in most cases.
->
->In the case the IXP is using multiple fabrics (e.g. unicast separated
->for multicast), multiple /64s can be assigned to the IXP.







  • 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