Concerns with the use of Proprietary Application Codes
draft-doolan-ccamp-proprietary-ac-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul Doolan | ||
| Last updated | 2015-04-30 (Latest revision 2014-10-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document explains the terms Application Code and Application Identifier and points out a danger that exists when proprietary application codes are used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)