Protocol ossification: Difference between revisions

Content deleted Content added
mNo edit summary
m Turned “RFC 8701” text into a clickable link
Line 8:
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>
 
GREASE, described in RFC{{IETF RFC|8701}}, adds randomly generated unknown options to TLS connections to prevent middleboxes from blocking unknown values. It is an attempt to stop the TLS protocol from "rusting shut" in the future.<ref>{{Cite web|url=https://tools.ietf.org/html/rfc8701|title=Applying GREASE to TLS Extensibility|last=Benjamin|first=David|website=tools.ietf.org|language=en|access-date=2020-06-23|date=January 2020}}</ref>
 
== See also ==