I would welcome a PR on this. The language for this kind of extensibility ought to allow for future permutations as well, even if it calls out explicitly `+zstd` for now.

…

On Mon, Aug 5, 2019 at 6:19 AM Aleksa Sarai [see §317C(6)] < ***@***.***> wrote: Sounds like a good idea to me, the main question is whether we should require support or define it as a SHOULD (such that we define +zstd to mean something specific without requiring everyone implement support). Though, given there is a C library (used fairly widely now) and implementations for Go and Rust, I'd be willing to argue that implementing support shouldn't be an onerous requirement for image consumers. Does anyone want to volunteer to do the PR, or should I? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#787?email_source=notifications&email_token=AAAQL2OEN2LDOYTZ5RBPJKTQC75DPA5CNFSM4II6WKK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3RMC7Y#issuecomment-518177151>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAQL2LCAYGY4YYMYX7KPY3QC75DPANCNFSM4II6WKKQ> .

add application/vnd.oci.image.layer.v1.tar+zstd to official media type? #787

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions