datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)
draft-ietf-dane-use-cases-05

RFC
Document Stream: IETF
Last updated: 2011-07-28
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (dane)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6394
IANA Action State: No IC 
Responsible AD: Stephen Farrell
IESG Note: Ond?ej Sur� (ondrej.sury@nic.cz) is the Document Shepherd.
Send notices to: dane-chairs@tools.ietf.org, draft-ietf-dane-use-cases@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-dane-use-cases.

Abstract:
Many current applications use the certificate-based authentication features in Transport Layer Security (TLS) to allow clients to verify that a connected server properly represents a desired domain name. Typically, this authentication has been based on PKIX certificate chains rooted in well-known certificate authorities (CAs), but additional information can be provided via the DNS itself. This document describes a set of use cases in which the DNS and DNS Security Extensions (DNSSEC) could be used to make assertions that support the TLS authentication process. The main focus of this document is TLS server authentication, but it also covers TLS client authentication for applications where TLS clients are identified by domain names. [STANDARDS-TRACK]

Authors:
Richard Barnes <rbarnes@bbn.com>

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