errata logo graphic

Found 3 records.

Status: Verified (1)

RFC5864, "DNS SRV Resource Records for AFS", April 2010

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 2260

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-05-13
Verifier Name: Pete Resnick
Date Verified: 2011-08-04

Section 4., pg.5 says:

[[ second paragraph on page 5: ]]

   DNS SRV RRs, like all DNS RRs, have a time-to-live (TTL), after which
   the SRV record information is no longer valid (see [RFC1034]).  DNS
|  RRs SHOULD be discarded after their TTL, and after the DNS query
   repeated.  This applies to DNS SRV RRs for AFS as it does for any
   other DNS RR.  Any information derived from the DNS SRV RRs, such as
   preference ranks, MUST be discarded when the DNS SRV RR is expired.

It should say:

   DNS SRV RRs, like all DNS RRs, have a time-to-live (TTL), after which
   the SRV record information is no longer valid (see [RFC1034]).  DNS
|  RRs SHOULD be discarded after their TTL, and the DNS query be
   repeated.  This applies to DNS SRV RRs for AFS as it does for any
   other DNS RR.  Any information derived from the DNS SRV RRs, such as
   preference ranks, MUST be discarded when the DNS SRV RR is expired.

Notes:

Rationale:
Obviously a late change to the text that distorts the proper sense.
The I-D text was correct.

Perhaps the affected sentence could more explicitly state:

..., and the DNS query be repeated as soon as the information
is needed again.


Status: Held for Document Update (1)

RFC5864, "DNS SRV Resource Records for AFS", April 2010

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 2767

Status: Held for Document Update
Type: Technical

Reported By: IƱaki Baz Castillo
Date Reported: 2011-04-05
Held for Document Update by: Peter Saint-Andre

Section 6 says:

   afsdb1, afsdb2, and afsdb3 all provide VLDB service via UDP.  The
   first two have the same priority but have weights indicating that
   afsdb1 should get about twice as many clients as afsdb2.

It should say:

   afsdb1, afsdb2, and afsdb3 all provide VLDB service via UDP.  The
   first two have the same priority but have weights indicating that
   afsdb2 should get about twice as many clients as afsdb1.

Notes:

The given DNS zone file shows:

_afs3-vlserver._udp SRV 0 2 7003 afsdb1.example.com.
_afs3-vlserver._udp SRV 0 4 7003 afsdb2.example.com.

This means that afsdb2.example.com. as weight 4 (double of weight for afsdb1.example.com.).

According to RFC 2782:

Weight
A server selection mechanism. The weight field specifies a
relative weight for entries with the same priority. Larger
weights SHOULD be given a proportionately higher probability of
being selected.


Status: Rejected (1)

RFC5864, "DNS SRV Resource Records for AFS", April 2010

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 2259

Status: Rejected
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-05-13
Rejected by: Pete Resnick
Date Rejected: 2011-08-04

Section Abstract says:

   ... DNS (Domain Name Service) ...

It should say:

   ... DNS (Domain Name System) ...

Notes:

Rationale: wrong expansion of acronym
--VERIFIER NOTES--
Both terms have been used. (See RFCs 830, 1001, 1834, etc.)


Report New Errata