ARIN Fraud Reporting Form ... Don't waste your time

I apologize if I was unclear.

I stated in my first message regarding the possibility that RIRs could delegate abandoned/hijacked space to provide reverse DNS answers - "This is something that ARIN *could* easily do technically. Admittedly, this would require reporting and investigation that I am uncertain whether or not ARIN is empowered/funded to do. This would also require a process be put in place for removing allocations from the delegation to the unused/abandoned reverse DNS servers... " The word 'could' was chosen by me instead of the word 'should' for a reason.

In my second message on this topic I in fact quoted the parts of ARIN's Number Resource Policy Manual regarding POC and reverse DNS delegation validation / removal.

I am well aware of ARIN's policies and the process for changing them.

To be clear, my point is merely that RIRs do not make address allocations and then walk away with no day to day involvement with these addresses on some technical level. To reiterate:
"The RIR's reverse DNS servers are queried all day every day for the reverse DNS delegations for every netblock that they allocate. This means that RIRs are, in at least this way, actively operationally involved in the use of the allocations that they make. This also means that an RIR has the technical vector to affect the active present use of the allocations that they have made in the past."

This was meant in no way to criticize RIRs (or any RIR in particular) or proscribe actions that I believe RIRs should take. This was meant to correct anyone that incorrectly states that RIRs allocate addresses and then walk away or do nothing but maintain whois records.

Reverse DNS delegation is a technical vector that could be used by RIRs to affect the active present use of the allocations that they have made in the past. I understand that reverse DNS would not affect route announcements/hijacks, but it would/could/might affect spam coming from these abandoned address spaces - which was the original topic for this discussion.

I agree that little/nothing is proscribed for RIRs at a policy level. The policies and procedures regarding this could be written. I agree that these policies and procedures do not exist now.

-DM

From: Ricky Beam
Sent: Friday, October 01, 2010 1:00 PM
To: nanog@nanog.org
Subject: Re: ARIN Fraud Reporting Form ... Don't waste your time

> It's not so much a matter of whether ARIN cares or whether ARIN

wants

> to do something about your issue. It's more a matter of whether ARIN
> is empowered to do anything at all about your issue.

EXACTLY.

Ron, what exactly do you expect ARIN to do? Where is the magic wand
one
would wave to erase routes from the internet? ARIN (in fact NO ONE)
has
no actual means to block or recend any route announcement. Do you
suggest
they sue whomever is involved? That won't be very fast, or even an
option
outside the US.

The problem as I see it is that ARIN is responsible for issuing number
resources but is not responsible for any maintenance of the number
space. It seems they have no requirement/method/need to revoke
assignments once the assigned entity no longer exists. I am not looking
for perfection but there should be some sort of diligence requirement
that the most obvious of the low hanging fruit (or fruit that falls
right off the tree into their lap) be dealt with in some way. If an
entity liquidates, then their resources should be reclaimed.

How many entities does ARIN have who have not made a payment for 2 or
more consecutive years but still have resources assigned? It is my
personal opinion that ARIN (and the other registrars) must have the
authority and the mechanism to reclaim community resources when the
entity they were issued to disappears. That seems like a fairly easy
concept. Note I am not talking about misuse here, just the fact that if
a community resource is issued to an entity and that entity no longer
exists, those resources should be reclaimed by the community within some
reasonable amount of time.

G

The problem as I see it is that ARIN is responsible for issuing number
resources but is not responsible for any maintenance of the number
space. It seems they have no requirement/method/need to revoke
assignments once the assigned entity no longer exists. I am not looking
for perfection but there should be some sort of diligence requirement
that the most obvious of the low hanging fruit (or fruit that falls
right off the tree into their lap) be dealt with in some way. If an
entity liquidates, then their resources should be reclaimed.

Resources being used by actual defunct organizations we will reclaim if reported.

How many entities does ARIN have who have not made a payment for 2 or
more consecutive years but still have resources assigned? It is my
personal opinion that ARIN (and the other registrars) must have the
authority and the mechanism to reclaim community resources when the
entity they were issued to disappears.

We already do this type of reclamation.

That seems like a fairly easy
concept. Note I am not talking about misuse here, just the fact that if
a community resource is issued to an entity and that entity no longer
exists, those resources should be reclaimed by the community within some
reasonable amount of time

Agreed,
/John

John Curran
President and CEO
ARIN

Folks -

It occurred to me that I could have been clearer, so here I am replying
to myself...

When we at ARIN can readily determine that an organization is defunct
and has no apparent successor, we will reclaim resources. This generally
happens because someone attempts a fraudulent transfer of those resources
but can also be a result of other investigations.

We give a report of returned, revoked, and reclaimed number resources at
each member meeting - last April's report can be found here:
https://www.arin.net/participate/meetings/reports/ARIN_XXV/PDF/Wednesday/Nobile_RSD.pdf

Obviously, we'll be presenting updated statistics this upcoming week in
Atlanta; there's been a bit of a surge of activity in this area.

/John

John Curran
President and CEO
ARIN

Thanks John,

Resources being used by actual defunct organizations we will reclaim if reported.

Folks -

It occurred to me that I could have been clearer, so here I am replying
to myself...

When we at ARIN can readily determine that an organization is defunct
and has no apparent successor, we will reclaim resources. This generally
happens because someone attempts a fraudulent transfer of those resources
but can also be a result of other investigations.

We give a report of returned, revoked, and reclaimed number resources at
each member meeting - last April's report can be found here:
https://www.arin.net/participate/meetings/reports/ARIN_XXV/PDF/Wednesday/Nobile_RSD.pdf

Is the information on Leslie's slide 5 at the above link available broken down by year? It might be informative to see any trends.

Thanks again,
John Springer

From: Ricky Beam
Sent: Friday, October 01, 2010 1:00 PM
To: nanog@nanog.org
Subject: Re: ARIN Fraud Reporting Form ... Don't waste your time

It's not so much a matter of whether ARIN cares or whether ARIN

wants

to do something about your issue. It's more a matter of whether ARIN
is empowered to do anything at all about your issue.

EXACTLY.

