Brandon Mitchell

> Wondering if there a circular argument here? > > Firstly, only the following appears to be registered with IANA. [application/vnd.oci.image.manifest.v1+json](https://www.iana.org/assignments/media-types/application/vnd.oci.image.manifest.v1+json) > > So to add a new layer type,...

> We noticed that the index manifest `sha256:be25`, and reference manifest `sha256:a77a` & `sha256:f2a0` all contain a `Subject` field. My questions are: > > 1. Should the reference manifest `sha256:a77a`...

> From my understanding, the image index serves as a collection of multiple image manifests rather than an image manifest itself, so it may not have a specific meaning in...

Does this affect Docker's streaming method for a blob push (not defined by OCI yet, but since it's used by docker it's well supported by registries), non-chunked pushes (used by...

Docker's streaming API uses a patch request without a content-length value. It's effectively the same as a post/put, but the digest is not known in advance, so they push the...

> For proxies or platforms like Workers they buffer the request body. So it would be nice to tell the client (like Docker) to limit the request body to a...

I believe ordered by popularity, there's: 1. POST/PUT 2. Docker's streaming PATCH 3. Chunked POST/PATCH/PUT 4. Single POST The only method covered by this PR would be 3. OCI hasn't...

For reference, the streaming patch is defined in the [distribution project](https://distribution.github.io/distribution/spec/api/#stream-upload). In practice, this was implemented as a POST / single PATCH (no length or range header) / PUT. I...

Yes, I believe docker was using the API that I linked above. Changing the behavior of the docker client or the distribution registry should be easy. Making sure that such...

The difference between the two PRs is the problem being solved with the feature, which APIs it applies to, and how that change will affect existing implementations. #391 was focused...