
From rjsparks@nostrum.com  Thu Dec  1 15:16:48 2011
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099D421F92C7 for <sip-clf@ietfa.amsl.com>; Thu,  1 Dec 2011 15:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0cC-g2w4o9fB for <sip-clf@ietfa.amsl.com>; Thu,  1 Dec 2011 15:16:47 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 35D3C21F92BE for <sip-clf@ietf.org>; Thu,  1 Dec 2011 15:16:43 -0800 (PST)
Received: from [192.168.2.105] (pool-71-170-49-200.dllstx.fios.verizon.net [71.170.49.200]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id pB1NGfAe032943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Dec 2011 17:16:42 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <4EBBF988.1030100@bell-labs.com>
Date: Thu, 1 Dec 2011 17:16:41 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FFACD15-69E3-4B01-9CE7-CA6A15809EB8@nostrum.com>
References: <856A6315-BB66-4575-9EFB-8725A9278DC9@nostrum.com> <4EBBF988.1030100@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 71.170.49.200 is authenticated by a trusted mechanism)
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] AD review: draft-ietf-sipclf-problem-statement-07
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 23:16:48 -0000

Hi Vijay  -

Thanks for the updated draft - comments inline and at the end.

On Nov 10, 2011, at 10:19 AM, Vijay K. Gurbani wrote:

> On 08/04/2011 04:06 PM, Robert Sparks wrote:
>> Summary: There are a few issues to address before IETF LC
>=20
> Robert: Thank you for your extensive review and suggestions for
> cleaning up the document.  I apologize on attending to your
> comments after a delay, but nonetheless, please see inline
> for more discussions.
>=20
> I will submit a revision as soon as the blackout period for
> submitting new I-Ds is lifted on Nov-14.
>=20
> > 1) Shouldn't this document be titled something like "framework and
> > data model"?
>=20
> We could do so; however, here's a quick history on the draft ... it
> started off life as a problem statement plus solution rolled in one.
> As the work progressed on this, it was deemed more beneficial to
> address issues such as transport and a data model.  Then it was =
decided
> to spin off the representation format in at least one, possibly two,
> different drafts and have a framework-type approach specified in this =
draft.
>=20
> Through all this, the title of the draft remained as an artifact from
> its origins.  If you'd like me to change it to reflect the framework =
and
> data model part, I can easily do so.  I do not know whether changing =
the
> title of a draft midstream will cause any problems to the tools that
> track the draft, but if not, I have no problem changing the title.  As
> I understand it,the name of the draft must remain the same ---
> draft-ietf-sipclf-problem-statement.

It really should change to reflect what the draft really is.
It won't cause problems with the tools.
The filename (draft-ietf-sipclf-problem-statement) does not need to =
change.
Please issue a revision with this change.


>=20
> > 2) Why does this document talk about the 4096 byte limit? Shouldn't
> > this be moved to the encoding draft?
>=20
> The consensus to put a 4096 byte limit was reached during WG
> deliberations (see thread starting at [1]).  What was decided during
> this thread was that the problem-statement draft would mandate a
> 4096 byte limit on a SIP record, including bodies.  However, whether =
or
> not to log a complete body is left up to the specific representation
> draft.  Thus, this 4096 byte limit applies to the existing indexed-
> ASCII representation draft as well as any other representational
> draft that comes along.

So the answer is that this limit is part of the model.

>=20
> > 3) The presentation of requirements on devices that forward requests
> > and responses is under-documented. The notion of "UAS-half" is not
> > explained. Looking at what we ended up with for Table 1 from the
> > "new reader" perspective, I suggest that the document doesn't =
actually
> > need it. The whole section can be simplified with the details =
focusing
> > on handling R-RUI, Status, Server-Txn, and Client-Txn
>=20
> OK, fair enough.  I will adopt the text you had suggested in a =
follow-up
> email to the list [2], modified slightly to read as follows (this text
> will replace Table 1 in the current draft):
>=20
Here's a minor tweak (only a suggestion, feel free to ignore it):
Replace:

>  In the following cases, an element will not have an appropriate
>  value to provide for one of these fields, even though the field
>  itself is mandatory and must appear in the SIP CLF record.  For
>  these cases, the representation document MUST define how to
>  represent such "not applicable" values. =20

With:

An element will not always have an appropriate value to provide
for one of these fields, even when the field is required to appear
in the SIP CLF record. Therefore, the representation document
MUST define how to indicate a field is "not applicable".

> For example, the R-URI
>  field is not applicable when logging a response, the Status field
>  is not applicable when logging a request, the To-tag is not known
>  when a request is first sent out, etc.
>=20
>  The Client-Txn field is always applicable to a UAC.  The Server-
>  Txn field does not apply to a UAC unless the element is also
>  acting as a UAS, and the message associated to this log record
>  corresponds to a message handled by that UAS.  For instance,
>  a proxy forwarding a request will populate both the Client-Txn
>  and Server-Txn fields in the record corresponding to the
>  forwarded request
>=20
>  The Server-Txn field is always applicable to a UAS. The
>  Client-Txn field does not apply to a UAS unless the element is
>  also acting as a UAC, and the message associated to this log
>  record corresponds to a message handled by that UAC. For instance,
>  a proxy forwarding a response will populate both the Server-Txn
>  and Client-Txn fields in the record corresponding to the
>  forwarded response.  However, a proxy would only populate
>  the Client-Txn field when creating a log record corresponding
>  to a request.
>=20
> > 4) It is not sufficiently clear what it means when a record MUST
> > contain an element that is not applicable to the element. Are you
> > trying to say "Must be present with a non-empty value that is not a
> > valid value for the field"?
>=20
> Yes.
The edit you did for 3 clarified this sufficiently, thanks!
>=20
> > (If so, why does it have to be non-empty? The -format- document will
> > eventually need to explain why the group chose "-" there over the
> > empty string.)
>=20
> As to why we chose a "-" instead of an empty string --- having a
> printable character appear where an element would have normally
> appeared if it were present is visually helpful for the system
> operators who are observing the SIP CLF records on the screen.

