Marking SIP Messages to Be Logged
RFC 8497

Document Type RFC - Proposed Standard (November 2018; No errata)
Last updated 2018-11-27
Replaces draft-dawes-insipid-logme-marking
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jun 2017 - Protocol for marking... )
Document shepherd Gonzalo Salgueiro
Shepherd write-up Show (last changed 2018-02-11)
IESG IESG state RFC 8497 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          P. Dawes
Request for Comments: 8497                                Vodafone Group
Category: Standards Track                                 C. Arunachalam
ISSN: 2070-1721                                            Cisco Systems
                                                           November 2018

                   Marking SIP Messages to Be Logged

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8497.

Dawes & Arunachalam          Standards Track                    [Page 1]
RFC 8497                     Log Me Marking                November 2018

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  "Log Me" Marking Protocol Aspects . . . . . . . . . . . . . .   4
     3.1.  Session-ID "logme" Parameter  . . . . . . . . . . . . . .   4
     3.2.  Starting and Stopping Logging . . . . . . . . . . . . . .   5
     3.3.  Identifying Test Cases  . . . . . . . . . . . . . . . . .   6
     3.4.  Passing the Marker  . . . . . . . . . . . . . . . . . . .   6
       3.4.1.  To/From a User Device . . . . . . . . . . . . . . . .   6
       3.4.2.  To/From an External Network . . . . . . . . . . . . .   6
       3.4.3.  Across a Non-supporting SIP Intermediary  . . . . . .   6
     3.5.  Logging Multiple Simultaneous Dialogs . . . . . . . . . .   6
     3.6.  Format of Logged Signaling  . . . . . . . . . . . . . . .   7
     3.7.  Marking-Related Dialogs . . . . . . . . . . . . . . . . .   7
     3.8.  Forked Requests . . . . . . . . . . . . . . . . . . . . .  13
   4.  SIP Entity Behavior . . . . . . . . . . . . . . . . . . . . .  13
     4.1.  Scope of Marking  . . . . . . . . . . . . . . . . . . . .  13
     4.2.  Endpoints . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  SIP Intermediaries Acting on Behalf of Endpoints  . . . .  15
     4.4.  B2BUAs  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     4.5.  "Log Me" Marker Processing by SIP Intermediaries  . . . .  17
       4.5.1.  Stateless Processing  . . . . . . . . . . . . . . . .  17
       4.5.2.  Stateful Processing . . . . . . . . . . . . . . . . .  17
         4.5.2.1.  "Log Me" Marking Not Supported by Originating UA   18
         4.5.2.2.  "Log Me" Marking Not Supported by Terminating UA   21
         4.5.2.3.  "Log Me" Marking Removed by Originating Network .  23
         4.5.2.4.  "Log Me" Marking Removed by Supporting
                   Terminating Network . . . . . . . . . . . . . . .  26
         4.5.2.5.  "Log Me" Marking Passed by Non-supporting
                   Terminating Network . . . . . . . . . . . . . . .  28

Dawes & Arunachalam          Standards Track                    [Page 2]
Show full document text