<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [address-policy-wg] RE: [policy-announce] 2009-06 New Policy Proposal (Removing Routing Requirements from the IPv6 Address Allocation Policy)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Vladislav, this is a function that the RIPE NCC have always provided, if this relationship is truely private then I would suggest consulting RFC1918 or RFC4193.<BR>
<BR>
------------------------------------------------<BR>
David Freedman<BR>
Group Network Engineering<BR>
Claranet Limited<BR>
<A HREF="http://www.clara.net">http://www.clara.net</A><BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: address-policy-wg-admin@ripe.net on behalf of poty@iiat.ru<BR>
Sent: Fri 5/29/2009 09:12<BR>
To: nick@inex.ie; frederic@placenet.org<BR>
Cc: address-policy-wg@ripe.net<BR>
Subject: RE: [address-policy-wg] RE: [policy-announce] 2009-06 New Policy Proposal (Removing Routing Requirements from the IPv6 Address Allocation Policy)<BR>
<BR>
Nick, just because there is the word "private". Why should RIPE or some other organization (including mine) provide the registration and supporting service (for example - uniqueness) for PRIVATE networks? If a company wants to use interconnection with other companies - it is their PRIVATE deal. And they should use their PRIVATE means for achieving that!<BR>
<BR>
<BR>
Potapov<BR>
Ru.iiat<BR>
<BR>
-----Original Message-----<BR>
From: address-policy-wg-admin@ripe.net [<A HREF="mailto:address-policy-wg-admin@ripe.net">mailto:address-policy-wg-admin@ripe.net</A>] On Behalf Of Nick Hilliard<BR>
Sent: Friday, May 29, 2009 4:18 AM<BR>
To: Frederic<BR>
Cc: address-policy-wg@ripe.net<BR>
Subject: Re: [address-policy-wg] RE: [policy-announce] 2009-06 New Policy Proposal (Removing Routing Requirements from the IPv6 Address Allocation Policy)<BR>
<BR>
On 27/05/2009 17:41, Frederic wrote:<BR>
> but we suggest that may be a good rule to write somewhere that it's ask<BR>
> to LIR to garant routing.<BR>
><BR>
> so we do not support this 2009-06. because this confirm to let choice<BR>
> for operator so it let choice to not garant routing.<BR>
<BR>
from my other mail to this mailing list:<BR>
<BR>
"- just because an organisation hasn't announced an ipv6 prefix on the<BR>
Internet-with-a-capital-I[*], that doesn't mean they aren't using the<BR>
address space for other entirely valid purposes."<BR>
<BR>
Frederic, can you please explain why a LIR which:<BR>
<BR>
1. requires an ipv6 allocation for use on a private network<BR>
2. meets all the other requirements of the IPv6 address allocation policy<BR>
3. requires unique addresses (e.g. interconnecting with other private ipv6<BR>
networks)<BR>
<BR>
... shouldn't be granted a RIPE IPv6 allocation?<BR>
<BR>
Or are you trying to say that there is only a single valid IPv6 network in<BR>
the world?<BR>
<BR>
Nick<BR>
--<BR>
Network Ability Ltd. | Head of Operations | Tel: +353 1 6169698<BR>
3 Westland Square | INEX - Internet Neutral | Fax: +353 1 6041981<BR>
Dublin 2, Ireland | Exchange Association | Email: nick@inex.ie<BR>
<BR>
[*] whatever the "Internet-with-a-capital-I" means<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>