[Gen-art] RE: Gen-Art Review: draft-ietf-msec-newtype-keyid-01.txt
"Karl Norrman (KI/EAB)" <karl.norrman@ericsson.com> Fri, 27 January 2006 17:37 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 1F2XX1-000546-Rq; Fri, 27 Jan 2006 12:37:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2XEi-0005IV-22 for gen-art@megatron.ietf.org; Fri, 27 Jan 2006 12:18:12 -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 MAA27693 for <gen-art@ietf.org>; Fri, 27 Jan 2006 12:16:38 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2XOm-0006pq-GW for gen-art@ietf.org; Fri, 27 Jan 2006 12:28:44 -0500
Received: by eikenes.alvestrand.no (Postfix) id 9BC3C2596DD; Fri, 27 Jan 2006 18:16:41 +0100 (CET)
Delivered-To: gen-art@alvestrand.no
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 801742596DC for <gen-art@alvestrand.no>; Fri, 27 Jan 2006 18:16:41 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15225-05 for <gen-art@alvestrand.no>; Fri, 27 Jan 2006 18:16:32 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.7
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by eikenes.alvestrand.no (Postfix) with ESMTP id C84382596DB for <gen-art@alvestrand.no>; Fri, 27 Jan 2006 18:16:32 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 6BDD9B11; Fri, 27 Jan 2006 18:17:40 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Jan 2006 18:17:40 +0100
Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Fri, 27 Jan 2006 18:17:39 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C62365.9322BF92"
Date: Fri, 27 Jan 2006 18:17:38 +0100
Message-ID: <3AD208E1F0D5EB47AC3C5617420BCB0203ADCE8C@esealmw104.eemea.ericsson.se>
X-MS-Has-Attach: yes
Thread-Topic: Gen-Art Review: draft-ietf-msec-newtype-keyid-01.txt
Thread-Index: AcWIeQeU1pren5bVTm2jpFCaSzouRya5wbOw
From: "Karl Norrman (KI/EAB)" <karl.norrman@ericsson.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@alvestrand.no
X-OriginalArrivalTime: 27 Jan 2006 17:17:39.0977 (UTC) FILETIME=[937D4F90:01C62365]
X-Brightmail-Tracker: AAAAAA==
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a9ddb14fac983e71b59f23b52a45b4e
X-Mailman-Approved-At: Fri, 27 Jan 2006 12:37:05 -0500
Cc: Russ Housely <housley@vigilsec.com>, "Vesa Lehtovirta (JO/LMF)" <vesa.lehtovirta@ericsson.com>
Subject: [Gen-art] RE: Gen-Art Review: draft-ietf-msec-newtype-keyid-01.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
Hello! Thank you very much for your review. Please see the attached updated draft and inline. [SNIP] > Summary: > [I understand from Laksminath Dondeti that this draft maybe > withdrawn, but FWIW, here is my review.] This document has > some minor issues with the IANA considerations and needs some > editorial tidying up. > > The 'empty map' option worries me, but I am not sufficiently > much of security expert to determine if this is justified. > If this is cleared the draft could go forward (but it sounds > like there will be another revision pass to go through). > > Detailed Review: > > Issues: > I am not sure that I fully understand what is going on the > justification of the need for an empty map(last para of s2). > '... required parameters are signalled in-band.' => in what protocol? > I think a slightly less opaque explanation would help here. An example is now given (the OMA DRM Content Format used for download). > Associated with this there should be an explicit statement in > s4 that no equivalent of SRTP_ID would be needed in this case. Such a statement is now added (Please note that there is a new Section 3, so this text is now in Section 5). > > IANA considerations: > This section should refer to the IANA process setup in > RFC3380 for the payload type and the CS ID map type. > It needs to define a new process for the Key ID Type registry. A process is now set up in the IANA considerations section. > > Security Considerations: > Are those that understand these things absolutely convinced > that creating keys without attaching them to an SA in the > process does not create some sort of opportunity to create mayhem? The security considerations section is now expanded. > > Editorial Nits > > You should run idnits: there are non ascii characters in the > document, e.g. bullet point marks in s2. This version passed idnits. Thanks and regards, Karl > > s1: 3rd para: s/possibility/ability/ > s1: 3rd para: (I take it that we are trying to make it easier > rather than more difficult) s/should be/would be/ > s1: 4th para: s/involved/keys/keys involved/ > s2: 1st para: s/the MBMS/MBMS/ > s2: 2nd para: s/athree level/three level/ > s2 10th para: s/involved keys in the/keys being carried in a/ > s3: Tables and figures should have captions > s3: s/bytes/octets/ (2 places) > s3: last para: Actually I think (2^16 -1), but I hope I never > have that many keys ;-) > s5: s/This memo is not foreseen to introduce security > implications./It is not a anticipated that this memo will > have any additional security implications beyond those > already identified for the MIKEY protocol./ >
_______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] RE: Gen-Art Review: draft-ietf-msec-new… Karl Norrman (KI/EAB)
- Re: [Gen-art] RE: Gen-Art Review: draft-ietf-msec… Brian E Carpenter
- Re: [Gen-art] RE: Gen-Art Review: draft-ietf-msec… Russ Housley
- RE: [Gen-art] RE: Gen-Art Review: draft-ietf-msec… Vesa Lehtovirta (JO/LMF)
- [Gen-art] Gen-Art Review: draft-ietf-msec-newtype… Elwyn Davies
- [Gen-art] Re: Gen-Art Review: draft-ietf-msec-new… Lakshminath Dondeti
- Re: [Gen-art] Re: Gen-Art Review: draft-ietf-msec… Brian E Carpenter
- [Gen-art] Re: Gen-Art Review: draft-ietf-msec-new… Elwyn Davies
- [Gen-art] Re: Gen-Art Review: draft-ietf-msec-new… Lakshminath Dondeti