Cleanup from the move from "Reframe" to "HTTP Delegated Routing"

[guseggert]

Done Criteria

Code and docs are clear that "HTTP Delegated Routing" is what is supported/maintained currently. References to Reframe should be updated.

Why Important

Now that we have the /routing/v1 HTTP API client integrated, and Reframe has been deprecated for two releases (0.17, 0.18), we should remove it in 0.19 to avoid user confusion.

Notes

Cleanup items

Preview Give feedback

1. Kubo code
2. Rebrand "HTTP delegated routing" as Reframe v1 (per discussion 3/20/23 it'll be called "Routing v1") in specs
3. Deprecate https://github.com/ipfs/go-delegated-routing and add a pointer to https://github.com/ipfs/go-libipfs/tree/main/routing/http
4. Remove reframe specs feat: remove reframe specs#372
5. Ensure https://github.com/ipfs/boxo/tree/main/routing/http#readme is accurate with what the module does (part of feat(routing/http)!: delegated peer routing server and client, IPIP 417 boxo#422)
6. https://github.com/ipfs-shipyard/someguy
7. chore: finish reframe deprecation ipfs-blog#675
   +0
8. chore: finish reframe removal #10372
   skip/changelog +1

[lidel]

cc @tinytb @achingbrain for visibility, as some of this impacts routing options for JS in browser.

Namely, if we don't plan to do delegated routing over libp2p protocol any time soon, then at very least we need DHT(+HTTP IPNI) racing proxy at routing.delegate.ipfs.io/, and that means we need to update someguy to IPIP-337

[aschmahmann]

@lidel correct, but also IPIP-337 is insufficient as is in that it doesn't support streaming, nor does it support IPNS. While in theory you could rely on IPIP-351 for IPNS resolution it too will not support streaming.

Perhaps you could argue IPNS doesn't want streaming, and endpoints should just use some heuristic to decide on their end what's "good enough" and return a single value, however that could also cause problems with consistency among IPNS records with overlapping validity (e.g. someone who publishes updates daily with record EOLs a year in the future).

[BigLep]

2023-03-20 discussion amongst @guseggert @lidel and @aschmahmann was to name this "Routing v1 HTTP API"

[lidel]

reassigning to @hacdias as he already had to remove remaining Reframe references from Kubo in #9932 👍

[hacdias]

I think as of #9877, we can successfully close this.

[BigLep]

@hacdias: a couple of thoughts:

1. Is there more removal/cleanup we should do in Kubo: https://github.com/search?q=repo%3Aipfs%2Fkubo%20reframe&type=code ?
2. Maybe add a followup note to to https://blog.ipfs.tech/2022-09-02-introducing-reframe/ (can be as a discussion form comment or in the blog post itself) saying that reframe has been replaced by /routing/v1 (and ideally link to the IPIP where the justification was provided)