From owner-aaa-bof@merit.edu  Fri Jun  4 01:19:24 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id BAA12909
	for <aaa-wg-archive@nic.merit.edu>; Fri, 4 Jun 1999 01:19:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0C1A044402; Fri,  4 Jun 1999 01:19:09 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E08EF44419; Fri,  4 Jun 1999 01:19:08 -0400 (EDT)
Received: from mailhost.auckland.ac.nz (mailhost.auckland.ac.nz [130.216.1.4])
	by segue.merit.edu (Postfix) with ESMTP id 0902E44402
	for <aaa-wg@merit.edu>; Fri,  4 Jun 1999 01:19:04 -0400 (EDT)
Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79])
	by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with SMTP id RAA06546
	for <aaa-wg@merit.edu>; Fri, 4 Jun 1999 17:18:56 +1200 (NZST)
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
To: aaa-wg@merit.edu
Subject: AAA Accounting I-Ds
In-Reply-To: <3.0.6.32.19990413151906.00972b30@158.222.8.12>
Message-ID: <SIMEON.9906041725.L@n.auckland.ac.nz>
Date: Fri, 4 Jun 1999 17:18:25 +1200 (New Zealand Standard Time)
X-Mailer: Simeon for Win32 Version 4.1.4 Build (40)
X-Authentication: none
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Hello all:

I've recently published a new Internet Draft which collects together
a lot of information about Accounting Attributes as they appear in
current IETF documents (I-Ds and RFCs) and some ITU material.  The
draft's filename is draft-brownlee-accounting-attributes-00.txt

In producing this, I've realised that there are lots of good ideas
for Accounting which are implemented in proprietary protocols and
extensions to standard protocols.  I'd be delighted to add information
about any such work from vendors willing to describe them - please send
a brief description to me, i.e. to   n.brownlee@auckland.ac.nz.

The Accounting subgroup of AAA has two other I-Ds:

draft-aboba-acct-00.txt  
                 Introduction to Accounting Management
                     Explains what 'accounting' is, and
                     sets out a clear framework for it.
draft-arkko-acctreq-00.txt
                 Requirements for Internet-Scale Accounting Management
                     Sets out a list of accounting rquirements.
                     Comparison table for existing protocols.

The subgroup is working towards producing three drafts, as follows:

1)  Accounting: A Management Framework
      Defines what 'accounting' means, points out the things
      one should consider when designing a system which 
      uses accounting.  (Makes the point that accounting
      requires a system-wide view, it's not just a protocol).

2)  Accounting: Attributes and File Formats
      Surveys existing IETF and ITU accounting documents,
      proposes an extensible set of generalised attributes,
      together with record and file formates for handling them.

3)  Accounting: Requirements for Internet Accounting
      Sets out requirements for accounting within AAA,
      in the context of drafts 1) and 2) above.

Our three current I-Ds are getting closer to this, but we now need 
some detailed comments back from this list!

Cheers, Nevil

+---------------------------------------------------------------------+
| Nevil Brownlee                     Director, Technology Development |
| Phone: +64 9 373 7599 x8941        ITSS, The University of Auckland |
|   FAX: +64 9 373 7021      Private Bag 92019, Auckland, New Zealand |
+---------------------------------------------------------------------P



From owner-aaa-bof@merit.edu  Tue Jun  8 10:42:44 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA29185
	for <aaa-wg-archive@nic.merit.edu>; Tue, 8 Jun 1999 10:42:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2525F4441F; Tue,  8 Jun 1999 10:42:27 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 088F344424; Tue,  8 Jun 1999 10:42:27 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5])
	by segue.merit.edu (Postfix) with ESMTP id 73DC14441F
	for <aaa-wg@merit.edu>; Tue,  8 Jun 1999 10:42:25 -0400 (EDT)
Received: from mailserver1.ericsson.se (mailserver1.ericsson.se [136.225.152.91])
	by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with ESMTP id QAA25842
	for <aaa-wg@merit.edu>; Tue, 8 Jun 1999 16:40:49 +0200 (MET DST)
Received: from madrid (madrid.ericsson.se [164.48.87.150])
	by mailserver1.ericsson.se (8.8.8/8.8.8/eri-1.0) with SMTP id QAA10354
	for <aaa-wg@merit.edu>; Tue, 8 Jun 1999 16:41:17 +0200 (MET DST)
Received: from e00c04fc1a1b1 by madrid (SMI-8.6/SMI-SVR4)
	id QAA19583; Tue, 8 Jun 1999 16:40:43 +0200
Received: by localhost with Microsoft MAPI; Tue, 8 Jun 1999 16:40:45 +0200
Message-ID: <37018470D6B5D21185650008C7A451373754D3@eestqnt101.ericsson.se>
From: =?us-ascii?Q?Jose_Luis_Ruiz_Sanchez?= <ecejolu@madrid.ericsson.se>
Reply-To: "ecejolu@madrid.ericsson.se" <ecejolu@madrid.ericsson.se>
To: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Subject: AAA meeting in Oslo?
Date: Tue, 8 Jun 1999 16:40:44 +0200
Organization: ECE/TM/DU
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hello,

I have not seen AAA on the agenda for IETF 45. Is there going to be a WG meeting in Oslo?

Jose Luis

-------------------------------------------------------------------------------------------------------------------------------
Jose L. Ruiz					tel. +34 91 339 3654
Ericsson Spain.					fax +34 91 339 2538
Retama 1					email: ecejolu@madrid.ericsson.se
28045 Madrid, Spain




From owner-aaa-bof@merit.edu  Thu Jun 10 07:20:35 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id HAA29018
	for <aaa-wg-archive@nic.merit.edu>; Thu, 10 Jun 1999 07:20:35 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7117F44422; Thu, 10 Jun 1999 07:20:16 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 454B44442E; Thu, 10 Jun 1999 07:20:16 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id F256944422
	for <aaa-wg@merit.edu>; Thu, 10 Jun 1999 07:20:14 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25822;
	Thu, 10 Jun 1999 07:20:12 -0400 (EDT)
Message-Id: <199906101120.HAA25822@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: aaa-wg@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-aboba-acct-01.txt
Date: Thu, 10 Jun 1999 07:20:12 -0400
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Authentication, Authorization and Accounting Working Group of the IETF.

	Title		: Introduction to Accounting Management
	Author(s)	: B. Aboba, J. Arkko
	Filename	: draft-aboba-acct-01.txt
	Pages		: 34
	Date		: 09-Jun-99
	
The field of Accounting Management is concerned with the collection of
resource consumption data for the purposes of capacity and trend anal-
ysis,  cost allocation, auditing, and billing. This document describes
the problems encountered in Accounting Management, as well as some  of
the  issues  encountered  in the design of accounting systems. It also
reviews the state of current practice.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-aboba-acct-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-aboba-acct-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-aboba-acct-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990609084225.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-aboba-acct-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-aboba-acct-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990609084225.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-aaa-bof@merit.edu  Thu Jun 10 11:03:35 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA01449
	for <aaa-wg-archive@nic.merit.edu>; Thu, 10 Jun 1999 11:03:34 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 1679C4444D; Thu, 10 Jun 1999 11:03:14 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id EBA7B4444F; Thu, 10 Jun 1999 11:03:13 -0400 (EDT)
Received: from omzrelay01.mcit.com (alpha.mcit.com [199.249.19.243])
	by segue.merit.edu (Postfix) with ESMTP id B5EDD4444D
	for <aaa-wg@merit.edu>; Thu, 10 Jun 1999 11:03:12 -0400 (EDT)
Received: from ndcrelay2.mcit.com ([166.37.172.6])
 by firewall.mcit.com (PMDF V5.2-32 #38416)
 with ESMTP id <0FD4000T995K9M@firewall.mcit.com> for aaa-wg@merit.edu; Thu,
 10 Jun 1999 14:49:02 +0000 (GMT)
Received: from omzmta02.mcit.com (omzmta02.mcit.com [166.37.194.120])
 by ndcrelay2.mcit.com (8.8.7/) with ESMTP	id OAA31209; Thu,
 10 Jun 1999 14:45:16 +0000 (GMT)
Received: from c25776a ([166.45.2.228])
 by omzmta02.mcit.com (InterMail v03.02.05 118 120)
 with SMTP id <19990610144851.HCOQ642@[166.45.2.228]>; Thu,
 10 Jun 1999 14:48:51 +0000
Date: Thu, 10 Jun 1999 09:48:58 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
In-reply-to: <199906101120.HAA25822@ietf.org>
To: Internet-Drafts@ietf.org
Cc: aaa-wg@merit.edu, david.burdett@mondex.com,
        "Oran@Cisco.Com" <oran@cisco.com>, stephen.thomas@transnexus.com
Message-id: <NBBBIIJFOKPMFOOILMBKKELEECAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Though it is a very systematic approach, I am intrigued why

The Open Settlement Protocol
<draft-thomas-mime-osp-token-00.txt> , and

The Internet Open Trading Protocol
<draft-ietf-trade-iotp-v1.0-protocol-03.txt>

are not included in the discussion or in the references. Is this an omission
or are there other reasons that we can share?
Case of ships in the night in the IETF?

Thanks, Henry

Henry Sinnreich
MCI WorldCom
400 International Parkway
Richardson, Texas 75081, USA



> -----Original Message-----
> From: owner-aaa-bof@merit.edu [mailto:owner-aaa-bof@merit.edu]On Behalf
> Of Internet-Drafts@ietf.org
> Sent: Thursday, June 10, 1999 6:20 AM
> To: IETF-Announce: ;IETF-Announce:;@wcom.com
> Cc: aaa-wg@merit.edu
> Subject: I-D ACTION:draft-aboba-acct-01.txt
>
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the Authentication, Authorization
> and Accounting Working Group of the IETF.
>
> 	Title		: Introduction to Accounting Management
> 	Author(s)	: B. Aboba, J. Arkko
> 	Filename	: draft-aboba-acct-01.txt
> 	Pages		: 34
> 	Date		: 09-Jun-99
>
> The field of Accounting Management is concerned with the collection of
> resource consumption data for the purposes of capacity and trend anal-
> ysis,  cost allocation, auditing, and billing. This document describes
> the problems encountered in Accounting Management, as well as some  of
> the  issues  encountered  in the design of accounting systems. It also
> reviews the state of current practice.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-aboba-acct-01.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with
> the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-aboba-acct-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-aboba-acct-01.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>



From owner-aaa-bof@merit.edu  Thu Jun 10 13:03:38 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA02549
	for <aaa-wg-archive@nic.merit.edu>; Thu, 10 Jun 1999 13:03:38 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5339A44455; Thu, 10 Jun 1999 13:03:13 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 36AC044457; Thu, 10 Jun 1999 13:03:13 -0400 (EDT)
Received: from keith.lloyd.com (keith.lloyd.com [158.222.1.2])
	by segue.merit.edu (Postfix) with ESMTP id 24C6A44455
	for <aaa-wg@merit.edu>; Thu, 10 Jun 1999 13:03:10 -0400 (EDT)
Received: from murray (root@keith.lloyd.com [158.222.1.2])
	by keith.lloyd.com (8.9.3/8.9.1) with SMTP id KAA16967
	for <aaa-wg@merit.edu>; Thu, 10 Jun 1999 10:03:07 -0700 (PDT)
Message-Id: <3.0.6.32.19990610100159.00926260@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 10 Jun 1999 10:01:59 -0700
To: aaa-wg@merit.edu
From: Brian Lloyd <brian@lloyd.com>
Subject: RE:  AAA meeting in Oslo?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

We will be meeting in Oslo.  No, I don't know why it didn't appear in the
schedule because we requested two slots, one each on adjacent days.  I know
that I will be attending and I believe that Paul will also.

We are working on getting the schedule "fixed."


Brian Lloyd                                    Lucent Technologies
brian@lloyd.com                                3461 Robin Lane, Suite 1
http://www.livingston.com                      Cameron Park, CA  95682
+1.530.676.6513 - voice                        +1.530.676.3442 - fax



From owner-aaa-bof@merit.edu  Fri Jun 11 04:48:55 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id EAA12398
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 04:48:54 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2360C4446D; Fri, 11 Jun 1999 04:48:40 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E4D6D4446B; Fri, 11 Jun 1999 04:48:39 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5])
	by segue.merit.edu (Postfix) with ESMTP id 4580E4446D
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 04:48:29 -0400 (EDT)
Received: from lmf.lmf.ericsson.se (umail.lmf.ericsson.se [131.160.11.2])
	by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with ESMTP id KAA14751;
	Fri, 11 Jun 1999 10:47:28 +0200 (MET DST)
Received: from lmf.ericsson.se by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id LAA28119; Fri, 11 Jun 1999 11:46:56 +0300 (EET DST)
Message-ID: <3760CCFE.73BA342B@lmf.ericsson.se>
Date: Fri, 11 Jun 1999 11:46:54 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Henry Sinnreich <henry.sinnreich@wcom.com>
Cc: aaa-wg@merit.edu, david.burdett@mondex.com,
        "Oran@Cisco.Com" <oran@cisco.com>, stephen.thomas@transnexus.com,
        bernarda@microsoft.com
Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
References: <NBBBIIJFOKPMFOOILMBKKELEECAA.henry.sinnreich@wcom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>Though it is a very systematic approach, I am intrigued why
>The Open Settlement Protocol
><draft-thomas-mime-osp-token-00.txt> , and
>The Internet Open Trading Protocol
>draft-ietf-trade-iotp-v1.0-protocol-03.txt>
>are not included in the discussion or in the references.

Well, we've certainly been aware of IOTP at least (though OSP is
news to me). There has been a discussion on the AAA list on
the subject as well, perhaps concentrating more on AAA in
general than accounting in particular. The discussion took
place at the end of 1998, and participants in that discussion
included at least you Henry, Hannu Nikkanen, Pat Calhoun, and
David Burdett. (Some people in the discussion believed e-commerce
and AAA are very much related, some believed they are the same
thing but for a very different purpose, and some believed there'd
be value in combining them or using the same mechanisms.)

We'd very much like to include text in the draft about
IOTP and other similar mechanisms. Perhaps you Henry have
some text that describes your opinion of how accounting and
IOTP/OSP/... relate and what are the possibilties these
mechanisms offer for the AAA? 

