<?xml version='1.0' encoding='UTF-8'?>

<reference  anchor='RFC6648' target='https://www.rfc-editor.org/info/rfc6648'>
<front>
<title>Deprecating the &quot;X-&quot; Prefix and Similar Constructs in Application Protocols</title>
<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'><organization /></author>
<author initials='D.' surname='Crocker' fullname='D. Crocker'><organization /></author>
<author initials='M.' surname='Nottingham' fullname='M. Nottingham'><organization /></author>
<date year='2012' month='June' />
<abstract><t>Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string &quot;X-&quot; or similar constructs.  In practice, that convention causes more problems than it solves.  Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice.</t></abstract>
</front>
<seriesInfo name='BCP' value='178'/>
<seriesInfo name='RFC' value='6648'/>
<seriesInfo name='DOI' value='10.17487/RFC6648'/>
</reference>
