New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configured Subscriptions - Protocol, Encoding #4

Closed

ericvoit opened this issue Oct 16, 2017 · 1 comment

Contributor

ericvoit commented Oct 16, 2017

For a configured subscription with multiple receivers, three possibilities exist for encoding and transport protocol:

(1) The transport protocol and the encoding should be the same for all receivers of a single subscription

(2) The transport protocol should be able to vary by receiver, but the encoding should be consistent across all receivers

(3) The transport protocol and the encoding should be allowed to vary for any particular receiver of a single subscription.

Contributor Author

ericvoit commented Dec 7, 2017

No objection has been asserted. Rough consensus has been achieved. The non-NMDA representation is:

+--rw subscription-config {configured}?
   +--rw subscription* [identifier]
      +--rw identifier                     subscription-id
      +--rw protocol                       transport {configured}?
      +--rw encoding                       encoding

The NMDA representation will be seen shortly.

ericvoit closed this as completed

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