Also, I might just kick off discussions by making some
initial comments on what I think the relationships are:

	- Accounting and trading protocols differ in the
	  sense that often at accounting we look at the
	  _bulk_ problem while trading and e-commerce
	  looks at single transactions between two peers.

	  Of course, this doesn't necessarily mean
	  that e.g. IOTP would be unsuitable for use
	  as an accounting protocol. We should perform
	  an analysis of what IOTP can actually do and
	  place the results in the draft, looking at
	  all the same issues we have already looked
	  at for the other mechanisms.

	- Another difference is that in accounting we
	  usually have agreements in place beforehand,
	  while in e-commerce we wish to enable previously
	  unknown peers to engage in transactions.

	- A third difference is that in accounting we
	  don't usually transfer money; it happens
	  later.

	  Of course, there might be some value in
	  a combined approach where both immediate
	  e-cash payments and we-pay-at-the-end-of-month
	  model would fit the same framework.

	- How do the trading/e-commerce mechanisms and
	  IOTP in particular handle roaming situations,
	  where there'd be more than two entities involved
	  in a transaction? Based on some pictures I've
	  seen in the IOTP working group I believe it
	  can handle this, but can somebody confirm this?

Jari
---- 
Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.


From owner-aaa-bof@merit.edu  Fri Jun 11 06:19:06 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id GAA13192
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 06:19:06 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BFE1D44474; Fri, 11 Jun 1999 06:18:50 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A371944471; Fri, 11 Jun 1999 06:18:50 -0400 (EDT)
Received: from omzrelay02.mcit.com (beta.mcit.com [199.249.19.244])
	by segue.merit.edu (Postfix) with ESMTP id 476474446B
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 06:18:49 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38417)
 id <0FD500501RBC1I@firewall.mcit.com> for aaa-wg@merit.edu; Fri,
 11 Jun 1999 10:18:48 +0000 (GMT)
Received: from ndcrelay2.mcit.com ([166.37.172.6])
 by firewall.mcit.com (PMDF V5.2-32 #38417)
 with ESMTP id <0FD5008BJRBB1V@firewall.mcit.com>; Fri,
 11 Jun 1999 10:18:48 +0000 (GMT)
Received: from omzmta01.mcit.com (omzmta01.mcit.com [166.37.194.119])
 by ndcrelay2.mcit.com (8.8.7/) with ESMTP	id KAA27675; Fri,
 11 Jun 1999 10:15:10 +0000 (GMT)
Received: from c25776a ([166.44.175.124])
 by omzmta01.mcit.com (InterMail v03.02.05 118 121 101)
 with SMTP id <19990611101842.QEFY1092@c25776a>; Fri, 11 Jun 1999 10:18:42 +0000
Date: Fri, 11 Jun 1999 05:18:47 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
In-reply-to: <3760CCFE.73BA342B@lmf.ericsson.se>
To: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Cc: aaa-wg@merit.edu, david.burdett@mondex.com,
        "Oran@Cisco.Com" <oran@cisco.com>, stephen.thomas@transnexus.com,
        bernarda@microsoft.com
Message-id: <NBBBIIJFOKPMFOOILMBKKEMOECAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Jari,

I believe you have tabled an excellent set of questions that may help in
answering the questions about AAA, IOTP and OSP. Would suggest we find a way
to discuss them with the folks interested in these topics. My 1st two cents
is that it is useful to have internal accounting mechanisms and data formats
between departments and OSS components that mirror external ones, for
clarity and expediency. Am not sure about the trade-offs in performance and
scalability and would suggest implementers to state their estimates. As a
priority, I believe OSS with lower complexity and cost should be the top
design target, since computing power seems to get cheaper all the time. Or
are we network engineers here ahead of our headlights and let e-commerce
folks contribute?

There are other interesting aspects, such as: Carry a telephony payment info
in the signaling protocol (SIP, H.323) or in a separate ("pricing, usage and
settlement") layer. Just to remind folks we have a difficult and interesting
problem space, far beyond RADIUS and DIAMETER IMHO.

>
> 	- Accounting and trading protocols differ in the
> 	  sense that often at accounting we look at the
> 	  _bulk_ problem while trading and e-commerce
> 	  looks at single transactions between two peers.
>
> 	  Of course, this doesn't necessarily mean
> 	  that e.g. IOTP would be unsuitable for use
> 	  as an accounting protocol. We should perform
> 	  an analysis of what IOTP can actually do and
> 	  place the results in the draft, looking at
> 	  all the same issues we have already looked
> 	  at for the other mechanisms.
>
> 	- Another difference is that in accounting we
> 	  usually have agreements in place beforehand,
> 	  while in e-commerce we wish to enable previously
> 	  unknown peers to engage in transactions.
>
> 	- A third difference is that in accounting we
> 	  don't usually transfer money; it happens
> 	  later.
>
> 	  Of course, there might be some value in
> 	  a combined approach where both immediate
> 	  e-cash payments and we-pay-at-the-end-of-month
> 	  model would fit the same framework.
>
> 	- How do the trading/e-commerce mechanisms and
> 	  IOTP in particular handle roaming situations,
> 	  where there'd be more than two entities involved
> 	  in a transaction? Based on some pictures I've
> 	  seen in the IOTP working group I believe it
> 	  can handle this, but can somebody confirm this?

Henry

> -----Original Message-----
> From: lmfjaar@lmf.ericsson.se [mailto:lmfjaar@lmf.ericsson.se]On Behalf
> Of Jari Arkko
> Sent: Friday, June 11, 1999 3:47 AM
> To: Henry Sinnreich
> Cc: aaa-wg@merit.edu; david.burdett@mondex.com; Oran@Cisco.Com;
> stephen.thomas@transnexus.com; bernarda@microsoft.com
> Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
>
>
>
> >Though it is a very systematic approach, I am intrigued why
> >The Open Settlement Protocol
> ><draft-thomas-mime-osp-token-00.txt> , and
> >The Internet Open Trading Protocol
> >draft-ietf-trade-iotp-v1.0-protocol-03.txt>
> >are not included in the discussion or in the references.
>
> Well, we've certainly been aware of IOTP at least (though OSP is
> news to me). There has been a discussion on the AAA list on
> the subject as well, perhaps concentrating more on AAA in
> general than accounting in particular. The discussion took
> place at the end of 1998, and participants in that discussion
> included at least you Henry, Hannu Nikkanen, Pat Calhoun, and
> David Burdett. (Some people in the discussion believed e-commerce
> and AAA are very much related, some believed they are the same
> thing but for a very different purpose, and some believed there'd
> be value in combining them or using the same mechanisms.)
>
> We'd very much like to include text in the draft about
> IOTP and other similar mechanisms. Perhaps you Henry have
> some text that describes your opinion of how accounting and
> IOTP/OSP/... relate and what are the possibilties these
> mechanisms offer for the AAA?
>
> Also, I might just kick off discussions by making some
> initial comments on what I think the relationships are:
>
> 	- Accounting and trading protocols differ in the
> 	  sense that often at accounting we look at the
> 	  _bulk_ problem while trading and e-commerce
> 	  looks at single transactions between two peers.
>
> 	  Of course, this doesn't necessarily mean
> 	  that e.g. IOTP would be unsuitable for use
> 	  as an accounting protocol. We should perform
> 	  an analysis of what IOTP can actually do and
> 	  place the results in the draft, looking at
> 	  all the same issues we have already looked
> 	  at for the other mechanisms.
>
> 	- Another difference is that in accounting we
> 	  usually have agreements in place beforehand,
> 	  while in e-commerce we wish to enable previously
> 	  unknown peers to engage in transactions.
>
> 	- A third difference is that in accounting we
> 	  don't usually transfer money; it happens
> 	  later.
>
> 	  Of course, there might be some value in
> 	  a combined approach where both immediate
> 	  e-cash payments and we-pay-at-the-end-of-month
> 	  model would fit the same framework.
>
> 	- How do the trading/e-commerce mechanisms and
> 	  IOTP in particular handle roaming situations,
> 	  where there'd be more than two entities involved
> 	  in a transaction? Based on some pictures I've
> 	  seen in the IOTP working group I believe it
> 	  can handle this, but can somebody confirm this?
>
> Jari
> ----
> Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
> Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
> Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.
>



From owner-aaa-bof@merit.edu  Fri Jun 11 07:39:42 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id HAA13831
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 07:39:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4816F4446B; Fri, 11 Jun 1999 07:39:25 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2C6064446D; Fri, 11 Jun 1999 07:39:25 -0400 (EDT)
Received: from pegasus.group5.co.uk (mailhost.group5.co.uk [193.128.238.226])
	by segue.merit.edu (Postfix) with ESMTP id 4E33F4446B
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 07:39:18 -0400 (EDT)
Received: from GK-Portable (unverified [62.188.133.117]) by pegasus.group5.co.uk
 (Rockliffe SMTPRA 2.1.5) with SMTP id <B0000815869@pegasus.group5.co.uk>;
 Fri, 11 Jun 1999 12:31:01 +0100
Message-Id: <3.0.32.19990611114940.006934e8@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Fri, 11 Jun 1999 12:39:08 +0100
To: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
Cc: aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 11:46 11/06/99 +0300, Jari Arkko wrote:

>Also, I might just kick off discussions by making some
>initial comments on what I think the relationships are:

Interesting comments...  would I be missing anything vital if I tried to
summarize that by saying:

  An accounting protocol deals with metering (recording details) of an ongoing
  relationship (or chain of relationships), where a trading protocol deals
  with establishing a non repudiable [sp?] proof of a specific transaction.

?


>	- Accounting and trading protocols differ in the
>	  sense that often at accounting we look at the
>	  _bulk_ problem while trading and e-commerce
>	  looks at single transactions between two peers.
>
>	  Of course, this doesn't necessarily mean
>	  that e.g. IOTP would be unsuitable for use
>	  as an accounting protocol. We should perform
>	  an analysis of what IOTP can actually do and
>	  place the results in the draft, looking at
>	  all the same issues we have already looked
>	  at for the other mechanisms.
>
>	- Another difference is that in accounting we
>	  usually have agreements in place beforehand,
>	  while in e-commerce we wish to enable previously
>	  unknown peers to engage in transactions.
>
>	- A third difference is that in accounting we
>	  don't usually transfer money; it happens
>	  later.
>
>	  Of course, there might be some value in
>	  a combined approach where both immediate
>	  e-cash payments and we-pay-at-the-end-of-month
>	  model would fit the same framework.
>
>	- How do the trading/e-commerce mechanisms and
>	  IOTP in particular handle roaming situations,
>	  where there'd be more than two entities involved
>	  in a transaction? Based on some pictures I've
>	  seen in the IOTP working group I believe it
>	  can handle this, but can somebody confirm this?

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-aaa-bof@merit.edu  Fri Jun 11 08:22:18 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA14354
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 08:22:18 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id E66054446B; Fri, 11 Jun 1999 08:22:00 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id CBDE04446D; Fri, 11 Jun 1999 08:22:00 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5])
	by segue.merit.edu (Postfix) with ESMTP id 475324446B
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 08:21:59 -0400 (EDT)
Received: from lmf.lmf.ericsson.se (umail.lmf.ericsson.se [131.160.11.2])
	by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with ESMTP id OAA09571;
	Fri, 11 Jun 1999 14:21:45 +0200 (MET DST)
Received: from lmf.ericsson.se by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id PAA11415; Fri, 11 Jun 1999 15:21:12 +0300 (EET DST)
Message-ID: <3760FF36.B1477B52@lmf.ericsson.se>
Date: Fri, 11 Jun 1999 15:21:10 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Graham Klyne <GK@dial.pipex.com>
Cc: aaa-wg@merit.edu
Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
References: <3.0.32.19990611114940.006934e8@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>Interesting comments...  would I be missing anything vital if I
>tried to summarize that by saying:
>
>  An accounting protocol deals with metering (recording details) of
>  an ongoing relationship (or chain of relationships), where a trading
>  protocol deals with establishing a non repudiable [sp?] proof of
>  a specific transaction.

That's pretty good.

When this gets ugly, though, is when we push a little bit the accounting
case from a simple one to a complex one. Say, accounting between
two members of a global ISP roaming association that don't trust each
other and offer limited credit. Then you get a) no (direct) previous
agreement, b) non-repudiation as a requirement, and c) transaction
per single event => the definitions move closer. Or perhaps we are
saying that if the case is as complex as this, one should use trading
protocols?

Jari
---- 
Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.


From owner-aaa-bof@merit.edu  Fri Jun 11 16:44:53 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA21885
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 16:44:53 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0E0AD4445D; Fri, 11 Jun 1999 16:44:37 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id DC5E344463; Fri, 11 Jun 1999 16:44:36 -0400 (EDT)
Received: from keith.lloyd.com (keith.lloyd.com [158.222.1.2])
	by segue.merit.edu (Postfix) with ESMTP id 81A714445D
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 16:44:35 -0400 (EDT)
Received: from murray (root@keith.lloyd.com [158.222.1.2])
	by keith.lloyd.com (8.9.3/8.9.1) with SMTP id NAA20079
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 13:44:34 -0700 (PDT)
Message-Id: <3.0.6.32.19990611133856.009ab7f0@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 11 Jun 1999 13:38:56 -0700
To: aaa-wg@merit.edu
From: Brian Lloyd <brian@lloyd.com>
Subject: RE:  AAA meeting in Oslo?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

We believe that we have discovered what happened WRT scheduling the AAA WG
meetings at Oslo.  We are in the process of getting things "fixed."  Right
now it looks like the schedule will end up with one meeting on Wednesday
and one on Friday morning.  Since I suspect that there are a number of
people planning to depart Oslo on Friday morning, we will try to get
something sooner.


Brian Lloyd                                    Lucent Technologies
brian@lloyd.com                                3461 Robin Lane, Suite 1
http://www.livingston.com                      Cameron Park, CA  95682
+1.530.676.6513 - voice                        +1.530.676.3442 - fax



From owner-aaa-bof@merit.edu  Fri Jun 11 17:07:27 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA22090
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 17:07:27 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DD8BE44461; Fri, 11 Jun 1999 17:07:10 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C30D644463; Fri, 11 Jun 1999 17:07:10 -0400 (EDT)
Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123])
	by segue.merit.edu (Postfix) with SMTP id 770A344461
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 17:07:07 -0400 (EDT)
Received: from 157.54.9.123 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 11 Jun 1999 14:05:43 -0700 (Pacific Daylight Time)
Received: by INET-IMC-03 with Internet Mail Service (5.5.2524.0)
	id <MX3LFJN4>; Fri, 11 Jun 1999 14:05:43 -0700
