[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-605) Should packets be identified as multicast or unicast exclusively?
[ https://issues.oasis-open.org/browse/MQTT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=84046#comment-84046 ]
Stefan Hagen commented on MQTT-605:
-----------------------------------
[~davide.lenzarini] and [~ian.craggs]: I think we should keep broadcast and multicast separate.
As in the Stevens citation, in my reading and from the perspective of potential receivers:
bq. in multicasting, nodes can choose to receive a message
Going on with a random citation from Ramadas Shanmugam, R. Padmini, and S. Nivedita: "Special Edition Using TCP/IP", Second Edition, 2002, Que Publishing, chapter 20, "Advantages of Multicasting":
bq. Therefore, multicasting prevents unwanted message transmission and avoids clogging of the network. Another important advantage of multicasting is that multicast messages can be forwarded through routers that are multicast-enabled. However, a broadcast message can be sent to all the computers on the local network and not across an internetwork.
> Should packets be identified as multicast or unicast exclusively?
> -----------------------------------------------------------------
>
> Key: MQTT-605
> URL: https://issues.oasis-open.org/browse/MQTT-605
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Task
> Components: MQTT-SN
> Affects Versions: v2.0
> Reporter: Ian Craggs
> Assignee: Ian Craggs
> Priority: Major
>
> In the 1.2 specification, the ADVERTISE, SEARCHGW and GWINFO are identified as being "broadcasted" to potentially multiple receivers, whereas the other packets are not. The question here is whether we should continue to identify these packets (and PUBLISH QoS -1,- or out of band) as broadcast (or multicast) only in normative text, or just call this out as implementation advice non-normatively.
> Andy Banks is concerned that if it is the latter, then interoperability could be affected.
> Ian Craggs thinks that which address to send packets on is an implementation decision, like the TCP/IP address and port of the MQTT broker in MQTT.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]