Open somdoron opened 4 years ago
It's an interesting concept, but that's fine by me. Although all dependent RFCs (for the new types) need to be marked as stable before 3.1 can. Some of then are quite new though?
We can move CHANNEL and PEER and resource property to RFC 3.2 as well
This I think can block us from changing the status of 3.1 to stable.
I suggest to remove it from 3.1 and either move it to 3.2 or to its own RFC.
@bluca @sappo what do you think?