[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-203) MQTT URI Scheme
[ https://tools.oasis-open.org/issues/browse/MQTT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick O'Leary updated MQTT-203: ------------------------------ Description: 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. was: 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. I suggest inserting a new section 7, between websockets and conformance, to document this uri scheme. Whilst we are not here to standardise client APIs, this does feel like a useful thing to document within the spec as it will be a key way implementations will interoperate. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]