mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-24 02:02:16 -05:00
Clarify text in burner JID protoxep
This commit is contained in:
parent
36e6792b5a
commit
0f3629bc87
@ -22,7 +22,7 @@
|
|||||||
</dependencies>
|
</dependencies>
|
||||||
<supersedes/>
|
<supersedes/>
|
||||||
<supersededby/>
|
<supersededby/>
|
||||||
<shortname>NOT_YET_ASSIGNED</shortname>
|
<shortname>burner</shortname>
|
||||||
&sam;
|
&sam;
|
||||||
<revision>
|
<revision>
|
||||||
<version>0.0.1</version>
|
<version>0.0.1</version>
|
||||||
@ -36,18 +36,18 @@
|
|||||||
In many XMPP applications it is desirable to be able to act anonymously to
|
In many XMPP applications it is desirable to be able to act anonymously to
|
||||||
prevent leaking personally identifiable information (PII) to a third party.
|
prevent leaking personally identifiable information (PII) to a third party.
|
||||||
Traditionally this is accomplished using SASL authentication and the
|
Traditionally this is accomplished using SASL authentication and the
|
||||||
ANONYMOUS mechanism as detailed in &xep0175;, however, ANONYMOUS auth
|
ANONYMOUS mechanism as detailed in &xep0175;, however, the ANONYMOUS
|
||||||
provides no mechanism for changing identities (requesting a new JID) without
|
mechanism is in reality an authorization mechanism and does not provide
|
||||||
creating a new session, nor does it provide authentication of users.
|
authentication of users.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
This specification solves these problems by decoupling anonymous identity
|
This specification solves these problems by decoupling anonymous identity
|
||||||
management from authentication.
|
management from authentication (auth) and authorization (authz).
|
||||||
This allows logged in users (authenticated or anonymous at the server
|
This allows logged in users (authenticated or anonymous at the server
|
||||||
operators disgression) to request a new temporary identifier, a "burner"
|
operators disgression) to request a new temporary identifier, a "burner"
|
||||||
JID, which may be used by its owner to construct a new session with the
|
JID, which may be used by its owner to construct a new session with the
|
||||||
server that is anonymous to third parties but is (optionally) locally
|
server that is authorized to communicate anonymously with third parties and
|
||||||
authenticated.
|
is (optionally) locally authenticated.
|
||||||
</p>
|
</p>
|
||||||
</section1>
|
</section1>
|
||||||
<section1 topic='Glossary' anchor='glossary'>
|
<section1 topic='Glossary' anchor='glossary'>
|
||||||
@ -145,19 +145,20 @@
|
|||||||
to='caiusmarcius@example.net/corioli'
|
to='caiusmarcius@example.net/corioli'
|
||||||
id='k3hs5174'>
|
id='k3hs5174'>
|
||||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||||
<identity category='conference' type='text'/>
|
<identity type='im' name='MyServer' category='server'/>
|
||||||
<identity category='authz' type='ephemeral'/>
|
<identity type='pep' name='MyServer' category='pubsub'/>
|
||||||
|
<identity type='ephemeral' category='authz'/>
|
||||||
…
|
…
|
||||||
<feature var='http://jabber.org/protocol/disco#info'/>
|
<feature var='http://jabber.org/protocol/disco#info'/>
|
||||||
<feature var='http://jabber.org/protocol/disco#items'/>
|
<feature var='http://jabber.org/protocol/disco#items'/>
|
||||||
<feature var='http://jabber.org/protocol/muc'/>
|
<feature var='http://jabber.org/protocol/muc'/>
|
||||||
…]]></example>
|
…]]></example>
|
||||||
</section1>
|
</section1>
|
||||||
<section1 topic='Implementation Notes' anchor='impl'>
|
<section1 topic='Implementation Notes' anchor='impl'>
|
||||||
<p>
|
<p>
|
||||||
It may be impractical to store verification information for every burner JID
|
It may be impractical to store verification information for every burner JID
|
||||||
issued by the system.
|
issued by the system.
|
||||||
To this end servers that implement this specification may choose to encode
|
To this end servers that implement this specification MAY choose to encode
|
||||||
information into the localpart of issued burner JIDs which can be verified
|
information into the localpart of issued burner JIDs which can be verified
|
||||||
when a user attempts to authorize a new session to use the burner JID.
|
when a user attempts to authorize a new session to use the burner JID.
|
||||||
If an implementation chooses to do this it is RECOMMENDED that an
|
If an implementation chooses to do this it is RECOMMENDED that an
|
||||||
|
Loading…
Reference in New Issue
Block a user