mirror of https://github.com/moparisthebest/xeps
added feed for draft-ietf-sieve-notify-xmpp
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1359 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
05740b7358
commit
cf66dc969f
|
|
@ -30,31 +30,33 @@
|
|||
<h3>1.1 <a name='intro-history'></a>History</h3>
|
||||
<p>The Jabber/XMPP protocols have been under development since 1998 and have been discussed and documented in public forums since January 1999 in the open-source projects that were a precursor to the XSF. Through force of history and activity since its founding in the summmer of 2001, the XSF has assumed responsibility for managing the evolution of the Jabber/XMPP protocols in two ways: (1) through working with the IETF to standardize the core protocols under the name Extensible Messaging and Presence Protocol (XMPP); and (2) through the definition of extensions to the core protocol in the XSF's XMPP Extension Protocol (XEP) specification series. Through this work, the XSF has in effect "homesteaded" the domain of XMPP Extensions and has acted as a trusted third party or "intellectual property conservancy" [<a href='#note2'>2</a>] to which new and established participants in the Jabber community have entrusted their XMPP Extensions.</p>
|
||||
<h3>1.2 <a name='intro-role'></a>Purpose</h3>
|
||||
<p>The XSF does not seek to disparage the legitimate rights of any individual or organization to assert ownership over an Implementation of XMPP or of any XMPP Extension. However, the XSF must ensure that XMPP Extensions do not pollute the free and open nature of the protocols. Preventing such pollution means that in perpetuity any entity may independently, and without payment or hindrance, create, use, sell, distribute, or dispose of implementations of XMPP and of any XMPP Extension. Such is the intent of this policy.</p>
|
||||
<p>The XSF does not seek to disparage the legitimate rights of any individual or organization to assert ownership over an Implementation or Deployment of XMPP or of any XMPP Extension. However, the XSF must ensure that XMPP Extensions do not pollute the free and open nature of the protocols. Preventing such pollution means that in perpetuity any entity may independently, and without payment or hindrance, create, use, sell, distribute, or dispose of implementations of XMPP and of any XMPP Extension. Such is the intent of this policy.</p>
|
||||
</blockquote>
|
||||
<h2>2. <a name='terms'></a>Terms</h2>
|
||||
<h2>2. <a name='terms'></a>Terminology</h2>
|
||||
<blockquote>
|
||||
<h3>2.1 <a name='xmpp'></a>XMPP</h3>
|
||||
<p>The core XML streaming, instant messaging, and presence protocols developed by the Jabber community have been contributed by the XSF to the Internet Engineering Task Force (IETF) under the name Extensible Messaging and Presence Protocol (XMPP). XMPP is all and only these core protocols, as currently defined in <a href='http://www.ietf.org/rfc/rfc3920.txt'>RFC 3920</a> and <a href='http://www.ietf.org/rfc/rfc3921.txt'>RFC 3921</a>.</p>
|
||||
<h3>2.2 <a name='extension'></a>XMPP Extension</h3>
|
||||
<p>For the purposes of this IPR policy, an XMPP Extension is any specification approved by, or submitted for approval or consideration by, the XSF or its constituent committees (most particularly the <a href='/council/'>XMPP Council</a>). Such a specification must exist in the form of a standards-track XMPP Extension Protocol (XEP) specification in order to be considered an official submission. (Also referred to as an Extension.)</p>
|
||||
<h3>2.3 <a name='implementation'></a>Implementation</h3>
|
||||
<p>Any software that implements XMPP or XMPP Extensions for the purpose of providing the functionality defined by the relevant specification(s).</p>
|
||||
<h3>2.4 <a name='claim'></a>Intellectual Property Claim</h3>
|
||||
<p>Any patent, copyright, or other proprietary claim or claims made by an entity regarding a XMPP Extension. (Also referred to as a Claim.)</p>
|
||||
</blockquote>
|
||||
<p>Any software program that implements the functionality defined in the core XMPP specifications or in XMPP Extensions Protocols for the purpose of providing the functionality defined by the relevant specification(s).</p>
|
||||
<h3>2.4 <a name='deployment'></a>Deployment</h3>
|
||||
<p>Any service deployed over a network that offers the capabilities defined in the core XMPP specifications or in XMPP Extension Protocols.</p>
|
||||
<h3>2.5 <a name='claim'></a>Intellectual Property Claim</h3>
|
||||
<p>Any patent, copyright, or other proprietary claim or claims made by an entity regarding an XMPP Extension. (Also referred to as a Claim.)</p>
|
||||
</blockquote>
|
||||
<h2>3. <a name='contributing'></a>Terms of Contributing an XMPP Extension</h2>
|
||||
<p>The XSF recognizes the possibility that the creator of an XMPP Extension may make an Intellectual Property Claim regarding an XMPP Extension. Therefore, the XSF takes the following positions:</p>
|
||||
<blockquote>
|
||||
<h3>3.1 <a name='contrib-ownership'></a>Ownership</h3>
|
||||
<p>By submitting an XMPP Extension for consideration by the XSF, the author of the Extension shall assign any ownership rights or other Claims asserted over the Extension to the XSF. This does not apply to Claims regarding any Implementations of the Extension, but rather to the Extension itself. Any documentation of the Extension (in the form of a XEP specification) shall be copyrighted by the XSF. Once an author assigns ownership to the XSF, the XSF shall in turn make the Extension available to all entities so that they may create, use, sell, distribute, or dispose of implementations of XMPP and all XMPP Extensions in perpetuity and without payment or hindrance.</p>
|
||||
<p>By submitting an XMPP Extension for consideration by the XSF, the author of the Extension shall assign any ownership rights or other Claims asserted over the Extension to the XSF. This does not apply to Claims regarding any Implementations or Deployments of the Extension, but rather to the Extension itself as represented in a protocol or data format. Any documentation of the Extension (in the form of a XEP specification) shall be copyrighted by the XSF. Once an author assigns ownership to the XSF, the XSF shall in turn make the Extension available to all entities so that they may create, use, sell, distribute, or dispose of Implementations or Deployments of XMPP and all XMPP Extensions in perpetuity and without payment or hindrance.</p>
|
||||
<h3>3.3 <a name='contrib-approval'></a>Approval of Extensions</h3>
|
||||
<p>No Extension shall be approved by the XSF or its constituent committees if there are Claims to the Extension itself, or any Claims that would prevent perpetual, unrestricted, royalty-free use of the Extension in a compliant Implementation by any interested party. If Claims preventing such use are discovered, the XSF shall immediately seek to replace the Extension with unencumbered protocols that may be implemented without condition by any entity.</p>
|
||||
<p>No Extension shall be approved by the XSF or its constituent committees if there are Claims to the Extension itself, or any Claims that would prevent perpetual, unrestricted, royalty-free use of the Extension in a compliant Implementation or Deployment by any interested party. If Claims preventing such use are discovered, the XSF shall immediately seek to replace the Extension with unencumbered protocols that may be implemented without condition by any entity.</p>
|
||||
<h3>3.3 <a name='contrib-private'></a>A Note about Private Extensions</h3>
|
||||
<p>By its nature as XML, XMPP enables implementers to create their own private extensions to XMPP within custom XML namespaces. Such extensions may be kept private, and there is no compulsion for implementers to contribute such extensions to the Jabber community. It is only when an implementer seeks to have an extension standardized through the XSF's public standards process that ownership over such an extension must be transferred to the XSF. If an implementer wishes to keep its extensions private, it may simply refrain from submitting them to the XSF. However, private extensions exist outside the boundaries of XMPP and approved XMPP Extensions and must not be considered or described as part of XMPP or XSF-approved XMPP Extensions.</p>
|
||||
</blockquote>
|
||||
<h2>4. <a name='legal'></a>Legal Notice</h2>
|
||||
<p>All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notice:</p>
|
||||
<h2>4. <a name='legal'></a>Legal Notices</h2>
|
||||
<p>All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notices:</p>
|
||||
<blockquote><pre>
|
||||
This XMPP Extension Protocol is copyright 1999 - [year]
|
||||
by the XMPP Standards Foundation (XSF) and is in full
|
||||
|
|
|
|||
|
|
@ -20,6 +20,12 @@
|
|||
<supersededby/>
|
||||
<shortname>TO BE ASSIGNED</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-10-30</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Clarified meaning of encrypted; specified rules for reporting of server-to-server connections.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2007-05-30</date>
|
||||
|
|
@ -65,8 +71,9 @@
|
|||
<li>If my contact's connection to their server is encrypted.</li>
|
||||
</ol>
|
||||
<p>If the answer to all three of these questions is "yes" and I have some level of trust in my XMPP server (see <link url='#security'>Security Considerations</link>) then I have some assurance that communications between me and my contact will not be subject to interception by the likes of "Eve" (a passive attacker who can eavesdrop on messages) and "Mallory" (an active attacker who can maliciously modify messages in transit).</p>
|
||||
<p>Note: By "encrypted" is meant channel encryption with Transport Layer Security (or, for client-to-server connections, legacy SSL) using something other than the null cipher. This protocol does not include more sophisticated information about the connection, such as the cipher suite used, the SASL authentication mechanism used (if any), the certificate identity (if any), the trusted roots involved in certificate authenticate, etc.</p>
|
||||
<p>The answer to the first question is straightforward, since my client knows if its connection to my server is encrypted (as well as the certificates involved).</p>
|
||||
<p>If I trust my server, I can ask it to report on the security of its connection to my contact's server.</p>
|
||||
<p>If I trust my server, I can ask it to report on the security of its connection to my contact's server. (Note: Because server-to-server connections are unidirectional and it is possible for the connection in one direction to be encrypted but for the connection in the opposite direction to be unencrypted, my server MUST NOT report the connection to my contact's server as encrypted unless the connection is encrypted in both directions.)</p>
|
||||
<p>If the server-to-server connection is encrypted and my server trusts that connection, my server can ask my contact's server to report on the security of my contact's connection.</p>
|
||||
<p>By feeling my way along the hops in this manner, I can learn if all three hops are encrypted and therefore can have some assurance that the entire communications path is encrypted.</p>
|
||||
</section2>
|
||||
|
|
|
|||
|
|
@ -22,6 +22,12 @@
|
|||
<supersededby/>
|
||||
<shortname>N/A</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>0.6</version>
|
||||
<date>2007-09-28</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Updated to reflect new scripts and use of mailserver.</remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.5</version>
|
||||
<date>2005-05-26</date>
|
||||
|
|
|
|||
2
xep.dtd
2
xep.dtd
|
|
@ -4,7 +4,7 @@
|
|||
<!ELEMENT header ( title, abstract, legal, number, status, type, sig, approver, dependencies, supersedes, supersededby, shortname, schemaloc*, registry?, expires?, author+, revision+ ) >
|
||||
<!ELEMENT title (#PCDATA)* >
|
||||
<!ELEMENT abstract (#PCDATA)* >
|
||||
<!ELEMENT legal (#PCDATA | link )* >
|
||||
<!ELEMENT legal ( conformance, copyright, permissions, warranty ) >
|
||||
<!ELEMENT number (#PCDATA)* >
|
||||
<!ELEMENT status (#PCDATA)* >
|
||||
<!ELEMENT type (#PCDATA)* >
|
||||
|
|
|
|||
8
xep.ent
8
xep.ent
|
|
@ -179,7 +179,13 @@
|
|||
|
||||
<!-- legal notice required by the XSF's IPR Policy -->
|
||||
|
||||
<!ENTITY LEGALNOTICE "<legal>This XMPP Extension Protocol is copyright 1999 - 2007 by the <link url='http://www.xmpp.org/xsf/'>XMPP Standards Foundation</link> (XSF) and is in full conformance with the XSF's Intellectual Property Rights Policy <<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>>. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<<link url='http://creativecommons.org/licenses/by/2.5/'>http://creativecommons.org/licenses/by/2.5/</link>>).</legal>" >
|
||||
<!ENTITY LEGALNOTICE "
|
||||
<legal>
|
||||
<conformance>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 <<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).</conformance>
|
||||
<copyright>This XMPP Extension Protocol is copyright (c) 1999 - 2007 by the XMPP Standards Foundation (XSF).</copyright>
|
||||
<permissions>This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<<link url='http://creativecommons.org/licenses/by/2.5/'>http://creativecommons.org/licenses/by/2.5/</link>>).</permissions>
|
||||
<warranty>THIS SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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.</warranty>
|
||||
</legal>" >
|
||||
|
||||
<!-- other XSF-related text shortcuts -->
|
||||
|
||||
|
|
|
|||
17
xep.xsl
17
xep.xsl
|
|
@ -51,7 +51,7 @@
|
|||
</meta>
|
||||
<meta>
|
||||
<xsl:attribute name='name'><xsl:text>DC.Rights</xsl:text></xsl:attribute>
|
||||
<xsl:attribute name='content'><xsl:value-of select='/xep/header/legal'/></xsl:attribute>
|
||||
<xsl:attribute name='content'><xsl:value-of select='/xep/header/legal/copyright'/></xsl:attribute>
|
||||
</meta>
|
||||
<!-- END META TAGS FOR DUBLIN CORE -->
|
||||
</head>
|
||||
|
|
@ -350,8 +350,19 @@
|
|||
</xsl:template>
|
||||
|
||||
<xsl:template match='legal'>
|
||||
<h2>Legal Notice</h2>
|
||||
<p class='indent'><xsl:apply-templates/></p>
|
||||
<h2>Legal Notices</h2>
|
||||
<div class='indent'>
|
||||
<h3>IPR Conformance</h3>
|
||||
<xsl:apply-templates select='/xep/header/legal/conformance'/>
|
||||
<h3>Copyright</h3>
|
||||
<xsl:apply-templates select='/xep/header/legal/copyright'/>
|
||||
<h3>Permissions</h3>
|
||||
<xsl:apply-templates select='/xep/header/legal/permissions'/>
|
||||
<!--
|
||||
h3>Warranty</h3>
|
||||
<xsl:apply-templates select='/xep/header/legal/warranty'/>
|
||||
-->
|
||||
</div>
|
||||
</xsl:template>
|
||||
|
||||
<xsl:template match='spec'>
|
||||
|
|
|
|||
Loading…
Reference in New Issue