Subject: [media-types] Review request for structured syntax suffix registration and media type registration

From: John Mudge <[email-masked]>
Date: Thu, 7 Apr 2016 02:40:05 -0700

Dear all,

This is a review request for:
1) Registration Request for Structured Syntax Suffix tlv
2) Media-Type Registration Request for application/vnd.oma.lwm2m+tlv

1) Registration Request for Structured Syntax Suffix tlv

Name
   Type Length Value

+suffix
   tlv

References
“Lightweight Machine to Machine Technical Specification”, OMA-TS-LightweightM2M-V1_0, http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0
Direct link: http://technical.openmobilealliance.org/Technical/Release_Program/docs/LightweightM2M/V1_0-20151214-C/OMA-TS-LightweightM2M-V1_0-20151214-C.pdf

Encoding considerations
   TLV is a binary format.

Interoperability considerations
   n/a

Fragment identifier considerations
The syntax and semantics of fragment identifiers specified for +tlv SHOULD be as specified for "application/vnd.oma.lwm2m+tlv". (At publication of this document, there is no fragment identification syntax defined for "application/vnd.oma.lwm2m+tlv".) The syntax and semantics for fragment identifiers for a specific "xxx/yyy+tlv" SHOULD be processed as follows: For cases defined in +tlv, where the fragment identifier resolves per the +tlv rules, then process as specified in +tlv. For cases defined in +tlv, where the fragment identifier does not resolve per the +tlv rules, then process as specified in "xxx/yyy+tlv". For cases not defined in +tlv, then process as specified in "xxx/yyy+tlv". 

Security considerations
There are no security considerations inherent in TLV. Each individual media type registered with a +tlv suffix can have additional security considerations. 

Contact
   John Mudge
   [email-masked] 

Author/Change controller.
   Open Mobile Naming Authority (OMNA)
   [email-masked]

2) Media-Type Registration Request for application/vnd.oma.lwm2m+tlv

Type name:	application

Subtype name:	vnd.oma.lwm2m+tlv

Required parameters:	none

Optional parameters:	none

Encoding considerations:	binary

Security considerations:	OMA LWM2M data is passive, meaning it does not contain executable or active content which may represent a security threat. The OMA LWM2M TLV format does not contain fields which are confidential. The usage of the LWM2M TLV format may be vulnerable to attacks modifying or spoofing the content of this format. The OMA LWM2M protocol uses source authentication and integrity protection.

Interoperability considerations:	This content type carries OMA LWM2M data model serialization within the scope of the OMA LWM2M enabler. The OMA LWM2M enabler specification includes static conformance requirements for this content.

Published specification:	OMA LWM2M 1.0 Technical Specification – especially section 6.3.3. Available from http://www.openmobilealliance.org

Applications, which use this media type: OMA LWM2M

Fragment identifier considerations: none

Additional information:
	Deprecated alias names for this type: none
	Magic number(s): none
	File extension(s): none
	Macintosh File Type Code(s): none

Intended usage: Limited use. Only for usage with OMA LWM2M, which meet the semantics given in the mentioned specification.

Restriction on usage: no

Person & email address to contact for further information: 
	John Mudge
	[email-masked]

Author/Change controller:
	Open Mobile Naming Authority (OMNA)
	[email-masked]

Provisional registration (standards tree only): LWM2M+TLV

Thank you in advance for your comments.

Kind regards,

John Mudge

Email: [email-masked]