Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

P. Dawes
C. Arunachalam

Stream:

IETF

Source:

insipid (art)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8497

Discuss this RFC: Send questions or comments to the mailing listinsipid@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8497

Abstract

SIP networks use signaling monitoring tools to diagnose user-reportedproblems and to perform regression testing if network or user agent(UA) software is upgraded. As networks grow and becomeinterconnected, including connection via transit networks, it becomesimpractical to predict the path that SIP signaling will take betweenuser agents and therefore impractical to monitor SIP signaling end toend.

This document describes an indicator for the SIP protocol that can beused to mark signaling as being of interest to logging. Such markingwill typically be applied as part of network testing controlled bythe network operator and is not used in normal user agent signaling.Operators of all networks on the signaling path can agree to carrysuch marking end to end, including the originating and terminatingSIP user agents, even if a session originates and terminates indifferent networks.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.