Re: [OPSEC] minutes part 3 (action items)

Joel Jaeggli <joelja@bogus.com> Tue, 23 December 2008 19:32 UTC

Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6A1B3A67D0; Tue, 23 Dec 2008 11:32:30 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12C313A67D0 for <opsec@core3.amsl.com>; Tue, 23 Dec 2008 11:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 ngq10-lpMdKG for <opsec@core3.amsl.com>; Tue, 23 Dec 2008 11:32:29 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id E7E373A6452 for <opsec@ietf.org>; Tue, 23 Dec 2008 11:32:28 -0800 (PST)
Received: from [192.168.11.143] (c-67-171-158-173.hsd1.wa.comcast.net [67.171.158.173]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id mBNJWEgP025589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Dec 2008 19:32:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <49513CBD.9080508@bogus.com>
Date: Tue, 23 Dec 2008 11:32:13 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081119)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
References: <494470BF.3030901@bogus.com> <200812210635.mBL6ZRdn024994@venus.xmundo.net>
In-Reply-To: <200812210635.mBL6ZRdn024994@venus.xmundo.net>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: ClamAV 0.93.3/8795/Tue Dec 23 17:58:21 2008 on nagasaki.bogus.com
X-Virus-Status: Clean
Cc: opsec wg mailing list <opsec@ietf.org>
Subject: Re: [OPSEC] minutes part 3 (action items)
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org

Fernando Gont wrote:
> At 11:34 p.m. 13/12/2008, Joel Jaeggli wrote:
> 
>> * draft-gont-opsec-ip-security-01
>>
>>         Test consensus on list for accepting as a working group document
>>
>>
>>         Preference for desired outcome, informational or BCP?
>>
>>         Venues for cross area review, where should we socialize it
>>
>>                 Are there specifica areas that should get special
>>                 attention?
> 
> I believe the high-order bit for action items relevant to this document
> is to test for consensus on list for accepting this document as a
> working group document. I guess that once we are working on this
> document, we can more formally ask for cross-area review.

agree

> This does not contradict with what you posted... I'm just saying that we
> should probably pursue the action items for this document in the order
> you stated them. That is, first check for consensus for accepting this
> doc as a wg item, then discuss preference for the desired outcome, and
> then discuss how we could implement the cross area review.
> 
> 
> 
>> * draft-gont-opsec-icmp-filtering-00
>>
>>         Are we concluded that feedback on structure provided during the
>>         wg meeting was sufficient to proceed?
> 
> I had asked this one the mailing-list already, and the feedback I got at
> the Minneapolis meeting didn't argue for a change in the structure of
> the document. So the document will continue "as is".

my opinion as well

> 
>>         Seperate v6 document or not
> 
> I will got back to the comments I had received on the v6 stuff. However,
> as I mentioned at the meeting, the high order bit was to agree on the
> structure of the document, as this would affect both the v4 and the
> possible v6 stuff. I will come back with some concrete
> proposals/alternatives for the v6 stuff asap, now that we have agreed on
> the most basic issue that was the structure of the whole document.

I believe the question is does much of what we could address for icmp6
carry the same weight of operational experience that we have with ipv4
icmp messages?

> Thanks!
> 
> Kind regards,
> 
> -- 
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 
> 

_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec