diff --git a/xep-0320.xml b/xep-0320.xml index 6dae5254..58412a49 100644 --- a/xep-0320.xml +++ b/xep-0320.xml @@ -9,8 +9,8 @@ Use of DTLS-SRTP in Jingle Sessions This specification defines how to use DTLS-SRTP (RFC 5763) in the Jingle application type for the Real-time Transport Protocol (RTP) as a way to negotiate media path key agreement for secure RTP in one-to-one media sessions. &LEGALNOTICE; - xxxx - ProtoXEP + 0320 + Experimental Standards Track Standards Council @@ -31,6 +31,12 @@ --> jingle &fippo; + + 0.1 + 2013-04-16 + psa +

Initial published version approved by the XMPP Council.

 + 0.0.2 2013-02-18 diff --git a/xep-0321.xml b/xep-0321.xml index 25c219d6..42c6773e 100644 --- a/xep-0321.xml +++ b/xep-0321.xml @@ -1,295 +1,295 @@ - - -%ents; -]> - - -
- Remote Roster Management - This document defines a way remote entities may manage user's roster to provide a simple way to keep rosters in sync. - - This XMPP Extension Protocol is copyright (c) 1999 - 2012 by the XMPP Standards Foundation (XSF). - Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the 'Specification'), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. - ## NOTE WELL: This Specification is provided on an 'AS IS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ## - In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages. - This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://www.xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA). - - xxxx - ProtoXEP - Standards Track - Standards - Council - - XMPP Core - XEP-0001 - XEP-0004 - XEP-0100 - - - - NOT_YET_ASSIGNED - - Sergey - Dobrov - binary@jrudevels.org - binary@jrudevels.org - - - Jan - Kaluža - hanzz.k@gmail.com - hanzz@njs.netlab.cz - - - 0.0.1 - 2012-12-07 - snd -

First draft.

 - -
- -

It's often desirable for some XMPP based services to make it possible to manage user's roster to provide some contacts there. The most obvious example of such kind of service is a gateway to some legacy IM system (see &xep0100;). The current way that's recommended by the &xep0100; is to use the &xep0144; to synchronize items that's not sutiable in certain situations.

- - -

This document addresses the following requirements:

-
    -
  1. Make it possible for remote services or entities to manage user's roster by the same mechanisms that descibed in the &rfc6121;.
    2. -
  2. Provide a way for user to control which services have permission to manage his roster.
    3. -
- - -
    -
  • Remote entity — the entity that wants to modify user's roster.
    • -
  • User — the entity which roster the remote entity wants to have access to.
    • -
  • User's server — the XMPP server User connected to.
    • -
  • Roster — the list of User's contacts as defined in the &rfc6121;.
    • -
- - - -

In order to be able to make any changes to the user's roster the remote entity MUST ask permission to do so first.

-

NOTE: in order to be able to perform the query, the remote entity MUST have a presence subscription to the User

- - -]]> -

If the presence subscription is absent, the server MUST NOT proceed with the request but MUST respond with the "forbidden" error:

- - - - You must have a presence subscription to be able to request remote roster management service. - -]]> -

The user's server SHOULD then generate a form request using &xep0004; to client in order to ask user if he's OK with granting the permission to the remote entity. The "challenge" form field is generated by the server and is used to identify the client's response. The server also MUST immediatly answer to the request IQ.

-

NOTE: if the entity is already granted with the permission, the server SHOULD immediatly answer with a success response and skip querying the user.

- - icq.example.com wants to be able to manage your roster with following reason: - Manage contacts in the ICQ contact list - Do you want to allow it? Send "yes 5439123" or "no 5439123" back, pleas. - - Roster management permission request - icq.example.com wants to be able to manage your roster with following reason: - Manage contacts in the ICQ contact list. - Do you allow it? - 5439123 - - urn:xmpp:tmp:roster-management:0 - - - 1 - - -]]> -

The client can answer by submit the form or with a text message response:

- - - - urn:xmpp:tmp:roster-management:0 - - 5439123 - 1 - -]]> - - yes 5439123 -]]> - -

If the user allowed the roster management then the server MUST inform the remote entity that it has been granted the permission:

- - -]]> - - -

If the user disallowed the roster management then the server MUST inform the remote entity that it hasn't been granted the permission:

- - -]]> - - -

In order to reject the permission to manage roster it's enough to reject entity's presence subscription:

- ]]> -

If the presence subscription is restored then the permission is needed to be rerequested as defined above.

- - - -

The remote entity being granted the permission to manage roster can request it from the User's server using usual jabber:iq:roster protocol to be able to edit it:

- - -]]> -

The server MUST then answer with User's roster including there only the items that belongs to the entity's hostname:

