FYI. I have updated XEP-0068 to reference this spec instead of the old Internet-Draft.
/psa -------- Original Message -------- Subject: BCP 178, RFC 6648 on Deprecating the "X-" Prefix and Similar Constructs in Application Protocols Date: Mon, 25 Jun 2012 10:31:34 -0700 (PDT) From: [email protected] To: [email protected], [email protected] CC: [email protected], [email protected] A new Request for Comments is now available in online RFC libraries. BCP 178 RFC 6648 Title: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols Author: P. Saint-Andre, D. Crocker, M. Nottingham Status: Best Current Practice Stream: IETF Date: June 2012 Mailbox: [email protected], [email protected], [email protected] Pages: 13 Characters: 28393 See Also: BCP0178 I-D Tag: draft-ietf-appsawg-xdash-05.txt URL: http://www.rfc-editor.org/rfc/rfc6648.txt 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 "X-" 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. This document is a product of the Applications Area Working Group Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to [email protected]. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
