Slashdot Mirror

The random type of UUIDs, which aren't guaranteed unique, but are merely probabilisticly unique -- and which don't use MACs at all -- are meant to be fallbacks if a MAC is unavailable on your system, or if one has privacy concerns and doesn't wish to broadcast a UUID's location of generation.

If there was enforcement of the Generic TLDs -- that is, if only non-profits could register .org; if only commercial enterprises (no fitting in any other category) could register .com; if only network service providers could register .net; if only search engines and brand-agnostic reference sites could register .info; if only porno sites could register .xxx -- such as there is with .gov, .edu, and .mil, then TLDs would actually have meaning.

As an aside, the .name suffix is for individuals' personal websites, but I'd prefer to see a .me extension. :-)

There goes my plan to cash in on a bunch Malaysian TLD URLs when Longhorn is released.

Ah well, it was a myopic business plan at best.

That's a good point. And while we're at it, why are there 16 /8 multicast subnets? And what exactly are Ford, Halliburton, Eli Lilly, Apple, H-P, IBM, and the U.K. Social Security Department doing with their 16 MILLION public, globally allocated IP addresses EACH??? Or what is BBN doing with their 48 MILLION addresses? And then there's BNR, now known as Nortel Networks, which needs fewer and fewer addresses each week. I think a /24 should be plenty for them. (ba-dum ching!)

It looks to the casual observer like there are lots of free addresses, or rather, there WOULD be, with a bit of reorganization and housecleaning...

IANA's port number listings

Thought you may want to consider changing your sig:

~~~~~~~~~~~~
ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://www.iana.org/
The following error was encountered: Connection Failed
The system returned: (113) No route to host
The remote host or network may be down. Please try the request again.
~~~~~~~~~~~~

Sig Reply
--
Shortage of IPv4 addresses? lynx -dump http://www.iana.org/assignments/ipv4-address-space | grep "IANA - Reserved"

Whoa - that's freaky... No wonder there's no real incentive to go to IPV6.... :-)

Although to be fair, thats only 89 class A's (or should I say, "/8"s) which means that it represents only 35% of the total address space. We don't have enough room to double - and with the exponential growth in network-capable devices, the doubling time is steadily getting shorter...

FWIW, a good read on the matter is at http://bgp.potaroo.net/ipv4/. Geoff's analysis concludes that we run out of addresses somewhere between March 2014 and February 2022.

1.2.3.4? It doesn't belong to anyone. 001/8 Sep 81 IANA - Reserved

Look at those masses of /8 (16 million) allocations not yet allocated. IPv4 shortage? Bah. Still, anything that drives v6 is good.

Your box isn't even close to default. You have all kinds of services turned on.

TCP 548 is AFP file sharing
TCP 137 & 139 is freaking NetBIOS!!
UDP 68 is bootp
UDP 631 is Internet Printing Protocol

My box has several ports open, but then I'm running server with SERVICES TURNED ON!

Try doing a port scan from another box on a default OS X install and I'll tell you what you'll see. Nothing.

And just FYI http://www.iana.org/assignments/port-numbers

ISOC Official Page
IETF Official Page
IESG Official Page
IRTF Official Page
IAB Official Page
RFC Editor Official Page
ICANN Official Page
IANA Official Page
W3C Official Page
W3C encyclopedia article
ICANN encyclopedia article
IANA encyclopedia article

Postel may be gone, but IANA, ICANN and IAB still have the same address... as for transparency, there's a lovely little explanation of how-it-works here:

http://www.iana.org/root-management.htm ...as for anything else, erm, if you're really so concerned, have you ASKED?

http://www.iana.org/contact.htm

It seems most people love to bitch piss and moan about ICANN/IANA, but they can't pick up a damned phone or write an email (or, for that matter, type in the F@#$ing URL that is rather forthcoming about process, policies and procedures) when it's far easier to scream "conspiracy!" ...god only knows how many tinfoil hat looneys already ring the phone off the hook. Hell, IMHO, it's pretty superhuman of them to publish their address and front-office phone number in the first place...and godlike that they still get a damned thing done as a result.

Postel may be gone, but IANA, ICANN and IAB still have the same address... as for transparency, there's a lovely little explanation of how-it-works here:

http://www.iana.org/root-management.htm ...as for anything else, erm, if you're really so concerned, have you ASKED?

http://www.iana.org/contact.htm

