Identifier numbers
An identifier number labels something because an organisation assigned it, not because it measures anything. RFC 911, HTTP 404, ISO 9001, TCP port 443 and the Intel 4004 are all numbers whose meaning comes entirely from a registry entry — outside that registry they are just numbers, and inside it they are precise.
This is the largest class of numbers in the catalogue and the one least like the others. A prime is prime whoever is counting; 404 means "not found" only because a committee wrote it down, and it would have worked just as well as 407. What these numbers share is provenance rather than subject: each was issued by a body — the IETF, ISO, IANA, IEEE, a manufacturer, an astronomical survey — and each carries authority only within that system. The interesting cases are the ones that escaped: 404 and 747 are used by people who have never heard of the registries that assigned them, while RFC 911 shares its value with an emergency number and means something entirely unrelated.
Why numbers become identifiers
A registry needs to hand out labels that are unique, permanent and uncontroversial. Names fail on all three: they get argued over, they need translating, and they go stale when the thing they name is revised. Numbers fail on none of them. The next document is simply the next number, and nobody has to agree what it should be called.
The cost is that the label carries no information. You cannot tell from the value that RFC 793 specifies TCP, that ISO 9001 is about quality management, or that the Intel 4004 was the first commercially available microprocessor. Every one of those has to be looked up — which is precisely what a registry is for.
Who assigns them
The registries in this hub are independent of one another and use incompatible schemes. The IETF numbers its documents in one continuous sequence stretching back to 1969, so a low RFC number means an old document and nothing else. ISO and IECissue catalogue numbers that group loosely by subject but are never reused, so a withdrawn standard's number stays withdrawn. IANA assigns port numbers from a range where anything below 1024 requires privilege to bind — one of the few cases where the value carries a real consequence.
Outside computing the pattern repeats. Astronomical catalogues number objects in the order they were observed, minor planets in the order their orbits were confirmed, and the UN dangerous goods list assigns a number to a substance so a responder can identify a tanker without asking the driver. Manufacturers number parts, and a few of those numbers — 555, 741, 747 — became the everyday name of the thing itself.
When the number escapes the registry
A handful of identifiers are recognised by people who have never heard of the body that issued them. 404is the clearest case: it appears on posters and in conversation as a word meaning "missing", entirely detached from the status code registry that defines it. 747 and 911 are model numbers used as the names of the aircraft and the car.
The reverse also happens. RFC 911 documents a 1984 gateway protocol and shares its value with the American emergency number by pure coincidence — two registries reaching the same figure with no connection whatsoever. That is the ordinary situation, and it is why an identifier always needs its registry named alongside it.
How to read an identifier on this site
Every identifier record here names the body that issued it and the period it has been in force, because those are the only facts that make the number mean anything. Where a value is used by more than one registry — and with over a hundred identifiers in the catalogue that is common — each meaning is recorded separately on the same number's profile rather than merged. 718 is a Porsche and a nickel superalloy; 1149 is an April Fools' RFC about carrier pigeons and the JTAG boundary scan standard. Neither pairing implies anything.
Identifier numbers in the catalogue
22
53
80
100
101
171
200
201
202
204
206
207
216
226
301
302
303
304
307
308
400
401
402
403
404
405
407
408
409
410
412
413
414
415
416
417
418
421
422
423
424
425
426
428
429
431
443
451
500
502
503
504
505
506
507
508
510
511
519
520
521
522
523
525
530
555
565
621
741
747
754
759
768
791
793
802
911
917
1003
1149
1203
1394
1588
1918
2068
2108
2324
2616
3166
3297
3,306
3480
4004
4217
4486
5150
6346
6502
6581
7230
7231
7400
7807
7810
8,080
8086
8446
8583
8601
9001
9110
9111
9112
9113
11,801
14,001
26,262
27,001
42,001
60,103
60,529
61,508
62,443
68,000
80,386
101,955
134,340
Common questions
What is an identifier number?
A number that labels something because an organisation assigned it, rather than because it counts or measures anything. RFC 911, ISO 9001, TCP port 443 and the Intel 4004 are identifiers: each means something precise inside the registry that issued it and nothing at all outside it.
Why do organisations use numbers instead of names?
Numbers can be issued in sequence without argument, they do not need translating, and they stay stable when a document is rewritten or a product is renamed. A committee can agree that the next document is 8446 far more easily than it can agree what to call it.
Does the value of an identifier mean anything?
Almost never. HTTP 404 would have worked just as well as 407, and minor planet numbers are issued in the order orbits are confirmed rather than by any property of the object. A few registries do encode meaning — HTTP groups 4xx as client errors and 5xx as server errors — but that is a property of the scheme, not of the number.
Is an identifier number significant in the way a prime is?
No, and the distinction matters. A prime is prime whoever is counting. An identifier is significant only because a body wrote it down, which is why Numberwise records who assigned it and when rather than treating the value itself as meaningful.