Re: [Standards] Suggestion for XEP-0045 : permit alias for the MUC address
On 9/23/11 3:17 PM, EcliptuX wrote: > Le 23/09/2011 23:05, Peter Saint-Andre a écrit : >> On 9/21/11 12:01 PM, EcliptuX wrote: >>> Hi, >>> >>> On my jabber server, I'm running a MUC on the address >>> conference.domain.tld >>> I want to be able to create an alias like muc.domain.tld, but the >>> XEP-0045 don't permit it. >>> >>> Is possible to add this specification in the next release ? >> The specification doesn't restrict the addresses -- I have seen >> conference.jabber.org, muc.xmpp.org, rooms.swift.im, etc. > > I think I was not clear :) > > I have an active room named sa...@conference.onnouscachetout.com > I regret the choice of the term "conference" I regret the choice of "conference.jabber.org" many years ago, too, but it's the best that Peter Millard and I could come up with at the time. > and I want to change it to > a shorter one as "muc" > I want to have my room on sa...@muc.onnouscachetout.com, but I want to > keep the old one working ! I don't want to disturb my guests ! > > So, I really want an alias of @conference.onnouscachetout.com to > @muc.onnouscachetout.com > > And it's look like the XEP-0045 don't support this fonctionnality yet :) In general we don't have JID aliasing. However, this is probably something that your MUC implementation could do for you -- I don't think it's a spec issue but a deployment issue. Peter -- Peter Saint-Andre https://stpeter.im/
Re: [Standards] Suggestion for XEP-0045 : permit alias for the MUC address
Le 23/09/2011 23:05, Peter Saint-Andre a écrit : On 9/21/11 12:01 PM, EcliptuX wrote: Hi, On my jabber server, I'm running a MUC on the address conference.domain.tld I want to be able to create an alias like muc.domain.tld, but the XEP-0045 don't permit it. Is possible to add this specification in the next release ? The specification doesn't restrict the addresses -- I have seen conference.jabber.org, muc.xmpp.org, rooms.swift.im, etc. I think I was not clear :) I have an active room named sa...@conference.onnouscachetout.com I regret the choice of the term "conference" and I want to change it to a shorter one as "muc" I want to have my room on sa...@muc.onnouscachetout.com, but I want to keep the old one working ! I don't want to disturb my guests ! So, I really want an alias of @conference.onnouscachetout.com to @muc.onnouscachetout.com And it's look like the XEP-0045 don't support this fonctionnality yet :)
Re: [Standards] request for reviews: XEP-0045 v1.25rc5
On 9/20/11 6:00 PM, Evgeniy Khramtsov wrote: > On 20.09.2011 08:46, Peter Saint-Andre wrote: >> On 9/19/11 4:40 PM, Alexander Holler wrote: >>> >>> No, but maybe adding some muc-features which are making it obvious what >>> is supported by the server is an option. I don't know if there is an >>> implemention which supports e.g. those voice-requests as described, >>> those I've tested seem not to have it implemented. >> If you test more implementations and find that none of them support the >> feature (and the developers say they have no plans to implement the >> feature), then it might make sense to remove the feature from the spec. >> >> Peter >> > > We have a patch and we are going to include it in the new ejabberd > version. Please don't remove the feature from the spec. Cool, thanks for letting us know. I won't touch that part of the spec. :) /psa
Re: [Standards] Suggestion for XEP-0045 : permit alias for the MUC address
On 9/21/11 12:01 PM, EcliptuX wrote: > Hi, > > On my jabber server, I'm running a MUC on the address conference.domain.tld > I want to be able to create an alias like muc.domain.tld, but the > XEP-0045 don't permit it. > > Is possible to add this specification in the next release ? The specification doesn't restrict the addresses -- I have seen conference.jabber.org, muc.xmpp.org, rooms.swift.im, etc. Peter -- Peter Saint-Andre https://stpeter.im/
[Standards] UPDATED REGISTRY: Jingle Transport Methods
The Jingle Transport Methods registry has been updated. Version: 0.2 Changelog: Added the "ibb" and "s5b" transports from XEP-0261 and XEP-0260, respectively. (psa) URL: http://xmpp.org/registrar/jingle-transports.html
[Standards] UPDATED REGISTRY: Jabber/XMPP Protocol Namespaces
The Jabber/XMPP Protocol Namespaces registry has been updated. Version: 0.41 Changelog: Added urn:xmpp:jingle:transports:ibb:1 and urn:xmpp:jingle:transports:s5b:1 from XEP-0261 and XEP-0260, respectively. (psa) URL: http://xmpp.org/registrar/namespaces.html
[Standards] DRAFT: XEP-0261 (Jingle In-Band Bytestreams Transport Method)
Version 1.0 of XEP-0261 (Jingle In-Band Bytestreams Transport Method) has been released. Abstract: This specification defines a Jingle transport method that results in sending data via the In-Band Bytestreams (IBB) protocol defined in XEP-0047. Essentially this transport method reuses XEP-0047 semantics for sending the data and defines native Jingle methods for starting and ending an IBB session. Changelog: Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa) Diff: http://xmpp.org/extensions/diff/api/xep/0261/diff/0.8/vs/1.0 URL: http://xmpp.org/extensions/xep-0261.html
[Standards] DRAFT: XEP-0260 (Jingle SOCKS5 Bytestreams Transport Method)
Version 1.0 of XEP-0260 (Jingle SOCKS5 Bytestreams Transport Method) has been released. Abstract: This specification defines a Jingle transport method that results in sending data via the SOCKS5 Bytestreams (S5B) protocol defined in XEP-0065. Essentially this transport method reuses XEP-0065 semantics for sending the data and defines native Jingle methods for starting and ending an S5B session. Changelog: Per a vote of the XMPP Council, advanced specification from Experimental to Draft; also added a further note about calculation of the 'dstaddr' attribute. (psa) Diff: http://xmpp.org/extensions/diff/api/xep/0260/diff/0.9/vs/1.0 URL: http://xmpp.org/extensions/xep-0260.html
