From victor.pascual.avila@gmail.com Fri Jul 3 06:40:23 2009 Return-Path: X-Original-To: sip-ops@core3.amsl.com Delivered-To: sip-ops@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D3FC3A68C0; Fri, 3 Jul 2009 06:40:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P+-gYxL1+gC; Fri, 3 Jul 2009 06:40:22 -0700 (PDT) Received: from mail-bw0-f207.google.com (mail-bw0-f207.google.com [209.85.218.207]) by core3.amsl.com (Postfix) with ESMTP id 579F73A6E0C; Fri, 3 Jul 2009 06:40:10 -0700 (PDT) Received: by bwz3 with SMTP id 3so361319bwz.37 for ; Fri, 03 Jul 2009 06:40:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=wXnrvZnoJThKLY7YESLSRVQbzLG7OPnksegz8jNUiUA=; b=KfkRtjb+UZ7h7UkjhYIxNhfFpp56zYNhm9u4amxes5CH3pKXSYF8+16MMXpueY/nSa AZLX+rkV1PhHZHfRWviVHjGLeuBgdjbfKV/GZaYHwTLAhnlLTerGKzy6V3weurRBPNEa 5p01riTt6nuDT7PSOCjPxKWQfWPvfbRXdUoM8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=H1oEQq0LDE2IgtD9/0NPZfV12/bQbcH/qdnEE0Ug4L3VpjLrzv2zzbwK0kpwrIk+Jk Xkd35HGm8aOIE1qCZB6Q8w97IKChE1dEut4ywsgG2lAbGML+QLEfp9QK32AHFSmOVq8g Tu6P0rT4zV4AeHoy8fXphukDUPvewPi3IKzto= MIME-Version: 1.0 Received: by 10.204.79.20 with SMTP id n20mr1281720bkk.78.1246628430637; Fri, 03 Jul 2009 06:40:30 -0700 (PDT) Date: Fri, 3 Jul 2009 15:40:30 +0200 Message-ID: <618e24240907030640k2898f908s450626af73dad5f8@mail.gmail.com> From: Victor Pascual Avila To: sip-ops@ietf.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dispatch@ietf.org Subject: [sip-ops] I-D Action:draft-kuthan-dispatch-diagrevived-00.txt X-BeenThere: sip-ops@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Operations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 13:40:23 -0000 Hi Folks, We have just submitted a draft which proposes a new header field called Debug. The purpose of this header field is to convey extra debugging information that can be used to locate errors in SIP entities involved in the processing of a SIP transaction. Abstract: A major responsibility of Session Initiation Protocol (SIP) servers is to provide application-layer routing. SIP routing can be quite complex and lead to similarly complicated paths that SIP requests traverse on the way to their actual destinations. It is therefore important to be in position to troubleshoot errors that occur along a SIP path, inside and outside troubleshooters' administrative domains. Particularly important for the troubleshooters is knowledge of where an error occurred in a SIP path. This document introduces a new header field called Debug. The purpose of the header field is to convey extra debugging information that can be used to locate errors in SIP implementations involved in processing of a SIP transaction. A temporal URL for this Internet-Draft is: http://www.ietf.org/proceedings/staging/draft-kuthan-dispatch-diagrevived-0= 0.txt Comments are welcome! Regards, --=20 Victor Pascual =C3=81vila From rjsparks@nostrum.com Fri Jul 17 14:15:14 2009 Return-Path: X-Original-To: sip-ops@core3.amsl.com Delivered-To: sip-ops@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E95503A6AE5; Fri, 17 Jul 2009 14:15:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MzWY58jY95Sy; Fri, 17 Jul 2009 14:15:13 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 1EFFD3A68EC; Fri, 17 Jul 2009 14:15:09 -0700 (PDT) Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6HLFf4C098114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jul 2009 16:15:41 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Message-Id: From: Robert Sparks To: sip-ops@ietf.org, dispatch mailing list Content-Type: multipart/alternative; boundary=Apple-Mail-140--1024798114 Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 17 Jul 2009 16:15:41 -0500 References: X-Mailer: Apple Mail (2.935.3) Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) Subject: [sip-ops] Fwd: draft CLF charter X-BeenThere: sip-ops@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Operations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 21:15:15 -0000 --Apple-Mail-140--1024798114 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Please follow and participate in this discussion on the sip-clf list if you are interested. RjS Begin forwarded message: > From: Robert Sparks > Date: July 17, 2009 4:13:58 PM CDT > To: sip-clf@ietf.org > Subject: draft CLF charter > > All - > > We are working on forming a CLF working group based on DISPATCH's > decision. > > Below is a proposed charter for this working group. Please review > and comment > on this list. Depending on the feedback we receive, we will target > forming this > group shortly after the Stockholm meeting. > > We'll also be discussing this in Thursday's opsarea meeting. > > Thanks, > > RjS > > >> The SIP Common Log File (CLF) working group is chartered to define >> a standard logging format for systems processing SIP messages. >> >> Well-known web servers such as Apache and web proxies like Squid >> support event logging using a common log format. The logs produced >> using these de-facto standard formats are invaluable to system >> administrators for trouble-shooting a server and tool writers to >> craft tools that mine the log files to produce reports and trends >> and to search for a certain SIP message or messages, a transaction >> or a related set of transactions. Furthermore, these log records >> can also be used to train anomaly detection systems and feed events >> into a security event management system. >> >> The Session Initiation Protocol does not have a common log >> format. Diverse element provide distinct log formats making >> it complex to produce tools to analyze them. >> >> The CLF working group will produce a format suitable for logging >> from any SIP element. The format will anticipate the need to >> search, merge, and summarize the log records from diverse elements. >> The format will anticipate the need to correlate messages from >> multiple elements related to a given request (that may fork) >> or a given dialog. The format will take SIP's extensibility into >> consideration, providing a way to represent SIP message components >> that are defined in the future. The format will anticipate being >> used both for off-line analysis and on-line real-time processing >> applications. The working group will consider the need for >> efficient processing in its design of this format. >> >> The working group is not pre-constrained to producing either a >> bit-field oriented or text-oriented format, and may choose to >> provide both. If the group chooses to specify both, it must be >> possible to mechanically translate between the formats without >> loss of information. >> >> Specifying the mechanics of exchanging, transporting, and storing >> SIP Common Log Format records is explicitly out of scope. Specifying >> a real-time transfer mechanism for heuristic analysis is explicitly >> out of scope. >> >> The group will generate: >> >> - A problem statement enunciating the motivation, >> and use cases for a SIP Common Log Format. This analysis >> will identify the required minimal information that must >> appear in any record. >> >> - A specification of the SIP Common Log Format record. >> >> The group will consider providing one or more reference >> implementations for decoding a CLF record. >> >> Goals and Milestones >> =========================== >> >> Nov 09 - Problem statement, motivation, and use cases to IESG >> (Informational) >> Feb 10 - SIP Common Log Format specification to IESG (PS) >> > --Apple-Mail-140--1024798114 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Please follow and participate = in this discussion on the sip-clf list if you are = interested.

