From jaltman@auristor.com Tue Jun 6 18:05:23 2023 From: jaltman@auristor.com (Jeffrey E Altman) Date: Tue, 6 Jun 2023 13:05:23 -0400 Subject: [OpenAFS-devel] Re: Request to create a Dump Tag registry In-Reply-To: <2ba1c266-9534-f915-b12f-1b52d3f6ab22@auristor.com> References: <2ba1c266-9534-f915-b12f-1b52d3f6ab22@auristor.com> Message-ID: <9533cb7f-7cb2-5677-59df-ea3c729f22a5@auristor.com> This is a cryptographically signed message in MIME format. --------------ms030109060102080507090307 Content-Type: multipart/alternative; boundary="------------dHuDpiD0IAP5oL0rS90A0tAk" --------------dHuDpiD0IAP5oL0rS90A0tAk Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/12/2022 11:40 PM, Jeffrey E Altman (jaltman@auristor.com) wrote: > > AuriStor has been investigating extending the Dump Stream to support > the functionality proposed in April 2011 as RPC Refresh (Gerrit 4573) > as well as additional data and metadata types implemented by > AuriStorFS. To avoid unnecessary collisions and to maximize > interoperability I propose the creation of a Dump Tag Registry. > > The Dump Format is poorly documented and many tags and sub-tags have > been squatted upon over the years without creation of a registry. > The dump stream registry has been created. It is linked from http://registrar.central.org/. > I will provide additional details of the AuriStor sub-tags to the > Registrar once a Registry has been published. > The 3 June 2023 draft of the "AFS Dump Stream Format" document that I written is available at http://registrar.central.org/dump/dump_format.txt I will reference this document in my AFS Technology Workshop presentation "An Overview of the Dump Stream Framework Adopted by OpenAFS and the Dump Tag Registry" on Wednesday 14 June 2023 at 2:20pm EDT (UTC-4). To register for the workshop which will be held virtually via Zoom Events (50 USD) the link https://workshop.openafs.org/afsbpw23/ redirects to https://events.zoom.us/e/view/vqOro4A_RfGeHNSVWD4Yvw Hope to see you there. Jeffrey Altman --------------dHuDpiD0IAP5oL0rS90A0tAk Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
AuriStor has been investigating extending the Dump Stream to support the functionality proposed in April 2011 as RPC Refresh (Gerrit 4573) as well as additional data and metadata types implemented by AuriStorFS. To avoid unnecessary collisions and to maximize interoperability I propose the creation of a Dump Tag Registry.
The Dump Format is poorly documented and many tags and sub-tags have been squatted upon over the years without creation of a registry.
The dump stream registry has been created. It is linked from
http://registrar.central.org/.
I will provide additional details of the AuriStor sub-tags to the Registrar once a Registry has been published.
The 3 June 2023 draft of the "AFS Dump Stream Format" document that I written is available at http://registrar.central.org/dump/dump_format.txt
I will reference this document in my AFS Technology Workshop
presentation "An Overview of the Dump Stream Framework Adopted by
OpenAFS and the Dump Tag Registry" on Wednesday 14 June 2023 at
2:20pm EDT (UTC-4).
To register for the workshop which will be held virtually via Zoom Events (50 USD) the link https://workshop.openafs.org/afsbpw23/ redirects to https://events.zoom.us/e/view/vqOro4A_RfGeHNSVWD4Yvw
Hope to see you there.
Jeffrey Altman
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 registrar@grand.central.org 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.
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 registrar@grand.central,org.
Thank you.
Jeffrey Altman