Internet DRAFT - draft-arends-dnsext-dlvptr
draft-arends-dnsext-dlvptr
DNS Extenstions Working Group R. Arends
Internet-Draft Nominet
Intended status: Experimental J. Schlyter
Expires: November 10, 2007 Kirei AB
May 9, 2007
The DNSSEC Lookaside Validation Pointer (DLVPTR) Resource Record
draft-arends-dnsext-dlvptr-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 10, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines the DNSSEC Lookaside Validation Pointer
(DLVPTR) Resource Record (RR), for publishing pointers to DNSSEC
Lookaside Validation (DLV) records.
Arends & Schlyter Expires November 10, 2007 [Page 1]
Internet-Draft DLV Pointer RR May 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. DLVPTR Processing . . . . . . . . . . . . . . . . . . . . . . . 3
3. The DLVPTR Resource Record . . . . . . . . . . . . . . . . . . 3
3.1. The DLVPTR RDATA Format . . . . . . . . . . . . . . . . . . 3
3.2. Presentation Format of the DLVPTR RR . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
Intellectual Property and Copyright Statements . . . . . . . . . . 6
Arends & Schlyter Expires November 10, 2007 [Page 2]
Internet-Draft DLV Pointer RR May 2007
1. Introduction
DNSSEC Lookaside Validation (DLV) [4] [2][5] is a method to publish
Trust Anchors (TAs) for islands of security [3] outside the
delegation chain. This, in turn, has the potential for efficient TA
management on the validator, as the validator can configure the TA
for the DLV repository, instead of TAs for each island of security.
Due to the design of DLV it is not efficient to have more than a few
TAs for DLV repositories. DLV requires the validator to send
additional requests to each DLV repository for each response, for
which there is no configured TA.
This memo introduces a change to the design of DLV. An island of
security can publish a pointer (DLVPTR) to the DLV repository of
choice. When the validator has a configured TA for this DLV,
additional requests will be send to just this DLV.
This change allows configuration of multiple DLV TAs in a validator
without significantly degrading response times.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1].
2. DLVPTR Processing
A Security Aware Resolver sends requests with the DNSSEC-OK bit set,
regardless of any configured TA. It expects the zone at a configured
TA to be secured, and thus responses to contain DNSSEC records.
When a Security Aware Resolver has no TAs configured for a requested
name, and has one or more DLV-TAs configured, and receives a response
for that name containing DNSSEC records, it sends a request for a
DLVPTR to the highest point in the delegation chain that contained
DNSSEC records.
DLV-ANCHOR && DLVPTR && DLV == record
DLV-ANCHOR && (!DLV) == remove
3. The DLVPTR Resource Record
3.1. The DLVPTR RDATA Format
The DLVPTR (type=TBD) record contains a domain name.
Arends & Schlyter Expires November 10, 2007 [Page 3]
Internet-Draft DLV Pointer RR May 2007
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
/ DLVPTRDNAME /
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
A DLVPTR record causes no additional section processing. DLVPTR RRs
are used in domains to point to some other location in the domain
space.
3.2. Presentation Format of the DLVPTR RR
The RDATA of the presentation format of the DLVPTR resource record
consists of one string (the domain name of the target DLV [2]), e.g.:
example.net. DLVPTR xyzzy.dlv.arpa.
4. Security Considerations
5. IANA Considerations
IANA needs to allocate a RR type code for DLVPTR from the standard RR
type space (type 50 requested).
6. References
6.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Andrews, M. and S. Weiler, "The DNSSEC Lookaside Validation
(DLV) DNS Resource Record", RFC 4431, February 2006.
6.2. Informative References
[3] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,
"DNS Security Introduction and Requirements", RFC 4033,
March 2005.
[4] Vixie, P. and M. Andrews, "DNSSEC Lookaside Validation (DLV)",
ISC-TN 2006-1, April 2006.
[5] Weiler, S., "DNSSEC Lookaside Validation (DLV)",
draft-weiler-dnssec-dlv-02 (work in progress), March 2007.
Arends & Schlyter Expires November 10, 2007 [Page 4]
Internet-Draft DLV Pointer RR May 2007
Appendix A. Acknowledgements
The author gratefully acknowledges, in no particular order, the
contributions of the following persons:
Geoffrey Sisson
Authors' Addresses
Roy Arends
Nominet
Sandford Gate
Sandy Lane West
Oxford OX4 6LB
United Kingdom
Phone: +44 1865 332211
Email: roy@nominet.org.uk
Jakob Schlyter
Kirei AB
P.O. Box 53204
Goteborg SE-400 16
Sweden
Phone: +46 31 787 80 07
Email: jakob@kirei.se
Arends & Schlyter Expires November 10, 2007 [Page 5]
Internet-Draft DLV Pointer RR May 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Arends & Schlyter Expires November 10, 2007 [Page 6]
