From d08bc7e9c866a7452ab96769137e73749c950709 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 22 Feb 2010 04:40:24 +0000 Subject: [PATCH] corrected examples git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3975 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0165.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0165.xml b/xep-0165.xml index f9b61ff2..5cabaef7 100644 --- a/xep-0165.xml +++ b/xep-0165.xml @@ -137,11 +137,11 @@

We have seen that, at a minimum, three names or address types are needed to provide a petname system for XMPP: a JID, a nickname, and a handle (preferably strengthened by inclusion of a fingerprint derived from a key). However, at present a subscription request contains only the JID of the sender:

+ ]]>

Naturally, based on the JID, it is possible to pull information about the sender from a persistent data store such as an LDAP database, &xep0054; node, or future profile system (see &xep0154;). However, to speed interactions, this document recommends that when a client sends a subscription request, it SHOULD include the preferred nickname of the sender (encapsulated via the format specified in XEP-0172) and the sender's key or keys.

+ psa stpeterRSAkey1