>Hi James,
>
> >>PS: When including the text about <locationType> element two issues
> >>that might need to get discussed, namely the ability to carry
> >multiple
> >>PIDF-Los (or to include multiple representations of the
> >location in the
> >>same PIDF-LO) in a NOTIFY and the need to define some error messages
> >>(e.g., to tell the Notifier that the requested locationType
> >is actually not available).
> >
> >this last "e.g." part -- shouldn't that be decided at
> >subscription time by the UAS not accepting the subscription,
> >or for the periodic interval update of location be a simple
> >RFC 3261 defined 480 (Temporarily Unavailable) ?
>
>That's a good question. I could imagine that providing the error during
>subscription time would probably be most useful. However, I could imagine
>that certain errors could happen during the lifetime of the subscription.
perhaps I misunderstood you comment about "defining some error
messages" as *creating* some new ones that don't exist already. If
that's the case, I apologize.
>A protoype implementation would help to understand the error codes better.
>
>Ciao
>Hannes
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
