zcash
Cross-link Zebra RFC and other consensus-adjacent standardizations.
The Zebra consensus node team has adopted an RFC process for collaborating on important design changes. It's likely that some of those RFCs may impact Zcash consensus or infrastructure, so the scope may be semi-overlapping with ZIPs.
I'd like to update the documentation for how the ZIP process works to clarify the relationship to other specification processes, such as for consensus nodes like Zebra RFCs.
Please see my comment on a Zebra RFC doc issue #922 for how I propose the two processes remain largely decoupled, with probable over-lapping / cross-referencing standards.
As I wrote at https://github.com/ZcashFoundation/zebra/issues/922#issuecomment-691968354 :
I propose to reserve ZIP numbers 600-999 to correspond to Zebra RFCs 0000-0399. That is, any ZIP that is basically a copy of an RFC, and is potentially implementation-specific, will have that number mapping. (Note that ZIP numbers 500-599 are already reserved for implementation-specific ZIPs.)
