Content deleted Content added
m Disambiguating links to Firewall (link changed to Firewall (computing)) using DisamAssist. |
m Disambiguated: tunnelling → tunneling protocol |
||
Line 4:
For example, protocol ossification initially prevented the adoption of [[TLS 1.3]], a problem which was fixed by a [[workaround]] which introduced elements into the TLS 1.3 handshake which appeared (falsely) to middleboxes to be a TLS 1.2 handshake.<ref>{{Cite web|url=https://blog.cloudflare.com/why-tls-1-3-isnt-in-browsers-yet/|title=Why TLS 1.3 isn't in browsers yet|date=2017-12-26|website=The Cloudflare Blog|language=en|access-date=2020-03-14}}</ref>
Protocol ossification can be avoided by the use of [[encryption]] or [[tunneling protocol|tunnelling]] to hide the structure of new protocol extensions from older middleboxes.<ref name=LWN>{{Cite web|url=https://lwn.net/Articles/745590/|title=QUIC as a solution to protocol ossification|website=lwn.net|access-date=2020-03-14|first=Jonathan|last=Corbet|date=January 29, 2018}}</ref> [[QUIC]] is an examples of a protocol which uses encryption to avoid middleboxes.<ref>{{Cite web|url=https://blog.cloudflare.com/the-road-to-quic/|title=The Road to QUIC|date=2018-07-26|website=The Cloudflare Blog|language=en|access-date=2020-03-14}}</ref>
The [[Internet Engineering Task Force]] created the Transport Services Working Group (TAPS WG) in 2015 as an attempt to address the problem.<ref>{{Cite web|url=https://www.iab.org/wp-content/IAB-uploads/2014/12/semi2015_welzl.pdf|title=Ossification: a result of not even trying?|first=Michael|last=Welzl|first2=Gorry|last2=Fairhurst|first3=David|last3=Ros|date=2015|website=www.iab.org|url-status=live|archive-url=|archive-date=|access-date=}}</ref>
| |||