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

Document Type Active Internet-Draft (insipid WG)
Last updated 2017-08-06
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Jun 2017 - Protocol for marking... )
Document shepherd Gonzalo Salgueiro
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                 P. Dawes
Internet-Draft                                            Vodafone Group
Intended status: Standards Track                          C. Arunachalam
Expires: February 7, 2018                                  Cisco Systems
                                                          August 6, 2017

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

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.  However, such marking can be carried 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 http://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 February 7, 2018.

Dawes & Arunachalam     Expires February 7, 2018                [Page 1]

Internet-Draft               log me marking                  August 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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 . . . . . . . . . .   5
     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.  Endpoints . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.2.  SIP Intermediaries  . . . . . . . . . . . . . . . . . . .  12
       4.2.1.  B2BUAs  . . . . . . . . . . . . . . . . . . . . . . .  13
       4.2.2.  "Log me" Marker Processing  . . . . . . . . . . . . .  14
         4.2.2.1.  Stateless processing  . . . . . . . . . . . . . .  14
         4.2.2.2.  Stateful processing . . . . . . . . . . . . . . .  14
   5.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .  23
     5.1.  Missing "Log me" Marker in Dialog Being Logged  . . . . .  24
       5.1.1.  Error Cases . . . . . . . . . . . . . . . . . . . . .  24
       5.1.2.  Non-Error Cases . . . . . . . . . . . . . . . . . . .  27
     5.2.  "Log Me" Marker Appears Mid-Dialog  . . . . . . . . . . .  28
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  29
Show full document text