Follow-up to #39, which made 6674 fastcached's default TCP port.
6674 was chosen precisely because nobody else has claimed it — unassigned in the IANA Service Name and Transport Protocol Port Number Registry, and absent from nmap-services entirely. Having picked it on the grounds that squatting another project's registered port is the wrong thing to do, registering it is the consistent finish. Until then our claim rests on nothing but the number being empty today, and someone else can register it out from under us.
This is paperwork, not code. The port works regardless, so this is not urgent — but it should not be dropped either.
What to file
Registration goes through the IANA ports & services form. The procedure is RFC 6335; assignments in the User Ports range go to Expert Review, so expect a review cycle measured in weeks, and expect questions.
Fields to prepare:
| Field |
Proposed value |
| Service name |
fastcache |
| Transport protocol |
TCP (we do not use UDP — request TCP only) |
| Port number |
6674 |
| Description |
fastcached cache daemon |
| Assignee / contact |
LASTRADA Software |
| Reference |
https://github.com/LASTRADA-Software/fastcached and the protocol docs |
Things the reviewer will likely probe
- Why a port number at all, given we auto-detect the protocol. The honest answer is that the assignment identifies the service, not a wire format — the daemon serves memcached text, memcached binary, memcached meta, RESP2 and our own
0xFC compile-cache protocol on the same listener. RFC 6335 wants one service name per assignment, so fastcache should be described as the cache service, with protocol autodetection noted as an implementation property.
- Whether an existing assignment suffices. It does not: we are not memcached and not redis, and defaulting to their ports is the collision this change exists to remove.
- UDP. Do not request it. We have no UDP listener, and RFC 6335 discourages speculative assignment of the sibling protocol.
Definition of done
If the application is rejected or stalls, that is worth knowing explicitly rather than silently — 6674 stays our default in any case.
Follow-up to #39, which made 6674 fastcached's default TCP port.
6674 was chosen precisely because nobody else has claimed it — unassigned in the IANA Service Name and Transport Protocol Port Number Registry, and absent from
nmap-servicesentirely. Having picked it on the grounds that squatting another project's registered port is the wrong thing to do, registering it is the consistent finish. Until then our claim rests on nothing but the number being empty today, and someone else can register it out from under us.This is paperwork, not code. The port works regardless, so this is not urgent — but it should not be dropped either.
What to file
Registration goes through the IANA ports & services form. The procedure is RFC 6335; assignments in the User Ports range go to Expert Review, so expect a review cycle measured in weeks, and expect questions.
Fields to prepare:
fastcacheThings the reviewer will likely probe
0xFCcompile-cache protocol on the same listener. RFC 6335 wants one service name per assignment, sofastcacheshould be described as the cache service, with protocol autodetection noted as an implementation property.Definition of done
docs/getting-started/install.mdunder Ports and in theDefaultPortdoc comment insrc/FastCache/Config/Config.hpp, both of which currently say only that the port is unassignedIf the application is rejected or stalls, that is worth knowing explicitly rather than silently — 6674 stays our default in any case.