Skip to content

[FR] “Sparse” peerings #33

Description

@ShadowJonathan

What

Peerings with “sparse” status, an explicit opt in on both sides go allow a connection more low-throughput, high-latency, more unreliable, or with less duty cycles than the current pinecone peerings require.

Why

Primarily, iot devices, to allow for power savings, yet stay connected to the network at times, allowing peers at the other side of the sparse connection to queue up packets and send them through whenever the underlying transport allows.

Secondly, resiliency in unreliable conditions, where a peer wants to accept high-latency costs, at the benefit of not becoming disconnected from the network at large. (Think remote outposts in unfavourable weather conditions resulting in unreliable uplinks, or network operators in hostile environments requiring prolonged connectivity over intermittent outages)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions