Re: [sip-clf] Proposed threat model for SIP CLF

"Spencer Dawkins" <spencer@wonderhamster.org> Tue, 30 March 2010 18:20 UTC

Return-Path: <spencer@wonderhamster.org>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63D663A6842 for <sip-clf@core3.amsl.com>; Tue, 30 Mar 2010 11:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 6qSnh3eVOcAZ for <sip-clf@core3.amsl.com>; Tue, 30 Mar 2010 11:20:58 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 8B7563A6A9A for <sip-clf@ietf.org>; Tue, 30 Mar 2010 11:20:55 -0700 (PDT)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MTjeS-1O5RVQ1Pvs-00QWbo; Tue, 30 Mar 2010 14:21:23 -0400
Message-ID: <EDEA9EF143C340B0A35A530EA4FF4648@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, Chris Lonvick <clonvick@cisco.com>
References: <Pine.GSO.4.63.1003271739350.14383@sjc-cde-011.cisco.com> <4BAF7692.2050206@bell-labs.com>
Date: Tue, 30 Mar 2010 13:21:04 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX18e44XtYRgC8MVwme4f6a2oGbUIFqAf4yImVtS OOlhqQDryHuFHDYvSkup7U1DqkXVvMURcmDG6Lh6hAd18ZRrCg 42Esx4DV0AoJ7vwAyFXu29VuTGhEhJlpZ0tHSFBLMw=
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] Proposed threat model for SIP CLF
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Mar 2010 18:20:59 -0000

Chris,

I'd like to echo Vijay's thanks for this suggested text.

I had a chat on the way out of the room on Friday morning about whether we 
might also want to say anything about whether we expect implementations to 
truncate log files from the beginning or the end, when a SIP node runs out 
of log space. There probably are other operational things we need to say 
about the work we're chartered to do, too ;-)

Spencer


> On 03/27/2010 08:15 PM, Chris Lonvick wrote:
>> Hi,
>>
>> I discussed having a threat model for the SIP CLF file in the WG
>> meeting. I whipped this up on the flight home.
> [...]
>
> Chris: The write-up is eminently reasonable.  I will include
> it in the next revision of the sipclf-problem-statement draft.
>
> Thank you for your time on the suggested text.
>
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> Web:   http://ect.bell-labs.com/who/vkg/
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf