Use of SRV records in conjuction with HTTP and URIs"
draft-andrews-http-srv-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark P. Andrews , Thor Kottelin | ||
| Last updated | 2014-11-20 (Latest revision 2014-05-19) | ||
| 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
The combined use of SRV records for HTTP along with URIs is not as straight forward as it would appear at first glance. This document looks at the issues involved and recommends solutions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)