RjS

Begin = forwarded message:

From: = Robert Sparks <rjsparks@nostrum.com>
Date: July 17, 2009 4:13:58 PM = CDT
Subject: = draft CLF charter

All -

We are working on = forming a CLF working group based on DISPATCH's decision.

Below = is a proposed charter for this working group. Please review and = comment
on this list. Depending on the feedback we receive, we will = target forming this
group shortly after the Stockholm = meeting.

We'll also be discussing this in Thursday's opsarea = meeting.

Thanks,

RjS


The SIP Common Log File (CLF) working group is chartered = to define
a standard logging = format for systems processing SIP messages.

Well-known web = servers such as Apache and web proxies like = Squid
support event logging = using a common log format.  The logs = produced
using these de-facto = standard formats are invaluable to system
administrators for trouble-shooting a server and tool = writers to
craft tools that = mine the log files to produce reports and = trends
and to search for a = certain SIP message or messages, a = transaction
or a related set = of transactions.  Furthermore, these log = records
can also be used to = train anomaly detection systems and feed = events
into a security event = management system.

The Session = Initiation Protocol does not have a common = log
format. Diverse element = provide distinct log formats making
it complex to produce tools to analyze = them.

The CLF working = group will produce a format suitable for = logging
from any SIP element. = The format will anticipate the need to
search, merge, and summarize the log records from diverse = elements.
The format will = anticipate the need to correlate messages = from
multiple elements related = to a given request (that may fork)
or a given dialog. The format will take SIP's = extensibility into
consideration, providing a way to represent SIP message = components
that are defined in = the future.  The format will anticipate = being
used both for off-line = analysis and on-line real-time processing
applications. The working group will consider the need = for
efficient processing in = its design of this format.

The working = group is not pre-constrained to producing either = a
bit-field oriented or = text-oriented format, and may choose to
provide both. If the group chooses to specify both, it = must be
possible to = mechanically translate between the formats = without
loss of = information.

Specifying the = mechanics of exchanging, transporting, and = storing
SIP Common Log Format = records is explicitly out of scope. = Specifying
a real-time = transfer mechanism for heuristic analysis is = explicitly
out of = scope.

The group will = generate:

- A problem = statement enunciating the motivation,
and use cases for a SIP Common Log Format. This = analysis
will identify the = required minimal information that must
appear in any record.

- A = specification of the SIP Common Log Format = record.

The group will = consider providing one or more reference
implementations for decoding a CLF = record.

Goals and = Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D

Nov 09 - = Problem statement, motivation, and use cases to IESG = (Informational)
Feb 10 - SIP = Common Log Format specification to IESG (PS)



