[Mip6] Comments on draft-le-aaa-mipv6-requirements-03

Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM> Wed, 18 February 2004 13:50 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10753 for <mip6-archive@odin.ietf.org>; Wed, 18 Feb 2004 08:50:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtS5N-0007cK-6D for mip6-archive@odin.ietf.org; Wed, 18 Feb 2004 08:49:57 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IDnvkH029274 for mip6-archive@odin.ietf.org; Wed, 18 Feb 2004 08:49:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtS5N-0007c5-1w for mip6-web-archive@optimus.ietf.org; Wed, 18 Feb 2004 08:49:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10729 for <mip6-web-archive@ietf.org>; Wed, 18 Feb 2004 08:49:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtS5L-0007FV-00 for mip6-web-archive@ietf.org; Wed, 18 Feb 2004 08:49:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtS4O-0007BI-00 for mip6-web-archive@ietf.org; Wed, 18 Feb 2004 08:48:56 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AtS3U-00077B-00 for mip6-web-archive@ietf.org; Wed, 18 Feb 2004 08:48:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtS3V-0007Jo-42; Wed, 18 Feb 2004 08:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtS3J-0007J2-R7 for mip6@optimus.ietf.org; Wed, 18 Feb 2004 08:47:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10632 for <mip6@ietf.org>; Wed, 18 Feb 2004 08:47:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtS3I-00075M-00 for mip6@ietf.org; Wed, 18 Feb 2004 08:47:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtS2K-00071o-00 for mip6@ietf.org; Wed, 18 Feb 2004 08:46:48 -0500
Received: from dns1.tilab.com ([163.162.42.4]) by ietf-mx with esmtp (Exim 4.12) id 1AtS1L-0006xR-00 for mip6@ietf.org; Wed, 18 Feb 2004 08:45:47 -0500
Received: from iowa2k01a.cselt.it ([163.162.242.201]) by dns1.cselt.it (PMDF V6.0-025 #38895) with ESMTP id <0HTA009848TW5E@dns1.cselt.it> for mip6@ietf.org; Wed, 18 Feb 2004 14:44:20 +0100 (MET)
Received: from iowa2k01a.cselt.it ([163.162.242.201]) by iowa2k01a.cselt.it with Microsoft SMTPSVC(5.0.2195.5329); Wed, 18 Feb 2004 14:45:56 +0100
Received: from EXC2K05A.cselt.it ([163.162.36.101]) by iowa2k01a.cselt.it with Microsoft SMTPSVC(5.0.2195.5329); Wed, 18 Feb 2004 14:45:56 +0100
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K05A.cselt.it with Microsoft SMTPSVC(5.0.2195.5329); Wed, 18 Feb 2004 14:45:14 +0100
Date: Wed, 18 Feb 2004 14:45:14 +0100
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: mip6@ietf.org
Cc: Guardini Ivano <Ivano.Guardini@TILAB.COM>
Message-id: <625BE97BF4795E43970345790166B9BCD4DCBE@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: Comments on draft-le-aaa-mipv6-requirements-03
thread-index: AcP2JTKYTPaFcL7fSSCrk1glQ4ShPw==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 18 Feb 2004 13:45:14.0806 (UTC) FILETIME=[6FE5CD60:01C3F625]
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Comments on draft-le-aaa-mipv6-requirements-03
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I read draft-le-aaa-mipv6-requirements-03 and have the following questions:

1) In the draft are you providing requirements on a specific a Diameter Mobile IPv6 Application to be developed (as explicitely mentioned in the abstract and in the introduction) or are you referring to general requirements on the interaction between AAA and MIPv6?

2) In the introduction it is stated that Mobile IPv6 does not have the equivalent of a Foreign Agent and as a result does not offer any mechanism by which the visited network can authenticate and authorize user access. As a consequence it is suggested the specification of a new Diameter Mobile IPv6 Application supporting, among the other features, also local and remote network access control. This is certainly an option that may be useful in certain enviroments. Nevertheless, I think that an additional requirement for a solution to integrate AAA and MIPv6 should be the easy deployability in existing network infastructures, where user authentication and authorization is commonly performed relying on mechanisms that are not related at all with Mobile IPv6 (e.g. EAP, cellular protocols). In such situations, it might be useful to continue to handle user access authorization with the already deployed mechanisms and exploit the MIPv6 Diameter extentions only for MIPv6 service authorization and configuration.

Comments?

--Gerardo



====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please contact us by
replying to MailAdmin@tilab.com. Thank you
====================================================================

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6