[Dime] AD-review of draft-ietf-dime-ikev2-psk-diameter-05.txt
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 05 May 2011 14:59 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74FCFE0682 for <dime@ietfa.amsl.com>; Thu, 5 May 2011 07:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.669
X-Spam-Level:
X-Spam-Status: No, score=-102.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lS+4feTnhpq for <dime@ietfa.amsl.com>; Thu, 5 May 2011 07:59:39 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED3DE0593 for <dime@ietf.org>; Thu, 5 May 2011 07:59:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An8HAIu4wk2HCzI1/2dsb2JhbACYUY1ld4hynF+DWAKbdYYHBJQKihE
X-IronPort-AV: E=Sophos;i="4.64,319,1301889600"; d="scan'208";a="187142466"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 May 2011 10:49:32 -0400
X-IronPort-AV: E=Sophos;i="4.64,319,1301889600"; d="scan'208";a="647974588"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 05 May 2011 10:49:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 05 May 2011 16:49:30 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040310F178@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: AD-review of draft-ietf-dime-ikev2-psk-diameter-05.txt
Thread-Index: AcwLM6OwJj1j0g4PTJOYEHBonlWjAg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Subject: [Dime] AD-review of draft-ietf-dime-ikev2-psk-diameter-05.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2011 14:59:40 -0000
Hi, Please find below the AD review of draft-ietf-dime-ikev2-psk-diameter-05.txt. While the document is in pretty good shape, there are a few key technical and editorial issues that need to be addressed before we can send the document to IETF Last Call. See below. Technical requirements are marked Tx and Editorial requirements are marked Ex. Thanks and Regards, Dan T1. In the Abstract section I find the following: > This document therefore extends the functionality offered by [RFC 5778] with pre-shared key based authentication offered by IKEv2 when no EAP is used. Would not this imply that the document should have the note 'Updates RFC 5779 - when approved' in the header? T2. In any case it seems to me that RFC 5778 should rather be a Normative Reference rather than an Informative reference. E1. [RFC5778] is the correct label for the reference and not [RFC 5778] E2. In Section 1 s/IKEv2 protocol allows/The IKEv2 protocol allows/ E3. Expand HAAA at the first occurrence which is in Section 1 E4. Section 4.2 - s/IKE_SA correspond/IKE_SA corresponds/ E5. Section 9 IANA Considerations needs a serious re-write. The first paragraph should not use verbs at past time as we are describing here codes and values defined in this specification. All the other sections need to be explicit about what allocations are required from IANA. For example it would be good to use the format 'IANA is required to allocate the following AVP Codes: IKEv2 Nonces - TBD5, Ni - TBD5, etc.'
- [Dime] AD-review of draft-ietf-dime-ikev2-psk-dia… Romascanu, Dan (Dan)
- Re: [Dime] AD-review of draft-ietf-dime-ikev2-psk… Cakulev, Violeta (Violeta)
- Re: [Dime] AD-review of draft-ietf-dime-ikev2-psk… Romascanu, Dan (Dan)