Slashdot Mirror

In the same regard, Xerox no longer owns all of 13.0.0.0/8 either. Amazon has a piece of that pie, too.

https://whois.arin.net/rest/or...

> I thought my IP address was the property of my ISP.

It is explicitly NOT. The agreement an ISP signs to get numbers includes these terms:
--
Legacy Holder acknowledges and agrees that: (a) the number resources are not property (real, personal, or intellectual) of Legacy Holder; (b) Legacy Holder does not and will not have or acquire any property rights in or to any number resources for any reason
---

See also:
https://www.arin.net/policy/nr...

The most important practical implication of that fact is that ARIN can, under the contract, revoke IP assignments from ISPs that aren't actively using them.

> my phone number is property of the phone company

Two words: Number Portability.

US, Canada and a few Caribbean islands - The ARIN service region includes Canada, many Caribbean and North Atlantic islands, and the United States

I don't get it. You have the words directly from the inventor of the technology and you think he's wrong, that you know better? There were many reasons for the invention of NAT, IP address exhaustion did not rank highly among them. If anything, *that* was the side effect, as the device and technology were originally marketed without even a nod in that direction. It was only after it was invented and tested that some people saw "hey, this can help with that IP address allocation mess too."

Disputing this is pointless -- the inventor of the technology has spoken, explaining why it was created. The uses it's served since then can't change that.

Off topic ironic finger pointing: RFC1466 which addressed potential future exhaustion and came up with additional guidelines for assigning IP blocks was written by Elise Gerich, who was director of national something or other at Merit, a non-profit that networks universities in Michigan. Merit has two /11's, two /12's, two /13's, and several smaller blocks -- just in 35/8 -- assigned to them just a year after authoring the RFC. http://whois.arin.net/rest/net... Somebody didn't read their own memo.

Specifically, RIPE's policy is that each LIR can get one /22 from the final /8, and that's it. The idea is to make sure that new LIRs can at least get some v4 space to run NAT64/CGNAT on.

ARIN didn't think that would be useful, for whatever reason.

https://www.arin.net/policy/nrpm.html#four10
ARIN's policy is that each LIR can get one network (/28 - /24) from the final /10 every 6 months for exactly the same purposes.

I don't trust the BBC, but ARIN's own site does confirm this: ARIN IPv4 Free Pool Reaches Zero

I can't see that detail in the article or the ARIN announcement. It's a bigger deal if no one can get a /22, but then again if the request was for a /9 that might be a much bigger group of people about to go behind Carrier-Grade NAT.

A list of companies still holding an entire /8 block, culled from the Wikipedia article List of assigned /8 IPv4 address blocks and verified against https://www.arin.net/ and https://apps.db.ripe.net/searc... on 7/2/2015:

3 - General Electric
4 - Level 3*
8 - Level 3*
9 - IBM (partially *)
12 - AT&T Services*
15 - Hewlett-Packard
16 - Hewlett-Packard (inherited from Digital Equipment Corporation via Compaq)
17 - Apple
18 - MIT**
19 - Ford
20 - Computer Sciences Corporation
32 - AT&T*
34 - Halliburton
38 - PSINet*
44 - Amateur Radio Digital Communications***
48 - Prudential Securities
53 - Daimler AG (via RIPE)

This list does not include military, postal, or other government entities.

* Network service provider

** Educational institution

** Special-use, mostly unreachable, see Wikipedia's article on AMPRNet for details

https://www.arin.net/resources... perhaps?

It did happen, even if you didn't notice much impact.

Name: slashdot.org IP: 216.34.181.45 Domain: slashdot.org Querying root.rwhois.net:4321 for slashdot.org... Can not resolve host 'root.rwhois.net' Querying whois.pir.org for slashdot.org... Domain Name:SLASHDOT.ORG Domain ID: D2289308-LROR Creation Date: 1997-10-05T04:00:00Z Updated Date: 2014-03-14T22:12:11Z Registry Expiry Date: 2015-10-04T04:00:00Z Sponsoring Registrar:Tucows Inc. (R11-LROR) Sponsoring Registrar IANA ID: 69 WHOIS Server: Referral URL: Domain Status: clientTransferProhibited Domain Status: clientUpdateProhibited Registrant ID:tuE8gFbzWFO9qSj2 Registrant Name:Host Master Registrant Organization:Dice Holdings, Inc. Registrant Street: 1040 Avenue of the Americas Registrant Street: ATTN Slashdot Media Registrant Street: 16th Floor Registrant City:New York Registrant State/Province:NY Registrant Postal Code:10018 Registrant Country:US Registrant Phone:+1.8557527436 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: mailto:hostmaster@slashdotmedi... Admin ID:tuVUNO2QRhDH8FrR Admin Name:DNS Admin Admin Organization:Dice Holdings, Inc. Admin Street: 1040 Avenue of the Americas Admin Street: ATTN Slashdot Media Admin Street: 16th Floor Admin City:New York Admin State/Province:NY Admin Postal Code:10018 Admin Country:US Admin Phone:+1.8557527436 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: mailto:dns-admin@slashdotmedia... Tech ID:tuSiUEvdGR8LFGdK Tech Name:DNS Technical Tech Organization:Dice Hol dings, Inc. Tech Stree t: 1040 Avenue of the Americas Tech Street: ATTN Slashdot Me dia Te ch Street: 16th Floor Tech City:New York Tech State/Province:NY Tech Postal Code:10018 Tech Country:US Tech Phone:+1.8557527436 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: mailto:dns-tech@slashdotmedia.... Name Server:NS3.P03.DYNECT.NET Name Server:NS1.P03.DYNECT.NET Name Server:NS2.P03.DYNECT.NET Name Server:NS4.P03.DYNECT.NET Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: DNSSEC:Unsigned Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. Querying whois.arin.net for 216.34.181.45... # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/whois_tou... # # If you see inaccuracies in the results, please report at # http://www.arin.net/public/who... # # # Query terms are ambiguous. The query is assumed to be: # "n 216.34.181.45" # # Use "?" to get help. # # # The following results may also be obtained via: # http://whoi

Name: slashdot.org IP: 216.34.181.45 Domain: slashdot.org Querying root.rwhois.net:4321 for slashdot.org... Can not resolve host 'root.rwhois.net' Querying whois.pir.org for slashdot.org... Domain Name:SLASHDOT.ORG Domain ID: D2289308-LROR Creation Date: 1997-10-05T04:00:00Z Updated Date: 2014-03-14T22:12:11Z Registry Expiry Date: 2015-10-04T04:00:00Z Sponsoring Registrar:Tucows Inc. (R11-LROR) Sponsoring Registrar IANA ID: 69 WHOIS Server: Referral URL: Domain Status: clientTransferProhibited Domain Status: clientUpdateProhibited Registrant ID:tuE8gFbzWFO9qSj2 Registrant Name:Host Master Registrant Organization:Dice Holdings, Inc. Registrant Street: 1040 Avenue of the Americas Registrant Street: ATTN Slashdot Media Registrant Street: 16th Floor Registrant City:New York Registrant State/Province:NY Registrant Postal Code:10018 Registrant Country:US Registrant Phone:+1.8557527436 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: mailto:hostmaster@slashdotmedi... Admin ID:tuVUNO2QRhDH8FrR Admin Name:DNS Admin Admin Organization:Dice Holdings, Inc. Admin Street: 1040 Avenue of the Americas Admin Street: ATTN Slashdot Media Admin Street: 16th Floor Admin City:New York Admin State/Province:NY Admin Postal Code:10018 Admin Country:US Admin Phone:+1.8557527436 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: mailto:dns-admin@slashdotmedia... Tech ID:tuSiUEvdGR8LFGdK Tech Name:DNS Technical Tech Organization:Dice Hol dings, Inc. Tech Stree t: 1040 Avenue of the Americas Tech Street: ATTN Slashdot Me dia Te ch Street: 16th Floor Tech City:New York Tech State/Province:NY Tech Postal Code:10018 Tech Country:US Tech Phone:+1.8557527436 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: mailto:dns-tech@slashdotmedia.... Name Server:NS3.P03.DYNECT.NET Name Server:NS1.P03.DYNECT.NET Name Server:NS2.P03.DYNECT.NET Name Server:NS4.P03.DYNECT.NET Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: DNSSEC:Unsigned Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. Querying whois.arin.net for 216.34.181.45... # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/whois_tou... # # If you see inaccuracies in the results, please report at # http://www.arin.net/public/who... # # # Query terms are ambiguous. The query is assumed to be: # "n 216.34.181.45" # # Use "?" to get help. # # # The following results may also be obtained via: # http://whoi