It seems most people love to bitch piss and moan about ICANN/IANA, but they can't pick up a damned phone or write an email (or, for that matter, type in the F@#$ing URL that is rather forthcoming about process, policies and procedures) when it's far easier to scream "conspiracy!" ...god only knows how many tinfoil hat looneys already ring the phone off the hook. Hell, IMHO, it's pretty superhuman of them to publish their address and front-office phone number in the first place...and godlike that they still get a damned thing done as a result.

• ISOC Official Page
• IETF Official Page
• IESG Official Page
• IRTF Official Page
• IAB Official Page
• RFC Editor Official Page
• ICANN Official Page
• IANA Official Page
• W3C Official Page
• W3C encyclopedia article
• ICANN encyclopedia article
• IANA encyclopedia article

ISOC Official Web Page

IETF Official Web Page

IESG Official Web Page

IRTF Official Web Page

IAB Official Web Page

RFC Editor Official Web Page

ICANN Official Web Page

IANA Official Web Page

W3C Official Web Page

W3C encyclopedia article

ICANN encyclopedia article and IANA encyclopedia article

ISOC Official Page IETF Official Page IESG Official Page IRTF Official Page IAB Official Page RFC Editor Official Page ICANN Official Page IANA Official Page W3C Official Page W3C encyclopedia article ICANN encyclopedia article IANA encyclopedia article

I really think DNS needs to be revised to enforce a unique constraint on a filter of the address. for instance if some-place.com, s0me-place.com, someplace.com and smeplace.com all took you to the same place because they are in fact the same..

No, no, no. IDN's aren't about country codes, they're about special character codings that result in things in your status bar that look like their ASCII equivalent characters, but aren't.

Don't worry, that special site hosted in Christmas Island will continue to resolve just fine. :)

In case you haven't noticed, China has roughly the equivalent of 3.2 Class A's assigned to it. Let's put this in proportion for a moment. According to IANA the IBM (009/8), DEC(016/8), MIT (018/8), and the US Postal Service (056/8) collectively hold more address space than China.

Why does the US Postal service require more than 1/4 of China's address space? More importantly, will they give it up when the time comes that the rest of the world needs it?

While we might not run out of address space for 20 years, I think that the author of your paper was being optimistic in assuming that the corporate world would be willing to modify its infrastructure to "play nice" with address space, shedding extra addresses and keeping everything on private networks (10/8) with only machines that need global accessibility having globally-routable IP addresses.

The IPv4 address shortage is only a myth to countries that have as much address space as they need. It is real elsewhere. China has a population of approximately 1,284,303,705 (July 2002, http://www.nationbynation.com/China/Population.htm l) with your 54,172,684 allocated addresses. That would leave one IP address for every 23 people. Compare this to the United States with 295,065,333 (December 2004, http://www.census.gov/cgi-bin/popclock) having at least 6 addresses for every last man, woman, child, and infant.

All in all, I don't think that they're bitter that companies got /8's because they asked. They're bitter because they can't have as much space as they need, let alone the sort of opulent overallocation seen elsewhere. And yes, their netspace is limited, and they need it.

Have to agree. I also include SIPE (France). I'd say that 80% of all messages are blocked this way, with almost no false positives. I rarely correspond with folks outside the U.S. other than through newsgroups or such, so blocking 8-bit IP networks managed wholly by other than ARIN is quite efficient. Perhaps 50%, probably more, of the remaining messages are spam from other networks, some of which are non-U.S. managed but which are not part of those managed by other than ARIN. Of these, quite a few are in character sets I would never use, and which are unlikely to be used for U.S. audiences. Of course that does not mean that they are not sent using U.S. systems, but I doubt that the sender is of U.S. origin. Not that I could know; can't read the messages anyway.

If anyone is interested in a regular expression that works pretty well (all on one line):

[^\d](43|5[89]|6[012]|8[0-8]|19[345]|20[0-3]|21[ 0- 37-9]|22[012])(\.[\d]{1,3}){3}

The list of non-ARIN networks is available at:
http://www.iana.org/assignments/ipv4-address-space

This changes from time to time, so the above regex will need to be updated once in a while.

All the networks listed as "various registries" will contain a mix of ARIN and/or others; I found it not worth the while to try to use the data therein, but ymmv.

Good luck,
Chuck (anonymous coward, too lazy to register)

This is what you want:

http://www.iana.org/assignments/ipv4-address-spa ce

Start with APNIC.

Too lame to link.

Don't use 127.0.0.1. Use 127.29.13.4, or some equally random address in the 127/8 loopback.

Another alternative, depending on how you want the failed delivery to fail, is to use an IP address within one of the reserved IANA ranges. Bogon lists on the default free routers usually silently drop packets to these addresses. Unless spammers are doctoring the TCP/IP stack in their hosts, silent drops of TCP SYNs usually take around three minutes before the application is notified of a failure to connect. One address I use is 1.1.1.1/32.

Spamming software is almost always poorly written. They'll filter out 127.0.0.1, but aren't smart enough to do anything else. Those bastards will probably try to deliver mail to themselves for a week.

Which type of address you select, bogon (eg 1.1.1.1/32) or loopback depends a bit on whether you want to tie up their delivery resources immediately (1.1.1.1/32) or over a few days (loopback).

One of the issues with loopback though is that the delivery failure depends on whether they are running an MTA on 127.0.0.1. If not, they'll usually get immediate "connection failed" messages, although if they are firewalling the local host, the effect will be the same as using a bogon address.

If they are running an MTA on local host, then they'll likely get "bounce messages" with a "not a relay" message (or what ever the exact status is, I'm rusty on the exact SMTP messages).

