Skip to content

Latest commit

Β 

History

History
44 lines (28 loc) Β· 1.13 KB

File metadata and controls

44 lines (28 loc) Β· 1.13 KB

Contributing to Crowsong

Comments on the drafts are welcome.

How to comment

GitHub Issues β€” preferred for specific technical questions, errata, and implementation feedback.

Email β€” trey@propertools.be for substantive discussion.

IETF mailing lists β€” DTNWG for L3 (routing) matters, DISPATCH for general routing of new work.

What kind of feedback is most useful

  • Implementation experience (did the spec produce the right output? was anything ambiguous?)
  • Security analysis (especially L4 threat model gaps)
  • Operational experience with degraded-channel communications
  • Prior art we've missed

What this is not

This is not a working group. There is no charter. There is no consensus process. There is one author, a reference implementation, a canonical test vector, and a poem.

If the work is useful, it will find its institutional home. If it isn't, it will at least have been honest about what it was trying to do.

The test

A contribution is useful if it makes the stack more likely to carry a signal across a gap.

That's the only test.


"Some signals are not for us."

But this one might be.