Name: slashdot.org IP: 216.34.181.45 Domain: slashdot.org Querying root.rwhois.net:4321 for slashdot.org... Can not resolve host 'root.rwhois.net' Querying whois.pir.org for slashdot.org... Domain Name:SLASHDOT.ORG Domain ID: D2289308-LROR Creation Date: 1997-10-05T04:00:00Z Updated Date: 2014-03-14T22:12:11Z Registry Expiry Date: 2015-10-04T04:00:00Z Sponsoring Registrar:Tucows Inc. (R11-LROR) Sponsoring Registrar IANA ID: 69 WHOIS Server: Referral URL: Domain Status: clientTransferProhibited Domain Status: clientUpdateProhibited Registrant ID:tuE8gFbzWFO9qSj2 Registrant Name:Host Master Registrant Organization:Dice Holdings, Inc. Registrant Street: 1040 Avenue of the Americas Registrant Street: ATTN Slashdot Media Registrant Street: 16th Floor Registrant City:New York Registrant State/Province:NY Registrant Postal Code:10018 Registrant Country:US Registrant Phone:+1.8557527436 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: mailto:hostmaster@slashdotmedi... Admin ID:tuVUNO2QRhDH8FrR Admin Name:DNS Admin Admin Organization:Dice Holdings, Inc. Admin Street: 1040 Avenue of the Americas Admin Street: ATTN Slashdot Media Admin Street: 16th Floor Admin City:New York Admin State/Province:NY Admin Postal Code:10018 Admin Country:US Admin Phone:+1.8557527436 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: mailto:dns-admin@slashdotmedia... Tech ID:tuSiUEvdGR8LFGdK Tech Name:DNS Technical Tech Organization:Dice Hol dings, Inc. Tech Stree t: 1040 Avenue of the Americas Tech Street: ATTN Slashdot Me dia Te ch Street: 16th Floor Tech City:New York Tech State/Province:NY Tech Postal Code:10018 Tech Country:US Tech Phone:+1.8557527436 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: mailto:dns-tech@slashdotmedia.... Name Server:NS3.P03.DYNECT.NET Name Server:NS1.P03.DYNECT.NET Name Server:NS2.P03.DYNECT.NET Name Server:NS4.P03.DYNECT.NET Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: Name Server: DNSSEC:Unsigned Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. Querying whois.arin.net for 216.34.181.45... # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/whois_tou... # # If you see inaccuracies in the results, please report at # http://www.arin.net/public/who... # # # Query terms are ambiguous. The query is assumed to be: # "n 216.34.181.45" # # Use "?" to get help. # # # The following results may also be obtained via: # http://whoi

I see fimble has a /29:

NetRange: 23.31.69.152 - 23.31.69.159
CIDR: 23.31.69.152/29
NetName: FIMBLE
Customer: FIMBLE (C03254701)
RegDate: 2012-12-19
Updated: 2013-12-11
Ref: http://whois.arin.net/rest/net...

OrgAbuseHandle: NAPO-ARIN
OrgAbuseName: Network Abuse and Policy Observance
OrgAbusePhone: +1-888-565-4329
OrgAbuseEmail: abuse@comcast.net
OrgAbuseRef: http://whois.arin.net/rest/poc...

Whi don't you have your own abuse poc? Also, about that /29, 157.69.31.23.in-addr.arpa is set correctly, but the rest of the IPs are not. This has probably nothing to do with reputation, but it'd be convenient for you to have comcast define CNAMEs for RFC2317 delegation.

I see fimble has a /29:

NetRange: 23.31.69.152 - 23.31.69.159
CIDR: 23.31.69.152/29
NetName: FIMBLE
Customer: FIMBLE (C03254701)
RegDate: 2012-12-19
Updated: 2013-12-11
Ref: http://whois.arin.net/rest/net...

OrgAbuseHandle: NAPO-ARIN
OrgAbuseName: Network Abuse and Policy Observance
OrgAbusePhone: +1-888-565-4329
OrgAbuseEmail: abuse@comcast.net
OrgAbuseRef: http://whois.arin.net/rest/poc...

Whi don't you have your own abuse poc? Also, about that /29, 157.69.31.23.in-addr.arpa is set correctly, but the rest of the IPs are not. This has probably nothing to do with reputation, but it'd be convenient for you to have comcast define CNAMEs for RFC2317 delegation.

I have verified. I am not on any RBLs as I mentioned in my original question. As for whether or not my IP range is residential, I was told when I signed up that it was not. However, I have no way that I know of to verify that.

%host mail.fimble.com
mail.fimble.com has address 23.31.69.157
% whois 23.31.69.15

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou...
#
# If you see inaccuracies in the results, please report at
# http://www.arin.net/public/who...
#

#
# Query terms are ambiguous. The query is assumed to be:
# "n 23.31.69.15"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/net...
#

TOPPAN PHOTOMASKS INC TOPPANPHOTOMASKSINC (NET-23-31-69-8-1) 23.31.69.8 - 23.31.69.15
Comcast Business Communications, LLC CBC-CM-4 (NET-23-30-0-0-1) 23.30.0.0 - 23.31.255.255

I have verified. I am not on any RBLs as I mentioned in my original question. As for whether or not my IP range is residential, I was told when I signed up that it was not. However, I have no way that I know of to verify that.

%host mail.fimble.com
mail.fimble.com has address 23.31.69.157
% whois 23.31.69.15

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou...
#
# If you see inaccuracies in the results, please report at
# http://www.arin.net/public/who...
#

#
# Query terms are ambiguous. The query is assumed to be:
# "n 23.31.69.15"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/net...
#

TOPPAN PHOTOMASKS INC TOPPANPHOTOMASKSINC (NET-23-31-69-8-1) 23.31.69.8 - 23.31.69.15
Comcast Business Communications, LLC CBC-CM-4 (NET-23-30-0-0-1) 23.30.0.0 - 23.31.255.255

I have verified. I am not on any RBLs as I mentioned in my original question. As for whether or not my IP range is residential, I was told when I signed up that it was not. However, I have no way that I know of to verify that.

%host mail.fimble.com
mail.fimble.com has address 23.31.69.157
% whois 23.31.69.15

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou...
#
# If you see inaccuracies in the results, please report at
# http://www.arin.net/public/who...
#