Ron, what exactly do you expect ARIN to do? Where is the magic wand
one
would wave to erase routes from the internet? ARIN (in fact NO ONE)
has
no actual means to block or recend any route announcement. Do you
suggest
they sue whomever is involved? That won't be very fast, or even an
option
outside the US.

The problem as I see it is that ARIN is responsible for issuing number
resources but is not responsible for any maintenance of the number
space. It seems they have no requirement/method/need to revoke
assignments once the assigned entity no longer exists. I am not looking

They do, indeed, for space that is/was issued by ARIN. That space is
subject to annual fees and there is a clear and consistent method
for doing so. The bigger problem is with legacy space (most of the
space listed in the complaint we are discussing, if not all).

In the case of legacy space, it's actually very hard for ARIN to even
identify the status of the organization in question, let alone take
any sort of action with respect to said space.

for perfection but there should be some sort of diligence requirement
that the most obvious of the low hanging fruit (or fruit that falls
right off the tree into their lap) be dealt with in some way. If an
entity liquidates, then their resources should be reclaimed.

Again, for space issued by ARIN, yes. For legacy space, this is a much
more complicated problem.

The good news is that this is limited to IPv4. Since there are no Pre-RIR
IPv6 allocations or assignments, it is a non-issue in IPv6.

How many entities does ARIN have who have not made a payment for 2 or
more consecutive years but still have resources assigned? It is my

I suspect not many. (Unless you are including those organizations
that do not pay fees because of their legacy status).

Owen

A yearly challenge response for legacy space contacts, could be useful. I think there is a plan like this in some RIRs

In message <608B18DB-6E75-4B5E-BA42-D1F69ECE4881@arin.net>,
John Curran wrote:

You note the following:

They could say, to everyone involved, and to the community as a whole,
``This ain't right. *We* maintain the official allocation records.
In most cases, *we* made the allocations, and that guy should NOT be
announcing routes to that IP space, and he shouldn't be announcing
anything at all via that AS number, because these things ain't his.''

At present, ARIN doesn't review the routing of address space to see
if an allocation made to party is being announced by another party.
From your emails, I'm guess that you'd like ARIN to do so.

John,

First, let me say thanks for your personal response.

Second let me also say that I am pleased to know, at least, that my serious
efforts to express myself clearly were not lost on everyone. You have
grasped my meaning clearly. (But not everyone here has done likewise.)

I've run several several ISPs and a hosting firm, and I'm not quite
sure how ARIN can definitively know that any of the AS#'s involved
should or should not be routing a given network block.

Please allow me to attempt to refute what you just said. I think that
I can do so, briefly, in (at least) two different ways.

1) You folks _are_ already (apparently) making some efforts... at least
as of this last summer, but perhaps also earlier... to ``validate'' (is
that the word you would use?) POC contacts. I know because I've lately
seen quite a number of your POC contact records (from the WHOIS data base)
that have a very helpful annotation attached to them, saying quite
directly and explicitly, that ARIN has been unable to verify or make
contact with this POC or that POC. So you are already passing judgement
on the validity and/or probable invalidity of things in your data base.
And more, you are making your determinations public, via the data base
itself. I'm not quite sure how it constitutes such a big leap to merely
extend what you are already doing in the way of validating POCs and just
impute the exact same level of confidence, or lack thereof, to IP block
and/or AS records which are associated with unverifiable/uncontactable
POCs... a set which you are already making serious efforts to delineate
anyway. If you can put an annotation into a whois records for a POC,
saying explicity that you can't get ahold of this person, then it would
seem to me to be a rather trivial matter of programming to transplant
a very similar sort of annotation into each and every IP block or AS
record that has that same specific POC record as one of its associated
POC records, either Admin, or Technical, or whatever.

You could just say, you know, something like ``We have been tring to contact
the Technical POC for this since XX-XX-2010, and we've been unable to do so.''
Well, not those words exactly, but I hope you get the general idea. Just
take the determinations that you folks are _already_ making, for the POC
records, and just impute them to, and include them in, also, to the
relevant block and/or AS records. Or alternatively, you could stop using
verbage altogether and just switch over to a system based on simple,
universally understood icons:



Now, you may perhaps be tempted to quibble with my point here, and repeat
again what you said above, I.e. that ARIN cannot make ``definitive''
determinations. Please don't yield to any such temptation. Quite
frankly, to the best of my knowledge, no living human can reliably make
any truly ``definitive'' determinations about anything at all. Only God
can do that. (And frankly, I harbor lingering suspicions that even He
gets it wrong a fair percentage of the time.)

Nobody expects you to have the infallibility of God... or even of the
Pope. And nobody is asking you to display such a level of infinite
perfection, least of all me. But ya know, even in the abundant absence
of certainty in our day-to-day lives, we all still drag ourselves out
of bed in the morning and do the best that we can. And that's all that
either I or anybody else has any right to ask of you/ARIN or to expect
of you/ARIN. Just do the best you can. Are your deteminations that
this POC or that POC cannot be contacted, or cannot currently be verified
``definitive''? No, that's probably too stong a word. But you/ARIN have
the good sense and the courtesy to publish the information you have gathered
regarding the contactability of POCs anyway, and it's appreciated. It helps.
Please just do more of it. This is not an all-or-nothing ``We can't say
anything definitively so we can't say anything at all, ever'' kind of
situation, I think.

2) You are already (apparently) processing _some_ certain flavors of
``fraud reports'' that come in to you via that nice fancy web form you
folks built and put up on the ARIN web site... you know... the one with
the nice (and misleading) introduction that entices people like me to
take the time to use it enter reports about incidents that have traditionally
been called around these parts ``hijacking''.

(Note: That's the word that _you_ used on your web site to say what
should be reported via the form. Was I a fool to take you at your word?
Let me be clear... I am *not* *not* *not* encouraging you to simply
redact/delete that word from your web site. No no! Rather I hope to
encourage you/ARIN to actually accept and at least investigate reports
of _all_ flavors of what we around here used to call good old fashioned
``hijacking'', regardless of whether the perp was gracious enough to
also make your choice clearer by dicking with the relevant WHOIS records
or not.)

So anyway, you are already, obviously, geared up to do ``investigations''.
And you _are_ already doing them. Yes? And you are not doing these
investigatons just for your health, as the saying goes, correct? I mean
you have a goal when you do these investigations... an end goal. Right?
And what is that goal? What comes out the other end when you feed the
raw facts into the top of this process and then turn the crank? What do
you have at the end of the day, eh? Do you have a... ahhh.. conclusion?
Might one even say that at the end of the process, ARIN reaches a
``determination''? Would you characterize these determinations... which
you obviously use as a basis for further action... as ``definitive
detrminations''? (If not, why not? And if you use these determinations
as a basis for further action, and yet you claim that they are not actually
``defininite determinations'', then aren't you placing ARIN at great risk
of a lawsuit by so doing?)

I think you can see where I'm going with this. You have, I think, tried to
demur (is that the right word?) on ARIN's behalf, from _either_ investigating
or, subsequently, from issuing any kind of ``determination'' as regards to
whether a given block is being routed by the party or parties who ought to
be routing it, or by some uninvited interloper. And you have done so on
that basis of your very reasonable sounding claim that ARIN cannot make
``definitive'' determinations about such things. I would argue that this
claim simply does not wash for two reasons:

    1) ARIN is _already_, apparently, conducting investigations and thence
  making ``definitive'' determinations, presumably on a routine and
  ongoing basis, about things relating to the allocations that it,
  and it alone, is the official Keeper of Records for. And ARIN
  is already doing this, even in the absence of God-like certainty
  about the conclusions it reaches, and which it subsequently uses
  as a basis for further action.

    2) If you (ARIN) claim to be utterly unable to make definitive determina-
  tions about what blocks belong to who, or who should be routing what,
  then (a) what exactly are we paying you for?? ... just kidding... *I*
  am not personally paying you... but more importantly (b) if even
  *you guys* cannot make definitive determinations about these things,
  then God help the rest of us! Because we mere mortals out here have
  a lot less data, knowledge, expertise, and experience than you ARIN
  folks have, and if you folks say you can't ``definitively'' figure
  out what belongs to who, then it sounds from where I'm sitting like
  you're saying that things inside of ARIN are just as bad as they were
  inside AIG the day _it_ went belly up... papers scattered all over
  the floors, and nobody even knows what all they actually own.

  Do I think that this is what you are trying to tell me? No. Do I
  even for a moment imagine that the inside of your shop... ARIN...
  is a confused and tangled mess like AIG was in its last days? No.
  No way. Not at all. Quiet the opposite. I think you folks... as
  the official Keepers of the Records... can... and apparently _do_
  routinely make ``definitive'' determinations about the proper
  interpretation of the records that you yourselves keep.

  I'd just like to see you get on with it.

  Just saying that you can't ever know anything, definitively, because
  you're not God, is not a compelling argument to support the view
  that you should never do anything, or say anything, because you are
  not omniscient. None of us are. But we still get up in the morning
  and go to work. One does one's best, and leave the rest to history.

There are
some heuristics that will suggest something is "fishy" about use of
a network block...

SOME??? Try a lot. (I'll be more than happy to share with you folks anything
and everything that I, bloodhound-like, manage to gleen. All I ask is that
you at least accept it... which the response I received earlier seemed to
indicate that you were not even willing to do. The teeny little one-inch
by two-inch data entry window you have on your fraud reporting form doesn't
help much either, and is very off-putting in a way that makes it seem like
it was intended to be that way.)

but are you actually suggesting that ARIN would
revoke resources as a result of that?

Did I say that?

Again, I have tried to be clear, but in this case it seems that I may have
failed. No, I *do not* expect ARIN to go out, guns drawn, and start choping
people's wires. No, I *do not* expect ARIN do do whatever might be
implied by this terminology you are using now, which is entirely foreign
to me. I have no real idea what sorts of hot-pokers-up-the-backside you
may be implying by your use of this terminology "revoke resources", but
whatever it means, it certainly sounds terribly ominous and foreboding,
and rather like something that I wouldn't wish on my worst enemy...
especially given the context and the way you phrased your question.

So no, please *do not* go around ``revoking resources''... whatever the hell
that means. Certainly, if some half-dead, left-for-dead dot-bomb company
has a /18, and if your records still say that they have a /18, then they still
have a /18. Period. And if then, some hijacker punk criminal comes along
and starts routing that /18... well... he's a shmuck, and ought to be dealt
with. But the old Dot-Bomb semi-defunct company still does ``own'' (please
excuse my use of that terminology, which I'm sure you won't approve) that
block. So you shouldn't be ``revoking'' anything. That's not what any of
this is about.

All I want from ARIN, and all I expect from ARIN, in cases like these are
(a) at least some willingness and effort expended to investigate and (2)
at least *some sort* of (perhaps minimalist) public statement to the effect
of ``Look folks, we've looked at this, and in our opinion, what's going on
here just doesn't look kosher.''

I would be satisfied if that ``minimalist public statement'' would be in
the form of a discrete little annotation within the relevant WHOIS record(s)...
you know... rather like what you folks are _already_ attaching to POC records,
only maybe worded a little stronger than that, when you can see some really
clear hanky panky going on... as in the cases I have publicised here recently.

Of course, that said, that's kind-of my minimum request. If it were entirely
up to me, you guys would call a big press conference, with CNN, MSNBC (and
of course, Comedy Central, BUT NOT FIXED NEWS!) every time you caught another
one of these fly-by-night hijacker jokers red-handed... as it would appear I
just have, in at least two of the cases I've reported on. (I infer that, with
a high level of certainty, from the fact that these nitwits already stopped
announcing routes to the space they had so obviously stolen. If it was
really your's in the first place, then you wouldn't just give it back the
minute somebody yelled ``thief'', now would you?) And after the press
conference, everyone would be invited to come out by the pool for free beer
and sandwiches, and a good time would be had by all, as we collectively
burned the hijacker in effigy. But you know, I'm not really expecting all
of that, so just however much of it you can manage to put together would be
just fine by me. (Hell! I'll even volunteer to spring for, and bring, the
beer and the sandwiches. Did I mention I was from California? I guess it's
kind-of obvious now, huh?)