- - - - Friends - - - Friends - - - Friends - - -]]> - - -

If client updates roster and this update affects the remote entity's contacts (i.e. belongs to it's hostname) then the server MUST forward these items to the remote entity:

- - - - Friends - Lovers - - -]]> - - - - Friends - Lovers - - -]]> - - -

The remote entity can also send the push query to the roster with the same semantics as specified for the jabber:iq:roster protocol described in the &rfc6121;:

- - - - Friends - Lovers - - -]]> -

The server MUST then inform the remote entity of success or an error and in the case of success also forward the push request to all connected User's resources.

-

If the entity tries to make changes into the items it's not allowed to, the server MUST NOT do any changes in the User's roster but respond to the entity with an error:

- - - You have tried to modify the item you don't allowed to. -]]> - - -

User can ask the server to provide a list of components or servers which have permissions to edit their roster.

- - - - ]]> -

In this case, server responds with list of components or servers which can edit user's roster.

- - - - - - - ]]> -

Eventually, user can reject permission granted to component to edit their roster.

- - - - - ]]> - - - - - - - - - - The protocol documented by this schema is defined in - XEP-XXXX: http://www.xmpp.org/extensions/xep-xxxx.html - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ]]> - - + + +%ents; +]> + + +
+ Remote Roster Management + This document defines a way remote entities may manage user's roster to provide a simple way to keep rosters in sync. + &LEGALNOTICE; + 0321 + Experimental + Standards Track + Standards + Council + + XMPP Core + XEP-0001 + XEP-0004 + XEP-0100 + + + + NOT_YET_ASSIGNED + + Sergey + Dobrov + binary@jrudevels.org + binary@jrudevels.org + + + Jan + Kaluža + hanzz.k@gmail.com + hanzz@njs.netlab.cz + + + 0.1 + 2013-04-16 + psa +

Initial published version approved by the XMPP Council.

 + + + 0.0.1 + 2012-12-07 + snd +

First draft.

 + +
+ +

It's often desirable for some XMPP based services to make it possible to manage user's roster to provide some contacts there. The most obvious example of such kind of service is a gateway to some legacy IM system (see &xep0100;). The current way that's recommended by the &xep0100; is to use the &xep0144; to synchronize items that's not sutiable in certain situations.

+ + +

This document addresses the following requirements:

+
    +
  1. Make it possible for remote services or entities to manage user's roster by the same mechanisms that descibed in the &rfc6121;.
    2. +
  2. Provide a way for user to control which services have permission to manage his roster.
    3. +
+ + +
    +
  • Remote entity — the entity that wants to modify user's roster.
    • +
  • User — the entity which roster the remote entity wants to have access to.
    • +
  • User's server — the XMPP server User connected to.
    • +
  • Roster — the list of User's contacts as defined in the &rfc6121;.
    • +
+ + + +

In order to be able to make any changes to the user's roster the remote entity MUST ask permission to do so first.

+

NOTE: in order to be able to perform the query, the remote entity MUST have a presence subscription to the User

+ + +]]> +

If the presence subscription is absent, the server MUST NOT proceed with the request but MUST respond with the "forbidden" error:

+ + + + You must have a presence subscription to be able to request remote roster management service. + +]]> +

The user's server SHOULD then generate a form request using &xep0004; to client in order to ask user if he's OK with granting the permission to the remote entity. The "challenge" form field is generated by the server and is used to identify the client's response. The server also MUST immediatly answer to the request IQ.

+

NOTE: if the entity is already granted with the permission, the server SHOULD immediatly answer with a success response and skip querying the user.

+ + icq.example.com wants to be able to manage your roster with following reason: + Manage contacts in the ICQ contact list + Do you want to allow it? Send "yes 5439123" or "no 5439123" back, pleas. + + Roster management permission request + icq.example.com wants to be able to manage your roster with following reason: + Manage contacts in the ICQ contact list. + Do you allow it? + 5439123 + + urn:xmpp:tmp:roster-management:0 + + + 1 + + +]]> +

The client can answer by submit the form or with a text message response:

+ + + + urn:xmpp:tmp:roster-management:0 + + 5439123 + 1 + +]]> + + yes 5439123 +]]> + +

If the user allowed the roster management then the server MUST inform the remote entity that it has been granted the permission:

+ + +]]> + + +

If the user disallowed the roster management then the server MUST inform the remote entity that it hasn't been granted the permission:

+ + +]]> + + +

In order to reject the permission to manage roster it's enough to reject entity's presence subscription:

+ ]]> +

If the presence subscription is restored then the permission is needed to be rerequested as defined above.

+ + + +

The remote entity being granted the permission to manage roster can request it from the User's server using usual jabber:iq:roster protocol to be able to edit it:

+ + +]]> +

