James,
I think your #1 and #2 covers it, in addition to an identifier that
points to the location element that suffers from the problem
identified. (The latter was discussed, if I recall correctly, but
seems to be missing from your syntax proposal.)
I don't feel strongly about identifying the originator of the error,
but it might be useful to have an extensible parameter list, in
standard SIP header fashion, so that we can easily add more debugging
information later.
Henning
On Jul 5, 2007, at 8:22 PM, James M. Polk wrote:
Henning
Regarding Conveyance -08 and the new Geolocation-Error header that
you want to replace the Warning header code(s) function (section
3.4 of the -07 ID)...
What fields do you want in the header?
#1 error-code,
#2 text-string explaining what error it is
#?
Do you need anything else?
Warning had/has the node ID of the sending entity. Do you want that
in the new Geolocation-Error header? Do you really see a purpose
in having that piece there?
Attempting to put the final pieces of -08 together, and this new
header is less than straightforward in writing it.
Is this viable ABNF for what you want?
Geolocation-Error = "Geolocation-Error" HCOLON (locationErrorValue
*(COMMA locationErrorValue))
locationErrorValue = numeric-code *(SEMI geoloc-error-param)
numeric-code = decimal-string
geoloc-error-param = "code" EQUAL error-text-string
/ generic-param ; (from RFC 3261)
error-text-string = string
(anyone) let me know what you think
Thanks
James
_______________________________________________
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
