…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…ssion-wide buffers are not used. 3.9 Snapshot Repository for Well-known Schemas Errata and other updates may happen to well-known schemas. Slightest modification to XML schemas may break interoperability of EXI nodes. However, negotiating everything is not efficient. Well-known a…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…pp.org discussion lists might also be appropriate; see < > for a complete list. Errata can be sent to < editor@xmpp.org >. Appendix F: Requirements Conformance The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMEN…
…ection 2 of RFC 7841 Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at Bray Standards Track [Page 1] RFC 8259 JSON December 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the …
…ection 2 of RFC 7841 Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at Bray Standards Track [Page 1] RFC 8259 JSON December 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the …
…ction 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at Copyright Notice Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. This document is su…
[ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata ] [ Info page ] INTERNET STANDARD Errata Exist Internet Engineering Task Force (IETF) T. Bray, Ed. Request for Comments: 8259 Textuality Obsoletes: 7159 December 2017 Category: Standards Track ISSN: 2070-1721 The Jav…