Marking SIP Messages to be Logged
draft-ietf-insipid-logme-marking-11

The information below is for an old version of the document
Document Type Active Internet-Draft (insipid WG)
Last updated 2018-07-10 (latest revision 2018-06-25)
Replaces draft-dawes-insipid-logme-marking
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Gonzalo Salgueiro
Shepherd write-up Show (last changed 2018-02-11)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
Internet Engineering Task Force                                 P. Dawes
Internet-Draft                                            Vodafone Group
Intended status: Standards Track                          C. Arunachalam
Expires: December 27, 2018                                 Cisco Systems
                                                           June 25, 2018

                   Marking SIP Messages to be Logged
                  draft-ietf-insipid-logme-marking-11

Abstract

   SIP networks use signaling monitoring tools to diagnose user reported
   problems and for regression testing if network or user agent 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 which 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 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 27, 2018.

Dawes & Arunachalam     Expires December 27, 2018               [Page 1]
Internet-Draft               log me marking                    June 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 . . . . . . . . . . . . . . . . . . . .   3
   3.  "Log Me" Marking Protocol Aspects . . . . . . . . . . . . . .   4
     3.1.  Session-ID logme Parameter  . . . . . . . . . . . . . . .   4
     3.2.  Starting and Stopping Logging . . . . . . . . . . . . . .   4
     3.3.  Identifying Test Cases  . . . . . . . . . . . . . . . . .   5
     3.4.  Passing the Marker  . . . . . . . . . . . . . . . . . . .   5
       3.4.1.  To and From a User Device . . . . . . . . . . . . . .   5
       3.4.2.  To and From an External Network . . . . . . . . . . .   5
     3.5.  Logging Multiple Simultaneous Dialogs . . . . . . . . . .   6
     3.6.  Format of Logged Signaling  . . . . . . . . . . . . . . .   6
     3.7.  Marking Related Dialogs . . . . . . . . . . . . . . . . .   6
     3.8.  Forked Requests . . . . . . . . . . . . . . . . . . . . .  11
   4.  SIP Entity Behavior . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Scope of Marking  . . . . . . . . . . . . . . . . . . . .  11
     4.2.  Endpoints . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.3.  SIP Intermediaries Acting on Behalf of Endpoints  . . . .  13
     4.4.  B2BUAs  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.5.  "Log me" Marker Processing by SIP Intermediaries  . . . .  15
       4.5.1.  Stateless processing  . . . . . . . . . . . . . . . .  15
       4.5.2.  Stateful processing . . . . . . . . . . . . . . . . .  15
         4.5.2.1.  "Log Me" marking not supported by Originating UA   15
         4.5.2.2.  "Log Me" marking removed by Originating Network .  19
         4.5.2.3.  "Log Me" marking not supported by Terminating UA   22
         4.5.2.4.  "Log Me" marking removed by Supporting
                   Terminating Network . . . . . . . . . . . . . . .  24
Show full document text