Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase

["Vijay K. Gurbani" <[e-mail]>]

On 03/15/2011 04:10 PM, Anders Nygren wrote:
> Hi
> The list of mandatory fields includes Status-Code but not Reason-Phrase.
> Wouldn't it be useful to have Reason-Phrase also since RFC3261
[...]
> So at times Reason-Phrase gives some additional information that can not be
> obtained from just the Status-Code. Maybe as an optional field.

Anders: I believe for the vast majority of the uses, a status-code
suffices (it gives you an accurate idea where in the transaction
machine a certain transaction is).

Reason-phrase is additional information, for sure, but it does
not detract from the knowledge gained earlier.

At this point, I don't see the need for it as an optional field
simply for the reason that this list could grow without bounds.

If an implementation wanted to produce a reason-phrase, the
vendor extension may be the best.  At least it will be visible and
a tool can parse and use the extension as intended.

If this is not agreeable, then we will have to rethink the
optional field logging to make it extensible to handle any SIP
header that an implementation may want to log instead of
picking and choosing some fields like Reason-phrase.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / [e-mail]
Web:   http://ect.bell-labs.com/who/vkg/