oneM2M TS-0009Release Notes diff from v5.1.0 to v5.1.0

  • ETSI title

  • 1 Scope
  • 2 References
    • 2.1 Normative references
    • 2.2 Informative references
  • 3 Abbreviations
  • 4 Conventions
  • 5 Overview on HTTP Binding
    • 5.0 Overview
    • 5.1 Introduction
    • 5.2 Request-Line
    • 5.3 Status-Line
  • 6 HTTP Message Mapping
    • 6.1 Introduction
    • 6.2 Parameter Mappings on Request-Line
      • 6.2.1 Method
      • 6.2.2 Request-Target
        • 6.2.2.1 Path component
        • 6.2.2.2 Query component
      • 6.2.3 HTTP-Version
    • 6.3 Status-Line
      • 6.3.1 HTTP-Version
      • 6.3.2 Status-Code
      • 6.3.3 Reason-Phrase
    • 6.4 Header Fields
      • 6.4.0 Introduction
      • 6.4.1 Host
      • 6.4.2 Accept
      • 6.4.3 Content-Type
      • 6.4.4 Content-Location
      • 6.4.5 Content-Length
      • 6.4.6 Etag
      • 6.4.7 X-M2M-Origin
      • 6.4.8 X-M2M-RI
      • 6.4.9 Void
      • 6.4.10 X-M2M-GID
      • 6.4.11 X-M2M-RTU
      • 6.4.12 X-M2M-OT
      • 6.4.13 X-M2M-RST
      • 6.4.14 X-M2M-RET
      • 6.4.15 X-M2M-OET
      • 6.4.16 X-M2M-EC
      • 6.4.17 X-M2M-RSC
      • 6.4.18 X-M2M-ATI
      • 6.4.19 Authorization
      • 6.4.20 X-M2M-CTS
      • 6.4.21 X-M2M-CTO
      • 6.4.22 X-M2M-RVI
      • 6.4.23 X-M2M-VSI
      • 6.4.24 X-M2M-AS
      • 6.4.25 X-M2M-ASRI
      • 6.4.26 X-M2M-OMR
      • 6.4.27 X-M2M-MSU
      • 6.4.28 X-M2M-PRPI
    • 6.5 Message-body
    • 6.6 Message Routing
    • 6.7 Ignoring HTTP Responses for Notifications to non-oneM2M Entitites
  • 7 Security Consideration
    • 7.1 Authentication on HTTP Request Message
    • 7.2 Transport Layer Security
  • Annex A (informative): Example Procedures
    • A.1 <container> resource creation
  • Annex B (informative): Void
  • History
Copyright © 2024 oneM2M Partnership Project