Changes

Line 2: Line 2:     
==Origins and Usage==
 
==Origins and Usage==
Hubert notes that, as early as 2000, [[Randy Bush]] was using the analogy of a "camel"<ref>[https://www.ietf.org/proceedings/49/slides/PLENARY-3/sld043.htm IETF 49 Archive - "How we Made this Camel" slide from The DNS Today: Are we Overloading the Saddlebags on an Old Horse?], December 13, 2000</ref> (as well as the precursor pack animal of the "last straw" metaphor, the horse), in a presentation to IETF at its 49th meeting entitled "The DNS Today: Are we Overloading the Saddlebags on an Old Horse?"<ref name="bush">[https://www.ietf.org/proceedings/49/slides/PLENARY-3/index.html IETF 49 Archive - Plenary Session - The DNS Today: Are we Overloading the Saddlebags on an Old Horse?], presented by Randy Bush, December 13, 2000</ref><ref name="hubert" /> Bush posited that multiple factors, including user expectations, application development demands, design by committee, and others were pushing DNS operators to continuing adding loads onto the DNS architecture. Bush's presentation was bolstered by his uses of the "last straw" metaphor, which emphasized that the addition of a small burden could cause a surprising, global, and catastrophic effect.<ref name="wikipedia" />  
+
Hubert notes that, as early as 2000, [[Randy Bush]] was using the analogy of a "camel"<ref>[https://www.ietf.org/proceedings/49/slides/PLENARY-3/sld043.htm IETF 49 Archive - "How we Made this Camel" slide from The DNS Today: Are we Overloading the Saddlebags on an Old Horse?], December 13, 2000</ref> (as well as the precursor pack animal of the "last straw" metaphor, the horse), in a presentation to IETF at its 49th meeting entitled "The DNS Today: Are we Overloading the Saddlebags on an Old Horse?"<ref name="bush">[https://www.ietf.org/proceedings/49/slides/PLENARY-3/index.html IETF 49 Archive - Plenary Session - The DNS Today: Are we Overloading the Saddlebags on an Old Horse?], presented by Randy Bush, December 13, 2000</ref><ref name="hubert" /> Bush posited that multiple factors, including user expectations, application development demands, design by committee, and others were pushing DNS operators to continue adding loads onto the DNS architecture. Bush's presentation was bolstered by his uses of the "last straw" metaphor, which emphasized that the addition of a small burden could cause a surprising, global, and catastrophic effect.<ref name="wikipedia" />  
    
Common usage of the phrase "DNS Camel," however, appears to largely date to Hubert's presentation, as well as his development of the "DNS Camel" tracker for [[RFC]]s related to the DNS,<ref>[https://powerdns.org/dns-camel/ PowerDNS.org - DNS Camel]</ref> which was also posted to GitHub in March 2018<ref>[https://github.com/ahupowerdns/protocol-camel/graphs/contributors Github - protocol-camel Contributor Graph]</ref>  
 
Common usage of the phrase "DNS Camel," however, appears to largely date to Hubert's presentation, as well as his development of the "DNS Camel" tracker for [[RFC]]s related to the DNS,<ref>[https://powerdns.org/dns-camel/ PowerDNS.org - DNS Camel]</ref> which was also posted to GitHub in March 2018<ref>[https://github.com/ahupowerdns/protocol-camel/graphs/contributors Github - protocol-camel Contributor Graph]</ref>  
 
* Hubert noted a lot of continued discussion about the "DNS Camel" at IETF 101.<ref name="hubert" />
 
* Hubert noted a lot of continued discussion about the "DNS Camel" at IETF 101.<ref name="hubert" />
* A since-expired Internet Draft from November 2018, dealing with simplifying EDNS implementation, employed the tag "camel-diet" in its document ID.<ref>[https://datatracker.ietf.org/doc/draft-spacek-edns-camel-diet/ IETF Data Tracker - Internet Draft: Minimal EDNS compliance requirements], last updated November 30, 2018</ref>  
+
* A since-expired Internet Draft from November 2018, dealing with simplifying EDNS implementation, employed the tag "camel-diet" in its document ID.<ref>[https://datatracker.ietf.org/doc/draft-spacek-edns-camel-diet/ IETF Data Tracker - Internet Draft: Minimal EDNS compliance requirements], last updated November 30, 2018</ref>
    
==Issues==
 
==Issues==
Bureaucrats, Check users, lookupuser, Administrators, translator
3,197

edits