So anyway, have I managed, successfully, to make my desires more clear and
apparent now? I hope so. No, I neither want nor expect ARIN to be pulling
plugs out of sockets, or to be diddling the global routing table, or to be
``revoking'' anything... least of all any allocations previously made to
some perfectly legit company who, through only the minor sin of inattention,
got their stuff hijacked out from under them. Revoking _their_ right-to-use
would simply be adding insult to injury. Don't you agree? I'd just like
to see investigations and some form of public statement(s) at the ends of
those. And I won't even mind if you have corporate counsel water down
the public statement so much that it ends up looking like the verbal
equivalent of barely raising an eyebrow. I do understand that ARIN, like
the rest of us, has to somehow survive and get by in this litigous environ-
ment. So I don't even care what the public statements say, or even what
subtle or un-subtle forms they take. Just so long as it is understood,
within the community, that (wink wink nod nod) whenever ARIN says that
``Some evidence suggests that the routing for this block may be non-normative,
as per Paragraph B, Subsection F, of the Addendum to the Bylaws of the
Regulations, updated, (c)1947, (c)1972, revised Sept 27th, 2007, with
respect to E.12 in sum and overview, as pertaining to all parts or to
the sum of the parts, together, when viewed as a unit.'' we all know and
understand that this really means ``hijacked''. (Ask your corporate
counsel. I'm sure that he'll be able to suggest some equally obscure and
convoluted way of saying ``hijacked'' without ever actually using that
word itself. That's what they are best at, after all... making simple
English statements utterly imponderable.[1]) Whatever doesn't get you sued
is fine by me. As long as you investigate and then say _something_ about
these kinds of cases.

In those rare
cases where the perp is considerate enough to ALSO fiddle the relevant
WHOIS records in some fradulent way, THEN (apparently) ARIN will get
involved, but only to the extent of re-jiggering the WHOIS record(s).
Once that's been done, they will happily leave the perp to announce
all of the fradulent routes and hijacked space he wants, in perpetuity.

Correct. We will revoke the address space, but I'm uncertain what else
you suggest we do... could you elaborate here?

See above.

Investigate. Then somehow... in watered-down words, and burried in the
WHOIS records, if necessary... tell us what you found out.

As I've said, I really don't think I'm asking for much.

And I'll say again too, you guys are the Keepers of the Records. If even
you guys can't say what they mean or how that meaning might or might not
comport with current existing objective reality (as known to us all via
looking glass servers) they God help us all! Because in that case, I think
we are REALLY screwed, and nobody knows anything, and the next stop is
canibalism.

Regards,
rfg

P.S. I meant to also inquire about those POC unable-to-contact annotations.
What should be infered frm those, exactly? Could you please enumerate the
ways in which your staff try (and sometimes, apparently, fail) to make
contact with these POCs? Is it all sytrictly done via e-mail? Do your
people ever try to _telephone_ any of these folks at the numbers you force
them to give ou as part of establishing a POC record in the first place?
Do your people ever try contacting the POCs via snail-mail?

I hope you see where I'm headed. If some poor fool with too much time on
his hands... you know... like me... submits something via your fraud reporting
form... I mean... you know...after you fix it so that the amount of info
that can be sent to you folks via the form is somewhat bigger than this:

http://www.active-robots.com/products/intelligent-displays/lcd/16x2lcd-750.jpg

...then my hope is that you would *not* just ``investigate'' by sending off
an e-mail to the purported POC e-mail address, and then waiting a week to
see if anything comes back. There's this wonderful new invention... you
may have heard of it, although in my experience, an awful lot of Internet
geeks refuse to use it. Why, I don't really know. Actually, here is a rare
photo of a geek actually using one:

   http://farm1.static.flickr.com/5/5040260_a2c426a753.jpg

So, you know, if you get a hijacking report, maybe, just maybe, could you
please, please, please pick up the phone and make a call and just even try
to see if the POC is alive or dead?

   http://farm4.static.flickr.com/3433/3176717757_20515698bf.jpg

Maybe this is a teachable moment for me. According to my reading of the
Legacy RSA:

" For purposes of this Legacy Agreement, the term "Services" may
include, without limitation, the inclusion of the legacy IP address
space, and/or Autonomous System numbers ("ASNs") previously issued to
Legacy Applicant in the ARIN "WHOIS" database, inverse addressing on
network blocks, maintenance of resource records, and administration of
IP address space related to Included Number Resources issued prior to
ARIN's inception on December 22, 1997 in its service area. IP address
space and ASNs shall be defined as "number resources." "

...

" If Legacy Applicant does not pay the Annual Legacy Maintenance Fee or
other fees that may be owed ARIN hereunder, ARIN shall provide written
notification to the Legacy Applicant approximately thirty (30) days
following the date on which the payment is not made. If Legacy Applicant
fails to make payment in response to the notice of delinquency, ARIN
shall provide Legacy Applicant with an additional written notice, by
certified or registered mail, return receipt requested, (as appropriate
in each country), and, when possible, by e-mail and telephone. If the
Legacy Applicant has not made payment within 12 months of the due date
and/or ARIN is unable to contact the Legacy Applicant during those 12
months, ARIN has the right to: (i) stop providing Services, or (ii)
terminate this Legacy Agreement and revoke the Included Number
Resources."

Or is this some other sort of "legacy" thing?

I refer you to NRPM section 12 and the current draft policy 2010-11 Required Resource Reviews.

Owen

They do, indeed, for space that is/was issued by ARIN. That space is
subject to annual fees and there is a clear and consistent method
for doing so. The bigger problem is with legacy space (most of the
space listed in the complaint we are discussing, if not all).

In the case of legacy space, it's actually very hard for ARIN to even
identify the status of the organization in question, let alone take
any sort of action with respect to said space.

Ok, I think I have a solution that is workable. A second database ...
call it "whoisnt" ... of number resources and their points of contact
that have not signed the legacy RSA and allow the community members to
decide individually if they wish to continue to provide unfettered
access from those resources. It might also provide maybe even some
small amount of community pressure on the holders of those resources to
place them under the legacy RSA.

