draft-ietf-rtgwg-mrt-frr-algorithm - some comments
Stewart Bryant <stewart.bryant@gmail.com> Wed, 09 December 2015 11:33 UTC
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE3F1A8035 for <rtgwg@ietfa.amsl.com>; Wed, 9 Dec 2015 03:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 B1u7b9cq-ewA for <rtgwg@ietfa.amsl.com>; Wed, 9 Dec 2015 03:33:40 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 9C6121A7020 for <rtgwg@ietf.org>; Wed, 9 Dec 2015 03:33:40 -0800 (PST)
Received: by wmec201 with SMTP id c201so255477095wme.0 for <rtgwg@ietf.org>; Wed, 09 Dec 2015 03:33:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:message-id:date:user-agent:mime-version :content-type; bh=6nE9CCXnuO+MOUdKfiZKgKwmfWHFd2hbhucqjcGDJjE=; b=cTv9jhLXFzqBvTZvj7eTZYHy4AaUKMFKEdXVd5fDpBBFZJ2plvgUScQlZUsuo+ggAf hiPKJHHdoBJVacRIlDQi28IX5jmOaTbokH1GVipzDorS8hL1YyxJoWOyyeWExy3ihXla Bux0G2PADoiL/OH/qyj4aI5R0uJyaEjp2o25yKCvoZyLfS6mPU2LLepxJqmW3tLS7uZb pKYqg7bqWNDHXvq80ueq8oke1LCqqzkxBSnZ4o/1YVFUaSP4IbKqUbtzrxUSpxRjOcYr em8F9Fn+STHQvtYt4fk4Kb1mFZywr/FJDh8zZ51byCIyqtdh2jZI4n1tcjDwIZtaH4UD zeRw==
X-Received: by 10.28.225.6 with SMTP id y6mr10986899wmg.58.1449660819057; Wed, 09 Dec 2015 03:33:39 -0800 (PST)
Received: from [192.168.2.132] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id q6sm25681374wmd.8.2015.12.09.03.33.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Dec 2015 03:33:37 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
To: draft-ietf-rtgwg-mrt-frr-algorithm@tools.ietf.org, "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-algorithm - some comments
Message-ID: <56681190.80602@gmail.com>
Date: Wed, 09 Dec 2015 11:33:36 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------020706050204050100060303"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ss16P5MIIapMMRfL0wBK3PwVUFU>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2015 11:33:42 -0000
Hi, I am sorry for the late comments I have looked at the algorithm draft and have a some top level concerns. Firstly you have the sections that describe the operation in detail and the python code both as normative. That is always a dangerous thing to do since it is not clear which has priority in the event of a difference. I am concerned that the algorithm, which can stand on it's own right and a comparison with other methods is included in this text. I think that the comparison text from this draft and from the architecture draft should be put into a single comprehensive evaluation draft. Again I am concerned about the assertion of completeness, since it is complete only against a number of unstated constraints. Finally the authors have clearly copied the security section from the architecture draft. Whilst I am sure that the algorithm has no security concerns per se, that is only because it is placed in an operational context by code that does input parameter filtering and an operating system that ensures it executes correctly. What I would expect from a security analysis was guidance to the implementers of any particular fragility in the algorithm that they needed to consider (there may of course be none). - Stewart
- draft-ietf-rtgwg-mrt-frr-algorithm - some comments Stewart Bryant
- RE: draft-ietf-rtgwg-mrt-frr-algorithm - some com… Chris Bowers
- Re: draft-ietf-rtgwg-mrt-frr-algorithm - some com… Stewart Bryant