[Insipid] RFC 8123 on Requirements for Marking SIP Messages to be Logged

rfc-editor@rfc-editor.org Wed, 22 March 2017 22:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8CF55129A0A; Wed, 22 Mar 2017 15:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FydD3eNMAiB1; Wed, 22 Mar 2017 15:57:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A490129B4D; Wed, 22 Mar 2017 15:56:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2FB6FB80D93; Wed, 22 Mar 2017 15:56:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, insipid@ietf.org
Message-Id: <20170322225646.2FB6FB80D93@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:56:46 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/0-7jZr8Jq8ZA4ezzkJDSULshsVo>
Subject: [Insipid] RFC 8123 on Requirements for Marking SIP Messages to be Logged
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Wed, 22 Mar 2017 22:57:13 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8123

        Title:      Requirements for Marking SIP Messages 
                    to be Logged 
        Author:     P. Dawes, 
                    C. Arunachalam
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    peter.dawes@vodafone.com, 
        Pages:      11
        Characters: 22368
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-insipid-logme-reqs-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8123

        DOI:        10.17487/RFC8123

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 document describes the 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 a marking will typically be applied
as part of network testing controlled by the network operator and not
used in regular client signaling.  However, such a marking can be
carried end-to-end, including the SIP terminals, even if a session
originates and terminates in different networks.

This document is a product of the INtermediary-safe SIP session ID Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC