Re: [Ecrit] I-D Action:draft-ietf-ecrit-lost-10.txt

[Hannes Tschofenig <Hannes.Tschofenig at gmx.net>]

Hi Karl Heinz,

I am currently addressing your comments as part of the AUTH48. Thanks 
for reading the draft so carefully. Nobody doing the implementation work 
has noticed these issues so far. Very good.

Karl Heinz Wolf wrote:
> I just had a look at the new LoST document, and I remembered that I
> had some questions concerning LoST, I still got no answer for.
>
> Here are the points that still confuse me:
>
> 1) listServices and path indication: The draft says: "Since the query
> is answered by the queried server, there
>    is no notion of recursion or indirection and no path indication."
> But the sample in figure 12 has a <path> element.
>
>   
The <path> element always has to be present according to the XML schema. 
However, it will only contain one <via> element, namely the contacted 
server.
Hence, I removed the "... and no path indication." part of the sentence.

> 2) the serviceNumber is still missing for the sample in figure 18, the
> default mapping sample (as mentioned here last year
> http://www.ietf.org/mail-archive/web/ecrit/current/msg04727.html )
> Although the servieNumber is optional in LoST, I thought the samples
> should contain it since they are emergency call samples and without a
> service number one cannot call the default PSAP.
>
>   
True. For the emergency services cases having the <serviceNumber> 
element there makes a lot of sense.


> 3) how to request a specific location profile for
> <getServiceBoundary>? see
> http://www.ietf.org/mail-archive/web/ecrit/current/msg05226.html
>
>
>   
The location profile is essentially pre-set when the initial query was 
created. Hence, in this example the response to the getServiceBoundary 
should actually be geodetic location info rather than civic.

I will fix the example -- good catch!



> And I just noticed something new:
>
> profile="urn:ietf:params:lost:location-profile:basic-civic" is used
> once, all the other examples use profile="civic".
>
>   
Fixed.

> editorial: there is a "s" missing in ListServicesResponse: "Figure 12:
> Example of <ListServiceResponse>"
>
>   
Fixed.

Ciao
Hannes

> I hope someone can clarify my concerns! Thanks in advance.
>
> karl heinz
>
>
> 2008/5/28  <Internet-Drafts at ietf.org>:
>   
> > 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           : LoST: A Location-to-Service Translation Protocol
> >        Author(s)       : T. Hardie, et al.
> >        Filename        : draft-ietf-ecrit-lost-10.txt
> >        Pages           : 79
> >        Date            : 2008-05-28
> >
> > This document describes an XML-based protocol for mapping service
> > identifiers and geodetic or civic location information to service
> > contact URIs.  In particular, it can be used to determine the
> > location-appropriate Public Safety Answering Point (PSAP) for
> > emergency services.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-10.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
> > Ecrit at ietf.org
> > https://www.ietf.org/mailman/listinfo/ecrit
> >
> >
> >     
> _______________________________________________
> Ecrit mailing list
> Ecrit at ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>   

_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit