< draft-wessels-dns-zone-digest-05.txt   draft-wessels-dns-zone-digest-06.txt >
Internet Engineering Task Force D. Wessels Internet Engineering Task Force D. Wessels
Internet-Draft P. Barber Internet-Draft P. Barber
Intended status: Experimental M. Weinberg Intended status: Experimental M. Weinberg
Expires: May 11, 2019 Verisign Expires: August 17, 2019 Verisign
W. Kumari W. Kumari
Google Google
W. Hardaker W. Hardaker
USC/ISI USC/ISI
November 7, 2018 February 13, 2019
Message Digest for DNS Zones Message Digest for DNS Zones
draft-wessels-dns-zone-digest-05 draft-wessels-dns-zone-digest-06
Abstract Abstract
This document describes an experimental protocol and new DNS Resource This document describes an experimental protocol and new DNS Resource
Record that can be used to provide a message digest over DNS zone Record that can be used to provide a message digest over DNS zone
data. The ZONEMD Resource Record conveys the message digest data in data. The ZONEMD Resource Record conveys the message digest data in
the zone itself. When a zone publisher includes an ZONEMD record, the zone itself. When a zone publisher includes an ZONEMD record,
recipients can verify the zone contents for accuracy and recipients can verify the zone contents for accuracy and
completeness. This provides assurance that received zone data completeness. This provides assurance that received zone data
matches published data, regardless of how the zone data has been matches published data, regardless of how the zone data has been
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 11, 2019. This Internet-Draft will expire on August 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 7, line 43 skipping to change at page 7, line 43
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. The ZONEMD Resource Record 2. The ZONEMD Resource Record
This section describes the ZONEMD Resource Record, including its This section describes the ZONEMD Resource Record, including its
fields, wire format, and presentation format. The Type value for the fields, wire format, and presentation format. The Type value for the
ZONEMD RR is TBD. The ZONEMD RR is class independent. The RDATA of ZONEMD RR is 63. The ZONEMD RR is class independent. The RDATA of
the resource record consists of four fields: Serial, Digest Type, the resource record consists of four fields: Serial, Digest Type,
Reserved, and Digest. Reserved, and Digest.
FOR DISCUSSION: This document is currently written as though a zone FOR DISCUSSION: This document is currently written as though a zone
MUST NOT contain more than one ZONEMD RR. Having exactly one ZONEMD MUST NOT contain more than one ZONEMD RR. Having exactly one ZONEMD
record per zone simplifies this protocol and eliminates confusion record per zone simplifies this protocol and eliminates confusion
around downgrade attacks, at the expense of algorithm agility. around downgrade attacks, at the expense of algorithm agility.
2.1. ZONEMD RDATA Wire Format 2.1. ZONEMD RDATA Wire Format
skipping to change at page 13, line 37 skipping to change at page 13, line 37
The duration of the experiment is expected to be no less than two The duration of the experiment is expected to be no less than two
years from the publication of this document. If the experiment is years from the publication of this document. If the experiment is
successful, it is expected that the findings of the experiment will successful, it is expected that the findings of the experiment will
result in an updated document for Standards Track approval. result in an updated document for Standards Track approval.
6. IANA Considerations 6. IANA Considerations
6.1. ZONEMD RRtype 6.1. ZONEMD RRtype
This document defines a new DNS RR type, ZONEMD, whose value TBD has This document defines a new DNS RR type, ZONEMD, whose value 63 has
been allocated by IANA from the "Resource Record (RR) TYPEs" been allocated by IANA from the "Resource Record (RR) TYPEs"
subregistry of the "Domain Name System (DNS) Parameters" registry: subregistry of the "Domain Name System (DNS) Parameters" registry:
Type: ZONEMD Type: ZONEMD
Value: TBD Value: 63
Meaning: Message Digest Over Zone Data Meaning: Message Digest Over Zone Data
Reference: This document Reference: This document
6.2. ZONEMD Digest Type 6.2. ZONEMD Digest Type
This document asks IANA to create a new "ZONEMD Digest Types" This document asks IANA to create a new "ZONEMD Digest Types"
registry with initial contents as follows: registry with initial contents as follows:
skipping to change at page 18, line 21 skipping to change at page 18, line 21
received digest. received digest.
o Explained why Reserved field is 8-bits. o Explained why Reserved field is 8-bits.
o IANA Considerations section now more specific. o IANA Considerations section now more specific.
o Added complex zone to examples. o Added complex zone to examples.
o o
From -05 to -06:
o RR type code 63 was assigned to ZONEMD by IANA.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987,
<https://www.rfc-editor.org/info/rfc1034>. <https://www.rfc-editor.org/info/rfc1034>.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
 End of changes. 9 change blocks. 
8 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/