RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Held for Document Update (3)

RFC 5582, "Location-to-URL Mapping Architecture and Framework", September 2009

Source of RFC: ecrit (rai)

Errata ID: 2041

Status: Held for Document Update
Type: Editorial

Reported By: Karl Heinz Wolf
Date Reported: 2010-02-12
Held for Document Update by: Robert Sparks

Section 7.1 says:

Each tree can map a location described by either civic or geographic
coordinates, but not both, for one type of service (such as
'sos.police', 'sos.fire' or 'counseling') and one location profile,
although nothing prevents re-using the same servers for multiple,
different services or both types of coordinates.  The collection of
all trees for one service and location profile is known as a forest.

It should say:

Each tree can map a location described by civic and/or geographic
coordinates, for one type of service (such as 'sos.police', 'sos.fire' or
'counseling'), although nothing prevents re-using the same servers for
multiple, different services.  The collection of all trees for one service 
is known as a forest.

Notes:

Trees may have mapping data in multiple location profiles, not only in a single profile. In particular, according to RFC 5222, a LoST server must understand civic and geographic coordinates. Furthermore, there is no mechanism to discover LoST servers based on the location profile.

Errata ID: 2042

Status: Held for Document Update
Type: Editorial

Reported By: Karl Heinz Wolf
Date Reported: 2010-02-12
Held for Document Update by: Robert Sparks

Section 8 says:

   To facilitate orientation among the trees, we introduce a forest
   guide (FG), which keeps track of the coverage regions of all the
   trees for one service and location profile.  

It should say:

   To facilitate orientation among the trees, we introduce a forest
   guide (FG), which keeps track of the coverage regions of all the
   trees for one service.  

Notes:

Trees may have mapping data in multiple location profiles, not only in a single profile. In particular, according to RFC 5222, a LoST server must understand civic and geographic coordinates. Furthermore, there is no mechanism to discover LoST servers based on the location profile.

Errata ID: 2043

Status: Held for Document Update
Type: Editorial

Reported By: Karl Heinz Wolf
Date Reported: 2010-02-12
Held for Document Update by: Robert Sparks

Section 3 says:

   resolver:  A resolver is contacted by a seeker, consults a forest
      mapping server, and then resolves the query using an appropriate
      tree.  Resolvers may cache query results.


   tree:  A tree consists of a self-contained hierarchy of authoritative
      mapping servers for a particular service.  Each tree exports its
      coverage region to the forest mapping servers.

It should say:

   resolver:  A resolver is contacted by a seeker, consults a forest
      guide, and then resolves the query using an appropriate
      tree.  Resolvers may cache query results.


   tree:  A tree consists of a self-contained hierarchy of authoritative
      mapping servers for a particular service.  Each tree exports its
      coverage region to the forest guide.

Notes:

The server should be correctly referred to as "forest guide", there is no "forest mapping server" in the architecture.

Report New Errata