AFS Assigned Numbers Registry - Rx services This is a registry of the Rx service ID codes used for various Rx-based application services. These codes are used to differentiate requests for different Rx services operating on the same transport endpoint. In most cases, each service has its own distinct service ID; this allows several services to be multiplexed on a single port, depending on the needs of the server. However, a few services have duplicate IDs, and so cannot be combined. In these cases, the registry indicates the UDP port number on which each service is normally used. ID Name Description Contact ======= ========== ======================================== ======================================== 0 Reserved 1 RXAFSCB AFS cache manager callback AFS3 Standardization Group Chairs 1 BOZO (port 7007) Basic OverSeer AFS3 Standardization Group Chairs 1 RXAFS (port 7000) AFS fileserver AFS3 Standardization Group Chairs 1 TC (port 7025+) AFS backup tape controller AFS3 Standardization Group Chairs 1 TDB (port 5001) Stage tape database Chaskiel Grundman 2 RXAFSOSD (port 7000) AFS OSD https://github.com/hwr/openafs-osd 4 AFSVol (port 7005) AFS volume management AFS3 Standardization Group Chairs 4 UPDATE (port 7008) AFS software update AFS3 Standardization Group Chairs 4 RMTSYS (port 7009) AFS remote syscall AFS3 Standardization Group Chairs 7 AFSOSDVOL (port 7005) AFS OSD volume management https://github.com/hwr/openafs-osd 13 OSDDB (port 7003) AFS OSD database https://github.com/hwr/openafs-osd 23 tt Stage remote control (tos) Chaskiel Grundman 50 VOTE Ubik vote/quorum AFS3 Standardization Group Chairs 51 DISK Ubik disk I/O AFS3 Standardization Group Chairs 52 SAMPLE Sample Ubik application AFS3 Standardization Group Chairs 52 VL (port 7003) AFS volume location AFS3 Standardization Group Chairs 73 PR AFS protection database AFS3 Standardization Group Chairs 99 HAFS hostafs control Jeffrey Hutzelman 409 RXSTATS rx statistics AFS3 Standardization Group Chairs 731 KAA kaserver auth AFS3 Standardization Group Chairs 732 KAT kaserver tgs AFS3 Standardization Group Chairs 733 KAM kaserver admin AFS3 Standardization Group Chairs 900 RXOSD (port 7006) RXOSD services https://github.com/hwr/openafs-osd 2500 YFSBOZO (port 7007) YFS Basic OverSeer afs3@auristor.com 2500 YFS YFS fileserver afs3@auristor.com 2501 YFSCB YFS cache manager callback extensions afs3@auristor.com 2502 YFSVol YFS volume management extensions afs3@auristor.com 2503 YFSVL YFS volume location extensions afs3@auristor.com 2504 YFSPR YFS protection database extensions afs3@auristor.com 2505 YFSStats YFS rx statistics extensions afs3@auristor.com 2506 YFSVote YFS Ubik vote/quorum extensions afs3@auristor.com 2507 YFSDisk YFS Ubik disk I/O extensions afs3@auristor.com 2508 YFSRXGK YFS rxgk extensions afs3@auristor.com 2509 YFSUPDATE YFS Software Update afs3@auristor.com 2510 YFSPROBE YFS Probe Service afs3@auristor.com 2511 YFSBUDB YFS Backup Database afs3@auristor.com 22314 BUDB AFS backup database AFS3 Standardization Group Chairs 60289 RXKST rxkad stress test AFS3 Standardization Group Chairs 34567 rxgk security negotiation AFS3 Standardization Group Chairs >=64512 Reserved - site local use ** Registration Policy New Rx service IDs are assigned on a first-come, first-served basis, except for ID 0, which is reserved and cannot be assigned, and IDs in the range 64512-65536, which are reserved for site-local use. All requests must include the service name and description. A specific number may be requested; the registars will attempt to satisfy such requests subject to availability. For services which are subject to standardization as part of the AFS3 protocol suite, numbers will be assigned when a document is approved, or earlier if requested by the AFS3 standardization group chairs. The point of contact for such services will be the chairs, and the RPC number space will be managed by the registrar. Documents creating standardized services must contain a list of RPCs suitable for use in constructing the initial registry contents. For "private" services which are not part of the AFS3 protocol suite, numbers will be assigned on request. An interface description is desirable but is not required. The registrar will not manage the RPC number space for such services, but will publish a link to an external reference if requested. ** UDP Port Registration The Rx protocol is layered on top of UDP, and thus any Rx service must listen on some UDP port. While service ID's may be used to multiplex more than one service on the same port (normally when multiple services are provided by the same process), they do not serve as a substitute for proper registration of the UDP ports used. Except when a new service is explicitly designed to always be co-located with an existing one, designers are encouraged to conserve UDP port namespace by avoiding the use of well-known ports in favor of using DNS SRV records or other means of discovery. Any service names or UDP port numbers used should be properly registered with the Internet Assigned Numbers Authority, which manages those namespaces.