Skip to content
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.

Writeup RFC for bam over libp2p #65

Closed
6 tasks done
thomaseizinger opened this issue May 5, 2019 · 2 comments · Fixed by #92
Closed
6 tasks done

Writeup RFC for bam over libp2p #65

thomaseizinger opened this issue May 5, 2019 · 2 comments · Fixed by #92
Assignees
@thomaseizinger
Milestone
Sprint 19 🛹🏢

Comments

@thomaseizinger
Copy link
Contributor

thomaseizinger commented May 5, 2019 •
edited
Loading

Deprecate BAM!, rename the RFC to "COMIT messages" to specify headers, encoding by default using JSON, usage of libp2p and substream management.

Related to #57

DoD:

  • RFC001 is re-written
  • RFC-001-BAM label on GitHub is renamed
  • Check/re-write BAM section in RFC-002
  • Check other BAM mentions in README.md and registry.md
  • Make sure to mention assumptions about the libp2p-stack (TcpTransport, Yamux multiplexer, Secio encryption)
  • Make sure the Error frame was removed as part of this process to align with Remove Error Frame from RFC-001 #117
@thomaseizinger thomaseizinger mentioned this issue Jul 5, 2019
Merged
@thomaseizinger thomaseizinger mentioned this issue Aug 2, 2019
Closed
@thomaseizinger thomaseizinger added this to the Sprint 19 🛹🏢 milestone Aug 7, 2019
@tcharding tcharding mentioned this issue Aug 12, 2019
Closed
@thomaseizinger thomaseizinger self-assigned this Aug 16, 2019
@D4nte
Copy link
Contributor

D4nte commented Aug 23, 2019

@thomaseizinger all boxes done? (not ticked)

@thomaseizinger
Copy link
Contributor Author

@thomaseizinger all boxes done? (not ticked)

Nope 😅

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

@thomaseizinger thomaseizinger

Labels
None yet
Projects
None yet
Milestone
Sprint 19 🛹🏢
Development

Successfully merging a pull request may close this issue.

Rewrite of RFC001 to mention libp2p comit-network/RFCs
2 participants
@D4nte @thomaseizinger