[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] I-D Action:draft-ietf-ecrit-lost-10.txt
Hi Hannes!
>>I hope you did not miss to remove sos.suicide? (figure 12 and 14!)
>
>
> I put you on CC when I sent the mail to the RFC Editor
Thank you, I read this mail now and it's corrected there.
>>
>>And also don't forget to correct the examples on your webpage!
>
> Will do that once the entire process is completed.
>
>>
>>just one more clarification please:
>>
>>>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!
>>>
>>
>>how is the location profile pre-set? is it somehow done with
>>the key (the draft does not say this, I'm just guessing)?
>
> With the initial <findService> request. The location profile used in the
> <location> element is supposed to be the same as the one that is later
> returned.
>
but how should the LoST server know what profile to return when a
client does a getServiceBoundary request (some time after the initial
findService)? Is the LoST Server expected to identify the clients
somehow and to store information what client gets which location
profile?
cheers
karl heinz
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit