[Insipid] RFC 8497 on Marking SIP Messages to Be Logged

rfc-editor@rfc-editor.org Wed, 28 November 2018 00:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848FA12D4EB; Tue, 27 Nov 2018 16:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsRT7snxD3SD; Tue, 27 Nov 2018 16:30:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D350130E13; Tue, 27 Nov 2018 16:30:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4D99BB80D1E; Tue, 27 Nov 2018 16:30:08 -0800 (PST)
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20181128003008.4D99BB80D1E@rfc-editor.org>
Date: Tue, 27 Nov 2018 16:30:08 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/oBH7lWhs8HiMNhLQzUHlyPDQD3c>
Subject: [Insipid] =?utf-8?q?RFC_8497_on_Marking_SIP_Messages_to_Be_Logge?= =?utf-8?q?d?=
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Nov 2018 00:30:24 -0000

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

        
        RFC 8497

        Title:      Marking SIP Messages to Be Logged 
        Author:     P. Dawes,
                    C. Arunachalam
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2018
        Mailbox:    peter.dawes@vodafone.com, 
                    carunach@cisco.com
        Pages:      46
        Characters: 106572
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-insipid-logme-marking-13.txt

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

        DOI:        10.17487/RFC8497

SIP networks use signaling monitoring tools to diagnose user-reported
problems and to perform regression testing if network or user agent
(UA) 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 that 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 is not used in normal user agent signaling.
Operators of all networks on the signaling path can agree to carry
such marking end to end, including the originating and terminating
SIP user agents, 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.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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