Deprecating Use of the "X-" Prefix in Application Protocols
draft-saintandre-xdash-03

 
Document Type Replaced Internet-Draft (individual)
Last updated 2011-09-14 (latest revision 2011-07-26)
Replaced by draft-ietf-appsawg-xdash
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-appsawg-xdash
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-saintandre-xdash-03.txt

Abstract

Historically, there has often been a perceived distinction between "standard" and "non-standard" parameters (such as media types and header fields), by prefixing the latter with the string "X-" or similar constructions (e.g., "x."). In practice, this convention causes more problems than it solves. Therefore, this document deprecates the "X-" convention for most application protocol parameters.

Authors

Peter Saint-Andre (psaintan@cisco.com)
dcrocker (dcrocker@bbiw.net)
mnot (mnot@mnot.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)