"X-" Considered Harmful
draft-saintandre-xdash-considered-harmful-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Peter Saint-Andre | ||
| Last updated | 2014-07-02 (Latest revision 2010-10-19) | ||
| Replaced by | draft-ietf-appsawg-xdash | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-appsawg-xdash | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many application protocols use named parameters to represent data (for example, header fields in Internet mail messages and HTTP requests). Historically, protocol designers and implementers have often differentiated between "standard" and "experimental" parameters by prefixing experimental parameters with the string "X-". This document argues that, on balance, the "X-" convention has more costs than benefits.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)