In message <67EF8EE2-8B1E-45F9-892E-9E6B88ADB727@arin.net>,

Resources being used by actual defunct organizations we will reclaim if
reported.

Well, fortunately, Joytel and some of their fellow travelers have just
recently gone 'round and identified a whole pantload of these for you:

24.230.0.0/19 NET-24-230-0-0-1 hijacked - empty
68.67.64.0/20 NET-68-67-64-0-1 legit -- GoRack, LLC (Jacksonville, FL)
192.100.5.0/24 NET-192-100-5-0-1 hijacked - empty
192.100.88.0/24 NET-192-100-88-0-1 hijacked - empty
192.100.134.0/24 NET-192-100-134-0-1 hijacked - empty
192.100.143.0/24 NET-192-100-143-0-1 hijacked - empty
192.101.177.0/24 NET-192-101-177-0-1 hijacked - empty
192.101.187.0/24 NET-192-101-187-0-1 hijacked - empty
...

Do you want me to repost the whole list, or have you seen it already?

Do I need to do something else to turn this into whatever qualifies at
your place as a formal report? (Note: The whole list is too long to
fit into the tiny little window you provide for fraud reporting on your
web site. Should I print it all out as hardcopy and FedEx it to you
in a shoebox?)

Regards,
rfg

In message <5A6D953473350C4B9995546AFE9939EE0A52B07A@RWC-EX1.corp.seven.com>,

So ARIN is in the process of verifying their contacts database.
Organizations with an unreachable contact might be a good place to plant
a "dig here" sign.

Fyi --

They (ARIN) already _are_ putting up ``dig here'' signs... in the POC records.

Unfortunately, it would now appear that the folks doing the digging in those
exact spots, are the hijackers, like Joytel. (Unless I'm mistaken, every
last one of the blocks that Joytel grabbed had one of those little annotations
on the associated POC record(s)).

Talk about the Law of Unintended Conseqences!

Oh well. It all comes out in the wash. Those POC annotations may perhaps
have helped Joytel to identify easy takeover targets, but then they also
helped _me_ to find the specific blocks that Joytel had jacked.

On balance, I say it is better to have them than to not have them. Even
if they might occasionally give those with sinister intent a small leg up.

Regards,
rfg

P.S. I hope that everybody knows that the jerk behind Joytel also, apparently,
tried to screw the taxpayers out of about $11+ million of ``stimulus'' money...
undoubtedly for yet another useless make-work ``shovel ready'' project.

http://jacksonville.bizjournals.com/jacksonville/stories/2009/11/30/story1.html#

No word on whether he ever actually got his hoped-for $11.8 million payoff.
Knowing how ga-ga the Obama administration is over anything that has the
word ``broadband'' in it however, I wouldn't put it past them, and they
probably did give this schmuck the cash. (They also really like the words
``young entrepreneur''. Sounds great to the unwashed masses in a press
release.)

      If companies want to move here, they have a great labor force, great
      quality of life and affordable office space, said Mark Anthony Marques,
      Joytel president and CEO. What we lack is a good enough connection to
      the Internet infrastructure.

      The company expects to know by mid-December whether it will receive
      funding for the project, which has the support of key players including
      Mayor John Peyton, U.S. Sen. Bill Nelson and U.S. Reps. Corrine Brown
      and Ander Crenshaw.

      About 400 gigabytes of high-speed Internet capacity will be available
      to providers by mid-2010 if funding is received. That is enough capacity
      to transfer the entire contents of the Library of Congress within five
      minutes.

... or alternatively, to spam every person on the planet, twice, in under
twenty minutes.

1) You folks _are_ already (apparently) making some efforts... at least
as of this last summer, but perhaps also earlier... to ``validate'' (is
that the word you would use?) POC contacts. I know because I've lately
seen quite a number of your POC contact records (from the WHOIS data base)
that have a very helpful annotation attached to them, saying quite
directly and explicitly, that ARIN has been unable to verify or make
contact with this POC or that POC. So you are already passing judgement
on the validity and/or probable invalidity of things in your data base.

Yes, we're attempting to validate contacts per the policy which the
community set (ARIN Network Resource Policy Manual, section 3.6 -
https://www.arin.net/participate/policy/nrpm/)

And more, you are making your determinations public, via the data base
itself. I'm not quite sure how it constitutes such a big leap to merely
extend what you are already doing in the way of validating POCs and just
impute the exact same level of confidence, or lack thereof, to IP block
and/or AS records which are associated with unverifiable/uncontactable
POCs... a set which you are already making serious efforts to delineate
anyway.

We will shortly be providing a "list of number resources with no valid POC"
for those who desire it (per the current bulk Whois policy.)

If you can put an annotation into a whois records for a POC,
saying explicity that you can't get ahold of this person, then it would
seem to me to be a rather trivial matter of programming to transplant
a very similar sort of annotation into each and every IP block or AS
record that has that same specific POC record as one of its associated
POC records, either Admin, or Technical, or whatever.

Also a nice idea, and one that I've taken as a formal suggestion for
improvement.

...

2) You are already (apparently) processing _some_ certain flavors of
``fraud reports'' that come in to you via that nice fancy web form you
folks built and put up on the ARIN web site... you know... the one with
the nice (and misleading) introduction that entices people like me to
take the time to use it enter reports about incidents that have traditionally
been called around these parts ``hijacking''.

(Note: That's the word that _you_ used on your web site to say what
should be reported via the form. Was I a fool to take you at your word?
Let me be clear... I am *not* *not* *not* encouraging you to simply
redact/delete that word from your web site. No no! Rather I hope to
encourage you/ARIN to actually accept and at least investigate reports
of _all_ flavors of what we around here used to call good old fashioned
``hijacking'', regardless of whether the perp was gracious enough to
also make your choice clearer by dicking with the relevant WHOIS records
or not.)

Your understanding of our fraud process is correct, and presently the only
form of "hijacking" which we have the ability to correct is address blocks
where the organization have been changed contrary to policy. To address
your follow-on question, our determinations are indeed definitive and we
correct the WHOIS database accordingly.

