RE: [Sipping] SIP-AAA Requirements (fwd)

Henry Sinnreich <Henry.Sinnreich@wcom.com> Wed, 01 May 2002 02:59 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 WAA18023 for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 22:59:14 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA13505 for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 22:59:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA12660; Tue, 30 Apr 2002 22:39:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA12628 for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 22:39:44 -0400 (EDT)
Received: from dgesmtp01.wcom.com (dgesmtp01.wcom.com [199.249.16.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17451 for <sipping@ietf.org>; Tue, 30 Apr 2002 22:39:40 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42260) id <0GVE00101VDCO4@firewall.wcom.com> for sipping@ietf.org; Wed, 1 May 2002 02:39:12 +0000 (GMT)
Received: from dgismtp01.wcomnet.com ([166.38.58.141]) by firewall.wcom.com (PMDF V5.2-33 #42260) with ESMTP id <0GVE00MH3VDB14@firewall.wcom.com>; Wed, 01 May 2002 02:39:12 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com (PMDF V5.2-33 #42262) with SMTP id <0GVE00601VD9CM@dgismtp01.wcomnet.com>; Wed, 01 May 2002 02:39:11 +0000 (GMT)
Received: from hsinnreich2 ([153.39.76.99]) by dgismtp01.wcomnet.com (PMDF V5.2-33 #42262) with ESMTP id <0GVE0047GVD2XY@dgismtp01.wcomnet.com>; Wed, 01 May 2002 02:39:03 +0000 (GMT)
Date: Tue, 30 Apr 2002 21:39:04 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] SIP-AAA Requirements (fwd)
In-reply-to: <Pine.WNT.4.44.0204301106440.-632041@chorizo.rapidconvergence.com>
To: 'Rohan Mahy' <rohan@cisco.com>, sipping@ietf.org, mobile-ip@sunroof.eng.sun.com
Cc: john.loughney@nokia.com, Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>, Pat Calhoun <Pat.Calhoun@eng.sun.com>, Charles Perkins <Charles.Perkins@eng.sun.com>, "'C. de Laat'" <C.T.A.M.deLaat@phys.uu.nl>, jrv@merit.edu
Message-id: <000001c1f0b9$5cc7f9b0$634c2799@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

As 3GPP, 3GPP2 and 802.11 wireless networks are poised to use both SIP
and Mobile IP, one cannot help notice there seems to be a lot
commonality between:

1-SIP AAA requirements
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

2-3GPP Requirements on SIP
http://ietf.org/internet-drafts/draft-garcia-sipping-3gpp-reqs-03.txt

3-and most of all, Mobile IP AAA Requirements, RFC 2977
ftp://ftp.isi.edu/in-notes/rfc2977.txt

The mobile IP WG http://ietf.org/html.charters/mobileip-charter.html has
actually covered a lot of groundwork, where it may make sense to avoid
duplication, such as for example for AAA Registration Keys
http://ietf.org/internet-drafts/draft-ietf-mobileip-aaa-key-09.txt

Here are some striking analogies:

Mobile IP    SIP
================
MN-----------UA
FA-----------Visited SIP Registrar
AAAL/H-------SIP AAA
AAAB---------Clearinghouse
See the AAAarch web page
http://iridal.phys.uu.nl/~aaaarch/doc10/home.html and also
http://ietf.org/internet-drafts/draft-johnston-sip-osp-token-02.txt

One more item that the Mobile IP WG has successfully solved is the
separation of specific AAA solutions such as RADIUS, DIAMETER or XML web
services from the mobile IP protocol itself. It is not for the SIPPING
WG to pick winners and losers in AAA solutions and promote one or
another, as has been discussed.

We should try to avoid coming up with several different/incompatible
infrastructures, multiple logons and general annoyance from duplication
of work. Or have the IESG step in to make order.

I believe the SIPPING Mobile IP and AAAarch IP folks should talk to each
other during the WG discussions or maybe possibly at a Bar BOF. I have
taken therefore the liberty to copy the Mobile IP and AAAarch lists.

>John will also be leading discussion on this topic at the interim
meeting next week.
The interested Mobile IP and AAAarch people cannot attend at such short
notice.

Thanks, Henry

Henry Sinnreich
WorldCom
400 International Parkway
Richardson, Texas 75081
USA

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
> On Behalf Of Rohan Mahy
> Sent: Tuesday, April 30, 2002 1:13 PM
> To: sipping@ietf.org
> Cc: john.loughney@nokia.com
> Subject: [Sipping] SIP-AAA Requirements (fwd)
>
>
> Hi,
>
> John Loughney has just submitted a first draft rewrite of the
> SIP AAA requirements.  Until it appears in the archive, you
> can download it from:
>
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

Comments are solicited on the SIPPING list only.

John will also be leading discussion on this topic at the interim
meeting next week.

thanks,
-rohan



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP