Re: [OSPF] Stephen Farrell's No Objection on draft-ietf-ospf-ttz-05: (with COMMENT)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 05 January 2017 14:36 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id D2CD81294C3;
Thu, 5 Jan 2017 06:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
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 DQpuJZTYTLiT; Thu, 5 Jan 2017 06:36:39 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com
[IPv6:2607:f8b0:4002:c05::22c])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 2D140129575;
Thu, 5 Jan 2017 06:36:39 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id r204so343982009ywb.0;
Thu, 05 Jan 2017 06:36:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=BINJxAjfdjfLO7fSwz1pVxwyI9ky/c4KStqxIFjf/bI=;
b=cR72IrtjO9/Kstw1ib5e+dX0YSrcZS5O6IQ7POdwyQvFMcrWYEjVQvOd5TdIFNcVll
Tw5ntss4pYdSDvP/ZNZ9v0ogHsOzPIkPckhTKyxRc4Pgz7fXQXy+eB88zdSWA3obMAd6
LzgXD9cgjvUw4hjwZx9Wd3fpoROfCYmzJl/+zE3lgHUohjKUnRZpaFd7fm9RuFfiBWEM
82fPkShai+I05Sko5Ma/RByUIBhhxpf+pE5MsYNFUcdjCfNnUrmTH3RxrRb7a4QKJ1fK
Pb3B+cdh1hqC8q2O8lcmWo7/8ppH+73N8hl58wJDFMl5m1Hybe4f076UkZpEBGQ0Fzck
FwIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=BINJxAjfdjfLO7fSwz1pVxwyI9ky/c4KStqxIFjf/bI=;
b=K3JGQBcGA3eljkanz2Wfp9GymDlka93CY5G5jMvuiLsAppf49tuS/nTc7zNv5KJbK0
KpotKff/J95ZI3kyf5SqnKOb/g74W1kFwWOK8nwUVUzwUwASilZkryJ74uDbpSpXqpWi
FlCE81cAzcRBSHzfUao2WrzohY5yCPtfiN9atmclkWQ/QPY4C6oWMQzhh8q03XyjPCdg
/sBgQm+JcQKEOHy93i+8YMIY9t1KaXAqhIGvBROIBz5I9rlY7Eso08Gq8RU0REx5mTp8
kC+3duwIKYjTQLcRYKSDwWhBmrHCkBQkvwLqDhTBUTUYfPiCeEc6eFL0F1+P76JkYqgA
AmSg==
X-Gm-Message-State: AIkVDXKIuA8myjUGyL/VzsW2xA1sGjgUxKZKAwkky0Jnt8mOLIzgcg5GLkf5bU/KJL6H9v3eL0c/V2P8gMPJlg==
X-Received: by 10.129.174.23 with SMTP id m23mr46237676ywh.152.1483626998458;
Thu, 05 Jan 2017 06:36:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.221.195 with HTTP; Thu, 5 Jan 2017 06:36:38 -0800 (PST)
Received: by 10.37.221.195 with HTTP; Thu, 5 Jan 2017 06:36:38 -0800 (PST)
In-Reply-To: <148362581683.20611.16224230586723841663.idtracker@ietfa.amsl.com>
References: <148362581683.20611.16224230586723841663.idtracker@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 5 Jan 2017 08:36:38 -0600
Message-ID: <CAKKJt-e64BGU9oHv2MbhxppK5iOvMVgdZfiq-eC2Ch+O=Vd4uw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=f403045e578838efd1054559d4eb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/KuCJcPprdD0_xRfnEyKE5cApvYI>
Cc: ospf@ietf.org, iesg@ietf.org, draft-ietf-ospf-ttz@ietf.org,
ospf-chairs@ietf.org
Subject: Re: [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
Precedence: list
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:36:41 -0000
Make Stephen happy, but ... On Jan 5, 2017 08:17, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote: 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;-) I think the changes we discussed on my comments to make it clearer what TTZ looks like to anything outside the TTZ will help, at least a bit, for SEC types to understand security threats. Maybe it's worth remembering Stephen's comments when you're adding context early in the document? Thanks, Spencer - 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