iddaspix

Results 1 issues of


                                            iddaspix

All protocol message types should have options/details

4

comment

Some protocol messages have a rigid structure: ``` [SUBSCRIBED, SUBSCRIBE.Request|id, Subscription|id] [UNSUBSCRIBED, UNSUBSCRIBE.Request|id] [REGISTERED, REGISTER.Request|id, Registration|id] [UNREGISTERED, UNREGISTER.Request|id] [PUBLISHED, PUBLISH.Request|id, Publication|id] ``` I think it would be a good idea...

Basic Profile

Enhancement

RFC

Needs consensus