#
# Query terms are ambiguous. The query is assumed to be:
# "n 23.31.69.15"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/net...
#

TOPPAN PHOTOMASKS INC TOPPANPHOTOMASKSINC (NET-23-31-69-8-1) 23.31.69.8 - 23.31.69.15
Comcast Business Communications, LLC CBC-CM-4 (NET-23-30-0-0-1) 23.30.0.0 - 23.31.255.255

Thanks for replying to my post instead of keeping the non-brilliance of my ideas to yourself. My biggest concern when writing that post was that I was talking to myself. I'll attempt to address your concerns one by one.

You're... welcome?

Just about all ISPs and backbone carriers carry full tables and many large organisations do as well for multihoming purposes.

Then I misunderstood you. I thought you were repeating what others have said earlier, claiming each router carries a complete copy of all the routes on the Internet, which of course isn't true.

Now that we have that cleared up, I'll snip out parts I don't need to reply to.

Your bitcoinesque solution for IPv6 allocation would make things worse.

It seemed like a technical solution to avoid the politics of Internet governance. I admit it wasn't well thought out, however I am curious how it would make things worse by allowing a small block of IPv6 addresses to be allocated in a decentralized way and adding cryptographic integrity along the way.

Plus, networks transit other networks all the time, meaning one network can advertise a prefix they don't own, legitimately.

I should have been more specific; I was suggesting originating advertisements would be signed as opposed to transient advertisements.

You are asking for DomainKeys but with routes. That is too computationally expensive right now and would require too many lookups and time. Perhaps somewhere down the line when the big iron routers catch up with CPU resources vs line speed.

Routers that speak BGP are on the ISP and backbone level,

Medium to large organisations also use BGP to advertise their address space to their ISP(s).

Not to your home router.

and are physically secured.

Originating BGP route advertisement signing is not intended to supplant physical security measures.

I'm aware of the difference between remote access, console access, and physical access, and hardware vs software.

Your home router doesn't speak BGP, and if it did, your ISP's router would ignore it.

None of this would really be necessary for a home user as their ISP would be doing all of this on their behalf.

That's what I just said...

To announce rogue routes, one needs to hack into the ISP and backbone peering routers -- which happened recently, but is rare.

To announce rogue routes, one only needs an ISP that doesn't filter incoming BGP advertisements properly. It seems apparent as the Internet grows there will be more and more BGP peerings and as a consequence of that not all of them will be competent or aboveboard with their implementations.

You're just restating what I said. I guess I wasn't clear, but I'm also assuming a best practice (or as near as possible) implementation, because there's no use talking about security if people are going to leave the front door open, right? It's not even a discussion at that point.

The Resource Public Key Infrastructure (RPKI) is a step in the right direction, however seems to be mainly for preventing mis-configurations from causing outages. Someone with malicious intent need only use AS path prepending to bypass this protection.

Again, anyone with access to the routers can do this right now. Any organization that doesn't shut its front door can have this happen. This can be solved through best practices. This isn't e-mail. Even if you got people on board for this, it would take a protocol revision AND all new hardware for everyone. It's not going to happen anytime soon.

Don't take it personally. Your offered solution for route signing (whether you wrote them or not) just isn't feasible right now.

No one router has a "full table" of all the routes. The routing protocols and the engineers work to make sure the tables are as close to lean as possible.

Just about all ISPs and backbone carriers carry full tables and many large organisations do as well for multihoming purposes. Global BGP tables are currently around 513,191 routes and this is what facilitated the issues mentioned in the article. One ISP made a mistake and started advertising more specific prefixes for blocks that were already summarized and this pushed the number of global routes beyond the limits of some older hardware. I would suggest reading about the Default Free Zone.

Your offered solution isn't necessary.

LISP is not something that I invented, it's something the IETF is working on to solve a perceived problem.(RFC6830) Some IETF contributors came to the conclusion the Internet routing system was not scaling well with the "explosive growth of new sites" and multihoming that many organisations now do. Problem Statement From all indications, the growth of the Internet does not appear to be slowing down, but accelerating. It seems like a prudent choice to evaluate different ideas as possible solutions to the issue of Internet scalability.

Your bitcoinesque solution for IPv6 allocation would make things worse.

It seemed like a technical solution to avoid the politics of Internet governance. I admit it wasn't well thought out, however I am curious how it would make things worse by allowing a small block of IPv6 addresses to be allocated in a decentralized way and adding cryptographic integrity along the way.

Plus, networks transit other networks all the time, meaning one network can advertise a prefix they don't own, legitimately.

I should have been more specific; I was suggesting originating advertisements would be signed as opposed to transient advertisements.

Routers that speak BGP are on the ISP and backbone level,

Medium to large organisations also use BGP to advertise their address space to their ISP(s).

and are physically secured.

Originating BGP route advertisement signing is not intended to supplant physical security measures.

Your home router doesn't speak BGP, and if it did, your ISP's router would ignore it.