Message-ID: <7CD674FF54FBD21181D800805F57CD54038C2F27@RED-MSG-44>
From: Bernard Aboba <bernarda@microsoft.com>
To: Jari Arkko <Jari.Arkko@lmf.ericsson.se>,
        Henry Sinnreich <henry.sinnreich@wcom.com>
Cc: aaa-wg@merit.edu, david.burdett@mondex.com,
        "Oran@Cisco.Com" <oran@cisco.com>, stephen.thomas@transnexus.com
Subject: RE: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
Date: Fri, 11 Jun 1999 14:05:37 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

As Jari noted, there is a distinction between accounting
and settlement. Accounting is merely the act of collecting data
which may subsequently be used for settlement. As I see it, 
IOTP is not an accounting protocol and was therefore not discussed
in the Accounting Management draft. 


From owner-aaa-bof@merit.edu  Fri Jun 11 17:31:59 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA22514
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 17:31:59 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 753C244467; Fri, 11 Jun 1999 17:31:23 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 44C8544471; Fri, 11 Jun 1999 17:31:23 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id 3109144467
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 17:31:22 -0400 (EDT)
Received: from mci.net ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JCA661IES68WW469@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Fri, 11 Jun 1999 17:31:20 EDT
Date: Fri, 11 Jun 1999 14:31:19 -0700
From: Paul Krumviede <paul@mci.net>
Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
To: Bernard Aboba <bernarda@microsoft.com>
Cc: Jari Arkko <Jari.Arkko@lmf.ericsson.se>,
        Henry Sinnreich <henry.sinnreich@wcom.com>, aaa-wg@merit.edu,
        david.burdett@mondex.com, "Oran@Cisco.Com" <oran@cisco.com>,
        stephen.thomas@transnexus.com
Message-id: <37618027.943FBBCA@mci.net>
Organization: MCI WorldCom
MIME-version: 1.0
X-Mailer: Mozilla 4.6 [en] (Win98; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
References: <7CD674FF54FBD21181D800805F57CD54038C2F27@RED-MSG-44>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Bernard Aboba wrote:
> 
> As Jari noted, there is a distinction between accounting
> and settlement. Accounting is merely the act of collecting data
> which may subsequently be used for settlement. As I see it,
> IOTP is not an accounting protocol and was therefore not discussed
> in the Accounting Management draft.

This is a much more succinct version of what I was attempting to
write. Then there are things in IOTP such as bill presentation
that may not be part of accounting protocol.

-paul


From owner-aaa-bof@merit.edu  Fri Jun 11 17:59:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA22694
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 17:59:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5E30944464; Fri, 11 Jun 1999 17:59:33 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 4146C44465; Fri, 11 Jun 1999 17:59:33 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id 09CE044464
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 17:59:32 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA21645;
	Fri, 11 Jun 1999 14:59:29 -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.105.47])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id OAA24020;
	Fri, 11 Jun 1999 14:59:25 -0700 (PDT)
Received: from mordor by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA28724; Fri, 11 Jun 1999 14:59:23 -0700
Date: Fri, 11 Jun 1999 14:59:33 -0700 (PDT)
From: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Reply-To: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Subject: RE:  AAA meeting in Oslo?
To: Brian Lloyd <brian@lloyd.com>
Cc: aaa-wg@merit.edu
In-Reply-To: "Your message with ID" <3.0.6.32.19990611133856.009ab7f0@127.0.0.1>
Message-ID: <Roam.SIMC.2.0.6.929138373.30977.pcalhoun@hsmpka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

> We believe that we have discovered what happened WRT scheduling the AAA WG
> meetings at Oslo.  We are in the process of getting things "fixed."  Right
> now it looks like the schedule will end up with one meeting on Wednesday
> and one on Friday morning.  Since I suspect that there are a number of
> people planning to depart Oslo on Friday morning, we will try to get
> something sooner.
> 
> 
> Brian Lloyd                                    Lucent Technologies
> brian@lloyd.com                                3461 Robin Lane, Suite 1
> http://www.livingston.com                      Cameron Park, CA  95682
> +1.530.676.6513 - voice                        +1.530.676.3442 - fax
> 
> 

Another good reason for *not* having it on Friday is that the Mobile-IP Wg is
meeting then, and there is *alot* of interest in that WG about using AAA.

PatC



From owner-aaa-bof@merit.edu  Fri Jun 11 19:35:48 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id TAA23892
	for <aaa-wg-archive@nic.merit.edu>; Fri, 11 Jun 1999 19:35:48 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A653244468; Fri, 11 Jun 1999 19:35:30 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8A73E44469; Fri, 11 Jun 1999 19:35:30 -0400 (EDT)
Received: from mondex1fd.mondex.com (mondex1fd.mondex.com [62.172.111.130])
	by segue.merit.edu (Postfix) with SMTP id F215544468
	for <aaa-wg@merit.edu>; Fri, 11 Jun 1999 19:35:27 -0400 (EDT)
Received: from MONDEX1FD [62.172.111.130]
	(HELO localhost)
	by mondex1fd.mondex.com (AltaVista Mail V2.0J/2.0J BL25J listener)
	id 0000_0050_3761_9c07_8026;
	Sat, 12 Jun 1999 00:30:15 +0100
Message-Id: <C1E11A7F1A7BD211AF230000F8078A745FCAE5@mondex1is.mondex.com>
From: David Burdett <David.Burdett@MONDEX.com>
To: Henry Sinnreich <henry.sinnreich@wcom.com>,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Cc: aaa-wg@merit.edu, "Oran@Cisco.Com" <oran@cisco.com>,
        stephen.thomas@transnexus.com, bernarda@microsoft.com,
        Don Eastlake <dee3@torque.pothole.com>
Subject: RE: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
Date: Sat, 12 Jun 1999 00:32:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BEB462.ADCF6F00"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BEB462.ADCF6F00
Content-Type: text/plain;
	charset="iso-8859-1"

I thought I'd contribute some comments on the relatiohship between IOTP and
AAA that Jari has written. Please, please comment further. These are just
initial thoughts.

David Burdett

> ----------
> From: 	Jari Arkko[SMTP:Jari.Arkko@lmf.ericsson.se]
> Sent: 	11 June 1999 01:46
> To: 	Henry Sinnreich
> Cc: 	aaa-wg@merit.edu; david.burdett@mondex.com; Oran@Cisco.Com;
> stephen.thomas@transnexus.com; bernarda@microsoft.com
> Subject: 	Re: ships in the night (was I-D
> ACTION:draft-aboba-acct-01.txt)
> 
> 
> >Though it is a very systematic approach, I am intrigued why
> >The Open Settlement Protocol
> ><draft-thomas-mime-osp-token-00.txt> , and
> >The Internet Open Trading Protocol
> >draft-ietf-trade-iotp-v1.0-protocol-03.txt>
> >are not included in the discussion or in the references.
> 
> Well, we've certainly been aware of IOTP at least (though OSP is
> news to me). There has been a discussion on the AAA list on
> the subject as well, perhaps concentrating more on AAA in
> general than accounting in particular. The discussion took
> place at the end of 1998, and participants in that discussion
> included at least you Henry, Hannu Nikkanen, Pat Calhoun, and
> David Burdett. (Some people in the discussion believed e-commerce
> and AAA are very much related, some believed they are the same
> thing but for a very different purpose, and some believed there'd
> be value in combining them or using the same mechanisms.)
> 
> We'd very much like to include text in the draft about
> IOTP and other similar mechanisms. Perhaps you Henry have
> some text that describes your opinion of how accounting and
> IOTP/OSP/... relate and what are the possibilties these
> mechanisms offer for the AAA? 
> 
> Also, I might just kick off discussions by making some
> initial comments on what I think the relationships are:
> 
> 	- Accounting and trading protocols differ in the
> 	  sense that often at accounting we look at the
> 	  _bulk_ problem while trading and e-commerce
> 	  looks at single transactions between two peers.
## Although e-commerce may seem to be between two parties, in many cases it
is not. For example a business may rely on third parties to provides
services such as accept a payment, deliver the goods, calculate the tax due,
etc.##

> 	  Of course, this doesn't necessarily mean
> 	  that e.g. IOTP would be unsuitable for use
> 	  as an accounting protocol. We should perform
> 	  an analysis of what IOTP can actually do and
> 	  place the results in the draft, looking at
> 	  all the same issues we have already looked
> 	  at for the other mechanisms.
## IOTP consists of two parts:
*	a "messaging architecture" that consists of a number of separate
"layers" which have been designed in a generic way to support the exchange
of XML data between parties on the internet, and
*	implementations of the messaging architecture to support some
specific business processes around e-commerce such as a business to consumer
purchase.

Although the latter is specific to a particular domain (e-commerce) the
former is hopefully more widely applicable. In the attached file is a brief
description of the architecture. If you want more detailed information I can
send you a powerpoint presentation that I gave at the last IETF meeting in
Minneapolis.
 <<XML Messaging Overview.txt>> 
##

> 	- Another difference is that in accounting we
> 	  usually have agreements in place beforehand,
> 	  while in e-commerce we wish to enable previously
> 	  unknown peers to engage in transactions.
## In business to business e-commerce there is usually pre-existing
relationshipe between the parties involved. There have been several
inquiries about people wanting to use IOTP for business-to-business. ##

> 	- A third difference is that in accounting we
> 	  don't usually transfer money; it happens
> 	  later.
## IOTP is designed to encapsulate any payment protocol. This means you
could have a "payment" which was really no more than "charge $xx to my
account for later billing". You could then actually do the billing using
IOTP by sending the statement by email and, say, get an electronic check as
payment by email in return. Alternatively you could use one of the
"bill-pay" approaches such as IFX. ##

> 	  Of course, there might be some value in
> 	  a combined approach where both immediate
> 	  e-cash payments and we-pay-at-the-end-of-month
> 	  model would fit the same framework.
## Agreed ##

> 	- How do the trading/e-commerce mechanisms and
> 	  IOTP in particular handle roaming situations,
> 	  where there'd be more than two entities involved
> 	  in a transaction? Based on some pictures I've
> 	  seen in the IOTP working group I believe it
> 	  can handle this, but can somebody confirm this?
## I'm not sure what you mean by "roaming" ... if you let me know I'll
gladly answer your question ;)"

David

> Jari
> ---- 
> Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
> Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
> Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.
> 
> 
> mailto:<david.burdett@mondex.com>
> Mondex International, US Advanced Technology Office
> 111 Pine St, 6th Floor, San Francisco, CA 94111
> Tel/Voicemail: +1 415 645 6973	Fax: +1 415 956 9370
> 


**********************************************************************************************

This Email and any attached files are confidential and may also be privileged. 
If you are not the intended recipient, please notify the postmaster using email 
address postmaster@mondex.com or call +44 171 557 5000 and ask for the 
IT Helpdesk.  You should not copy this email and any attached files, use them 
for any purpose or disclose the contents to any other person; all copies of the 
Email and associated files in your possession should be destroyed.

Mondex International Limited
47-53 Cannon Street
London EC4M 5SQ
United Kingdom
Registered No: 3122085, England

Phone:          +44 171 557 5000
Fax:            +44 171 557 5200
Email:          postmaster@mondex.com
WebSite:        http://www.mondexinternational.com

*********************************************************************************************
------_=_NextPart_000_01BEB462.ADCF6F00
Content-Type: text/plain;
	name="XML Messaging Overview.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="XML Messaging Overview.txt"

XML MESSAGING OVERVIEW

These are ideas that are based on methods and techniques contained =
within the current IOTP specification. It is the intention that these =
ideas are separated from the current IOTP specification and =
incorporated into a separate standard involving other areas of =
expertise to help make sure they widely and generally applicable.

XML Messaging consits of three layers:
	- a "wrapper" layer which defines how to surround XML data with useful =
additional information to identify it and preserve its authenticity
	- a "document exchange" layer which describes how data wrapped using =
the approach defined in the first layer can be swapped between two =
parties to implement all, or part, of a process
	- some "simple standard messaging transactions" which use document =
exchanges to implement some useful functions.

WRAPPER LAYER
The first layer specifies standard approaches to the basic wrapping of =
data you want to send to someone with some useful things. It includes:
	- a method of "labelling" XML data with tagged information that =
includes, for example, a globally unique id, timetamp, document =
purpose, software used to generate the document, related documents, etc
	- a method of digitally signing the data when required - leveraging =
the work being done by the W3C/IETF dsig working group
	- a method of arbitrarily encapsulating any data, e.g. binary data, =
inside XML
	- a method of specifying both the nature and position of technical =
errors in an XML document.

DOCUMENT EXCHANGE LAYER
The second layer uses the first layer to implement a basic "document =
exchange" that can support a business process, for example. A document =
exchange is essentially a request-response pair with optional extra =
swaps of data inbetween the request and response where this is needed, =
for example as in some payment protocols. Examples of "document =
exchanges" include:
	- Payment: making a payment (the request) and getting a receipt (the =
response)
	- Authentication: who are you (the request) and I'm John Doe (the =
response)

... I hope you get the idea.

Specific features include:
	- how to chain document exchanges into something useful.
	- the specification of a "Status" component which provides information =
on the success or failure of any process
	specification on how Status components, together with digital =
signatures, can be used to prove the authenticity of any request
	- how to report errors
	- how to handle idempotency, restarts and recovery.

As an example of chaining docuemt exchanges together, consider:
	- an offer to buy (1st document exchange)
	- making a payment (2nd document exchange), and
	- delivering the goods (3rd document exchange)

However you should only deliver the goods if you *know* the payment is =
successful. This is where the Status component and the digital =
signatures come in. This is much more useful than a single document =
exchange.

USEFUL TRANSACTIONS
The third layer is detailed definitions of some generic instances of =
some useful document exchanges. Specifically:
	- a "transaction status inquiry" which allows inquiries on the current =
status of any document exchange that conforms to the approach described =
above.
	- a "ping" transaction that lets you know if an IOTP server is awake =
and working OK, and finally:
	- an "authentication transaction" which allowa any two parties to =
determine the authenticity of each other.

------_=_NextPart_000_01BEB462.ADCF6F00--


From owner-aaa-bof@merit.edu  Sat Jun 12 13:37:33 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA01780
	for <aaa-wg-archive@nic.merit.edu>; Sat, 12 Jun 1999 13:37:33 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4583D44482; Sat, 12 Jun 1999 13:37:16 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 22B3644483; Sat, 12 Jun 1999 13:37:16 -0400 (EDT)
