Re: [sig-policy] Need to understand logic behind assigning /64 IPv6 addr

To: Usman Latif <osmankh at yahoo dot com>
Subject: Re: [sig-policy] Need to understand logic behind assigning /64 IPv6 addresses
From: Sander Steffann <sander at steffann dot nl>
Date: Fri, 16 Sep 2011 16:35:52 +0200
Cc: sig-policy at lists dot apnic dot net
Delivered-to: sig-policy at mailman dot apnic dot net
In-reply-to: <CA996BAA.4735C%skeeve at eintellego dot net>
List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy>
List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
List-post: <mailto:sig-policy@lists.apnic.net>
List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
References: <CA996BAA.4735C%skeeve@eintellego.net>


> If that is the case… and Uecomm has a /32, I don't think you are going to have a problem for a long time if you use /64's.  This is a key reason that many are handing out /56's…. There is 16.7million /56's in a /32.
> 
> So while it might seem like wastage… giving a /64, or a /56 to each end user, really, in the end is meaningless in the scale of things… 

And giving a /64 or less to your customers will hurt the ISP in the long run.

Giving less than a /64 means that autoconf will not work, which will increase support cost. If other ISPs in the same service area do give enough addresses for autoconf, you will be the ISP with a bad reputation. Equipment (CPE's etc) that will 'just work' with those other ISPs won't work for your customers.

When you give a customer just one /64, then they will have problems with things like separate networks for the home office or a separate guest network. I have heard someone from (I think) Linksys state that new products will use multiple /64's for such setups. Home automation stuff doesn't run on ethernet and can not be bridged. That means it will need separate address space. Because of all this, multiple /64's are expected to be used in one home or small business. Providing just one /64 will also increase support cost. Maybe not today, but certainly soon.

And then you reach the point in the future where the support cost is much too high for your business, you decide to adjust your policies and give each customer multiple /64's, and you get to do a customer-renumbering project, which can also be expensive in support cost...

So I recommend that you start with multiple /64's from day one. A /56 is commonly used, so it might be a good starting point.

- Sander

Attachment: smime.p7s
Description: S/MIME cryptographic signature