Requirements for Marking SIP Messages to be Logged
draft-ietf-insipid-logme-reqs-04

The information below is for an old version of the document
Document Type Active Internet-Draft (insipid WG)
Authors Peter Dawes  , Chidambaram Arunachalam 
Last updated 2015-10-14 (latest revision 2015-08-19)
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
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: Informational                            C. Arunachalam
Expires: February 20, 2016                                 Cisco Systems
                                                         August 19, 2015

           Requirements for Marking SIP Messages to be Logged
                    draft-ietf-insipid-logme-reqs-04

Abstract

   SIP networks use signalling monitoring tools to debug customer
   reported problems and for regression testing if network or client
   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 clients, and
   therefore impractical to monitor SIP signalling end-to-end.

   This draft describes requirements for adding an indicator to the SIP
   protocol data unit (PDU, or a SIP message) that marks the PDU as a
   candidate for logging.  Such marking will typically be applied as
   part of network testing controlled by the network operator and not
   used in regular client signalling.  However, such marking can be
   carried end-to-end including the SIP terminals, 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 20, 2016.

Dawes & Arunachalam     Expires February 20, 2016               [Page 1]
Internet-Draft                log me marker                  August 2015

Copyright Notice

   Copyright (c) 2015 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in this Document . . . . . . . . . . . . . .   3
   3.  Motivating Scenario . . . . . . . . . . . . . . . . . . . . .   3
   4.  Basic Debugging Procedure . . . . . . . . . . . . . . . . . .   4
   5.  Requirements for a "Log Me" Marker  . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
     6.1.  Trust Domain  . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Security Threats  . . . . . . . . . . . . . . . . . . . .   7
       6.2.1.  "Log Me" Marking  . . . . . . . . . . . . . . . . . .   7
       6.2.2.  Sending Logged Information  . . . . . . . . . . . . .   7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Service providers who use SIP (see RFC 3261 [RFC3261]) in their
   networks need the ability to debug customer reported problems and
   also need to run regression tests if SIP client software/hardware is
   upgraded.  Such debugging and tests might be confined to a single
   service provider but might also be needed for customers who have
   different service providers, including providers in different
   countries that are interconnected through networks belonging to one
   or more third parties.

   A mechanism is needed to mark particular SIP sessions, i.e. those
   related to debugging or regression testing, as candidates for logging
   and this marking must be carried within the candidate SIP messages as
   they are routed across networks (and geographies) to enable logging

Dawes & Arunachalam     Expires February 20, 2016               [Page 2]
Show full document text