A la carte: Announcing the supported transport protocols via DNS
draft-yourtchenko-tran-announce-dns-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andrew Yourtchenko , Dan Wing | ||
| Last updated | 2010-03-31 | ||
| 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
While TCP has enjoyed many enhancements over the decades, it is useful to allow applications to use new transports, such as SCTP. It is inefficient to naively probe the server using the new transport protocol. This document proposes a new DNS resource record which provides an efficient way to query which protocols are supported by a server. The presence of this record will allow the client to avoid the excessive probing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)