DNS Redirect Use by Service Providers
draft-livingood-dns-redirect-03

Document Type Expired Internet-Draft (individual)
Last updated 2010-10-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-livingood-dns-redirect-03.txt

Abstract

The objective of this document is to describe the design of so-called DNS Redirect services deployed today by Internet Service Providers (ISPs), DNS Application Service Providers (ASPs), and other organizations providing so-called DNS Redirect services via their recursive DNS servers, as well as to describe the recommended practices regarding relating to DNS redirect. This document specifically and narrowly addresses those cases where DNS Redirect is being utilized to provide a web error redirect service to end users, and describes the critical implications for DNS Redirect when DNSSEC is deployed.

Authors

Tom Creighton (tom_creighton@cable.comcast.com)
Chris Griffiths (chris_griffiths@cable.comcast.com)
Jason Livingood (jason_livingood@cable.comcast.com)
Ralf Weber (rw@hohensolms.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)