>=20
> > 5) There is prose in the definition of the =46rom record field that
<snip/> The rest of this is great - thanks.

One last micro-nit - Can you tune the timestamps in the examples so
that you don't have "missing" retransmissions? For instance, in the
last example, you leave the CANCEL pending long enough that it
should have been resent.

RjS


From vkg@bell-labs.com  Fri Dec  2 09:57:45 2011
Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB7B51F0C76 for <sip-clf@ietfa.amsl.com>; Fri,  2 Dec 2011 09:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level: 
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P7HCzmMRNFtS for <sip-clf@ietfa.amsl.com>; Fri,  2 Dec 2011 09:57:45 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 41E091F0C36 for <sip-clf@ietf.org>; Fri,  2 Dec 2011 09:57:44 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pB2HvhbV005798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2011 11:57:43 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB2Hvh4W015643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Dec 2011 11:57:43 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id pB2HvgVG014400; Fri, 2 Dec 2011 11:57:43 -0600 (CST)
Message-ID: <4ED91262.8020808@bell-labs.com>
Date: Fri, 02 Dec 2011 12:01:06 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <856A6315-BB66-4575-9EFB-8725A9278DC9@nostrum.com> <4EBBF988.1030100@bell-labs.com> <1FFACD15-69E3-4B01-9CE7-CA6A15809EB8@nostrum.com>
In-Reply-To: <1FFACD15-69E3-4B01-9CE7-CA6A15809EB8@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] AD review: draft-ietf-sipclf-problem-statement-07
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 17:57:46 -0000

On 12/01/2011 05:16 PM, Robert Sparks wrote:
> Hi Vijay  -
>
> Thanks for the updated draft - comments inline and at the end.

Robert: Thanks for going through the draft; more inline.

> It really should change to reflect what the draft really is.
> It won't cause problems with the tools.
> The filename (draft-ietf-sipclf-problem-statement) does not need to change.
> Please issue a revision with this change.

Sure; I will do so in the next couple of days.

> Here's a minor tweak (only a suggestion, feel free to ignore it):
> Replace: [...]
>
> With: [...]

Sure; I will do so.

> One last micro-nit - Can you tune the timestamps in the examples so
> that you don't have "missing" retransmissions? For instance, in the
> last example, you leave the CANCEL pending long enough that it
> should have been resent.

Wow!  Now that is what I call a "close reading of the draft!"

Yes, sure; I will modify the timestamps of line 13 and 16 so
the difference is < 500ms.

I will issue a revision in the next couple of days with these changes.

Thanks, Robert.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From internet-drafts@ietf.org  Tue Dec  6 11:18:21 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88C721F84D6; Tue,  6 Dec 2011 11:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlgh7vftbtJw; Tue,  6 Dec 2011 11:18:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8257221F84A6; Tue,  6 Dec 2011 11:18:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111206191821.21562.48421.idtracker@ietfa.amsl.com>
Date: Tue, 06 Dec 2011 11:18:21 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action: draft-ietf-sipclf-problem-statement-09.txt
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 19:18:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the SIP Common Log Format Working Group o=
f the IETF.

	Title           : The Common Log Format (CLF) for the Session Initiation P=
rotocol (SIP): Framework and Data Model
	Author(s)       : Vijay K. Gurbani
                          Eric W. Burger
                          Tricha Anjali
                          Humberto Abdelnur
                          Olivier Festor
	Filename        : draft-ietf-sipclf-problem-statement-09.txt
	Pages           : 34
	Date            : 2011-12-06

   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 and produce reports and trends.
   Furthermore, these log files 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, and as a result, each server supports a distinct log format
   that makes it unnecessarily complex to produce tools to do trend
   analysis and security detection.  We propose a common log file format
   for SIP servers that can be used uniformly by user agents, proxies,
   registrars, redirect servers as well as back-to-back user agents.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-problem-statement-09.=
txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipclf-problem-statement-09.t=
xt


From vkg@bell-labs.com  Tue Dec  6 11:28:57 2011
Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258B221F84B4 for <sip-clf@ietfa.amsl.com>; Tue,  6 Dec 2011 11:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.457
X-Spam-Level: 
X-Spam-Status: No, score=-106.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntHAsdFcGVeX for <sip-clf@ietfa.amsl.com>; Tue,  6 Dec 2011 11:28:55 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF7E21F8A35 for <sip-clf@ietf.org>; Tue,  6 Dec 2011 11:28:55 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pB6JSsaU022690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sip-clf@ietf.org>; Tue, 6 Dec 2011 13:28:54 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pB6JSsGD003174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sip-clf@ietf.org>; Tue, 6 Dec 2011 13:28:54 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id pB6JSsoB022350 for <sip-clf@ietf.org>; Tue, 6 Dec 2011 13:28:54 -0600 (CST)
Message-ID: <4EDE6DC6.8070103@bell-labs.com>
Date: Tue, 06 Dec 2011 13:32:22 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: "sip-clf@ietf.org" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [sip-clf] Updated draft-ietf-sipclf-problem-statement-09
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 19:28:57 -0000

Folks: I have addressed the last set of nits Robert identified in
[1].  The new version (-09) is in the IETF archives [2], and
the diffs against -08 are at [3].

More specifically, (a) "Framework and Data Model" added as a subtitle,
(b) text suggested by Robert incorporated in page 12, (c) the timing
nits identified by Robert has been fixed.

