[Mip4] review of draft-nakhjiri-radius-mip4-01.txt

Jari Arkko <jari.arkko@piuha.net> Tue, 23 August 2005 14:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7ZsD-0003wb-Ml; Tue, 23 Aug 2005 10:35:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7ZsC-0003wR-Pu for mip4@megatron.ietf.org; Tue, 23 Aug 2005 10:35:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07993 for <mip4@ietf.org>; Tue, 23 Aug 2005 10:35:30 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7ZsJ-0006Pw-Hg for mip4@ietf.org; Tue, 23 Aug 2005 10:35:40 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 6C0668987B for <mip4@ietf.org>; Tue, 23 Aug 2005 17:35:14 +0300 (EEST)
Message-ID: <430B342E.90809@piuha.net>
Date: Tue, 23 Aug 2005 17:35:26 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip4@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Subject: [Mip4] review of draft-nakhjiri-radius-mip4-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I read this draft. In general, it seems very useful to
document & standardize the aaa-side of the mobile ipv4
authentication protocols. (Would there be commitment
from pp2 to take this?)

I don't have a lot of comments, it seems pretty straightforward
given the things that we've already defined in other specifications.
I wish the Diameter - RADIUS translation was easier or even
automatic, but I don't see other way around this given that
RFC 4004 was already published.

Some technical comments:

Section 5 description of attributes that already exist
was confusing. Suggest splitting section 5 to new
attributes and instruction for the use of old attributes
parts.

Section 6 needs more details. Maybe ok for an -01, though.

Presumably this draft is still structurally and key-wise
the same as RFC 4004? If no, that would make the
implementation of a RADIUS-Diameter gateway even
harder.

Some editorial nits:

>    The HA may reside in the mobile nodeÆs home domain, in which case HA 

Non-ASCII char. In several places, applies to double quotes
too.

>    [DIAMIP] P. Calhoun, C. Perkins, ææDiameter Mobile IP applicationÆÆ,
>    IETF work in progress, draft-ietf-aaa-diameter-mobileip-18.txt, May
>    2004.

RFC 4004 now.

>    MIP-answer (HMA). RADIUS currently does not any messages that 

s/does not any/does not have any/

--Jari


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/