Fixed Boundary (/29) Assignments
Clive D.W. Feather clive at on-the-train.demon.co.uk
Thu Feb 8 17:26:05 CET 2001
-----BEGIN PGP SIGNED MESSAGE----- In message <Pine.GSO.4.21.0102071649210.7706-100000 at shell1.phx.gblx.net> , David R Huberman <huberman at gblx.net> writes >> In my experience, most residential customers are quite happy to use private >> IP addresses > >I must respectively disagree, and disagree vehemently. In my experiences, >residential broadband customers, paying high monthly fees, demand publicly >routable IP address space, citing both the very 'limitations' of private >address space you articulate (e.g. Napster and other IP-dependent >applications) and sales pitches of other providers who are willing to give >them publicly unique address space just to close the deal. [...] >More importantly, the conservationist's desire to promote the use of >private address space should not take precedence over real-world business >concerns. Market demand for residential DSL is high, and in many markets, >IPs have become a selling point. This debate sounds very like the static v dynamic IP debate for dialups. The people saying "NAT is good enough" are like the people saying "dialup customers don't need static IP". Well, such people are wrong. My opinion: it is not RIPE's job to restrict the type of service that an ISP provides in the name of "IP conservation". Conservation is important, but it is done by ensuring good practice, not by imposing arbitrary rules that prevent ISPs from providing innovative services. I'm agnostic on the /29 proposal, though I suspect it will save time and effort all round. But residential ADSL customers should be able to get reasonable amounts of IP space (and /30 is *not* reasonable) without significant pain. - -- Clive D.W. Feather | Internet Expert | Work: <clive at demon.net> Tel: +44 20 8371 1138 | Demon Internet | Home: <clive at davros.org> Fax: +44 20 8371 1037 | Thus plc | Web: <http://www.davros.org> Written on my laptop; please observe the Reply-To address -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQEVAwUBOoLInSNAHP3TFZrhAQFPyQgAj/fzhFyDaqkt+uYi94EYWgxk4VoT6YS/ Vl34sS4ikKusirEW/89mOeq4CJJ9RuY0zSEOtIKxbQfxhftqkm6eqJhOQC6aCszp Du8eBtI1Lt8l12MNjzrjf9HQnn/+H9zFjAQ+hjXygVQre6h/jIdRyGB/Fd8h6tJQ sg9O2g+HhInLfN27PkFS/4EHFaCabP85bx5fZYUjW9aBO6wTTFVBCH+BtNjL5ORZ vkTax3xDIroSo/AAxqcf0v9J4JGOz+UQlnGAtQbKuEKQM+h02x1WCCOLZXS3vG95 4wIeKLRoPcKm7IWl7YoqJjSjC+uG8gUnpG4Z4OwWeALnEwWjSTDmJw== =wnPy -----END PGP SIGNATURE-----
[ lir-wg Archives ]