1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 02:02:16 -05:00

acks & sec

This commit is contained in:
Peter Saint-Andre 2015-10-12 21:13:43 -06:00 committed by Kevin Smith
parent 5472b7ef79
commit 21793cd1d3

View File

@ -418,14 +418,6 @@
<p></p>
<example caption="" ><![CDATA[
]]></example>
</section3>
<section3 topic='' anchor='usecase-admin-'>
<p></p>
<example caption="" ><![CDATA[
]]></example>
</section3>
@ -435,7 +427,7 @@
<section1 topic='Configuration options' anchor='config'>
<section2 topic='Transparency' anchor="config-transparency">
<p>TODO: SemiAnon/NonAnom</p>
<p>TODO: transparent vs. opaque conversations</p>
</section2>
</section1>
@ -449,26 +441,35 @@
</section1>
<section1 topic='Accessibility Considerations' anchor='access'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>OPTIONAL.</p>
</section1>-->
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>TBD.</p>
<p>Discuss normalization of nicknames.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>This specification doesn't add additional security considerations beyond those of its dependencies.</p>
<p>TBD.</p>
<p>Topics to cover:</p>
<ul>
<li>transparent vs. opaque conversations</li>
<li>nickname registration and security implications of normalization</li>
</ul>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>None.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>Needs a namespace.</p>
<p>Register a namespace.</p>
</section1>
<section1 topic='XML Schema' anchor='schema'>
<p>TBD.</p>
</section1>
<section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to the participants in XMPP Summit 18 for their significant input during design sessions: Dave Cridland, Philipp Hancke, Waqas Hussain, Lance Stout, Sam Whited, and Matthew Wild.</p>
</section1>
</xep>
<!--TODO: Query whole service for MAM. Provide data form for filtering by node ID.
TODO: Two config nodes - one public read one private read?
TODO: Open Issue: How many config nodes do you need? Do you do different access to different items within a node for reading? Writing?
TODO: Subscription option to check conversation config (e.g. anonymity) before join.
TODO: Subscription option to check conversation config (e.g. transparency of JIDs) before join.
-->