I think you can see where I'm going with this. You have, I think, tried to
demur (is that the right word?) on ARIN's behalf, from _either_ investigating
or, subsequently, from issuing any kind of ``determination'' as regards to
whether a given block is being routed by the party or parties who ought to
be routing it, or by some uninvited interloper.

Incorrect. We determine whether an entry for an address block in WHOIS has
been changed contrary to community-adopted policy. This means carefully
reviewing the information supplied on the associated change requests and
various corresponding public records. *None of it related to whether a
given party should be routing a given address block*

...
So no, please *do not* go around ``revoking resources''... whatever the hell
that means. Certainly, if some half-dead, left-for-dead dot-bomb company
has a /18, and if your records still say that they have a /18, then they still
have a /18. Period. And if then, some hijacker punk criminal comes along
and starts routing that /18... well... he's a shmuck, and ought to be dealt
with. But the old Dot-Bomb semi-defunct company still does ``own'' (please
excuse my use of that terminology, which I'm sure you won't approve) that
block. So you shouldn't be ``revoking'' anything. That's not what any of
this is about.

Semi-defunct firms may hold address blocks, but address blocks assigned to
fully defunct organizations are returned to the free pool per community
policy.

All I want from ARIN, and all I expect from ARIN, in cases like these are
(a) at least some willingness and effort expended to investigate and (2)
at least *some sort* of (perhaps minimalist) public statement to the effect
of ``Look folks, we've looked at this, and in our opinion, what's going on
here just doesn't look kosher.''

The good news is that if you're referring to investigation of errant entries
in WHOIS, we currently do expend effort to investigate and correct. In order
for ARIN to investigate and annotate address blocks according to their state
in the routing tables, it would take a very clear mandate from the community.
You can suggest such a policy if you feel strongly about this; the process to
to so is shown here: https://www.arin.net/participate/policy/pdp/appendix_b/

/John

John Curran
President and CEO
ARIN

We will shortly be providing a "list of number resources with no valid
POC"
for those who desire it (per the current bulk Whois policy.)

> If you can put an annotation into a whois records for a POC,
> saying explicity that you can't get ahold of this person, then it
would
> seem to me to be a rather trivial matter of programming to

transplant

> a very similar sort of annotation into each and every IP block or AS
> record that has that same specific POC record as one of its
associated
> POC records, either Admin, or Technical, or whatever.

Also a nice idea, and one that I've taken as a formal suggestion for
improvement.

Those two things would be enough for me for the numbers covered by
agreement, the legacy issue is a tougher nut. There should be some sort
of requirement that any network being announced have a valid point of
contact. Whose jurisdiction that would fall under for a global Internet
beats me.

John,

Let me thank you yet again for devoting your personal time (on a Friday
night no less) to responding to me concerns. I may not always agree with
you, but I appreciate the effort, and the consideration.

In message <4DB05053-FCD4-4459-B226-991435E90C65@arin.net>,

We will shortly be providing a "list of number resources with no valid POC"
for those who desire it (per the current bulk Whois policy.)

But I think you understand that I was suggesting something that's readily
accessible, even to the Great Unwashed Masses, within the individual
WHOIS records... not exclusive to just your ordained bulk whois clientel.

You did get that, right?

If you can put an annotation into a whois records for a POC,
saying explicity that you can't get ahold of this person, then it would
seem to me to be a rather trivial matter of programming to transplant
a very similar sort of annotation into each and every IP block or AS
record that has that same specific POC record as one of its associated
POC records, either Admin, or Technical, or whatever.

Also a nice idea, and one that I've taken as a formal suggestion for
improvement.

Thank you.

Your understanding of our fraud process is correct, and presently the only
form of "hijacking" which we have the ability to correct...

Well, now, as Ronald Regan used to say ``There you go again!''

I've tried to be clear. I'll try again.

Many many many people have told me, off-list, and even before this conver-
sation, that you folks can't change the routing table, and that even if
you could, most probably would never want you to exercise that authority.
So I do fully understand where the weight of public opinion falls along that
particular axis. Believe me, I do.

But please do try to understand me. I was not asking you to ``correct''
any hijacking incident. You can't. So let's just agree on that, and
also agree that that is not what we are even talking about.

What I said was ``annotate'' and/or ``announce'' and/or ``make _some_
sort of public statement or comment''. This, I think, would not be
straying so substantially outside of your charter than anybody would
ever beat you up over it, especially if you folks exercised the kind
of caution and careful investigation which I believe you are more than
capable of, and if you thence only made public ``This is really fishy
looking'' type comments when your internal investigations have shown that
yes, indeed, this one really looks, smells, and tastes pretty darn awful.
(And frankly, I think this would apply to all four of the cases I have
written about here recently.)

So have I been unambiguously clear now? I neither want nor expect you
to ``correct'' anything. That sort of thing, I would agree, is not
your job. But I don't think that fact implies that either you personally,
or ARIN as an organization have any kind of formal responsibility to
behave as blind deaf mutes with no opinions whatsoever, at any time, about
anything.

Some people would tell you that its a free country, and that you have
a right to an opinion. I guess what I'm saying is that when it comes to
ARIN, and allegations of hijacking of number resources that you have
been chartered to administer, you have not merely a right, but actually
a _responsibility_ to an opinion. And you should formulate it, and state
it, publically, when the need arises, which is to say whenever you receive
a credible allegation of the misappropriation of number resources that
lie within your portfolio.

I think you can see where I'm going with this. You have, I think, tried to
demur (is that the right word?) on ARIN's behalf, from _either_ investigating
or, subsequently, from issuing any kind of ``determination'' as regards to
whether a given block is being routed by the party or parties who ought to
be routing it, or by some uninvited interloper.

Incorrect. We determine whether an entry for an address block in WHOIS has
been changed contrary to community-adopted policy. This means carefully
reviewing the information supplied on the associated change requests and
various corresponding public records. *None of it related to whether a
given party should be routing a given address block*

