refactor: move DHT endpoint to separate section

- create new "DHT Routing API" section for DHT-specific operations
- move /routing/v1/dht/closest/{peer-id} to the new DHT section
- keep general peer lookup in "Peer Routing API" section
- update cache value to 172800 (48h) for consistency
- fix typo: "Query Paramters" -> "Query Parameters"

Author: lidel

src/routing/http-routing-v1.md

@@ -106,23 +106,16 @@ Each object in the `Providers` list is a record conforming to a schema, usually
 
 ## Peer Routing API
 
-### `GET /routing/v1/dht/closest/{peer-id}?[closerThan]&[count]`
+### `GET /routing/v1/peers/{peer-id}`
 
 #### Path Parameters
 
-- `peer-id` is a [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) represented as a CIDv1 encoded with `libp2p-key` codec.
-
-#### Query Paramters
-
-- `closerThan` is an optional [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) represented as a CIDv1 encoded with `libp2p-key` codec.
-  - Returned peer records must be closer to `peer-id` than `closerThan`.
-  - If omitted the routing implementation should use its own [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md).
-- `count` is an optional number that specifies how many peer records the requester desires.
-  - Minimum 1, maximum 100, default 20.
+- `peer-id` is the [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) to fetch peer records for,
+represented as a CIDv1 encoded with `libp2p-key` codec.
 
 #### Response Status Codes
 
-- `200` (OK): the response body contains peer records.
+- `200` (OK): the response body contains the peer record.
 - `404` (Not Found): must be returned if no matching records are found.
 - `422` (Unprocessable Entity): request does not conform to schema or semantic constraints.
 
@@ -134,7 +127,7 @@ Each object in the `Providers` list is a record conforming to a schema, usually
   - When present, `ttl` SHOULD be shorter for responses whose resolution ended in no results (e.g. 15 seconds),
     and longer for responses that have results (e.g. 5 minutes).
   - Implementations SHOULD include `max-ttl`, set to the maximum cache window of the underlying routing system.
-    For example, if Amino DHT results are returned, `stale-while-revalidate` SHOULD be set to `79200` (22h, which at the time of writing this specification, is the [Provider Record Republish Interval](https://github.com/libp2p/specs/tree/master/kad-dht#content-provider-advertisement-and-discovery)).
+    For example, if Amino DHT results are returned, `stale-while-revalidate` SHOULD be set to `172800` (48h, which at the time of writing this specification, is the provider record expiration window).
 - `Vary: Accept`: allows intermediate caches to play nicely with the different possible content types.
 
 #### Response Body
@@ -154,22 +147,31 @@ Each object in the `Providers` list is a record conforming to a schema, usually
 }
 ```
 
-The number of peer records in the responses SHOULD be limited to the `count` query parameter, which defaults to 20 if unspecified.
+The `application/json` responses SHOULD be limited to 100 peers.
 
 The client SHOULD be able to make a request with `Accept: application/x-ndjson` and get a [stream](#streaming) with more results.
 
 Each object in the `Peers` list is a record conforming to the [Peer Schema](#peer-schema).
 
-### `GET /routing/v1/peers/{peer-id}`
+## DHT Routing API
+
+### `GET /routing/v1/dht/closest/{peer-id}?[closerThan]&[count]`
 
 #### Path Parameters
 
-- `peer-id` is the [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) to fetch peer records for,
-represented as a CIDv1 encoded with `libp2p-key` codec.
+- `peer-id` is a [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) represented as a CIDv1 encoded with `libp2p-key` codec.
+
+#### Query Parameters
+
+- `closerThan` is an optional [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md) represented as a CIDv1 encoded with `libp2p-key` codec.
+  - Returned peer records must be closer to `peer-id` than `closerThan`.
+  - If omitted the routing implementation should use its own [Peer ID](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md).
+- `count` is an optional number that specifies how many peer records the requester desires.
+  - Minimum 1, maximum 100, default 20.
 
 #### Response Status Codes
 
-- `200` (OK): the response body contains the peer record.
+- `200` (OK): the response body contains peer records.
 - `404` (Not Found): must be returned if no matching records are found.
 - `422` (Unprocessable Entity): request does not conform to schema or semantic constraints.
 
@@ -201,7 +203,7 @@ represented as a CIDv1 encoded with `libp2p-key` codec.
 }
 ```
 
-The `application/json` responses SHOULD be limited to 100 peers.
+The number of peer records in the responses SHOULD be limited to the `count` query parameter, which defaults to 20 if unspecified.
 
 The client SHOULD be able to make a request with `Accept: application/x-ndjson` and get a [stream](#streaming) with more results.