Marking SIP Messages to Be Logged
RFC 8497
Revision differences
Document history
Date | By | Action |
---|---|---|
2019-08-19
|
Gunter Van de Velde | Closed request for Telechat review by OPSDIR with state 'Overtaken by Events' |
2019-08-19
|
Gunter Van de Velde | Assignment of request for Telechat review by OPSDIR to Fred Baker was marked no-response |
2018-12-19
|
(System) | Received changes through RFC Editor sync (changed abstract to 'SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if … Received changes through RFC Editor sync (changed abstract to 'SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signaling will take between user agents and therefore impractical to monitor SIP signaling end to end. This document describes an indicator for the SIP protocol that can be used to mark signaling as being of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and is not used in normal user agent signaling. Operators of all networks on the signaling path can agree to carry such marking end to end, including the originating and terminating SIP user agents, even if a session originates and terminates in different networks.') |
2018-11-27
|
(System) | Received changes through RFC Editor sync (created alias RFC 8497, changed title to 'Marking SIP Messages to Be Logged', changed abstract to 'SIP networks … Received changes through RFC Editor sync (created alias RFC 8497, changed title to 'Marking SIP Messages to Be Logged', changed abstract to 'SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signaling will take between user agents and therefore impractical to monitor SIP signaling end to end.', changed pages to 46, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-11-27, changed IESG state to RFC Published) |
2018-11-27
|
(System) | RFC published |