IETF draft: Content-Digest and Want-Content-Digest

A heads up about [draft-ietf-httpbis-digest-headers-06](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-digest-headers-06):

> This document defines HTTP fields that support integrity checksums. The `Digest` field can be used for the integrity of HTTP representations.
> The `Content-Digest` field can be used for the integrity of HTTP message content. `Want-Digest` and `Want-Content-Digest` can be used to indicate a sender's desire to receive integrity fields respectively.

It’s an IETF standardization effort of interest to IPFS integration efforts into web browsers. The standardized `Content-Digest: cid=bafy..` response header could replace `x-ipfs-path: /ipfs/bafy..`. The standardized `Want-Content-Digest: cid` request header could be used by clients to indicate they support IPFS.

Start by reading draft-ietf-httpbis-digest-headers-06 and the issue's context on IPFS integration in web browsers. The payload does not identify a repository file, entry point, test, or concrete implementation target, so the expected completion criteria need to be clarified before work can begin.

Written by the indexing model from the issue text.