metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP178

RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC6648
Published
June 2012
Authors
P. Saint-Andre; D. Crocker; M. Nottingham
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
art
Pages
13
Also known as
BCP178

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6648-deprecating-the-x-prefix-and-similar-constructs-in-application-protocols