Re: [Standards] Incorrect example in XEP-0198?
On Tue, 18 May 2021 at 20:38, Peter Saint-Andre wrote: > +1. Example 6 looks like a copy-paste error. Who wrote these specs?!? > > Thankfully, for years we either couldn't, or at least normally didn't, commit directly to the XEP repository ourselves, and left it to the Editor to actually commit the changes. Nobody will ever know it was probably me. Dave. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Incorrect example in XEP-0198?
On 5/7/21 7:33 AM, Edwin Mons wrote: > On 07/05/2021 14:33, Kevin Smith wrote: >> On 7 May 2021, at 13:30, Matthew Wild wrote: >>> On Fri, 7 May 2021 at 12:10, Edwin Mons wrote: Hi all, I was looking at XEP-0198, and noticed something odd in Example 6. Shouldn't that have been a stream error instead, as the text above states? If so, will send out a PR. >>> Which is correct? The text or the example? While I was originally >>> inclined to agree that this should be a stream error, it should be >>> noted that section 6 "Error Handling" states: >>> >>> "If an error occurs with regard to an or >>> element, the server MUST return a element." >>> >>> and >>> >>> "Stream management errors SHOULD be considered recoverable; however, >>> misuse of stream management MAY result in termination of the stream." >>> >>> It's relevant in the context that a stream error will terminate the >>> session (such that it can't be resumed). >>> >>> I don't feel strongly either way. >> The text in question mentions wanting the connection terminated, which >> suggests stream error is right (which also seems logically sound to me). >> >> "If a server receives a second element it SHOULD respond with a >> stream error, thus terminating the client connection.” > > This was indeed how I interpreted the text and am inclined to implement. +1. Example 6 looks like a copy-paste error. Who wrote these specs?!? /psa ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Incorrect example in XEP-0198?
On Fri, 7 May 2021 at 14:34, Edwin Mons wrote: > On 07/05/2021 14:33, Kevin Smith wrote: > > The text in question mentions wanting the connection terminated, which > suggests stream error is right (which also seems logically sound to me). > > > > "If a server receives a second element it SHOULD respond with > a stream error, thus terminating the client connection.” > > This was indeed how I interpreted the text and am inclined to implement. > Yes, I think that you want to emit a stream error here. Rationale: A client sending a second is unambiguously broken. There's three possible outcomes here: * The server responds , and the client accepts its second has failed but its first is still in effect. * The server responds , and the client turns off stream management entirely. * The server responds with a stream error, and the client goes away. The server cannot know which of the first two a client might do if it sends , and moreover, even if we tried to specify that, the client is unambiguously demonstrating it's broken anyway, so we still wouldn't know. Therefore the only safe thing is to issue a stream error explaining the situation and disconnect. Any opinions on what stream error to send? I think we may be in to territory; nothing else seems to fit. Dave. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] XMPP Council Agenda 2021-05-19
Hi everyone, The next XMPP Council Meeting will take place on 2021-05-19 at 15:00Z in xmpp:coun...@muc.xmpp.org?join. Everyone is welcome to join and add to the discussions. This agenda is composed from: - Editor notifications to standards@ - xsf/xeps GitHub PRs marked as Needs Council - xsf/xeps GitLab MRs marked as Needs Council - Suggestions directly sent to me (see below) Agenda as follows: 1) Roll Call 2) Agenda Bashing * Feel free to pre-bash on-list or directly to me if you think something is missing. 3) Editor’s Update * Nothing. 4) Items for voting None. 5) Pending Votes None. 6) Date of Next 7) AOB 7a) Open access model for PEP nodes Context: https://github.com/xsf/xeps/pull/1059 8) Close End of Agenda. Note that I am aiming for 30 minutes, but meetings may be extended as necessary if all council members agree. Meetings are normally held every Wednesday at 15:00 UTC in the xmpp:coun...@muc.xmpp.org?join chatroom. Meetings are open, and anyone (XSF Member or not) may attend, though only XMPP Council members may vote. Relevant comments from the floor are welcomed. Using your web browser, you can join anonymously via https://xmpp.org/chat?council Note that conversations in the room are logged publicly at https://logs.xmpp.org/council/ If you have suggestions for an agenda item, you can message me via XMPP or email at this address or at jo...@zombofant.net. I aim to publish the Agenda on the day before the Council meeting before 19:00Z. Stay safe, smart & healthy, Jonas signature.asc Description: This is a digitally signed message part. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