Received: from omzrelay02.mcit.com (beta.mcit.com [199.249.19.244])
	by segue.merit.edu (Postfix) with ESMTP id DF87944482
	for <aaa-wg@merit.edu>; Sat, 12 Jun 1999 13:37:14 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38417)
 id <0FD800D016A1D7@firewall.mcit.com> for aaa-wg@merit.edu; Sat,
 12 Jun 1999 17:37:13 +0000 (GMT)
Received: from omzrelay.mcit.com ([166.37.204.49])
 by firewall.mcit.com (PMDF V5.2-32 #38417)
 with ESMTP id <0FD800E3O6A09P@firewall.mcit.com>; Sat,
 12 Jun 1999 17:37:13 +0000 (GMT)
Received: from omzmta02.mcit.com (omzmta02.mcit.com [166.37.194.120])
 by omzrelay.mcit.com (8.8.7/) with ESMTP	id RAA12452; Sat,
 12 Jun 1999 17:38:08 +0000 (GMT)
Received: from c25776a ([166.37.185.87])
 by omzmta02.mcit.com (InterMail v03.02.05 118 120)
 with SMTP id <19990612173711.RYRO642@[166.37.185.87]>; Sat,
 12 Jun 1999 17:37:11 +0000
Date: Sat, 12 Jun 1999 12:37:18 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
In-reply-to: <C1E11A7F1A7BD211AF230000F8078A745FCAE5@mondex1is.mondex.com>
To: David Burdett <David.Burdett@mondex.com>,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Cc: aaa-wg@merit.edu, "Oran@Cisco.Com" <oran@cisco.com>,
        stephen.thomas@transnexus.com, bernarda@microsoft.com,
        Don Eastlake <dee3@torque.pothole.com>
Message-id: <NBBBIIJFOKPMFOOILMBKGEODECAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

David Burdett wrote:
## I'm not sure what you mean by "roaming" ... if you let me know I'll
gladly answer your question ;)"

David, please see the drafts listed at the page of the Roaming Operations WG
at
http://www.ietf.org/html.charters/roamops-charter.html

Henry



From owner-aaa-bof@merit.edu  Mon Jun 14 03:48:11 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id DAA21036
	for <aaa-wg-archive@nic.merit.edu>; Mon, 14 Jun 1999 03:48:11 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 309F744420; Mon, 14 Jun 1999 03:47:54 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0A5B744425; Mon, 14 Jun 1999 03:47:54 -0400 (EDT)
Received: from pegasus.group5.co.uk (mailhost.group5.co.uk [193.128.238.226])
	by segue.merit.edu (Postfix) with ESMTP id 0218D44420
	for <aaa-wg@merit.edu>; Mon, 14 Jun 1999 03:47:51 -0400 (EDT)
Received: from GK-Portable (unverified [62.188.142.65]) by pegasus.group5.co.uk
 (Rockliffe SMTPRA 2.1.5) with SMTP id <B0000816237@pegasus.group5.co.uk>;
 Mon, 14 Jun 1999 08:38:51 +0100
Message-Id: <3.0.32.19990611155117.006a39c0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com (Unverified)
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 14 Jun 1999 08:47:30 +0100
To: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
Cc: aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 15:21 11/06/99 +0300, Jari Arkko wrote:
>
>>Interesting comments...  would I be missing anything vital if I
>>tried to summarize that by saying:
>>
>>  An accounting protocol deals with metering (recording details) of
>>  an ongoing relationship (or chain of relationships), where a trading
>>  protocol deals with establishing a non repudiable [sp?] proof of
>>  a specific transaction.
>
>That's pretty good.
>
>When this gets ugly, though, is when we push a little bit the accounting
>case from a simple one to a complex one. Say, accounting between
>two members of a global ISP roaming association that don't trust each
>other and offer limited credit. Then you get a) no (direct) previous
>agreement, b) non-repudiation as a requirement, and c) transaction
>per single event => the definitions move closer. Or perhaps we are
>saying that if the case is as complex as this, one should use trading
>protocols?

Sounds like a case for trading AND accounting protocols?

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-aaa-bof@merit.edu  Mon Jun 14 08:07:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA23426
	for <aaa-wg-archive@nic.merit.edu>; Mon, 14 Jun 1999 08:07:15 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0B66F44402; Mon, 14 Jun 1999 08:06:59 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E3E1B44420; Mon, 14 Jun 1999 08:06:58 -0400 (EDT)
Received: from omzrelay01.mcit.com (alpha.mcit.com [199.249.19.243])
	by segue.merit.edu (Postfix) with ESMTP id BB95944402
	for <aaa-wg@merit.edu>; Mon, 14 Jun 1999 08:06:57 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38416)
 id <0FDB00J01GBKHN@firewall.mcit.com> for aaa-wg@merit.edu; Mon,
 14 Jun 1999 12:06:57 +0000 (GMT)
Received: from ndcrelay.mcit.com ([166.37.172.49])
 by firewall.mcit.com (PMDF V5.2-32 #38416)
 with ESMTP id <0FDB00LRYGBKC0@firewall.mcit.com>; Mon,
 14 Jun 1999 12:06:56 +0000 (GMT)
Received: from omzmta04.mcit.com (omzmta04.mcit.com [166.37.194.122])
 by ndcrelay.mcit.com (8.8.7/) with ESMTP	id MAA03707; Mon,
 14 Jun 1999 12:06:17 +0000 (GMT)
Received: from c25776a ([166.44.186.67])
 by omzmta04.mcit.com (InterMail v03.02.05 118 121 101)
 with SMTP id <19990614120654.VCMS632@c25776a>; Mon, 14 Jun 1999 12:06:54 +0000
Date: Mon, 14 Jun 1999 07:07:02 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: ships in the night (was I-D ACTION:draft-aboba-acct-01.txt)
In-reply-to: <3.0.32.19990611155117.006a39c0@pop.dial.pipex.com>
To: Graham Klyne <GK@Dial.pipex.com>, Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Cc: aaa-wg@merit.edu
Message-id: <NBBBIIJFOKPMFOOILMBKEEPDECAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Another item of interest is the use and efficiency of Tag-Value pairs vs.
XML processing.
Would be interested in comments by implementers.

Thanks, Henry



From owner-aaa-bof@merit.edu  Tue Jun 22 12:05:27 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA06704
	for <aaa-wg-archive@nic.merit.edu>; Tue, 22 Jun 1999 12:05:27 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id AD7FD44429; Tue, 22 Jun 1999 12:05:09 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9368D44433; Tue, 22 Jun 1999 12:05:09 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id AA09F44429
	for <aaa-wg@merit.edu>; Tue, 22 Jun 1999 12:05:08 -0400 (EDT)
Received: from wcom.com ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JCP7XW77SS934Q5Y@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Tue, 22 Jun 1999 12:05:07 EDT
Date: Tue, 22 Jun 1999 09:04:39 -0700
From: Paul Krumviede <Paul.Krumviede@wcom.com>
Subject: Oslo agenda and solicitation for items
To: AAA WG <aaa-wg@merit.edu>
Message-id: <376FB417.50C25863@wcom.com>
Organization: MCI WorldCom
MIME-version: 1.0
X-Mailer: Mozilla 4.6 [en] (Win98; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

We've been allocated 2 slots for the AAA WG meeting in Oslo:
	Wednesday, July 14 at 1530-1730
	Friday, July 16 at 0900-1130

I'd like to see us discuss the outputs from the subgroups (e.g. the
authorization and accounting groups), and would like to solicit
suggestions for other agenda items. Please send them to Brian
and me.

thanks,
-paul


From owner-aaa-bof@merit.edu  Tue Jun 22 12:08:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA06736
	for <aaa-wg-archive@nic.merit.edu>; Tue, 22 Jun 1999 12:08:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5472444433; Tue, 22 Jun 1999 12:08:31 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 3751844438; Tue, 22 Jun 1999 12:08:31 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id DDB0644433
	for <aaa-wg@merit.edu>; Tue, 22 Jun 1999 12:08:29 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA14697;
	Tue, 22 Jun 1999 09:08:28 -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.51.47])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id JAA23632;
	Tue, 22 Jun 1999 09:08:28 -0700 (PDT)
Received: from mordor by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id JAA28631; Tue, 22 Jun 1999 09:08:26 -0700
Date: Tue, 22 Jun 1999 09:08:07 -0700 (PDT)
From: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Reply-To: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Subject: Re: Oslo agenda and solicitation for items
To: Paul Krumviede <Paul.Krumviede@wcom.com>
Cc: AAA WG <aaa-wg@merit.edu>
In-Reply-To: "Your message with ID" <376FB417.50C25863@wcom.com>
Message-ID: <Roam.SIMC.2.0.6.930067687.8150.pcalhoun@hsmpka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Has there been any work in the authentication subgroup?

PatC



From owner-aaa-bof@merit.edu  Tue Jun 22 12:19:39 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA06827
	for <aaa-wg-archive@nic.merit.edu>; Tue, 22 Jun 1999 12:19:38 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 01C1E44437; Tue, 22 Jun 1999 12:19:20 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D8A2F44439; Tue, 22 Jun 1999 12:19:19 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id E5A2744437
	for <aaa-wg@merit.edu>; Tue, 22 Jun 1999 12:19:18 -0400 (EDT)
Received: from wcom.com ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JCP8GYJ5Z2934Q5Y@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Tue, 22 Jun 1999 12:19:16 EDT
Date: Tue, 22 Jun 1999 09:19:16 -0700
From: Paul Krumviede <Paul.Krumviede@wcom.com>
Subject: Re: Oslo agenda and solicitation for items
To: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>,
        AAA WG <aaa-wg@merit.edu>
