On Apr 30, 2007, at 8:31 PM, James M. Polk wrote:
for whatever reason, a request has a PIDF-LO with city, street,
street number, etc *but* not state or country. How does this get
indicated in the new Geolocation-Error header field format?
The same way it does in the existing Warning header, I presume. I was
not trying to make the new header do location verification.
this is exactly the example that was given to me two IETFs ago when
you (and others) wanted the XML blob as a message body part in the
424 response (with the exact failure and the exact fields that are
bad (for whatever reason)).
I had no problem with goin along with that message body in 424
idea, but I had a timing issue with "it ain't done yet, and it
ain't even started yet, so how long is it gonna take to get there"
wondering.
I put it into -06 and got a few comments that absolutely didn't
like the idea, so I took it back out, leaving us with little exact
info on what's bad in the request that Warning (and Reason) can't
solve for in their current form.
To cite a slightly related example, we don't have a formal mechanism
to specify exactly which part of an SDP description is broken, or to
call out the syntax error in SIP messages by line number or precise
description. I think of these more like compiler errors, which are
also presented as (maybe) some generic label and plain text.
In general, such information isn't useful to machines, since they
can't debug the problem by themselves, so if an implementation wants
to be helpful, a simple
Geo-Error: "Missing <country>" <some-syntax-error-code>
is probably about as helpful as you can get. This type of error
message is only useful to humans, after all.
Thus, I agree that no additional XML error reporting is necessary here.
but they aren't trustworthy domains, so the administrators don't
want to give someone the answer if they don't already have it
That's presumably not a problem in our case.
Henning
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
