Browse Prior Art Database

Using DNS-Based Authentication of Named Entities (DANE) TLSA Records with SRV Records (RFC7673)

IP.com Disclosure Number: IPCOM000245025D
Original Publication Date: 2015-Oct-01
Included in the Prior Art Database: 2016-Feb-06
Document File: 32 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Finch: AUTHOR [+3]

Abstract

The base DNS-Based Authentication of Named Entities (DANE) specification [RFC6698] describes how to use TLSA resource records secured by DNSSEC [RFC4033] to associate a target server's connection endpoint with its Transport Layer Security (TLS) certificate (thus enabling administrators of domain names to specify the keys used in that domain's TLS servers). Some application protocols locate connection endpoints indirectly via SRV records [RFC2782]. As a result of this indirection, the rules specified in [RFC6698] cannot be directly applied to such application protocols. (Rules for SMTP [RFC5321], which uses MX resource records instead of SRV records, are described in [RFC7672].)

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                          T. Finch Request for Comments: 7673                       University of Cambridge Category: Standards Track                                      M. Miller ISSN: 2070-1721                                      Cisco Systems, Inc.                                                           P. Saint-Andre                                                                     &yet                                                             October 2015

         Using DNS-Based Authentication of Named Entities (DANE)                      TLSA Records with SRV Records

Abstract

   The DNS-Based Authentication of Named Entities (DANE) specification    (RFC 6698) describes how to use TLSA resource records secured by    DNSSEC (RFC 4033) to associate a server's connection endpoint with    its Transport Layer Security (TLS) certificate (thus enabling    administrators of domain names to specify the keys used in that    domain's TLS servers).  However, application protocols that use SRV    records (RFC 2782) to indirectly name the target server connection    endpoints for a service domain name cannot apply the rules from RFC    6698.  Therefore, this document provides guidelines that enable such    protocols to locate and use TLSA records.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7673.

Finch, et al.                Standards Track                    [Page 1]
 RFC 7673                      TLSA and SRV                  October 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Comp...