Named Ports
draft-moss-named-ports-v.01-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | bill Moss | ||
| Last updated | 2002-01-11 | ||
| 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 likely involves a new TCP/IP standard. I'm not so technical to know if it's feasible or informed to know if it exists (perhaps in IPv6), or is proposed. But simply put, in addition to the numbered range of ports used now for IP services like ssh, http, etc., in the interest of security, arbitrary named ports could be used e.g. http://foo.bar.net:mooky, or telnet 0 thisone, further these named ports could be encrypted strings.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)