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] Commented: (MQTT-24) Edits to Introduction section


    [ http://tools.oasis-open.org/issues/browse/MQTT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34023#action_34023 ] 

Rahul Gupta commented on MQTT-24:
---------------------------------

Updated in WD-06

This specification is split into four main sections:
•	The packet template that is common to all MQTT control packet types
•	The specific details of each control packet type
•	How the packets flow between client and server
•	Conformance requirements for this version of specification

1.2  Normative references
--------------------------
[RFC793] 
Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
http://www.ietf.org/rfc/rfc793.txt

[RFC2119] 
S. Bradner, Key words for use in RFCs to Indicate Requirement Levels. IETF RFC 2119, March 1997. 
http://www.ietf.org/rfc/rfc2119.txt

[RFC 3629]
F. Yergeau UTF-8, a transformation format of ISO 10646 IETF RFC 3629, November 2003. 
http://www.ietf.org/rfc/rfc3629.txt

[Unicode 6.2] Unicode 6.2 specification
http://www.unicode.org/versions/Unicode6.2.0


-------------------

Raph - Do you suggest adding other details in your updated above, to be included in Section 2.3 UTf-8 encoded strings ? Please suggest

> Edits to Introduction section
> -----------------------------
>
>                 Key: MQTT-24
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-24
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: edits
>    Affects Versions: 3.1.1
>            Reporter: Peter Niblett
>            Priority: Minor
>
> 1. The introduction says the spec has three main sections, however there's now an additional section on Conformance requirements.
> 2. The Normative References should include a reference to a Unicode standard, as well as to UTF-8.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




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