[OSPF] Stephen Farrell's No Objection on draft-ietf-ospf-ttz-05: (with COMMENT)
"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Thu, 05 January 2017 14:16 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ospf@ietf.org
Delivered-To: ospf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BE4129556; Thu, 5 Jan 2017 06:16:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148362581683.20611.16224230586723841663.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jan 2017 06:16:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/mhTlefM169p-FKT8JQiwmovtBeE>
Cc: ospf@ietf.org, ospf-chairs@ietf.org, draft-ietf-ospf-ttz@ietf.org
Subject: [OSPF] Stephen Farrell's No Objection on draft-ietf-ospf-ttz-05: (with COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jan 2017 14:16:57 -0000
Stephen Farrell has entered the following ballot position for draft-ietf-ospf-ttz-05: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-ospf-ttz/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- - section 13: I don't agree that there are no new security considerations, and in fact you seem to raise one so I'd suggest dropping the "nothing to see here" pseudo-boilerplate;-) - section 13: If a router inside a TTZ is borked, then mechanisms that detect borked routers won't work as well from outside the TTZ I guess (e.g. they might identify the wrong router as the borked one). And contrary-wise, hiding topology may help in that it may make it harder for an attacker to find a desirable target. Did anyone think about this? (This is not a discuss only because I'm not familiar enough with ospf but I bet a beer that hiding topology will create more new security issues that are not described here;-) - 8.1: Did I miss where "Z flag" was described? - nit: six authors again, plus 2 contributors plus 4 "other authors." I really don't get why it's not possible to reduce to 5 in cases like this.
- [OSPF] Stephen Farrell's No Objection on draft-ie… Stephen Farrell
- Re: [OSPF] Stephen Farrell's No Objection on draf… Spencer Dawkins at IETF
- Re: [OSPF] Stephen Farrell's No Objection on draf… Huaimo Chen
- Re: [OSPF] Stephen Farrell's No Objection on draf… Huaimo Chen