<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Turchanyi Geza</b> <<a href="mailto:turchanyi.geza@gmail.com">turchanyi.geza@gmail.com</a>><br>Date: May 4, 2008 12:00 PM<br>
Subject: Re: [address-policy-wg] Joking follow-up, second round<br>To: Carlos Friacas <<a href="mailto:cfriacas@fccn.pt">cfriacas@fccn.pt</a>><br><br></span>Hello,<span class="q"><br><br>
<div><span class="gmail_quote">On 5/2/08, <b class="gmail_sendername">Carlos Friacas</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cfriacas@fccn.pt" target="_blank">cfriacas@fccn.pt</a>> wrote:</span> </div>
</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span class="q">On Wed, 30 Apr 2008, Turchanyi Geza wrote:<br><br></span><span class="q"><span><br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">3, My suggestion was at RIPE 55 (and in my previous letter): let's do<br>something similar in case of IPv6 what we have done with IPv4. "pseudo"<br>
dynamic IPv6! (Which is rather static, BTW.)<br></blockquote><br></span>For ISPs i'm assuming it would be easier to use static allocations, instead of managing pools. Adding records to public databases is something separate...</span></blockquote>
<div> </div>
<div>Please rememeber, that I also suggested a technical solution: calculate the IPv6 addresses (subnet) from the previously allocated IPv4 address of the DSL user! </div>
<div> </div>
<div>That means: if we are able to allocate IPv4 addresses in "pseudo dynamic" way (wich is rather static), then we will be able to allocate IPv6 networks roughly at the same way.</div><span class="q">
<div> </div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">4, It is possible to allocate even /48 for every DSL users, even with the<br>"pseudo" dynamic IPv6 allocation mechanism, however, why should we do it? If<br>
an "anonym" DSL user could use the same amount of the address space than a<br>RIPE registered DSL user then nobody will register its address space in the<br>database!<br></blockquote><br></span>You're trying to draw a line to distinguish residential users from enterprises, is that it?</blockquote>
<div> </div></span>
<div>No. I try to draw a line between "light" service and "serious" one (Or: between "dummies" and "experts".)</div><span class="q">
<div> </div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">5, The IPv6 address space is huge, however, if we do not know who is using<br>it then we will loose it soon.<br></blockquote>
<br></span>We should always be able to link a single IPv6 address to an LIR/ISP...</blockquote>
<div> </div></span>
<div>It won't help, unfortunately. How many people live in Holland? How many SIM card (mobile phone contract) exist? Much more, than people...</div><span class="q">
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">6, Therefore my suggestion was amends previous policies (what were fine for<br>the "experts", knowing what an IP address is and what a subnet is).<br>
<br></blockquote></span></blockquote>
<div><br> </div></span><span class="q">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">8, I also would prefer if the "anonym" DSL users would share a visible<br>different address space than the registered one. If IANA would reserve a<br>
prefix (preferably a /16) for the "anonym" DSL (mobile, CATV, etc) users,<br>then the RIRs could allocate big pools from this prefix to ISPs using<br>different allocation criteria than for the "registered" IPv6 networks.</blockquote>
</span></blockquote>
<div> </div></span>
<p>Different allocation criteria also mean: sparser usage at the beginning. If we allocate an IPv6 subnet to each and every DSL costumer, very few of them will realy use it at the beginning. However, fast IPv6 transition is not possible without this "generosity".</p>
<div><span>The suggested size of the "anonym" pool is depend on the number of costumers: a /36 for very larg ISPs (more than 15 million costumers), a /40 for medium ISPs, a /44 for smaller ISP-s (less than 1 million costumers)<br>
</span></div>
<div><span>Yes, there are ISP-s serving more than 15-16 millions costumers! This is one of the reasons why I suggested the creation of a new type of reusable addresses, the AS-local IPv4 address pool!</span></div>
<div><span> </span></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid"><span class="q">
<p>Back to the AS-local IPv4 address space concept:<br><br><br><br>Private address space have to be unique within a routing domain, AS-local<br>address space is unique within the given Autonomous System. (A group of<br>autonomous Systems might share<br>
<br>even this address space, but this is the exception, and not the rule.)<br><br><br><br>I do think that the AS-local address pool can be created as a collaborative<br>effort. IANA, ISPs can lease address blocks for this pool. This is not<br>
trading, but still a reallocation! Any reallocation policy should allow<br>creation of a common address pool!<br><br><br><br>It is easier to allocate "automatic" and "anonym" IPv6 network for DSL users<br>
if we have a<br><br>big enough, better routable IPv4 address pool, an AS-local address pool.<br><br><br><br>Please read also my proposals:<br><br><br><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.ripe.net/ripe/meetings/ripe-55/presentations/turchanyi--two-jokes.pdf" target="_blank">http://www.ripe.net/ripe/meetings/ripe-55/presentations/turchanyi--two-jokes.pdf</a><br>
<br><br><br>and my presentation: (<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.ripe.net/ripe/meetings/ripe-55/presentations/turchanyi-two-jokes-half-proposal.pdf" target="_blank">http://www.ripe.net/ripe/meetings/ripe-55/presentations/turchanyi-two-jokes-half-proposal.pdf</a><br>
<br><br><span></span></p></span>
<p>Best regards,<span></span></p>
<p><span></span> </p>
<p>Geza</p></blockquote>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">
<p><span></span> </p></blockquote>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">
<p><span></span> </p></blockquote>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">
<p><span></span> </p></blockquote></blockquote></blockquote></blockquote></blockquote>