Message-id: <376FB784.6D3F534E@wcom.com>
Organization: MCI WorldCom
MIME-version: 1.0
X-Mailer: Mozilla 4.6 [en] (Win98; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
References: <Roam.SIMC.2.0.6.930067687.8150.pcalhoun@hsmpka>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

"pcalhoun@eng.sun.com" wrote:
> 
> Has there been any work in the authentication subgroup?
> 
> PatC

Not that I am explicitly aware of, although I think that Alex Latzko
was doing something recently on this front.

-paul


From owner-aaa-bof@merit.edu  Wed Jun 23 07:20:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id HAA16921
	for <aaa-wg-archive@nic.merit.edu>; Wed, 23 Jun 1999 07:20:23 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4E6324443C; Wed, 23 Jun 1999 07:20:05 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2C84744448; Wed, 23 Jun 1999 07:20:05 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 14B004443C
	for <aaa-wg@merit.edu>; Wed, 23 Jun 1999 07:20:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25185;
	Wed, 23 Jun 1999 07:20:00 -0400 (EDT)
Message-Id: <199906231120.HAA25185@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: aaa-wg@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-aaa-authorization-reqs-00.txt
Date: Wed, 23 Jun 1999 07:20:00 -0400
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Authentication, Authorization and Accounting Working Group of the IETF.

	Title		: AAA Authorization Architecture and Requirements
	Author(s)	: J. Vollbrecht, P. Calhoun, S. Farrell, M. Holdrege, 
                          G. Gross, L. Gommans, B. de Bruijn, D. Spence
	Filename	: draft-ietf-aaa-authorization-reqs-00.txt
	Pages		: 70
	Date		: 22-Jun-99
	
This memo serves as the base requirements for Authorization of
Internet Resources and Services (AIRS).  It presents an architectural
framework for understanding the authorization of Internet resources
and services and derives requirements for authorization protocols.
The authorization needs of several different applications are
considered in a lengthy appendix.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-aaa-authorization-reqs-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990622131916.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-aaa-authorization-reqs-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990622131916.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-aaa-bof@merit.edu  Wed Jun 23 08:50:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA17590
	for <aaa-wg-archive@nic.merit.edu>; Wed, 23 Jun 1999 08:50:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0920D44450; Wed, 23 Jun 1999 08:50:32 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D87CC44453; Wed, 23 Jun 1999 08:50:31 -0400 (EDT)
Received: from cheetah.safari.net (cheetah.safari.net [206.96.248.28])
	by segue.merit.edu (Postfix) with SMTP id 4CD2F44450
	for <aaa-wg@merit.edu>; Wed, 23 Jun 1999 08:50:30 -0400 (EDT)
Received: (qmail 14223 invoked from network); 23 Jun 1999 12:50:29 -0000
Received: from rhino.safari.net (HELO noc) (qmailr@208.235.96.54)
  by smtp.safari.net with SMTP; 23 Jun 1999 12:50:29 -0000
Received: (qmail 23081 invoked by uid 500); 23 Jun 1999 12:50:28 -0000
From: xs-dated-c435c26fe1fd0080@rhino.safari.net
Received: (qmail 23069 invoked from network); 23 Jun 1999 12:50:26 -0000
Received: from katanga.safari.net (HELO mail1.safari.net) (qmailr@206.96.248.4) by rhino.safari.net with SMTP; 23 Jun 1999 12:50:26 -0000
Received: (qmail 11579 invoked by uid 2600); 23 Jun 1999 12:50:20 -0000
Received: (qmail 11574 invoked from network); 23 Jun 1999 12:50:18 -0000
Received: from loki.ietf.org (132.151.1.177) by mail1.safari.net with SMTP; 23 Jun 1999 12:50:18 -0000
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA03216 for ietf-123-outbound.09@ietf.org; Wed, 23 Jun 1999 07:45:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA03096 for <all-ietf@loki.ietf.org>; Wed, 23 Jun 1999 07:23:57 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25185; Wed, 23 Jun 1999 07:20:00 -0400 (EDT)
Message-Id: <199906231120.HAA25185@ietf.org>
Mime-Version: 1.0
X-Security: MIME headers sanitized on rhino See http://www.wolfenet.com/~jhardin/procmail-security.html for details. $Revision: 1.84 $Date: 1999-06-12 12:30:37-07 
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: aaa-wg@merit.edu
Reply-To: Internet-Drafts@odin.ietf.org
Subject: I-D ACTION:draft-ietf-aaa-authorization-reqs-00.txt
Date: Wed, 23 Jun 1999 07:20:00 -0400
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Authentication, Authorization and Accounting Working Group of the IETF.

	Title		: AAA Authorization Architecture and Requirements
	Author(s)	: J. Vollbrecht, P. Calhoun, S. Farrell, M. Holdrege, 
                          G. Gross, L. Gommans, B. de Bruijn, D. Spence
	Filename	: draft-ietf-aaa-authorization-reqs-00.txt
	Pages		: 70
	Date		: 22-Jun-99
	
This memo serves as the base requirements for Authorization of
Internet Resources and Services (AIRS).  It presents an architectural
framework for understanding the authorization of Internet resources
and services and derives requirements for authorization protocols.
The authorization needs of several different applications are
considered in a lengthy appendix.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-aaa-authorization-reqs-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990622131916.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-aaa-authorization-reqs-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990622131916.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-aaa-bof@merit.edu  Fri Jun 25 14:18:37 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id OAA09063
	for <aaa-wg-archive@nic.merit.edu>; Fri, 25 Jun 1999 14:18:37 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3B08944415; Fri, 25 Jun 1999 14:18:28 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1609844427; Fri, 25 Jun 1999 14:18:28 -0400 (EDT)
Received: from mushroom.icoe.att.com (icoe-gate.icoe.att.nl [194.242.71.50])
	by segue.merit.edu (Postfix) with ESMTP id 8610144415
	for <aaa-wg@merit.edu>; Fri, 25 Jun 1999 14:18:25 -0400 (EDT)
Received: by mushroom.icoe.att.com; id TAA12332; Fri, 25 Jun 1999 19:44:55 +0200 (MET DST)
Received: from unknown(135.76.170.11) by mushroom.icoe.att.com via smap (4.0a)
	id xma012327; Fri, 25 Jun 99 19:44:00 +0200
Received: from spinach.icoe.att.com (spinach.icoe.att.com [135.76.170.7])
	by watermelon.icoe.att.com (8.8.8/8.8.8) with ESMTP id UAA19245;
	Fri, 25 Jun 1999 20:21:16 +0200 (MET DST)
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Submission to WG: <draft-bakker-middleware-aaa.txt> - AAA Considerations for Middleware
To: AAA WG <aaa-wg@merit.edu>
Cc: steven@icoe.att.com
X-Organisation: AT&T ICoE
X-Telephone: +31.20.4097.643
X-Fax: +31.20.4531.574
X-Fruit-of-the-day: pistachio
X-Drink-of-the-day: 7-up
X-URL: http://www.icoe.att.com
Comments: Disinformation is not as good as datinformation.
Mime-Version: 1.0
Content-Type: multipart/mixed ;
	boundary="==_Exmh_4016120840"
Date: Fri, 25 Jun 1999 20:12:43 +0100
Message-ID: <9522.930337963@spinach.icoe.att.com>
From: Steven Bakker <steven@icoe.att.com>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

This is a multipart MIME message.

--==_Exmh_4016120840
Content-Type: text/plain; charset=us-ascii

Folks,

I just submitted the enclosed draft to the editor.  I'd like to get 
comments on this, especially whether this is relevant to the WG or I
should go and play somewhere else.

It's a bunch of ideas I came up with regarding AAA (and trust) in a more
advanced services network (middleware and all that jazz).  I think it has
relevance to AAA and perhaps to policy(?)

Thanks in advance,
Steven Bakker

--==_Exmh_4016120840
Content-Type: text/plain ; name="draft-bakker-middleware-considerations-aaa.txt"; charset=us-ascii
Content-Description: draft-bakker-middleware-considerations-aaa.txt







INTERNET-DRAFT                                                 S. Bakker
<draft-bakker-middleware-considerations-aaa.txt>                    AT&T
Expires December 1999                                          June 1999


                   AAA Considerations for Middleware
             draft-bakker-middleware-considerations-aaa.txt

Status of this Memo

   This document is a submission to the AAA Working Group of the
   Internet Engineering Task Force (IETF).  Comments should be submitted
   to the aaa-wg@merit.edu mailing list or the author.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at:

     http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at:

     http://www.ietf.org/shadow.html.

Abstract

   The IETF AAA Working Group is currently looking at defining the
   requirements for Authentication, Authorization and Accounting.
   Various documents have already been written that outline AAA
   requirements for various services and protocols. This document falls
   into that category, as it outlines some ideas for middleware that
   have specific AAA requirements.

1. Introduction

   When talking about AAA, most discussions seem to focus on a model
   whereby a (possibly roaming) user requires access to some resource in
   a pre-determined domain.  Examples are roaming users dialing into a
   foreign ISP and wishing to retrieve their mail from their home ISP.



Bakker                    Expires December 1999                 [Page 1]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


   Another example is an application requesting certain QoS features on
   an end-to-end connection, which requires cooperation between
   intermediate devices and providers.  We will outline another paradigm
   that is best described as a cloud model.

   This cloud model goes much further than the scope of merely the AAA-
   wg and is not easily described in a single document.  However, we
   feel that the idea may pose some additional requirements for AAA.
   Therefore, we won't go into too much detail on the model itself, but
   rather highlight the areas of interest regarding AAA.  For a general
   overview of AAA and the terminology, see [1].

2. The Cloud Model

   In today's Internet, many companies offer content or other services
   over the network. One usually has to subscribe to various services at
   each individual content provider. Subsequently, a user has to
   authenticate herself for each service she uses and will be billed for
   each service separately.

   In the cloud model, the whole network (ISPs, content providers, etc.)
   is viewed as one entity from the user's perspective. The user
   connects to the cloud, authenticates herself and will be able to use
   the services she is subscribe to, such as video-on-demand, voice, e-
   mail, etc. These services need not be provided by the user's ISP
   directly, but can be operated by third parties, which may or may not
   be directly connected to the ISP's infrastructure. The cloud can
   handle the authentication, authorization and accounting of the user's
   activities and present a single bill to the user.

   This cloud model will typically be implemented by a collection of
   middleware products.  A collection of Policy Enforcement Points
   (PEPs) in the ISPs network will act as (proxy-) gateways to the
   various services.

   The importance (and currently lack) of standardization in the
   middleware area has already been stressed in [2], and is not in the
   scope of this document.

 2.1. Terminology

  2.1.1. User

   A user is typically a human, but can also be a network device, an
   application or another network. The cloud model is especially
   focusing on individual human users, but it is not restricted to this.

  2.1.2. ISP and CSP



Bakker                    Expires December 1999                 [Page 2]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


   In the context of the cloud model it is important to distinguish
   between parties that provide access to the Internet (the
   infrastructure) in general, and those that provide one or more
   services over that infrastructure (such as voice, video, etc.). In
   this document we will use the term ISP to denote a party that provide
   access to the infrastructure, and CSP (Content/Service Provider) to
   denote a parties providing services over the infrastructure. In many
   instances (as is currently the predominant case) ISPs will be CSPs to
   a large extent, but it is likely that in the future many if not most
   CSPs will be separate from the ISPs.

 2.2. ISP Functions

   The function of the ISP in this model is to act as a single party
   with which the user deals. It will handle requests for subscription
   to various services (CSPs), transparently authenticate users to CSPs
   and present a single itemized bill to the user. Furthermore, the ISP
   should be able to negotiate QoS parameters/bandwidth reservation with
   any intermediate carriers/ISPs.

 2.3. CSP Functions

   The function of the CSP is to provide some service on top of the IP
   infrastructure (voice, video, data). In the cloud model, the CSP has
   no direct relationship with the end-user, but rather with the user's
   ISP.  This means that the CSP will bill the ISP, rather than the end-
   user, for its services.

 2.4. Example

   A user wants to use a video-on-demand service. The user's ISP has
   agreements with CSPs that offer such a service and offers the user
   the ability to subscribe to one or more of them. This could be done
   by phone, through a web page, a custom application, etc. Once
   registered, the user only needs to authenticate herself once to the
   cloud (ISP) and from then on will be able to use the service. The
   middleware, through the ISP, will transparently take care of
   authentication and authorization of service requests on behalf of the
   user.

   The ISP will then add any charges to the user's bill.

 2.5. Benefits

   Some of the benefits of the cloud model are:

   o Abstraction
     The model adds a layer of abstraction and simplifies access to the



Bakker                    Expires December 1999                 [Page 3]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


     network from the user's point of view.

   o Less complexity at the edges
     Since much of the authentication/authorization will be done on the
     user's behalf by the ISPs PEPs, the actual software needed at the
     user's side need not be very sophisticated.

3. Trust Relationships

   It is clear that in order for the Cloud Model to work trust
   relationships MUST exist between the ISP and CSPs.

 3.1. Direct Trust Relationships

   If trust relationships are to be established directly, ISPs will have
   to set them up with all CSPs whose services they wish to offer to
   their customers. Some ISPs may hand-pick the CSPs whose services they
   wish to offer to their customers, but many will want to allow their
   users to pick anyone they like. Direct trust relationships do not
   scale well here. Due to the large number of ISPs and CSPs (and hence
   the number of trust relationships) direct trust relationships will
   put a strain on the ISP's and CSP's resources (databases,
   administrative personnel, etc.)  to the extent that for some the
   resources needed for managing these relationships may actually start
   to dwarf those needed to operate the service itself.

 3.2. A Broker Model for Trust Relationships

   Most CSPs will not care very much who their customer is, as long as
   they are able and willing to pay.  Compare this to the use of credit
   cards today.  People can order things on-line and both consumer and
   provider have an agreement with a credit card company, which acts as
   a kind of broker in this case.

   A similar construction could be designed for trust relationships
   between CSPs and ISPs. One could think of a (relatively) small number
   of "Trust Relationship Brokers" (TRB), acting as clearing houses for
   trust relationships. In this model, CSPs and ISPs need only to
   maintain trust relationships with one or several of those TRBs and
   CSPs could authenticate ISPs through the TRBs.

   Many issues remain open in a TRB model, such as who is billing whom.
   The CSP could bill the TRB, who could in turn bill the ISP.
   Alternatively, the TRB could be used to only provide or verify
   billing information (such as credit card number, billing address,
   etc.)

 3.3. TR Requirements



Bakker                    Expires December 1999                 [Page 4]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


   It MUST be possible to set up direct trust relationships between ISPs
   and CSPs. Since there is no TRB model in existence today, something
   is needed to bootstrap the Cloud Model.

   It MUST be possible to use a TRB eventually. Whether this will just
   be used for verification and authentication or also as a payment
   clearing house is not clear at the moment. The former requires less
   administration than the latter.

   Perhaps the payment clearing house TRB model is feasible only if the
   TRB is a bank-like institute.

4. AAA Requirements

   In order for this model to be able to work, there are a number of
   requirements on various middleware-related protocols.  AAA is one of
   the key ones.  Let's look at each of the three As (though out of
   order).  In outlining these requirements we follow the guidelines in
   [4].

 4.1. Authentication

   It MUST be possible for the ISP to authenticate on behalf of its
   users. It might be possible to subscribe each user to a CSP
   individually, but since a trust relationship MUST exist between the
   ISP and a CSP, this SHOULD NOT be necessary. Rather, the ISP
   authenticates with one ID (its own) and requests authorization for a
   particular host/service combination.

 4.2. Accounting.

   Accounting is the crux for billing and raises some interesting
   points.  [3] Gives an overview of Accounting Management and we refer
   to that for more in-depth information.

  4.2.1. Inter-domain Accounting

   While inter-domain usage-sensitive accounting is not strictly
   necessary in the cloud model, it SHOULD be provided. It allows the
   ISP and CSP to compare accounting data, thus effectively providing an
   additional integrity check. Since these types of services are still
   in their infancy, we think this type of extra check is crucial in
   debugging.

   Furthermore, real-time inter-domain accounting would allow a user's
   ISP to perform real-time auditing. Real-time auditing is desirable in
   cases where users pre-pay for a service and must be cut off when
   their credit reaches zero (as is currently the case in various mobile



Bakker                    Expires December 1999                 [Page 5]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


   telephony services). If this is to be enabled, it MUST also be
   possible for the user's ISP to tell the CSP to end a particular
   session for a user prematurely, i.e. revoke the authorization for
   user/service combination on the fly.

 4.3. Authorization

   Similar to authentication, the ISP MUST be able to get authorization
   for services on behalf of its users. Part of that authorization will
   be intra-domain ("to which services is the user subscribed?"), and
   part will be inter-domain ("can you send that video to user X?").

   Although strictly speaking intra-domain authorization need not be
   standardized (except within the domain itself), it is probably much
   easier if one (set of) mechanism(s) can be used for both the intra-
   and inter- domain authorization.

  4.3.1. Revoking Authorization

   It MUST be possible to revoke the authorization for any session on
   the fly, as explained above. Complicated models are possible, whereby
   the auditing process triggers a parallel process that kills a
   session, or gives feedback to the Accounting protocol, causing the
   CSP's PEP to eventually drop the session.

   Although interesting, these mechanisms are not strictly necessary in
   the cloud model, since all accesses will go through the ISP's PEPs as
   well.  Therefore, in order to kill a session, the ISP's PEP (acting
   as a proxy between user and CSP) can be told to do this. Of course,
   some mechanism needs to be designed for this, but it's an intra-
   domain problem and requires less urgent attention.

   This does however raise another important issue. At the ISPs side, it
   MUST be possible to uniquely identify a real-time accounting session
   with an ongoing user session.

4. Acknowledgments

   The author would like to thank Ryan Moats and Richard V. Huber for
   their comments and suggestions.

5. References

[1] S. Hares, F. Baker. "Requirements for a General Authentication,
    Authorization and Accounting Protocol." (work in progress), draft-
    ietf-hares-aaa-req.txt, December 1998.





Bakker                    Expires December 1999                 [Page 6]

INTERNET-DRAFT      AAA Considerations for Middleware          June 1999


[2] B. Aiken, J. Strassner, B. Carpenter, I. Foster, C. Lynch, J.  Mam-
    bretty, R. Moore, B. Teitelbaum. "Terminology for describing middle-
    ware for network policy and services." (work in progress), draft-
    aiken-middleware-reqndef-00.txt, April 1999.


[3] B. Aboba, J. Arkko.  "Introduction to Accounting Management." (work
    in progress), draft-aboba-acct-00.txt, August 1998.


[4] S. Bradner. "Key words for use in RFCs to Indicate Requirement Lev-
    els", BCP 14, RFC 2119, March 1997.

Author's Address

    Steven Bakker
    AT&T
    Laarderhoogtweg 25
    1101 EB Amsterdam Zuidoost
    The Netherlands

     Phone: +31 20 4097 643
       Fax: +31 20 4531 574
    E-Mail: steven@icoe.att.com



























Bakker                    Expires December 1999                 [Page 7]

--==_Exmh_4016120840--






