Moving Crypt4GH into its own GitHub repo

The Crypt4GH encrypted file format standard is currently part of the hts-specs repo, where it lives next to the SAM, BAM, CRAM, VCF, BED file format standards: https://github.com/samtools/hts-specs. The reason it was placed in there was originally that it is essentially another file format standard (not an API, etc). And samtools was actually the first tool that natively supported it.

However, there have been calls to move Crypt4GH into its own GitHub repo instead; which is reasonable. We have two questions:

1 - Is this a good idea? Does it fit with the larger view on standards in the GA4GH?

2 - What would be the best name/location for this new repo? (Is there a naming scheme that differentiates between standards, implementations, APIs, etc. in https://github.com/ga4gh/?)