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

Document Type Active Internet-Draft (insipid WG)
Last updated 2017-02-13
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                       February 13, 2017
Expires: August 17, 2017

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

Abstract

   SIP networks use signalling 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 signalling will take between user agents,
   and therefore impractical to monitor SIP signalling end-to-end.

   This document describes an indicator for the SIP protocol which can
   be used to mark signalling as of interest to logging.  Such marking
   will typically be applied as part of network testing controlled by
   the network operator and not used in regular user agent signalling.
   However, such marking can be carried end-to-end including the 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 August 17, 2017.

Copyright Notice

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

Dawes                    Expires August 17, 2017                [Page 1]
Internet-Draft               log me marking                February 2017

   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.  Motivating Scenario . . . . . . . . . . . . . . . . . . . . .   3
   4.  Skeleton Diagnostic Procedure . . . . . . . . . . . . . . . .   4
   5.  Protocol for Log-Me Marking . . . . . . . . . . . . . . . . .   5
     5.1.  Configuration for Log-Me Marking  . . . . . . . . . . . .   5
     5.2.  Starting and Stopping Log-Me Marking  . . . . . . . . . .   5
     5.3.  End Points of Log-Me Marking  . . . . . . . . . . . . . .   6
       5.3.1.  Originating and Terminating User Agent  . . . . . . .   6
       5.3.2.  Originating Edge Proxy and Terminating Edge Proxy . .   7
     5.4.  Maintaining State . . . . . . . . . . . . . . . . . . . .   7
     5.5.  Missing Log-me Marker in Dialog Being Logged  . . . . . .   9
     5.6.  Logging Multiple Simultaneous Dialogs . . . . . . . . . .  10
     5.7.  Forked Requests . . . . . . . . . . . . . . . . . . . . .  10
     5.8.  B2BUA Handling of Log-Me Marked Dialogs . . . . . . . . .  10
       5.8.1.  All B2BUA Roles . . . . . . . . . . . . . . . . . . .  10
       5.8.2.  Proxy-B2BUA . . . . . . . . . . . . . . . . . . . . .  10
         5.8.2.1.  Terminating Behaviour . . . . . . . . . . . . . .  10
       5.8.3.  Signaling-only and SDP-Modifying Signaling-only . . .  11
         5.8.3.1.  Terminating Behaviour . . . . . . . . . . . . . .  11
         5.8.3.2.  Originating Behaviour . . . . . . . . . . . . . .  11
       5.8.4.  Media Relay, Media Aware, Media Termination . . . . .  11
     5.9.  'Log-Me' Marker . . . . . . . . . . . . . . . . . . . . .  11
       5.9.1.  Header Field Parameter for Session-ID . . . . . . . .  11
       5.9.2.  Identifying Test Cases  . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
     6.1.  Trust Domain  . . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  Security Threats  . . . . . . . . . . . . . . . . . . . .  12
Show full document text