From owner-aaa-bof@merit.edu  Fri Jun 25 16:17:51 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA10452
	for <aaa-wg-archive@nic.merit.edu>; Fri, 25 Jun 1999 16:17:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 15E7E44498; Fri, 25 Jun 1999 16:16:45 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8C6D3444AF; Fri, 25 Jun 1999 16:16:39 -0400 (EDT)
Received: from hardees.rutgers.edu (hardees.rutgers.edu [128.6.18.2])
	by segue.merit.edu (Postfix) with ESMTP id 42B14444A9
	for <aaa-wg@merit.edu>; Fri, 25 Jun 1999 16:12:50 -0400 (EDT)
Received: from localhost (latzko@localhost)
	by hardees.rutgers.edu (8.8.8/8.8.8) with ESMTP id QAA04667
	for <aaa-wg@merit.edu>; Fri, 25 Jun 1999 16:13:04 -0400 (EDT)
Date: Fri, 25 Jun 1999 16:13:04 -0400 (EDT)
From: Alexander Latzko <latzko@hardees.Rutgers.EDU>
To: AAA WG <aaa-wg@merit.edu>
Subject: Draft submission
Message-ID: <Pine.SOL.4.10.9906251611240.22603-101000@hardees.rutgers.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1639486704-930341584=:22603"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-1639486704-930341584=:22603
Content-Type: TEXT/PLAIN; charset=US-ASCII


I've just submitted this draft to the internet-drafts folks hopefully
before the deadline.

Its a strawman on the process of authentication transactions.

Comments bricks stones etc

thanks
alex


-- 
latzko@noc.rutgers.edu 		                                n2mlq
Alex Latzko		+1-732-445-5021 (voice)	+1-732-445-2968 (fax)
Rutgers University Computing Services TD:NOG      Backbone Operations
110 Frelinghuysen Road, Piscataway, NJ 08855-8089

---559023410-1639486704-930341584=:22603
Content-Type: APPLICATION/octet-stream; name="id-aaa.txt"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SOL.4.10.9906251613040.22603@hardees.rutgers.edu>
Content-Description: ascii text
Content-Disposition: attachment; filename="id-aaa.txt"


---559023410-1639486704-930341584=:22603--


From owner-aaa-bof@merit.edu  Fri Jun 25 16:20:51 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA10482
	for <aaa-wg-archive@nic.merit.edu>; Fri, 25 Jun 1999 16:20:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A9EA24446A; Fri, 25 Jun 1999 16:20:31 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 881AA4446E; Fri, 25 Jun 1999 16:20:31 -0400 (EDT)
Received: from hardees.rutgers.edu (hardees.rutgers.edu [165.230.165.66])
	by segue.merit.edu (Postfix) with ESMTP id 6E2134446A
	for <aaa-wg@merit.edu>; Fri, 25 Jun 1999 16:20:30 -0400 (EDT)
Received: from localhost (latzko@localhost)
	by hardees.rutgers.edu (8.8.8/8.8.8) with ESMTP id QAA04926
	for <aaa-wg@merit.edu>; Fri, 25 Jun 1999 16:20:44 -0400 (EDT)
Date: Fri, 25 Jun 1999 16:20:44 -0400 (EDT)
From: Alexander Latzko <latzko@hardees.Rutgers.EDU>
To: aaa-wg@merit.edu
Subject: Take two:Draft submission
Message-ID: <Pine.SOL.4.10.9906251619550.22603-200000@hardees.rutgers.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="-559023410-1639486704-930341584=:22603"
Content-ID: <Pine.SOL.4.10.9906251619551.22603@hardees.rutgers.edu>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-1639486704-930341584=:22603
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.SOL.4.10.9906251619552.22603@hardees.rutgers.edu>

Looks like the attachement failed the first time around.

I've just submitted this draft to the internet-drafts folks hopefully
before the deadline.

Its a strawman on the process of authentication transactions.

Comments bricks stones etc

thanks
alex


-- 
latzko@noc.rutgers.edu 		                                n2mlq
Alex Latzko		+1-732-445-5021 (voice)	+1-732-445-2968 (fax)
Rutgers University Computing Services TD:NOG      Backbone Operations
110 Frelinghuysen Road, Piscataway, NJ 08855-8089

---559023410-1639486704-930341584=:22603
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="id-aaa.txt"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SOL.4.10.9906251620440.22603@hardees.rutgers.edu>
Content-Description: draft-latzko-aaa-authentication.txt
Content-Disposition: attachment; filename="id-aaa.txt"

DQoNCg0KDQoNCg0KZHJhZnQtbGF0emtvLWFhYS1hdXRoZW50aWNhdGlvbi1y
ZXFzLTAwLnR4dCAgICAgICAgICAgICAgIEEgTGF0emtvDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSdXRnZXJz
IFVuaXZlcnNpdHkNCiAgICAgICAgICAgICBBQUEgQXV0aGVudGljYXRpb24g
UmVxdWlyZW1lbnRzIGFuZCBEaXNjdXNzaW9uDQpTdGF0dXMgb2YgdGhpcyBN
ZW1vDQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgYW4gSW50ZXJuZXQtRHJhZnQg
YW5kIGlzIGluICBmdWxsICBjb25mb3JtYW5jZSAgd2l0aA0KICAgYWxsIHBy
b3Zpc2lvbnMgb2YgU2VjdGlvbiAxMCBvZiBSRkMyMDI2Lg0KDQogICBJbnRl
cm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzICBvZiAgdGhlICBJ
bnRlcm5ldCAgRW5naW5lZXJpbmcNCiAgIFRhc2sgIEZvcmNlICAoSUVURiks
ICBpdHMgIGFyZWFzLCAgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUg
dGhhdA0KICAgb3RoZXIgZ3JvdXBzIG1heSAgYWxzbyAgZGlzdHJpYnV0ZSAg
d29ya2luZyAgZG9jdW1lbnRzICBhcyAgSW50ZXJuZXQtDQogICBEcmFmdHMu
DQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZh
bGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5kICBtYXkg
YmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBk
b2N1bWVudHMgYXQgYW55DQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0
ZSAgdG8gIHVzZSAgSW50ZXJuZXQtICBEcmFmdHMgIGFzICByZWZlcmVuY2UN
CiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3
b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhlICBsaXN0ICAgb2YgICBjdXJy
ZW50ICAgSW50ZXJuZXQtRHJhZnRzICAgY2FuICAgYmUgICBhY2Nlc3NlZCAg
IGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0
cy50eHQNCg0KICAgVGhlIGxpc3Qgb2YgSW50ZXJuZXQtRHJhZnQgU2hhZG93
ICBEaXJlY3RvcmllcyAgY2FuICBiZSAgYWNjZXNzZWQgIGF0DQogICBodHRw
Oi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sLg0KDQpBYnN0cmFjdA0KDQog
ICBBIGNvbW1vbiBkZWZpbml0aW9uIGJhc2UgZm9yIEF1dGhlbnRpY2F0aW9u
LCBBdXRob3JpemF0aW9uIGFuZA0KICAgQWNjb3VudGluZyBzZXJ2aWNlIGlu
IHRoZSBpbnRlcm5ldCBpcyBoaWdobHkgZGVzaXJhYmxlIGlmIGZvciBncm93
dGgNCiAgIGluIGEgY29tbW9uIGRpcmVjdGlvbi4gIEl0IGlzIHBvc3NpYmxl
IGZvciBBY2NvdW50aW5nIHRvIHN0YW5kIGFsb25lDQogICBpZiBvbmUgaXMg
d2lsbGluZyB0byB0cnVzdCB3aGF0IHRoZSBvdGhlciBwZXJzb24gc2F5cy4g
IEF1dGhlbnRpY2F0aW9uDQogICBpcyByZXF1aXJlZCBpZiBBdXRob3JpemF0
aW9uIGlzIHRvIHdvcmsuICBUaGlzIGRvY3VtZW50cyBpcyBhDQogICBkaXNj
dXNzaW9uIGFuZCBmbG93IHRyYWNlIG9mIGEgYmFzaWMgYXV0aGVudGljYXRp
b24gZmxvdy4NCg0KICAgQXNzdW1wdGlvbnMNCg0KICAgT25lIGFzc3VtcHRp
b24gd2hpY2ggaXMgbWFkZSBoZXJlIGlzIHRoZXJlIGlzIGEgc2luZ2xlIGNs
aWVudCB0YWxraW5nDQogICB0byBhIHNpbmdsZSBzZXJ2ZXIgZm9yIGVhY2gg
dHJhbnNhY3Rpb24uICBUaGUgc2VydmVyIG1heSBiZSBhIHJlbGF5IHRvDQog
ICBvdGhlciBzZXJ2ZXJzIHdoaWNoIGFjdHVhbGx5IGhvc3QgdGhlIGF1dGhl
bnRpY2F0aW9uIGRhdGEuDQoNCiAgIEEgc2Vjb25kIGFzc3VtcHRpb24gaXMg
c3RhdGUgaXMgb25seSBtYWludGFpbmVkIGZvciB0aGUgbGVuZ3RoIG9mIHRo
ZQ0KICAgYXV0aGVudGljYXRpb24gdHJhbnNhY3Rpb24gYmVmb3JlIGJlaW5n
IHBhc3NlZCB0byB0aGUgYXV0aG9yaXphdGlvbg0KICAgc2VydmVyLCB3aGlj
aCBpdHNlbGYgbWF5IGJlIGEgY28tcHJvY2VzcyBvciBub3QuDQoNCiAgIFRo
ZSB0aGlyZCBhc3N1bXB0aW9uIGlzIGF1dGhlbnRpY2F0aW9uIG1heSBiZSB0
aGUgZW5kIG9mIHRoZQ0KICAgdHJhbnNhY3Rpb24gd2l0aCBubyBmdXJ0aGVy
IGF1dGhvcml6YXRpb24sIG9yIGFjY291bnRpbmcgcGVyZm9ybWVkLg0KDQog
ICBGb3VydGhseSwgbm8gYXNzdW1wdGlvbnMgYXJlIG1hZGUgdG8gdGhlIGFj
dHVhbCBtZWNoYW5pc20gcGVyZm9ybWluZw0KICAgdGhlIHRyYW5zYWN0aW9u
Lg0KDQoNCg0KTGF0emtvICAgICAgICAgICAgICAgICAgIGV4cGlyZXMgRGVj
ZW1iZXIgMTk5OSAgICAgICAgICAgICAgICAgIFtQYWdlIDFdDQoNCg0KDQoN
Cg0KSU5URVJORVQgRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgMjQgSnVuZSAxOTk5DQoNCg0KICAgU2VjdXJp
dHkNCg0KICAgVGhpcyBpcyBlc3NlbnRpYWxseSBhIHNlY3VyaXR5IHNlcnZp
Y2UsIGhvd2V2ZXIsIHRoZSBhY3R1YWwgdHJhbnNhY3Rpb24NCiAgIHNlY3Vy
aXR5IGlzIGJleW9uZCB0aGUgcmVhbG0gb2YgdGhpcyBkb2N1bWVudCBhbmQg
cmVmZXJzIHRvIHdlbGwga25vd24NCiAgIHNlY3VyaXR5IHRlY2huaXF1ZXMg
ZG9jdW1lbnRlZCBlbHNld2hlcmUuDQoNCiAgIFRyYW5zYWN0aW9uIGZsb3cN
Cg0KDQogICBjbGllbnQgc2VuZHMgcmVxdWVzdCBmb3IgYXV0aGVudGljYXRp
b24gc2VydmljZToNCg0KICAgICAgICAgICBlaXRoZXINCiAgICAgICAgICAg
YXMgcGFydCBvZiB0aGUgcmVxdWVzdCB0aGUgY2xpZW50IHNlbmQgYSBoYW5k
c2hha2UNCiAgICAgICAgICAgcmVxdWVzdCB1c2luZyBhIHNoYXJlZCBzZWNy
ZXQga2V5IHNvIHRoZXJlIGlzIHJlYXNvbmFibGUNCiAgICAgICAgICAgdHJ1
c3QgYmV0d2VlbiB0aGUgY2xpZW50IGFuZCBzZXJ2ZXIuDQoNCiAgICAgICAg
ICAgb3INCiAgICAgICAgICAgYXMgcGFydCBvZiB0aGUgcmVxdWVzdCBhIHN5
bW1ldHJpY2FsIGtleSBleGNoYW5nZQ0KICAgICAgICAgICAoZGlmZmllLWhl
bGxtYW4gZm9yIGV4YW1wbGUpIHdpbGwgb2NjdXIgc28gdGhlcmUgaXMgcmVh
c29uYWJsZQ0KICAgICAgICAgICB0cnVzdCBiZXR3ZWVuIHRoZSBjbGllbnQg
YW5kIHNlcnZlci4NCg0KDQogICBzZXJ2ZXIgcmVzcG9uZHMgd2l0aCBvbmUg
b2YgdGhyZWUgdGhpbmdzDQogICAgICAgICAgIDE+eWVzLCBJJ2xsIHNlcnZl
IHlvdSBhbmQgdGhlIHRyYW5zYWN0aW9uIGNvbnRpbnVlcw0KDQogICAgICAg
ICAgIDI+bm8sICBJIHdvbid0IHNlcnZlIHlvdSwgYW5kIHRoZSB0cmFuc2Fj
dGlvbiBzdG9wcw0KDQogICAgICAgICAgIDM+bWF5YmUsIEkgZG9uJ3Qga25v
dyB5b3UsIHNlbmQgbWUgc29tZXRoaW5nIG1lYW5pbmdmdWwNCiAgICAgICAg
ICAgSWYgbWF5YmUsIHRoZW4gYWZ0ZXIgc29tZSBjb25maWd1cmVkIHRpbWVv
dXQsIHlvdSBlaXRoZXIgdHJ5DQogICAgICAgICAgIHRoZSBoYW5kc2hha2Ug
YWdhaW4gb3Igc3RvcC4gVGhlIHRpbWVvdXQgcHJldmVudHMgYSBkZW5pYWwt
DQogICAgICAgICAgIG9mLXNlcnZpY2UgYXR0YWNrLg0KDQoNCiAgIFRoZSBh
dXRoZW50aWNhdGlvbiBzZXJ2ZXIgd2lsbCB0aGVuIHNlbmQgdG8gdGhlIGNs
aWVudCBhIHJlcXVlc3QNCiAgICAgICAgICAgZm9yIHRva2VuKHMpLigxKSBB
bG9uZyB3aXRoIHRoaXMgbWF5IGJlIGEgc2VyaWVzIG9mIGtleQ0KICAgICAg
ICAgICBwaHJhc2UgcHJvbXB0cyBvciBvdGhlciBmaXhlZCBzdHJpbmcgaW5m
b3JtYXRpb24gbmVlZGVkDQogICAgICAgICAgIGJ5IHRoZSBjbGllbnQuDQoN
CiAgICAgICAgICAgW0FmdGVyIHRoZSBpbml0aWFsIGhhbmRzaGFrZSB0aGUg
Y2xpZW50IHRoZW4gc2VuZHMgdG8gdGhlDQogICAgICAgICAgIGF1dGhlbnRp
Y2F0aW9uIHNlcnZlciB0aGUgdG9rZW4ocykgdG8gYmUgYXV0aGVudGljYXRl
ZC4gRG9uZQ0KICAgICAgICAgICBlYXJsaWVyLi4uc2VlIGFib3ZlLl0NCg0K
ICAgICAgICAgICBUaGUgbWluaW11bSB0aGUgdG9rZW4ocykgbXVzdCBjb250
YWluIGlzIGEgdW5pcXVlIGlkZW50aWZpZXINCiAgICAgICAgICAgKHByaW5j
aXBsZSBzdHJpbmcpIGZvciB0aGUgcGVyc29uIG9yIHNlcnZpY2UgYmVpbmcN
CiAgICAgICAgICAgYXV0aGVudGljYXRlZC4gICBUaGUgaW5pdGlhbCB0b2tl
biBleGNoYW5nZSBtYXkgYWxzbw0KICAgICAgICAgICBjb250YWluIHRoZSBh
IHBhc3MgcGhyYXNlIG9yIG90aGVyIGluZm9ybWF0aW9uIGRlcml2YWJsZQ0K
ICAgICAgICAgICBvbmx5IGJlIHRoZSBjbGllbnQgZW50aXR5Lg0KDQoNCg0K
DQpMYXR6a28gICAgICAgICAgICAgICAgICAgZXhwaXJlcyBEZWNlbWJlciAx
OTk5ICAgICAgICAgICAgICAgICAgW1BhZ2UgMl0NCg0KDQoNCg0KDQpJTlRF
Uk5FVCBEUkFGVCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAyNCBKdW5lIDE5OTkNCg0KDQogICAgICAgICAgIERlcGVu
ZGluZyBvbiB0aGUgc2V2ZXJpdHkgbGV2ZWwgcmVxdWlyZWQgdGhlIHJlc3Bv
bnNlIGZyb20NCiAgICAgICAgICAgdGhlIGF1dGhlbnRpY2F0aW9uIHNlcnZl
ciB3aWxsIGJlOg0KDQogICAgICAgICAgIGRlbmllZCAoIGluY2x1ZGVkIHRv
a2VuIGluY29ycmVjdCApDQoNCiAgICAgICAgICAgZGVuaWVkICggb3V0IG9m
IHJlc291cmNlICggdGltZSwgbG9naW4gc2xvdHMsIGNwdSwgd2hhdGV2ZXIp
DQogICAgICAgICAgIGFjY2VwdGVkICggdGhlIHRva2VuIGNvbnRhaW5lZCB1
bmlxdWUgaWRlbnRpZmljYXRpb24NCiAgICAgICAgICAgICAgICAgICAgICBz
dWNoIGFzIHRhdXRvbG9neSwgYSBiaW9tZXRyaWMgc3RyaW5nLCBvcg0KICAg
ICAgICAgICAgICAgICAgICAgIGEgcGFzcyBwaHJhc2UgZW1iZWRkZWQgaW4g
dGhlIGluaXRpYWwgdG9rZW4NCiAgICAgICAgICAgICAgICAgICAgICBleGNo
YW5nZSApDQogICAgICAgICAgIGFjY2VwdGVkIGZvciBmdXJ0aGVyIHByb2Nl
c3NpbmcuICBBdCB0aGlzIHBvaW50IGlmIGENCiAgICAgICAgICAgICAgICAg
ICBjaGFsbGVuZ2UvcmVzcG9uc2UgbWV0aG9kIGlzIGJlaW5nIHVzZWQgdGhl
DQogICAgICAgICAgICAgICAgICAgY2hhbGxlbmdlIHdpbGwgYmUgc2VudC4N
CiAgICAgICAgICAgICAgICAgICBJZiBhIGJpb21ldHJpYyBpcyBiZWluZyB1
c2VkIHRoZSBiaW9tZXRyaWMgZGV2aWNlDQogICAgICAgICAgICAgICAgICAg
KGhhdmluZyBwYXNzZWQgdGhlIGtleSBleGNoYW5nZSBhbmQgYmVpbmcgdHJ1
c3RlZCkNCiAgICAgICAgICAgICAgICAgICB0aGVuIHRoZSBiaW9tZXRyaWMg
d2lsbCBiZSBwcm9tcHRlZCBmb3IgaWYgaXQNCiAgICAgICAgICAgICAgICAg
ICB3YXNuJ3Qgc2VudC4NCg0KICAgICAgICAgICAgICAgICAgIElmIGFmdGVy
IGZ1cnRoZXIgcHJvY2Vzc2luZyAgKHdoaWNoIG1heSBiZSBhbg0KICAgICAg
ICAgICAgICAgICAgIGl0ZXJhdGl2ZSBwcm9jZXNzICkgdmFsaWRpdHkgaXMg
ZGV0ZXJtaW5lZCwgdGhlbg0KICAgICAgICAgICAgICAgICAgIGFuIGFjY2Vw
dCBtZXNzYWdlIHdpbGwgdGhlbiBiZSBzZW50Lg0KDQoNCiAgIFJhbmRvbSB0
aG91Z2h0cyBvZiBjb21wbGV0aW9uLg0KDQogICBUaGUgc2VjdXJpdHkgb2Yg
dGhlIGF1dGhlbnRpY2F0aW9uIHNlcnZlciBpcyBvbmx5IGFzIGdvb2QgYXMg
dGhlDQogICBzZWN1cml0eSBvZiB0aGUgdG9rZW4uICBJZiBzb21lb25lIHN0
ZWFscyB5b3VyIHBhc3N3b3JkLCB5b3UncmUgb3V0IG9mDQogICBsdWNrDQoN
CiAgIFRoZSBiYWNrIGVuZCBkYXRhYmFzZSB1c2VkIGluIHRoaXMgbWVtbyBp
cyBub3Qgc3BlY2lmaWVkIHNpbmNlIHRoYXQncw0KICAgYW4gaW1wbGVtZW50
YXRpb24gc3BlY2lmaWMgcHJvYmxlbS4NCg0KICAgQWxsIHRyYW5zYWN0aW9u
cyBiZXR3ZWVuIHRoZSBjbGllbnQgYW5kIHNlcnZlciB3aWxsIGJlIGVuY3J5
cHRlZC4NCg0KICAgWzFdIGluIHRoaXMgY2FzZSwgYSB0b2tlbiBpcyBkZWZp
bmVkIGFzDQogICAgICAgICAgICcxLiBhIHRoaW5nIHNlcnZpbmcgYXMgYSBz
eW1ib2wsIHJlbWluZGVyLCBvciBkaXN0aW5jdGl2ZSBtYXJrIG9mDQogICAg
ICAgICAgIHNvbWV0aGluZycgaW4gdGhlIGZvcm0gb2YgYSBzdHJpbmcgb2Yg
b2N0ZXRzLg0KDQoNCiAgIEF1dGhvcnMgQWRkcmVzcw0KICAgQWxleCBMYXR6
a28NCiAgIFJ1dGdlcnMgVW5pdmVyc2l0eSBDb21wdXRpbmcgU2VydmljZXMN
CiAgIDExMCBGcmV5bGluZ2h1eXNlbiBSb2FkDQogICBQaXNjYXRhd2F5LCBO
ZXcgSmVyc2V5IDA4ODU0LTgwODkNCg0KICAgVGVsZXBob25lOiAxIDczMiA0
NDUgNTAyMQ0KICAgRW1haWw6ICAgICBsYXR6a29Abm9jLnJ1dGdlcnMuZWR1
DQoNCg0KDQoNCkxhdHprbyAgICAgICAgICAgICAgICAgICBleHBpcmVzIERl
Y2VtYmVyIDE5OTkgICAgICAgICAgICAgICAgICBbUGFnZSAzXQ0KDQoNCg==
---559023410-1639486704-930341584=:22603--


