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

service


Click on the red underlined text to get to the source

... [IMP-REQS] also stipulates that presence services must be separable from instant messaging services; i.e., it must be possible to use the ...
... IMP-REQS] also stipulates that presence services must be separable from instant messaging services; i.e., it must be possible to use the protocol to provide a presence service, an instant messaging service ...
... from instant messaging services; i.e., it must be possible to use the protocol to provide a presence service, an instant messaging service, or both. Although the text of this memo assumes that implementations ...
... instant messaging services; i.e., it must be possible to use the protocol to provide a presence service, an instant messaging service, or both. Although the text of this memo assumes that implementations and deployments ...
... deployments will want to offer a unified instant messaging and presence service, there is no requirement that a service must offer ...
... presence service, there is no requirement that a service must offer both a presence service and an instant messaging service ...
... requirement that a service must offer both a presence service and an instant messaging service, and the protocol makes it possible to offer separate and distinct services ...
... service must offer both a presence service and an instant messaging service, and the protocol makes it possible to offer separate and distinct services ...
... presence service and an instant messaging service, and the protocol makes it possible to offer separate and distinct services for presence and for instant messaging. ...


... o headline -- The message is probably generated by an automated service that delivers or broadcasts content (news, sports, market information, RSS feeds, etc.). No reply ...
... Although the 'type' attribute is OPTIONAL, it is considered polite to mirror the type in any replies to a message; furthermore, some specialized applications (e.g., a multi-user chat service) MAY at their discretion enforce the use of a particular message type (e.g., ...
... stanza of type "error" with an error condition of <service-unavailable/>. ...


... notifications only as defined above. (Note: While presence information MAY be provided on a user's behalf by an automated service, normally it is provided by the user's client.) ...
... presence probe from a subdomain of the server's hostname or another such trusted service, it MAY provide presence information about the user to that entity). Specifically: ...


... "set" to the user, the user's server MUST return to the sending entity a <service-unavailable/> stanza error, since this is the ...
... <error type='cancel'> <service-unavailable xmlns ...


... stanza (i.e., neither deliver it nor return an error) if it is a presence stanza, (b) MUST return a <service-unavailable/> stanza error to ...
... sender if it is an IQ stanza, and (c) SHOULD return a <service-unavailable/> stanza error to the sender ...
... nor return an error) if it is a presence stanza, (b) MUST return a <service-unavailable/> stanza error to the sender ...
... reply to the stanza on behalf of the user; if not, the server MUST reply with a <service-unavailable/> stanza error. ...
... not enabled, the server MUST return to the sender a <service-unavailable/> stanza error. (Note: Offline message ...
... storage and message forwarding are not defined in XMPP, since they are strictly a matter of implementation and service provisioning.) ...
... stanza on behalf of the user; if not, the server MUST reply with a <service-unavailable/> stanza error. ...
... 1. First attempt to resolve the foreign hostname using an [SRV] Service of "xmpp-server" and Proto of "tcp", resulting in resource records such as "_xmpp-server._tcp.example.com.", as ...
... address record resolution fails, attempt to resolve the "_im" or "_pres" [SRV] Service as specified in [IMP-SRV], using the "_im" Service ...
... Service as specified in [IMP-SRV], using the "_im" Service for <message/> stanzas and the "_pres" Service ...
... Service for <message/> stanzas and the "_pres" Service for <presence/> stanzas (it is up to the implementation how to handle <iq/> stanzas ...


... instant messaging, and is not required to support both if only a presence service or an instant messaging service is desired. ...
... instant messaging, and is not required to support both if only a presence service or an instant messaging service is desired. ...


... stanza for a user who does not exist, the use of the <service-unavailable/> error condition helps protect against ...


... Instant Messaging SRV Protocol Label registry for protocols that can provide services that conform to the "_im" SRV Service ...
... services that conform to the "_im" SRV Service label. Because XMPP is one such protocol, the IANA registers ...
... SRV Protocol Label registry for protocols that can provide services that conform to the "_pres" SRV Service label. ...
... provide services that conform to the "_pres" SRV Service label. Because XMPP is one such protocol, the IANA ...


... Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...



Google
Web
RFC-Ref