Re: [Standards] roster schema
Yes, it is a good idea to define more granular errors for these conditions. I'll try to add those to the -04 draft, since I will probably submit the -03 draft today and won't have time to do this (mostly today I'm just going to check for egregious errors). The reason for the hurry is that there's an IETF deadline of first-thing Monday morning to submit Internet-Drafts before IETF 69, missing that deadline will mean the -03 drafts would not be published until after July 23 and I'd like to get my updated documents out there before then so I can gather feedback. Cool OK. It's not set in stone, it's set in wax (SHOULD not MUST). But I'm not going to spend more time on this so I retract the recommendation (not requirement) of limiting the size to 1024 characters or whatever. One thing I was thinking of along these lines would be rather than set the sizes in this way regarding how clients would interact with the server, have a implementation guide for server developers to the recommended sizing for certain fields, not sure if the place for that would be in the RFC but it would help developers by letting them immediately see how they will need to likely size their databases without having to go out and look at other existing XMPP software to try and determine what others are doing first, just a thought. Richard
Re: [Standards] roster schema
Richard Dobson wrote: One thing I was thinking of along these lines would be rather than set the sizes in this way regarding how clients would interact with the server, have a implementation guide for server developers to the recommended sizing for certain fields, not sure if the place for that would be in the RFC but it would help developers by letting them immediately see how they will need to likely size their databases without having to go out and look at other existing XMPP software to try and determine what others are doing first, just a thought. Well, we've always needed an implementation guide. Probably one for server developers and another for client developers. IMHO that would be a great project for a few people to work on (perhaps after the next set of RFCs is published, or concurrent with the RFC process). I don't think all those implementation details belong in the RFCs, however. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
[Standards] UPDATED: XEP-0205 (Best Practices to Discourage Denial of Service Attacks)
Version 0.2 of XEP-0205 (Best Practices to Discourage Denial of Service Attacks) has been released. Abstract: This document recommends a number of practices that can help discourage denial of service attacks on XMPP-based networks. Changelog: Add recommendation regarding multiple messages to distinct recipients; removed numerical recommendations since they are a matter of implementation or deployment. (psa) Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0205.xml?r1=590r2=1030 URL: http://www.xmpp.org/extensions/xep-0205.html
Re: [Standards] XEP-0004: Data Forms - Open Issues
Peter Saint-Andre wrote: http://www.xmpp.org/extensions/tmp/xep-0004-2.9.html http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0004.xml?r1=851r2=1031 We had a discussion [1] about ordering of items in the jdev room today so I've made an adjustment [2] to clarify that as well. /psa [1] http://www.jabber.org/muc-logs/[EMAIL PROTECTED]/2007-07-10.html#12:26:19 [2] http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0004.xml?r1=1031r2=1033 smime.p7s Description: S/MIME Cryptographic Signature
[Standards] XEP-0077: clarification and correction
Based on a message I received off-list, I've provisionally made one clarification and one correction to XEP-0077 (In-Band Registration): http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0077.xml?r1=535r2=1032 http://www.xmpp.org/extensions/tmp/xep-0077-2.3.html#usecases-cancel /psa smime.p7s Description: S/MIME Cryptographic Signature
[Standards] XEP-0115 1.4pre1
I've made a first pass at updating XEP-0115 (Entity Capabilities) in line with recent list discussion: http://www.xmpp.org/extensions/tmp/xep-0115-1.4.html http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0115.xml?r1=742r2=1035 Feedback is welcome as always. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
