draft-ietf-dnssec-ddi-01.txt   draft-ietf-dnssec-ddi-02.txt 
INTERNET-DRAFT Donald E. Eastlake 3rd INTERNET-DRAFT Donald E. Eastlake 3rd
CyberCash, Inc. CyberCash, Inc.
Expires 27 February 1997 28 August 1996
Detached Domain Name System Information Detached Domain Name System Information
-------- ------ ---- ------ ----------- -------- ------ ---- ------ -----------
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Status of This Document Status of This Document
This draft, file name draft-ietf-dnssec-ddi-01.txt, is intended to be This draft, file name draft-ietf-dnssec-ddi-02.txt, is intended to be
become a Proposed Standard RFC. Distribution of this document is become a Proposed Standard RFC. Distribution of this document is
unlimited. Comments should be sent to the DNS Security Working Group unlimited. Comments should be sent to the DNS Security Working Group
mailing list <dns-security@tis.com> or to the author. mailing list <dns-security@tis.com> or to the author.
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 2, line 24 skipping to change at page 2, line 24
Status of This Document....................................1 Status of This Document....................................1
Abstract...................................................2 Abstract...................................................2
Table of Contents..........................................2 Table of Contents..........................................2
1. Introduction............................................3 1. Introduction............................................3
2. General Format..........................................4 2. General Format..........................................4
2.1 Binary Format..........................................4 2.1 Binary Format..........................................4
2.2. Text Format...........................................5 2.2. Text Format...........................................6
3. Usage Example...........................................7 3. Usage Example...........................................7
4. Security Considerations.................................7 4. Security Considerations.................................7
References.................................................8 References.................................................8
Author's Address...........................................8 Author's Address...........................................8
Expiration and File Name...................................8 Expiration and File Name...................................8
1. Introduction 1. Introduction
The Domain Name System (DNS) is a replicated hierarchical distributed The Domain Name System (DNS) is a replicated hierarchical distributed
database system [RFC 1034, 1035] that can provide highly available database system [RFC 1034, 1035] that can provide highly available
service. It provides the operational basis for Internet host name to service. It provides the operational basis for Internet host name to
address translation, automatic SMTP mail routing, and other basic address translation, automatic SMTP mail routing, and other basic
Internet functions. The DNS has recently been extended as described Internet functions. The DNS has recently been extended as described
in draft-ietf-dnssec-secext-10.txt [approved as a Proposed Standard in RFC 2065 to permit the general storage of public cryptographic
but not yet issued as an RFC] to permit the general storage of public keys in the DNS and to enable the authentication of information
cryptographic keys in the DNS and to enable the authentication of retrieved from the DNS though digital signatures.
information retrieved from the DNS though digital signatures.
The DNS was not originally designed for storage of information The DNS was not originally designed for storage of information
outside of the active zones and authoritative master files that are outside of the active zones and authoritative master files that are
part of the connected DNS. However there may be cases where this is part of the connected DNS. However there may be cases where this is
useful, particularly in connection with security information. useful, particularly in connection with security information.
2. General Format 2. General Format
The formats used for detached Domain Name System (DNS) information The formats used for detached Domain Name System (DNS) information
are similar to those used for connected DNS information. The primary are similar to those used for connected DNS information. The primary
skipping to change at page 5, line 36 skipping to change at page 5, line 36
was obtained from the connected DNS system. It is an unsigned was obtained from the connected DNS system. It is an unsigned
number of seconds since the start of 1 January 1970, GMT, ignoring number of seconds since the start of 1 January 1970, GMT, ignoring
leap seconds, in network (big-endian) order. Note that this time leap seconds, in network (big-endian) order. Note that this time
can not be before the initial proposal of this standard. can not be before the initial proposal of this standard.
Therefore, the initial byte of an actual retrieval time, Therefore, the initial byte of an actual retrieval time,
considered as an unsigned quantity, will be larger than 80 hex. considered as an unsigned quantity, will be larger than 80 hex.
The end of detached DNS information is indicated by a "retrieval The end of detached DNS information is indicated by a "retrieval
time" field initial byte equal to 80 hex. Use of a "retrieval time" field initial byte equal to 80 hex. Use of a "retrieval
time" field with a leading zero bit in binary detached DNS time" field with a leading zero bit in binary detached DNS
information is reserved for future use. It may indicate a information is reserved for future use. It may indicate a
different format. different format. Retrieval times will not generally be 32 bit
aligned with respect to each other due to the variable length
nature of RRs.
RR count - an unsigned integer number (with bytes in network order) RR count - an unsigned integer number (with bytes in network order)
of resource records with the preceding retrieval time. of following resource records retrieved at the preceding retrieval
time.
Resource Records - the actual data which is in the same format as if Resource Records - the actual data which is in the same format as if
it were being transmitted in a DNS response. In particular, name it were being transmitted in a DNS response. In particular, name
compression via pointers is permitted with the origin at the compression via pointers is permitted with the origin at the
beginning of the particular detached information data section, beginning of the particular detached information data section,
just after the RR count. just after the RR count.
2.2. Text Format 2.2. Text Format
The standard text format for detached DNS information is as The standard text format for detached DNS information is as
skipping to change at page 7, line 13 skipping to change at page 7, line 13
through the detached information. through the detached information.
3. Usage Example 3. Usage Example
A document might be authenticated by a key retrieved from the DNS in A document might be authenticated by a key retrieved from the DNS in
a KEY resource record (RR). To later prove the authenticity of this a KEY resource record (RR). To later prove the authenticity of this
document, it would be desirable to preserve the KEY RR for that document, it would be desirable to preserve the KEY RR for that
public key, the SIG RR signing that KEY RR, the KEY RR for the key public key, the SIG RR signing that KEY RR, the KEY RR for the key
used to authenticate that SIG, and so on through SIG and KEY RRs used to authenticate that SIG, and so on through SIG and KEY RRs
until a well known trusted key is reached, perhaps the key for the until a well known trusted key is reached, perhaps the key for the
DNS root. (In some cases these KEY RRs will actually be sets of KEY DNS root or some third party authentication service. (In some cases
RRs with the same owner and class because SIGs actually sign such these KEY RRs will actually be sets of KEY RRs with the same owner
record sets.) and class because SIGs actually sign such record sets.)
This information could be preserved as a set of detached DNS This information could be preserved as a set of detached DNS
information blocks. information blocks.
4. Security Considerations 4. Security Considerations
The entirety of this document concerns a means to represent detached The entirety of this document concerns a means to represent detached
DNS information. Security considerations are not covered in this DNS information. Security considerations are not covered in this
draft although such detached information may be security relevant draft. Such detached information may be security relevant resource
resource records as described in draft-ietf-dnssec-secext-10.txt. records as described in RFC 2065.
References References
[RFC 1034] - Domain Names - Concepts and Facilities, P. Mockapetris, [RFC 1034] - Domain Names - Concepts and Facilities, P. Mockapetris,
November 1987 November 1987.
[RFC 1035] - Domain Names - Implementation and Specifications, P. [RFC 1035] - Domain Names - Implementation and Specifications, P.
Mockapetris, November 1987. Mockapetris, November 1987.
draft-ietf-dnssec-secext-10.txt - Domain Name System Security [RFC 2065] - Domain Name System Security Extensions, D. Eastlake, C.
Extensions, D. Eastlake, C. Kaufman. Kaufman, January 1997.
Author's Address Author's Address
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
CyberCash, Inc. CyberCash, Inc.
318 Acton Street 318 Acton Street
Carlisle, MA 01741 USA Carlisle, MA 01741 USA
Telephone: +1 508 287 4877 Telephone: +1 508 287 4877
+1 508 371 7148(fax) +1 508 371 7148(fax)
+1 703 620 4200(main office, Reston, Virginia) +1 703 620 4200(main office, Reston, Virginia)
EMail: dee@cybercash.com EMail: dee@cybercash.com
Expiration and File Name Expiration and File Name
This draft expires 27 February 1997. This draft expires September 1997.
Its file name is draft-ietf-dnssec-ddi-01.txt. Its file name is draft-ietf-dnssec-ddi-02.txt.
 End of changes. 12 change blocks. 
18 lines changed or deleted 19 lines changed or added

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