errata logo graphic

Found 8 records.

Status: Verified (3)

RFC1034, "Domain names - concepts and facilities", November 1987

Source of RFC: Legacy
Area Assignment: int

Errata ID: 564

Status: Verified
Type: Technical

Reported By: Chlisin
Date Reported: 2003-02-06

Section 3.3 says:

   The usual mail address <local-part>@<mail-domain> is mapped into a
   domain name by converting <local-part> into a single label
   (regardles of dots it contains), converting <mail-domain> into a
   domain name using the usual text format for domain names (dots
   denote label breaks), and concatenating the two to form a single
   domain name. 

It should say:

   The usual mail address <local-part>@<mail-domain> is mapped into a
   domain name by converting <local-part> into a single label
   (regardless of dots it contains), converting <mail-domain> into a
   domain name using the usual text format for domain names (dots
   denote label breaks), and concatenating the two to form a single
   domain name.


Errata ID: 565

Status: Verified
Type: Editorial

Reported By: "Yin Shuming"
Date Reported: 2006-02-18

Section 4.3.1 says:

This bit specifies specifies whether the requester wants recursive service 
for this query. Clients may.....

It should say:

This bit specifies whether the requester wants recursive service for this 
query. Clients may.....


Errata ID: 1074

Status: Verified
Type: Editorial

Reported By: John Kristoff
Date Reported: 2006-03-13

 

Section 2.2. says:

  - Where there tradeoffs between the cost of acquiring data, the

but should probably say:

  - Where there are tradeoffs between the cost of acquiring data, the

Section 3.6.2. says:

  For example, suppose a name server was processing a query with for

but should probably simply say:

  For example, suppose a name server was processing a query for

Section 4.3.4. misspells 'because':

  This feature can be particularly important in a system which
  implements naming short shorts that use search lists beacuse

It should say:

[see above]

Notes:

from pending


Status: Held for Document Update (5)

RFC1034, "Domain names - concepts and facilities", November 1987

Source of RFC: Legacy
Area Assignment: int

Errata ID: 755

Status: Held for Document Update
Type: Technical

Reported By: John Kristoff
Date Reported: 2006-03-13
Held for Document Update by: Brian Haberman
Date Held: 2012-04-26

 

Section 6.1. ends this way:

  Relative and absolute domain names may be freely intermixed in a
  master

which is incomplete.  It's unclear exactly how that sentence may have
been intended to end, but minimally I would suggeste it at least
terminated with 'file.'.

Section 6.2.8. in the diagram shows 'QTYPE=A', but should be of
type 'CNAME' based on the context of the example.

It should say:

[see above]

Notes:

from pending


Errata ID: 4270

Status: Held for Document Update
Type: Editorial

Reported By: Jean-Philippe Paradis
Date Reported: 2015-02-12
Held for Document Update by: Ted Lemon
Date Held: 2015-02-12

Section 2.4 says:

In the interests of performance, implementations may couple these
functions.  For example, a resolver on the same machine as a name server
might share a database consisting of the the zones managed by the name
server and the cache managed by the resolver.

It should say:

In the interests of performance, implementations may couple these
functions.  For example, a resolver on the same machine as a name server
might share a database consisting of the zones managed by the name
server and the cache managed by the resolver.

Notes:

Just a duplicate "the".


Errata ID: 4269

Status: Held for Document Update
Type: Editorial

Reported By: Jean-Philippe Paradis
Date Reported: 2015-02-12
Held for Document Update by: Ted Lemon
Date Held: 2015-02-12

Section 2.3 says:

The organization of the domain system derives from some assumptions
about the needs and usage patterns of its user community and is designed
to avoid many of the the complicated problems found in general purpose
database systems.

It should say:

The organization of the domain system derives from some assumptions
about the needs and usage patterns of its user community and is designed
to avoid many of the complicated problems found in general purpose
database systems.

Notes:

Just a duplicate "the".


Errata ID: 4229

Status: Held for Document Update
Type: Editorial

Reported By: Sun Congyou
Date Reported: 2015-01-11
Held for Document Update by: Ted Lemon
Date Held: 2015-01-14

Section 4.2.2 says:

[RFC-1033] catalogs available DNS software an discusses administration 
procedures.

It should say:

[RFC-1033] catalogs available DNS software and discusses administration 
procedures.

Errata ID: 4230

Status: Held for Document Update
Type: Editorial

Reported By: Sun Congyou
Date Reported: 2015-01-11
Held for Document Update by: Ted Lemon
Date Held: 2015-01-14

Section 4.3.3 says:

   - When the query name or a name between the wildcard domain and
     the query name is know to exist.

It should say:

   - When the query name or a name between the wildcard domain and
     the query name is known to exist.

Report New Errata