draft-ietf-curdle-dnskey-eddsa-01.txt   draft-ietf-curdle-dnskey-eddsa-02.txt 
Internet Engineering Task Force O. Sury Internet Engineering Task Force O. Sury
Internet-Draft CZ.NIC Internet-Draft CZ.NIC
Intended status: Standards Track R. Edmonds Intended status: Standards Track R. Edmonds
Expires: April 13, 2017 Fastly Expires: May 19, 2017 Fastly
October 10, 2016 November 15, 2016
EdDSA for DNSSEC EdDSA for DNSSEC
draft-ietf-curdle-dnskey-eddsa-01 draft-ietf-curdle-dnskey-eddsa-02
Abstract Abstract
This document describes how to specify EdDSA keys and signatures in This document describes how to specify EdDSA keys and signatures in
DNS Security (DNSSEC). It uses the Edwards-curve Digital Security DNS Security (DNSSEC). It uses the Edwards-curve Digital Security
Algorithm (EdDSA) with the choice of two curves, Ed25519 and Ed448. Algorithm (EdDSA) with the choice of two curves, Ed25519 and Ed448.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 April 13, 2017. This Internet-Draft will expire on May 19, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. DNSKEY Resource Records . . . . . . . . . . . . . . . . . . . 2 3. DNSKEY Resource Records . . . . . . . . . . . . . . . . . . . 2
4. RRSIG Resource Records . . . . . . . . . . . . . . . . . . . 3 4. RRSIG Resource Records . . . . . . . . . . . . . . . . . . . 3
5. Algorithm Number for DS, DNSKEY and RRSIG Resource Records . 3 5. Algorithm Number for DS, DNSKEY and RRSIG Resource Records . 3
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6.1. Ed25519 Examples . . . . . . . . . . . . . . . . . . . . 3 6.1. Ed25519 Examples . . . . . . . . . . . . . . . . . . . . 3
6.2. Ed448 Example . . . . . . . . . . . . . . . . . . . . . . 4 6.2. Ed448 Examples . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
10. Security Considerations . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
DNSSEC, which is broadly defined in [RFC4033], [RFC4034], and DNSSEC, which is broadly defined in [RFC4033], [RFC4034], and
[RFC4035], uses cryptographic keys and digital signatures to provide [RFC4035], uses cryptographic keys and digital signatures to provide
authentication of DNS data. Currently, the most popular signature authentication of DNS data. Currently, the most popular signature
algorithm in use is RSA. GOST ([RFC5933]) and NIST-specified algorithm in use is RSA. GOST ([RFC5933]) and NIST-specified
elliptic curve cryptography ([RFC6605]) are also standardized. elliptic curve cryptography ([RFC6605]) are also standardized.
[I-D.irtf-cfrg-eddsa] describes the elliptic curve signature system [I-D.irtf-cfrg-eddsa] describes the elliptic curve signature system
EdDSA and recommends two curves, Ed25519 and Ed448. EdDSA and recommends two curves, Ed25519 and Ed448.
This document defines the use of DNSSEC's DS, DNSKEY, and RRSIG This document defines the use of DNSSEC's DS, DNSKEY, and RRSIG
resource records (RRs) with a new signing algorithm, Edwards-curve resource records (RRs) with a new signing algorithm, Edwards-curve
Digital Signature Algorithm (EdDSA) using a choice of two curves, Digital Signature Algorithm (EdDSA) using a choice of two instances:
Ed25519 and Ed448. Ed25519 and Ed448.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. DNSKEY Resource Records 3. DNSKEY Resource Records
An Ed25519 public key consists of a 32-octet value, which is encoded An Ed25519 public key consists of a 32-octet value, which is encoded
into the Public Key field of a DNSKEY resource record as a simple bit into the Public Key field of a DNSKEY resource record as a simple bit
string. The generation of a public key is defined in Chapter 5.1.5 string. The generation of a public key is defined in Section 5.1.5
in [I-D.irtf-cfrg-eddsa]. in [I-D.irtf-cfrg-eddsa].
An Ed448 public key consists of a 57-octet value, which is encoded An Ed448 public key consists of a 57-octet value, which is encoded
into the Public Key field of a DNSKEY resource record as a simple bit into the Public Key field of a DNSKEY resource record as a simple bit
string. The generation of a public key is defined in Chapter 5.2.5 string. The generation of a public key is defined in Section 5.2.5
in [I-D.irtf-cfrg-eddsa]. in [I-D.irtf-cfrg-eddsa].
4. RRSIG Resource Records 4. RRSIG Resource Records
In Chapter 10.3 in [I-D.irtf-cfrg-eddsa], the use of a context label
is described. EdDSA signatures in this scheme use the 12-octet
context label 'DNSSECRRSIG\0' (where \0 represents a zero-valued
octet).
An Ed25519 signature consists of a 64-octet value, which is encoded An Ed25519 signature consists of a 64-octet value, which is encoded
into the Signature field of an RRSIG resource record as a simple bit into the Signature field of an RRSIG resource record as a simple bit
string. The Ed25519 signature algorithm is described in Chapter string. The Ed25519 signature algorithm is described in
5.1.6 in [I-D.irtf-cfrg-eddsa]. Section 5.1.6 and verification of the Ed25519 signature is described
in Section5.1.7 in [I-D.irtf-cfrg-eddsa].
An Ed448 signature consists of a 114-octet value, which is encoded An Ed448 signature consists of a 114-octet value, which is encoded
into the Signature field of an RRSIG resource record as a simple bit into the Signature field of an RRSIG resource record as a simple bit
string. The Ed448 signature algorithm is described in Chapter 5.2.6 string. The Ed448 signature algorithm is described in Section 5.2.6
and verification of the Ed448 signature is described in Chapter 5.2.7 and verification of the Ed448 signature is described in Section 5.2.7
in [I-D.irtf-cfrg-eddsa]. in [I-D.irtf-cfrg-eddsa].
5. Algorithm Number for DS, DNSKEY and RRSIG Resource Records 5. Algorithm Number for DS, DNSKEY and RRSIG Resource Records
The algorithm number associated with the use of Ed25519 in DS, DNSKEY The algorithm number associated with the use of Ed25519 in DS, DNSKEY
and RRSIG resource records is TBD. The algorithm number associated and RRSIG resource records is TBD1. The algorithm number associated
with the use of Ed448 in DS, DNSKEY and RRSIG resource records is with the use of Ed448 in DS, DNSKEY and RRSIG resource records is
TBD. This registration is fully defined in the IANA Considerations TBD2. This registration is fully defined in the IANA Considerations
section. section.
6. Examples 6. Examples
6.1. Ed25519 Examples 6.1. Ed25519 Examples
This section needs an update after the algorithm for Ed25519 is This section needs an update after the algorithm number for Ed25519
assigned. is assigned.
Private-key-format: v1.2 Private-key-format: v1.2
Algorithm: TBD (ED25519) Algorithm: TBD1 (ED25519)
PrivateKey: ODIyNjAzODQ2MjgwODAxMjI2NDUxOTAyMDQxNDIyNjI= PrivateKey: ODIyNjAzODQ2MjgwODAxMjI2NDUxOTAyMDQxNDIyNjI=
# corresponding to 82260384628080122645190204142262 INT
example.com. 3600 IN DNSKEY 257 3 TBD ( example.com. 3600 IN DNSKEY 257 3 TBD1 (
l02Woi0iS8Aa25FQkUd9RMzZHJpBoRQwAQEX1SxZJA4= ) l02Woi0iS8Aa25FQkUd9RMzZHJpBoRQwAQEX1SxZJA4= )
example.com. 3600 IN DS 3613 TBD 2 ( example.com. 3600 IN DS 3613 TBD1 2 (
3aa5ab37efce57f737fc1627013fee07bdf241bd10f3 3aa5ab37efce57f737fc1627013fee07bdf241bd10f3b1964ab55c78e79
b1964ab55c78e79a304b ) a304b )
www.example.com. 3600 IN A 192.0.2.1 example.com. 3600 IN MX 10 mail.example.com.
www.example.com. 3600 IN RRSIG A TBD 3 3600 (
20150820000000 20150730000000 3613 example.com.
cvTRVrU7dwnemQuBq9/E4tlIiRpvWcEmYdzqs6SCQxw6
qmczBBQGldssMx1TCJnwsEs9ZuA2phPzuJNoon9BCA== )
Private-key-format: v1.2 example.com. 3600 IN RRSIG MX 3 3600 (
Algorithm: TBD (ED25519) 1440021600 1438207200 3613 example.com. (
PrivateKey: DSSF3o0s0f+ElWzj9E/Osxw8hLpk55chkmx0LYN5WiY= Edk+IB9KNNWg0HAjm7FazXyrd5m3Rk8zNZbvNpAcM+eysqcUOMIjWoevFkj
H5GaMWeG96GUVZu6ECKOQmemHDg== )
example.com. 3600 IN DNSKEY 257 3 TBD ( This section needs an update after the algorithm number for Ed25519
zPnZ/QwEe7S8C5SPz2OfS5RR40ATk2/rYnE9xHIEijs= ) is assigned.
example.com. 3600 IN DS 55648 TBD 2 ( Private-key-format: v1.2
96401675bc7ecdd541ec0f70d69238c7b95d3bd4de1e Algorithm: TBD1 (ED25519)
231a068ceb214d02a4ed ) PrivateKey: DSSF3o0s0f+ElWzj9E/Osxw8hLpk55chkmx0LYN5WiY=
www.example.com. 3600 IN A 192.0.2.1 example.com. 3600 IN DNSKEY 257 3 TBD1 (
www.example.com. 3600 IN RRSIG A TBD 3 3600 ( zPnZ/QwEe7S8C5SPz2OfS5RR40ATk2/rYnE9xHIEijs= )
20150820000000 20150730000000 35452 example.com.
yuGb9rCNIuhDaRJbuhYHj89Y/3Pi8KWUm7lOt00ivVRGvgulmVX8DgpE
AFyMP2MKXJrqYJr+ViiCIDwcOIbPAQ==)
6.2. Ed448 Example example.com. 3600 IN DS 35217 TBD1 2 (
This section needs an update after the algorithm for Ed448 is 401781b934e392de492ec77ae2e15d70f6575a1c0bc59c5275c04ebe80c
6614c )
example.com. 3600 IN MX 10 mail.example.com.
example.com. 3600 IN RRSIG MX 3 3600 (
1440021600 1438207200 35217 example.com. (
5LL2obmzdqjWI+Xto5eP5adXt/T5tMhasWvwcyW4L3SzfcRawOle9bodhC+
oip9ayUGjY9T/rL4rN3bOuESGDA== )
6.2. Ed448 Examples
This section needs an update after the algorithm number for Ed448 is
assigned. assigned.
Private-key-format: v1.2 Private-key-format: v1.2
Algorithm: TBD (ED448) Algorithm: TBD2 (ED448)
PrivateKey: TBD PrivateKey: xZ+5Cgm463xugtkY5B0Jx6erFTXp13rYegst0qRtNsOYnaVpMx0Z/c5EiA9x
8wWbDDct/U3FhYWA
example.com. 3600 IN DNSKEY 257 3 TBD ( example.com. 3600 IN DNSKEY 257 3 TBD2 (
TBD ) 3kgROaDjrh0H2iuixWBrc8g2EpBBLCdGzHmn+G2MpTPhpj/OiBVHHSfPodx
1FYYUcJKm1MDpJtIA )
example.com. 3600 IN DS 3613 TBD 2 ( example.com. 3600 IN DS 9713 TBD2 2 (
TBD ) 6ccf18d5bc5d7fc2fceb1d59d17321402f2aa8d368048db93dd811f5cb2
b19c7 )
www.example.com. 3600 IN A 192.0.2.1 example.com. 3600 IN MX 10 mail.example.com.
www.example.com. 3600 IN RRSIG A TBD 3 3600 (
20150820000000 20150730000000 3613 example.com.
TBD )
Private-key-format: v1.2 example.com. 3600 IN RRSIG MX 3 3600 (
Algorithm: TBD (ED448) 1440021600 1438207200 9713 example.com. (
PrivateKey: TBD Nmc0rgGKpr3GKYXcB1JmqqS4NYwhmechvJTqVzt3jR+Qy/lSLFoIk1L+9e3
9GPL+5tVzDPN3f9kAwiu8KCuPPjtl227ayaCZtRKZuJax7n9NuYlZJIusX0
SOIOKBGzG+yWYtz1/jjbzl5GGkWvREUCUA )
example.com. 3600 IN DNSKEY 257 3 TBD ( This section needs an update after the algorithm number for Ed448 is
TBD ) assigned.
example.com. 3600 IN DS 55648 TBD 2 ( Private-key-format: v1.2
TBD ) Algorithm: TBD2 (ED448)
PrivateKey: WEykD3ht3MHkU8iH4uVOLz8JLwtRBSqiBoM6fF72+Mrp/u5gjxuB1DV6NnPO
2BlZdz4hdSTkOdOA
www.example.com. 3600 IN A 192.0.2.1 example.com. 3600 IN DNSKEY 257 3 TBD2 (
www.example.com. 3600 IN RRSIG A TBD 3 3600 ( kkreGWoccSDmUBGAe7+zsbG6ZAFQp+syPmYUurBRQc3tDjeMCJcVMRDmgcN
20150820000000 20150730000000 35452 example.com. Lp5HlHAMy12VoISsA )
TBD )
example.com. 3600 IN DS 38353 TBD2 2 (
645ff078b3568f5852b70cb60e8e696cc77b75bfaaffc118cf79cbda1ba
28af4 )
example.com. 3600 IN MX 10 mail.example.com.
example.com. 3600 IN RRSIG MX 3 3600 (
1440021600 1438207200 38353 example.com. (
+JjANio/LIzp7osmMYE5XD3H/YES8kXs5Vb9H8MjPS8OAGZMD37+LsCIcjg
5ivt0d4Om/UaqETEAsJjaYe56CEQP5lhRWuD2ivBqE0zfwJTyp4WqvpULbp
vaukswvv/WNEFxzEYQEIm9+xDlXj4pMAMA )
7. Acknowledgements 7. Acknowledgements
Some of the material in this document is copied liberally from Some of the material in this document is copied liberally from
[RFC6605]. [RFC6605].
The authors of this document wish to thank Jan Vcelak, Pieter Lexis The authors of this document wish to thank Jan Vcelak, Pieter Lexis,
and Kees Monshouwer for a review of this document. Kees Monshouwer, Simon Josefsson, Paul Hoffman and others for a
review of this document.
8. IANA Considerations 8. IANA Considerations
This document updates the IANA registry "Domain Name System Security This document updates the IANA registry "Domain Name System Security
(DNSSEC) Algorithm Numbers". The following entry has been added to (DNSSEC) Algorithm Numbers". The following entry has been added to
the registry: the registry:
+--------------+---------------+---------------+ +--------------+---------------+---------------+
| Number | TBD | TBD | | Number | TBD1 | TBD2 |
| Description | Ed25519 | Ed448 | | Description | Ed25519 | Ed448 |
| Mnemonic | ED25519 | Ed448 | | Mnemonic | ED25519 | ED448 |
| Zone Signing | Y | Y | | Zone Signing | Y | Y |
| Trans. Sec. | * | * | | Trans. Sec. | * | * |
| Reference | This document | This document | | Reference | This document | This document |
+--------------+---------------+---------------+ +--------------+---------------+---------------+
* There has been no determination of standardization of the use of * There has been no determination of standardization of the use of
this algorithm with Transaction Security. this algorithm with Transaction Security.
9. Implementation Status 9. Security Considerations
(Note to the RFC Editor: please remove this entire section as well as
the reference to RFC 6982 before publication.)
This section records the status of known implementations of the Ed25519 and Ed448 offers improved security properties and
protocol defined by this specification at the time of posting of this implementation characteristics compared to RSA and ECDSA algorithms,
Internet-Draft, and is based on a proposal described in [RFC6982]. and the introduction of these algorithms are thus expected to improve
The description of implementations in this section is intended to security of DNSSEC.
assist the IETF in its decision processes in progressing drafts to
RFCs. Please note that the listing of any individual implementation
here does not imply endorsement by the IETF. Furthermore, no effort
has been spent to verify the information presented here that was
supplied by IETF contributors. This is not intended as, and must not
be construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may
exist.
According to [RFC6982], "this will allow reviewers and working groups The security considerations of [I-D.irtf-cfrg-eddsa] and [RFC7748]are
to assign due consideration to documents that have the benefit of inherited in the usage of Ed25519 and Ed448 in DNSSEC.
running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as
they see fit".
10. Security Considerations Ed25519 is intended to operate at around the 128-bit security level,
and Ed448 at around the 224-bit security level. A sufficiently large
quantum computer would be able to break both. Reasonable projections
of the abilities of classical computers conclude that Ed25519 is
perfectly safe. Ed448 is provided for those applications with
relaxed performance requirements and where there is a desire to hedge
against analytical attacks on elliptic curves.
The security level of Ed25519 is slightly under the standard 128-bit These assessments could, of course, change in the future if new
level and the security level of Ed448 is slightly under the standard
224-bit level ([RFC7748]). Security considerations listed in
[RFC7748] also apply to the usage of Ed25519 and Ed448 in DNSSEC.
Such an assessment could, of course, change in the future if new
attacks that work better than the ones known today are found. attacks that work better than the ones known today are found.
11. References A private key used for a DNSSEC zone MUST NOT be used for any other
purpose than for that zone. Otherwise cross-protocol or cross-
application attacks are possible.
11.1. Normative References 10. References
10.1. Normative References
[I-D.irtf-cfrg-eddsa] [I-D.irtf-cfrg-eddsa]
Josefsson, S. and I. Liusvaara, "Edwards-curve Digital Josefsson, S. and I. Liusvaara, "Edwards-curve Digital
Signature Algorithm (EdDSA)", draft-irtf-cfrg-eddsa-08 Signature Algorithm (EdDSA)", draft-irtf-cfrg-eddsa-08
(work in progress), August 2016. (work in progress), August 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 7, line 38 skipping to change at page 7, line 42
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005, Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005,
<http://www.rfc-editor.org/info/rfc4035>. <http://www.rfc-editor.org/info/rfc4035>.
[RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves [RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves
for Security", RFC 7748, DOI 10.17487/RFC7748, January for Security", RFC 7748, DOI 10.17487/RFC7748, January
2016, <http://www.rfc-editor.org/info/rfc7748>. 2016, <http://www.rfc-editor.org/info/rfc7748>.
11.2. Informative References 10.2. Informative References
[RFC5933] Dolmatov, V., Ed., Chuprina, A., and I. Ustinov, "Use of [RFC5933] Dolmatov, V., Ed., Chuprina, A., and I. Ustinov, "Use of
GOST Signature Algorithms in DNSKEY and RRSIG Resource GOST Signature Algorithms in DNSKEY and RRSIG Resource
Records for DNSSEC", RFC 5933, DOI 10.17487/RFC5933, July Records for DNSSEC", RFC 5933, DOI 10.17487/RFC5933, July
2010, <http://www.rfc-editor.org/info/rfc5933>. 2010, <http://www.rfc-editor.org/info/rfc5933>.
[RFC6605] Hoffman, P. and W. Wijngaards, "Elliptic Curve Digital [RFC6605] Hoffman, P. and W. Wijngaards, "Elliptic Curve Digital
Signature Algorithm (DSA) for DNSSEC", RFC 6605, Signature Algorithm (DSA) for DNSSEC", RFC 6605,
DOI 10.17487/RFC6605, April 2012, DOI 10.17487/RFC6605, April 2012,
<http://www.rfc-editor.org/info/rfc6605>. <http://www.rfc-editor.org/info/rfc6605>.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982,
DOI 10.17487/RFC6982, July 2013,
<http://www.rfc-editor.org/info/rfc6982>.
Authors' Addresses Authors' Addresses
Ondrej Sury Ondrej Sury
CZ.NIC CZ.NIC
Milesovska 1136/5 Milesovska 1136/5
Praha 130 00 Praha 130 00
CZ CZ
Email: ondrej.sury@nic.cz Email: ondrej.sury@nic.cz
 End of changes. 42 change blocks. 
119 lines changed or deleted 120 lines changed or added

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