RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 5910, "Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)", May 2010

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 2597
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: NOGUCHI Shoji
Date Reported: 2010-11-01
Verifier Name: Alexey Melnikov
Date Verified: 2010-11-04

Section 5.2.5 says:

   Example <update> Command,
                 Removing all DS and Key Data Using <secDNS:rem>
                 with <secDNS:all>:

   C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   C:  <command>
   C:    <update>
   C:      <domain:update
   C:       xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
   C:        <domain:name>example.com</domain:name>
   C:      </domain:update>
   C:    </update>
   C:    <extension>
   C:      <secDNS:update urgent="true"
|  C:       xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.0">
   C:        <secDNS:rem>
   C:          <secDNS:all>true</secDNS:all>
   C:        </secDNS:rem>
   C:      </secDNS:update>
   C:    </extension>
   C:    <clTRID>ABC-12345</clTRID>
   C:  </command>
   C:</epp>

It should say:

   Example <update> Command,
                 Removing all DS and Key Data Using <secDNS:rem>
                 with <secDNS:all>:

   C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   C:  <command>
   C:    <update>
   C:      <domain:update
   C:       xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
   C:        <domain:name>example.com</domain:name>
   C:      </domain:update>
   C:    </update>
   C:    <extension>
   C:      <secDNS:update urgent="true"
|  C:       xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1">
   C:        <secDNS:rem>
   C:          <secDNS:all>true</secDNS:all>
   C:        </secDNS:rem>
   C:      </secDNS:update>
   C:    </extension>
   C:    <clTRID>ABC-12345</clTRID>
   C:  </command>
   C:</epp>

Notes:

secDNS-1.0 -> secDNS-1.1

Status: Reported (1)

RFC 5910, "Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)", May 2010

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 6863
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Patrick Mevzek
Date Reported: 2022-02-25

Section 4.3, 5.1.2, 5.2.1 says:


   <secDNS:dsData>
     <secDNS:keyTag>12345</secDNS:keyTag>
     <secDNS:alg>3</secDNS:alg>
     <secDNS:digestType>1</secDNS:digestType>
     <secDNS:digest>49FD46E6C4B45C55D4AC</secDNS:digest>
     <secDNS:keyData>
       <secDNS:flags>257</secDNS:flags>
       <secDNS:protocol>3</secDNS:protocol>
       <secDNS:alg>1</secDNS:alg>
       <secDNS:pubKey>AQPJ////4Q==</secDNS:pubKey>
     </secDNS:keyData>
    </secDNS:dsData>

It should say:


   <secDNS:dsData>
     <secDNS:keyTag>12345</secDNS:keyTag>
     <secDNS:alg>3</secDNS:alg>
     <secDNS:digestType>1</secDNS:digestType>
     <secDNS:digest>49FD46E6C4B45C55D4AC</secDNS:digest>
     <secDNS:keyData>
       <secDNS:flags>257</secDNS:flags>
       <secDNS:protocol>3</secDNS:protocol>
       <secDNS:alg>3</secDNS:alg>
       <secDNS:pubKey>AQPJ////4Q==</secDNS:pubKey>
     </secDNS:keyData>
    </secDNS:dsData>

Notes:

The DS alg value must match the underlying (inside) DNSKEY alg value.

From RFC 5910 respectively:
- A <secDNS:alg> element that contains an algorithm value as
described in Section 5.1.2 of RFC 4034 [RFC4034].
and
- A <secDNS:alg> element that contains an algorithm number field
value as described in Section 2.1.3 of RFC 4034 [RFC4034].

Section 5.1.2 of RFC 4034 says:
The algorithm number used by the DS RR is identical to the algorithm
number used by RRSIG and DNSKEY RRs.


The three occurrences are just examples so do not change the meaning of the specification, yet incorrect examples can create confusion.

Report New Errata