docs(changelog) ipip-412

ipfs · Jul 13, 2023 · b52d913 · b52d913
1 parent 64244db
commit b52d913
Showing 1 changed file with 21 additions and 5 deletions.
diff --git a/docs/changelogs/v0.22.md b/docs/changelogs/v0.22.md
@@ -6,7 +6,7 @@
 
 - [Overview](#overview)
 - [🔦 Highlights](#-highlights)
-  - [Gateway: support for `order=` and `dups=` parameter (IPIP-412)](#gateway-support-for-order-and-dups-parameter-ipip-412)
+  - [Gateway: support for `order=` and `dups=` parameters (IPIP-412)](#gateway-support-for-order-and-dups-parameters-ipip-412)
   - [`ipfs name publish` now supports V2 only IPNS records](#ipfs-name-publish-now-supports-v2-only-ipns-records)
 - [📝 Changelog](#-changelog)
 - [👨‍👩‍👧‍👦 Contributors](#-contributors)
@@ -15,11 +15,27 @@
 
 ### 🔦 Highlights
 
-#### Gateway: support for `order=` and `dups=` parameter (IPIP-412)
+#### Gateway: support for `order=` and `dups=` parameters (IPIP-412)
 
-The gateway now supports optional CAR parameters via the `Accept` header, as
-specified in [IPIP-412](https://github.com/ipfs/specs/pull/412). By default,
-order is DFS and there are no duplicates.
+The updated [`boxo/gateway` library](https://github.com/ipfs/boxo/tree/main/gateway)
+introduces support for ordered CAR responses through the inclusion of optional
+CAR content type parameters: `order=dfs` and `dups=y|n` from
+[IPIP-412](https://github.com/ipfs/specs/pull/412).
+
+Previously, Kubo already provided CARs in DFS order without duplicate blocks.
+With the implementation of IPIP-412, this behavior is now explicitly defined
+rather than implied.
+
+In the absence of `dups` or `order` in `Accept` request reader, the default CAR
+response will have the `Content-Type: application/vnd.ipld.car; version=1; order=dfs; dups=n`
+and the same blocks as Kubo 0.21.
+
+Kubo 0.22 still only supports DFS block ordering (`order=dfs`). However, it is
+now possible to request a DFS CAR stream with duplicate blocks by opting in via
+`Accept: application/vnd.ipld.car; order=dfs; dups=y`. This opt-in feature can be
+beneficial for memory-constrained clients and IoT devices, as it allows for
+streaming large DAGs without the need to store all previously encountered
+blocks in memory.
 
 #### `ipfs name publish` now supports V2 only IPNS records