Editing RFB (protocol) (section)

== Versions ==

Published versions of the RFB protocol are as follows:

{| class="wikitable"
|-
! Version
! Published
! Date
! Specification
|-
| RFB 3.3
| ORL
| January 1998
| [https://web.archive.org/web/20140921005313/http://grox.net/doc/apps/vnc/rfbproto.pdf The Remote Framebuffer Protocol 3.3]
|-
| RFB 3.7
| RealVNC Ltd
| August 2003
| [https://web.archive.org/web/20040325204925/http://www.realvnc.com/docs/rfbproto.pdf The Remote Framebuffer Protocol 3.7]
|-
| RFB 3.8 (current)
| RealVNC Ltd
| June 2007
| [https://web.archive.org/web/20070703000012/http://www.realvnc.com/docs/rfbproto.pdf The Remote Framebuffer Protocol 3.8]
|-
| IETF RFC (3.8)
| RealVNC Ltd
| March 2011
| {{IETF RFC|6143}}
|}

Developers are free to add additional encoding and security types but they must book unique identification numbers for these with the maintainers of the protocol so that the numbers do not clash. Clashing type numbers would cause confusion when handshaking a connection and break cross-compatibility between implementations. The list of encoding and security types was maintained by RealVNC Ltd and is separate from the protocol specification so that new types can be added without requiring the specification to be reissued. Since December 2012, the list went to [[IANA]].<ref>{{cite web |title=Remote Framebuffer (RFB) |url=https://www.iana.org/assignments/rfb/rfb.xml |website=www.iana.org}}</ref>

A community version of the RFB protocol specification which aims to document all existing extensions is hosted by the [[TigerVNC]] project.<ref name="rfbproto"/>