[1] http://www.ietf.org/mail-archive/web/sip-clf/current/msg00517.html
[2] http://www.ietf.org/id/draft-ietf-sipclf-problem-statement-09.txt
[3] 
http://tools.ietf.org/rfcdiff?url2=draft-ietf-sipclf-problem-statement-09

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From iesg-secretary@ietf.org  Tue Dec  6 13:01:31 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6381F0C65; Tue,  6 Dec 2011 13:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KG+wQzIpVHbX; Tue,  6 Dec 2011 13:01:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D808B1F0C35; Tue,  6 Dec 2011 13:01:30 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111206210130.23030.58788.idtracker@ietfa.amsl.com>
Date: Tue, 06 Dec 2011 13:01:30 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-09.txt> (The Common	Log Format (CLF) for the Session Initiation Protocol (SIP):	Framework and Data Model) to Informational RFC
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 21:01:31 -0000

The IESG has received a request from the SIP Common Log Format WG
(sipclf) to consider the following document:
- 'The Common Log Format (CLF) for the Session Initiation Protocol (SIP):
   Framework and Data Model'
  <draft-ietf-sipclf-problem-statement-09.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-12-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   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 and produce reports and trends.
   Furthermore, these log files 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, and as a result, each server supports a distinct log format
   that makes it unnecessarily complex to produce tools to do trend
   analysis and security detection.  We propose a common log file format
   for SIP servers that can be used uniformly by user agents, proxies,
   registrars, redirect servers as well as back-to-back user agents.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sipclf-problem-statement/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sipclf-problem-statement/


No IPR declarations have been submitted directly on this I-D.



From musgravepj@gmail.com  Wed Dec  7 06:41:29 2011
Return-Path: <musgravepj@gmail.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C00E21F8B23 for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 06:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUHMNkjTrzSC for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 06:41:28 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF0721F8A91 for <sip-clf@ietf.org>; Wed,  7 Dec 2011 06:41:28 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so500785vcb.31 for <sip-clf@ietf.org>; Wed, 07 Dec 2011 06:41:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=EcbgrgNQjmhf3wbGdG2tnaH2E2W1snw8v/9dv5hklUI=; b=FqP8iFI7xV0pbFWcyJ9NQpK+U3tFP0xBucNV1lSRKq0WseIBxnITLYbexExHEHPj0C f8GPn1+Qjk9+HMIhVixUr7BclYoaGkDBalFfSLI58c13orhyUmll49OdLaQ3Aq/QblMc k37KFL8EKvLm9D6IHeoPsuTo3H68gaDFCprec=
Received: by 10.52.34.78 with SMTP id x14mr10739346vdi.122.1323268887753; Wed, 07 Dec 2011 06:41:27 -0800 (PST)
Received: from [192.168.1.109] ([204.237.37.240]) by mx.google.com with ESMTPS id c10sm1373979vdj.20.2011.12.07.06.41.26 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Dec 2011 06:41:27 -0800 (PST)
From: Peter Musgrave <musgravepj@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Dec 2011 09:41:25 -0500
Message-Id: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com>
To: sip-clf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [sip-clf] WG Last Call: draft-ietf-sipclf-format-03
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 14:41:29 -0000

Hi all,=20

I would like to start a WG last call on the recent (hopefully final) =
update to the sip-clf format doc.=20

Please provide your comments by Friday Dec. 16th - including just a =
simple "looks good".

I would really like to get this WG wrapped up in time for Xmas!

Regards,=20

Peter Musgrave=

From musgravepj@gmail.com  Wed Dec  7 07:03:09 2011
Return-Path: <musgravepj@gmail.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFBA521F8C2A for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 07:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRLdvg1RryAk for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 07:03:09 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 226BA21F8C15 for <sip-clf@ietf.org>; Wed,  7 Dec 2011 07:03:04 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so529109vbb.31 for <sip-clf@ietf.org>; Wed, 07 Dec 2011 07:03:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=aJ/tOmLJqsvlHSkiqG0QmmaofnfhHoappS+cQVEZM/Q=; b=A13KfShI2zcDc7LJ61ZJ5aZ2hCAN8lu3wbdBK8Ma7AFRdUUFjqR05vzYOHkvDhf39o HurVxPl4GhgtksFh+v5+FNxWZvz86q8LdrprOXcRLvB4bRxqAvzmADScNrm/9eyuza3E td1UM89pIFNO0PenPpKj4Rdu/L47Qha9qYtik=
Received: by 10.52.34.78 with SMTP id x14mr10809070vdi.122.1323270184442; Wed, 07 Dec 2011 07:03:04 -0800 (PST)
Received: from [192.168.1.109] ([204.237.37.240]) by mx.google.com with ESMTPS id ir2sm1460608vdb.9.2011.12.07.07.03.02 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Dec 2011 07:03:03 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <musgravepj@gmail.com>
In-Reply-To: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com>
Date: Wed, 7 Dec 2011 10:03:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E0AFFE0-29A3-4B24-8FB0-443ECA3BCE4C@gmail.com>
References: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] WG Last Call: draft-ietf-sipclf-format-03
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 15:03:09 -0000

Hi Gonzalo,=20

Great job on the final version. I have two comments, one picky; one more =
substantive:


4.2
For the timestamp and fractional seconds the order is most significant =
character first I assume? Is it worth stating this explicitly?

4.3
The optional fields have a 2 byte hex length indicator. It is stated =
earlier that hex is to be specified in ASCII characters. This limits the =
size of an optional value to 255 bytes - which I suspect was not the =
intent.
Does this field need to made large enough to hold 4096 byte lengths?

Thanks

Peter

On 2011-12-07, at 9:41 AM, Peter Musgrave wrote:

