Re: [OPSEC] Fwd: ID Tracker State Update Notice: <draft-ietf-opsec-protect-control-plane-06.txt>
Joel Jaeggli <joelja@bogus.com> Sun, 09 January 2011 16:42 UTC
Return-Path: <joelja@bogus.com>
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 E3BC63A6813 for <opsec@core3.amsl.com>; Sun, 9 Jan 2011 08:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.607
X-Spam-Level:
X-Spam-Status: No, score=-101.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
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 Oe2YvZ6XDU8W for <opsec@core3.amsl.com>; Sun, 9 Jan 2011 08:42:14 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id B9F0F3A6812 for <opsec@ietf.org>; Sun, 9 Jan 2011 08:42:13 -0800 (PST)
Received: from 58b035843c84.netpoint.com ([213.221.117.228]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p09Gi7Pg057666 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 9 Jan 2011 16:44:18 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D2933D7.5050105@bogus.com>
Date: Sat, 08 Jan 2011 20:04:39 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <20101223193418.26547.34582.idtracker@localhost> <64E1A73D-2221-4035-8E77-79A6515A0DC3@kumari.net> <20110104092257.2ff16390@t61p> <AANLkTikb2SO2pPXYdKzA8y2ar0P9LRri=mqMqQLcPezn@mail.gmail.com>
In-Reply-To: <AANLkTikb2SO2pPXYdKzA8y2ar0P9LRri=mqMqQLcPezn@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "opsec@ietf.org mailing list" <opsec@ietf.org>, Warren Kumari <warren@kumari.net>
Subject: Re: [OPSEC] Fwd: ID Tracker State Update Notice: <draft-ietf-opsec-protect-control-plane-06.txt>
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/mail-archive/web/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>
X-List-Received-Date: Sun, 09 Jan 2011 16:42:15 -0000
On 1/5/11 5:48 PM, Christopher Morrow wrote: > On Tue, Jan 4, 2011 at 10:22 AM, John Kristoff <jtk@cymru.com> wrote: >> On Thu, 23 Dec 2010 15:22:22 -0500 >> Warren Kumari <warren@kumari.net> wrote: >> >>> So, our active queue is beginning to look very sparse... I have a >>> draft that I started writing a while ago that Chris Morrow and Danny >>> McPherson have agreed to fix / update (poke...), does anyone have >>> anything else that they are working on? >> >> I had started a port filtering draft. A second revision has been >> started, but we haven't spent much time on it lately. I can endeavor >> to get this work going again this week. >> >> <http://tools.ietf.org/html/draft-kristoff-opsec-port-filtering-00> > > I hate to a) sign up for work, b) beat a horsey carcass, but... there > is/was a filtering capabilities draft that made it to IESG review, > then the author(s) (me mostly) ran out of time to work on it. I can > dust that off, re-submit it and get the comments addressed if it'd > help? speaking as the guy who removed the caps documents from the charter. I think there was a lack of stomach for the work that would have taken a completed capabiliteis document and matched it with a product development cycle and produced the router/firewall etc... That said operational recomendations on port filtering sounds like a worthwhile activity. > -Chris > (I happen to believe in the purpose/need for the draft, but a job > change and work took away ietf time from me) > _______________________________________________ > OPSEC mailing list > OPSEC@ietf.org > https://www.ietf.org/mailman/listinfo/opsec >
- [OPSEC] Fwd: ID Tracker State Update Notice: <dra… Warren Kumari
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Joel Jaeggli
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … George Jones
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … John Kristoff
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Smith, Donald
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … George Jones
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Joel Jaeggli
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Fernando Gont
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Christopher Morrow
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Jared Mauch
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Ronald Bonica
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Smith, Donald
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … George Jones
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … George Jones
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Smith, Donald
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Warren Kumari
- Re: [OPSEC] Fwd: ID Tracker State Update Notice: … Joel Jaeggli