= --Apple-Mail-140--1024798114-- From dworley@nortel.com Thu Jul 23 11:43:01 2009 Return-Path: X-Original-To: sip-ops@core3.amsl.com Delivered-To: sip-ops@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF33A28C12F; Thu, 23 Jul 2009 11:43:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.447 X-Spam-Level: X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlYqUIqzQ4Yi; Thu, 23 Jul 2009 11:43:01 -0700 (PDT) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id E452428C0DB; Thu, 23 Jul 2009 11:42:54 -0700 (PDT) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n6NIf6M24799; Thu, 23 Jul 2009 18:41:06 GMT Received: from [47.141.31.129] ([47.141.31.129]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 14:40:53 -0400 From: "Dale Worley" To: Victor Pascual Avila In-Reply-To: <618e24240907030640k2898f908s450626af73dad5f8@mail.gmail.com> References: <618e24240907030640k2898f908s450626af73dad5f8@mail.gmail.com> Content-Type: text/plain Organization: Nortel Networks Date: Thu, 23 Jul 2009 14:40:52 -0400 Message-Id: <1248374452.4427.14.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Jul 2009 18:40:53.0497 (UTC) FILETIME=[1BB7BE90:01CA0BC5] Cc: sip-ops@ietf.org, dispatch@ietf.org Subject: Re: [sip-ops] I-D Action:draft-kuthan-dispatch-diagrevived-00.txt X-BeenThere: sip-ops@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Operations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2009 18:43:01 -0000 On Fri, 2009-07-03 at 15:40 +0200, Victor Pascual Avila wrote: > A temporal URL for this Internet-Draft is: > http://www.ietf.org/proceedings/staging/draft-kuthan-dispatch-diagrevived-00.txt Now at http://www.ietf.org/id/draft-kuthan-dispatch-diagrevived-00.txt Dale From victor.pascual.avila@gmail.com Fri Jul 24 07:34:49 2009 Return-Path: X-Original-To: sip-ops@core3.amsl.com Delivered-To: sip-ops@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 483603A6B54; Fri, 24 Jul 2009 07:34:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vd-BGFxVPNKw; Fri, 24 Jul 2009 07:34:48 -0700 (PDT) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by core3.amsl.com (Postfix) with ESMTP id 224353A6778; Fri, 24 Jul 2009 07:34:47 -0700 (PDT) Received: by ey-out-2122.google.com with SMTP id 22so449139eye.31 for ; Fri, 24 Jul 2009 07:34:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DFtDPW4g+taIwbnadW1leJ+zKVYoy+JkGwPaPLUXdh4=; b=KKlZRkSzvSKUim4/YYqHzmELcjgqQINpiszKxpAk2y6sT82IDBU8KGBufVxlRGr3eV tI3R5hCBZ+pWnTYoK0p8YbOtS+YYi6m9Yt/6DmTTqkfZHzfsaLxLxaRavTr64thhBx1J wsDLZAPtf5v7BS++j6cn94J/j130nNaqIk7vI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=na5S6BudtU8/UrUMkzlLyVifRBgn6AgS9SIwhF9963Dnq+0ZlcRvfXz/FZUNK6hu99 mCi+jOABhg2YZjwdIFhYqf11QmIutoEMyrxh2m1b9g2WRyHQnje3uWojTaa0rQAbUnlb LYI2FmaXR57Dq2pMmZE9dfRB5IGHgFSoBb4iE= MIME-Version: 1.0 Received: by 10.216.86.193 with SMTP id w43mr8146wee.17.1248446086138; Fri, 24 Jul 2009 07:34:46 -0700 (PDT) In-Reply-To: <1248374452.4427.14.camel@victoria-pingtel-com.us.nortel.com> References: <618e24240907030640k2898f908s450626af73dad5f8@mail.gmail.com> <1248374452.4427.14.camel@victoria-pingtel-com.us.nortel.com> Date: Fri, 24 Jul 2009 16:34:46 +0200 Message-ID: <618e24240907240734o78c758eds1578a27e9811ab00@mail.gmail.com> From: Victor Pascual Avila To: Dale Worley Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: sip-ops@ietf.org, dispatch@ietf.org Subject: Re: [sip-ops] I-D Action:draft-kuthan-dispatch-diagrevived-00.txt X-BeenThere: sip-ops@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Operations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2009 14:34:49 -0000 On Thu, Jul 23, 2009 at 8:40 PM, Dale Worley wrote: > On Fri, 2009-07-03 at 15:40 +0200, Victor Pascual Avila wrote: >> A temporal URL for this Internet-Draft is: >> http://www.ietf.org/proceedings/staging/draft-kuthan-dispatch-diagrevive= d-00.txt > > Now at http://www.ietf.org/id/draft-kuthan-dispatch-diagrevived-00.txt Thanks for the update, Dale. We would appreciate feedback as to whether this is helpful and going in the right direction, as well as detailed comments-- there are some open issues (Appendix B) that we would like to get discussed (Topology Hiding, Amount of troubleshooting information, Selective logging and B2BUA traversal). Cheers, --=20 Victor Pascual =C3=81vila