> Hi all,=20
>=20
> I would like to start a WG last call on the recent (hopefully final) =
update to the sip-clf format doc.=20
>=20
> Please provide your comments by Friday Dec. 16th - including just a =
simple "looks good".
>=20
> I would really like to get this WG wrapped up in time for Xmas!
>=20
> Regards,=20
>=20
> Peter Musgrave


From gsalguei@cisco.com  Wed Dec  7 10:10:41 2011
Return-Path: <gsalguei@cisco.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B0421F8B4E for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 10:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlBaeK9icmMJ for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 10:10:21 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 355FD21F8BCB for <sip-clf@ietf.org>; Wed,  7 Dec 2011 10:10:10 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pB7IA9q9023413 for <sip-clf@ietf.org>; Wed, 7 Dec 2011 13:10:09 -0500 (EST)
Received: from dhcp-64-102-210-155.cisco.com (dhcp-64-102-210-155.cisco.com [64.102.210.155]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pB7IA8UD020725; Wed, 7 Dec 2011 13:10:08 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-47--770658359
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <0E0AFFE0-29A3-4B24-8FB0-443ECA3BCE4C@gmail.com>
Date: Wed, 7 Dec 2011 13:10:08 -0500
Message-Id: <867FAA7E-B3D4-4F53-A7C1-B3088C4CD67F@cisco.com>
References: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com> <0E0AFFE0-29A3-4B24-8FB0-443ECA3BCE4C@gmail.com>
To: Peter Musgrave <musgravepj@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] WG Last Call: draft-ietf-sipclf-format-03
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 18:10:41 -0000

--Apple-Mail-47--770658359
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Peter -=20

Thanks for the review. A few comments inline...

On Dec 7, 2011, at 10:03 AM, Peter Musgrave wrote:

> Hi Gonzalo,=20
>=20
> Great job on the final version. I have two comments, one picky; one =
more substantive:
>=20
>=20
> 4.2
> For the timestamp and fractional seconds the order is most significant =
character first I assume? Is it worth stating this explicitly?
>=20
Once we specified that Unix Epoch time is used that this would be =
understood, but I think a bit of text stating that this explicitly could =
be helpful. I will add this in the next version.
> 4.3
> The optional fields have a 2 byte hex length indicator. It is stated =
earlier that hex is to be specified in ASCII characters. This limits the =
size of an optional value to 255 bytes - which I suspect was not the =
intent.
> Does this field need to made large enough to hold 4096 byte lengths?
>=20
Thanks for spotting this. It was an oversight on my part and this will =
definitely be addressed in the next version with updated field length of =
4 bytes.

Regards,

Gonzalo

> Thanks
>=20
> Peter
>=20
> On 2011-12-07, at 9:41 AM, Peter Musgrave wrote:
>=20
>> Hi all,=20
>>=20
>> I would like to start a WG last call on the recent (hopefully final) =
update to the sip-clf format doc.=20
>>=20
>> Please provide your comments by Friday Dec. 16th - including just a =
simple "looks good".
>>=20
>> I would really like to get this WG wrapped up in time for Xmas!
>>=20
>> Regards,=20
>>=20
>> Peter Musgrave
>=20
>=20


--Apple-Mail-47--770658359
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Peter =
-&nbsp;<div><br></div><div>Thanks for the review. A few comments =
inline...<br><div><br><div><div>On Dec 7, 2011, at 10:03 AM, Peter =
Musgrave wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi Gonzalo, <br><br>Great job on the final version. I =
have two comments, one picky; one more =
substantive:<br><br><br>4.2<br>For the timestamp and fractional seconds =
the order is most significant character first I assume? Is it worth =
stating this explicitly?<br><br></div></blockquote>Once we specified =
that Unix Epoch time is used that this would be understood, but I think =
a bit of text stating that this explicitly could be helpful. I will add =
this in the next version.<br><blockquote type=3D"cite"><div>4.3<br>The =
optional fields have a 2 byte hex length indicator. It is stated earlier =
that hex is to be specified in ASCII characters. This limits the size of =
an optional value to 255 bytes - which I suspect was not the =
intent.<br>Does this field need to made large enough to hold 4096 byte =
lengths?<br><br></div></blockquote>Thanks for spotting this. It was an =
oversight on my part and this will definitely be addressed in the next =
version with updated field length of 4 =
bytes.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo<=
/div><div><br><blockquote type=3D"cite"><div>Thanks<br><br>Peter<br><br>On=
 2011-12-07, at 9:41 AM, Peter Musgrave wrote:<br><br><blockquote =
type=3D"cite">Hi all, <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
start a WG last call on the recent (hopefully final) update to the =
sip-clf format doc. <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Please provide =
your comments by Friday Dec. 16th - including just a simple "looks =
good".<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would really =
like to get this WG wrapped up in time for =
Xmas!<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Regards, =
<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Peter =
Musgrave<br></blockquote><br><br></div></blockquote></div><br></div></div>=
</body></html>=

--Apple-Mail-47--770658359--

From internet-drafts@ietf.org  Wed Dec  7 11:19:02 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5287321F8BBC; Wed,  7 Dec 2011 11:19:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37yS+3rep5JN; Wed,  7 Dec 2011 11:19:01 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E24F221F8B95; Wed,  7 Dec 2011 11:19:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111207191901.31407.2572.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2011 11:19:01 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action: draft-ietf-sipclf-format-04.txt
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 19:19:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the SIP Common Log Format Working Group o=
f the IETF.

	Title           : Format for the Session Initiation Protocol (SIP) Common =
Log Format (CLF)
	Author(s)       : Gonzalo Salgueiro
                          Vijay Gurbani
                          Adam Roach
	Filename        : draft-ietf-sipclf-format-04.txt
	Pages           : 26
	Date            : 2011-12-07

   The SIPCLF Workgroup has defined a common log format framework for
   Session Initiation Protocol (SIP) servers.  This common log format
   mimics the wildly successful event logging mechanism found in well-
   known web servers like Apache and web proxies like Squid.  This
   document proposes an indexed text encoding format for the SIP Common
   Log Format (CLF) that retains the key advantages of a text-based
   format, while significantly increasing processing performance over a
   purely text-based implementation.  This file format adheres to the
   SIP CLF data model and provides an effective encoding scheme for all
   mandatory and optional fields that appear in a SIP CLF record.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-format-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipclf-format-04.txt


From gsalguei@cisco.com  Wed Dec  7 11:35:33 2011
Return-Path: <gsalguei@cisco.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2D7C11E80B3 for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 11:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAMOTQ2OHyku for <sip-clf@ietfa.amsl.com>; Wed,  7 Dec 2011 11:35:33 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7EE11E80B4 for <sip-clf@ietf.org>; Wed,  7 Dec 2011 11:35:33 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pB7JZWV0001713 for <sip-clf@ietf.org>; Wed, 7 Dec 2011 14:35:32 -0500 (EST)
Received: from dhcp-64-102-210-155.cisco.com (dhcp-64-102-210-155.cisco.com [64.102.210.155]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pB7JZVs7011887; Wed, 7 Dec 2011 14:35:31 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-51--765535376
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com>
Date: Wed, 7 Dec 2011 14:35:31 -0500
Message-Id: <BF7A1BD5-B112-4AE7-ADEA-62DE6490355F@cisco.com>
References: <6B7FE711-B51A-4166-90A2-E9ADE5DB2982@gmail.com>
To: Peter Musgrave <musgravepj@gmail.com>, "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [sip-clf] WG Last Call: draft-ietf-sipclf-format-03
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 19:35:33 -0000

--Apple-Mail-51--765535376
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Folks -=20

To help expedite this I have addressed the two issues Peter raised in =
his review. =20
The new version (-04) is in the IETF archives [1], and the diffs against =
-03 are at [2].

Specifically, these changes are:

(a) Added text to indicate Timestamp is most significant octet first
(b) Updated Optional Field Length to be 4 bytes to allow for fields of =
up to 4096 bytes.

[1] http://tools.ietf.org/html/draft-ietf-sipclf-format-04
[2] http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-04.txt

Thanks,

- Gonzalo

On Dec 7, 2011, at 9:41 AM, Peter Musgrave wrote:

> Hi all,=20
>=20
> I would like to start a WG last call on the recent (hopefully final) =
update to the sip-clf format doc.=20
>=20
> Please provide your comments by Friday Dec. 16th - including just a =
simple "looks good".
>=20
> I would really like to get this WG wrapped up in time for Xmas!
>=20
> Regards,=20
>=20
> Peter Musgrave
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>=20


--Apple-Mail-51--765535376
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Folks =
-&nbsp;<div><br></div><div>To help expedite this I have addressed the =
two issues Peter raised in his review. &nbsp;</div><div>The new version =
(-04) is in the IETF archives [1], and&nbsp;the diffs against -03 are at =
[2].</div><div><br>Specifically, these changes =
are:</div><div><br></div><div>(a) Added text to indicate Timestamp is =
most significant octet first<br>(b) Updated Optional Field Length to be =
4 bytes to allow for fields of up to 4096 bytes.<br><br>[1]&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-sipclf-format-04">http://too=
ls.ietf.org/html/draft-ietf-sipclf-format-04</a><br>[2]&nbsp;<a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-04.t=
xt">http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-04.txt</=
a><br><br>Thanks,<br><br>- Gonzalo</div><div><br><div><div>On Dec 7, =
2011, at 9:41 AM, Peter Musgrave wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi =
all, <br><br>I would like to start a WG last call on the recent =
(hopefully final) update to the sip-clf format doc. <br><br>Please =
provide your comments by Friday Dec. 16th - including just a simple =
"looks good".<br><br>I would really like to get this WG wrapped up in =
time for Xmas!<br><br>Regards, <br><br>Peter =
Musgrave<br>_______________________________________________<br>sip-clf =
mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br><br></div></blockquote></div><br></div></b=
ody></html>=

--Apple-Mail-51--765535376--

From internet-drafts@ietf.org  Sat Dec 17 14:10:13 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D7521F8B14; Sat, 17 Dec 2011 14:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0dcydon0I0a; Sat, 17 Dec 2011 14:10:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6372D21F8B0D; Sat, 17 Dec 2011 14:10:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111217221004.19229.1918.idtracker@ietfa.amsl.com>
Date: Sat, 17 Dec 2011 14:10:04 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action: draft-ietf-sipclf-format-05.txt
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Dec 2011 22:10:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the SIP Common Log Format Working Group o=
f the IETF.

	Title           : Format for the Session Initiation Protocol (SIP) Common =
Log Format (CLF)
	Author(s)       : Gonzalo Salgueiro
                          Vijay Gurbani
                          Adam Roach
	Filename        : draft-ietf-sipclf-format-05.txt
	Pages           : 27
	Date            : 2011-12-17

   The SIPCLF Workgroup has defined a common log format framework for
   Session Initiation Protocol (SIP) servers.  This common log format
   mimics the successful event logging format found in well-known web
   servers like Apache and web proxies like Squid.  This document
   proposes an indexed text encoding format for the SIP Common Log
   Format (CLF) that retains the key advantages of a text-based format,
   while significantly increasing processing performance over a purely
   text-based implementation.  This file format adheres to the SIP CLF
   data model and provides an effective encoding scheme for all
   mandatory and optional fields that appear in a SIP CLF record.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-format-05.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sipclf-format-05.txt


From gsalguei@cisco.com  Sat Dec 17 14:29:16 2011
Return-Path: <gsalguei@cisco.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD3921F8510 for <sip-clf@ietfa.amsl.com>; Sat, 17 Dec 2011 14:29:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QTG7lGoEK5T for <sip-clf@ietfa.amsl.com>; Sat, 17 Dec 2011 14:29:16 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 5379A21F8507 for <sip-clf@ietf.org>; Sat, 17 Dec 2011 14:29:16 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pBHMTEgs008953 for <sip-clf@ietf.org>; Sat, 17 Dec 2011 17:29:15 -0500 (EST)
Received: from rtp-gsalguei-8715.cisco.com (rtp-gsalguei-8715.cisco.com [10.116.61.54]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pBHMTBkK010776; Sat, 17 Dec 2011 17:29:11 -0500 (EST)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-117-108884686
Date: Sat, 17 Dec 2011 17:29:11 -0500
Message-Id: <5A0FC90E-29D6-4905-A54F-8AD0CEAFAE2B@cisco.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [sip-clf] Updated draft-ietf-sipclf-format-05
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Dec 2011 22:29:17 -0000

--Apple-Mail-117-108884686
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Folks -=20

I have released a new version of the SIPCLF format draft based on the =
WGLC comments received. =20
The new version (-05) is in the IETF archives [1], and the diffs against =
-04 are at [2].

Specifically, these changes are:

(a) Variety of nits cleaning up the text
(b) Updated the text referencing Table 1 of Section 8.2 in the Problem =
Statement draft (Note: it was removed after AD review)
(c) Added a Perl script to decode the Base64 encoded text

[1] http://tools.ietf.org/html/draft-ietf-sipclf-format-05
[2] http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-05.txt

Thanks,

- Gonzalo


--Apple-Mail-117-108884686
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Folks =
-&nbsp;<div><br></div><div>I have released a new version of the SIPCLF =
format draft based on the WGLC comments received. &nbsp;</div><div>The =
new version (-05) is in the IETF archives [1], and&nbsp;the diffs =
against -04 are at [2].</div><div><br>Specifically, these changes =
are:</div><div><br></div><div>(a) Variety of nits cleaning up the =
text<br>(b) Updated the text referencing Table 1 of Section 8.2 in the =
Problem Statement draft (Note: it was removed after AD =
review)</div><div>(c) Added a Perl script to decode the Base64 encoded =
text<br><br>[1]&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-sipclf-format-05"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-sipclf-format-0">http://tool=
s.ietf.org/html/draft-ietf-sipclf-format-0</a>5</a><br>[2]&nbsp;<a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-05.t=
xt">http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipclf-format-05.txt</=
a><br><br>Thanks,<br><br>- Gonzalo</div><div><br></div></body></html>=

--Apple-Mail-117-108884686--

From musgravepj@gmail.com  Sat Dec 31 06:21:47 2011
Return-Path: <musgravepj@gmail.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11BA21F845F; Sat, 31 Dec 2011 06:21:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0A4bs-W1aij; Sat, 31 Dec 2011 06:21:46 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4A62021F844E; Sat, 31 Dec 2011 06:21:46 -0800 (PST)
Received: by qadz3 with SMTP id z3so9539817qad.10 for <multiple recipients>; Sat, 31 Dec 2011 06:21:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:cc:to:mime-version :x-mailer; bh=saaA4FjkAEkjzu4rWef69pyQJGwz1vPiNLewk6lzRnk=; b=UvY3JlG/zv2pebHZWv02lnKDEaK4qbaXZWS/OjA56GdujMOInSMB38cjG9gvdIHqhK jWCj+cLyWW1DHdWgdlrkMQrN+hhGoaF48cxQNC+ou1Ih9y64iL5vwlxwSX44Q3n3E+LV tiQYFd9L/horlwoeBI/45jG0Qy45yT4ZBwBKA=
Received: by 10.224.203.67 with SMTP id fh3mr48789181qab.13.1325341304735; Sat, 31 Dec 2011 06:21:44 -0800 (PST)
Received: from [192.168.1.105] ([204.237.33.112]) by mx.google.com with ESMTPS id gw5sm51720500qab.11.2011.12.31.06.21.41 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 31 Dec 2011 06:21:43 -0800 (PST)
From: Peter Musgrave <musgravepj@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--858250243
Date: Sat, 31 Dec 2011 09:21:40 -0500
Message-Id: <935A83F4-8DCA-4CC8-B8C8-D6CF1133E797@gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>, iesg-secretary@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: sip-clf@ietf.org
Subject: [sip-clf] Pub Req. for draft-ietf-sipclf-format-05
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Dec 2011 14:21:48 -0000

--Apple-Mail-1--858250243
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

draft-ietf-sipclf-format-05

(1.a) Who is the Document Shepherd for this document? Has the
        Document Shepherd personally reviewed this version of the=20
        document and, in particular, does he or she believe this=20
        version is ready for forwarding to the IESG for publication?=20
Peter Musgrave is the document shepherd. He has read this version and =
believes it is ready for publication.

  (1.b) Has the document had adequate review both from key WG members=20
        and from key non-WG members? Does the Document Shepherd have=20
        any concerns about the depth or breadth of the reviews that=20
        have been performed? =20
The document has had adequate review from key members of the WG as well =
as members active in SIP and IPFIX WGs.=20

  (1.c) Does the Document Shepherd have concerns that the document=20
        needs more review from a particular or broader perspective,=20
        e.g., security, operational complexity, someone familiar with=20
        AAA, internationalization or XML?=20
No.

  (1.d) Does the Document Shepherd have any specific concerns or=20
        issues with this document that the Responsible Area Director
        and/or the IESG should be aware of? For example, perhaps he=20
        or she is uncomfortable with certain parts of the document, or=20=

        has concerns whether there really is a need for it. In any=20
        event, if the WG has discussed those issues and has indicated=20
        that it still wishes to advance the document, detail those=20
        concerns here. Has an IPR disclosure related to this document=20
        been filed? If so, please include a reference to the=20
        disclosure and summarize the WG discussion and conclusion on=20
        this issue.=20
There are no specific concerns.
There are no IPR disclosures for this document.

  (1.e) How solid is the WG consensus behind this document? Does it=20
        represent the strong concurrence of a few individuals, with=20
        others being silent, or does the WG as a whole understand and=20
        agree with it?  =20
The WG as a whole has accepted this document as a reasonable format. =
Historically the WG considered
two approaches - the text based format described here and a binary =
format motivated by the desire to=20
stream to an IPFIX logging entity. This stalled progress in the WG for =
some time. Eventually the WG
was persuaded that for a file logging format in the SIPCLF charter the =
text format met the needs and that
the datamodel developed could be used as the basis for specifying a =
binary log streaming format within the
IPFIX community if there was sufficient interest in doing so.=20

Since this decision there has not been any contrary statements made =
during the last several review cycles of this document.=20

  (1.f) Has anyone threatened an appeal or otherwise indicated extreme=20=

        discontent? If so, please summarise the areas of conflict in=20
        separate email messages to the Responsible Area Director. (It=20
        should be in a separate email because this questionnaire is=20
        entered into the ID Tracker.)=20
No.

  (1.g) Has the Document Shepherd personally verified that the=20
        document satisfies all ID nits? (See the Internet-Drafts =
Checklist=20
        and http://tools.ietf.org/tools/idnits/). Boilerplate checks are=20=

        not enough; this check needs to be thorough. Has the document=20
        met all formal review criteria it needs to, such as the MIB=20
        Doctor, media type and URI type reviews?=20
There is one NIT error (normative reference to the problem statement) =
that can be resolved when there is an
RFC number for the problem statement.=20

One reference is reported as unused - even though the reference is on =
page 21 and appears properly formatted.

  (1.h) Has the document split its references into normative and=20
        informative? Are there normative references to documents that=20
        are not ready for advancement or are otherwise in an unclear=20
        state? If such normative references exist, what is the=20
        strategy for their completion? Are there normative references=20
        that are downward references, as described in [RFC3967]? If=20
        so, list these downward references to support the Area=20
        Director in the Last Call procedure for them [RFC3967].=20
See comment about NIT error above.

  (1.i) Has the Document Shepherd verified that the document IANA=20
        consideration section exists and is consistent with the body=20
        of the document? If the document specifies protocol=20
        extensions, are reservations requested in appropriate IANA=20
        registries? Are the IANA registries clearly identified? If=20
        the document creates a new registry, does it define the=20
        proposed initial contents of the registry and an allocation=20
        procedure for future registrations? Does it suggest a=20
        reasonable name for the new registry? See [RFC5226]. If the=20
        document describes an Expert Review process has Shepherd=20
        conferred with the Responsible Area Director so that the IESG=20
        can appoint the needed Expert during the IESG Evaluation?=20
Yes.

  (1.j) Has the Document Shepherd verified that sections of the=20
        document that are written in a formal language, such as XML=20
        code, BNF rules, MIB definitions, etc., validate correctly in=20
        an automated checker?=20
Not applicable.

  (1.k) The IESG approval announcement includes a Document=20
        Announcement Write-Up. Please provide such a Document=20
        Announcement Write-Up? Recent examples can be found in the
        "Action" announcements for approved documents. The approval=20
        announcement contains the following sections:=20

     Technical Summary=20
        The document describes a standard indexed ASCII format for the =
logging of SIP messages
        sent and received by a SIP entity. The format adheres to the =
SIPCLF data model defined by
        [insert RFC reference]. The format is fully extensible as it =
provides a mechanism for=20
        logging any optional element, including vendor specific =
extensions to allow it to be=20
        tailored to the needs of specific implementations.=20

     Working Group Summary=20
        The WG debated the relative merits of ASCII versus binary =
encoding of logging
        information. This was primarily a debate from people who wanted =
to use IPFIX
        style logging servers versus those who wanted to use text based =
log tools and
        scripts. =20

     Document Quality=20
        There were two implementations of the sipclf logging format. =
These implementors=20
        helped find areas in earlier drafts where details were =
incomplete or ambiguous.=20


--Apple-Mail-1--858250243
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p =
style=3D"margin: 0.0px 0.0px 1.0px 56.0px; text-indent: -56.0px; font: =
12.0px Helvetica"><b>draft-ietf-sipclf-format-05</b></p><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
min-height: 16px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">(1.a) Who is the Document Shepherd =
for this document? Has the</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
Document Shepherd personally reviewed this version of =
the&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; document and, in =
particular, does he or she believe this&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; version is ready for forwarding to the =
IESG for publication?&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">Peter Musgrave is the document =
shepherd. He has read this version and believes it is ready for =
publication.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.b) Has the document had adequate review both from key WG =
members&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; and from key non-WG =
members? Does the Document Shepherd have&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; any concerns about the depth or breadth of =
the reviews that&nbsp;</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; have been performed? =
&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">The document has had adequate review from key =
members of the WG as well as members active in SIP and IPFIX =
WGs.&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.c) Does the Document Shepherd have concerns that the =
document&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; needs more review =
from a particular or broader perspective,&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; e.g., security, operational complexity, =
someone familiar with&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; AAA, =
internationalization or XML?&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">No.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; min-height: 16px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; (1.d) Does the Document Shepherd have any =
specific concerns or&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; issues =
with this document that the Responsible Area Director</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; and/or the IESG should be aware of? For =
example, perhaps he&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; or she =
is uncomfortable with certain parts of the document, or&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; has concerns whether there really is a =
need for it. In any&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; event, =
if the WG has discussed those issues and has indicated&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; that it still wishes to advance the =
document, detail those&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
concerns here. Has an IPR disclosure related to this =
document&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; been filed? If so, =
please include a reference to the&nbsp;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
disclosure and summarize the WG discussion and conclusion =
on&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; this =
issue.&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">There are no specific concerns.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">There are no IPR disclosures for this document.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
min-height: 16px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; (1.e) How solid is the WG =
consensus behind this document? Does it&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; represent the strong concurrence of a few =
individuals, with&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; others =
being silent, or does the WG as a whole understand and&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; agree with it?&nbsp; &nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; ">The =
WG as a whole has accepted this document as a reasonable format. =
Historically the WG considered</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">two approaches - the text based =
format described here and a binary format motivated by the desire =
to&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">stream to an IPFIX logging entity. This stalled =
progress in the WG for some time. Eventually the WG</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; ">was =
persuaded that for a file logging format in the SIPCLF charter the text =
format met the needs and that</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">the datamodel developed could be =
used as the basis for specifying a binary log streaming format within =
the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">IPFIX community if there was sufficient interest =
in doing so.&nbsp;</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">Since this decision there has not been any contrary statements made =
during the last several review cycles of this document.&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
min-height: 16px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; (1.f) Has anyone threatened =
an appeal or otherwise indicated extreme&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; discontent? If so, please summarise the =
areas of conflict in&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
separate email messages to the Responsible Area Director. =
(It&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; should be in a =
separate email because this questionnaire is&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; entered into the ID =
Tracker.)&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">No.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.g) Has the Document Shepherd personally verified that =
the&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; document satisfies =
all ID nits? (See the <a =
href=3D"http://www.ietf.org/id-info/checklist.html"><span =
style=3D"text-decoration: underline ; color: #1a37ee">Internet-Drafts =
Checklist</span></a>&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; and <a =
href=3D"http://tools.ietf.org/tools/idnits/"><span =
style=3D"text-decoration: underline ; color: =
#1a37ee">http://tools.ietf.org/tools/idnits/</span></a>). Boilerplate =
checks are&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; not enough; this =
check needs to be thorough. Has the document&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; met all formal review criteria it needs =
to, such as the MIB&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; Doctor, =
media type and URI type reviews?&nbsp;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; ">There is one NIT error =
(normative reference to the problem statement) that can be resolved when =
there is an</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">RFC number for the problem =
statement.&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; ">One =
reference is reported as unused - even though the reference is on page =
21 and appears properly formatted.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.h) Has the document split its references into normative =
and&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; informative? Are =
there normative references to documents that&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; are not ready for advancement or are =
otherwise in an unclear&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; state? =
If such normative references exist, what is the&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; strategy for their completion? Are there =
normative references&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; that =
are downward references, as described in [RFC3967]? If&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; so, list these downward references to =
support the Area&nbsp;</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; Director in the Last =
Call procedure for them [RFC3967].&nbsp;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; ">See comment about NIT error =
above.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.i) Has the Document Shepherd verified that the document =
IANA&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; consideration section =
exists and is consistent with the body&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; of the document? If the document specifies =
protocol&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; extensions, are =
reservations requested in appropriate IANA&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; registries? Are the IANA registries =
clearly identified? If&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; the =
document creates a new registry, does it define the&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; proposed initial contents of the registry =
and an allocation&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
procedure for future registrations? Does it suggest a&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; reasonable name for the new registry? See =
[RFC5226]. If the&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
document describes an Expert Review process has Shepherd&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; conferred with the Responsible Area =
Director so that the IESG&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; can =
appoint the needed Expert during the IESG Evaluation?&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">Yes.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; (1.j) Has the Document Shepherd verified that sections of =
the&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; document that are =
written in a formal language, such as XML&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; code, BNF rules, MIB definitions, etc., =
validate correctly in&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; an =
automated checker?&nbsp;</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">Not applicable.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
min-height: 16px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp; (1.k) The IESG approval =
announcement includes a Document&nbsp;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
Announcement Write-Up. Please provide such a Document&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; Announcement Write-Up? Recent examples can =
be found in the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; "Action" =
announcements for approved documents. The approval&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; announcement contains the following =
sections:&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp;&nbsp; &nbsp; Technical Summary&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; The document describes a standard indexed =
ASCII format for the logging of SIP messages</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; sent and received by a SIP entity. The =
format adheres to the SIPCLF data model defined by</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; [insert RFC reference]. The format is =
fully extensible as it provides a mechanism for&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; logging any optional element, including =
vendor specific extensions to allow it&nbsp;to be&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; tailored to the needs of specific =
implementations.&nbsp;</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; min-height: 16px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp;&nbsp; &nbsp; Working Group Summary&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; The WG debated the relative merits of =
ASCII versus binary encoding of logging</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; =
information. This was primarily a debate from people who wanted to use =
IPFIX</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; style logging servers =
versus those who wanted to use text based log tools and</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
">&nbsp; &nbsp; &nbsp; &nbsp; scripts. &nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 13px/normal Courier; =
min-height: 16px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 13px/normal Courier; ">&nbsp;&nbsp; &nbsp; Document =
Quality&nbsp;</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; There were two =
implementations of the sipclf logging format. These =
implementors&nbsp;</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
13px/normal Courier; ">&nbsp; &nbsp; &nbsp; &nbsp; helped find areas in =
earlier drafts where details were incomplete or =
ambiguous.&nbsp;</div><div><br></div></body></html>=

--Apple-Mail-1--858250243--
