[Insipid] I-D Action: draft-ietf-insipid-logme-reqs-09.txt

internet-drafts@ietf.org Tue, 18 October 2016 09:22 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietf.org
Delivered-To: insipid@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1261129503; Tue, 18 Oct 2016 02:22:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147678256078.30861.6456655243391185124.idtracker@ietfa.amsl.com>
Date: Tue, 18 Oct 2016 02:22:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/st4zqkzgh7KqWDURJFu_XhHRXhY>
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-09.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 09:22:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the INtermediary-safe SIP session ID of the IETF.

        Title           : Requirements for Marking SIP Messages to be Logged
        Authors         : Peter Dawes
                          Chidambaram Arunachalam
	Filename        : draft-ietf-insipid-logme-reqs-09.txt
	Pages           : 10
	Date            : 2016-10-18

Abstract:
   SIP networks use signaling 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 signaling will take between clients, and
   therefore impractical to monitor SIP signaling 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 signaling.  However, such marking can be
   carried end-to-end including the SIP terminals, even if a session
   originates and terminates in different networks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-reqs/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-insipid-logme-reqs-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-logme-reqs-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/