RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 7707, "Network Reconnaissance in IPv6 Networks", March 2016

Source of RFC: opsec (ops)

Errata ID: 5175
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Kevin Tyers
Date Reported: 2017-10-30
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2017-10-31

Section 5.1.4. says:

the response would
   contain an RCODE of 0 (no error).  Otherwise, the response would
   contain an RCODE of 4 (NXDOMAIN).

It should say:

the response would
   contain an RCODE of 0 (no error).  Otherwise, the response would
   contain an RCODE of 3 (NXDOMAIN).

Notes:

In RFC1035 section 4.1.1. it states that an RCODE of 3 is 'Name Error' aka NXDOMAIN. RCODE 4 is "Not Implemented". RFC 7707 incorrectly refers to NXDOMAIN as RCODE 4 instead of RCODE 3.

Here is the output of testing this in Wireshark:
.... .... .... 0011 = Reply code: No such name (3)

Status: Reported (1)

RFC 7707, "Network Reconnaissance in IPv6 Networks", March 2016

Source of RFC: opsec (ops)

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

Reported By: Anvar Durmanov
Date Reported: 2024-09-24

Section 4.1.1.1 says:

1.  The "Universal" bit (bit 6, from left to right) of the address is 
set to 1.

It should say:

1.  The "Universal" bit (bit 7, from left to right) of the address is 
set to 1.

Notes:

The "Universal" bit is the bit #7 and not the bit #6.

Report New Errata



Advanced Search