David, My understanding of best practices was /56 for residential and /48 for business.
My hesitation with requiring all static /48's to be SWIP'ed is that it will push companies to /56. The paradigm with IPv6 is very different, which complicates the discussion. A single business user with 1 computer could get a /48 or a company with 5000 computers. Another way around the issue is to require SWIP when a /48 or larger block is routed. If the block is not part of the routing table I don't see how a simple assignment is going to help anyone. Thanks, Kevin Blumberg -----Original Message----- From: ARIN-PPML [mailto:arin-ppml-boun...@arin.net] On Behalf Of David R Huberman Sent: Monday, June 19, 2017 1:37 PM To: arin-ppml@arin.net Subject: Re: [arin-ppml] IPv4 SWIP requirements (?) Hello, Albert wrote: > Based on comments so far, most agree that a /48 should be SWIP'ed > since it is routable on the internet, and since so far the majority > seems to think that /56 is small enough to not require SWIP, this > leaves 7 choices of /49 to /55 to set the limit for SWIP in the Draft. I think that when we consider SWIP boundaries, we should take into account strictly technical considerations, and not arbitrary ones. I think the argument for requiring a /48 or larger to be SWIPed is well-grounded in network engineering practices. I'm not sure I understand the technical argument for anything smaller than a /48 being mandatory. Thank you, David _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues. _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.