Subject: Re: [Ecrit] I-D Action:draft-ietf-ecrit-lost-sync-08.txt

From: Karl Heinz Wolf <[email-masked]>
Date: Wed, 25 Nov 2009 15:50:00 +0100

Hannes,

I just noticed the following misleading sentence in lost-sync, Section 3.3:

In this example a request is made
   for a specific mapping (with source="authoritative.bar.example" and
   sourceId="7e3f40b098c711dbb6060800200c9a66") that is more recent than
   "2006-11-01T01:00:00Z".

Since a getMappingsRequest with <exists> does not only request updates
of the existing mappings but also missing ones, I would suggest to
make that explicit in the explanation of the example:

In this example a request is made
   for a specific mapping (with source="authoritative.bar.example" and
   sourceId="7e3f40b098c711dbb6060800200c9a66") that is more recent than
   "2006-11-01T01:00:00Z" as well as any missing mapping.

Would this make the example clearer?

Karl heinz

On Mon, Oct 26, 2009 at 2:45 PM,  <[email-masked]> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.
>
>
>        Title           : Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements
>        Author(s)       : H. Schulzrinne, H. Tschofenig
>        Filename        : draft-ietf-ecrit-lost-sync-08.txt
>        Pages           : 27
>        Date            : 2009-10-26
>
> The Location-to-Service Translation (LoST) protocol is an XML-based
> protocol for mapping service identifiers and geodetic or civic
> location information to service URIs and service boundaries.  In
> particular, it can be used to determine the location-appropriate
> Public Safety Answering Point (PSAP) for emergency services.
>
> The main data structure, the <mapping> element, used for
> encapsulating information about service boundaries is defined in the
> LoST protocol specification and circumscribes the region within which
> all locations map to the same service Uniform Resource Identifier
> (URI) or set of URIs for a given service.
>
> This document defines an XML protocol to exchange these mappings
> between two nodes.  This mechanism is designed for the exchange of
> authoritative <mapping> elements between two entities.  Exchanging
> cached <mapping> elements, i.e. non-authoritative elements, is
> possible but not envisioned.  In any case, this document can also be
> used without the LoST protocol even though the format of the
> <mapping> element is re-used from the LoST specification.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-sync-08.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> _______________________________________________
> Ecrit mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/ecrit
>
>