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

Fwd: RE: IPv6 addresses for Exchange Points

  • From: Fearghas McKay < >
  • Date: Wed, 9 May 2001 18:05:28 +0100

The main discussion on this will happen on the LIR WG list - so I suggest people interested in IPV6 for IXPs should subscribe to LIR for the discussion.


--- begin forwarded text


Delivered-To: lists-lir-wg-out@localhost
From: paul.mylotte@localhost
To: lir-wg@localhost
Subject: RE: IPv6 addresses for Exchange Points 
Date: Wed, 9 May 2001 17:00:44 +0100 
Sender: owner-lir-wg@localhost

At the RIPE 39 joint meeting it was clarified that we should cater for the 
support of both types of IPv6 exchanges, viz:

*	allocate addresses for IPv6 exchange infrastructure only (no onwards

allocation in the manner of a backbone ISP). 
*	allocate a sub TLA to the IPv6 exchange which will then act in the 
manner of an ISP and allocate downstream.

In order to progress this, I would like to propose: 

*	 IPv6 exchanges that need addresses for the purpose of internal
addressing 
can apply for the addresses already set aside for this purpose and held by
IANA, 
as per RFC2928 and RFC2450. In this case a /48 allocation will be
sufficient. 
(How IPv6 exchanges should apply for these addresses is out of scope - 
either direct to IANA, or IANA allocates down to RIRs first).

*	IPv6 exchanges that plan to onward allocate addresses in the manner
of an ISP 
should apply via the existing mechanism. The existing mechanism is currently
being 
reviewed and this review should take account of any changes necessary to
include 
IPv6 exchanges explicitly desiring addresses for onward allocation as being 
acceptable candidates for address space.

 Regards,

 Paul

 P. S. Mylotte
 BTexact Technologies
 Adastral Park
 01473 606333 / + 44 1473 606333
 paul.mylotte@localhost

BTexact Technologies is a trademarkof British Telecommunications plc
Registered office 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000

This electronic message contains information from British Telecommunications
plc which may be priveleged or confidential. The information is intended to
be for the use of the individual(s) or entity named above. If you are not
the intended recipient be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. If you have
received this electronic message in error, please notify us by telephone or
email (to the number or address above) immediately.

> -----Original Message-----
> From:	Mirjam Kuehne [SMTP:mir@localhost]
> Sent:	07 May 2001 16:35
> Cc:	ipv6-wg@localhost lir-wg@localhost
> Subject:	IPv6 addresses for Exchange Points 
> 
> 
> [Apologies for multiple postings. I suggest to keep the discussion on
> lir-wg@localhost as it is related to address allocation policies].
> 
> 
> Dear colleagues,
> 
> At RIPE 39 last week in Bologna the issue of IPv6 address assignments
> to Internet Exchange Points was discussed (see also my mail from
> 24 April 2001 to these lists).
> 
> There was consensus to assign a /64 to an isolated Exchange Point.  It
> was further suggested to assign the agreed standard assignment size to
> a site (currently a /48) to a group of inter-connected Exchange
> Points.
> 
> An Internet Exchange Point was defined as follows:
> 
> 3 or more ASes and 3 or more separate entities attached to a LAN (the
> same infrastructure) for the purpose of peering and more are welcome
> to join.
> 
> The RIPE NCC proposes to proceed with assignments for Exchange Points
> under the above policy. 
> 
> Kind Regards,
> Mirjam Kuehne
> RIPE NCC
> 
> 

--- end forwarded text







  • 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