<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body style="font-family:Geneva,Helvetica,Arial,sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); ">Dear </span>Gert<span style="color: rgb(0, 0, 0); ">,</span><br />
<br />
Agree with your opinion regards RFC 2050.<br />
<br />
Main idea this RFC: <span style="color: rgb(0, 0, 0); white-space: pre-wrap; ">This document describes the registry system for the distribution of</span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; "> globally unique Internet address space and registry operations.</span><br />
<br />
<span style="color: rgb(0, 0, 0); white-space: pre-wrap; ">Goals:<br />
> 1. </span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; ">Conservation: Fair distribution of globally unique Internet address</span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; "> space according to the<br />
> operational needs of the end-users and Internet</span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; "> Service Providers operating networks using this<br />
> address space.</span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; "> Prevention of stockpiling in order to maximize the lifetime of the</span><span style="color: rgb(0, 0, 0); white-space: pre-wrap; "> Internet address<br />
> space.</span><br />
<br />
<span style="color: rgb(0, 0, 0); white-space: pre-wrap; ">This doesn't required anymore. </span>While RIPE doesn't have free space for distributing.<br />
<br />
It was very useful before and respect for people who wrote it while principes in this RFC were very useful long time. But for now it looks as deprecated and not updated.<br />
<br />
Some words from RFC which looks like depriceated:<br />
<pre style="color: rgb(0, 0, 0); word-wrap: break-word; white-space: pre-wrap; ">
...Currently there are three regional IRs established;
InterNIC serving North America, RIPE NCC serving Europe, and AP-
NIC serving the Asian Pacific region...</pre>
<pre style="color: rgb(0, 0, 0); word-wrap: break-word; white-space: pre-wrap; ">
...3.2 Network Engineering Plans..
</pre>
<pre style="word-wrap: break-word; white-space: pre-wrap; ">
2. a description of the network topology
3. a description of the network routing plans, including the
routing protocols to be used as well as any limitations..
</pre>
<br />
--<br />
Kind regards,<br />
Alexey Ivanov<br />
LeaderTelecom B.V. Team<br />
<br />
URL: <a href="http://www.leadertelecom.nl/" target="_blank">http://www.LeaderTelecom.nl/</a> - IP- addresses<br />
URL: <a href="http://www.GetWildcard.com/nl" target="_blank">http://www.GetWildcard.com/nl</a> - WildCard SSL certificates<br />
<br />
11.10.2012 17:46 - Gert Doering написал(а):<br />
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt" type="cite">
Hi,<br />
<br />
On Thu, Oct 11, 2012 at 03:27:48PM +0200, Wilfried Woeber wrote:<br />
> Gert Doering wrote:<br />
><br />
> [...]<br />
> > There are traces of needs-based still present in the system<br />
><br />
> AFAIK RFC2050 still is in effect.<br />
><br />
> All more recent suggestions to get it modified or retired were not successful.<br />
><br />
> I got to understand that messing around with it [c|w]ould have far-reaching<br />
> unwanted consequences for the whole IP Address Distribution System.<br />
<br />
Like we have Addresses to Distribute :-) - the IPv4 run-out has fairly<br />
fundamental consequences for the environment in which we operate, and<br />
at least one of the pillars of RFC2050 ("conservation") is not exactly<br />
relevant anymore.<br />
<br />
I consider RFC2050 a very useful document to establish principles, but it<br />
can not be binding - and in doubt, the bottom-up community based process<br />
will win.<br />
<br />
Gert Doering<br />
-- APWG chair<br />
--<br />
have you enabled IPv6 on something today...?<br />
<br />
SpaceNet AG Vorstand: Sebastian v. Bomhard<br />
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann<br />
D-80807 Muenchen HRB: 136055 (AG Muenchen)<br />
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279</div>
</body></html>