[arin-ppml] IPv4 SWIP requirements (?)

Michael Peddemors michael at linuxmagic.com
Sat May 27 16:40:08 EDT 2017


While this is a nice step, and indicates a move forward towards this..
(Wish I just had more time to contribute..)

It would be nice that somehow we find a way to 'assist' ARIN, in a 
public manner, and have it adopted in policy in some form.

We have had several ppl who 'see' on a regular basis bad/poor SWIP 
records and practices.

Proposal Idea:

Allow the community at large to 'register' complaints, but instead of 
having it sent to what for all intents and purposes can seem like a an 
opaque resolution process, have such complaints registered as publicly 
searchable 'tickets'.


ABC Company operates a /16 assigned by ARIN, which lists a redirection 
to a 'rwhois' server, which is currently not responding, or 
non-existant.  Rather than ARIN having to search those out (while it can 
be automated of course, a simple script can attempt to probe the listed 
'rwhois' servers) which may take resources ARIN doesn't have at it's 
disposal, allow a ticket to be filed by the internet community, and all 
tickets and their investigation/resolution status can be viewed.


Ticket Submitted By: <email_address>
Ticket Submitted Date:
Ticket Class: Non-Responsive RWhois Server in SWIP record
Ticket Status: Unconfirmed
Arin Confirmation Date:
First Notification to Owner Sent:
Owner Response:
Expected Resolution Date:

You get my drift.. that way if the information is public, not only will 
this encourage owners to update the information (shame them) but will 
give the community an idea of whether the actual resolution process is 
ongoing, and an idea that is will culminate in actual action.

While I have no doubt that ARIN takes seriously all reports sent to 
them, we have no way of knowing if it simply cannot be addressed due to 
limited resources, or slipped through the cracks, or if ARIN actually is 
hard at work solving the problem..

On 17-05-27 11:00 AM, Cj Aronson wrote:
> Peter
> The draft is still on the AC's docket and the shepherds are working on
> it.  I think it should be part of this discussion so I mentioned it so
> that folks could take a look.
> Thanks!
> -----Cathy
> {Ô,Ô}
>   (( ))
>   ◊  ◊
> On Fri, May 26, 2017 at 5:34 PM, Peter Thimmesch
> <peter.thimmesch at addrex.net <mailto:peter.thimmesch at addrex.net>> wrote:
>     Hello Cathy,
>     Yes, the was some rather heated discussion at the ARIN meeting in
>     New Orleans about the proposed wording in 3.6.7 Non-Responsive Point
>     of Contact Records. I believe, please correct me if you think
>     otherwise, that the consensus of opinions that spoke at the meeting
>     were strongly against the removing of records from public Whois.
>     Therefore pointing someone to consider this type of punitive action
>     would be seemingly designed to do what?
>     What problem is trying to be solved with this proposed policy? Is it
>     to align the two existing policies or to create a punitive measure?
>     Regards,
>     Peter Thimmesch
>     On May 26, 2017, at 19:09, Cj Aronson <cja at daydream.com
>     <mailto:cja at daydream.com>> wrote:
>>     Scott,
>>     On Fri, May 26, 2017 at 4:45 PM, Scott Leibrand
>>     <scottleibrand at gmail.com <mailto:scottleibrand at gmail.com>> wrote:
>>         On Fri, May 26, 2017 at 3:32 PM, Ronald F. Guilmette
>>         <rfg at tristatelogic.com <mailto:rfg at tristatelogic.com>> wrote:
>>             In message <8A3A301D-39B5-4F81-8E2C-90E23B81919E at panix.com
>>             <mailto:8A3A301D-39B5-4F81-8E2C-90E23B81919E at panix.com>>,
>>             David Huberman <daveid at panix.com
>>             <mailto:daveid at panix.com>> wrote:
>>             >In short, there is an argument that the SWIP rules are no-op now. So to answer
>>             >your question directly; what do you do? Nothing. Those days are long gone
>>             >and ARIN has other focuses now.
>>             So, let me see if I understand this...
>>             ARIN doesn't, can't, and most probably won't either
>>             enforce the existing
>>             (IPv4) SWIP rules, nor, for that matter, any new SWIP
>>             rules that may be
>>             drafted and/or promulgated with respect to IPv6.  Is that
>>             about the size
>>             of it?
>>         Pretty much, unless someone comes up with a new method of
>>         enforcing SWIP rules.  Some of the discussions with law
>>         enforcement could eventually result in such carrots or sticks,
>>         but no one has proposed any specifics yet.
>>     There is this draft policy that has a few "sticks" at least for
>>     delegations to downstream ISPs.
>>     https://www.arin.net/policy/proposals/2017_3.html
>>     <https://www.arin.net/policy/proposals/2017_3.html>
>>     ----Cathy
>>     _______________________________________________
>>     PPML
>>     You are receiving this message because you are subscribed to
>>     the ARIN Public Policy Mailing List (ARIN-PPML at arin.net
>>     <mailto:ARIN-PPML at arin.net>).
>>     Unsubscribe or manage your mailing list subscription at:
>>     http://lists.arin.net/mailman/listinfo/arin-ppml
>>     <http://lists.arin.net/mailman/listinfo/arin-ppml>
>>     Please contact info at arin.net <mailto:info at arin.net> if you
>>     experience any issues.
> _______________________________________________
> 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.

"Catch the Magic of Linux..."
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.

More information about the ARIN-PPML mailing list