From owner-aaa-bof@merit.edu  Mon Jun 28 11:18:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09727
	for <aaa-wg-archive@nic.merit.edu>; Mon, 28 Jun 1999 11:18:16 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 28C3E44418; Mon, 28 Jun 1999 11:17:54 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0ED9C4441B; Mon, 28 Jun 1999 11:17:54 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 10C8C44418
	for <aaa-wg@Merit.edu>; Mon, 28 Jun 1999 11:17:53 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id LAA25421; Mon, 28 Jun 1999 11:17:48 -0400 (EDT)
Message-ID: <3777921C.2E649C8A@Merit.edu>
Date: Mon, 28 Jun 1999 11:17:48 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steven Bakker <steven@icoe.att.com>
Cc: AAA WG <aaa-wg@merit.edu>
Subject: Re: Submission to WG: <draft-bakker-middleware-aaa.txt> - AAA 
 Considerations for Middleware
References: <9522.930337963@spinach.icoe.att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Mr. Bakker,

I just read your draft, "AAA Considerations for Middleware", with
interest.  I have been working with the authorization subgroup of the
AAA WG.  We are attempting to develop an architecture broad enough to
support a wide range of authorization applications.  From this, we are
in the process of deriving authorization requirements.  We have recently
documented our work in an Internet Draft titled "AAA Authorization
Architecture and Requirements" and available at:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-authorization-reqs-00.txt

I believe that our architecture encompasses your Cloud Model in the
sense that it allows for it without requiring it.  We considered that in
some applications, the User may have a contractual relationship only
with what we call his User Home Organization (translate ISP in your
terminology) and not with what we call the Service Provider (translate
CSP in your terminology).  We discuss contractual relationships and the
chaining of trust relationships (e.g., User to User Home Organization
and User Home Organization to Service Provider).  There is brief
discussion of the role of a broker acting as middleman between the User
Home Organization and the Service Provider in the architecture section
with more extensive consideration of the broker role given in some of
the examples in the appendix.

I wonder if you would be so good as to review our draft from the point
of view of considering whether our authorization architecture adequately
supports middleware applications and the Cloud Model.  You will notice
that the requirements section is largely a placeholder to be filled in,
so if you have specific suggestions for authorization requirements that
could be added in the next revision, we would be grateful.

Steven Bakker wrote:
> 
> Folks,
> 
> I just submitted the enclosed draft to the editor.  I'd like to get
> comments on this, especially whether this is relevant to the WG or I
> should go and play somewhere else.
> 
> It's a bunch of ideas I came up with regarding AAA (and trust) in a more
> advanced services network (middleware and all that jazz).  I think it has
> relevance to AAA and perhaps to policy(?)
> 
> Thanks in advance,
> Steven Bakker
> 
>   --------------------------------------------------------------------------------
>                                                         Name: draft-bakker-middleware-considerations-aaa.txt
>    draft-bakker-middleware-considerations-aaa.txt       Type: Plain Text (text/plain)
>                                                  Description: draft-bakker-middleware-considerations-aaa.txt

-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Mon Jun 28 15:27:17 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA13627
	for <aaa-wg-archive@nic.merit.edu>; Mon, 28 Jun 1999 15:27:17 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B853F44430; Mon, 28 Jun 1999 15:26:59 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9BC0D44432; Mon, 28 Jun 1999 15:26:59 -0400 (EDT)
Received: from hardees.rutgers.edu (hardees.rutgers.edu [165.230.165.66])
	by segue.merit.edu (Postfix) with ESMTP id 8797844430
	for <aaa-wg@merit.edu>; Mon, 28 Jun 1999 15:26:58 -0400 (EDT)
Received: from localhost (latzko@localhost)
	by hardees.rutgers.edu (8.8.8/8.8.8) with ESMTP id PAA28072
	for <aaa-wg@merit.edu>; Mon, 28 Jun 1999 15:27:14 -0400 (EDT)
Date: Mon, 28 Jun 1999 15:27:14 -0400 (EDT)
From: Alexander Latzko <latzko@hardees.Rutgers.EDU>
To: aaa-wg@merit.edu
Subject: draft: Content Services AAA Requiremenents
Message-ID: <Pine.SOL.4.10.9906281525170.19605-100000@hardees.rutgers.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Hi,

This got lost in mails, and now its too late to get it in for the Oslo
draft pile.  In any case, this is a strawman draft Siggy Maier and I 
cooked up about content services.

Please send us some comments so we have something to talk about in 
Oslo.

Thanks
alex

INTERNET-DRAFT 						Siggy Maier 
Expires:                                                Nortel Networks
							Alex Latzko
							Rutgers University

Content Services AAA Requirements

       1. Status of this Memo

       This document is an Internet-Draft and is in full
       conformance with all provisions of Section 10 of RFC2026.

       Internet-Drafts are working documents of the Internet
       Engineering Task Force (IETF), its areas, and its working
       groups.  Note that other groups may also distribute working
       documents as Internet-Drafts.

       Internet-Drafts are draft documents valid for a maximum of
       six months and may be updated, replaced, or obsoleted by
       other documents at any time.  It is inappropriate to use
       Internet-Drafts as reference material or to cite them other
       than as "work in progress."

       The list of current Internet-Drafts can be accessed at
       http://www.ietf.org/ietf/1id-abstracts.txt

       The list of Internet-Draft Shadow Directories can be
       accessed at http://www.ietf.org/shadow.html.

 
       2.) Abstract

       This document describes some of the AAA requirements for
Content/application services as input toward the general AAA requirements
being defined by the AAA WG.




3.) Context:

Content/applications such as News, eMail, FTP servers, Games, Specialty
content (ie. vertical industry databases, financial information, etc.),
Unified messaging, On-line magazines subscriptions, etc.; require AAA
services to control who has access, what content they can access and the
ability to bill for that access.

Requests for  AAA services will be directly from the content/application
server, or from a content/application broker. A broker function may be used
to support the following functionality:
*	Single sign-on to multiple applications/content sources (ie.
minimize the number of trust relationships)
*	Reselling 3rd party applications/content
*	Police what services a user can access
*	State aware assignment of users across multiple servers (ie. load
sharing)
*	Service interworking 


