OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-203) MQTT URI Scheme

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

Paul Fremantle commented on MQTT-203:

Sorry I wasn't able to join the F2F. 

Was there any discussion of DNS SRV records for use within URIs? 

Roger implemented something around this previously: https://groups.google.com/forum/#!msg/mqtt/hixhyVMZVxg/T6k3p4BP-GAJ

The reason I think that DNS SRV records are important is that in many cases you want a logical name for a topic which can be available on one of several brokers. This is like the email system, where my email (e.g. paul@freo.me) is not actually hosted on a host called freo.me. The mail uses MX records, but DNS SRV records are a more flexible equivalent. 

Ideally, I'd like to see a rule whereby we look up the SRV record for the broker and if that fails, try to connect to the address directly. This would allow me to specify a topic like: mqtt://freo.me/whereabouts/paul which could then be a well-defined URI that resolves to a specific broker.

> MQTT URI Scheme
> ---------------
>                 Key: MQTT-203
>                 URL: https://issues.oasis-open.org/browse/MQTT-203
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>            Reporter: Nicholas O'Leary
>            Priority: Critical
> There have been a number of discussions in the community on how to specify a broker's connection details in a uri.
> The result of the community discussion is captured here - https://github.com/mqtt/mqtt.github.io/wiki/URI-Scheme
> In summary, the following uri format is proposed:
>     mqtt://[username][:password]@host.domain[:port][?clientid=clientid]
> The uri scheme could alternative be 'mqtts' to specify a secure TLS connection should be used.
> Other connection-time options (clean session etc) could also be expressed as query parameters.
> A path portion of the uri could be used to specify a specific topic.
> This JIRA can be addressed by way of Committee Note, rather than as an addition to the spec itsef.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]