2. Scope¶
This document addresses common requirements related to configuration of, participation in, and administration of individual text-based conference rooms. All of the requirements addressed herein apply at the level of the individual room and are “common” in the sense that they have been widely discussed within the Jabber/XMPP community or are familiar from existing text-based conference environments (e.g., Internet Relay Chat as defined in RFC 1459 [1] and its successors: RFC 2810 [2], RFC 2811 [3], RFC 2812 [4], RFC 2813 [5]).
This document explicitly does not address the following:
- Relationships between rooms (e.g., hierarchies of rooms)
- Management of multi-user chat services (e.g., managing permissions across an entire service or registering a global room nickname); such use cases are specified in Service Administration (XEP-0133) [6]
- Moderation of individual messages
- Encryption of messages sent through a room
- Advanced features such as attaching files to a room, integrating whiteboards, and using MUC rooms as a way to manage the signalling for multi-user audio or video conferencing (see Multiparty Jingle (XEP-0272) [7])
- Interaction between MUC deployments and foreign chat systems (e.g., gateways to IRC or to legacy IM systems)
- Mirroring or replication of rooms among multiple MUC deployments
This limited scope is not meant to disparage such topics, which are of inherent interest; however, it is meant to focus the discussion in this document and to present a comprehensible protocol that can be implemented by client and service developers alike. Future specifications might address the topics mentioned above.
Oh snap, got some RFCs in the mix! Those IRC RFC are… available for reading. 
Discover XEP-0133: Service Administration is on my list. 
Okay, so we know what this isn’t about…