4.) Authentication requirements:

a)	The authentication request is coming from a content/application
server must have a field and value that identifies the particular
content/application for which the user is being authenticated. If the
user/group/organization is not a valid user, or not valid for the particular
content/application, the authentication request should be rejected.
b)	In the event that the authentication request is coming from a broker
application a unique value should be used to identify the request is coming
from a broker. In this event the authentication function should simply
authenticate the user, and the authorization function should return a list
of the content/application services that the user/group/organization has
authenticated access to. The broker would then restrict the end user access
to only these services 
c)	The authentication could be based on the actual end user, the group
the end user is associated with, or the organization (ie. corporation,
government), or a combination of these. This means that depending on the
requirements of the content/application, the subscription may be based on
the end user, a group (ie. a department) or an organization.
d)	The complete range of authentication mechanisms should be supported
including simple assertion, shared secret, mutual authentication, public key
& private key, tokens, and biometrics. Content/application will vary in the
degree of security/proof they require.
e)	The value used to identify the more common applications/content
could be standardized, and other content/application could have values
assigned by the vendor.
f)	The authentication request should have a variety of standard
attributes, and vendor specific attributes that can be used as a checklist
for authentication. Standard attributes may include the ID of the server or
broker making the request, the content/application ID, the
user/group/organization requesting access, appropriate security information
(ie. password, token, certificate), local time of day and date, etc. .
Content/application vendor specific attributes may include that ability to
include any special end user service requests regarding service options or
QoS, etc.
g)	There is a need to support pre-paid services. The authentication
server would have to perform a 2-step authentication process, where after
authenticating the user, it also authenticates with a pre-paid services
billing server to ensure they still have prepaid service access. 

5.) Authorization

a)	If the authentication request from an content/application server is
successful, the authorization server should return the content/application
specific authorization attributes that reflects the end
users/group/organization's service subscription profile
b)	If the authentication request from a broker is successful, the list
of content/application services the user is allowed to access is returned to
the broker. Additionally the following options should be supported:
*	The authorization attributes for each authorized service are
returned to the broker
*	The authorization attributes are requested by the
content/application server when the end user connects to that server
*	The broker requests the appropriate authorization attributes when
the end user selects a particular service and passes them to the
content/application server.
c)	The authorization server may need to perform concurrency control to
ensure the same user ID and security mechanism is not currently in use, or
does not have more than "x" concurrent sessions. The authorization server
should monitor accounting records to maintain awareness of active sessions a
user has, as well as support the option to query/audit the
content/application server or broker to determine how many active sessions a
user has. 
d)	For pre-paid service support, the authorization function should
communicate back to the server/broker how much time or value is left, along
with the attributes of the subscribed service.
e)	The authorization server should at any time be able to issue a
command to a broker or content/application server to disconnect a user. This
may be due to fraud detection, overdue  payment, etc. 
f)	The authorization server should be able to change the authorization
attributes based on time of day or day of week, the actual capabilities of
the content/application server the user is connected to


6.) Accounting

a)	Accounting records generated by the content/application servers or
the brokers should contain standard attribute such as the identity of
user/group/organization, the length of the session, amount of data, unique
session ID, as well as standard attributes for more common
applications/content services as well as allowing for vendor specific
extensions
b)	Accounting records should be sent at the start and stop of any
session with the appropriate usage metrics for the content/application 
c)	The accounting server should be able to query the
content/application server to audit the status of current sessions to be
able to validate that long sessions are still active (ie. protect against
lost stop or start accounting records)
d)	Accounting records need to be sent to accounting collection device
or a backup to ensure secure confirmed delivery of all accounting data; and
the accounting clients should be able to send accounting records to multiple
targets



7.) Other

a)	There needs to be the option to require all connections between the
broker or the content/application server and the AAA server to be over
secure links (ie. IPSEC) to ensure AAA security is not compromised


8.) Specific Examples

Legacy timesharing services will be able to use a generic AAA
mechanism for many of the features now served by a local database.

The strength of negotiation of the Authentication feature of AAA will be
left to that particular section of the AAA-WG.  Severity may range from
simple acceptance to a multi layer handshake.

Three specific examples of legacy timeshare features will be detailed
herein.  

- example 1 (login) 

The first legacy timesharing application to require AAA features is
the standard problem of logging in to a system.  In order to login a
AAA based solution MUST accept a user identifier of some number of
octets and whatever Authentication method has been specified, and
return a common code of success or failure.  Authentication support
MUST allow for server side selection of the Authentication technology
to be use on a per user basis.  AAA support for login Authorization
SHOULD support features for controlling which console (or virtual
console ) someone may login at, and SHOULD support some form of time
control, including but not limited to time of day, length of
session,and expiration.  The AAA server SHOULD be able to support
logging of all login attempts.

The Authorization section MAY also offer support for access control
lists or other security related keys.

The Accounting section MUST produce a record indicating the success or
failure of the login attempt, to include but not limited to the
terminal (or virtual terminal), time of day, success or failure.
Since login support is stateless, the Accounting section may if
possible support functionality for both logging exec level commands
and logout time,and usage.

-example 2 (ftp)

The second legacy timesharing application to require AAA features is
FTP (rfc lots).  FTP actually can require more support from a AAA
server than example 1 above.

Authentication for FTP  MUST accept a user identifier of some number 
of octets and support whatever Authentication method has been specified for 
the user, and MUST return a common code for success or failure.  The AAA 
server SHOULD be able to log each attempt.

The Authorization feature of the AAA server MUST at a minimum support 
the ability to control access to available files, and SHOULD also be
able to control access on a time and incoming host basis.

The Accounting features of the AAA server MUST be able to log all
transactions used by the FTP session, including but not limited to the
file identifier (to include file length) , the time stamp, the user
identifier (to include remote host information).





-- 
latzko@noc.rutgers.edu 		                                n2mlq
Alex Latzko		+1-732-445-5021 (voice)	+1-732-445-2968 (fax)
Rutgers University Computing Services TD:NOG      Backbone Operations
110 Frelinghuysen Road, Piscataway, NJ 08855-8089





From owner-aaa-bof@merit.edu  Mon Jun 28 15:50:31 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA13904
	for <aaa-wg-archive@nic.merit.edu>; Mon, 28 Jun 1999 15:50:31 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A818D44434; Mon, 28 Jun 1999 15:50:13 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8E8A444435; Mon, 28 Jun 1999 15:50:13 -0400 (EDT)
Received: from smtpgw02.wanmail.net (unknown [209.154.194.61])
	by segue.merit.edu (Postfix) with ESMTP id 736BA44434
	for <aaa-wg@merit.edu>; Mon, 28 Jun 1999 15:50:12 -0400 (EDT)
Received: from wcomexch1.wcom.net (wcomexch1.wcom.net [209.154.236.12])
	by smtpgw02.wanmail.net (8.9.1/8.9.1) with ESMTP id PAA07041;
	Mon, 28 Jun 1999 15:50:11 -0400 (EDT)
Received: by wcomexch1.wcom.net with Internet Mail Service (5.5.2448.0)
	id <M0X6VYMN>; Mon, 28 Jun 1999 15:54:17 -0400
Message-ID: <9A74C89D6696D2118E500008C7BA7C56BF6986@wcomexch1.wcom.net>
From: "Beadles, Mark A." <MBeadles@wcom.net>
To: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Cc: "nasreqng list (E-mail)" <nasreq@tdmx.rutgers.edu>
Subject: FW: I-D ACTION:draft-ietf-nasreq-criteria-01.txt
Date: Mon, 28 Jun 1999 15:54:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BEC1A0.016F5D1A"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BEC1A0.016F5D1A
Content-Type: text/plain;
	charset="iso-8859-1"

This draft from NASREQ also serves as input to AAA.  It contains
requirements for AAA protocols used by Network Access Servers.

+ Mark Anthony Beadles +  UUNET Product Development  + 
+  mbeadles@wcom.net   + http://networking.us.uu.net +
+  Voice 614.723.1941  +       Fax 614.723.8407      +



-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Monday, 28 June 1999 7:45 AM
Cc: nasreq@tdmx.rutgers.edu
Subject: I-D ACTION:draft-ietf-nasreq-criteria-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Network Access Server Requirements Working
Group of the IETF.

	Title		: Criteria for Evaluating Network Access Server 
                          Protocols
	Author(s)	: M. Beadles
	Filename	: draft-ietf-nasreq-criteria-01.txt
	Pages		: 11
	Date		: 25-Jun-99
	
This document analyzes and defines requirements for protocols used  by
Network  Access Servers (NAS).  Protocols used by NAS's may be divided
into four spaces:  Access protocols, Network protocols, AAA protocols,
and  Management  protocols.   Primary  attention  is  given to setting
requirements for AAA protocols, since  that  space  is  currently  the
least well defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nasreq-criteria-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-nasreq-criteria-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nasreq-criteria-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------_=_NextPart_000_01BEC1A0.016F5D1A
Content-Type: message/rfc822

To: 
Subject: 
Date: Mon, 28 Jun 1999 15:54:17 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01BEC1A0.016F5D1A"


------_=_NextPart_002_01BEC1A0.016F5D1A
Content-Type: text/plain



------_=_NextPart_002_01BEC1A0.016F5D1A
Content-Type: application/octet-stream;
	name="ATT21499"
Content-Disposition: attachment;
	filename="ATT21499"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990625144322.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nasreq-criteria-01.txt

------_=_NextPart_002_01BEC1A0.016F5D1A
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-ietf-nasreq-criteria-01.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01BEC1A0.016F5D1A--

------_=_NextPart_000_01BEC1A0.016F5D1A--


From owner-aaa-bof@merit.edu  Wed Jun 30 03:38:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id DAA07512
	for <aaa-wg-archive@nic.merit.edu>; Wed, 30 Jun 1999 03:38:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id CB73E44446; Wed, 30 Jun 1999 03:38:22 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A5F344444C; Wed, 30 Jun 1999 03:38:22 -0400 (EDT)
Received: from mushroom.icoe.att.com (icoe-gate.icoe.att.nl [194.242.71.50])
	by segue.merit.edu (Postfix) with ESMTP
	id 6C9A044446; Wed, 30 Jun 1999 03:38:20 -0400 (EDT)
Received: by mushroom.icoe.att.com; id JAA11701; Wed, 30 Jun 1999 09:04:37 +0200 (MET DST)
Received: from unknown(135.76.170.11) by mushroom.icoe.att.com via smap (4.0a)
	id xma011695; Wed, 30 Jun 99 09:03:55 +0200
Received: from spinach.icoe.att.com (spinach.icoe.att.com [135.76.170.7])
	by watermelon.icoe.att.com (8.8.8/8.8.8) with ESMTP id JAA03450;
	Wed, 30 Jun 1999 09:41:26 +0200 (MET DST)
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Re: Submission to WG: <draft-bakker-middleware-aaa.txt> - AAA Considerations for Middleware 
To: "David W. Spence" <DWSpence@merit.edu>
Cc: Steven Bakker <steven@icoe.att.com>, AAA WG <aaa-wg@merit.edu>
X-Organisation: AT&T ICoE
X-Telephone: +31.20.4097.643
X-Fax: +31.20.453.1574
X-Fruit-of-the-day: Mandarin orange
X-Drink-of-the-day: grappa
X-URL: http://www.icoe.att.com
References: <3777921C.2E649C8A@Merit.edu> 
In-reply-to: Message from "David W. Spence" <DWSpence@Merit.edu> 
   of Mon, 28 Jun 1999 11:17:48 -0400 
Comments: Disinformation is not as good as datinformation.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 30 Jun 1999 09:32:46 +0100
Message-ID: <14189.930731566@spinach.icoe.att.com>
From: Steven Bakker <steven@icoe.att.com>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

>>>>> On Mon, 28 Jun 1999, "DWS" == David W. Spence wrote:

David,

  DWS> I wonder if you would be so good as to review our draft from the
  DWS> point of view of considering whether our authorization architecture
  DWS> adequately supports middleware applications and the Cloud Model.
  DWS> You will notice that the requirements section is largely a
  DWS> placeholder to be filled in, so if you have specific suggestions for
  DWS> authorization requirements that could be added in the next revision,
  DWS> we would be grateful.

I'd be happy to.

Cheers,
Steven



From owner-aaa-bof@merit.edu  Wed Jun 30 10:40:02 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA11911
	for <aaa-wg-archive@nic.merit.edu>; Wed, 30 Jun 1999 10:40:02 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id ADB2644468; Wed, 30 Jun 1999 10:39:43 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 940C84446C; Wed, 30 Jun 1999 10:39:43 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by segue.merit.edu (Postfix) with ESMTP id 9AF1D44468
	for <aaa-wg@merit.edu>; Wed, 30 Jun 1999 10:39:37 -0400 (EDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.3) with SMTP id QAA11955
	for <aaa-wg@merit.edu>; Wed, 30 Jun 1999 16:39:36 +0200 (MET DST)
Received: from malsels by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id QAA09239; Wed, 30 Jun 1999 16:39:36 +0200
Message-ID: <377A2C27.7508@era-t.ericsson.se>
Date: Wed, 30 Jun 1999 16:39:35 +0200
From: Fergal Ladley <Fergal.Ladley@era-t.ericsson.se>
Organization: Ericsson Radio Systems AB
X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: aaa-wg@merit.edu
Cc: erafela@era-t.ericsson.se
Subject: An Internet Draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi all,

I have written a draft which I will present to the mobile IP WG in Oslo. 
It deals with one specific case of authentication and authorisation so
while it may be rather too narrow in scope for the AAA WG, the ideas
might be of some interest to some members of the group.

Cheers,
Fergal.

Details:

Title:    A DIAMETER-based Authentication and Access Control Protocol
Author:   Fergal Ladley
Filename: draft-ladley-diameter-pr-00.txt
Pages:    35
Date:     23-Jun-99
Abstract:

   This document specifies a DIAMETER-based protocol which may be used
   to authenticate and perform access control of users on an IP network.
   The protocol allows mutual authentication of a user and a network
   and a means based on the IPSec Authentication Header for the network
   to deny access to unauthorised users.

You can get it at

http://www.ietf.org/internet-drafts/draft-ladley-diameter-pr-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
        "get draft-ladley-diameter-pr-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Or you can get it by e-mail:

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ladley-diameter-pr-00.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail   
        readers exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

Or you can get it here:

ftp://ftp.ietf.org/internet-drafts/draft-ladley-diameter-pr-00.txt


