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

"Arun Arunachalam (carunach)" <> Tue, 25 October 2016 13:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D7FA4129493 for <>; Tue, 25 Oct 2016 06:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.951
X-Spam-Status: No, score=-14.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id l3UMFRfL1POQ for <>; Tue, 25 Oct 2016 06:38:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B853F129428 for <>; Tue, 25 Oct 2016 06:38:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=7470; q=dns/txt; s=iport; t=1477402725; x=1478612325; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=7oLAr3Eup/4XfpqzaqtPEeehi7xLG3Gk1neM5teCVu4=; b=eMoOiOJwWY1yEA27XZs6k5VshQ/4S6FZK6Ud0RiwX3DurGPSZWYkB5kn Fh7TlLOoJbAp7fuwVYKRdpRz9B1bo6zNLA3eG7Nu4rWWJeZu2K9n56FBI gnIj0cGQ71eIHNAuXutT2V2Md/Q6jKTy+RUaJraF9E1hNaFEvhW0ug982 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CoAQDZXw9Y/51dJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgy8BAQEBAR1YfQeNLqYnhRaCBxwBCoJEgmxKAoFsPxQBAgEBAQEBAQF?= =?us-ascii?q?iHQuEYwEBBAEBAWQHCxACAQg/BycLFBECBA4FiFMOwXEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEciDoIglCEOkuCcoIvBZQ4hV4BhimJbYFuToQfiSiNCIQAAR42XoU?= =?us-ascii?q?CcoVkgS2BAAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,545,1473120000"; d="scan'208,217";a="339935357"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2016 13:38:44 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u9PDciGJ011034 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Oct 2016 13:38:44 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 25 Oct 2016 08:38:44 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Tue, 25 Oct 2016 08:38:43 -0500
From: "Arun Arunachalam (carunach)" <>
To: "" <>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-10.txt
Thread-Index: AQHSLsOEn5NZ4CgOQUyQ+WVsrDHciqC5gH0A
Date: Tue, 25 Oct 2016 13:38:43 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B16F5D389CCD4585B68109DC6B800772ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "Arun Arunachalam \(carunach\)" <>, "Dawes, Peter, Vodafone Group" <>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-10.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Oct 2016 13:38:50 -0000

Hi Folks,

We have posted a new version to address issues identified by Idnits<> tools

Peter & Arun

On Oct 25, 2016, at 9:27 AM,<> wrote:

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-10.txt
Pages           : 10
Date            : 2016-10-25

  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:

There's also a htmlized version available at:

A diff from the previous version is available at:

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

Internet-Drafts are also available by anonymous FTP at:

insipid mailing list