RFC 3920:Extensible Messaging and Presence Protoco...
RFC-Ref

Extensible Messaging and Presence Protocol (XMPP): Core


1. Introduction
1.1. Overview
1.2. Terminology
2. Generalized Architecture
2.1. Overview
2.2. Server
2.3. Client
2.4. Gateway
2.5. Network
3. Addressing Scheme
3.1. Overview
3.2. Domain Identifier
3.3. Node Identifier
3.4. Resource Identifier
3.5. Determination of Addresses
4. XML Streams
4.1. Overview
4.2. Binding to TCP
4.3. Stream Security
4.4. Stream Attributes
4.4.1. Version Support
4.5. Namespace Declarations
4.6. Stream Features
4.7. Stream Errors
4.7.1. Rules
4.7.2. Syntax
4.7.3. Defined Conditions
4.7.4. Application-Specific Conditions
4.8. Simplified Stream Examples
5. Use of TLS
5.1. Overview
5.1.1. ASN.1 Object Identifier for XMPP Address
5.2. Narrative
5.3. Client-to-Server Example
5.4. Server-to-Server Example
6. Use of SASL
6.1. Overview
6.2. Narrative
6.3. SASL Definition
6.4. SASL Errors
6.5. Client-to-Server Example
6.6. Server-to-Server Example
7. Resource Binding
8. Server Dialback
8.1. Overview
8.2. Order of Events
8.3. Protocol
9. XML Stanzas
9.1. Common Attributes
9.1.1. to
9.1.2. from
9.1.3. id
9.1.4. type
9.1.5. xml:lang
9.2. Basic Semantics
9.2.1. Message Semantics
9.2.2. Presence Semantics
9.2.3. IQ Semantics
9.3. Stanza Errors
9.3.1. Rules
9.3.2. Syntax
9.3.3. Defined Conditions
9.3.4. Application-Specific Conditions
10. Server Rules for Handling XML Stanzas
10.1. No 'to' Address
10.2. Foreign Domain
10.3. Subdomain
10.4. Mere Domain or Specific Resource
10.5. Node in Same Domain
11. XML Usage within XMPP
11.1. Restrictions
11.2. XML Namespace Names and Prefixes
11.2.1. Streams Namespace
11.2.2. Default Namespace
11.2.3. Dialback Namespace
11.3. Validation
11.4. Inclusion of Text Declaration
11.5. Character Encoding
12. Core Compliance Requirements
12.1. Servers
12.2. Clients
13. Internationalization Considerations
14. Security Considerations
14.1. High Security
14.2. Certificate Validation
14.3. Client-to-Server Communications
14.4. Server-to-Server Communications
14.5. Order of Layers
14.6. Lack of SASL Channel Binding to TLS
14.7. Mandatory-to-Implement Technologies
14.8. Firewalls
14.9. Use of base64 in SASL
14.10. Stringprep Profiles
15. IANA Considerations
15.1. XML Namespace Name for TLS Data
15.2. XML Namespace Name for SASL Data
15.3. XML Namespace Name for Stream Errors
15.4. XML Namespace Name for Resource Binding
15.5. XML Namespace Name for Stanza Errors
15.6. Nodeprep Profile of Stringprep
15.7. Resourceprep Profile of Stringprep
15.8. GSSAPI Service Name
15.9. Port Numbers
16. References
16.1. Normative References
16.2. Informative References
17. Appendix A. Nodeprep
17.1. A.1. Introduction
17.2. A.2. Character Repertoire
17.3. A.3. Mapping
17.4. A.4. Normalization
17.5. A.5. Prohibited Output
17.6. A.6. Bidirectional Characters
18. Appendix B. Resourceprep
18.1. B.1. Introduction
18.2. B.2. Character Repertoire
18.3. B.3. Mapping
18.4. B.4. Normalization
18.5. B.5. Prohibited Output
18.6. B.6. Bidirectional Characters
19. Appendix C. XML Schemas
19.1. C.1. Streams namespace
19.2. C.2. Stream error namespace
19.3. C.3. TLS namespace
19.4. C.4. SASL namespace
19.5. C.5. Resource binding namespace
19.6. C.6. Dialback namespace
19.7. C.7. Stanza error namespace
20. Appendix D. Differences Between Core Jabber Protocols and XMPP
20.1. D.1. Channel Encryption
20.2. D.2. Authentication
20.3. D.3. Resource Binding
20.4. D.4. JID Processing
20.5. D.5. Error Handling
20.6. D.6. Internationalization
20.7. D.7. Stream Version Attribute
21. Contributors
22. Acknowledgements
23. Author's Address
24. Full Copyright Statement
25. Intellectual Property
26. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org