Right. You may perhaps not have realized it, but I do believe that you
actually just _agreed_ completely with what I said just above. At present,
you decline to even look at things that don't involve the fiddling of WHOIS
records. Somebody could be murdered in the next room, and you would decline
to investigate that too, because the community hasn't explicitly chartered
you to do that.

I understand your position, and I think I may even understand what motivates
it... like maybe years and years of having your own constituency beat you
about the head and neck whenever you try to do even the smallest, kindest,
and most generous and well-meaning things if they... the herd of cats...
haven't explicity approved of you doing it, themselves, in writing, and
in triplicate.

But to say I understand your position, and to say that I can even under-
stand what I believe motivates it, is not to say that I agree with it.

I don't in this case. I think you are perhaps not in quite such a tightly
fitting straight-jacket... created for you by your primary constiuency,
the ISPs... as you make out, and that you do actually have some freedom
to Do The Right Thing, especially in cases like these blatant hijacking
incidents. But I also believe that you have made a private personal and
concious decision not to touch any of this with a ten foot pole, because
years of surviving in the kind of highly politically contentious job you
have has taught you to never stick your neck out, even a little bit, even
for an unambiguously good cause, unless what you plan to do or say (or
what you plan to eat for lunch, or when you plan to breath) has already
been approved, in triplicate, by the whole of the ARIN membership. I'm
quite sure that that is the only practical and viable way to survive,
long term, in a highly political job like your's. However I am equally
sure that it is unhealthy for any human being to live in a straight-jacket
for years at time, with no let-up.

So despite you protestations to the contrary, I will say again that I
think you have not only a right, but a responsibility to express an opinion
on matters critically affecting the number resources that you are tasked to
shepard... matters such as blatant hijacking of those resources by crooks...
and that the same goes for ARIN, as an organization, and that furthermore,
you do a disservice to the community, to your office, and yes, even to
yourself as an intelligent, concious, living, growing human being when you
hold your tongue on important matters simply because you have not been
officially and formally bidden to speak.

And you _don't_ always do that, consistantly and always, anyway.

In fact right now, within this very exchange you and I have been having,
you have expressed yourself in ways that, I feel sure, were not explicitly
or specifically sanctioned by your board or your membership, yes? But you
have shown yourself to be fully fit and able to express these opinions of
your's anyway, as part of your reasonable exercise of your executive
discretion, in your pursuit of what you believe to be the community's
best interests. That is correct, isn't it? That's why you are here,
arguing with me on a Friday evening, when we both should probably be
doing something else. You are expressing your opinion, about certain
matters relating to your job, and you are doing so in ways that you feel
are supportive of the community which you serve... not with every sylable
you utter having to have been be pre-approved... not with your corporate
counsel looking over your shoulder at every keystroke. You're a bright
guy, and a leader among men. You have an opinion, and you are expressing
it, for the good of the community. Marvlous! I say Bravo!

Just please explain to me how you taking a public position here, tonite,
in this conversation with me... a position which you take and speak about
and defend as part of your executive discretion, as the leader of ARIN,
in what you hope will be its best interests and those of the community...
is really all that different from what _I_ have requested you to do?
i.e. take a position... a public position... on matters affecting your job
and the resources you oversee, in the best interests of the community.

I think you get my drift, because it isn't really all that subtle a point
I am making. I don't think that you can have it both ways. I don't think
that you can express your opinions, forcefully and eloquently, here with
me, on a Friday night... as I believe you are free to do, within the
limits of your executive discretion... but then go in to work on Monday
morning and claim that you have been obliged to check all of your opinions
at the door on the way in, and that both your and your organization are
likewise obliged by protocol to remain utterly mute until cocktail hour,
when you are off the clock and on your own time, even when it comes to
matters as serious as raw blatant theft and hijacking... acts which deface
and besmirch the very community you are sworn to protect. (Well, ok. Please
_do_ allow me just a tiny bit of literary license, alright? They have
Richard III on the IFC channel just now, and Shakespere in my general
vicinity always makes my prose rather prolix.)

Sigh. I feel sure that I haven't convinced you to bite off even just this
tiny additional bit of authority/responsibility and stake it out as part
of the turf that goes quite naturally with your executive discretion...
discretion which you must be afforded, like it or not, by your constituency,
in order for you to do your job. I'm sure that you have thought too long
and too hard about your job, and what it takes to survive in it, long term,
to be beguiled at this point by even the most evocative of retorical
flourishes. But I will count myself as having been successful if I have
at least caused you to think a bit more... not about what freedom you have
to ``do'', but about what freedom I believe you have to speak, and to speak
and express opinions in ways that benefit the community far more than your
silence would (or does).

``Look folks, we've looked at this, and in our opinion, what's going on
here just doesn't look kosher.''

The good news is that if you're referring to investigation of errant entries
in WHOIS, we currently do expend effort to investigate and correct. In order
for ARIN to investigate and annotate address blocks according to their state

in the routing tables, it would take a very clear mandate from the community.

So you have said. So you have repeated. I am still not buying that you
are nearly as handcuffed as you say you are, because if nothing else, you
would have found it impossible to type this e-mail that I am responding
to if you had actually been wearing the kinds of handcuffs you claim,
i.e. ones which prevent you from even just expressing opinions on important
and relevant matters.

You can suggest such a policy if you feel strongly about this; the process to
to so is shown here: https://www.arin.net/participate/policy/pdp/appendix_b/

Thank you. I may perhaps do so. But I am not at all heartened to believe
that doing so would be likely to have any effect, given that you have
not evinced even the slightest hint, during this exchange of any actual
desire to have your portfolio enhanced in this specific way. (And I
think that your vote would, quite rightly, outweigh any others when it
comes to such questions, i.e. those affecting the scope of your authority
and responsibility.)

In short, I leave discouraged, but unbowed.

At least I know who _not_ to expend time reporting certain very naughty
things to now, and I guess that is a small step forward, as it will save
me some time which I can better spend actually chasing more of these
hijacking weasles to ground.

Regards,
rfg

It's an individual decision of each organization choosing to accept and
further pass along the route.

