diff --git a/xep-0047.xml b/xep-0047.xml index f02e4c42..56f592b8 100644 --- a/xep-0047.xml +++ b/xep-0047.xml @@ -11,6 +11,7 @@ &LEGALNOTICE; 0047 Draft + Standards Track Standards @@ -24,6 +25,12 @@ ibb &infiniti; &stpeter; + + 2.0rc1 + 2012-06-12 + psa +

Per a vote of the XMPP Council, advanced to Final; in addition, specified that the 'block-size' attribute defines the size of the data chunk before instead of after base64-encoding, to accord with existing implementations.

+
1.3 2011-03-01 @@ -172,7 +179,7 @@

If the responder informs the initiator that it wishes to proceed with the session, the initiator can begin to send data over the bytestream (in addition, because the bytestream is bidirectional, the responder can also send data; see the Bidirectionality section of this document for details).

-

Each chunk of data is contained in a <data/> element qualified by the 'http://jabber.org/protocol/ibb' namespace. The data element SHOULD be sent in an IQ stanza to enable proper tracking and throttling, but instead MAY be sent in a message stanza. The base64-encoded data to be sent, prior to any wrapping in the <data/> element and IQ or message stanza, MUST NOT be larger than the 'block-size' determined in the bytestream negotiation.

+

Each chunk of data is contained in a <data/> element qualified by the 'http://jabber.org/protocol/ibb' namespace. The data element SHOULD be sent in an IQ stanza to enable proper tracking and throttling, but instead MAY be sent in a message stanza. The data to be sent, prior to base64-encoding and prior to any wrapping in XML, MUST NOT be larger than the 'block-size' determined in the bytestream negotiation.

-

Thanks to Fabio Forno for his feedback.

+

Thanks to Sergey Dobrov, Fabio Forno, Todd Herman, Lance Stout, and Matthew Wild for their feedback.