Skip to main content

9. Changes from RFC 2052

9.1 Document Status​

Obsolescence

This document obsoletes RFC 2052.

Status Comparison:

AspectRFC 2052RFC 2782
PublicationOctober 1996February 2000
StatusExperimentalStandards Track
MaturityPreliminaryFormal Standard

9.2 Major Technical Change​

9.2.1 Underscore Prefix​

Most Important Change

The major change from that previous, experimental, version of this specification is that now the protocol and service labels are prepended with an underscore, to lower the probability of an accidental clash with a similar name used for unrelated purposes.

Format Comparison:

RFC 2052 (Old):
  Service.Proto.Name

RFC 2782 (New):
  _Service._Proto.Name

Example:

RFC 2052:
  ldap.tcp.example.com.  IN  SRV  0  0  389  server.example.com.

RFC 2782:
  _ldap._tcp.example.com.  IN  SRV  0  0  389  server.example.com.

9.3 Clarifications and Refinements​

Aside from that, changes are only intended to increase the clarity and completeness of the document.

9.3.1 Weight Field Clarification​

This document especially clarifies the use of the Weight field of the SRV records, providing:

  • Detailed algorithm description
  • Mathematical formulation
  • Implementation guidance
  • Edge case handling
Tags:
Last updated on