A DANE Record and DNSSEC Authentication Chain Extension for TLS
draft-ietf-tls-dnssec-chain-extension-04
|
| Document |
Type |
|
Active Internet-Draft (tls WG)
|
|
Last updated |
|
2017-07-20
(latest revision 2017-06-01)
|
|
Replaces |
|
draft-shore-tls-dnssec-chain-extension
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
(wg milestone:
May 2017 - DANE Record and DNSS...
)
Revised I-D Needed - Issue raised by WGLC
|
|
Document shepherd |
|
Joseph Salowey
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Joseph Salowey <joe@salowey.net>, shuque@gmail.com
|
TLS M. Shore
Internet-Draft Fastly
Intended status: Standards Track R. Barnes
Expires: December 3, 2017 Mozilla
S. Huque
Salesforce
W. Toorop
NLNet Labs
June 1, 2017
A DANE Record and DNSSEC Authentication Chain Extension for TLS
draft-ietf-tls-dnssec-chain-extension-04
Abstract
This draft describes a new TLS extension for transport of a DNS
record set serialized with the DNSSEC signatures needed to
authenticate that record set. The intent of this proposal is to
allow TLS clients to perform DANE authentication of a TLS server
without needing to perform additional DNS record lookups. It will
typically not be used for general DNSSEC validation of TLS endpoint
names.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 3, 2017.
Copyright Notice
Copyright (c) 2017 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
Shore, et al. Expires December 3, 2017 [Page 1]
Internet-Draft TLS DNSSEC Chain Extension June 2017
(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 Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DNSSEC Authentication Chain Extension . . . . . . . . . . . . 4
3.1. Protocol, TLS 1.2 . . . . . . . . . . . . . . . . . . . . 4
3.2. Protocol, TLS 1.3 . . . . . . . . . . . . . . . . . . . . 4
3.3. Raw Public Keys . . . . . . . . . . . . . . . . . . . . . 4
3.4. DNSSEC Authentication Chain Data . . . . . . . . . . . . 5
4. Construction of Serialized Authentication Chains . . . . . . 7
5. Caching and Regeneration of the Authentication Chain . . . . 8
6. Verification . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Trust Anchor Maintenance . . . . . . . . . . . . . . . . . . 9
8. Mandating use of this extension . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
12.1. Normative References . . . . . . . . . . . . . . . . . . 10
12.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Updates from -01 and -02 . . . . . . . . . . . . . . 13
Appendix B. Updates from -01 . . . . . . . . . . . . . . . . . . 13
Appendix C. Updates from -00 . . . . . . . . . . . . . . . . . . 13
Appendix D. Test vectors . . . . . . . . . . . . . . . . . . . . 13
D.1. _443._tcp.www.example.com . . . . . . . . . . . . . . . . 15
D.2. _25._tcp.example.com wildcard . . . . . . . . . . . . . . 17
D.3. _443._tcp.www.example.org CNAME . . . . . . . . . . . . . 19
D.4. _443._tcp.www.example.net DNAME . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text