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=59268#comment-59268 ] 

Raphael Cohen commented on MQTT-203:

If we permit port, we're implying to the casual reader that the domain name in the URI is a CNAME. We also require a responsible client to do three look ups in the absence of port; SRV for _mqtts._tcp.DOMAINNAME, then _mqtt._tcp.DOMAINNAME and then CNAME if that's not found. (A client would have to also be able to tease out literal IPv6 and IPv4 addresses, and potentially Unix domain sockets; one reason I've never really liked URIs. Look at the mess Sun made with them when using them for Java class loaders and java.net). If port is present, then a client just does a CNAME / A / AAAA look up.

Whilst I'm sure we can mutually resolve this, I just worry that a casual developer is going to ignore whatever we write in a note and just go 'yep, looks like HTTP, do that'. Port exists in HTTP because it was specified a _long time_ before SRV was defined (indeed, the SRV RFC has a SHOULD that prevents HTTP and similar protocols from adding it). There have been proposals to add it, and we can get some useful insights into how to do it right from this draft (http://tools.ietf.org/html/draft-andrews-http-srv-02#section-3) - one of a series that have been revised over the last few years.

> 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: 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

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