Of course, another alternative is to delete the subdomain, meaning that the MX record lookup will fail.

Still, I prefer one of the "bad MX" address methods - there is a chance it will waste some of the resources of the spammers, increasing their costs.

Another idea, as part of this, is to create a bogus web page that contains a whole stack of these "sacrificial subdomain" email addresses. If spammers are using web page robots to collect addresses, they'll end up collecting a lot of them. That might frustrate them, such that they'll delete all email addresses for the particular domain, which, of course, would include any of your legitimate ones. You can have a look at mine here, which contains 7500 bogus addresses, covering a range of "sacrificial subdomain"s. I used 30 bogus domains, and a list of male and female names from files listed in Kevin Mitnick's book, "The Art of Deception". Using the full 30 domains, and the full male and female name list, I ended up with a 22 MB html file, with 256 000 or so addresses. I figured that was a bit too many (!) and cut it back. That being said, if my "sending" bandwidth was free or near free, it might be worth making the page around the 5 to 10 MBs in size, to also tie up spammer resources while they are running their address collecting robot.

None of these techniques are perfect, then again, if there is anything realatively simple you can do to frustrate the spammers, it is worth it. They might give up if their costs become too high.

Wikipedia has 202, IANA has 247
Guess we could do a diff on the official 193 coutries and investigate why they're claiming to be countries. My guess is there's 10 - 50 major scammers out there who've registered countries just to claim benefits from the UN ;)

There are 247 countries as far as internet domains are concerned. It all depends on who's counting.

How well this system works will in part depend upon how many data format plug-ins are provided. For example, take something like the SID audio format. It's relatively unknown, but has an officially registered MIME type with IANA giving it a status above many other file format types, and it is used to provide background sounds on some web sites. Will it make the cut?

This is just one file format chosen at random. There are thousands out there, some of which are used pretty heavily for documentation in certain circles. How about all of the OpenOffice file formats, or the AbiWord format?

I can see this feature being hugely useful if Apple does a good job of providing plug-ins, and making it easy for third-parties to add more.

Try changing ports from the defaults (6881-6889) to something else. I've heard rumours that some ISPs are throttling the transfer rates on those ports in an effort to reduce bandwidth consumption. Not suprising if BT is now sucking back 35% of net traffic. Anyways, try switching over to a different series of ports and see if that helps.

You will have to define your BabyMIB, of course, for which you will want your own Enterprise OID. A true geek would want to assign e. g. 1.3.6.1.4.1.x.1.n for the n-th kid to monitor. Below this OID you could just add any Trap OID you could imagine.

"Honey, Christine just threw a MyDiapersAreDirty trap! Standard escalation procedure!"

On the other hand, you could of course just use the old-fashioned look-with-your-own-eyes method that worked perfectly for the past few thousands years...

