Merge branch 'main' into ipns-v2-only

Author: lidel

IPIP/0000-template.md

@@ -1 +1 @@
-Moved to [../ipip-template.md].
+Moved to [`../ipip-template.md`](../ipip-template.md).

ipip-template.md

@@ -36,13 +36,6 @@ interoperable implementations.
 When modifying an existing specification file, this section should provide a
 summary of changes. When adding new specification files, list all of them.
 
-## Test fixtures
-
-List relevant CIDs. Describe how implementations can use them to determine
-specification compliance. This section can be skipped if IPIP does not deal
-with the way IPFS handles content-addressed data, or the modified specification
-file already includes this information.
-
 ## Design rationale
 
 The rationale fleshes out the specification by describing what motivated
@@ -67,6 +60,13 @@ Explain the security implications/considerations relevant to the proposed change
 
 Describe alternate designs that were considered and related work.
 
+## Test fixtures
+
+List relevant CIDs. Describe how implementations can use them to determine
+specification compliance. This section can be skipped if IPIP does not deal
+with the way IPFS handles content-addressed data, or the modified specification
+file already includes this information.
+
 ### Copyright
 
 Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

src/http-gateways/path-gateway.md

@@ -21,6 +21,9 @@ editors:
     url: https://hacdias.com/
 xref:
   - url
+  - trustless-gateway
+  - ipip-0402
+  - ipip-0412
 tags: ['httpGateways', 'lowLevelHttpGateways']
 order: 0
 ---
@@ -142,15 +145,22 @@ For example:
 
 ### `Range` (request header)
 
-`Range` can be used for requesting specific byte ranges of UnixFS files and raw
+`Range` can be used for requesting specific byte range of UnixFS files and raw
 blocks.
 
 Gateway implementations SHOULD be smart enough to require only the minimal DAG subset
 necessary for handling the range request.
 
-NOTE: for more advanced use cases such as partial DAG/CAR streaming, or
-non-UnixFS data structures, see the `selector` query parameter
-[proposal](https://github.com/ipfs/go-ipfs/issues/8769).
+Gateways SHOULD support single range requests. The support of more than one
+range is optional: implementation MAY decide to not support more than one range.
+
+:::note
+
+For more advanced use cases such as partial DAG/CAR streaming, or non-UnixFS
+data structures, see `dag-scope` and `entity-bytes` from :cite[ipip-0402] and
+ordered CARs from :cite[ipip-0412].
+
+:::
 
 ### `Service-Worker` (request header)
 
@@ -214,11 +224,13 @@ These are the equivalents:
 - `format=cbor` → `Accept: application/cbor`
 - `format=ipns-record` → `Accept: application/vnd.ipfs.ipns-record`
 
-<!-- TODO Planned: https://github.com/ipfs/go-ipfs/issues/8769
-- `selector=<cid>`  can be used for passing a CID with [IPLD selector](https://ipld.io/specs/selectors)
-    - Selector should be in dag-json or dag-cbor format
-    - This is a powerful primitive that allows for fetching subsets of data in specific order, either as raw bytes, or a CAR stream. Think “HTTP range requests”, but for IPLD, and more powerful.
--->
+### `dag-scope` (request query parameter)
+
+Only used on CAR requests, same as :ref[dag-scope] from :cite[trustless-gateway].
+
+### `entity-bytes` (request query parameter)
+
+Only used on CAR requests, same as :ref[entity-bytes] from :cite[trustless-gateway].
 
 # HTTP Response
 
@@ -592,7 +604,7 @@ The following response types require an explicit opt-in, can only be requested w
 - Raw Block (`?format=raw`)
   - Opaque bytes, see [application/vnd.ipld.raw](https://www.iana.org/assignments/media-types/application/vnd.ipld.raw).
 - CAR (`?format=car`)
-  - Arbitrary DAG as a verifiable CAR file or a stream, see [application/vnd.ipld.car](https://www.iana.org/assignments/media-types/application/vnd.ipld.car).
+  - A CAR file or a stream that contains all blocks required to trustlessly verify the requested content path query, see [application/vnd.ipld.car](https://www.iana.org/assignments/media-types/application/vnd.ipld.car) and Section 5 (CAR Responses) at :cite[trustless-gateway].
 - TAR (`?format=tar`)
   - Deserialized UnixFS files and directories as a TAR file or a stream, see :cite[ipip-0288].
 - IPNS Record