[Gen-art] Gen-art review of draft-ietf-msec-bootstrapping-tesla-02.txt
Elwyn Davies <elwynd@dial.pipex.com> Thu, 15 December 2005 00:09 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emggi-0006Wd-FG; Wed, 14 Dec 2005 19:09:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emggh-0006WU-Hk for gen-art@megatron.ietf.org; Wed, 14 Dec 2005 19:09:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16795 for <gen-art@ietf.org>; Wed, 14 Dec 2005 19:08:28 -0500 (EST)
Received: from b.painless.aaisp.net.uk ([81.187.81.52] helo=smtp.aaisp.net.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Emghq-0007qf-0E for gen-art@ietf.org; Wed, 14 Dec 2005 19:10:47 -0500
Received: from 247.254.187.81.in-addr.arpa ([81.187.254.247] helo=[127.0.0.1]) by smtp.aaisp.net.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1EmggE-0001FW-0W; Thu, 15 Dec 2005 00:09:06 +0000
Message-ID: <43A0B498.6020801@dial.pipex.com>
Date: Thu, 15 Dec 2005 00:11:04 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <hardie@qualcomm.com>, Hannes.Tschofenig@siemens.com, Russ Housely <housley@vigilsec.com>, steffen.fries@siemens.com
Subject: [Gen-art] Gen-art review of draft-ietf-msec-bootstrapping-tesla-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org
I was selected as General Area Review Team reviewer for this specification (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Document: draft-ietf-msec-bootstrapping-tesla-02.txt Intended Status: Proposed Standard Shepherding AD: Russ Housely Review Trigger: IESG Telechat, 12 December 2005 Summary: This document is almost ready for PS. More precise specification is needed of at least two and possibly four of the TESLA parameters to be carried in MIKEY. There are also a number of editorial nits. Ted Hardie has also registered two comments regarding possible alternatives to NTP and the need to specify which registries are affected by the IANA considerations. Detail: Generally the document is very well written and the security analysis is admirably clear and (apparently) comprehensive. Issues: s4.2: Need to be more precise about how time values are carried (items 7 and 11). One possibility is to refer to s6.6 of RFC3830 which gives three options for timestamp formats. s4.2: I think it might be desirable to be more precise about how big items 8 and 9 are (2 byte or 4 byte integers maybe) s4.2: Presumably Type 11 is optional, dependent on the sync method used. Does anything need to be said about how it is decided whether this should be present/processed? Is it a matter of policy to be determined OOB or it being present implies the use of 'type 2' synchronization? s4.3, last para: The use of SHOULD as regards NTP apparently allows for alternatives to the two methods specified for transmitting time stamps. If this is correct something needs to be said about how suitable methods ahould be selected (identified by Ted Hardie). s6: The registries and defining documents into which the attributes are to be inserted need to be specified. Editorial: Abstract: is maybe a bit long., acronyms MAC, MIKEY need expanding.. s1, para 2: s/paramter/parameter/ s1, para 3: s/in a way/in a way that is intended to/ s1, para 3: s/does only focus/only focuses/ s1, para 3: s/on the generation/on the generation of those parameters/ s1, para 4: s/Diffie Hellman)/Diffie-Hellman)./ s1, para 4: s/Diffie Hellman/Diffie-Hellman/ s1, para 4: s/Recently a/A/ [It won't be recently once this is a long in the tooth RFC] s1, para 4: s/schemens/schemes/ s1, para 5: s/usage for SRTP is/usage for SRTP are/ s3: Various acronyms need expanding and maybe stating that they are defined elsewhere (PRF, HMAC-SHA1) s3: Would be useful to say full list of parameters is in s4.3 of -msec-srtp-tesla. s3: The last para duplicates the statement just before the list about the location of the defaults in s6.2 of -msec-srtp-tesla. s4.2: It might be desirable to note that policy Type 11 does NOT correspond to item 11 in s3 which is actually covered by s4.4. s4.3, item 2:s/shortly repeated/summarized/ s5.1: expand MitM acronym s5.1, countermeasures: s/protocol run it is not possible/protocol exchange will make it impossible/ s5.3, Threat: s/parameters exchange/the parameters exchanged/ s5.3, Threat: s/discurpt/disrupt/ s5.5, Threat: s/desireable/desirable/ _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-art review of draft-ietf-msec-boots… Elwyn Davies