AFS Assigned Numbers Registry has been updated

The AFS Assigned Numbers Registry, http://registrar.central.org/, was 
created in 2011 as a successor to the older non-authoritative listings 
maintained at http://www.central.org/numbers/index.html.

Since 2014 requests submitted to [email protected] have been 
responded to and assignments have been issued, but the visible registry 
pages have not been updated.   As a result, allocations made by the 
registrar have not be visible to the community.

The registry pages are now believed to be up to date.   At the very 
least, they contain all of the allocated values that have been assigned 
by the registrars.

The lack of visibility of assignments has been particularly problematic 
for error tables additions have been coordinated with the registry 
leading to conflicts. The following Gerrit issues have been submitted in 
an effort to synchronize the error tables used by OpenAFS with those in 
use by other implementations.

  * RXGK - https://gerrit.openafs.org/#/c/15467/
  * BZ - https://gerrit.openafs.org/#/c/15468/
  * CMD - https://gerrit.openafs.org/#/c/15469/
  * U - https://gerrit.openafs.org/#/c/15470/

During the review of source trees available for review by the registrar 
it was noted that opcode AFSVol 65552 which was assigned by the 
registrar to AFSVol_GetCapabilities in 2006 for use in implemented 
compressed dump format support was later used by openafs-osd for 
AFSVol_OsdPolicyUsage.  openafs-osd made use of 65552 through 65555 
without registration even though registration had been requested for 
eleven prior AFSVol opcodes not in use by OpenAFS.  The 
AFSVol_GetCapabiliites RPC is not implemented by OpenAFS but was 
implemented by the original requestor and has been implemented by 
AuriStorFS on the assumption that OpenAFS would implement it someday.   
This conflict potentially prevents deployment of openafs-osd volservers 
within the same cell as other AFS-family servers.

During the 2023 AFS Tech Workshop it was noted that some sites have 
deployed private Rx Services on the standard AFS3 ports and have done so 
without registration. As a reminder, allocation of new Rx Service IDs 
for use on standard AFS3 ports must be registered before use to avoid 
conflicts.  This is true for all ID values excluding the site local use 
range 64512-65536.  The registrar will not manage the RPC number space 
for private services but is willing to publish the private allocations.

Please review the registry contents. If there are missing entries, 
please submit requests to add them to [email protected],org.

Thank you.

Jeffrey Altman