<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.iab-protocol-maintenance" target="https://datatracker.ietf.org/doc/html/draft-iab-protocol-maintenance-09">
   <front>
      <title>Maintaining Robust Protocols</title>
      <author initials="M." surname="Thomson" fullname="Martin Thomson">
         <organization>Mozilla</organization>
      </author>
      <author initials="D." surname="Schinazi" fullname="David Schinazi">
         <organization>Google LLC</organization>
      </author>
      <date month="October" day="18" year="2022" />
      <abstract>
	 <t>   The main goal of the networking standards process is to enable the
   long term interoperability of protocols.  This document describes
   active protocol maintenance, a means to accomplish that goal.  By
   evolving specifications and implementations, it is possible to reduce
   ambiguity over time and create a healthy ecosystem.

   The robustness principle, often phrased as &quot;be conservative in what
   you send, and liberal in what you accept&quot;, has long guided the design
   and implementation of Internet protocols.  However, it has been
   interpreted in a variety of ways.  While some interpretations help
   ensure the health of the Internet, others can negatively affect
   interoperability over time.  When a protocol is actively maintained,
   protocol designers and implementers can avoid these pitfalls.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-iab-protocol-maintenance-09" />
   
</reference>
