Opened 5 years ago
Closed 3 years ago
#1465 closed enhancement (fixed)
Add introduction tag request to SSU
| Reported by: | zzz | Owned by: | zzz |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.24 |
| Component: | router/transport | Version: | 0.9.17 |
| Keywords: | Cc: | ||
| Parent Tickets: | Sensitive: | no |
Description
Routers can have trouble getting an introducer tag at times of congestion and at startup.
Bob doesn't know if Alice is firewalled when she sends the Session Request. So Bob can either offer an introduction tag, or not, in the Session Created. But Bob only has a limited number of routers he can offer for, since these sessions must stay up a long time. If Bob knew that Alice needed one, he could definitely give her one, and not give them to the routers that don't need them.
This would require an extra byte in the Session Request message.
Or, Bob could take a guess based on the incoming IP/port and a look through the netdb or other data structures.
Subtickets
Change History (3)
comment:1 Changed 4 years ago by
comment:2 Changed 4 years ago by
| Milestone: | eventually → 0.9.24 |
|---|---|
| Status: | new → accepted |
Surprise! There's an unused extended options field in the SSU header. I propose that we use it.
Details: http://zzz.i2p/topics/1987
comment:3 Changed 3 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Implemented in 0.9.24.
Related: #1656 #1352