Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

P. Dawes
C. Arunachalam

Stream:

IETF

Source:

insipid (art)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 8123

Abstract

SIP networks use signaling monitoring tools to debug customer-reported problems and for regression testing if network or clientsoftware is upgraded. As networks grow and become interconnected,including connection via transit networks, it becomes impractical topredict the path that SIP signaling will take between clients and,therefore, impractical to monitor SIP signaling end-to-end.

This document describes the requirements for adding an indicator tothe SIP Protocol Data Unit (PDU) or a SIP message that marks the PDUas a candidate for logging. Such a marking will typically be appliedas part of network testing controlled by the network operator and notused in regular client signaling. However, such a marking can becarried end-to-end, including the SIP terminals, even if a sessionoriginates and terminates in different networks.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.