[arin-ppml] private whois record

Chu, Yi [NTK] Yi.Chu at sprint.com
Wed Aug 8 13:20:48 EDT 2012

See inline


-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Kevin Kargel
Sent: Wednesday, August 08, 2012 11:58 AM
To: 'Chris Engel'; 'patrick at klos.com'; 'arin-ppml at arin.net'
Subject: Re: [arin-ppml] private whois record

This discussion is getting off track.  The point of conflict is not whether
the phone call needs to go directly to the NOC but whether the WHOIS
information can be completely obfuscated with a private registration.
[Chu, Yi [NTK]] You still have the upstream ISP's record in whois, as this is the reassignment out of the ISP block.  So you can take it to the upstream ISP, and resolve your issue from there.

The Administrative PoC is less important and I see no problem hiding that
behind an upstream or a legitimate false front, but the NOC and ABUSE PoC's
need to terminate somewhere that is one degree of separation from someone
who can actually do something.

The TECH, NOC and ABUSE PoC's are often most appropriately not even in the
same organization as the Admin PoC.  I have many customers who outsource
their network operations, either to me or another third party.  That
outsource would be much more appropriate as a TECH/NOC/ABUSE PoC than the
poor customer who has no idea what an IP address is.
[Chu, Yi [NTK]] For that matter, one can think of the upstream ISP as the entity being 'outsourced' to.  In most cases, ISP's are responsible and managing on behalf of the customer anyway.


> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of Chris Engel
> Sent: Wednesday, August 08, 2012 9:36 AM
> To: 'patrick at klos.com'; arin-ppml at arin.net
> Subject: Re: [arin-ppml] private whois record
> >
> > It's not about who wants to receive (or not receive) sales calls?  It's
> > about who you trust your organization's network to?  It's about who you
> > trust to receive and handle the first notice that your network is either
> > having troubles or causing troubles, or that a server on your network
> has
> > been compromised and is causing damage to someone else.  Who do you
> > think
> > should be in that position?
> >
> > Patrick
> You don't need the first point of contact to be a highly paid and highly
> trained engineer. It doesn't take much technical training to differentiate
> between a sales call and someone who is experiencing serious disruption
> coming from your network.  It's pretty much the same deal with calling
> your doctors office outside of normal hours. The first person to pick up
> the phone isn't the doctor or even an RN. It's an answering service
> operator, that's because you don't need much training to do some very
> basic screening and categorization of the call....  and what a Doctor is
> responsible for is a heck of alot more important then an  average endpoint
> network admin.  The only thing that really matters is that for a genuine
> problem, you get a timely response from someone who can act on it. Needing
> to speak to an answering service or CSR first to determine that you aren't
> just some guy trying to sell routers,  isn't too much to ask in exchange
> for a publically published contact that is !
> !a ctively monitored.  YMMV.
> Christopher Engel
> _______________________________________________
> 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 may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

More information about the ARIN-PPML mailing list