[Dime] comments on http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-cmd-iana-00.txt
"Glen Zorn" <gwz@net-zen.net> Wed, 03 June 2009 14:17 UTC
Return-Path: <gwz@net-zen.net>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3F273A6A2A for <dime@core3.amsl.com>; Wed, 3 Jun 2009 07:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level:
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPEs4KfI3Ygd for <dime@core3.amsl.com>; Wed, 3 Jun 2009 07:17:21 -0700 (PDT)
Received: from smtpauth02.prod.mesa1.secureserver.net (smtpauth02.prod.mesa1.secureserver.net [64.202.165.182]) by core3.amsl.com (Postfix) with SMTP id 08A4E3A6B97 for <dime@ietf.org>; Wed, 3 Jun 2009 07:17:20 -0700 (PDT)
Received: (qmail 16877 invoked from network); 3 Jun 2009 14:16:58 -0000
Received: from unknown (124.122.162.36) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 03 Jun 2009 14:16:57 -0000
From: Glen Zorn <gwz@net-zen.net>
To: dime@ietf.org
Date: Wed, 03 Jun 2009 21:13:47 +0700
Organization: Network Zen
Message-ID: <006901c9e455$856d84b0$90488e10$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnkVYKqM1/+y7e7T6eBSoo4nqClZg==
Content-Language: en-us
Subject: [Dime] comments on http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-cmd-iana-00.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 03 Jun 2009 14:17:21 -0000
Last sentence of the Abstract, s/causes/caused. Last sentence of Section 1 says: This document has as a goal providing in advance the change in the command codes allocation policy, so that interoperability problems as the ones described above are avoided as soon as possible. Suggest changing to: This document has as a goal providing in advance the change in the command codes allocation policy made in {reference to rfc3588bis}, so that interoperability problems such as those mentioned above may be avoided as much as possible. Reason: no description is given of any interoperability problems. Question: section 4, paragraph 2 says "The values 0-255 (0x00-0xff) are reserved for RADIUS backward compatibility" ; strictly speaking, for backwards compatibility, shouldn't only those command codes that mapped directly to RADIUS messages at the time RFC3588 was published be reserved? Otherwise, it's forward compatibility, too... Section 4, paragraph 3 says "The request to IANA for a Vendor-Specific Command Code SHOULD include a reference to a publicly available specification which documents the command in sufficient detail to aid in interoperability between independent implementations." The word "aid" seems a little weak to me; how about "provide for"? The body of the RADTYPE reference appears to be poorly formatted. ~gwz Play assigns meaning to human activity--work erases it. -- P.L. Wilson