[Mip4] draft-ietf-mip4-aaa-nai-00.txt
Bjorn Andersson <bjorn@iki.fi> Wed, 08 October 2003 07:57 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05553 for <mip4-archive@odin.ietf.org>; Wed, 8 Oct 2003 03:57:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79Bw-0005er-Mr for mip4-archive@odin.ietf.org; Wed, 08 Oct 2003 03:57:05 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h987v4Un021748 for mip4-archive@odin.ietf.org; Wed, 8 Oct 2003 03:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79Bw-0005eh-2q for mip4-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 03:57:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05532 for <mip4-web-archive@ietf.org>; Wed, 8 Oct 2003 03:56:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A79Bt-0001sZ-00 for mip4-web-archive@ietf.org; Wed, 08 Oct 2003 03:57:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A79Bt-0001sV-00 for mip4-web-archive@ietf.org; Wed, 08 Oct 2003 03:57:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79Bt-0005dv-Bv; Wed, 08 Oct 2003 03:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79B7-0005X9-CK for mip4@optimus.ietf.org; Wed, 08 Oct 2003 03:56:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05481 for <mip4@ietf.org>; Wed, 8 Oct 2003 03:56:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A79B4-0001qq-00 for mip4@ietf.org; Wed, 08 Oct 2003 03:56:10 -0400
Received: from fep21-0.kolumbus.fi ([193.229.0.48] helo=fep21-app.kolumbus.fi) by ietf-mx with esmtp (Exim 4.12) id 1A79B4-0001qi-00 for mip4@ietf.org; Wed, 08 Oct 2003 03:56:10 -0400
Received: from yin.bjorns.net ([62.248.140.69]) by fep21-app.kolumbus.fi with ESMTP id <20031008075610.NUOM29573.fep21-app.kolumbus.fi@yin.bjorns.net> for <mip4@ietf.org>; Wed, 8 Oct 2003 10:56:10 +0300
Received: from bjorn by yin.bjorns.net with local (Exim 3.35 #1 (Debian)) id 1A79B3-0004Nm-00 for <mip4@ietf.org>; Wed, 08 Oct 2003 10:56:09 +0300
Date: Wed, 08 Oct 2003 10:56:09 +0300
From: Bjorn Andersson <bjorn@iki.fi>
To: mip4@ietf.org
Message-ID: <20031008075609.GA16710@yin.bjorns.net>
References: <200309221845.OAA29925@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <200309221845.OAA29925@ietf.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA05482
Subject: [Mip4] draft-ietf-mip4-aaa-nai-00.txt
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Regarding draft-ietf-mip4-aaa-nai-00.txt: I would rather like to see a "Generalized NAI" spec (for both advertisements and registration messages) and then have this draft refer to that. Is there any reason not to write a generalized NAI draft, or resurrect the old one? E.g. the route optimization and hierarchy drafts use some other NAI extensions. A FA NAI extension in registraion requests also solves an authentication problem with MIP NAT traversal. I think it would be clearer if we have a document describing just the GNAI extension, instead of specifing a general extension in a document describing a solution to a specific problem. Anyway, idenpendently of where it is specified, I think it is clear that we need, or will need, NAI extensions for various purposes. It would be nice if we could nail down a generalized NAI extension number and some subtype numbers for e.g. the HA, AAAH and FA (and maybe a "Previous FA" NAI). Björn -- Björn Andersson <bjorn@iki.fi> PGP id 5AFC144B -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4
- [Mip4] I-D ACTION:draft-ietf-mip4-aaa-nai-00.txt Internet-Drafts
- [Mip4] draft-ietf-mip4-aaa-nai-00.txt Bjorn Andersson