Like it or not, there is not "THE INTERNET" there is a set of independent
networks operating under a commonly agreed framework of protocols.
Each network operator is free to accept, deny, or otherwise handle
any traffic they wish on any basis they choose.

This is the greatest strength of the internet. It is also it's most exploitable
weakness in some ways. However, changing it would fundamentally
destroy much of it's usefulness and resilience as a tool for the
democratization of communication. As such, I must oppose any
such move to apply greater central authority.

Owen

Yearly? I say every 30 days.

mailing lists do the c-r every 30 days. surely correct arin registration data is more important than a single email address on a mailing list.

-Dan

It's an individual decision of each organization choosing to accept

and

further pass along the route.

Like it or not, there is not "THE INTERNET" there is a set of
independent
networks operating under a commonly agreed framework of protocols.
Each network operator is free to accept, deny, or otherwise handle
any traffic they wish on any basis they choose.

This is the greatest strength of the internet. It is also it's most
exploitable
weakness in some ways. However, changing it would fundamentally
destroy much of it's usefulness and resilience as a tool for the
democratization of communication. As such, I must oppose any
such move to apply greater central authority.

Owen

Of course, and I absolutely agree with that so long as the individual
operators have the information they need to make those individual
decisions. And that is the goal. Having information as to which
resource have no valid points of contact and what other resources are
associated with that invalid POC might be useful to some when some
traffic crosses their net or reaches their other resources that causes
problems.

I see now that I really need to back up a couple of steps here and ask John
for something which is, in a way, entirely different from what I have asked
for so far. (See above.) And in fact, this one ought to be as EASY AS PIE
for ARIN to implement, since it would appear that they are ALREADY DOING IT.

I asked John for a ``new'' kind of ``this is not quite right'' annotation
within AS and IP block whois records. *And* I asked him to make these
annotations public, right within the public WHOIS records... *not* just
within some special, semi-secret feed of some special, semi-secret version
of the WHOIS data base.

So while I was looking at the WHOIS records for the set of blocks that were
(apparently now past tense) being 'jacked by AS14202 earlier today (Saturday)
I happened to come across the following annotation in one of the relevant
IP block WHOIS records (but _only_ one):

  Comment: The information for this network has been reported to
  Comment: be invalid. ARIN has attempted to obtain updated data, but has
  Comment: been unsuccessful. To provide current contact information,
  Comment: please e-mail hostmaster@arin.net.

YESSS! This is exactly the kind of thing I have been asking for!

But more to the point, this is the exact kind of thing that (very bizzarely)
John Curran just told me that he would accept as, in effect, and enhancement
request... AS IF IT DIDN'T ALREADY EXIST, or as if ARIN wasn't already doing
this exact thing. (See the WHOIS for NET-204-89-0-0-1, which, as we speak,
contains the above helpful annotation.)

So OK, John... Can you explain yourself... please? Why did you say you
were accepting my request into your suggestion box, when it appears that
ARIN has already been doing exactly the thing I asked for... even if only
haphazardly, in a disorganized way, and only within a limited number of
cases?

I googled for some of the verbage in the above notice, and I got over 9,000
hits. So obviously, this notice that's present within the WHOIS record
for NET-204-89-0-0-1... and many many many others... isn't a ``one off''.
You ARIN folks have apparently already placed that same annotaion in lots and
lots of AS and IP block records. Maybe you haven't been doing it _lately_
or perhaps maybe you haven't been doing it _consistantly_, but that's a
hell of a different thing that just playing dumb and/or saying (or implying)
that ARIN has never done it at all, don't you agree John?

So let's get down to brass tacks here. John, you can see the annotation
that's present within the WHOIS record for NET-204-89-0-0-1 just as well
as I can. And you obviously don't have any trouble with understanding
the English language, and the annotation is clear and straightforward.
ARIN has been unable to verify the POC. And this annotation is _not_
just on the POC record itself. It is on an IP block WHOIS record. This
is _exactly_ what I was asking for. ARIN has clearly already been doing it,
so there's no need for a whole new study committee, an environmental impact
statement, circulation of proposals, sub-committee delegation, advancement
of the proposal back to the super-committee for re-review, recirculation,
republication, balloting, re-balloting, amendment, etc., etc., etc.,
in other words all of the bullshit bureaucratic stumbling blocks that
bureaucrats... like my favorite, Sir Humphrey Appleby... put up as road-
blocks to even the smallest and simplest bit of forward movement.

I'll say it again, because I don't want there to be any misunderstanding:
Clearly, ARIN has already been doing this... putting in these WHOIS record
annotations. I have LOTS of example of that.

So now, John, did someone ever expressely *withdraw* ARIN's permission to
create and attach these exact sorts of annotations? If so, who, and when?

If not, then the ball's in your court John, and your choice is simple,
I think: Do you want to do something simple... something that ARIN
quite obviously already has permission to do... or do you want to be
Sir Humphrey Appleby and smother this small simple idea in its crib with
layer upon layer of bureaucracy?

If the latter, then I have every confidence that you are skilled enough
to succeed at erecting an impenetrable wall of bureaucracy. If the former
however, then when should we expect to start seeing these annotations in
_all_ of the IP block and AS WHOIS records that have uncontactable POCs...
a set which ARIN has, apparently, already identified, in spades.

(If your staff can't get this done in a week, then please do contact me
off list, because I'm quite sure that _I_ can do it in a half an hour,
in Perl... and I'd be only too happy to volunteer my time for this good
cause.)

You might well ask ``What would be the point of all this? What would be
the use?'' The point and the usefulness is that if these kinds of annotations
are present within AS and IP block WHOIS records, then guys like the poor
overworked, well-meaning manager of Colosseum.com (AS19842) who I spoke to
earlier today about his customer, AS14202, and all of the hijacked IP
space it was announcing would be able to see at a glance that something
isn't right. And who knows? Maybe even if those annotations were in
there for all of the blocks that are _still_ being hijacked by AS6061 and
AS10392, even as we speak, then maybe it would be just a little less easy
for companies like Beyond The Network America to play dumb, and to act
like they don't know exactly what's really going on here. And that would
be helpful.

Regards,
rfg