The server MUST then answer with User's roster including there only the items that belongs to the entity's hostname:

+ + + + Friends + + + Friends + + + Friends + + +]]> + + +

If client updates roster and this update affects the remote entity's contacts (i.e. belongs to it's hostname) then the server MUST forward these items to the remote entity:

+ + + + Friends + Lovers + + +]]> + + + + Friends + Lovers + + +]]> + + +

The remote entity can also send the push query to the roster with the same semantics as specified for the jabber:iq:roster protocol described in the &rfc6121;:

+ + + + Friends + Lovers + + +]]> +

The server MUST then inform the remote entity of success or an error and in the case of success also forward the push request to all connected User's resources.

+

If the entity tries to make changes into the items it's not allowed to, the server MUST NOT do any changes in the User's roster but respond to the entity with an error:

+ + + You have tried to modify the item you don't allowed to. +]]> + + +

User can ask the server to provide a list of components or servers which have permissions to edit their roster.

+ + + + ]]> +

In this case, server responds with list of components or servers which can edit user's roster.

+ + + + + + + ]]> +

Eventually, user can reject permission granted to component to edit their roster.

+ + + + + ]]> + + + + + + + + + + The protocol documented by this schema is defined in + XEP-XXXX: http://www.xmpp.org/extensions/xep-xxxx.html + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ]]> + + diff --git a/xep-0322.xml b/xep-0322.xml index 4bb5d667..e9017670 100644 --- a/xep-0322.xml +++ b/xep-0322.xml @@ -9,17 +9,9 @@
Efficient XML Interchange (EXI) Format This specification describes how EXI compression can be used in XMPP networks. - - This XMPP Extension Protocol is copyright (c) 1999 - 2013 by the XMPP Standards Foundation (XSF). - Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. - ## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ## - In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages. - - This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://www.xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA). - - - xxxx - ProtoXEP + &LEGALNOTICE; + 0322 + Experimental Standards Track Standards Council @@ -38,6 +30,12 @@ peter.waher@jabber.org http://se.linkedin.com/pub/peter-waher/1a/71b/a29/ + + 0.1 + 2013-04-16 + psa +

Initial published version approved by the XMPP Council.

 + 0.0.4 2013-03-19 @@ -835,4 +833,4 @@

Thanks to Joachim Lindborg, Yusuke Doi, Takuki Kamiya, Tina Beckman, Karin Forsell, Jeff Freund and Rumen Kyusakov for all valuable feedback.

 - \ No newline at end of file + diff --git a/xep-0323.xml b/xep-0323.xml index 1287730c..ad8e7536 100644 --- a/xep-0323.xml +++ b/xep-0323.xml @@ -8,15 +8,8 @@
Sensor Networks - Sensor Data This specification provides the common framework for sensor data interchange over XMPP networks. - - This XMPP Extension Protocol is copyright (c) 1999 - 2013 by the XMPP Standards Foundation (XSF). - Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. - ## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ## - In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages. - This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://www.xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA). - - xxxx - ProtoXEP + 0323 + Experimental Standards Track Standards Council @@ -35,6 +28,12 @@ peter.waher@jabber.org http://se.linkedin.com/pub/peter-waher/1a/71b/a29/ + + 0.1 + 2013-04-16 + psa +

Initial published version approved by the XMPP Council.

 + 0.0.5 2013-04-01 @@ -1427,4 +1426,4 @@

Thanks to Joachim Lindborg, Karin Forsell, Tina Beckman, Kevin Smith and Tobias Markmann for all valuable feedback.

 - \ No newline at end of file + diff --git a/xep-0324.xml b/xep-0324.xml index e1d0746d..038c579c 100644 --- a/xep-0324.xml +++ b/xep-0324.xml @@ -8,17 +8,9 @@
Sensor Networks - Provisioning This specification describes an architecture for efficient provisioning of services, access rights and user privileges in sensor networks. - - This XMPP Extension Protocol is copyright (c) 1999 - 2013 by the XMPP Standards Foundation (XSF). - Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. - ## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ## - In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages. - - This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://www.xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA). - - - xxxx - ProtoXEP + &LEGALNOTICE; + 0324 + Experimental Standards Track Standards Council @@ -26,7 +18,7 @@ XMPP Core XEP-0001 XEP-0030 - sensor-data + XEP-0323 @@ -38,6 +30,12 @@ peter.waher@jabber.org http://se.linkedin.com/pub/peter-waher/1a/71b/a29/ + + 0.1 + 2013-04-16 + psa +

Initial published version approved by the XMPP Council.

 + 0.0.5 2013-04-04 @@ -1669,4 +1667,4 @@

Thanks to Joachim Lindborg and Karin Forsell for all valuable feedback.

 - \ No newline at end of file +