-
Notifications
You must be signed in to change notification settings - Fork 42
RFC 6122 features
Jajcus edited this page Jul 10, 2011
·
1 revision
RFC 6122 features sets implemented in PyXMPP2.
The 'Client' and 'Server' columns contain one of:
- 'YES' – feature is fully supported
- 'NO' – feature is not supported
- 'application' – implementation of this feature is the application responsibility
- 'partial' – feature partially implemented
- 'N/A' – not applicable, according to the RFC
- empty – no data
These are declarations only, not proven by any formal certifications, but they should be mostly true.
| Feature | Description | Client | Server | Notes |
|---|---|---|---|---|
| address-domain-length | Ensure that the domainpart of an XMPP address is at least one byte in length and at most 1023 bytes in length, and conforms to the underlying length limits of the DNS. | YES | YES | |
| address-domain-prep | Ensure that the domainpart of an XMPP address conforms to the Nameprep profile of stringprep. | YES | YES | |
| address-localpart-length | Ensure that the localpart of an XMPP address is at least one byte in length and at most 1023 bytes in length. | YES | YES | |
| address-localpart-prep | Ensure that the localpart of an XMPP address conforms to the Nodeprep profile of stringprep. | YES | YES | |
| address-resource-length | Ensure that the resourcepart of an XMPP address is at least one byte in length and at most 1023 bytes in length. | YES | YES | |
| address-resource-prep | Ensure that the resourcepart of an XMPP address conforms to the Resourceprep profile of stringprep. | YES | YES |