ARIN does sparse allocation, where every /32 has 15 more /32s reserved for you (a /28). Since almost no one really knows what they're doing yet (in my opinion; it's all first generation greenfield deployments we are doing), I say go ahead and give a /48 to each customer and re evaluate in the future when you have more data. Being liberal with customers is better for them than being overly stingy. And you aren't harming the "free pool" since the first /32 is one sixteenth of what is already held for you.
Sent using OWA for iPhone ________________________________________ From: [email protected] <[email protected]> on behalf of james machado <[email protected]> Sent: Thursday, August 13, 2015 4:15:18 PM To: John Santos; [email protected] Subject: Re: [arin-ppml] Automatic IPv6 Eligibility John, A /64 is just one network. Arguments have been made that a smart phone "needs" multiple /64's just to run IPv6 much less a "site" or building. The current fight is between a /56 and a /48 for each customer as internal networking in v6 is going to happen. Much discussion has been happening on both Nanog and IPv6-ops mailing lists. James On Thu, Aug 13, 2015 at 3:59 PM, John Santos <[email protected]> wrote: > > Maybe off-topic, but the recommendation for assigning a /48 to each of > the ISP's customers... Does that apply only to business customers > and organizations, etc., or does it also apply to residential customers? > Why would a residence (unless they're network hackers like most of us) > ever need more than a /64, let alone 2^16 /64's? I don't see any obvious > use case for people subnetting their house or appartment :-) > > I'm sure this has been discussed to death here and elsewhere. I've not > yet been involved in any large-scale IPv6 deployments (just our lone LAN > that easily fits in a IPv4 /24, and doesn't yet have any off-site IPv6 > connectivity), so I'm trying to internalize IPv6 best practices before > screwing up too badly. > > -- > John Santos > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539 > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&data=01%7c01%7cdavid.huberman%40microsoft.com%7c06e8fab9a69144071e9a08d2a4351821%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=VernkETOP5Y%2bDrncl9%2f4WwqYm6eBqjiAZvlTa4M0Mx4%3d > Please contact [email protected] if you experience any issues. _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&data=01%7c01%7cdavid.huberman%40microsoft.com%7c06e8fab9a69144071e9a08d2a4351821%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=VernkETOP5Y%2bDrncl9%2f4WwqYm6eBqjiAZvlTa4M0Mx4%3d Please contact [email protected] if you experience any issues. _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
