Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
Fernando Gont <fgont@si6networks.com> Tue, 20 October 2015 01:17 UTC
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCEE1AD0B6 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXRUaxaPbZS1 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:17:49 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C617A1B2A29 for <opsawg@ietf.org>; Mon, 19 Oct 2015 18:17:48 -0700 (PDT)
Received: from [181.46.190.53] (helo=[172.16.17.13]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZoLYd-0000sg-SL; Tue, 20 Oct 2015 03:17:44 +0200
To: Melinda Shore <melinda.shore@gmail.com>, opsawg@ietf.org
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com> <D24A9604.20C16%uri@ll.mit.edu> <20151019231628.CB57D3AC7EDB@rock.dv.isc.org> <562582EA.4030301@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56259652.1000409@si6networks.com>
Date: Mon, 19 Oct 2015 22:18:10 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <562582EA.4030301@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ce56ZksgCttf4GCYJKfegav8t-w>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 01:17:51 -0000
Hi, Melinda, Thanks so much for your feedback! Please find my comments in-line.... On 10/19/2015 08:55 PM, Melinda Shore wrote: > On 10/19/15 3:16 PM, Mark Andrews wrote: >> When one actually wants to use the capabilities we built into the >> protocol one then has to fight the firewalls even to get the packet >> delivered. Cleaning out old/broken firewalls takes decades. > > Right, but vendors do love their firewalls. It can take an > inordinately long time to get IETF documents out (longer than > it takes to design and implement a product feature) and vendors > are likely to release products that break DNS before a firewalls > draft is done. I think that even with some of the content that we have, plus more specific stuff (possibly in separate document(s)), at least we have something to point vendors at. > I've been watching this discussion and getting a strong sense > of déjà vu, and I think this is going to be a difficult document > to get through the IETF process. It may be preferable, anyway, > to focus on a series of protocol- or application-specific > firewall problems documents - for example, to move a firewall > considerations for DNS document to dnsop. It may be the only > way to get consensus about content. The goal of this document is, to some extent, mostly a high-level discussion. More detailed stuff should probably be done in separate documents, and just referenced from this one to keep the problem "tractable". Thanks! Best regards, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Brian E Carpenter
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Blumenthal, Uri - 0553 - MITLL
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Mark Andrews
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Melinda Shore
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Mark Andrews
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Fernando Gont
- Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewa… Fernando Gont