[arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6

Thu Jul 20 19:08:25 EDT 2017

Well I think in the bus example you would swip to the overall authority.
But seriously this conversation has gone in so many different directions do
any of us remember the original point?

My vote as it applies to v6: Non-residential allocations of greater than or
equal to a /48.

If you as an ISP choose to allocate a /48 to a residential customer - then
have fun. But this does not affect the purpose of the policy as most use it
these days which is abuse management. Also as I understand it, there is an
exception to the CPNI as it applies to business customers as long as they
have an account manager and adequate language in the contract. How many of
the smaller ISPs have a customer deserving of a /48 or better that does not
have a larger account or spend? If a customer requests a large enough block
from us, regardless of v4 vs v6, they agree via email/ticketing/contract
that their business information will be made public. This is not difficult
to put in your signed agreements with your business customers thus making
the CPNI argument invalid.

-Chris

On Thu, Jul 20, 2017 at 2:28 PM, <hostmaster at uneedus.com> wrote:

> My transit bus example is another example of SWIP difficulty.  Very hard
> to provide a street address to SWIP a bus when it is mobile 16 hours a day.
>
> Current policy says SWIP every /64 or more, which is every network in v6.
>
> I did a check here, and in v4, only 1% of customers have more than 8 ip's,
> and these customers are colocation customers who have a bunch of SSL
> sites.  These are grandfathered. New customers are told to use 1 IPv4
> address and SNI or better yet, IPv6, as we do not have the money to buy
> more V4.  We would rather use our v4 inventory for access customers.
>
> Yes, it is just a few pieces of information for SWIP.  However, we do not
> have clerical staff to do it, because except for the SSL colocates, there
> never has been v4 SWIP's required here. Why should the policy state that
> just because we give each customer an assignment of v6, we must SWIP that
> same small customer that did not require SWIP in v4? (Welcome to IPv6, now
> fill out this form.....) Also noted is that the SWIP registration details
> without written permission might get us in trouble with the FCC over CPNI.
> As a WISP that has licensed microwave links, we do pay attention to Uncle
> Charlie.
>
> Albert Erdmann
> Network Administrator
> Paradise On Line Inc.
>
> On Thu, 20 Jul 2017, Chris James wrote:
>
> @Paul - The API key is to email it.
>>
>> @Owen - Very difficult when you have dynamic ranges, and vps/container
>> platforms spanning tens of thousands of instances across these dynamic
>> ranges.
>>
>>
>> On Thu, Jul 20, 2017 at 1:51 PM, Paul McNary <pmcnary at cameron.net> wrote:
>>
>> Owen
>>>
>>> The reassignment policy page says IPv6 has to be done vi API.
>>> Is that something else that is incorrect on the web site?
>>>
>>> Paul
>>>
>>>
>>> On 7/20/2017 3:16 PM, Owen DeLong wrote:
>>>
>>> How can it be overly difficult to fill out an email template with your
>>>> customers’
>>>> Name, Address, Phone Number?
>>>>
>>>> Really?
>>>>
>>>> Owen
>>>>
>>>> On Jul 19, 2017, at 23:48 , Pallieter Koopmans <Pallieter at pallieter.org
>>>> >
>>>>
>>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> ARIN could quantify and require rules for when to SWIP, but in the
>>>>> end, there are going to be exceptions needed if the rules are to be
>>>>> strictly followed. Many will not separately SWIP a separately routed
>>>>> sub-block if it is too difficult or pointless to gather and share that
>>>>> data back upstream to ARIN.
>>>>>
>>>>> Thus a more fuzzy rule to require a best-effort and to add a
>>>>> rule-based reason (preferably both a carrot and a stick) for block
>>>>> owners to do their best to provide (only) useful data. In order to do
>>>>> that, one needs to look back at why that data is needed. For a block
>>>>> owner to assign the SWIP on a sub-block, he basically delegates tech
>>>>> and abuse contact requests down to those that are probably more likely
>>>>> to be able to actually act on the tech/abuse requests (and thus reduce
>>>>> request-handling workload higher up and overall). But for that to
>>>>> work, those tech/abuse contact requests need to be actually handled,
>>>>> otherwise, it is better to leave them with the block owner.
>>>>>
>>>>> In the end, the contact details should be as close to the "person"
>>>>> that is actually capable to both handle (think: volume/languages/etc)
>>>>> and act (think: authority) on the tech/abuse requests.
>>>>>
>>>>> eBrain
>>>>> Innovative Internet Ideas
>>>>>
>>>>> Pallieter Koopmans
>>>>> Managing Director
>>>>>
>>>>> +31-6-3400-3800 (mon-sat 9-22 CET)
>>>>> Skype: PallieterKoopmans
>>>>> _______________________________________________
>>>>> PPML
>>>>> You are receiving this message because you are subscribed to
>>>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>>>> Unsubscribe or manage your mailing list subscription at:
>>>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>>>> Please contact info at 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 at arin.net).
>>>> Unsubscribe or manage your mailing list subscription at:
>>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>>> Please contact info at 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 at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contact info at arin.net if you experience any issues.
>>>
>>
>> --
>> This e-mail message may contain confidential or legally privileged
>> information and is intended only for the use of the intended recipient(s).
>> Any unauthorized disclosure, dissemination, distribution, copying or the
>> taking of any action in reliance on the information herein is prohibited.
>> E-mails are not secure and cannot be guaranteed to be error free as they
>> can be intercepted, amended, or contain viruses. Anyone who communicates
>> with us by e-mail is deemed to have accepted these risks. This company is
>> not responsible for errors or omissions in this message and denies any
>> responsibility for any damage arising from the use of e-mail. Any opinion
>> and other statement contained in this message and any attachment are
>> solely
>> those of the author and do not necessarily represent those of the company.
>>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>

-- 
This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended recipient(s). 
Any unauthorized disclosure, dissemination, distribution, copying or the 
taking of any action in reliance on the information herein is prohibited. 
E-mails are not secure and cannot be guaranteed to be error free as they 
can be intercepted, amended, or contain viruses. Anyone who communicates 
with us by e-mail is deemed to have accepted these risks. This company is 
not responsible for errors or omissions in this message and denies any 
responsibility for any damage arising from the use of e-mail. Any opinion 
and other statement contained in this message and any attachment are solely 
those of the author and do not necessarily represent those of the company.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20170720/a5df3939/attachment.htm>