[OASIS Issue Tracker] (MQTT-235) NoLocal Subscription for MQTT Subscribers

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59228#comment-59228 ] 

Raphael Cohen commented on MQTT-235:
------------------------------------

I'd like to point out that 'noLocal' is actually an orthogonal subscription axis to topic. (Just as other things can be considered to be, eg client id, or, content-type, etc). Whilst we might not want to recast the protocol to do this explicitly, it does mean that 'noLocal' is chosen by the subscriber, not by the publisher, so it ought to go in SUBSCRIBE. That said, I understand Ken's point about bridging needed CONNECT level properties. Is it worth opening a separate JIRA for bridging? Personally, I'm not a fan of bridging and message routing, but, if we go down this route, we should be aware that other MQ protocols are much better suited for such uses.

If we do use the remaining requestQos bit, how do we handle duplicate subscriptions and unsubscribes, particularly when the bit differs?

> NoLocal Subscription for MQTT Subscribers 
> ------------------------------------------
>
>                 Key: MQTT-235
>                 URL: https://issues.oasis-open.org/browse/MQTT-235
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Rahul Gupta
>            Priority: Critical
>             Fix For: 3.1.1
>
>
> Based on a query in MQTT Google group, a query was posted with a requirement that the server should not publish message to a subscriber if messages are published by the same client-id and subscribed by the using the same client-id for the same topic. In this case a client connection may both publish and subscribe to a topic and the subscriber should inhibit the delivery of messages published by its own connection. This feature is available in JMS and a subscriber can inhibit to receive publication by using the noLocal flag during subscription.
> This feature is also needed to enable bridging and making proxy subscription between servers so as to stop messages going round in loops.
> I would like propose to add a element in SUBSCRIBE Control packet for individual subscriptions to make a choice on noLocal parameter.  This field could be shared in the same byte as for requstedQos. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)