I am ok with either of these, though I somewhat prefer Option 2.
I don't know what you mean about Option 1 being opaque to automata. It
seems to me it provides comparable info to Option 2, giving that the UAC
knows what it used in the request.
Paul
Francois Audet wrote:
In the interest of moving forward on this arcane issue of marginal
interest, I am making the
following concrete proposal.
Here are 2 alternatives. I'd like to have a virtual show of hands on
which option is
preferred by people.
OPTION 1
Use Response code 480, with new Warning header field 390 (URI
Scheme Not Supported)
for both cases when SIP or SIPS is rejected.
The proxy or UAS may use the warning text field to provide more
indications, e.g.:
Warning: 390 isi.edu "SIPS Not Allowed"
Warning: 390 isi.edu "SIPS Required"
OPTION 2
Use Response code 480, with 2 new Warning headera field 390
(SIPS Not Allowed)
and 391 (SIPS Required).
The proxy or UAS may use the warning text field to provide user,
e.g.:
Warning: 390 isi.edu "Please use a SIP URI"
Warning: 391 isi.edu "A secure SIPS URI is required"
OPTION 1 has the characteristic of being "opaque" to Automatas, but it
is generic
enough to support other URI schemes. The precise reasons is described in
human-readable
format.
OPTON 2 has the characteristic of precisely describing the reason for
the rejection. It
is NOT opaque to Automatas. If new warnings are necessary for other URI
shemes, new warning
headers can be defined.
In both cases, existing UACs (or UACs that do not wish to have any
special behavior based
on this) will exhibit the desired behavior, i.e., it will look like
"temporarily unavailable".
_______________________________________________
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
_______________________________________________
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
