2 References

24.5463GPPConfiguration management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

– References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.

– For a specific reference, subsequent revisions do not apply.

– For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows;".

[3] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".

[4] OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification".

[5] 3GPP TS 24.547: "Identity management – Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;".

[6] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".

[7] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format".

[8] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[9] IETF RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".

[10] IETF RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".

[11] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification".

[12] IETF RFC 7252: "The Constrained Application Protocol (CoAP)".

[13] IETF RFC 7959: "Block-Wise Transfers in the Constrained Application Protocol (CoAP) ".

[14] IETF RFC 7641: "Observing Resources in the Constrained Application Protocol (CoAP)".

[15] IETF RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".

[16] IETF RFC 8516: ""Too Many Requests" Response Code for the Constrained Application Protocol".

[17] IETF RFC 8949: "Concise Binary Object Representation (CBOR)".

[18] IETF RFC 8610: "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

[19] Constrained RESTful Environments (CoRE) Parameters at IANA, https://www.iana.org/assignments/core-parameters/core-parameters.xhtml

[20] IETF RFC 9290: "Concise Problem Details for Constrained Application Protocol (CoAP) APIs.

[21] Internet draft draft-ietf-core-new-block-14: "Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission".

[22] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".

[23] 3GPP TS 29.501: "Principles and Guidelines for Services Definition".

[24] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications".

[25] IETF RFC 3339: "Date and Time on the Internet: Timestamps".

[26] 3GPP TS 23.003: "Numbering, addressing and identification".

[27] IETF RFC 8132: "PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)".

[28] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".