[Apple's] got more bandwidth than Jesus.

Unlike Xerox, GE, IBM, Ford Motors, Halliburton (what the fuck?) and, yes, Apple, Jesus doesn't have a Class A NetBlock. Plus, alongside seemingly half of the Fortune 500, Apple has it's backend provided by Akamai, and frankly, that sort of setup wouldn't ever need resurrection, because it'd never go down.

However, Jesus does have the edge in RFC 2629: Delivery of Packets via Archangel and Shepherd.

Well first thing that ran through my mind is that I should toss any resume from anyone what has a BS from Brown University. And you are full of it.

Then I saw it was for your disseration. Silly me.

So lets see if we could find a position for you, assuming you are not a professional troll.

1. Cisco is not the only network equipment vendor. And you can get wire speed IPv6 performance with Cisco or other "lesser" vendors, it depends on the product, not the 2506 you leaned on while overhearing "talking-points." Maybe Purchasing?

2. You are short sighted, so that rules out Planning or Management. Your NAT decode is fubar. There are not 4 billion addresses available if you exclude RFC 1918 non routables and class D and E are likewise unallocated as sources. But a more convincing point would have been that networks 89-126 aren't even allocated yet. Thats about 654 million addresses we still have not even handed out, and that is just the biggest chunk.

3. 56 bit ethernet addresses huh? Not going there. Massive routing tables? Have you read anything about IPv6 routing and TLA heirarchy, or come across the term aggregation in your 92.5 seconds of research? Since you can't remember numbers, and dont know what an RFC is after doing a dissertation, I'm afraid Accounting is not for you and Engineering means reading and understanding specs, so ixnay there.

4. Bloated? We went from 2x32bit addresses to 2x128bit addresses in the header, a 4x increase, yet the overall header only increased by 2x? That is not bloating, that's good engineering. Bloat is when you increase the address size 4x and the whole header grows 16x. I'm afraid you definitely are not cut out for engineering.

Since you did manage to get some buzzwords in there (some in the right order too), and seem to do reasonably well at calculating percentages, and you were able to make a nice sequentially numbered list and even do bold headers, I have the perfect career for you: Marketing.

Hint: Don't worry if you get some facts wrong in that big Powerpoint presentation to the customer. When they call and say they don't want your product afterall, you can always say, "Well what better place than the meeting room to address these points," at which point someone with a brain gets called into another stupid meeting to undo all your "talking-points."

BGP currently shows roughly 1.3B addresses as being routable. That represents a little more than 25% of the IPv4 space.

There are alot of special use /8's around and a ton of academic institutions (MIT) and large corporations (Eli Lilly, etc.) that received /8 assignments back in the day.

I can not imagine MIT utilizing 16.7M IP's, and most other /8 recipients from that time wont either.

For more information see http://www.iana.org/assignments/ipv4-address-space

40% of the IPv4 address space is unallocated, and much of the allocated space is probably unused.

Dozens of /8s are available; last time I checked it was about 40% of the total address space.

Here's a list of who owns all the Class A IP blocks

http://www.iana.org/assignments/ipv4-address-space

Its not the lack of addresses, IANA still has 2/3rds of IPv4 addresses reserved.

See here

I'm told the reason is problems routing those addresses, i.e. that to assign them would increase the size of the routing tables on the backbone routers with the associated slow-down of processing.

I don't get why we can't just use the AS system to handle this though, the routers don't all need to know the entire routing table, just a CIDR route for a bunch of associated classes.

"...the first of the IPv6 glue records will be added to the root zone on 28 June [2004]."

Hmm, might have to update a few things with the IANA first though, see http://www.iana.org/root-whois/kp.htm.

Off-topic, but how'd a conservative government like North Korea get stuck with a top-level-domain that spells "K1ddy P0rn"????

IANA | .kp - Korea, Democratic People's Republic
Root-Zone Whois Information .kp - Korea, Democratic People's Republic

Sponsoring Organization: Not assigned
Administrative Contact: Not assigned
Technical Contact: Not assigned
URL for registration services: None listed.
Whois server: None listed.

I'll bet that IANA are not going to be happy about having example.com slashdotted!

See rfc 2606 for more info on example.com

(For those who missed it, after coming up from maintenance, all links off the slashdot front page went to example.com instead of slashdot.org - ie http://example.com/comments.pl?sid=114762&threshol d=1&mode=thread&commentsort=0&op=Reply )

As of January of this year, this is the list of recognised uri schemes.

All are very specific, and none of them run arbitrary commands.

Here is the RFC for registering new URL schemes.

and here is the guidelines for creating new schemes.

Try this one: RFC 1347. IPv9 is another name for the TUBA protocol (see here), which was apparently a competing proposal of IPv6 for big-number addressing with TCP and UDP that has never been put into broad use. Some people seem to think it's superior to IPv6 in some ways, but I was under the impression that it's largely deprecated at this point. Obviously some people are still using it - perhaps they are using it as an interim solution until they can transition to IPv6 (when everyone else does - which will be a cold day in hell).

Actually IPv9 is TUBA. Which is described in RFC1347.

You seem to be complaining that Comcast's spam blocking techniques don't stop the spread of worms. The block is designed to prevent the worm from sending spam. If you want someone to whom to complain about the spread of worms, you might want to direct your anger at the blameworthy.

Actually, it's not 1.7 billion addresses. Because of the way the address space is allocated, not every potential address is available, and that's before you take into account things like CIDR (classless interdomain routing not this)

From http://www.iana.org/root-whois/iq.htm:

.iq - Iraq

Sponsoring Organization:
Alani Corp.
c/o InfoCom
630 International Parkway
Richardson, Texas 75081
United States

Administrative Contact:
Saud Alani
Alani Corporation
c/o InfoCom
630 International Parkway
Richardson, Texas 75081
United States
Email: alani@mynet.net
Voice: +964 1 556 4753
Fax: +1 972 644 8609

Technical Contact:
Bayan Elashi
InfoCom Corporation
630 International Parkway
Suit 100
Richardson, Texas 75081
United States
Email: bayan@infocomusa.com
Voice: +1 972 644 5363
Fax: +1 972 644 8609

Domain Servers:

ns1.mynet.net 63.175.195.20
ns2.mynet.net 208.21.175.13

URL for registration services: None listed.

Whois server: None listed.

Record last updated - 13-October-2002
Record created - 09-May-1997

Google indicates there were at least some .IQ domains it spidered...

IANA lists it as being there, and a little digging shows it hosted out of Texas by InfoComCorp, apparently related to Synaptix somehow.

'course, the nameserver looks rather empty. :)

058/8 Apr 04 APNIC (whois.apnic.net)
059/8 Apr 04 APNIC (whois.apnic.net)
060/8 Apr 03 APNIC (whois.apnic.net)
061/8 Apr 97 APNIC (whois.apnic.net)
202/8 May 93 APNIC (whois.apnic.net)
203/8 May 93 APNIC (whois.apnic.net)
210/8 Jun 96 APNIC (whois.apnic.net)
211/8 Jun 96 APNIC (whois.apnic.net)
218/8 Dec 00 APNIC (whois.apnic.net)
219/8 Sep 01 APNIC (whois.apnic.net)
220/8 Dec 01 APNIC (whois.apnic.net)
221/8 Jul 02 APNIC (whois.apnic.net)
222/8 Feb 03 APNIC (whois.apnic.net)

I personally think that web browsers should barf on pages that don't validate.

* No wonder it is blocked; they get failing remarks for their "master development" skillz:

File: Slashdot.htm
Doctype:
Encoding:

I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to validate the document. The sources I tried are:

• The HTTP Content-Type field.
• The XML Declaration.
• The HTML "META" element.

And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation.

Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use.

IANA maintains the list of official names for character sets.

I personally think that web browsers should barf on pages that don't validate.

* No wonder it is blocked; they get failing remarks for their "master development" skillz:

File: Slashdot.htm
Doctype:
Encoding:

I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to validate the document. The sources I tried are:

• The HTTP Content-Type field.
• The XML Declaration.
• The HTML "META" element.

And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation.

Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use.

IANA maintains the list of official names for character sets.

You've never had a right to privacy as a domain owner. If that bothers you, don't use DNS and just publish your web server's IP number.

Or:

• Look for a country-code domain that will allow you to keep your contact info private. I don't know of any that will; but I haven't really looked through the list.
• Use a proxy registration service and don't break their terms of service. (You shouldn't be spamming anyway. :-)
• Buy a subdomain from a private party. I own oligarch.com, so I could hypothetically offer to let you pay me to make NS records on oligarch.com pointing lostcluster.oligarch.com to your name servers. Presto, you now have a working domain delegated to you with none of your info in the WHOIS. True, it's not a second-level domain; but there are many situations where people find this acceptable, particularly when it's under a nice, short second-level domain (e.g., cjb.net).
• Turn off your computer. Go outside and play. <g>

And I'm sure there are other ways to go about using the DNS without putting your data in an ICANN-controlled database.

I couldn't find it on IANA's list of MAC-adresses. It should be on that list :P

As another user pointed out, you don't need to have Apache 2 running as your webserver if you want to access Subversion. You can do one of the following:

• Run Apache 1.x as your webserver on port 80, and then have Apache 2.x running side-by-side as a separate server and have it listen on port 3690, the port that IANA has reserved for the Subversion protocol.
• Instead of Apache, run the lightweight Subversion server svnserve. It's quite simple to set up compared to Apache, but can only grant blanket read/write permissions. Also, you can't fine-tune permissions on a per-directory basis like you can with Apache.
• If you have pre-existing accounts on your system, you can tunnel through ssh via the svn+ssh://host/path/to/repo pragma which will authenticate itself via ssh and use the Unix file permissions on the repository.
• If you are the only one accessing your repository, you can even use the file:///path/to/repo pragma and forego a server altogether.

Thomas