[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sig-ipv6] Re: IPv6 Policy Document Revision suggestion
- To: stuart.prevost@bt.com
- Subject: [sig-ipv6] Re: IPv6 Policy Document Revision suggestion
- From: Gert Doering <gert@space.net>
- Date: Thu, 13 Jul 2000 18:33:43 +0200
- Cc: ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net, mir@ripe.net, ipng@sunroof.eng.sun.com, sig-ipv6@apnic.net, richardj@arin.net, Daniel.Karrenberg@ripe.net, joao@ripe.net
- In-reply-to: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk>; from stuart.prevost@bt.com on Thu, Jul 13, 2000 at 03:47:30PM +0100
- References: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk>
- Sender: owner-sig-ipv6@lists.apnic.net
Hi,
On Thu, Jul 13, 2000 at 03:47:30PM +0100, stuart.prevost@bt.com wrote:
> From reading all the emails it seems that the /48 approach as the
> *minimum* allocation is the way the IETF would like IPv6 deployment to
> proceed. However, as it has been demonstrated, the /35 allocations today
> would only allow for 8,192 /48 per subTLA, and this is assuming that the
> subTLA holder hasn't split up the NLA block so they can allocate to other
> providers, in which case this figure could be as small as 256 or lower!!!!
>
> I see this as the reason why ISPs consider /48 for a home customer
> as too large, and hence the sliding-window & /56 discussion at the last RIPE
> meeting.
Exactly this was the reason from our side for welcoming the /48, /56, /64
suggestion: having more "elbow space" in the /35 allocated to us, being
able to do reasobale NLA structuring (to our resellers, and to *their*
resellers).
regards,
Gert Doering
-- NetMaster
--
SpaceNet GmbH Mail: netmaster@Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
80807 Muenchen Fax : +49-89-32356-299
* sig-ipv6: APNIC SIG on IPv6 technology and policy issues *
* To unsubscribe: send "unsubscribe" to sig-ipv6-request@apnic.net *