[101150] in North American Network Operators' Group
Re: /56 for home sites, /48 for business sites & billing considerations
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Wed Dec 19 15:36:46 2007
Date: Wed, 19 Dec 2007 21:31:59 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: Mohacsi Janos <mohacsi@niif.hu>
CC: nanog@merit.edu
In-Reply-To: <20071219151600.C30295@mignon.ki.iif.hu>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2BA4AA79DAFBB8547BC1ACE8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mohacsi Janos wrote:
>> This would force these places to:
>> a) use bridging to get that single /64 onto their network
>> thus making firewalling really difficult.
>=20
> I am not quite sure. My colleague tested NetScreen box with /64
> advertised from LNS. It seems to be working.
If you are routing the /64, thus that it exists entirely on the
clien-side, then it should work, but if you are allocating 1 single /64
to the customer, and eg keeping ::1 as the ISP side, then you have to do
weird magic to make that work.
>> b) get a 'power users' abo, which would thus make people have
>> to PAY for getting more IP addresses.
>>
>=20
> They aready do it. In Hungary, if you are home user you can have 1
> single IPv4 address. If you are a business customer, then your can have=
> an address space allocated from your provider. You pay more if you need=
> bigger address block....
That is IPv4 and seems to be the case in general for IPv4.
That mentality needs to be stopped for IPv6.
When an ISP is not going to provide /48's to endusers then RIPE NCC
should revoke the IPv6 prefix they received as they are not following
the reasons why they received the prefix for.
Greets,
Jeroen
--------------enig2BA4AA79DAFBB8547BC1ACE8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHaX+/KaooUjM+fCMRAlRhAJ9BOR2feGwfufwQFb5iY1JVmoKRhgCgixqR
O8BWYIdf1DXd2yoCOahczFM=
=CJ0y
-----END PGP SIGNATURE-----
--------------enig2BA4AA79DAFBB8547BC1ACE8--
