RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Held for Document Update (1)

RFC 1712, "DNS Encoding of Geographical Location", November 1994

Source of RFC: Legacy
Area Assignment: int

Errata ID: 541

Status: Held for Document Update
Type: Technical

Reported By: "Coleman, Arthur"
Date Reported: 2006-03-09
Held for Document Update by: Brian Haberman

Section 3 says:

the definitions for Latitude and Longitude are swapped.

I believe this can be considered a typo as the actual values in the
resource record can (and should) be kept in their current order.=20

The correct descriptions are (in general terms):=20
    Latitude is the degrees North or South of the Equator and can be
referenced with a range of -90 to +90.=20
    Longitude is the degrees East or West of the prime meridian and can
be referenced with a range of -180 to +180.

Below is my attempt to write the errata.  If someone wants to make
suggestion about how the errata should be written, please tell me and I
will make a go at doing it as requested.

    Art Coleman   acoleman@verisign.com


In RFC 1712 the terms Latitude and Longitude are swapped in that each
was given the other's definition. =20
Also the preferred order of the terms is Latitude then Longitude.  In
addition to matching the terms with their correct definitions, this
ordering is also addressed.

In Section 3, page 3 is a table, it says:

        MSB                                        LSB=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                 LONGITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                  LATITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                  ALTITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

It should say:

        MSB                                        LSB=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                  LATITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                 LONGITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+=20
        /                  ALTITUDE                  /=20
        +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

Rational: It is only the terms that are being corrected, the value
ranges associated with the first (-90..90) and second (-180..180)
arguments are in the preferred order.


In Section 3, page 3 under 'where:', it says:

   LONGITUDE The real number describing the longitude encoded as a=20
             printable string. The precision is limited by 256 charcters

             within the range -90..90 degrees. Positive numbers=20
             indicate locations north of the equator.

   LATITUDE The real number describing the latitude encoded as a=20
            printable string. The precision is limited by 256 charcters=20
            within the range -180..180 degrees. Positive numbers=20
            indicate locations east of the prime meridian.

Is should say:

   LATITUDE The real number describing the latitude encoded as a=20
            printable string. The precision is limited by 256 characters

            within the range -90..90 degrees. Positive numbers=20
            indicate locations north of the equator.

   LONGITUDE The real number describing the longitude encoded as a=20
             printable string. The precision is limited by 256
characters=20
             within the range -180..180 degrees. Positive numbers=20
             indicate locations east of the prime meridian.

Rational: to match the terms with their correct definitions, and fix the
spelling of the word 'characters'.


In Section 4, page 3, it says:

   GPOS has the following format:=20
           <owner> <ttl> <class> GPOS <longitude> <latitude> <altitude>

It should say:

   GPOS has the following format:=20
           <owner> <ttl> <class> GPOS <latitude> <longitude> <altitude>

Rational: It is only the terms that are being corrected, the value
ranges associated with the first (-90..90) and second (-180..180)
arguments are in the preferred order.


In Section 4, page 4, it says:

   The owner, ttl, and class fields are optional and default to the last

   defined value if omitted. The longitude is a floating point number=20
   ranging from -90 to 90 with positive values indicating locations=20
   north of the equator.  For example Perth, Western Australia is=20
   located at 32^ 7` 19" south of the equator which would be specified=20
   as -32.68820.  The latitude is a number ranging from -180.0 to 180.0.

   For example Perth, Western Australia is located at 116^ 2' 25" east=20
   of the prime meridian which would be specified as 116.86520.  Curtin=20
   University, Perth is also 10 meters above sea-level.

It should say:

   The owner, ttl, and class fields are optional and default to the last

   defined value if omitted. The latitude is a floating point number=20
   ranging from -90 to 90 with positive values indicating locations=20
   north of the equator.  For example Perth, Western Australia is=20
   located at 32^ 7` 19" south of the equator which would be specified=20
   as -32.68820.  The longitude is a number ranging from -180.0 to
180.0.=20
   For example Perth, Western Australia is located at 116^ 2' 25" east=20
   of the prime meridian which would be specified as 116.86520.  Curtin=20
   University, Perth is also 10 meters above sea-level.

Rational: to match the terms with their correct definitions.

Notes:

from pending

Report New Errata



Search RFCs
Advanced Search
×