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

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

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

Raphael Cohen commented on MQTT-203:
------------------------------------

I think addressing this with a committee note is the right way to go. At the same time, I'd like to make sure that we do a few other things in the same note:-
- outline the use of DNS SRV records for finding brokers (and perhaps tying this very simply to the URI format)
- suggest the use of DNS LOC records to allow IoT clients to find geographically close brokers (eg taking a GPS fix and then finding the broker in the SRV set closest to them)

A couple of things I'd like to explore at the same time
- explore publishing MQTTS broker certificates in DNS (there's a couple of ways) so clients can do the double-check (ie DNS cert cert matches TLS provided cert - forcing an attacker to then control the entire infrastructure). For instance, opendns do this currently for some of their services.
- explore having a URN

In doing this, we need to be mindful that
- we don't upset security conscious users;
- we don't make things hard in the future if we need multiple topic spaces or routing features
- and likewise for redirect ideas (for which I'd recommend SRV as above, but we need to be careful)


> MQTT URI Scheme
> ---------------
>
>                 Key: MQTT-203
>                 URL: https://tools.oasis-open.org/issues/browse/MQTT-203
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>            Reporter: Nick O'Leary
>            Priority: Minor
>
> 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
(v6.1.1#6155)