None of this would really be necessary for a home user as their ISP would be doing all of this on their behalf.

To announce rogue routes, one needs to hack into the ISP and backbone peering routers -- which happened recently, but is rare.

To announce rogue routes, one only needs an ISP that doesn't filter incoming BGP advertisements properly. It seems apparent as the Internet grows there will be more and more BGP peerings and as a consequence of that not all of them will be competent or aboveboard with their implementations.

The Resource Public Key Infrastructure (RPKI) is a step in the right direction, however seems to be mainly for preventing mis-configurations from causing outages. Someone with malicious intent need only use AS path prepending to bypass this protection.

I suspect Microsoft may be making a big deal about this partly to encourage IPv6 adoption and partly because they may want to exert undue influence on the process by which the community develops IP addressing policy to arrive at a result more favorable to large corporations like themselves.

Today the rule is justified need, and many large companies might like to buy a 2 year or a 3 year supply of IP addresses, from anyone they can pay a big enough premium for addresses,but the community policies today just don't work that way; under current policies subject to justified need, if Microsoft follows the rules, they have to efficiently utilize all their allocations, before applying to transfer more resources.

They were referring to this: "ARIN enters phase four of the IPv4 countdown plan"

> As of now, only AfriNIC is not in address exhaustion mode."

That is not true - ARIN (north America's RiR) is still handing out IPv4's and will continue to do so until down to their last /10.

https://www.arin.net/resources...

That's because the entire 192.168 IP range isn't routable on the Internet:

# Query terms are ambiguous. The query is assumed to be:
# "n 192.168.2.100"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/net...
#

NetRange: 192.168.0.0 - 192.168.255.255
CIDR: 192.168.0.0/16
OriginAS:
NetName: PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
NetHandle: NET-192-168-0-0-1
Parent: NET-192-0-0-0-0
NetType: IANA Special Use
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.

You guys are both newbs.

Your ISP can give you a block of dynamic/static IP addresses, which your router assigns instead of 192.168.1.X?

That's how the internet works to begin with, and it used to be the norm for IPv4 networks. A lot of large networks still do it that way -- the computer I'm on at work has a globally unique IP address. You can still get a block of static IPs if you buy a business-class connection. That used to be almost the definition of a business connection, back when more people ran their own servers instead of using hosting services. IP addresses cost money, so ISPs try to have as few as possible. NAT came about when people started getting multiple computers per household but didn't want to pay for a business connection. It was never meant to prop up the internet as a whole.

I was partly wrong in my first response. The Sixxs guys does not seem to keep proper track of things. Here is the allocations that the US Department of Defense has:

http://whois.arin.net/rest/org/USDDD/nets

They got 22x /22. However whoever calculated that equals one /13 is mistaken. It equals 69% of a /17. You need a bit less than 5 bits to express 22 nets. Apparently some guy noticed that most of those 22 networks were allocated from the same /13 block, but that in no way means the remaining of that /13 is reserved to DoD. If it was it would have been allocated to them.

There seems to be no foundation for the claim that Google got any exceedingly large allocations. They got two /32 from ARIN: http://whois.arin.net/rest/org/GOGL/nets

Google also got a /29 from RIPE. And possible more similar sized networks from other regions, which seems reasonable given their size.

Can you tell us what to the Google /16 block is? If not we can assume this is just wrong.

I was partly wrong in my first response. The Sixxs guys does not seem to keep proper track of things. Here is the allocations that the US Department of Defense has:

http://whois.arin.net/rest/org/USDDD/nets

They got 22x /22. However whoever calculated that equals one /13 is mistaken. It equals 69% of a /17. You need a bit less than 5 bits to express 22 nets. Apparently some guy noticed that most of those 22 networks were allocated from the same /13 block, but that in no way means the remaining of that /13 is reserved to DoD. If it was it would have been allocated to them.

There seems to be no foundation for the claim that Google got any exceedingly large allocations. They got two /32 from ARIN: http://whois.arin.net/rest/org/GOGL/nets

Google also got a /29 from RIPE. And possible more similar sized networks from other regions, which seems reasonable given their size.

Can you tell us what to the Google /16 block is? If not we can assume this is just wrong.

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

just use whois...

whois 11.0.0.0

The following results may also be obtained via:
http://whois.arin.net/rest/nets;q=11.0.0.0?showDetails=true&showARIN=false&ext=netref2

NetRange: 11.0.0.0 - 11.255.255.255
CIDR: 11.0.0.0/8
OriginAS:
NetName: DODIIS
NetHandle: NET-11-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1984-01-19
Updated: 2007-08-22
Ref: http://whois.arin.net/rest/net/NET-11-0-0-0-1

OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2011-08-17
Ref: http://whois.arin.net/rest/org/DNIC

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: 1-614-692-2708
OrgTechEmail: HOSTMASTER@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/MIL-HSTMST-ARIN

OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: 1-800-365-3642
OrgTechEmail: registra@nic.mil
OrgTechRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-800-365-3642
OrgAbuseEmail: registra@nic.mil
OrgAbuseRef: http://whois.arin.net/rest/poc/REGIS10-ARIN

ARIN WHOIS data and services are subject to the Terms of Use
available at: https://www.arin.net/whois_tou.html

Indeed. And it's been covered numerous times before. First off, reclaiming a single /8 will not make any measurable dent. There was a NANOG post a few months back from John Curran that pretty much was the last word. While there is *a lot* of address space that could be reclaimed, a) it would only prolong the inevitable, and b) it would take lenghtly, expensive legal fights to get it all back. ARIN's official stance is to accept any legacy blocks anyone wants to hand over, but they aren't even bothering to ask that any be returned.

(Honestly, you'd be an idiot to hand over something worth so much that's costing you absolutely zero.)

For all intents and purposes the addresses that my company registered in the early 90's are ours. If we want to sell them, there's nothing within ARIN's Number Resource Policy Manual that says that cannot sell all or any part of our address space to anybody else. The transfer has to be done through ARIN and it has to be a group within ARIN's zone, but if we charge for it, ARIN doesn't care.

ford could've averted their recent financial woes by auctioning off their 16 million ip addresses http://whois.arin.net/rest/net/NET-19-0-0-0-1

As a former employee, posting this as anonymous for obvious reasons; however, the below information is freely available if you know where to look.

WHMCS is hosted by Hostgator on a dedicated server. This can be found by:

% dig NS whmcs.com +short | head -1 | xargs dig +short | xargs whois
# http://whois.arin.net/rest/nets;q=50.116.115.104?showDetails=true&showARIN=false&ext=netref2

HGBLOCK = Hostgator IP block, the Arin address is Hostgator's main office, and websitewelcome.com is Hostgator's generic domain they use for reseller server's hostnames/nameservers.

at least hosted on US servers

whois -h whois.arin.net 50.116.96.245

OrgName: WEBSITEWELCOME.COM
OrgId: BO
Address: 11251 Northwest Freeway
City: Houston
StateProv: TX
PostalCode: 77092
Country: US
RegDate: 2011-02-16
Updated: 2011-06-09
Ref: http://whois.arin.net/rest/org/BO

every spammer ive seen here is hosted in the US
seems like the new haven for them

For example, with IPv6, there isn't really provider independent address space.

Uh.

Yes there is. See for example this and this/this.

According to DNSTools the domain "dumpgodaddy.com" was reserved for 1 year starting two days ago, but gives no IP address for it. The name resolves to 67.215.66.132, which can't be pinged or accessed via port 80, and is within an IP block assigned to OpenDNS, LLC.

For the last 10 years I have read: "Yes, IPv4 addresses are running out.. blaa FUD blaa blaa FUD" So far nothing has happened. Most computers out there are NAT'ed so, please stop spreading FUD.

And indeed, they have been running out for the past ten years - look at slide 5 from this presentation: https://www.arin.net/knowledge/v4_deplete_v6_adopt.pdf The fact is that ISPs and hosting companies are having to now undergo major changes in order to continue to grow. The fact that we've known this was coming and developed IPv6, gotten into every major OS and the gear of every major network equipment manufacturer is simply good preparation for what's to come.

I thought there was an announcement that the IPv4 address space is now totally exhausted. Or at least there are no new blocks to be assigned. The tunnel broker, Hurricane Electric indicates that IPv4 is exahusted.

The original such announcement came from APNIC I think a year ago, when they indicated that they were out of IPv4 address assignments to their ISPs. More recently, they changed their transfer policy so that even if 2 organizations want to undergo a transfer of IPv4 addresses from one to the other, the recipient has to justify their requirement for IPv4. In short, getting IPv4 is getting more difficult in this region.

ARIN so far seems to have pretty much the same policy that it had months ago - nothing has changed, even if Comcast and HE are indicating that they are out of IPv4 addresses. RIPE will be distributing /22s, while AfriNIC was supposed to have run out by August 11 but their status is unclear and not current. LACNIC too seems to be @ an end of its allocations.

Given all that, there is no reason why any ISP shouldn't start forcing the move to IPv6, since that's the only place where all the addresses really are.

Why? What's the point of keeping them, since there is an annual subscription associated w/ these addresses. His ISP could either return them to ARIN (I'm assuming that's the RIR in question here), or, if they want more money for it, do what Nortel did w/ MS and sell them. ARIN is quite interested in getting back as many IPv4 addresses that it can to have it available for people who can't move to IPv6 and need to have IPv4 addresses. So if they are capable of migrating sooner, why wait?

The only rational reason I see is that the ISPs may not be willing to spend the money now, which begs the question - do they plan to go out of business when they run out? B'cos it'll sure be more expensive then, when everything is important and urgent, instead of just important. Otherwise, since they know that they're going to, in the end, transition to IPv6, it'll be immaterial whether they spend the money on the transition now or later. In fact, chances are likely that they'll be guzzling money later when there are critical shortages of IP addresses. Otherwise, buy whatever equipment is needed now, and come up with either dual stack or dual stack lite solutions. In fact, this solution would be even cheaper than IPv4, since he'd be getting much larger IPv6 blocks than IPv4, and would therefore have a lot more of them.

Let's say you did.

ping www.med.govt.nz
IP address: 192.188.71.101
ARIN says to query APNIC

inetnum: 192.188.71.0 - 192.188.71.255
netname: MEDGOVT-NZ
descr: Ministry of Economic Development
country: NZ

person: Maryanne Craig
address: Ministry of Economic Development
address: 33 Bowen Street
address: WELLINGTON
address: NEW ZEALAND
country: NZ
phone: +64 4 462 4215
e-mail: Maryanne.Craig@med.govt.nz

person: Stephen Isaacs
address: Ministry of Economic Development
address: 33 Bowen Street
address: WELLINGTON
address: NEW ZEALAND
country: NZ
phone: +64 4 470 2526
e-mail: stephen.isaacs@med.govt.nz

Now the real question is, do I also own the IP the domain name is pointing to if I have a static IP address, or am I leasing it?

The concern that some day organizations might try to claim some sort of property right to an IP address was thought up a long time ago.
The ISP assigned the address, if it was obtained in the past 12 years [or so], had to sign the RSA, which contains the following clause, as a condition of being assigned IP addresses:

Applicant acknowledges and agrees that the number resources are not property (real, personal, or intellectual) and that Applicant does not acquire any property rights in or to any number resources by virtue of this Agreement or otherwise. Applicant further agrees that it will not attempt, directly or indirectly, to obtain or assert any trademark, service mark, copyright, or any other form of property rights in any number resources in the United States or any other country.

but as an end user I can easily get an IPv4 address (I just pay my ISP xx/month), whereas I can find no way to get an actually-mine IPv6 address.

Technically you are wrong on both points (The best kind of wrong!)

The IPv4 address you 'buy' from your ISP was allocated to them by ARIN. The same company that allocates IPv6 addresses.

In fact you can purchase large blocks of both, and pricing is even on the same web page.
https://www.arin.net/fees/fee_schedule.html

So you can get IPv6 there, which isn't the best or cheapest place to do so, but still a lot better than your solution of not being able to find them.

Also you are getting your IPv4 addresses from the same place, despite how many delegations those address blocks have made before reaching you.

"Ownership" is the same for both IPv4 and IPv6.

You have a very good point. Unfortunately, in today's legal climate, it's hard to find someone who:

a. has personal knowledge of the issues or events,
b. is ready to stick their neck out, and
c. won't panic under pressure.

You'd be amazed at how many people fail the last one. The least bit of pressure, and they cave in.

Lets look at the immediate facts.

1. I reported that 770star.com had been used by starmedia communications to, among other things, run an illegal lottery or prize draw.
2. Alex Cholella, the owner of starmedia, screams at iWeb
3. iWeb suspends my hosting account.

Most people would have agreed immediately to remove the "offending material." I won't. 770star.com is hosted by iWeb on one of their smart servers, and they need to buy a clue, that my reporting this guy's behaviour is helping them keep their servers clean.

PING 770star.com (184.107.161.43) 56(84) bytes of data.
64 bytes from 184.107.161.43: icmp_req=1 ttl=54 time=7.02 ms
^C
--- 770star.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.027/7.027/7.027/0.000 ms
barbara@u6:~> whois 184.107.161.43
NetRange: 184.107.0.0 - 184.107.255.255
CIDR: 184.107.0.0/16
OriginAS: AS32613
NetName: IWEB-BLK-07
NetHandle: NET-184-107-0-0-1
Parent: NET-184-0-0-0-0
NetType: Direct Allocation
RegDate: 2010-05-24
Updated: 2010-05-24
Ref: http://whois.arin.net/rest/net/NET-184-107-0-0-1

OrgName: iWeb Technologies Inc.
OrgId: GIT-20
Address: 20, place du Commerce
City: Montreal
StateProv: QC
PostalCode: H3E-1Z6
Country: CA
RegDate: 2003-11-06
Updated: 2008-09-08
Comment: http://www.iweb.com/
Ref: http://whois.arin.net/rest/org/GIT-20

For now, I'm assuming that nobody bothered to check that they themselves were hosting some of the illegal activities. If they restore my hosting account, I'll give them the benefit of the doubt. If they don't, then you can draw your own conclusions.

Most people wouldn't have even have bothered trying to expose the scammer, because they're afraid of getting a SLAPP suit. It's not easy being a whistle-blower.

You have a very good point. Unfortunately, in today's legal climate, it's hard to find someone who:

a. has personal knowledge of the issues or events,
b. is ready to stick their neck out, and
c. won't panic under pressure.

You'd be amazed at how many people fail the last one. The least bit of pressure, and they cave in.

Lets look at the immediate facts.

1. I reported that 770star.com had been used by starmedia communications to, among other things, run an illegal lottery or prize draw.
2. Alex Cholella, the owner of starmedia, screams at iWeb
3. iWeb suspends my hosting account.

Most people would have agreed immediately to remove the "offending material." I won't. 770star.com is hosted by iWeb on one of their smart servers, and they need to buy a clue, that my reporting this guy's behaviour is helping them keep their servers clean.

PING 770star.com (184.107.161.43) 56(84) bytes of data.
64 bytes from 184.107.161.43: icmp_req=1 ttl=54 time=7.02 ms
^C
--- 770star.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.027/7.027/7.027/0.000 ms
barbara@u6:~> whois 184.107.161.43
NetRange: 184.107.0.0 - 184.107.255.255
CIDR: 184.107.0.0/16
OriginAS: AS32613
NetName: IWEB-BLK-07
NetHandle: NET-184-107-0-0-1
Parent: NET-184-0-0-0-0
NetType: Direct Allocation
RegDate: 2010-05-24
Updated: 2010-05-24
Ref: http://whois.arin.net/rest/net/NET-184-107-0-0-1

OrgName: iWeb Technologies Inc.
OrgId: GIT-20
Address: 20, place du Commerce
City: Montreal
StateProv: QC
PostalCode: H3E-1Z6
Country: CA
RegDate: 2003-11-06
Updated: 2008-09-08
Comment: http://www.iweb.com/
Ref: http://whois.arin.net/rest/org/GIT-20

For now, I'm assuming that nobody bothered to check that they themselves were hosting some of the illegal activities. If they restore my hosting account, I'll give them the benefit of the doubt. If they don't, then you can draw your own conclusions.

Most people wouldn't have even have bothered trying to expose the scammer, because they're afraid of getting a SLAPP suit. It's not easy being a whistle-blower.

Well, he certainly has a bias in this. I think he means all addr registered to ARIN. But, if you never registered your preARIN numbers, then seems like you wouldn't be affected by the policies (but this is lawyer territory, so wdik). While registering might be the right thing to do, it doesn't seem like rights enumerated up from the start (I would assume some retained all their rights such as DoD). For some people, I think it is going to come down to the lawyers battling it out over things like implicit rights, what rights IANA et al. reserved, etc.

A comment I found succinct, from their list-serv:

Jo Rhett said:
"I wanted to have explicit clarity on what rights these are."

This is probably the crux of the problem. Was their any explicit clarity
on the rights (or responsibilities) for legacy assignments?
A block that I got in December of 1994 from the University of Toronto
(who handled block assignments in Canada at that time) had little legal
language associated with it and what was written was different than what
IANA was saying at the time, which was different than what InterNIC said
under the Versisign registry contract which may have been different from
what the Department of Commerce intended, who was getting advice and
policy development from Jon Postel.

I'm having trouble finding documentation on the assignment. Since there
wasn't really any legalese related to it, we didn't think much about
document management related to the assignment. We just asked for the
block, got one, used it, maintained it, thought of it as "ours"
(whatever that word means) and carried on with our day-to-day work of
figuring out how to run a network with the IP addresses that were handed
to us with little explanation. In a sense, we homesteaded before the
surveyors arrived to put stakes in the ground and we're still figuring
out how to plough around them without digging them up.

Mel Stotyn

From thread:
http://lists.arin.net/pipermail/arin-discuss/2008-October/thread.html#1073
From msg:
http://lists.arin.net/pipermail/arin-discuss/2008-October/001071.html

Well, he certainly has a bias in this. I think he means all addr registered to ARIN. But, if you never registered your preARIN numbers, then seems like you wouldn't be affected by the policies (but this is lawyer territory, so wdik). While registering might be the right thing to do, it doesn't seem like rights enumerated up from the start (I would assume some retained all their rights such as DoD). For some people, I think it is going to come down to the lawyers battling it out over things like implicit rights, what rights IANA et al. reserved, etc.

A comment I found succinct, from their list-serv:

Jo Rhett said:
"I wanted to have explicit clarity on what rights these are."

This is probably the crux of the problem. Was their any explicit clarity
on the rights (or responsibilities) for legacy assignments?
A block that I got in December of 1994 from the University of Toronto
(who handled block assignments in Canada at that time) had little legal
language associated with it and what was written was different than what
IANA was saying at the time, which was different than what InterNIC said
under the Versisign registry contract which may have been different from
what the Department of Commerce intended, who was getting advice and
policy development from Jon Postel.

I'm having trouble finding documentation on the assignment. Since there
wasn't really any legalese related to it, we didn't think much about
document management related to the assignment. We just asked for the
block, got one, used it, maintained it, thought of it as "ours"
(whatever that word means) and carried on with our day-to-day work of
figuring out how to run a network with the IP addresses that were handed
to us with little explanation. In a sense, we homesteaded before the
surveyors arrived to put stakes in the ground and we're still figuring
out how to plough around them without digging them up.

Mel Stotyn

From thread:
http://lists.arin.net/pipermail/arin-discuss/2008-October/thread.html#1073
From msg:
http://lists.arin.net/pipermail/arin-discuss/2008-October/001071.html