[Standards-JIG] JEP-0065: JID restriction

Peter Saint-Andre stpeter at jabber.org
Fri Feb 17 18:40:14 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently, Section 4.6 of JEP-0065 (SOCKS5 Bytestreams) states:

***

Once the Target has successfully authenticated with the Proxy (even
anonymously), it SHOULD send a CONNECT request to a host named: SHA1(SID
+ Initiator JID + Target JID), port 0, where the SHA1 hashing algorithm
is specified by RFC 3174 [8]. The JIDs provided MUST be full JIDs (i.e.,
<user at host/resource>); furthermore, in order to ensure proper results,
the appropriate stringprep profiles (as specified in XMPP Core [9]) MUST
be applied to the JIDs before application of the SHA1 hashing algorithm.

***

The requirement that JIDs be of the form <node at domain.tld/resource>
seems overly restrictive (since any kind of entity could engage in file
transfer, not just connected IM users). Therefore I propose that we
remove this restriction.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD9hiNNF1RSzyt3NURAj86AKCLAjKiLTk6W0CnriORFBC6HaN0TACgw7RX
OOVsIEDLg6vaPpD2WrswIM8=
=NYZY
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060217/c71689c8/attachment.bin>


More information about the Standards mailing list